2026-06-21.log

- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.3.59)01:00
+ Ar|stote|is (~linx@149.210.3.59)01:00
- cow321 (QUIT: Ping timeout: 256 seconds) (~deflated8@user/meow/deflated8837)01:48
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)03:03
+ cow321 (~deflated8@user/meow/deflated8837)03:32
- a3f (QUIT: Ping timeout: 252 seconds) (~a.fatoum@flummi.grey.stw.pengutronix.de)03:33
+ a3f (~a.fatoum@flummi.grey.stw.pengutronix.de)03:37
- paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@173.206.172.163)03:44
elbugh, 76% battery and won't boot03:46
elbit's rapidly getting to the point where I basically have to be plugged in to boot :-(03:46
- 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
- digitalrane (QUIT: Ping timeout: 245 seconds) (~digitalra@user/digitalrane)04:23
+ digitalrane (~digitalra@user/digitalrane)04:33
+ AshCurry_ (~AshCurry@user/AshCurry)06:30
- AshCurry (QUIT: Ping timeout: 252 seconds) (~AshCurry@user/AshCurry)06:30
* AshCurry_ -> AshCurry06:30
- exark (QUIT: Ping timeout: 258 seconds) (~exark@user/exark)07:28
joschminute: i vaguely remember that in the more recent past you said that you had copies of the original pages with images like https://web.archive.org/web/20191207012651/https://mntre.com/reform/reform-beta-1.html somewhere public? Is that still the case?07:58
+ wakest (m-a7d6fe@67.219.99.225)09:36
cararemixedI get this issue on boot where it refuses to allow keyboard input for my password. No idea why it gets stuck. Resets of the controller doesn't help. https://usercontent.irccloud-cdn.com/file/ASWORdIG/1782034767.JPG11:40
cararemixedThe keyboard itself works in that I can use the menu, control backlight, etc. Potentially loose cables? I tried to make sure things were snug.11:42
cararemixedI think the cable must have an issue that causes it to short out.11:43
joschcararemixed: this happens/happened to me sometimes. Moving the display to a different position sometimes helps but then I have to open it and fix the jst plug at the keyboard.11:55
cararemixedI have adjusted it recently to ensure it was well seated. Perhaps it's getting taught and pulled out?11:56
cararemixedI'm without tools to check at the moment but I'll see what I can do.11:56
joschyes, opening and closing the display pulls the cable in my case11:57
cararemixedI think I'll hotglue the cable to part of the case to see if I can relieve the stress on the connector.11:57
+ mjw (~mjw@gnu.wildebeest.org)12:12
- murphnj (QUIT: Ping timeout: 245 seconds) (~murphnj@user/murphnj)12:46
+ murphnj (~murphnj@user/murphnj)12:46
+ paperManu (~paperManu@173.206.172.163)13:15
+ aelius_ (~aelius@user/aelius)13:38
- aelius (QUIT: Ping timeout: 265 seconds) (~aelius@user/aelius)13:40
* aelius_ -> aelius13:40
MartiniMoeif I would like to try barebox with NixOS and it would not work, what is the way to flash u-boot again from the stock debian?14:05
minutejosch: uhm yeah that page should still be up, one moment14:05
minuteMartiniMoe: sudo reform-flash-bootloader emmc i think (check the help)14:06
MartiniMoeminute: okay that sounds easy enough :D might try barebox later then14:06
joschMartiniMoe: i flashed barebox using reform-flash-bootloader yesterday, one sec...14:07
joschMartiniMoe: sudo reform-flash-bootloader --image barebox-mnt-pocket-reform-rk3588.img sd14:08
minutecararemixed: in the failure case, is there no reaction on screen (kernel messages) if you choose "reset USB" in the keyboard oled menu? then likely a hardware/cable issue. do you already have keyboard 2.0 (AKA keyboard 1.5)?14:08
joscherrr14:08
joschMartiniMoe: remove the --image option :)14:08
joschreform-flash-bootloader emmc14:08
josch(sorry for the confusion)14:08
- robin (QUIT: Quit: Leaving) (~robin@user/terpri)14:08
minutejosch: https://mntre.com/media/reform_md/reform-historic/reform-beta-1.html14:09
minutejosch: also https://mntre.com/media/reform_md/reform-1-handbook.pdf14:09
minutenext summer is 10 years of mnt reform :0 how's that possible14:10
cararemixedminute: Yes. I think its a cable issue but it seems to recur even after reseating so I will try securing the cable. Puzzling enough that I was curious if the cables themselves have issues but I will see if I can make the connection more reliable.14:10
joschminute: my IRC-search-foo was too weak -- thank you for helping!14:10
josch(forwarding that link to the forum now)14:10
minutecararemixed: the cable could totally have a crimping issue14:10
cararemixedAlso this is the older keyboard but I have a 2.0 on order.14:10
joschreform-historic/reform-beta-1.html is so good :)14:11
cararemixedFirmware is rather recent but on the 2040 chip variant14:11
minutecararemixed: maybe in the state where it works, try hotgluing the end of the connector/cable interface (where the little crimped ends are) on both sides...14:11
minuteit could be that one wire is not properly crimped or got loose14:12
cararemixedYes though I do want to be able to swap the module.14:12
minuteyeah i mean only on the cable14:12
minutelike, the wires are individually plugged into the plastic end of the cable14:12
cararemixedWhen that order ships. oh right14:12
minutebut thinking about it, it might be tricky, not to get any glue in the front14:13
minuteand thereby not being able to plug it in/make contact... 14:13
minutejosch: the links are on this page in the "archive" section https://mntre.com/media/reform_md/2020-05-08-the-much-more-personal-computer.html14:14
joschminute: haha you answered my next question before i could type it XD thank you!14:15
Zabacararemixed: if you have a multimeter you can check for continuity berween the ends of the cable’s wires while wiggling them around 14:20
minuteZaba: yeah in my experience that can work but can also be hard to do with all the moving parts :D14:23
minuteoh right i wanted to look into cable testers14:24
Zabait helps to have alligator clips for multimeter probes yeah14:28
Zabaor any other way to fix things in place 14:28
Zabaeither way you do not really want to continue using a potentially faulty cable even in a state where it “appears” to work because it can still induce less obvious faults 14:31
minuteyeah one needs a breakout ideally14:44
+ jjbliss (jjbliss@infinity.garden)15:09
+ b00 (~b0@user/b0)15:38
- b0 (QUIT: Quit: Ping timeout (120 seconds)) (~b0@user/b0)15:38
* b00 -> b015:38
+ DFP (~DFP@109.72.102.233)15:59
- spew (QUIT: Quit: nyaa~) (~spew@user/spew)16:04
joschminute: this post might need your expert input: https://community.mnt.re/t/watchdog-shutdowns-on-battery/4437/16:21
- xktr (QUIT: Ping timeout: 246 seconds) (~xktr@user/xktr)17:07
+ xktr (~xktr@user/xktr)17:08
lidstah62 games, added RoadWarden : https://arkham.lidstah.info/reform-games.html :)19:23
minutejosch: right. pretty cool post. i'll get to it as soon as i'm back to work :D19:32
minutelidstah: cool!19:33
+ siviq (~siviq@user/siviq)20:16
- siviq (QUIT: Quit: Client closed) (~siviq@user/siviq)20:33
lidstahminute: yup, it's a nice rpg/textual adventure with some clean pixel graphics. It uses renpy, so it should even work natively - but I need to read a bit of pygame/renpy doc.20:35
MartiniMoewill the current config of barebox also first try to boot off the micro sd and after that try to boot off the emmc? So, will this behaviour be the same as with u-boot?22:02
MartiniMoe(ok if I understand this right it will always first try to boot off the emmc, but it can be reconfigured from within barebox)22:10
joschMartiniMoe: it *should* prefer emmc and i think i saw it do exactly that -- do you experience something different?22:11
MartiniMoejosch: no, its just that I rely on u-boots behaviour to first try to boot from sd :D22:12
MartiniMoejosch: but it seems I can easily reconfigure it in barebox, so I will try flashing that now :)22:12
joschand you can also manually select something on each boot22:15
MartiniMoejosch: yes, however it does not seem to like the extlinux.conf from my NixOS :(22:15
MartiniMoealso the screen is weirdly grey except for lines displaying something and weirdly fades to black for lines that get updated :D22:16
joschMartiniMoe: if you encounter problems with your extlinux.conf contact a3f who has been super supportive in the past with issue reports like this :)22:17
joschMartiniMoe: display v1 or v2?22:17
MartiniMoejosch: v222:18
MartiniMoejosch: where / how to contact a3f? :D22:18
joschMartiniMoe: here or in #barebox22:19
MartiniMoejosch: ah, nice, thanks, maybe they will react :D22:20
joschMartiniMoe: do you have any error indicating why your extlinux.conf does not work?22:23
MartiniMoejosch: not yet. its just not listed as a bootable device22:25
MartiniMoejosch: I'm now trying to get into the barebox shell to debug a little :)22:26
MartiniMoewith `global.loglevel=7` when I try to boot the partition directly it displays `WARNING: extlinux: Unhandled key: MENU` and same for key `LINUX`22:33
joschMartiniMoe: i can confirm that barebox ignores my installation on sd-card with an extlinux.conf unless i add the /boot/loader entries back22:55
MartiniMoeyeah, I'll try to get some /boot/loader/entries files with my nixos :/22:55
joschMartiniMoe: they are also easy to write by hand until you auto-generate them22:56
minuteMartiniMoe: the display issue is a known issue23:34
minuteMartiniMoe: it's because of a missing reset pulse on warm reboot... it shouldn't happen when you power cycle23:35

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