| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 00:04 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 00:04 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@2603:8080:b200:7b02::b71) | 00:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 00:19 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 00:19 | |
| + kerntallett (~kerntalle@90.196.184.225) | 00:21 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 00:34 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 00:34 | |
| - murphnj (QUIT: Remote host closed the connection) (~murph@user/murphnj) | 00:40 | |
| sevan | just an observation: every time the keyboard is restarted, a new input node is added to /devices/platform/soc@0/38100000.usb/xhci-hcd.0.auto/usb1/1-1/1-1.3/1-1.3:1.0/0003:1209:6D00.0003/input/, should the behaviour be that it recognised the previous node has gone? (input0) rather than assigning a new node? (input2) | 00:41 |
|---|---|---|
| josch | sevan: that sounds similar to the devnum of the atmel device incrementing by 1 on every press of the reset button -- why does it increment? | 00:45 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 00:49 | |
| sevan | josch: that's what I'm wondering too, but I don't have an answer. Only reason I'm curious is because once you have restarted there is jitter | 00:49 |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 00:49 | |
| sevan | josch: can't type to fast, otherwise one keypress is multiplyed many times | 00:50 |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 00:51 | |
| sevan | iiiiii ppppppprrrrrrreeeeessssssseeeeeeddddddd eeeeeeaaaaaaaccccccchhhhh kkkkkeeeeeyyyyyy 3333xxxxx | 00:51 |
| josch | oh wow, i do not remember that issue with imx8mq | 00:52 |
| sevan | that was three times btw, not 3333 :) | 00:52 |
| sevan | back to it tomorrow. | 00:58 |
| sevan | gnite :) | 00:58 |
| josch | bye! | 00:59 |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.4.16) | 01:00 | |
| + Ar|stote|is (~linx@149.210.4.16) | 01:00 | |
| - mtm (QUIT: Ping timeout: 252 seconds) (~textual@47.202.75.129) | 01:03 | |
| noam | uhhhhhh how worried should I be about connecting a really, really, REALLLLY bad power supply, intentionally, to a reform classic? :P | 01:03 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 01:04 | |
| josch | noam: didn't you already connect a solar panel to your reform? :) | 01:04 |
| noam | josch: I'm not sure you understood my question | 01:04 |
| noam | REALLLY. REALLLLLLLY bad power supply xD | 01:04 |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 01:04 | |
| noam | The solar panel was _way_ higher quality DC | 01:04 |
| josch | hahahaha | 01:04 |
| noam | not kidding lmfao | 01:04 |
| sigrid | try it out and find out | 01:05 |
| josch | only one way to find out ;) | 01:05 |
| noam | I'm not worried about things breaking, the charging IC is clearly really good | 01:05 |
| noam | I'm more worried about the effect on the cells of alternating between charging and discharging at, uh, ~6Hz if I had to guess | 01:05 |
| + mtm (~textual@47.202.75.129) | 01:05 | |
| noam | (did I mention it's a _really bad_ supply? xD) | 01:05 |
| noam | ...worst case it gives me an excuse to grab some sodium-ion cells xD | 01:07 |
| + murphnj (~murph@user/murphnj) | 01:10 | |
| noam | I wish there was an easy way to see incoming voltage, not just battery voltage :/ | 01:16 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 01:19 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 01:19 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 01:29 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 01:34 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 01:34 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 01:49 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 01:49 | |
| - kerntallett (QUIT: Remote host closed the connection) (~kerntalle@90.196.184.225) | 01:53 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 02:04 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 02:04 | |
| - Gooberpatrol_66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66) | 02:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 02:19 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 02:20 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 02:34 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 02:35 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 02:49 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 02:50 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 03:00 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 03:01 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 03:04 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 03:05 | |
| - MyNetAz (QUIT: Remote host closed the connection) (~MyNetAz@user/MyNetAz) | 03:19 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 03:19 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 03:20 | |
| + MyNetAz (~MyNetAz@user/MyNetAz) | 03:30 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 03:34 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 03:35 | |
| - Gooberpatrol66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66) | 03:39 | |
| - paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@107.159.243.8) | 03:41 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 03:50 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 03:50 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 04:05 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 04:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 04:20 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 04:20 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 04:35 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 04:35 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 04:50 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 04:50 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 05:05 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 05:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 05:20 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 05:20 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 05:32 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 05:35 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 05:35 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 05:50 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 05:50 | |
| - aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.193.71) | 06:00 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 06:05 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 06:05 | |
| + aloo_shu (~aloo_shu@90.166.193.71) | 06:12 | |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 06:17 | |
| + jacobk_ (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 06:17 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 06:20 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 06:20 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 06:35 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 06:35 | |
| - glu (QUIT: Read error: Connection reset by peer) (~glu@user/glu) | 06:50 | |
| + glu (~glu@user/glu) | 06:50 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 06:50 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 06:50 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 07:05 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 07:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 07:20 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 07:21 | |
| + bkeys1 (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:25 | |
| - bkeys (QUIT: Ping timeout: 260 seconds) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 07:27 | |
| * bkeys1 -> bkeys | 07:27 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:35 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:36 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:50 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:51 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:05 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:06 | |
| - jacobk_ (QUIT: *.net *.split) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 08:19 | |
| - murphnj (QUIT: *.net *.split) (~murph@user/murphnj) | 08:19 | |
| - BoostisBetter (QUIT: *.net *.split) (4a410829d7@irc.cheogram.com) | 08:19 | |
| - SavagePeanut (QUIT: *.net *.split) (59eaa45ac7@irc.cheogram.com) | 08:19 | |
| - mesaoptimizer (QUIT: *.net *.split) (~mesaoptim@user/PapuaHardyNet) | 08:19 | |
| - laumann (QUIT: *.net *.split) (~quassel@user/laumann) | 08:19 | |
| - TadeusTaD (QUIT: *.net *.split) (tadeustad@user/TadeusTaD) | 08:19 | |
| - kensanata (QUIT: *.net *.split) (~alex@user/kensanata) | 08:19 | |
| - amk (QUIT: *.net *.split) (~amk@user/amk) | 08:19 | |
| - Kooda (QUIT: *.net *.split) (~kooda@natsu.upyum.com) | 08:19 | |
| - eschaton (QUIT: *.net *.split) (eschaton@2600:3c01::f03c:91ff:fefd:5d92) | 08:19 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:20 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:21 | |
| + jacobk_ (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 08:24 | |
| + murphnj (~murph@user/murphnj) | 08:24 | |
| + mesaoptimizer (~mesaoptim@user/PapuaHardyNet) | 08:24 | |
| + laumann (~quassel@user/laumann) | 08:24 | |
| + TadeusTaD (tadeustad@user/TadeusTaD) | 08:24 | |
| + kensanata (~alex@user/kensanata) | 08:24 | |
| + Kooda (~kooda@natsu.upyum.com) | 08:24 | |
| + eschaton (eschaton@2600:3c01::f03c:91ff:fefd:5d92) | 08:24 | |
| - MyNetAz (QUIT: Write error: Connection reset by peer) (~MyNetAz@user/MyNetAz) | 08:24 | |
| + amk (~amk@user/amk) | 08:27 | |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 08:29 | |
| + MyNetAz (~MyNetAz@user/MyNetAz) | 08:35 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:35 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:36 | |
| - colinsane (QUIT: Ping timeout: 244 seconds) (~colinunin@97-126-24-77.tukw.qwest.net) | 08:42 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:51 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:51 | |
| + colinsane (~colinunin@97-113-142-203.tukw.qwest.net) | 08:59 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:06 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:06 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:21 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:21 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:36 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:36 | |
| + BoostisBetter (4a410829d7@irc.cheogram.com) | 09:45 | |
| BoostisBetter | How can I reload the WiFi driver/service on the pocket? systemctl reload what? | 09:46 |
| ch | probably rmmod + modprobe the driver | 09:48 |
| ch | name depends on the "card" you're using | 09:48 |
| BoostisBetter | ch: default for the pocket | 09:50 |
| BoostisBetter | Sorry don't remember what it is. | 09:50 |
| ch | probably qcacld2 then | 09:51 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:51 | |
| BoostisBetter | ch: that sounds right! | 09:51 |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:51 | |
| BoostisBetter | So sudo rmmod + modprobe qcacld2 | 09:51 |
| BoostisBetter | ch: actually there is no card just the built in on the imx8mplus | 09:52 |
| BoostisBetter | So you are totally right. | 09:52 |
| ch | these are two commands, each takes the module name | 09:52 |
| BoostisBetter | Then just use systemctl to reload them? | 09:52 |
| ch | yeah thats why i used quotes | 09:52 |
| ch | no systemctl, just normal commands (as root) | 09:53 |
| BoostisBetter | ch: sorry not truing to be dense, but what exactly do I write to reload the WiFi driver? | 09:53 |
| BoostisBetter | ch: sorry not trying to be dense, but what exactly do I write to reload the WiFi driver? | 09:53 |
| josch | BoostisBetter: you write first: | 09:54 |
| josch | sudo rmmod qcacld2 | 09:54 |
| BoostisBetter | sudo rmmod qcacld2 | 09:54 |
| josch | and then, after that command is done: | 09:54 |
| josch | sudo modprobe qcacld2 | 09:54 |
| BoostisBetter | Ahh OK gotcha! | 09:54 |
| BoostisBetter | josch: thanks and also CH for the help! | 09:54 |
| josch | BoostisBetter: i'm reading something about configuration defaults in the backlog -- did you manage to find what you were looking for? | 09:55 |
| ch | sorry i'm on my way to somewhere and typing on a phone :) | 09:56 |
| BoostisBetter | josch: No, not really. What I'm really looking for is the default way that the pocket reform uses the network manager in Sway, but through Waybar. | 09:58 |
| BoostisBetter | Currently my network applet in the way bar is using the terminal based solution that was for the original reform, but that's not what shipped with the pocket. | 09:59 |
| josch | BoostisBetter: this is how: https://source.mnt.re/reform/reform-system-image/-/blob/main/etc/skel/.config/sway/config?ref_type=heads#L274 | 09:59 |
| - jacobk_ (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| BoostisBetter | josch: thanks! | 10:04 |
| BoostisBetter | So that appears to be the problem. The NM Applet doesn't start. And when I tried using the Modprobe, it said that the Wi-Fi driver wasn't present for that kernel. | 10:05 |
| BoostisBetter | But when I restart and log in to Sway, it'll automatically connect to a Wi-Fi. So it only seems to be a problem when I am switching between Wi-Fi connections and it doesn't automatically grab it. | 10:06 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:06 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:06 | |
| josch | BoostisBetter: nm-applet is only one of the many front-ends for networkmanager | 10:10 |
| BoostisBetter | So I think this is just an issue of using the 6.11.10 kernel | 10:10 |
| josch | BoostisBetter: whether or not nm-applet works is independent of whether networkmanager connects to the networks you have configured | 10:10 |
| BoostisBetter | I mean that qcacld2 is not available to the 6.11.10 kernel | 10:11 |
| BoostisBetter | and as such the applet fails to load | 10:11 |
| josch | if you nm-applet doesn't start, maybe try starting it from a terminal and see what it prints | 10:11 |
| josch | BoostisBetter: so your modprobe fails? | 10:11 |
| BoostisBetter | it doeesn't seem to be installed | 10:11 |
| BoostisBetter | yes | 10:11 |
| josch | BoostisBetter: do you have the reform-qcacld2 package installed? | 10:12 |
| BoostisBetter | i don't seem to have nm-applet installed either | 10:12 |
| josch | BoostisBetter: running reform-check should tell you these things | 10:12 |
| minute | BoostisBetter: how did you end up in this situation with the non standard configs? | 10:14 |
| BoostisBetter | minute: trying to use debian stable with mnt repos still enabled | 10:15 |
| BoostisBetter | josch has been helping me a lot and I am almost back to good | 10:16 |
| minute | ah ok | 10:16 |
| BoostisBetter | josch: reform-check told me to install firmware-mediatek and firmware-misc but neither packages are available | 10:16 |
| BoostisBetter | josch: it also says that this is a missing boot command setting, console=ttymxc1, but I forget how to add it to the boot parameters | 10:18 |
| josch | BoostisBetter: about missing packages, reform-check should've told you that you need non-free-firmware enabled. Does it? | 10:19 |
| BoostisBetter | no it does not | 10:20 |
| BoostisBetter | which lines in sources need that added? | 10:21 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:21 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:21 | |
| josch | BoostisBetter: wait, if it does not, can we first try to fix this so that it doesn't happen again in the future? | 10:22 |
| BoostisBetter | josch: you bet | 10:22 |
| BoostisBetter | also it tells me that uboot is out of date and to update, but reform-flash-uboot fails. Most likely because of the missing firmware packages | 10:23 |
| josch | BoostisBetter: what does this print for you: | 10:23 |
| josch | apt-get indextargets 'Created-By: Packages' 'Origin: Debian' 'Repo-URI: http://deb.debian.org/debian/' --format '$(COMPONENT)' | sort -u | 10:23 |
| josch | BoostisBetter: no, reform-flash-uboot has nothing to do with firmware. If it fails, you need to look at the error message. | 10:23 |
| BoostisBetter | epo-URI: http://deb.debian.org/debian/' --format '$(COMPONENT)' | sort -u | 10:23 |
| BoostisBetter | main | 10:23 |
| josch | ooooh i see the bug | 10:24 |
| josch | one sec... | 10:24 |
| BoostisBetter | josch: regarding uboot failing here is the error message: No device unto which to flash uboot provided. Exiting. | 10:24 |
| josch | yes | 10:25 |
| josch | this means you need to provide the device onto which to flash uboot | 10:25 |
| josch | the --help output should tell you how | 10:25 |
| BoostisBetter | thought the script would take care of that | 10:25 |
| BoostisBetter | josch: got it to work just told it emmc | 10:26 |
| josch | BoostisBetter: which script takes care of that? | 10:27 |
| BoostisBetter | nothing, just a RTM issue on my end | 10:28 |
| BoostisBetter | reform-check could metion though that the device (emmc, sd card) has to be specified though | 10:28 |
| josch | it says over here: | 10:29 |
| josch | echo "reform-flash-uboot emmc" >&2 | 10:29 |
| josch | did it not print that for you? | 10:29 |
| BoostisBetter | josch: that did, but the reform-check just said "reform-flash-uboot" | 10:30 |
| josch | BoostisBetter: can you paste me the output where it said that via xmpp or a pastebin? | 10:31 |
| josch | i do not see how that's possible by looking at the source code of reform-check | 10:31 |
| BoostisBetter | josch: just sent it to you | 10:31 |
| BoostisBetter | josch: it is possible that my reform-check is old | 10:32 |
| josch | BoostisBetter: if it is, it should say so at the top where it prints your reform-tools version | 10:32 |
| BoostisBetter | josch: so getting the firmware packages to be installed? What lines in sources do I need to update? | 10:33 |
| josch | if your hardware works correctly, then you do not need the firmware packages | 10:33 |
| josch | you said your wifi connects, so firmware for that is there | 10:34 |
| BoostisBetter | josch: good point. As you mentioned to me it was because the flash.bin was out of date | 10:34 |
| BoostisBetter | josch: why would reform-check not see it then? | 10:34 |
| josch | but it did. you just sent me the output that it did | 10:34 |
| BoostisBetter | josch: I'm talking about the firmware packages. Why does it tell me that the firmware packages are missing if you're saying that they're installed? | 10:35 |
| josch | they are not installed | 10:35 |
| josch | but if your wifi is working, you do not seem to need them | 10:36 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:36 | |
| BoostisBetter | josch: I would prefer being standard with what is supposed to be there though. | 10:36 |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:36 | |
| josch | okay, in that case, you can edit your /etc/apt/sources.list and replace mentions of "main" by "main non-free-firmware" | 10:37 |
| - jn (QUIT: Ping timeout: 245 seconds) (~quassel@user/jn/x-3390946) | 10:37 | |
| josch | as your system is trixie, you should for example have one line that says: | 10:37 |
| + jn (~quassel@2001-4dd4-69f1-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de) | 10:37 | |
| - jn (QUIT: Changing host) (~quassel@2001-4dd4-69f1-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de) | 10:37 | |
| + jn (~quassel@user/jn/x-3390946) | 10:37 | |
| josch | deb http://deb.debian.org/debian trixie main non-free-firmware | 10:38 |
| BoostisBetter | josch: thank you it is done and the packages are installed. | 10:48 |
| josch | nice | 10:49 |
| - Asmadeus (QUIT: Ping timeout: 245 seconds) (~asmadeus@user/meow/Asmadeus) | 10:51 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:51 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:51 | |
| BoostisBetter | josch: | 10:56 |
| BoostisBetter | josch: One thing lingering is that the not correct icons are being used for the Bluetooth applet, network applet, and the audio applet. | 10:56 |
| BoostisBetter | Sorry about spamming your name there. | 10:56 |
| BoostisBetter | josch: But having just said that, I think I know what happened. I think I changed from Papyrus dark to just plain Papyrus and that's why the icons change. So I'll go back to setting Papyrus to dark. | 10:57 |
| BoostisBetter | They look way way WAY better | 10:57 |
| josch | BoostisBetter: you change that with gsettings set org.gnome.desktop.interface icon-theme 'Papirus-Dark' | 10:58 |
| BoostisBetter | josch: vielen Dank schon wieder! | 10:59 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:06 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:06 | |
| amospalla | BoostisBetter: are you using debian stable? I am on debian stable and I have waybar config files under /etc/skel/.config/waybar | 11:12 |
| josch | The files in /etc/skel/ are from the system image you used to install the system. | 11:13 |
| josch | They do not get changed as you upgrade reform-tools to newer versions. | 11:14 |
| josch | If you want to see the latest contents of /etc/skel/ as is distributed in the system images, you have to look into the reform-system-image git | 11:14 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:21 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:21 | |
| + Asmadeus (~asmadeus@user/meow/Asmadeus) | 11:23 | |
| amospalla | Yes, I looked which packages do these files belong to, but no installed package owned them. | 11:25 |
| josch | they used to belong to reform-tools | 11:27 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:36 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:36 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:51 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:51 | |
| + mjw (~mjw@gnu.wildebeest.org) | 11:52 | |
| - iank (QUIT: Ping timeout: 244 seconds) (~iank@fsf/staff/iank) | 11:55 | |
| - chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 11:58 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:06 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:06 | |
| + iank (~iank@fsf/staff/iank) | 12:17 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:21 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:22 | |
| + paperManu (~paperManu@107.159.243.8) | 12:30 | |
| BoostisBetter | and what if your /etc/skel/ is empty? | 12:36 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:36 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:37 | |
| amospalla | BoostisBetter: these files come from https://source.mnt.re/reform/reform-system-image/-/tree/main/etc/skel/.config/waybar | 12:38 |
| BoostisBetter | yes but that is for the Reform and not exactly identical to the pocket? right? | 12:39 |
| BoostisBetter | my waybar is now fully restored as well | 12:40 |
| BoostisBetter | so I'm good on that front now | 12:40 |
| josch | BoostisBetter: the root partition of the system image is bit-by-bit identical for all platforms | 12:40 |
| josch | this means that the contents of /etc/skel are bit-by-bit identical independent on the module | 12:41 |
| BoostisBetter | josch: Does this mean that my etc/skel/ should actually be populated? | 12:44 |
| BoostisBetter | I'm having a weird issue in using amospalla's low power suspend script in that the root directory becomes inaccessible and I have to power cycle (reboot now) in order to get it to come back. When I do power cycle it has to repair some of the VG partition. | 12:46 |
| BoostisBetter | amospalla: have you had anything like this happen on your pocket? Are you using an NVME with yours? | 12:46 |
| josch | BoostisBetter: do you plan to add other users to your installation? | 12:46 |
| BoostisBetter | Nope | 12:47 |
| josch | then you could even rm -r /etc/skel | 12:47 |
| BoostisBetter | Will do | 12:47 |
| josch | BoostisBetter: STOP! | 12:47 |
| josch | sorry, there actually is some content in it that comes from the package bash | 12:47 |
| BoostisBetter | That also answers the purpose for that folder. Thanks. Don't worry, I'm not using the pocket right now. | 12:47 |
| josch | you can delete everything in it except for the following files: | 12:48 |
| BoostisBetter | josch: Not on mine, the folder is empty. | 12:48 |
| josch | BoostisBetter: did you show hidden files? | 12:48 |
| BoostisBetter | I used LS in a terminal | 12:48 |
| josch | use ls -a | 12:48 |
| BoostisBetter | OK will do when I'm back on the pocket. | 12:49 |
| josch | BoostisBetter: this is what you can delete: | 12:49 |
| josch | sudo rm -r /etc/skel/.config /etc/skel/.local | 12:49 |
| josch | those directory trees were put there by the system image scripts | 12:50 |
| josch | they are only relevant when creating new users | 12:50 |
| josch | if they confuse you, you can delete them | 12:50 |
| josch | if you ever want to create a new user, it is probably better anyways to obtain new defaults from the git repo | 12:50 |
| BoostisBetter | You know, one happy thing about the pocket not being able to suspend is that the SOC actually stays warm. How this is useful, at least in my particular case, is in the winter, and where I work, I can't bring it in with me to work, so I leave it in the car. But because it's on, the SOC doesn't really go under 45, 44C. However, the rest of the case gets really cold. The keyboard, batteries, the LPC | 12:51 |
| BoostisBetter | , etc. And what I'm wondering is the case or the pseudo bag case that came with the pocket. If I were to put the pocket in there and not close it, would this be a good way to allow some of that heat from the SOC to keep other components a little bit more warm? | 12:51 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:51 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:52 | |
| amospalla | BoostisBetter: what do you mean with "root directory becomes inaccesible"? | 12:53 |
| amospalla | maybe that you do a hard reset and you need a file system repair after that? | 12:54 |
| BoostisBetter | amospalla: I mean the root folder, which to me just points to a connection issue with the NVMe drive somehow it becomes de-synced or disconnects. It's not a full disconnect because I can still access folders and directories and stuff on the drive, but the ability for applications to reach back and hit certain things seems to be removed. | 12:55 |
| BoostisBetter | Maybe it has to do with encryption. | 12:55 |
| amospalla | I see. | 12:55 |
| BoostisBetter | How would I do a file system repair? | 12:55 |
| BoostisBetter | When rebooting and after unlocking the encrypted drive, it does go through a thing where it's repairing the VG partition. | 12:55 |
| BoostisBetter | I think the terminology it used is orphaned something. | 12:56 |
| amospalla | The moment you can not access your root path something bad has already happened. | 12:56 |
| amospalla | what modules do you have under /etc/psuspend.conf? | 12:57 |
| BoostisBetter | Let me go look. One moment. | 12:59 |
| BoostisBetter | amospalla: the script does freeeze the root | 13:02 |
| BoostisBetter | is it possible that unfreezing it just is hanging? | 13:02 |
| + gustav28 (~gustav@c-78-82-54-227.bbcust.telenor.se) | 13:02 | |
| - mtm (QUIT: Ping timeout: 248 seconds) (~textual@47.202.75.129) | 13:04 | |
| BoostisBetter | amospallo: modules enabled are: | 13:04 |
| BoostisBetter | "network" | 13:04 |
| BoostisBetter | "systemd" | 13:04 |
| BoostisBetter | "session_freeze" # Freeze user sessions, except for root. | 13:04 |
| BoostisBetter | "session_freeze_root" # Freeze root sessions. | 13:04 |
| BoostisBetter | "display" | 13:04 |
| BoostisBetter | "cpu" | 13:04 |
| + mtm (~textual@47.202.75.129) | 13:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:06 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:07 | |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 13:08 | |
| * Guest8058 -> mjw | 13:10 | |
| amospalla | does 'grep interconnect /usr/local/bin/psuspend' return anything? | 13:11 |
| BoostisBetter | amospalla: It could be because when I tried updating the LPC, the script fails or it doesn't necessarily complete. And so it's possible that the LPC was in a weird state even though I did a keyboard reset through the LPC. | 13:11 |
| BoostisBetter | bkeys: Are you aware that you're connecting and disconnecting every couple of minutes? | 13:12 |
| amospalla | BoostisBetter: I don't see the relation between your nvme and the lpc. Does 'grep interconnect /usr/local/bin/psuspend' return anything? | 13:13 |
| BoostisBetter | amospalla: Let me check. | 13:13 |
| amospalla | I just removed that module from psuspend. I didn't know what that was really doing. Besides that, I don't see how this script could mess with a nvme. | 13:17 |
| amospalla | But anyway, you were not using that. | 13:19 |
| BoostisBetter | grep interconnect doesn't return anything | 13:20 |
| BoostisBetter | so I should remove that module from my script as well? | 13:21 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:21 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:22 | |
| BoostisBetter | amospalla: IE: just freeze the user session and not the rootZ? | 13:23 |
| BoostisBetter | amospalla: IE: just freeze the user session and not the root? | 13:23 |
| - GNUmoon (QUIT: Ping timeout: 264 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon) | 13:26 | |
| amospalla | BoostisBetter: no need to do anything then, maybe update it as per readme instructions if you want to have the latest file, but I don't think there is anything new for you. The user session module freezes interactive user sessions, so any background root daemons keep running. | 13:28 |
| BoostisBetter | amospalla: I'll check it out on github and see if I should update. Thanks! | 13:29 |
| amospalla | Root sessions get frozen too, but that means a console or ssh session, not services started from systemd. | 13:29 |
| amospalla | That is why there exists the systemd module, to stop daemons. | 13:30 |
| BoostisBetter | Just seems like an unlikely coincidence that it would be complaining about the root folder not being accessible when we're suspending root sessions, even though the relationship between the two is not as strong as would be implied. | 13:30 |
| BoostisBetter | I suspect it has to do more with the Buggy LPC or something like that. | 13:30 |
| BoostisBetter | Perhaps the LPC is not reporting the control F1 quickly enough or maybe it's spamming it all of a sudden all at once and this is causing the suspend service to run on top of each other and that's where the glitch is happening. | 13:31 |
| BoostisBetter | minute: josch: this thread goes into the glitchy lpc update issue: https://community.mnt.re/t/error-updating-system-controller-firmware/2797 | 13:33 |
| BoostisBetter | Maybe something to get a head of. | 13:33 |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 13:34 | |
| amospalla | BoostisBetter: psuspend should give you visual feedback when starting/stopping. | 13:35 |
| BoostisBetter | amospalla: Yes, but that visual feedback is dependent on the LPC and its control of the keyboard LEDs. I think the quick light up of the green LEDs is a really good idea. But what I've noticed whenever the keyboard stutters like that, and it might be sending multiple control F1 commands, is that the LED lighting up is delayed. | 13:36 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:36 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:37 | |
| BoostisBetter | So it's possible that the script doesn't have any issues at all and it's really just a keyboard stuttering that's causing the script or the service to be run multiple times in rapid succession. | 13:37 |
| amospalla | Systemd logs should give you hints about what is happening. | 13:38 |
| josch | BoostisBetter: i see that there is a segmentation fault, probably with picotool from the looks of the error message | 13:38 |
| josch | BoostisBetter: you'd have to run this under gdb to find out what causes this | 13:38 |
| josch | and i cannot do this because i don't have a pocket | 13:39 |
| josch | i also heard that soon fwupd will be ready? | 13:39 |
| BoostisBetter | josch: no, and I agree that doing this would be helpful. I have as of now not yet done any Linux based development work. So while I can figure it out if fwupd is almost ready that sounds like a win. Just a bummer because I was updating to get better charger compatibility. | 13:40 |
| BoostisBetter | And now I'll need to wait with a glitchy lpc. | 13:41 |
| + glu_ (~glu@user/glu) | 13:45 | |
| - glu (QUIT: Ping timeout: 252 seconds) (~glu@user/glu) | 13:46 | |
| * glu_ -> glu | 13:46 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:52 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:52 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:07 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:07 | |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 14:16 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:22 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:22 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:37 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:37 | |
| - natalie (QUIT: Ping timeout: 272 seconds) (~natalie@user/natalie) | 14:41 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:52 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:52 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 14:53 | |
| - MyNetAz (QUIT: Ping timeout: 252 seconds) (~MyNetAz@user/MyNetAz) | 14:54 | |
| - mark_ (QUIT: Ping timeout: 244 seconds) (~mjw@gnu.wildebeest.org) | 15:14 | |
| + MyNetAz (~MyNetAz@user/MyNetAz) | 15:18 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 15:34 | |
| minute | typing this from my MNT Reform Next | 16:04 |
| - mark_ (QUIT: Ping timeout: 244 seconds) (~mjw@gnu.wildebeest.org) | 16:04 | |
| Sario | minute: nice! | 16:05 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:05 | |
| minute | i need to go out into the cold and to DHL to fetch trackpad keycaps :S | 16:05 |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:20 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:20 | |
| - MyNetAz (QUIT: Ping timeout: 252 seconds) (~MyNetAz@user/MyNetAz) | 16:33 | |
| minute | ok nice, trackpad buttons fit well | 16:50 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:51 | |
| - josch (QUIT: Ping timeout: 252 seconds) (~josch@mister-muffin.de) | 16:51 | |
| + josch (~josch@mister-muffin.de) | 16:51 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:51 | |
| midfavila | wowowowow the next is working? | 17:06 |
| midfavila | very cool | 17:06 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:06 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:06 | |
| minute | midfavila: yeah it's really nice actually :D | 17:08 |
| minute | i'm suddenly so tired lol | 17:09 |
| minute | still need to bring up wifi+bt board that'll come in the next days | 17:09 |
| - aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.193.71) | 17:10 | |
| minute | and next week we have to shoot a campaign video :0 | 17:14 |
| + MyNetAz (~MyNetAz@user/MyNetAz) | 17:19 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:21 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:21 | |
| gsora | oooo | 17:23 |
| gsora | congrats!!! | 17:23 |
| midfavila | nice :3 | 17:29 |
| midfavila | please advertise directly into my brain | 17:29 |
| midfavila | i can't wait to see what you'll come up with | 17:29 |
| midfavila | personally i prefer the classic chassis but i think the slimmer design of the next will steal some of the thunder of the framework crowd, insofar as there's demographic overlap | 17:30 |
| minute | hope so :3 | 17:33 |
| midfavila | >inb4 MNT absolutely DESTROYS all other computer manufacturers in the next year | 17:34 |
| midfavila | dell? gone. HP? never heard of 'em. lenovo? irrelevant | 17:34 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:36 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:36 | |
| gsora | friends told me if it wasn't for the design the would've got a reform already | 17:57 |
| gsora | i'm a fan of the thicc design, but i can see the appeal for a slimmer laptop | 17:57 |
| [tj] | my powerbook is too large to actually put in a bag | 18:00 |
| [tj] | but I don't think the reform is a problem there | 18:00 |
| BoostisBetter | minute: nice work on the Next! | 18:01 |
| [tj] | minute: will there be a next prototype with you at congress? | 18:01 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:02 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:03 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:28 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:29 | |
| midfavila | >not carrying your reform around in a bag the size of your torso | 18:42 |
| midfavila | smdh | 18:42 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 18:45 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 18:56 | |
| robin | trackpoint on reform when (luckily for me, my first reform will be a pocket with trackball, once i make sure it will actually fit into my purse) | 19:09 |
| * mjw -> Guest275 | 19:11 | |
| - Guest275 (QUIT: Killed (tantalum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 19:11 | |
| * mark_ -> mjw | 19:11 | |
| + Guest275 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 19:11 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:19 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:19 | |
| + SavagePeanut (59eaa45ac7@irc.cheogram.com) | 19:21 | |
| BoostisBetter | the mini trackball on the Pocket Reform is excellent. Really one of the best mousing devices I have ever used in what I would consider the UMPC category. | 19:26 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:34 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:35 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:49 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:50 | |
| minute | [tj]: yes @ congress | 19:59 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:04 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:05 | |
| BoostisBetter | minute: I have had some success updating the sysctl firmware | 20:17 |
| BoostisBetter | but I am curious if the most recent firmware is dated 30/07 internally instead of 26 Aug? | 20:17 |
| BoostisBetter | minute: josch: there appears to be an error in the bus and address values that causes the script to fail. Also at the end a picotool reboot -f is issued, even though the previous load command already does that. | 20:18 |
| minute | yeah that script needs to be replaced soon by fwupd | 20:19 |
| minute | not sure how we get fwupd out the door | 20:19 |
| minute | currently bogged down in reform next campaign stuff :3 | 20:19 |
| minute | (going well though) | 20:19 |
| minute | and will also use the same fwupd stuff anyway | 20:19 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:19 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:20 | |
| BoostisBetter | minute: I was wrong, the only issue with the script is the final picotool reboot command | 20:21 |
| BoostisBetter | not necessary | 20:21 |
| BoostisBetter | minute: is rebooting the reform really necessary when done flashing the controller? | 20:21 |
| minute | BoostisBetter: do you mean the pocket reform? | 20:26 |
| minute | BoostisBetter: since the newest firmwares it doesn't reboot anymore when upgrading. | 20:26 |
| BoostisBetter | minute: actually I think it is because of possible root sytem problems | 20:26 |
| BoostisBetter | minute: is the latest sysctl firmware internally dated 30/07-or is it supposed to say 26/08? | 20:27 |
| BoostisBetter | minute: it appears to work but the date on the firmware from the system status screen shows 30 07 | 20:27 |
| - Gooberpatrol66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66) | 20:31 | |
| + reform16256 (~pjjw@syn-074-065-211-150.res.spectrum.com) | 20:33 | |
| BoostisBetter | > BoostisBetter: since the newest firmwares it doesn't reboot anymore when upgrading. | 20:34 |
| BoostisBetter | That is curious because the tool reports that it booted it back in appliance mode | 20:34 |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 20:36 | |
| reform16256 | yay, pocket reform finally arrived! very cute. | 20:38 |
| * reform16256 -> pjjw | 20:38 | |
| - pjjw (QUIT: Remote host closed the connection) (~pjjw@syn-074-065-211-150.res.spectrum.com) | 20:45 | |
| + erle (~erle@user/erle) | 20:58 | |
| BoostisBetter | amospalla: also disregard everything I have said about psuspend causing a problem with the root fs. I believe this was a hold over from updating the sysctl and not rebooting the system. | 21:03 |
| BoostisBetter | congrats reform16256! | 21:04 |
| * gsora -> gianguido | 21:35 | |
| * gianguido -> gsora | 21:35 | |
| + aloo_shu (~aloo_shu@90.166.193.71) | 21:59 | |
| - glu (QUIT: Ping timeout: 272 seconds) (~glu@user/glu) | 21:59 | |
| + glu (~glu@user/glu) | 22:00 | |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-54-227.bbcust.telenor.se) | 22:15 | |
| amospalla | BoostisBetter: ok, good to know it updated. | 22:27 |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 22:32 | |
| - bkeys (QUIT: Remote host closed the connection) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 22:57 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!