2026-01-15.log

* wielaard -> mjw00:01
- Ar|stote|is (QUIT: Read error: Connection reset by peer) (~linx@149.210.3.83)00:10
+ Ar|stote|is (~linx@149.210.3.83)00:18
amkis there a way to disable the pocket changing keyboard brightness on being plugged in? sometimes it seems to reset when its left connected and wakes me up if i left it open in my room lol00:42
- L29Ah (PART: !!unknown attribute: msg!!) (~L29Ah@wikipedia/L29Ah)00:54
rick_amk you can set it to the same low setting when its on battery see line 49 and 55 as a short workaround in /usr/libexec/reform-tools/reform-power-daemon00:54
rick_this way it wont flicker anymore XD00:55
amkah neat, thank you!01:00
rick_i set ac to the lower level, so both are at: "xLBRT\x05" and afterwards you have to restart the service: /usr/libexec/reform-tools/reform-power-daemon01:02
rick_just remembert, this can be overwritten again in the next package update ^^01:03
- chomwitt (QUIT: Ping timeout: 250 seconds) (~chomwitt@2a02:85f:9a0a:f200:1ac0:4dff:fedb:a3f1)01:34
- bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@134.22.115.162)01:39
- cow321 (QUIT: Ping timeout: 264 seconds) (~deflated8@user/meow/deflated8837)01:41
+ bkeys (~Thunderbi@h69.128.19.98.dynamic.ip.windstream.net)02:08
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@h69.128.19.98.dynamic.ip.windstream.net)02:11
+ bkeys (~Thunderbi@98.19.128.69)02:11
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@98.19.128.69)02:29
+ bkeys1 (~Thunderbi@98.19.128.69)02:29
* bkeys1 -> bkeys02:32
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)02:33
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@98.19.128.69)02:35
+ bkeys (~Thunderbi@98.19.128.69)02:35
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@98.19.128.69)02:42
+ bkeys (~Thunderbi@98.19.128.69)02:43
+ L29Ah (~L29Ah@wikipedia/L29Ah)02:45
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)03:06
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)03:13
+ cow321 (~deflated8@user/meow/deflated8837)03:13
- cow321 (QUIT: Ping timeout: 240 seconds) (~deflated8@user/meow/deflated8837)03:23
+ cow321 (~deflated8@user/meow/deflated8837)03:24
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@98.19.128.69)03:27
+ bkeys (~Thunderbi@98.19.128.69)03:27
- cow321 (QUIT: Ping timeout: 240 seconds) (~deflated8@user/meow/deflated8837)03:32
- L29Ah (QUIT: Ping timeout: 252 seconds) (~L29Ah@wikipedia/L29Ah)03:32
- paperManu_ (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156)03:51
- paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@146.71.9.156)03:52
+ pomel0 (~pomel0@user/pomel0)03:56
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)04:04
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)04:04
+ cow321 (~deflated8@user/meow/deflated8837)05:09
- voltaire28 (QUIT: Ping timeout: 252 seconds) (~jlafon@28.162.2.93.rev.sfr.net)05:17
+ reform12019 (~ryan@user/wirelessrpm)05:49
+ voltaire28 (~jlafon@28.162.2.93.rev.sfr.net)05:51
reform12019uhoh, broke my boot with an optimistic apt full-upgrade. Can't seem to find nvme partition anymore. :-(05:51
- ex--parrot (QUIT: Ping timeout: 265 seconds) (~fincham@user/ex-parrot)05:54
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)06:07
- cow321 (QUIT: Read error: Connection reset by peer) (~deflated8@user/meow/deflated8837)06:07
+ cow321 (~deflated8@user/meow/deflated8837)06:09
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)06:10
+ ex-parrot (~fincham@user/ex-parrot)06:17
+ ohnoitsnoah (~ohnoitsno@2603:8081:3c00:59f3::10a9)06:33
- reform12019 (QUIT: Remote host closed the connection) (~ryan@user/wirelessrpm)06:44
- wakest (QUIT: Ping timeout: 264 seconds) (m-a7d6fe@67.219.99.225)07:14
+ chomwitt (~chomwitt@2a02:85f:9a0a:f200:1ac0:4dff:fedb:a3f1)07:20
joschrwa_: did you get your nvme back somehow? There seems to be another user with what sounds similar above ^07:57
rwa_haven't had the time to dig into this any further due to work stuff08:37
rwa_hopefully spare some time later this day08:38
- voltaire28 (QUIT: Ping timeout: 240 seconds) (~jlafon@28.162.2.93.rev.sfr.net)09:30
+ voltaire28 (~jlafon@28.162.2.93.rev.sfr.net)09:42
- robin (QUIT: Quit: Leaving) (~robin@user/terpri)10:31
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@98.19.128.69)11:48
+ bkeys1 (~Thunderbi@98.19.128.69)11:48
* bkeys1 -> bkeys11:50
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@98.19.128.69)11:54
+ bkeys1 (~Thunderbi@h69.128.19.98.dynamic.ip.windstream.net)11:54
* bkeys1 -> bkeys11:56
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@h69.128.19.98.dynamic.ip.windstream.net)12:01
+ bkeys (~Thunderbi@98.19.128.69)12:01
gsorai have finally found something the rk3588 really struggles with: rust-analyzer on a small to medium project 12:08
theesm1hi everyone o/ what's the lowest supported frequency for the A76 and A55 cores on the pockets rk3588? device trees opp-table and scaling_min_freq info says 1008 and 1200 MHz, some datasheets say 408 MHz 12:13
+ mjw (~mjw@gnu.wildebeest.org)12:19
- ohnoitsnoah (QUIT: Quit: Konversation terminated!) (~ohnoitsno@2603:8081:3c00:59f3::10a9)12:41
- chomwitt (QUIT: Ping timeout: 244 seconds) (~chomwitt@2a02:85f:9a0a:f200:1ac0:4dff:fedb:a3f1)12:47
- jah (QUIT: Ping timeout: 245 seconds) (~jahkosha@user/jahkosha)12:48
+ jahkosha (~jahkosha@user/jahkosha)12:48
* jahkosha -> jah12:49
minutetheesm1: i think one can go lower than 1ghz but there were some mailing list threads about why it wasn't done in practice, iirc it doesn't lower the power consumption but is more unstable12:59
+ paperManu (~paperManu@146.71.9.156)12:59
theesm1minute: thanks for the explaination, makes sense not to go lower than 1GHz if it doesn't lower power consumption (which would've been the only incentive i had to do so)14:05
- paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@146.71.9.156)14:06
rwa_josch minute: reseating the nvme doesn't change anything, there is a difference in modules when booting from sd card (successfull) compared to booting from emmc with / on nvme14:22
rwa_when booting from internal the module "nvme_fabrics" is not listed in /proc/modules14:23
rwa_both images are running kernel 6.17.13 from trixie backports14:23
- pomel0 (QUIT: Ping timeout: 264 seconds) (~pomel0@user/pomel0)14:24
+ FirefoxDeHuk (~FirefoxDe@user/FirefoxDeHuk)14:24
- mjw (QUIT: Ping timeout: 256 seconds) (~mjw@gnu.wildebeest.org)14:25
+ pomel0 (~pomel0@user/pomel0)14:25
rwa_but i doubt that this is required anyway14:27
- FirefoxDeHuk (QUIT: Quit: Client closed) (~FirefoxDe@user/FirefoxDeHuk)14:46
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)14:46
rwa_this is a kernel log of a boot with missing nvme: https://paste.sr.ht/~rwa/777f5b950927f52e690d02dfb0957f2a6a66337714:47
gordon1rwa_: do you have access to nvme tools in your initrd or somewhere else, can you show nvme list?14:48
rwa_gonna check, but when the kernel log says "nvme nvme0: I/O tag 12 (000c) QID 0 timeout, disable controller" i doubt that there will be anything visible14:50
gordon1rwa_: if it does not, can you also try this hack here, does it make nvme appear? https://github.com/gordon-quad/mkinitramfs-ll/blob/master/hooks/2-rescan-nvmes14:51
- qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit)14:54
+ qbit (~qbit@user/qbit)14:56
rwa_rescan detects the nvme controller but it eventuallY fails with the same message in kernel log14:57
gordon1okay, if you do this, what do you see in nvme list?14:57
gordon1which nvme btw?14:58
gordon1wd?14:58
rwa_wd green sn35014:58
gordon1i'm asking about nvme list because i had similar issue when wd nvmes turn themselves into SANDISK POLARIS in their smart15:00
rwa_nvme tools is not available in default busybox15:00
gordon1smartctl maybe then?15:01
gordon1if the device appears in /dev/nvme* so you can call it ofc15:01
rwa_there is no nvme device in /dev15:02
gordon1right, hope you have different issue then, because mine didn't recover after that15:02
gordon1but this rescan script i had in my initrd for a while since rk3588 just didn't register nvme first time occasionally15:03
rwa_the point is that nvme is visible and mountable when the system boots from ssd15:03
rwa_ssd=sd card15:04
gordon1interesting15:04
gordon1are you sure you have exactly the same dtbs?15:05
rwa_yep15:05
rwa_got nvme into the busybox, doesn't anything though15:06
gordon1yeah, so u-boot nvme init does something then?15:06
rwa_+show15:09
rwa_not sure what you mean with "u-boot nvme init"15:12
gordon1i guess u-boot needs to do pci init and nvme discover to be able to boot from it15:15
gordon1it has commands for that, something along the lines pcie scan ; nvme init15:15
rwa_i think it does that, kernel logs show the pci device but fails to initialize the controller15:23
rwa_i should mention that /boot is on emmc15:24
rwa_its only looking for / on nvme15:24
- Ar|stote|is (QUIT: Ping timeout: 264 seconds) (~linx@149.210.3.83)15:36
* Guest149 -> mjw15:40
+ Ar|stote|is (~linx@149.210.3.83)15:40
+ L29Ah (~L29Ah@wikipedia/L29Ah)15:46
+ chomwitt (~chomwitt@2a02:85f:9a0a:f200:1ac0:4dff:fedb:a3f1)15:51
- pomel0 (QUIT: Ping timeout: 264 seconds) (~pomel0@user/pomel0)15:52
+ pomel0 (~pomel0@user/pomel0)15:53
- pomel0 (QUIT: Read error: Connection reset by peer) (~pomel0@user/pomel0)15:58
+ pomel0 (~pomel0@user/pomel0)16:03
- pomel0 (QUIT: Ping timeout: 255 seconds) (~pomel0@user/pomel0)16:08
minutejust ran into a bug again that only i ever encountered/posted to the internet before, 1 year ago https://mntmn.com/reform-irc-logs/2025-01-10.log.html#t22:10:2516:18
minute[ 4826.403236] dma-pl330 fea10000.dma-controller: Reset Channel-5 CS-db89a020 FTC-db89a02016:18
minute[ 4826.403249] dma-pl330 fea10000.dma-controller: pl330_update:1678 Unexpected!16:18
- chomwitt (QUIT: Ping timeout: 260 seconds) (~chomwitt@2a02:85f:9a0a:f200:1ac0:4dff:fedb:a3f1)16:18
minute[ 4826.403450] dma-pl330 fea10000.dma-controller: pl330_submit_req:150016:18
minute[ 4859.890079] dma-pl330 fea10000.dma-controller: Runtime PM usage count underflow!16:18
- bkeys (QUIT: Ping timeout: 245 seconds) (~Thunderbi@98.19.128.69)16:18
gordon1minute: yep, that's what i had, but looks like captan tape solved the issue16:21
gordon1... or 6.18.316:21
gordon1joy of science with multiple variables16:21
gordon1http://0x0.st/P8W4.txt looks almost the same, except Reset Channel message16:22
gordon1ACTION saving his dmesg in a big plastic bag16:24
minutegordon1: heh. 16:28
+ siviq (~siviq@user/siviq)17:04
- elb (QUIT: Remote host closed the connection) (~elb@2600:4041:6682:ea00:e7f3:f2e0:d264:a888)17:40
+ bkeys (~Thunderbi@172.56.65.248)18:15
- gianmarcogg03 (QUIT: Ping timeout: 265 seconds) (~quassel@user/gianmarcogg03)18:26
+ gianmarcogg03_ (~quassel@user/gianmarcogg03)18:26
+ bkeys1 (~Thunderbi@172.56.65.248)18:27
- bkeys (QUIT: Ping timeout: 240 seconds) (~Thunderbi@172.56.65.248)18:28
* bkeys1 -> bkeys18:28
- bkeys (QUIT: Client Quit) (~Thunderbi@172.56.65.248)18:29
+ bkeys (~Thunderbi@172.56.65.248)18:29
amkheya opened an account this morning on the gitlab to make a small pr, would it be okay to get it approved? :)18:31
- bkeys (QUIT: Client Quit) (~Thunderbi@172.56.65.248)18:31
+ bkeys (~Thunderbi@172.56.65.248)18:32
- bkeys (QUIT: Client Quit) (~Thunderbi@172.56.65.248)18:32
+ pomel0 (~pomel0@user/pomel0)18:32
+ bkeys (~Thunderbi@172.56.65.248)18:33
- bkeys (QUIT: Client Quit) (~Thunderbi@172.56.65.248)18:36
+ bkeys (~Thunderbi@172.56.65.248)18:37
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)18:37
- bkeys (QUIT: Client Quit) (~Thunderbi@172.56.65.248)18:38
+ bkeys (~Thunderbi@172.56.65.248)18:38
- bkeys (QUIT: Client Quit) (~Thunderbi@172.56.65.248)18:39
+ bkeys (~Thunderbi@172.56.65.248)18:40
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@172.56.65.248)18:48
+ bkeys1 (~Thunderbi@172.56.65.248)18:48
- voltaire28 (QUIT: Ping timeout: 252 seconds) (~jlafon@28.162.2.93.rev.sfr.net)18:49
* bkeys1 -> bkeys18:50
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@172.56.65.248)18:54
+ bkeys1 (~Thunderbi@172.56.65.248)18:54
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@172.56.65.248)18:56
+ bkeys (~Thunderbi@172.56.65.248)18:56
- bkeys (QUIT: Client Quit) (~Thunderbi@172.56.65.248)18:58
+ bkeys (~Thunderbi@172.56.65.248)18:58
- siviq (QUIT: Quit: Client closed) (~siviq@user/siviq)19:14
- bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@172.56.65.248)19:21
joschso i have good news, bad news and bad news19:29
joschhttps://mister-muffin.de/p/5TFn.jpg19:29
joschgood news: nvme works fine with the most recent system image even after installing the system onto nvme19:29
joschbad news: it's really hard to fit the MNT Pocket Reform wifi/bt extension board into classic Reform19:30
joschbad news: while reconnecting everything, something blew up on my motherboard, looks like D30 (photo above)19:30
+ pomel0 (~pomel0@user/pomel0)19:41
+ mark_ (~mjw@gnu.wildebeest.org)19:48
+ wielaard (~mjw@gnu.wildebeest.org)20:15
- mark_ (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)20:18
gordon1there's definitely a hole in D3020:19
jfredeeeep!20:19
gordon1and potentially it took D29 with it20:19
gordon1not sure if that's residue or a crack20:20
gordon1josch: do i see soot on J13 or is it just lighting?20:21
joschgordon1: probably just light, the connector is okay20:40
josch"looks okay"20:40
joschactually, it should be okay, because the unit is able to run off batteries but it cannot charge them20:41
gordon1yeah, i think it is safe just to replace the diode20:41
joschgordon1: do you think i can do that with a normal soldering iron or would i need to find somebody with better equipment?20:42
gordon1absolutely20:42
gordon1let me check it just quick20:42
gordon1yeah20:42
gordon1it looks big enough20:43
gordon1josch: do you have grandpa's soldering iron for tinning buckets or something more modern with temperature control? 20:43
gordon1latter should be just fine20:44
gordon1josch: the trick is you don't care about the diode survivability' so you just can heat it from the side at the centerline till it can be bulldozed from pads20:44
gordon1just set your temp correctly since this is the way you can life the pads - if you overheat it20:45
- mjw (QUIT: Killed (tantalum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d)20:50
* wielaard -> mjw20:50
+ Guest8632 (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d)20:51
+ bkeys (~Thunderbi@172.56.64.18)20:57
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)21:13
+ pomel0 (~pomel0@user/pomel0)21:13
joschgordon1: s/life/lift/? Do you have a temperature recommendation? No, it's a modern soledering iron but not a particularly thin tip. :)21:20
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@172.56.64.18)21:32
+ bkeys1 (~Thunderbi@172.56.64.18)21:32
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@172.56.64.18)21:35
+ bkeys (~Thunderbi@172.56.64.18)21:35
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@172.56.64.18)21:39
+ bkeys (~Thunderbi@172.56.64.18)21:40
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@172.56.64.18)21:45
+ bkeys1 (~Thunderbi@172.56.64.18)21:45
- bkeys1 (QUIT: Client Quit) (~Thunderbi@172.56.64.18)21:46
+ bkeys (~Thunderbi@172.56.64.18)21:47
- bkeys (QUIT: Client Quit) (~Thunderbi@172.56.64.18)21:48
+ bkeys (~Thunderbi@172.56.64.18)21:48
+ elb (~elb@2600:4041:6682:ea00:2e98:b826:732c:b385)21:48
+ voltaire28 (~jlafon@28.162.2.93.rev.sfr.net)21:54
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@172.56.64.18)21:55
+ bkeys (~Thunderbi@172.56.64.18)21:56
minutejosch: ouch22:00
minutejosch: use 380-400 degrees, big solder blob, so big iron tip is even better22:00
minutejosch: you can use a big solder blob as a hot enveloping liquid to loosen the part and kind of wipe it away22:01
minutejosch: (also use flux)22:01
+ robin (~robin@user/terpri)22:02
minutejosch: also cover U4 legs with kapton tape before maybe, that you don't accidentally get solder on it, this stuff bridges easily and is a bit of a pain to clean up again22:02
minutejosch: that diode prevents backfeeding of power from the power input of U422:03
minute(which is the battery monitor)22:04
minutei added it in some revision after discovering that u4 can backpower stuff22:04
- bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@172.56.64.18)22:05
joschminute: wow, thanks a lot for your comments, highly appreciated! I'll take them to heart <322:08
joschi already found the same diode and it should be here in a few days22:08
gordon1josch: yes, lift, sorry, had to catch the bus22:22
gordon1josch: yes, what minute said22:23
gordon1>i added it in some revision after discovering that u4 can backpower stuff22:23
gordon1i remember once on one of the banana pies i was so puzzled why my usb devices are still powered on even after you cut the power to the board if it is battery powered :)22:24
gordon1saved few pennies on the diode22:24
minutehehe22:25
gordon1josch: if you want to go fancy, you can get one of those chipquik low temp solders for desoldering smd, then you can go lower than 380 without any risk of damaging anything by overheating22:25
gordon1e.g. https://www.ebay.co.uk/itm/19312188202722:27
joschgordon1: i hope you managed to catch your bus! Thank you for making time for me despite being in a rush. :)22:27
gordon1i made my own rose's metal with 98°C, but not RoHS22:28
joschoh that's funny solder22:28
gordon1but i usually use leaded solder anyway22:28
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.3.83)22:28
gordon1which reminds me22:28
gordon1minute: antennas i sent you are non-RoHS, i mean they were non-RoHS even from JLC because i ordered cheapest ones22:29
minutegordon1: ah, good to know!22:29
gordon1lets say they're automotive grade22:30
+ chomwitt (~chomwitt@2a02:85f:9a0a:f200:1ac0:4dff:fedb:a3f1)22:33
+ Ar|stote|is (~linx@149.210.3.83)22:34
- paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)22:55
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)22:56
- paperManu (QUIT: Ping timeout: 260 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)23:03
joschgosh... i really ought to learn how to kicad...23:16
gordon1josch: great first project, imo is a keyboard, or some other button based input device - it is very forgiving on the routing  23:19
+ paperManu (~paperManu@146.71.9.156)23:24
+ paperManu_ (~paperManu@146.71.9.156)23:25
minutei agree with gordon1's assessment here23:49
minutekicad has gottan a lot better and there's tons of tutorials and videos on how to get started!23:49
minutei can say kicad really changed my life :DD23:49
minutekicad 4.x...23:50
gordon1i definitely contributed to me having too many keyboards23:50
gordon1*it23:50
minutehehe23:55
gordon1i don't remember first kicad i used but it felt really as a downgrade from eagle, just my stubborness of using mostly open software prevailed, but yeah, after some version it suddenly got all the cool kid's features like shoving tracks, and differential pair routing, length matching etc 23:57
gordon1https://gitlab.com/kicad/code/kicad/-/issues/1950 future is here!23:59

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