2025-10-17.log

- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)00:05
+ kensanata (~alex@user/kensanata)00:07
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)00:37
* mesaoptimizer0 -> mesaoptimizer00:38
+ paperManu_ (~paperManu@198.58.139.163)00:38
+ kensanata (~alex@user/kensanata)00:39
- kensanata (QUIT: Ping timeout: 240 seconds) (~alex@user/kensanata)01:05
+ kensanata (~alex@user/kensanata)01:11
- kensanata (QUIT: Ping timeout: 260 seconds) (~alex@user/kensanata)01:16
+ kensanata (~alex@user/kensanata)01:20
bremnerjosch: Linux anthia 6.18.0-rc1+ #19 SMP Thu Oct 16 11:32:04 ADT 2025 aarch64 GNU/Linux ;)01:27
joschhah :)01:32
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)01:36
+ kensanata (~alex@user/kensanata)01:37
+ reform1219 (~ian@2601:985:d80:6560::c714)01:46
- reform1219 (QUIT: Client Quit) (~ian@2601:985:d80:6560::c714)01:46
bremnerhmm. looks like PCI resume is is still a problem: https://paste.debian.net/1401262/01:48
bremnerthat's despite all buses being unloaded before the hibernate according to lspci01:49
bremnerminute: just checked, and that commit is indeed in the rockchip-devel branch that I am running (under a different hash, because rebase)01:59
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)02:06
+ kensanata (~alex@user/kensanata)02:07
- paperManu (QUIT: Ping timeout: 248 seconds) (~paperManu@198.58.139.163)02:37
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)02:48
- mjw (QUIT: Ping timeout: 260 seconds) (~mjw@gnu.wildebeest.org)03:17
- wickedshell (QUIT: Ping timeout: 244 seconds) (~wickedshe@c-174-56-77-83.hsd1.nm.comcast.net)03:47
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.16.73)04:30
- svp (QUIT: Ping timeout: 260 seconds) (~svp@host-79-7-240-189.business.telecomitalia.it)04:35
- paperManu_ (QUIT: Ping timeout: 256 seconds) (~paperManu@198.58.139.163)04:36
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)04:48
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)04:49
+ svp (~svp@2002:4f07:f0bd:0:69b1:b463:d245:e861)04:53
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.6.130)05:59
+ Ar|stote|is (~linx@149.210.6.130)06:08
- bkeys (QUIT: Ping timeout: 265 seconds) (~Thunderbi@98.19.131.193)06:33
+ bkeys (~Thunderbi@98.19.131.193)06:39
+ rwa_ (~rene@2001:9e8:339e:8500:b483:a0bf:15bc:f89)07:13
+ aloo_shu (~aloo_shu@85.51.16.22)07:14
rwa_oh, the USB-C port on the Classic MB 3.0 is for charging/power only and has no usb signaling?07:14
joschrwa_: yes, the only use besides charging is that you can use it to observe the serial output of your SoM07:22
rwa_ok, i knew that there is no DP AltMode, but i somehow expected it to allow connection of usb devices via kvm hub07:25
rwa_not a big deal, but i need to adjust my setup a bit07:25
joschrwa_: i have no clue about all this modern usb stuff but would that not work via the usb-a plugs?07:26
rwa_sure, but i need additional cables for that07:27
rwa_a have a monitor with built-in kvm switch07:27
rwa_USB-A host connection is wired to my desktop rig, USB-C connection which could do PD and USB signaling is available for Reform07:28
rwa_so i need to switch mouse/keyboard or the USB-A host cable 07:29
joschoooh i see07:29
rwa_tbh this would be a real "problem" if Desktop Reform becomes a thing... :/07:32
joschi wonder if the reform next can do it07:32
rwa_yep, it is cappable of USB signaling on the USB-C port07:38
rwa_and this somehow lead me to the assumption that MB3.0 for classic would be cappable as wel07:39
rwa_+l07:39
joschone more reason to 3d print some scaffolding to put the reform next motherboard into the classic :)07:41
rwa_:)07:43
- rwa_ (QUIT: Quit: Leaving) (~rene@2001:9e8:339e:8500:b483:a0bf:15bc:f89)08:43
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)09:45
+ kensanata (~alex@user/kensanata)09:49
+ andreas-e (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890e.rev.sfr.net)11:23
+ cararemixed (uid724089@id-724089.helmsley.irccloud.com)11:34
cararemixedI've recently run an apt upgrade on my pocket reform and the system fails to boot to a GUI now. I'm not sure if it's a kernel update which causes the mode switch to fail but I don't see much on the screen other than the _ cursor in the top-left. I can get it booting again with a system image on the microsd slot but if I upgrade that it gives me the same issue.11:47
joschcararemixed: sorry for that, we had somebody else with the same issue yesterday. I really have to investigate this now.11:49
joschIt sounds like a problem with gdm.11:49
joschelb: you switched to tuigreet but did you manage to figure out what was wrong with gdm?11:49
cararemixedIf you have something I can try I'll look into it. I need to get the system back on the local network and see if I can get in remotely and check.11:51
joschcararemixed: yesterday, elb managed to switch to tuigreet to be able to log back in by connecting to the system via ssh11:52
cararemixedExcellent. Easy enough for the short term. I'll look into it once I'm back home.11:52
+ mjw (~mjw@gnu.wildebeest.org)11:59
+ sevarat (~sevarat@2601:602:8710:8de3:b234:d924:b4e5:f029)12:09
+ paperManu (~paperManu@198.58.139.163)12:13
minutecararemixed: btw if the cursor is movable, you could try pressing ctrl-alt-f2 or f3 (hyper+3 = f3 on pocket), sometimes you can switch away to linux console if it's not totally borked12:14
minutejosch: cararemixed: oh and this issue is news to me. oof oof, wonder what that is12:14
minutejosch: cararemixed: just apt update and apt upgrade can reproduce it or...?12:14
joschminute: i'm trying to reproduce it now and will file an RC bug and make a forum post if i can repro it12:15
josch(flashing sd-card right now)12:15
joschcould be this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=111656312:18
elbjosch: no, I don't know what's wrong with gdm12:19
elbminute: it was just apt update and apt upgrade for me, yes12:19
elbgdm appeared to be happy, systemctl status said it was running, I didn't see any particular errors12:20
joschyup, i can repro -- fresh system image gdm does not start12:20
elb(I didn't dig super deep, though, once I installed greetd and enabled it instead, I bounced; gdm is really slow, anyway)12:20
joschi'll write a quick forum post but gdm3 already has an RC bug12:20
joschelb, cararemixed: did you see the RC bug with apt-listchanges when you upgraded?12:20
elbI did not12:20
elbI did have a bug reported, but it wasn't gdm12:21
+ potash (~potash@user/foghorn)12:21
elblet me see if I can figure out what it was12:21
joschelb: /var/log/apt/term.log should show you exactly what you were shown when you upgraded12:22
joschelb, cararemixed: could either of you write a quick forum post? i have to do family stuff for a few hours now, sorry12:23
joschbut i confirmed the issue with a fresh system image12:23
joschafter the setup wizard, the blinking cursor is shown instead of gdm12:23
minuteuff uff12:23
elbnothing there12:24
minuteare you able to switch consoles?12:24
elbno, there are no other consoles12:24
minutehyper+alt 3 etc12:24
minuteweird12:24
elbor at least not as far as I could tell12:24
elbbut I don't have any other consoles _now_, either12:24
elbthere's only one getty, and it's on tty712:24
cararemixedI created a forum account but I'm not sure if I'm able to post yet. I'm at a cafe but I'll be back in an hour or so.12:25
cararemixedI'll check other TTYs first.12:25
elb(the no other ttys available thing does seem like a problem to me in general, I hadn't dug into that, either, I asn't sure if that was an embedded system problem, like Linux didn't know how to getty on this screen or something)12:26
elbI'll make a quick post12:27
minuteelb: no normally the ttys are ther12:27
minutethere12:27
minuteso something is weird then12:27
minuteat least in gdm one could normally switch to other vts12:27
minutein gnome itself that doesn't seem to work for me atm 12:27
elbsystemd doesn't start any gettys on my system12:28
minuteweird12:29
minutei wonder if something changed in debian at some point and i have an older setup?!12:30
elbis this a pocket-only thing?12:30
minuteelb: i'm on pocket12:30
elb(for the forum post)12:30
minuteah. unknown i guess... would be strange if pocket only12:31
elbI'm going ot post it in the pocket reform category for now12:31
minutegrimmware: my pocket playing youtube/music on battery over wifi r/n at 34% battery, all stable. main changes: charger board v2, fresh cells12:31
minutei'm planning to offer charger board+cells+little usb-c connector bundle in some cheap case so we can ship that anywhere12:32
minute(we can ship batteries if part of a "device")12:32
minute(IATA rules)12:32
elbjosch: minute: posted something to the forum12:35
elbI included the workaround of installing an enabling greetd, but gnome users may not find that satisfactory (I don't know how hard it is to start a valid gnome session from there)12:36
minuteunfortunate that gnome screen locking is tied to gdm. i wonder if they could be convinced to decouple that12:39
minute27%, still stable12:41
chorcminute: were you able to identify what triggered that MPS chip burnout? is there a strategy to avoid it until v2 ships?12:53
- mjw (QUIT: Ping timeout: 256 seconds) (~mjw@gnu.wildebeest.org)12:53
* Guest1398 -> mjw12:56
minutechorc: so far it is thought to be overvoltage spikes but it could also be overcurrent because of subotimal layout. v2 has another protector chip in front of the charger to catch any spikes, and a much improved layout13:00
minutechorc: i would say: keep keyboard brightness low, and if on low battery, shut down before you recharge, that way less current has to go through the MPS chip (i.e. it doesn't have to charge with full current _and_ supply all system current at the same time)13:01
+ gustav25 (~gustav@c-78-82-53-102.bbcust.telenor.se)13:02
minutepocket still stable at 15%13:03
minuteok, need to run to the company. hibernate would be nice now ;D13:08
joschhaha :)13:13
bremner*merge* diff 0 of 59 :sadface:13:19
bremnerapparently things have drifted too far for the "pci reset" patches to apply13:20
elbholy cow minute13:26
elbhow do you fedi13:26
elbyou boosted my post and my notifications are _exploding_13:27
minuteelb: oh woops, hope that's not a nuisance13:43
cararemixedOk. I have my pocket again, the other ttys never worked for my. hyper+alt+N doesn't seem to work.13:45
elbminute: heh no it'll pass, I just can't imagine my fedi feed always being like this -- which I have to imagine yours is, if this is just the reflected glory ;-)13:51
cararemixedShoot. Realizing I had sshd disabled so I can't remote. Does anyone have handy notes on mounting a chroot. I'm quite rusty even if I used to do this sort of thing years ago.13:57
grimmwareminute: that's a nice little regulatory hack, I like it!13:59
grimmwareelb: followed :)14:00
grimmwareoh my god that little HP is stunning14:01
- paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@198.58.139.163)14:07
cararemixedDoh. It was just my resolve.conf. I was trying to bind mount all the things but now I've got it. Fixing up the installation now.14:11
chorcminute: thanks, I'll follow those until my v2 arrives14:25
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)14:26
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)14:26
elbgrimmware: there are few things I enjoy more than a good piece of test equipment :-)14:36
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)14:44
joschcararemixed: i usually do this: mount /dev/mmcblk0p2 /mnt && mount /dev/mmcblk0p1 /mnt/boot && mount -o bind /dev /mnt/dev && mount -t sysfs sys /mnt/sys && mount -t proc proc /mnt/proc14:47
joschand then umount --recursive /mnt14:48
- jahkosha (QUIT: Ping timeout: 244 seconds) (~jahkosha@user/jahkosha)14:54
+ jahkosha (~jahkosha@user/jahkosha)14:55
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)15:06
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)15:07
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)15:07
+ kensanata (~alex@user/kensanata)15:09
[tj]minute: do you have a good resource on laying out usb3 signals?15:12
cararemixedjosch: that is mostly what I had done. The issue was networking to download and install a package to provide the alternative login screen. I had to copy the /etc/resolve.conf over to the chroot as well.15:12
cararemixedI might write up a script if I need to repeat this again any time soon. It might be handy to include with the reform scripts if anyone ends up needing to rescue a system.15:14
- jahkosha (QUIT: Ping timeout: 260 seconds) (~jahkosha@user/jahkosha)15:19
joschThe culprit is firmware-misc-nonfree. Downgrading that package back to version 20250808-1 makes gdm work again. I filed this as a bug with RC severity against firmware-nonfree here: https://bugs.debian.org/111826115:39
joschcararemixed: ^15:39
- Ar|stote|is (QUIT: Read error: Connection reset by peer) (~linx@149.210.6.130)15:49
+ Ar|stote|is (~linx@149.210.6.130)15:56
+ jahkosha (~jahkosha@user/jahkosha)15:58
+ rwa_ (~rene@2001:9e8:339e:8500:b483:a0bf:15bc:f89)16:04
- rwa_ (QUIT: Remote host closed the connection) (~rene@2001:9e8:339e:8500:b483:a0bf:15bc:f89)16:25
minute[tj]: altium academy zack peterson on youtube16:29
jfredOops, I guess I should have reported the GDM issues I was having a while back, I assumed it was something particular to my setup. I ended up switching back to greetd from GDM since I like it better anyway ^^;16:35
- enwu (QUIT: Read error: Connection reset by peer) (~enwu@user/enwu)16:45
+ enwu6 (~enwu@user/enwu)16:45
+ mark_ (~mjw@gnu.wildebeest.org)16:46
[tj]minute: thanks!17:11
- mark_ (QUIT: Ping timeout: 248 seconds) (~mjw@gnu.wildebeest.org)17:12
- andreas-e (QUIT: Quit: Leaving) (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890e.rev.sfr.net)17:32
- kensanata (QUIT: Ping timeout: 246 seconds) (~alex@user/kensanata)20:00
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)20:01
+ kensanata (~alex@user/kensanata)20:01
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)20:09
+ kensanata (~alex@user/kensanata)20:16
- kensanata (QUIT: Ping timeout: 264 seconds) (~alex@user/kensanata)20:22
+ mark_ (~mjw@gnu.wildebeest.org)20:22
* mjw -> Guest515520:23
- Guest5155 (QUIT: Killed (tantalum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)20:23
* mark_ -> mjw20:23
+ Guest5155 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)20:23
+ kensanata (~alex@user/kensanata)20:23
* mhoye_ -> mhoye20:28
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)20:29
+ kensanata (~alex@user/kensanata)20:29
- antti (QUIT: Quit: auf Wiedersehen) (~antti@user/antti)20:43
+ antti (~antti@user/antti)20:44
- antti (QUIT: Client Quit) (~antti@user/antti)20:46
+ antti (~antti@user/antti)20:50
- antti (QUIT: Client Quit) (~antti@user/antti)20:51
+ antti (~antti@user/antti)20:52
- antti (QUIT: Client Quit) (~antti@user/antti)20:52
+ antti (~antti@user/antti)20:56
- antti (QUIT: Quit: auf Wiedersehen) (~antti@user/antti)21:25
+ antti (~antti@user/antti)21:26
- antti (QUIT: Quit: auf Wiedersehen) (~antti@user/antti)21:41
+ wickedshell (~wickedshe@c-174-56-77-83.hsd1.nm.comcast.net)21:44
+ antti (~antti@user/antti)21:50
- antti (QUIT: Remote host closed the connection) (~antti@user/antti)21:50
+ antti (~antti@user/antti)21:52
- antti (QUIT: Client Quit) (~antti@user/antti)21:52
+ antti (~antti@user/antti)21:54
- gustav25 (QUIT: Quit: Quit) (~gustav@c-78-82-53-102.bbcust.telenor.se)22:15
- sevarat (QUIT: Ping timeout: 248 seconds) (~sevarat@2601:602:8710:8de3:b234:d924:b4e5:f029)22:32
- paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)23:13
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)23:19
+ paperManu (~paperManu@198.58.139.163)23:33
elbok so wlgreet is not ideal, it's winding up without a complete session :-/23:36

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!