2025-10-19.log

minutegrimmware: yep, this fix works https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/14000:07
minutech: whenever you have time, could you confirm that your display still works after reboot with this kernel? https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/14000:07
elbminute: I'm pretty sure my adapter just doesn't go that fast, I ordered one with some other stuff I was getting from Digikey anyway00:09
elbminute: does that console line work on rk3588?  if so, why doesn't it normally have a serial console?00:09
minuteelb: that line is specifically for rk3588, and it was something missing in our uboot, that's why it wasn't there by default. also, with that command you can change the baud rate as well, that's why i looked it up for you00:10
joschelb: the reason it does not normally have a serial console is that u-boot does not add this to $bootargs00:10
joschelb: there is a MR fixing this which needs more testing00:10
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)00:20
elboh, yeah, I know how to set up kernel serial console, I guess I just assumed there was a _reason_ it wasn't doing it00:21
joschnah just accidental omission, sorry XD00:21
elbpersonally, I feel like u-boot itself should run at a more ... pedestrian baud rate, as well00:22
elbbut maybe that's just because my adapter won't do 1.5 Mbps ;-)00:22
joschelb: once you have an adapter that does 1.5 Mbps you'll definitely feel the difference00:24
elbI've used a lot of serial consoles in my day, I know that even 115200 is not lag-free00:24
joschusing tmux with vim inside is much more pleasant at 1.5 Mbps00:24
elbit looks like u-boot is not in the pocket reform repo, is that correct?00:25
elboh this makes sense, that's because it's SoM specific, not motherboard specific00:25
elb(I found it)00:25
joschelb: https://source.mnt.re/reform/reform-rk3588-uboot/00:26
joschoh sry :D00:26
elbI guess I should look into recovery from a bad uboot flash before I go too far, here ;-)00:29
elbuh it'll use an sd card, right?00:29
joschelb: if you zeroed emmc, it will fall back to looking on sd-card, yes00:30
- elb (QUIT: Remote host closed the connection) (~elb@68.133.31.194)00:31
+ elb (~elb@68.133.31.194)00:33
elbwell that was unpleasant, my Emacs crashed00:33
elb(not on any reform, on my regular desktop)00:34
minuteaw00:37
lidstahI was about to start asking some questions (before I purchase the reform), and you already answered one :) Hi all!00:37
josch_o/00:38
lidstahI do have another question: I read that the official debian image for the reform is based on Debian unstable - And I'm the kind of guy who likes its Debian the boring way (aka stable). I've seen that there's a community maintained trixie image/iso/etc, but, should I use the official image, is it stable for everyday usage, or is the community trixie version best suited for me? (typical use here:00:53
lidstahtmux, ssh, vim, git, light webbrowsing, listening music, some emulation (fs-uae, dosbox and old consoles, the more demanding stuff being deferred to my proxmox cluster)00:53
joschlidstah: both have upsides and downsides -- it's hard to give a general recommendation00:53
lidstahand sorry for any mistakes, my english is far from perfect00:54
joschDebian unstable will sometimes break and you might be the one discovering this and then need to spend the time to fix things00:54
joschDebian stable is not necessarily more stable because the community maintained image/iso is maintained by only one person who also messes up badly from time to time00:55
lidstahgot it - shit happens, I understand that00:57
lidstahmmh, might run unstable on the emmc, check how's stable by booting on sdcard sometimes/as a backup, and keep data on a nvme drive then00:59
lidstahthank you :)01:00
joschlidstah: if you run into problems, please shout!01:01
lidstahof course01:02
lidstahplus, tinkering with unstable will remember me the good ol' days :)01:04
minutehuh, what https://xcancel.com/mariobalanica/status/197782609910424398001:05
minutethis person managed to get amd rx580 working on rk358801:06
Tramtristglad to see im not the only one using xcancel :)01:06
minuteTramtrist: it's quite useful :D01:06
TramtristIndeed... deleted my X account years ago but its very useful01:07
minutehttps://github.com/mariobalanica/arm-pcie-gpu-patches/tree/main/linux/6.1601:17
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)01:17
+ pomel0 (~pomel0@user/pomel0)01:17
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)01:24
+ pomel0 (~pomel0@user/pomel0)01:24
chminute: will test after athens (so hopefully tue evening)01:24
minutech: nice!01:26
+ Guest57 (~Guest83@2603:800c:3d00:cf33:5141:e882:2da:2a)01:40
- Guest57 (QUIT: Client Quit) (~Guest83@2603:800c:3d00:cf33:5141:e882:2da:2a)01:41
- chrcav (QUIT: Ping timeout: 245 seconds) (~chrcav@user/chrcav)01:41
+ antti- (~antti@user/antti)01:44
* antti- -> antti`01:44
- yqshao (QUIT: Quit: Ping timeout (120 seconds)) (~yqshao@user/yqshao)01:44
+ yqshao (~yqshao@user/yqshao)01:44
- antti (QUIT: Ping timeout: 248 seconds) (~antti@user/antti)01:44
* antti` -> antti01:44
joschhuh, somehow this pipeline got stuck... https://source.mnt.re/reform/reform-system-image/-/pipelines/490401:46
- kensanata (QUIT: Ping timeout: 244 seconds) (~alex@user/kensanata)01:46
+ kensanata (~alex@user/kensanata)01:47
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)02:27
+ chrcav (~chrcav@user/chrcav)02:28
+ murph_nj (~murph@2600:4040:af92:e600:63fd:ded8:1e89:d7b5)02:28
+ kensanata (~alex@user/kensanata)02:29
- murphnj (QUIT: Ping timeout: 260 seconds) (~murph@user/murphnj)02:32
- chrcav (QUIT: Ping timeout: 248 seconds) (~chrcav@user/chrcav)02:44
+ chrcav (~chrcav@user/chrcav)02:51
- mjw (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org)02:58
- paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@198.58.139.163)03:00
- paperManu_ (QUIT: Ping timeout: 256 seconds) (~paperManu@198.58.139.163)03:04
+ paperManu (~paperManu@198.58.139.163)03:26
- lidstah (QUIT: Ping timeout: 272 seconds) (~lidstah@gateway/tor-sasl/lidstah)03:28
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)03:28
- paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@198.58.139.163)03:37
- op_4 (QUIT: Remote host closed the connection) (~tslil@user/op-4/x-9116473)04:05
+ op_4 (~tslil@user/op-4/x-9116473)04:05
+ ZetaR (~user@c-76-148-139-78.hsd1.fl.comcast.net)04:20
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)05:09
+ pomel0 (~pomel0@user/pomel0)05:09
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)05:28
+ pomel0 (~pomel0@user/pomel0)05:28
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)05:52
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.16.22)06:11
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)06:16
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)06:16
+ pomel0 (~pomel0@user/pomel0)06:43
- deuill (QUIT: Quit: Gateway shutdown) (~deuill@mail.deuill.org)07:03
- kensanata (QUIT: Ping timeout: 256 seconds) (~alex@user/kensanata)08:37
+ kensanata (~alex@user/kensanata)08:38
arjanreform2_lpc kernel module is now available in guix https://codeberg.org/guix/guix/pulls/309509:54
joscharjan: nice! Tell me if there is anything we can do better in reform-tools to make your packaging work easier09:58
+ sts-q (~sts-q@89.58.73.149)09:58
arjanthanks! I might try packaging the rest of reform-tools later, will keep that it mind09:59
+ gustav25 (~gustav@c-78-82-53-102.bbcust.telenor.se)10:02
- plomtest (QUIT: Remote host closed the connection) (~plom@user/plomtest)10:14
+ plomtest (~plom@user/plomtest)10:14
+ MartiniMoe (~moe@2001-4dd4-89cb-0-cf33-d0b9-e272-a563.ipv6dyn.netcologne.de)10:15
- schalken (QUIT: Ping timeout: 256 seconds) (~schalken@117-118-178-69.gci.net)10:26
+ schalken (~schalken@117-118-178-69.gci.net)10:28
+ aelius (~aelius@user/aelius)10:34
joscharjan: the license is wrong -- you list it as gpl3+ but the lpc module is distributed under the terms of the gpl210:50
arjanoops good catch11:04
f_\o/11:05
+ rwa_ (~rene@2001:9e8:3394:5100:1b3a:6:8a18:abd5)11:06
- MartiniMoe (QUIT: Ping timeout: 246 seconds) (~moe@2001-4dd4-89cb-0-cf33-d0b9-e272-a563.ipv6dyn.netcologne.de)11:20
grimmwareminute: sick, just installed it! Hilariously it’s causing niri to not render something but my track record with that is just to build main and whatever problem I’ve discovered has already been fixed so fingers crossed.11:43
- rwa_ (QUIT: Remote host closed the connection) (~rene@2001:9e8:3394:5100:1b3a:6:8a18:abd5)11:43
grimmwareminute: http://paste.debian.net/1401545/ that's new, that'll be why my screen is no longer starting up in nir12:00
grimmware*niri12:00
grimmwareI'll come back and have a closer look at this later12:00
- lidstah (QUIT: Ping timeout: 272 seconds) (~lidstah@gateway/tor-sasl/lidstah)12:06
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)12:08
grimmwareyeah looks like this has broken something :/12:18
minutegrimmware: that must be unrelated12:19
minutegrimmware: i.e. other new kernel stuff12:19
grimmwareyeah, makes sense12:19
minutegrimmware: at least i have a hard time imagining how this patch would affect drm on that level hmm...12:19
grimmwareis that branch ahead of main?12:19
minuteor did i change some return value?12:19
minutegrimmware: no it's rebased on main12:20
grimmwareyeah I booted off of a branch rebased off of main a few times yesterday and didn't have this issue12:20
minuteanyway i can do a quick test with sway, niri uses wlroots right?12:20
grimmwaresway works fine12:20
minutehuh12:20
minutedid you rebuild niri in parallel or sth? 12:21
joschgrimmware: are you on debian and are maybe affected by the missing firmware issue?12:21
grimmwareoh?12:21
grimmwareminute: I just rebuilt niri to see if it eliminated the bug which it didn't12:21
minutegrimmware: do you still have gpu accel? in sway, what do you see in glxinfo?12:23
minutemaybe josch has the right hunch12:23
grimmwaregimme a sec to switch back over12:24
minutejosch: did the mali gpu firmware get mangled in the firmware misc package, was that the problem?12:24
grimmwareminute: what am I looking for in glxinfo?12:25
minutegrimmware: llvmpipe vs panfrost12:26
minutegrimmware: i.e. the opengl / gpu driver12:26
minutellvmpipe = software rendering12:26
grimmwareOpenGL renderer string: Mali-G610 (Panfrost)12:26
grimmwarethat what you're looking for?12:26
joschminute: the problem was that the tooling which de-duplicates the firmware files created the symlink but failed to install the file that the symlink is pointing to12:27
minuteok hm looks like gpu ist still ok grimmware12:27
minutejosch: wow ok12:27
josch(the MNT repo has the patched package in it)12:27
grimmwarehmm, I disabled the mnt repos whilst I was fiddling with reprepo so I think I'm going to set that back to normal and do an apt upgrade to see if I'm just missing something that should have been kept in step12:29
joschgrimmware: what is your version of firmware-misc-nonfree?12:29
grimmwareI should be safe from the current gdm situation cos I'm still using a terminal greeter12:29
joschif you don't have version 20250917-1 then that's not the problem12:29
grimmwareno, in fact I'm behind that12:30
joschgood12:30
+ MartiniMoe (~moe@2001-4dd4-89cb-0-d0e4-da8c-8150-98a9.ipv6dyn.netcologne.de)12:30
grimmwarewelp this is still looking like it could be a me problem given we're not at any other conclusion yet so I'm gonna step away from it for a bit and do some chores and then come back when I can debug in a clean house12:31
grimmwareif anyone has any more ideas leave them here and I'll come back round to them but I wouldn't sweat it too much until I can eliminate some other possibilities12:31
grimmwarethanks for your help :)12:32
- MartiniMoe (QUIT: Ping timeout: 248 seconds) (~moe@2001-4dd4-89cb-0-d0e4-da8c-8150-98a9.ipv6dyn.netcologne.de)12:37
minutegrimmware: i'll try to build niri and see if it works for me12:39
grimmwareminute: ty! I think you need to set render-drm-device in the config for it to work correctly in the first place, I've just tried fiddling with that setting and no dice12:41
minutegrimmware: ah sorry, niri actually uses smithay, not wlroots12:46
minutegrimmware: you need to manually set the render device?12:46
grimmwareI've had to in the past hitting this exact same problem12:47
minutesounds weird12:47
minute(it's building here)12:48
grimmwarehttps://github.com/YaLTeR/niri/issues/1199 has some relevant context12:49
minutedone building, lets see if i can start it12:56
minutegrimmware: it starts fine on top of gnome (nested)12:57
+ MartiniMoe (~moe@2001-4dd4-89cb-0-9e46-2680-ac3e-2445.ipv6dyn.netcologne.de)12:57
- MartiniMoe (QUIT: Client Quit) (~moe@2001-4dd4-89cb-0-9e46-2680-ac3e-2445.ipv6dyn.netcologne.de)12:57
minuteok, quitting gnome12:57
minutegrimmware: elb: josch: ch: there's a bug in the pocket keyboard fw. ctrl+alt+f2 -> ctrl+alt+hyper+2 (and alt+hyper+2 if on tty) works _only_ if you press alt and the 2 first, then hyper at the end. i think the hyper modifies the alt or sth13:01
amkhttps://soju.dadd.ie/uploads/akraak/38e5d421-1000018898.jpg half life 2 running via box64+zink :) pretty smooth too13:01
grimmwarehahah, I knew there was something up with terminal switching but I only ever ran into it when I was desperately trying to debug something else13:02
grimmwareamk: sweet.13:02
minuteamk: very nice! is zink faster than bumping the OpenGL version to 3.x?13:04
minutegrimmware: typing this from niri running on my pocket reform without any render device config13:04
amkminute: the opengl renderer seemed buggy the screen was all garbled and stuff so I gave zink a try which fixed the issues13:05
minuteamk: wow ok13:05
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)13:05
grimmwareminute: legit, thank you so much for looking. I'll finish this apt upgrade and then I'll give it all another go, I'll also try pulling the default config but I think that pretty firmly makes it a me problem which is, ultimately, optimal13:06
grimmwareminute: also be sure to have a good play around with niri, it's lovely13:06
minutegrimmware: yeah it's very interesting indeed13:08
minutegrimmware: is there something like alt-tab app switcher, i.e. cycling through apps/windows/overview?13:08
minuteniri doesn't consider by default the rotation of the panel btw13:09
minutei had to set transform "90" for DSI-113:09
minuteoh, there's a hot corner for some kind of overview13:10
grimmwareYeah I think super+o as well13:10
minutenice, niri is like sway but with really nice mouse support and less jank (some smooth animations)13:10
minutegrimmware: do you use a bar?13:11
grimmwareIt’s made me ditch local tmux13:11
grimmwareJust use alacrity with vim copy mode keybindings to emulate tmux13:11
minuteoh nice13:12
minute`niri validate` is also really nice13:12
grimmwareI like that you can always launch a new terminal and it’s not hilariously small13:12
minutehaha right!!13:16
minutethe workspace can just grow13:16
minutethat's actually the most annoying thing about classic tiling, you're so right13:16
minuteor some apps that are just squeezed in very unnatural ways because they expect floating13:16
minutegrimmware: btw i'd just recommend to remove the render-device explicit config. it just works out of the box for me13:24
grimmwareYeah I’ve just tried that but no dice! The dumb thing as well is if I quit nori my screen stays off :/13:25
grimmwareWhich would be less of a problem if i wasn’t trying to clean the house at the same time13:25
grimmwareI mean this should be self evident from my presence here but I am doing a *terrible* job of cleaning the house13:28
minutegrimmware: hah. i also should do some chores. btw i built latest niri from today's git13:29
minutegrimmware: and started directly from tty where i logged in as my user13:29
minute(i.e. no greeter)13:29
minutei'm trying to find out how to start niri from gdm...13:30
minutebtw cursor is more laggy for me on 120hz screen than on gnome, interesting13:32
grimmwarehmm, I launched from greeter... perhaps I should try from a tty.13:32
grimmwareI'm actually using their systemd setup which could be a factor13:33
grimmwareI also built from main today'13:34
minutejosch: about steam, i have `export PAN_MESA_DEBUG=gl3` in my /etc/profile and forgot about that! i get opengl 3.3 by default13:35
minutehmm maybe that's also why niri works for me? :D13:35
minutegrimmware: ah, systemd setup sounds like it could be the issue, maybe unexpected permissions etc13:36
minutegrimmware: try just starting the niri executable from tty13:36
+ paperManu (~paperManu@198.58.139.163)13:38
minuteah i should have used niri --session or niri-session13:44
joschminute: PAN_MESA_DEBUG=gl3 was the missing piece! The game runs now o013:46
minutejosch: neat. i should add that to my fedi post13:46
+ wakest (m-a7d6fe@67.219.99.225)13:46
joschawesome, great you remembered that :)13:50
joschbut it's incredible how "out of the box" this is working now o013:51
minutejosch: yesss13:51
minute> /home/minute/src/niri/target/debian/niri_25.8.0-1_arm64.deb13:51
grimmwarethe PAN_MESA_DEBUG did not save me13:52
minutegrimmware: yeah thought so. did you try launching from tty?13:52
grimmwarethe annoying thing is it essentially turns the screen off and I then can't turn it back on again13:52
minutegrimmware: do you have an external screen perhaps?13:53
grimmwareminute: yeah, I'd need to check if there's anything that's a little more intelligent going on with the session service, I might have to temporarily disable it13:53
grimmwarecos it could be that the binary is checking for a socket or some shit13:53
grimmwareminute: I do, I'm supopsed to be cleaning13:53
grimmwareI just can't leave well enough alone13:54
minuteok13:54
grimmwaretoo excited about having the screen flicker fixed13:54
minuteit's weird though that the display doesn't turn on again13:54
minutethis could be the behavior that prompted me to introduce a fix that introduced the flicker... because on ch's pocket the screen wouldn't come up after reboot13:55
minutegrimmware: ok i built the deb (using cargo-deb) and installed it and now i was able to launch niri from gdm just like that. it works14:01
minuteand now it's much faster for some reason...14:03
grimmwareminute: yeah I think it mighht be that issue again because I just disabled and then attempted to re-enable my display under sway and it didn't come back on14:03
minutegrimmware: damn14:03
minutegrimmware: ok thanks for testing that, it's what i feared and why i didn't directly merge it14:03
minutewhy is my display different than yours and ch's in that regard...14:04
minuteanyway, i won't give up on that issue14:04
grimmwareminute: do you have a workflow for just applying the patches to the kernel tree so that you can diff them without having to do a diff of a diff?14:04
minutegrimmware: yeah14:05
minutegrimmware: well, the 2 patches are merged now in my MR14:06
minutegrimmware: so, no diff of diff needed14:06
minutegrimmware: btw because i was lazy i just created that patch in emacs. emacs can directly edit a diff and adjust it if you're careful enough14:07
minutegrimmware: so i just edited the diff and pushed that and i was lucky it built14:07
minutegrimmware: but normally i would git clone the same linux version that debian uses, but from kernel.org, then apply any needed patches from reform-debian-packages (that can be easily done with bash for loop), then commit that as a baseline.14:08
minutegrimmware: from there, any changes will show up in local git as diffs to what is in reform-debian-packages, so i can commit new things and "git show xyz > foo.patch" for example14:08
grimmwareminute: I'm really just after being able to directly compare the different patched versions of the file directly myself between commits because dealing with the diffs of diffs is a bit of a mindfuck14:09
minutegrimmware: i wouldn't bother14:09
grimmwarelike I've hacked this together before by just adding an exit to one of the build scripts14:09
minutebtw the following works for me: niri msg output DSI-1 off; and then: niri msg output DSI-1 on14:13
minutei understand that doesn't work for you so there must be some subtle difference for those display panels14:13
minutegrimmware: btw so far i thought you have display v1. maybe you have v2? because you were talking about the "fade out" effect that happens only on v2 i think14:14
minutegrimmware: what's the output of `cat /sys/devices/platform/fde30000.dsi/fde30000.dsi.0/mnt_pocket_reform_panel_version` ?14:15
minute(for me it's 1)14:15
grimmware114:16
grimmwareI've had this thing since before there *was* a v2 :)14:16
minutegrimmware: ok, gotcha!14:17
grimmwareas far as I'm aware we have the same configuration, v1 rk3588 16GB14:17
minuteyeah. but i guess displays are from different batches14:19
minuteanyway, i have to do more display hacking soon to help bringup the edk2 display stuff as well14:19
minutei think i'll rework the driver so it's more easy to read/follow/debug14:19
minuteand that more of the sequencing can be adjusted at runtime so we can test this out faster with scripts14:20
+ mjw (~mjw@gnu.wildebeest.org)14:20
minuterather than rebuilds + reboots14:20
grimmwareyeah that sounds good14:21
grimmwareminute: do you still get ghosting?14:23
minutegrimmware: don't know, maybe? i didn't pay attention recently14:26
minutemy panel is quite crusty so i wanna replace it with v2 soon14:26
minuteafter i fix those issues for v1 users...14:26
grimmwarelike, if my panel turns out to be kind of unique I'm not against also replacing but I would like to know that I'm not just walking away from a problem that I could help solve if it's actually useful to other people14:28
minutegrimmware: i think ch has the same kind of panel14:28
minutei'll check on monday or tuesday if i have a panel in old stock that behaves like this14:29
minutegrimmware: btw yes i still get ghosting, esp on gray (just saw in gdm)14:30
grimmwareyeah same14:31
minutewe should probably offer disp v2 in the shop soon :314:31
- wakest (QUIT: Remote host closed the connection) (m-a7d6fe@67.219.99.225)14:39
+ aloo_shu (~aloo_shu@85.51.16.22)14:54
grimmwareOkay back at an external monitor and niri will actually fail to render anything even on the external monitor unless I have that render-drm-device set14:56
grimmwareah great qutebrowser no longer actually renders anything what the hell14:57
minutegrimmware: started from tty?15:00
grimmwarenah15:03
minutegrimmware: then we can't really compare15:06
grimmwareYeah sorry just debugging what I can in a single boot first because I have to turn the whole machine off and on again for every test of the inbuilt display15:08
minutegrimmware: ok gotcha.15:09
minutegrimmware: so the oscillation/flicker comes from the display not being fully turned off but the dsi stream from the computer stopping. 15:10
- chomwitt (QUIT: Ping timeout: 246 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)15:20
+ paperManu_ (~paperManu@198.58.139.163)15:29
- paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@198.58.139.163)15:32
grimmwareminute: I've just thrown together a build that's a combination of your patch and my patches (much easier with the patches merged together), there's a few things that are happening in init that are happening in the wrong order according to the datasheet and a missing soft_reset. I feel like this would be consistent with the behaviour that we're seeing and it would make sense if the batch that15:47
grimmwareyou're on was just a bit more forgiving. I mean it's still kind of a shot in the dark but I figure if it lands us back exactly where we are then that's fine too.15:47
grimmwarejust because we'd eliminate that difference as a source of where this could come from15:47
+ wakest (m-a7d6fe@67.219.99.225)15:53
elbminute: that (re: hyper order) actually makes sense, I suppose the hyper should modify _every_ key that is currently pressed and right now it may not15:57
elbctrl+alt+n then hold and hit hyper works for me, confirmed15:58
minutegrimmware: sure, please show!16:07
minuteelb: great. yeah it looks like hyper changes alt to altgr16:08
elboh, so it probably _is_ recognizing all the keys, and it's just not the right keystroke16:11
elbI've got the firmware open now16:11
grimmwareminute: https://source.mnt.re/grimmware/reform-debian-packages/-/pipelines/4907 is the pipeline, it's currently building16:11
minuteelb: yeah in the matrix defintion, in the hyper layer, altgr / rightalt or however it's called should be changed to leftalt on that key 16:14
grimmwaream I right in thinking that I don't actually need qcacld on rk3588?16:18
elbI actually wondered about those keys when I created my layout, in general the swapping of left-for-right modifiers16:19
grimmwareright here goes nothing16:24
grimmwarelol no it hasn't come on at all this time16:27
lidstahHi all, and just ordered the reform (spent half of the night reading forums and docs, got the printed manual too) :)16:31
lidstahs/got/took/16:32
grimmwarehi lidstah!16:33
grimmwareI'm digging around in pocket reform display code16:33
lidstahHi grimmware :)16:33
lidstahbrowsing the site and shop also made me want to recap my old A1200 (although it doesn't seem there's a ZZ9000 A1200 version, I'm wondering if the Zorro-II version would work in a towered A1200…)16:36
lidstah(and reading further, nope)16:38
grimmwareaight that's another build kicked off with some more of the recommended delays added, imma go shower and then walk the dog and come back and test the new build16:44
grimmwareso glad I got a suitable setup for testing this in CI <316:45
- xktr (QUIT: Ping timeout: 256 seconds) (~xktr@user/xktr)16:56
+ xktr (~xktr@user/xktr)16:57
joschgrimmware: no qcacld needed on rk3588 -- can you confirm that reform-check is telling you this information as well?16:58
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)17:16
grimmwarereform-check is telling me... a lot17:59
grimmwareI'll have a look at that tomorrow17:59
grimmwaremy adjusted timings didn't help, I think I'm going to have to come back to this during the week and add a bunch of debug so I can actually prove to myself that I know any of what's going on here18:00
- Ar|stote|is (QUIT: Read error: Connection reset by peer) (~linx@149.210.6.130)18:03
+ Ar|stote|is (~linx@149.210.6.130)18:09
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)18:18
minutelidstah: cool, welcome!18:20
- chomwitt (QUIT: Ping timeout: 244 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)18:20
minutelidstah: and yeah, zz9k should work with towered a1200, i tested it once (i don't have that tower anymore though). it also works with zorro adapter on a50018:20
- timide (QUIT: Remote host closed the connection) (~timide@user/timide)18:24
+ rwa_ (~rene@2001:9e8:3394:5100:1b3a:6:8a18:abd5)18:47
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)18:48
+ timide (~timide@user/timide)18:57
lidstahminute: ah thanks for the answer about the zz9000 and the A120019:20
lidstahmight be a nice project for next summer (although I should recap it first and get a new power supply for it, it's been stored properly but I haven't powered it on since ~15 years)19:29
+ bkeys1 (~Thunderbi@98.19.131.193)19:47
- bkeys (QUIT: Ping timeout: 244 seconds) (~Thunderbi@98.19.131.193)19:49
* bkeys1 -> bkeys19:49
- mhoye (QUIT: Ping timeout: 244 seconds) (~mhoye@li319-32.members.linode.com)19:49
+ mhoye (~mhoye@li319-32.members.linode.com)19:51
- rwa_ (QUIT: Quit: Leaving) (~rene@2001:9e8:3394:5100:1b3a:6:8a18:abd5)20:20
- chomwitt (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)20:45
- kensanata (QUIT: Ping timeout: 248 seconds) (~alex@user/kensanata)20:47
+ kensanata (~alex@user/kensanata)20:48
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)20:56
- chomwitt (QUIT: Ping timeout: 250 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)21:02
+ paperManu (~paperManu@198.58.139.163)21:17
+ wielaard (~mjw@gnu.wildebeest.org)21:31
- mjw (QUIT: Ping timeout: 256 seconds) (~mjw@gnu.wildebeest.org)21:33
+ AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net)21:36
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)21:39
* wielaard -> mjw21:41
- jacqueline (QUIT: Ping timeout: 264 seconds) (~jacquelin@user/jacqueline)21:49
- switchy (QUIT: Ping timeout: 264 seconds) (~switchy@mechboards/switchy)21:51
- se6astian (QUIT: Ping timeout: 264 seconds) (~quassel@46.101.193.235)21:52
+ se6astian (~quassel@46.101.193.235)21:53
- frickler (QUIT: Ping timeout: 264 seconds) (~jens@user/frickler)21:55
- sknebel (QUIT: Ping timeout: 264 seconds) (~quassel@v22016013254630973.happysrv.de)21:55
+ sknebel (~quassel@v22016013254630973.happysrv.de)21:56
+ frickler (~jens@user/frickler)21:57
+ switchy (~switchy@mechboards/switchy)22:03
+ jacqueline (~jacquelin@user/jacqueline)22:04
- gustav25 (QUIT: Quit: Quit) (~gustav@c-78-82-53-102.bbcust.telenor.se)22:15
- digitalrane (QUIT: Ping timeout: 250 seconds) (~digitalra@user/digitalrane)22:31
- chomwitt (QUIT: Ping timeout: 244 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)23:12
- cobra (QUIT: Ping timeout: 265 seconds) (~cobra@user/Cobra)23:22
- AnimaInvicta (PART: !!unknown attribute: msg!!) (~AnimaInvi@88-120-179-216.subs.proxad.net)23:28
+ deuill (~deuill@mail.deuill.org)23:29
+ cobra (~cobra@user/Cobra)23:37
+ pomel0 (~pomel0@user/pomel0)23:45
- cobra (QUIT: Quit: ZNC 1.8.2 - https://znc.in) (~cobra@user/Cobra)23:57

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