2025-07-21.log

- andreas-e (QUIT: Quit: Leaving) (~Andreas@2a02-8434-b6a3-e901-daca-beef-9a0a-5e34.rev.sfr.net)00:18
- potash (QUIT: Quit: The Lounge - https://thelounge.chat) (~potash@user/foghorn)00:22
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@ip-80-113-60-100.ip.prioritytelecom.net)00:27
ch40hmm00:33
* ch40 -> ch00:33
chmaybe best to check what the desktops support (:00:33
chbut not today00:33
+ casparvitch (~casparvit@130.102.176.164)01:27
- schalken (QUIT: Quit: Leaving) (~schalken@117-118-178-69.gci.net)01:43
+ schalken (~schalken@117-118-178-69.gci.net)01:44
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)02:01
- chomwitt (QUIT: Ping timeout: 245 seconds) (~chomwitt@2a02:85f:9ad5:a100:1ac0:4dff:fedb:a3f1)03:23
- casparvitch (QUIT: Ping timeout: 245 seconds) (~casparvit@130.102.176.164)04:07
+ jn_ (~quassel@2a0a-a54a-c4e6-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)04:19
- jn_ (QUIT: Changing host) (~quassel@2a0a-a54a-c4e6-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)04:19
+ jn_ (~quassel@user/jn/x-3390946)04:19
- jn (QUIT: Ping timeout: 276 seconds) (~quassel@user/jn/x-3390946)04:19
+ casparvitch (~casparvit@130.102.176.164)04:58
- casparvitch (QUIT: Ping timeout: 240 seconds) (~casparvit@130.102.176.164)05:41
+ casparvitch (~casparvit@1.146.79.201)05:42
- casparvitch (QUIT: Read error: Connection reset by peer) (~casparvit@1.146.79.201)07:29
+ casparvitch (~casparvit@1.146.79.201)07:35
- casparvitch (QUIT: Read error: Connection reset by peer) (~casparvit@1.146.79.201)08:10
+ casparvitch (~casparvit@130.102.176.164)08:12
- casparvitch (QUIT: Ping timeout: 240 seconds) (~casparvit@130.102.176.164)09:40
+ mjw (~mjw@ip-80-113-60-71.ip.prioritytelecom.net)10:01
+ chomwitt (~chomwitt@2a02:85f:9ad5:a100:1ac0:4dff:fedb:a3f1)10:29
+ casparvitch (~casparvit@36-255-114-132.ip4.superloop.au)11:20
- casparvitch (QUIT: Ping timeout: 276 seconds) (~casparvit@36-255-114-132.ip4.superloop.au)11:27
+ gsora (~gsora@user/gsora)11:44
+ andreas-e (~Andreas@2a02-8434-b6a3-e901-daca-beef-9a0a-5e34.rev.sfr.net)11:51
+ casparvitch (~casparvit@36-255-114-132.ip4.superloop.au)11:59
- BAndiT1983 (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@46.101.193.235)12:01
- anuejn_ (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@46.101.193.235)12:01
- se6astian (QUIT: Quit: se6astian) (~quassel@46.101.193.235)12:01
minutecc ch https://lore.kernel.org/all/7228f2c6-fbdd-4e19-b703-103b8535d77d@redhat.com/ and https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/391612:12
minutesounds like openrgb upstreaming is the way for LEDs12:13
+ gustav28 (~gustav@c-78-82-54-7.bbcust.telenor.se)13:02
- mjw (QUIT: Ping timeout: 248 seconds) (~mjw@ip-80-113-60-71.ip.prioritytelecom.net)13:12
- chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:85f:9ad5:a100:1ac0:4dff:fedb:a3f1)13:35
+ chomwitt (~chomwitt@2a02:85f:9a2a:ce00:1ac0:4dff:fedb:a3f1)13:35
- colinsane (QUIT: Ping timeout: 276 seconds) (~colinunin@97-113-88-198.tukw.qwest.net)13:35
doki am having a lots of issue with the usb on my keyboard4 today...13:57
doki tried to debug a bit with cynthion/luna usb analyzer but it is not very clear to me what the issue is13:57
dokalso reseting the usb stack does not always works13:58
dokwhich is new, it was working as workaround few days ago13:58
doki don't know if this issue comes from the keyboard or from my computer14:01
+ BAndiT1983 (~quassel@46.101.193.235)14:03
+ se6astian (~quassel@46.101.193.235)14:03
+ anuejn (~quassel@46.101.193.235)14:03
dokbut someone on the usb bus is spamming ACK "transaction" not sure what this means, maybe a straight ACK packet but this is weird14:05
Zabawell, the usb controller polls input devices periodically, maybe that’s what you’re seeing 14:15
doki also see the polling of the HID IN endpoint14:16
doki reverted my local modifications back to origin/master and it did got stuck again14:18
doki am starting to wonder if my issue is related to the thunderstorm yesterday night14:19
- casparvitch (QUIT: Ping timeout: 248 seconds) (~casparvit@36-255-114-132.ip4.superloop.au)14:21
- bkeys (QUIT: Ping timeout: 268 seconds) (~Thunderbi@98.19.131.193)15:02
+ bkeys (~Thunderbi@66.110.201.50)15:08
- bkeys (QUIT: Ping timeout: 245 seconds) (~Thunderbi@66.110.201.50)15:28
- svp (QUIT: Ping timeout: 245 seconds) (~svp@host-79-7-240-189.business.telecomitalia.it)15:44
joschminute: alsa-ucm-conf is a Depends of reform-desktop-full now15:48
joschminute: also nice to see your updated git committer name :)15:49
joschIs the Reform Next surface a different finish compared to the classic? It looks somehow more "matte"15:50
josch(really awesome to see the photos, it looks so good!)15:50
bremnerch: do you have any pointers about DT bindings? documentation, where they live in the tree, etc...15:52
+ bkeys (~Thunderbi@66.110.201.50)15:54
+ svp (~svp@host-79-7-240-189.business.telecomitalia.it)16:04
+ mjw (~mjw@81.175.68.189)16:15
jogudok I've been having similar issues with my V4 keyboard but I've been testing alternative firmwares. The only lead I have right now is that RGB seems to make the problem worse so disabling it or dimming it significantly might help prevent the USB device from crashing16:29
doki've seen the issue regardless of the rgb level, even at the lowest setting16:31
joguI've never had it happen on the official firmware with RGB off, but all other firmwares I've tried (QMK, KMK, & ZMK) show it pretty quick and even with RGB off16:32
joguI haven't dug too much into debugging on the official firmware but under ZMK (Zephyr) debug logs show a lot of CRC errors, RX overflow, bit suff error even before the device dies out16:36
jogulsusb shows this when it stops responding: cannot read device status, Resource temporarily unavailable (11)16:36
joguIs this also what you see?16:36
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)16:48
+ bkeys1 (~Thunderbi@66.110.201.50)16:48
dokhow does Zephyr handle printing the debug information? it can break/make the USB depending on how it's done16:49
dokthe kernel sees nothing16:50
dokno unusual messages16:50
* bkeys1 -> bkeys16:51
joguNot sure of the low level details how Zephyr handles printing. I've disabled USB logging (no ttyACM device) and am using a second Rpi pico connected to the UART port to get logging16:52
dokfrom my experience on barebox (u-boot fork) uart printf can break device-driver16:52
dokbetter use an external usb debugger16:53
dokand wireshark usbmon isn't very helpful either16:53
joguYeah, I'm sure there are better ways to debug. I'm not a hardware person and just using what I have laying around haha16:54
[tj]jogu: sounds like a power issue if dimming helps16:55
- chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:85f:9a2a:ce00:1ac0:4dff:fedb:a3f1)16:55
dokalso usb hub can "help" a lot16:55
+ chomwitt (~chomwitt@2a02:85f:9a5b:c600:1ac0:4dff:fedb:a3f1)16:56
dokhelp to make things work, not debug them ^^16:56
[tj]jogu: that might be enough, if you can connect over swd then you might get more helpful information. With swd you should be able to single step the keyboards mircocontroller, this won't help a ton if it is a power issue16:57
jogu[tj] I tried looking at the PCB in kicad but I don't think the SWD pins are exposed 16:58
joguNot confident enough in my soldering skills to try anything more brave either haha16:58
jogudok by external usb debugger do you mean this cynthion device you mentioned earlier/16:59
dokyes, or a logic analyzer16:59
doki have more used a `lecroy teledyne advisor` when debugging USB at my previous job17:01
dokbut now at home i have a Cynthion/LUNA17:02
doki didn't used much, until now17:02
doki'll soon acquire a DIY/protope logic analyzer that goes to between 32 to 64 MS/s17:04
dokso i'll be able to see the USB line directly, at least i'll try to17:05
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)17:16
doksadly it doesn't support 5v :/17:16
+ jogu (~jogu@user/jogu)17:17
joguI see, maybe I'll have to try and investigate getting access to a logic analyzer17:18
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)17:31
minutejosch: thanks!17:31
+ jogu (~jogu@user/jogu)17:31
minutedok: can you try another fw branch where i'm sending the reports only when needed?17:32
dokyeah, i haven't tried your branch17:33
dokbut i still had the issue with the same kind of fix17:33
dok(i sent the MR)17:33
minutedok: i'm quite interested in cynthion, can you recommend it?17:33
doki am very biased because i used a lecroy teledyne, so far i do not recommend cynthion, it is cool and does work but the packetry interface isn't the best.17:35
dokbut it is still more useful than wireshark (usbmon) and can capture much longer than a logic analyzer17:36
doki should try to upgrade it's firmware, seems to have changed17:37
doks/firmware/gateware/17:39
dokon the other hand teledyne lecroy is expensive and their software only runs on windows, is very slow and breaks often...17:41
dokso maybe i do recommend cynthion :)17:46
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@66.110.201.50)17:57
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@81.175.68.189)18:17
minutedok: ok thx18:31
+ bkeys (~Thunderbi@66.110.201.50)18:52
+ mjw (~mjw@81.175.68.189)18:55
- bkeys (QUIT: Ping timeout: 245 seconds) (~Thunderbi@66.110.201.50)19:03
- kensanata (QUIT: Quit: OK) (~alex@user/kensanata)19:10
+ kensanata (~alex@user/kensanata)19:11
+ bkeys (~Thunderbi@98.19.131.193)19:13
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@98.19.131.193)19:49
+ bkeys (~Thunderbi@98.19.131.193)19:51
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@98.19.131.193)20:00
+ bkeys (~Thunderbi@66.110.201.50)20:08
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)20:19
+ bkeys1 (~Thunderbi@66.110.201.50)20:19
* bkeys1 -> bkeys20:22
chbremner: docs should be in ./Documentation/devicetree/bindings but probably you have to git grep20:25
bremnerch: ok20:25
+ shtrophic (~m-hrdsqi@user/shtrophic)20:27
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)20:29
+ bkeys1 (~Thunderbi@66.110.201.50)20:29
* bkeys1 -> bkeys20:32
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)20:39
+ bkeys1 (~Thunderbi@66.110.201.50)20:39
* bkeys1 -> bkeys20:42
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)20:49
+ bkeys1 (~Thunderbi@66.110.201.50)20:50
* bkeys1 -> bkeys20:52
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)21:00
+ bkeys (~Thunderbi@66.110.201.50)21:00
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)21:10
+ bkeys1 (~Thunderbi@66.110.201.50)21:10
* bkeys1 -> bkeys21:12
+ reform8153 (~user@90.187.186.49)21:20
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50)21:20
+ bkeys1 (~Thunderbi@66.110.201.50)21:21
reform8153hello21:21
reform8153someone else already tried full-upgrade?21:21
reform8153i get Error: Internal Error, AutoRemover broke stuff 21:22
reform8153due to unsatified  dependencies21:22
* bkeys1 -> bkeys21:23
joschreform8153: can you put more context in a pastebin?21:25
reform8153sure21:27
bremneroh, I remember seeing that often ~ 1 month ago21:28
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50)21:30
+ bkeys1 (~Thunderbi@66.110.201.50)21:31
frickleractually running "apt autoremove" fixed that issue for me couple of days ago21:33
* bkeys1 -> bkeys21:33
+ xorAxAx (sid624141@id-624141.hampstead.irccloud.com)21:36
xorAxAxhi, are non rockwell CPU modules for the reform still available somewhere?21:36
xorAxAxor the pocket21:36
reform8153this is the apt history https://pastebin.com/WctjuTbv 21:39
joschuh funky you even recently upgraded21:40
reform8153and this is the error https://pastebin.com/HSnGvw3421:41
joschreform8153: if you pastebin this (only do this if you are fine with sharing which packages you have installed) then i can likely reproduce your issue locally: dpkg-query --showformat '${binary:Package}=${Version}\n' --show21:41
joschoh21:41
joschwait21:41
joschthe issue might be more simple :)21:42
reform8153great :D21:42
joschfrickler: did your apt also get stuck because of reform-qcacld2?21:42
joschreform8153: can you confirm that apt wants to autoremove these?21:42
fricklerjosch: I think so, yes21:43
bremnerxorAxAx: by chance did you mean "non-rockchip"?21:43
joschreform8153: what platform are you on?21:45
reform8153idk if it want's to remove that. it only tells me that it can't resolve the dependency issues21:46
reform8153i am on the standard mnt pocket reform with the default chipset21:46
reform8153can't rememner what is was rn :)21:46
joschreform8153: so when you run cat /proc/device-tree/model it says this:21:47
joschMNT Pocket Reform with i.MX8MP Module21:47
reform8153MNT Pocket Reform with i.MX8MP Moduleu21:47
reform8153yes21:47
joschreform8153: can you give me the output of this:21:48
joschdpkg -l | grep qcacld21:48
xorAxAxbremner: yeah, sorry :D21:49
reform8153https://pastebin.com/L1BZ1MV521:49
xorAxAxbremner: you dont have the rockwell version of the cpu module yet? :P21:49
joschreform8153: okay this is indeed a job for the autoremover21:49
joschreform8153: you can safely remove reform-qcacld2-6.10.9-mnt-reform-arm64 and reform-qcacld2-6.11.10-mnt-reform-arm6421:50
reform8153nice21:50
joschfrickler: but you have a pocket with rk3588, no?21:50
joschreform8153: but running "sudo apt autoremove" gave you the same error you say?21:50
reform8153ok will do that and then do full-upgrade21:50
fricklerjosch: ack21:52
reform8153ok seem it is running21:53
joschxorAxAx: maybe try writing to the forum -- there are probably a couple of people who upgraded to rk3588 and want to get rid of their old board or something?21:53
joschxorAxAx: I can recommend the A311D with which I am writing this :)21:53
xorAxAxjosch: ah, which manufacturer is that?21:54
joschxorAxAx: it's the bananapi cm4: https://shop.mntre.com/products/mnt-reform-cm4-processor-module-adapter21:55
xorAxAxah, thats still available!21:56
xorAxAxah, no, out of stock21:57
- reform8153 (QUIT: Remote host closed the connection) (~user@90.187.186.49)21:57
+ reform15982 (~user@business-90-187-186-49.pool2.vodafone-ip.de)21:59
reform15982full-uprade seems to have worked! thx for the help josh21:59
joschnice, glad to hear!22:03
joschfrickler: if you have the rk3588 reform, just get rid of qcacld222:03
joschfrickler: unless of course you plan to switch back to imx8mplus in the future22:03
fricklerjosch: seems it was part of the initial system image, though? would it make sense to have a platform specific cleanup tool? also no switching back, started with rk3588 right away, going to stick with it ;)22:05
joschfrickler: yes, it's part of the system image because that system image is supposed to work out-of-the-box everywhere22:06
joschfrickler: the clean-up-tool is called reform-check -- i don't think it would be a good idea to have a tool run "apt remove X" for you22:06
joschminute: do you agree that reform-check should suggest users without imx8m+ to remove the qcalcd2 package?22:07
frickleralso the issue was just 2 days ago, seems I misremembered. I can post the history.log somewhere if you need more data to check things22:07
reform15982i was actually curious... was there a stable release already for the pocket?22:07
joschreform15982: there is no stable release, the MNT repo is based on unstable22:07
reform15982kk22:08
joschreform15982: and if you are thinking of Debian Trixie: that has the problem that there is no qcalcd222:08
joschwell, it technically has that but there are 2 problems22:09
reform15982hehe sounds like unstable is good for now :D22:09
joscha) building it takes ~15 minutes every time you rebuild the dkms module (okay, should be rare on stable in comparison to unstable but still...)22:09
joschb) you have to install the firmware manually because the firmware package ezurio-qca-firmware has been waiting in the Debian NEW queue for over a year22:10
kfxis there a reason the driver is dkms-ed instead of existing as a patch?  has anyone tried upstreaming the driver into mainline?22:12
joschkfx: yes, m.inute tried and failed22:14
- reform15982 (QUIT: Remote host closed the connection) (~user@business-90-187-186-49.pool2.vodafone-ip.de)22:15
kfx:(22:15
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-54-7.bbcust.telenor.se)22:15
joschthe vendor module is 811k loc, that's why it takes so long to build22:15
sigridwhat's qcalcd2?22:17
joschhttps://github.com/boundarydevices/qcacld-2.0/tree/boundary-CNSS.LEA.NRT_3.122:17
joschand on top of that we add 2.2k lines of patch because the thing failed to compile on 6.7, then on 6.8, then on 6.11, then on 6.13, then on 6.14, then on 6.15...22:18
joschit's lots of fun every time...22:18
sigridlovely22:19
sigridlinux kernel is sure a fast moving target22:19
kfxI miss the odd/even release cadence.  at least back then you got more than a week out of a kernel release22:20
joschwell, if you have 811k loc, some of the api it uses is bound to change every once in a while :D22:21
+ RoosterZero (~RoosterZe@user/RoosterZero)22:25
grimmwareThe cost of progress.22:33
grimmwareI’m glad I’m so helpful.22:34
minutejosch: yes, agreed @ qcacld222:40
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@66.110.201.50)22:41
minutexorAxAx: check mouser and crowd supply, they should have some stock22:42
minutekfx: the upstream driver is ath10k22:43
+ casparvitch (~casparvit@36.255.114.132)23:30

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