| + kuno_ (sid299442@id-299442.helmsley.irccloud.com) | 00:11 | |
| + ex--parrot (~fincham@user/ex-parrot) | 00:11 | |
| + bluerise_ (~bluerise@p5b0acf0d.dip0.t-ipconnect.de) | 00:12 | |
| + jryans_ (sid12941@id-12941.ilkley.irccloud.com) | 00:13 | |
| + kklimonda (~kklimonda@user/kklimonda) | 00:13 | |
| + Asmadeus_ (~asmadeus@240b:13:8c80:d300::42:13) | 00:14 | |
| - romi (QUIT: Ping timeout: 264 seconds) (~romi@user/romi) | 00:15 | |
| - kuno (QUIT: Ping timeout: 264 seconds) (sid299442@id-299442.helmsley.irccloud.com) | 00:15 | |
| - bluerise (QUIT: Ping timeout: 264 seconds) (~bluerise@user/bluerise) | 00:15 | |
| - Asmadeus (QUIT: Ping timeout: 264 seconds) (~asmadeus@240b:13:8c80:d300::42:13) | 00:15 | |
| - jryans (QUIT: Read error: Connection reset by peer) (sid12941@id-12941.ilkley.irccloud.com) | 00:15 | |
| - kklimonda_ (QUIT: Quit: ZNC 1.8.2+deb2+b1 - https://znc.in) (~kklimonda@user/kklimonda) | 00:15 | |
| - erle (QUIT: Ping timeout: 264 seconds) (~erle@2a02:8109:da40:c4:6c9d:80a0:ec0:e8ca) | 00:15 | |
| - ex-parrot (QUIT: Ping timeout: 264 seconds) (~fincham@user/ex-parrot) | 00:15 | |
| - ezequielg (QUIT: Ping timeout: 264 seconds) (sid363064@id-363064.uxbridge.irccloud.com) | 00:15 | |
| + erle (~erle@2a02:8109:da40:c4:6c9d:80a0:ec0:e8ca) | 00:15 | |
| * kuno_ -> kuno | 00:15 | |
| * jryans_ -> jryans | 00:15 | |
| + ezequielg (sid363064@id-363064.uxbridge.irccloud.com) | 00:17 | |
| + romi (~romi@user/romi) | 00:18 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 00:20 | |
| - jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@utdpat241106.utdallas.edu) | 00:39 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.8.188) | 01:00 | |
| + Ar|stote|is (~linx@149.210.8.188) | 01:01 | |
| + Guest68 (~Guest92@2603-900a-110c-5200-8062-ad5f-1806-295d.inf6.spectrum.com) | 01:15 | |
| Guest68 | hello people | 01:23 |
|---|---|---|
| * bluerise_ -> bluerise | 01:27 | |
| - bluerise (QUIT: Changing host) (~bluerise@p5b0acf0d.dip0.t-ipconnect.de) | 01:28 | |
| + bluerise (~bluerise@user/bluerise) | 01:28 | |
| Guest68 | 8) | 01:39 |
| - mjw (QUIT: Ping timeout: 260 seconds) (~mjw@gnu.wildebeest.org) | 02:15 | |
| - cwebber`` (QUIT: Remote host closed the connection) (~user@2600:6c64:7e3f:fdb0::6db) | 02:37 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 02:57 | |
| - vagrantc (QUIT: Ping timeout: 240 seconds) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 03:19 | |
| - ajr (QUIT: Quit: Connection closed for inactivity) (uid609314@user/ajr) | 03:21 | |
| + jacobk (~quassel@129.110.242.173) | 03:25 | |
| Guest68 | I heard there might be some changes to MNT Reform soon so it can more easily run Ubuntu. Is that true, how long until that comes out? | 03:47 |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@129.110.242.173) | 04:52 | |
| + jacobk (~quassel@utdpat242024.utdallas.edu) | 05:01 | |
| - jacobk (QUIT: Ping timeout: 240 seconds) (~quassel@utdpat242024.utdallas.edu) | 05:21 | |
| noam | How accurate is https://source.mnt.re/reform/reform-som-template ? | 05:41 |
| noam | minute: assuming I read the schematic correctly, and did the measurement correctly, the 5V and ground pins are shorted. | 05:47 |
| + jacobk (~quassel@108.218.212.124) | 05:48 | |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@108.218.212.124) | 06:03 | |
| + jacobk (~quassel@108.218.212.124) | 06:05 | |
| noam | ...minute: I'm also reading ~20 ohms across C709, which I'm fairly sure is further evidence in favor of a shorted cap :/ | 06:08 |
| - jacobk (QUIT: Excess Flood) (~quassel@108.218.212.124) | 06:09 | |
| + jacobk (~quassel@108.218.212.124) | 06:09 | |
| noam | well - the component that I'm 90% sure is a ceramic cap by the voltage pins, which I'm pretty sure is labelled C709 but tbh my ability to read it is bad enough that I felt the need to write this sentence, so | 06:10 |
| - jacobk (QUIT: Ping timeout: 240 seconds) (~quassel@108.218.212.124) | 06:50 | |
| + jacobk (~quassel@64.189.201.150) | 07:32 | |
| josch | Guest68: where did you hear that? | 07:34 |
| + chomwitt (~chomwitt@2a02:587:7a1a:f800:1ac0:4dff:fedb:a3f1) | 07:37 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 08:12 | |
| Boostisbetter | Team, suspend has been flawless for me. There are some things that can interfere with suspend, but so far the list is small. | 08:13 |
| + klardotsh_ (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 08:21 | |
| - klardotsh (QUIT: Ping timeout: 248 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 08:22 | |
| - klardotsh_ (QUIT: Ping timeout: 255 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 08:26 | |
| - Guest68 (QUIT: Quit: Client closed) (~Guest92@2603-900a-110c-5200-8062-ad5f-1806-295d.inf6.spectrum.com) | 09:06 | |
| vkoskiv | Boostisbetter: How long do you typically keep it suspended for? Just leave it plugged in and suspend when not using? | 09:41 |
| vkoskiv | For me, hibernate will be even more useful when that works, since I like to carry the thing around and get back to where I was when opening it up | 09:41 |
| Boostisbetter | vkoskiv: hibernation is the answer I think. I hope we can get it working. | 09:54 |
| Boostisbetter | vkoskiv: My Reform is plugged in most of the time and suspended. When I need it at the desk I leave it plugged in, but if I am going to work and want to bring it with, it is unplugged. At all times when not in use it is suspended. | 09:55 |
| Boostisbetter | My Reform has been off off for less than an hour at this point | 09:55 |
| Boostisbetter | total | 09:55 |
| Boostisbetter | vkoskiv: Also I was up to over 300 successful resumes. I think 6.5 has fixed the regression completely (I think 6.4 did as well). | 10:05 |
| minute | my reform lpc survived the night without resetting itself. | 10:54 |
| minute | still says 100% | 10:55 |
| Boostisbetter | minute: woot! | 11:26 |
| Boostisbetter | BTW if I use the @ sign and then a user here does it still mention them? | 11:26 |
| Boostisbetter | minute just testing | 11:26 |
| cmahns | generally irc clients highlight on any mention of your name and don't require the @ sign | 11:27 |
| - buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org) | 11:38 | |
| + buckket (~buckket@vps.buckket.org) | 11:39 | |
| + mjw (~mjw@gnu.wildebeest.org) | 11:47 | |
| josch | Boostisbetter: tha depends on the irc client. Try writing something to @josch to see if irssi does or does not consider the @ part of the text to highlit me on. | 11:50 |
| - Boostisbetter (QUIT: Ping timeout: 255 seconds) (4a410829d7@irc.cheogram.com) | 12:12 | |
| abortretryfail | vkoskiv: have you tried hibernating yours yet? | 12:19 |
| vkoskiv | Just the few times when I was investigating, mine doesn't come up from suspend either | 12:20 |
| vkoskiv | Though it's with A311D, so it needs work | 12:21 |
| abortretryfail | Hmm, yeah different animal. | 12:21 |
| + Guest92 (~Guest92@2603-900a-110c-5200-8062-ad5f-1806-295d.inf6.spectrum.com) | 12:40 | |
| - mjw (QUIT: Ping timeout: 248 seconds) (~mjw@gnu.wildebeest.org) | 12:46 | |
| * Asmadeus_ -> Asmadeus | 12:48 | |
| + cwebber (~user@user/cwebber) | 12:48 | |
| * mark_ -> mjw | 12:50 | |
| Guest92 | josch - https://mntre.com/media/reform_md/2022-07-01-july-update.html CTRL+F Ubuntu | 13:04 |
| josch | so, i'm maintaining the changes to Debian that make it run well on the reform. Theoretically those could be added to Ubuntu as well but I haven't heard of somebody doing that work. | 13:06 |
| flowy | the 1tb transcend ssd that shipped with my reform is starting to give unrecoverable read errors. i've just ordered a hynix p31 nvme, as it seems highly regarded for energy efficiency, and someone reported it working in the MNT community forums. | 13:27 |
| vkoskiv | How many TBW? | 13:27 |
| flowy | this will provide the opportunity to start fresh so i'm curious to try josch's images at reform.debian.net | 13:27 |
| flowy | 1TB | 13:28 |
| vkoskiv | Yeah but how many terabytes written | 13:28 |
| vkoskiv | `sudo smartctl -x /dev/nvme0` | 13:28 |
| flowy | aah right | 13:28 |
| vkoskiv | I bought the cheapest possible WD blue nvme, I'm not holding much hope that it'll last very long :D | 13:28 |
| flowy | 4.38 TB read, only 3.7 TBW | 13:30 |
| flowy | 15 'Media and Data Integrity Errors' | 13:30 |
| vkoskiv | That's... Really low? How many unsafe shutdowns? Not sure how bad that is for an NVMe | 13:31 |
| vkoskiv | Mine has 300, I think every shutdown on the reform increments it | 13:31 |
| flowy | 166 unsafe shutdowns somehow, out of 415 cycles total | 13:31 |
| vkoskiv | I have 309 total, 300 unsafe. shutdowns. 1.05TBW. | 13:31 |
| vkoskiv | Do you just see those errors in dmesg or is there a way to check it? | 13:32 |
| flowy | what unearthed the read errors was some investigation into weird flatpak db messages. running 'flatpak repair' ran into the bad sectors and reinstalled those packages | 13:32 |
| vkoskiv | I guess smartctl shows a number of error log entries, mine has 1. | 13:33 |
| vkoskiv | But my 10% spare threshold is still at 0% used | 13:33 |
| flowy | yeah, i found the messages in dmesg while doing flatpak repair. might be possible to find them again in systemd's logs | 13:33 |
| flowy | maybe i shouldn't be so concerned | 13:33 |
| flowy | though at this point i got sort of into the idea of comparing energy consumption between the new and old ssds | 13:34 |
| vkoskiv | I'm surprised you saw errors all the way up in userspace w/ flatpak, though. I'd assume the kernel hides those until it's not possible anymore. | 13:34 |
| flowy | yeah well they were unrecoverable read errors. so the data couldn't be read anymore | 13:34 |
| vkoskiv | Yeah, since my Reform only uses roughly ~10 watts at full CPU load, I think a good energy-efficient SSD would make a big impact on battery life. | 13:35 |
| vkoskiv | If you find a good SSD with low power consumption, I'd love to read about it on the forum perhaps. | 13:35 |
| abortretryfail | every shutdown increments as unsafe? | 13:35 |
| vkoskiv | I think that's the case, yes. I don't know if anyone has investigated that yet. | 13:35 |
| abortretryfail | ACTION has a Phison emmc rescued from a Steam Deck | 13:36 |
| abortretryfail | it seems to be pretty lean on power use. | 13:36 |
| flowy | i see debian.reform.net uses debian CI systems? does that mean the image is built on debian infrastructure? | 13:40 |
| flowy | err reform.debian.net * | 13:40 |
| sigrid | vkoskiv: yes, the reason was mentioned a few times here | 13:40 |
| sigrid | idk if anybody fixed it for linux. on 9front it does not do unsafe shutdowns | 13:41 |
| abortretryfail | 162 "unsafe" shutdowns huh. | 13:41 |
| abortretryfail | heh, yep. shutdown -h now increments that. wonderful | 13:43 |
| josch | flowy: the image is not built on "debian infrastructure" but on infrastructure administrated by the debian project via the debian.net team | 13:51 |
| flowy | josch: thanks. your work is much appreciated! | 13:54 |
| flowy | i'll try it out when my new ssd arrives | 13:54 |
| josch | cool, please report bugs :) | 13:55 |
| - Guest92 (QUIT: Quit: Client closed) (~Guest92@2603-900a-110c-5200-8062-ad5f-1806-295d.inf6.spectrum.com) | 14:00 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 14:03 | |
| Boostisbetter | @josch testing. | 14:07 |
| Boostisbetter | No, Dino doesn't do that, this was from the conversejs client. I'll try it again in just a second. | 14:08 |
| josch | Boostisbetter: yes, prefixing my name with an @ still highlights me | 14:11 |
| Boostisbetter | josch how about now? | 14:13 |
| SarioScream | Most clients will highlight/ping if your nick is anywhere in a message | 14:13 |
| Boostisbetter | awesome, just wanted to check that it was working with ConverseJS, as it does tagging pretty easily. | 14:14 |
| minute | SarioScream: guess how that works out for me | 14:15 |
| minute | Boostisbetter: does conversejs have direct IRC support or are you bridging xmpp to irc somehow? | 14:15 |
| Boostisbetter | minute bridging using cheaogram on XMPP | 14:16 |
| SarioScream | Boostisbetter: on IRC highlighting/pinging is handled by your client, so it doesn't matter which client the person pinging you is using | 14:16 |
| Boostisbetter | SarioScream awesome! Good to know. | 14:17 |
| Boostisbetter | I can get a little obsessed with formatting. The way Conversations on Android does it is with a colon at the end of the name, and I adopted this as my standard, but I am letting go of that and jus doing it the way the client permits. | 14:18 |
| Boostisbetter | Glad it is working regardless. | 14:18 |
| minute | Boostisbetter: interesting. is cheogam sort of a bridge service that you run on your server? | 14:18 |
| minute | cheogram | 14:18 |
| Boostisbetter | minute no it is a service that the account (on my server) is connected to | 14:19 |
| minute | i am sometimes thinking if we could make this chat here web-accessible including history/logs | 14:19 |
| Boostisbetter | I have 3 xmpp accounts, and this account is the one that is setup to use that 3rd party bridge. | 14:19 |
| SarioScream | Boostisbetter: the nick: format is very common as an autocomplete | 14:19 |
| Boostisbetter | minute I can tell you that it is a pretty reliable way to bridge from xmpp to irc. | 14:19 |
| minute | ok | 14:20 |
| - Boostisbetter (QUIT: Ping timeout: 264 seconds) (4a410829d7@irc.cheogram.com) | 14:24 | |
| - abortretryfail (QUIT: Quit: WeeChat 3.6) (~arf@146.ip-149-56-132.net) | 14:25 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 14:26 | |
| + abortretryfail (~arf@146.ip-149-56-132.net) | 14:29 | |
| Boostisbetter | minute every once in a while the system kicks me out, but I believe that is because the cheogram server is being restarted for updates, etc. | 14:31 |
| Boostisbetter | so if I just toggle the account I get back in, usually. | 14:31 |
| Boostisbetter | I think sometimes libera chat sees this as an abusive client and they sometimes block me for a time, but this is rare. | 14:31 |
| + sevan (~sevan@user/venture37) | 15:34 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 16:02 | |
| - mark_ (QUIT: Ping timeout: 258 seconds) (~mjw@gnu.wildebeest.org) | 16:08 | |
| - jacobk (QUIT: Ping timeout: 272 seconds) (~quassel@64.189.201.150) | 16:19 | |
| + jacobk (~quassel@utdpat241106.utdallas.edu) | 16:43 | |
| + bkeys1 (~Thunderbi@134.22.115.162) | 16:49 | |
| - bkeys (QUIT: Ping timeout: 258 seconds) (~Thunderbi@199.226-24.cm.ptn.tftn.dynamic.friendlycity.net) | 16:52 | |
| * bkeys1 -> bkeys | 16:52 | |
| + klardotsh (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 17:04 | |
| - jacobk (QUIT: Ping timeout: 272 seconds) (~quassel@utdpat241106.utdallas.edu) | 17:09 | |
| - mjw (QUIT: Quit: Leaving) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 17:09 | |
| minute | it is possible that we power off a bit too early | 17:21 |
| minute | i am testing a311d reforms with a test sd card and after shutting down and booting the next one with the same sd card, it wants to fsck | 17:21 |
| + mjw (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 17:31 | |
| vkoskiv | Does linux control that, or does it send a shutdown to LPC and that turns the rails off? | 17:48 |
| vkoskiv | Could just slap some sleeps in the powerdown command to test, perhaps? I need to flash my lpc + kbd here soon | 17:48 |
| eery | It's a shell script attached to the systemd poweroff target, I think. If you don't have the script you have to manually power off with the circle menu | 17:53 |
| vkoskiv | Though I'm not even sure what a safe poweroff on an nvme means. Presumably some command has to be sent to it before cutting power | 17:53 |
| sigrid | it means telling nvme shutdown is going to happen | 17:56 |
| sigrid | then waiting until it signals "ok, done with my stuff" | 17:56 |
| sigrid | the kernel is supposed to do that | 17:56 |
| sigrid | if you just add a sleep it won't do anything | 17:57 |
| abortretryfail | So, the nvme block device driver in the kernel has to do it? | 17:57 |
| vkoskiv | Need instead to give the kernel a stern talking to for being mean to the NVMe | 17:57 |
| sigrid | abortretryfail: yes | 17:58 |
| sigrid | it already does that, but shutting down via lpc (I guess) happens before nvme drivers gets a chance to do that | 17:58 |
| vkoskiv | That's what I was thinking of, putting a sleep in the LPC code to delay the actual shutdown | 17:59 |
| vkoskiv | If it indeed is just a timing issue | 17:59 |
| vkoskiv | But a proper solution would be to not send the shutdown before NVMe says okay | 17:59 |
| abortretryfail | I guess a way to test it would be to comment out the LPC shutdown and manually shut it down using the keyboard a few seconds later | 18:00 |
| minute | there was some poweroff PR, right... but i didn't review it yet | 18:00 |
| minute | abortretryfail: yep | 18:00 |
| abortretryfail | If it still thinks it was an "unsafe", then maybe its nvmem_imc_ocotp's fault | 18:01 |
| sigrid | relevant change in 9front was very easy to make: http://git.9front.org/plan9front/plan9front/390c71f0c79b2b8b94997cd9ae03037272075f8b/commit.html | 18:02 |
| sigrid | it just switches all drives off from userspace, *then* triggers power rails via lpc | 18:02 |
| - S0rin (QUIT: Ping timeout: 258 seconds) (~S0rin@user/s0rin) | 18:20 | |
| + S0rin (~S0rin@user/s0rin) | 18:21 | |
| vkoskiv | I just recently learned two very useful commands | 18:37 |
| vkoskiv | `apt-cache pkgnames | less` | 18:37 |
| vkoskiv | Way better than `apt search --names-only <thing> | grep <thing>` I often did | 18:37 |
| vkoskiv | Just /search for patterns, cool. | 18:37 |
| vkoskiv | Sort of similar: `pkg-config --list-all | less` | 18:38 |
| vkoskiv | Again, no need to just try a few guesses at the name, then going to google to find the answer | 18:38 |
| minute | nice | 18:44 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 18:56 | |
| - Boostisbetter (QUIT: Ping timeout: 258 seconds) (4a410829d7@irc.cheogram.com) | 19:02 | |
| + jacobk (~quassel@129.110.242.224) | 19:06 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 19:16 | |
| josch | vkoskiv: you probably mean apt-cache show pkgnames? | 19:23 |
| vkoskiv | Nope, just `apt-cache pkgnames` | 19:24 |
| josch | minute: the fsck sdcard after reboot problem exists on imx as well | 19:24 |
| josch | vkoskiv: oh i had no idea, thanks! TIL :) | 19:25 |
| minute | josch: oh damn @ fsck | 19:26 |
| vkoskiv | I think it just dumps the hashtable or something, they aren't in alphabetical order. But |sort fixes it nicely. | 19:26 |
| minute | josch: we should fix that :# | 19:26 |
| josch | vkoskiv, abortretryfail: the lpc/nvme shutdown PR is this one: https://source.mnt.re/reform/reform-tools/-/merge_requests/46 | 19:27 |
| - Boostisbetter (QUIT: Ping timeout: 258 seconds) (4a410829d7@irc.cheogram.com) | 19:30 | |
| minute | josch: ah, does this patch send the poweroff from inside of the lpc module instead of from inside of a script? but how does the kernel know that this is the last module to power off? | 19:31 |
| minute | hmm > This module is overwriting the pm_power_off pointer that's been established by another module | 19:31 |
| minute | is that the way this is ensured? | 19:32 |
| josch | minute: i have no clue about that patch i only created the merge request for Michael Fincham who i think does not have an account | 19:32 |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 19:32 | |
| minute | hm. | 19:33 |
| vkoskiv | It seems like a lot of modules do that in their setup functions | 19:36 |
| vkoskiv | So... Maybe? | 19:36 |
| vkoskiv | Yeah, that's the power off callback I guess | 19:37 |
| vkoskiv | I mean, if some other driver has already set that, couldn't we stash the old value, call that in our callback, then run our code? | 19:41 |
| vkoskiv | Other drivers do seem to be doing a similar pattern, setting it to their own handler, then to NULL on remove | 19:43 |
| vkoskiv | Then some other drivers check it, and don't modify it if it's already set | 19:44 |
| vkoskiv | Heck, I'll just test this patch on my system. What's the worst that could happen? | 19:45 |
| minute | vkoskiv: but how do you know that you're the last one | 19:56 |
| minute | vkoskiv: i.e. that the nvme and sd are powered down | 19:56 |
| vkoskiv | I would make the assumption that pm_power_off only gets called when linux thinks it's safe to do so | 19:58 |
| vkoskiv | i.e. dunno :D | 19:58 |
| vkoskiv | Loaded reform2_lpc with those changes, shut down, still incremented unsafe_shutdowns | 19:58 |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@129.110.242.224) | 20:03 | |
| minute | vkoskiv: and you disabled the script first? | 20:03 |
| vkoskiv | I unloaded the kernel module, swapped in the new one, and enabled that. | 20:07 |
| minute | vkoskiv: i mean, did you disable the systemd script? | 20:08 |
| minute | vkoskiv: that turns off reform via usb hid | 20:08 |
| vkoskiv | I did not! | 20:09 |
| vkoskiv | Where's that at? | 20:10 |
| minute | https://source.mnt.re/reform/reform-tools/-/blob/main/systemd/reform-poweroff?ref_type=heads | 20:10 |
| vkoskiv | Success! Yeah, just commented out the contents of the poweroff script, put the patched kernel module back, shut down and no more unsafe_shutdown increment | 20:17 |
| vkoskiv | Before loading the patched ko, I verified that the system remained on after the kernel shut down | 20:17 |
| vkoskiv | Then loaded the ko, and now it seems to work better than before at least. | 20:17 |
| minute | vkoskiv: wow ok | 20:25 |
| + mark_ (~mjw@gnu.wildebeest.org) | 20:40 | |
| - mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 20:41 | |
| * mark_ -> mjw | 20:41 | |
| + mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 20:41 | |
| - SarioScream (QUIT: Quit: WeeChat 3.0) (sario@libera/staff/owl/sario) | 20:56 | |
| josch | oh i now see that Michael Fincham is ex--parrot! | 20:57 |
| josch | ex--parrot: vkoskiv successfully tested your MR :) | 20:57 |
| josch | vkoskiv: did you comment out all of /usr/lib/systemd/system-shutdown/reform-poweroff? | 20:59 |
| vkoskiv | Yes | 21:05 |
| + jacobk (~quassel@utdpat241106.utdallas.edu) | 21:05 | |
| josch | okay, then i'm just going to delete that file for good | 21:05 |
| josch | minute: the reform-lpc module patch by ex--parrot as well as the deletion of reform-poweroff are now part of https://source.mnt.re/reform/reform-tools/-/merge_requests/59 | 21:10 |
| josch | minute: would you like me to build you another system image so that you can easily test the reform-tools version proposed in that MR? | 21:10 |
| + cwebber` (~user@024-151-142-028.res.spectrum.com) | 21:13 | |
| minute | josch: that would be super, thanks | 21:14 |
| - cwebber (QUIT: Ping timeout: 240 seconds) (~user@user/cwebber) | 21:15 | |
| - doctorhoo (QUIT: Ping timeout: 255 seconds) (~doctorhoo@217-210-162-155-no600.tbcn.telia.com) | 21:20 | |
| + doctorhoo (~doctorhoo@2a00:801:779:4c0:29db:a57e:c818:b4ad) | 21:20 | |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2a00:801:779:4c0:29db:a57e:c818:b4ad) | 21:23 | |
| + doctorhoo (~doctorhoo@2001:2043:5e0f:a800:2eaa:8b14:1cf2:bf91) | 21:23 | |
| josch | minute: i assume that you didn't find any bugs when you tested on a311d recently? | 21:28 |
| josch | because then i'd put the fixes to those in there as well | 21:29 |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2001:2043:5e0f:a800:2eaa:8b14:1cf2:bf91) | 21:32 | |
| + doctorhoo (~doctorhoo@217-210-162-155-no600.tbcn.telia.com) | 21:33 | |
| minute | josch: yep, it behaved fine so far | 21:52 |
| - Boostisbetter (QUIT: Ping timeout: 248 seconds) (4a410829d7@irc.cheogram.com) | 21:53 | |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@utdpat241106.utdallas.edu) | 21:57 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 21:59 | |
| + jacobk (~quassel@129.110.242.224) | 22:03 | |
| - Boostisbetter (QUIT: Ping timeout: 264 seconds) (4a410829d7@irc.cheogram.com) | 22:36 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 22:49 | |
| + cwebber`` (~user@2600:6c64:7e3f:fdb0::6db) | 22:53 | |
| - cwebber`` (QUIT: Remote host closed the connection) (~user@2600:6c64:7e3f:fdb0::6db) | 22:54 | |
| + cwebber (~user@user/cwebber) | 22:54 | |
| - cwebber` (QUIT: Ping timeout: 255 seconds) (~user@024-151-142-028.res.spectrum.com) | 22:55 | |
| - jacobk (QUIT: Ping timeout: 240 seconds) (~quassel@129.110.242.224) | 23:16 | |
| + jacobk (~quassel@129.110.242.224) | 23:17 | |
| - jacobk (QUIT: Ping timeout: 272 seconds) (~quassel@129.110.242.224) | 23:27 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 23:33 | |
| josch | minute: nice! here are your images with reform-tools 1.34: https://source.mnt.re/reform/reform-system-image/-/jobs/2494/artifacts/browse | 23:37 |
| - chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:587:7a1a:f800:1ac0:4dff:fedb:a3f1) | 23:50 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!