2025-01-11.log

+ savasten (~savasten@64.39.201.193)00:12
savastengood day all. I ran into an issue after updating the System Controller on the Pocket Reform. Unit seems to boot unfortunately no display output. Hdmi Gives a uboot message for just a second and then display is lost. Any recommendations on a fix or direction to reverting the system controller firmware. running the i.MX8MPlus off of emmc.00:20
+ Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66)00:25
- Gooberpatrol66 (QUIT: Ping timeout: 246 seconds) (~Gooberpat@user/gooberpatrol66)00:26
joschsavasten: that's this issue, no? https://community.mnt.re/t/unable-to-charge/292900:28
savastenYes00:30
chdid you upgrade anything else too?00:38
ch> ERROR: The RP2040 device returned an error: rebooting00:41
cheh, whats that00:41
savastenThat is the error after falshing00:42
chminute: the kbd update script is missing a '1' in the magic string, please see if you want to take https://source.mnt.re/reform/pocket-reform/-/merge_requests/3000:46
chsavasten: so if you can see uboot output appearing, then the sysctl will have come up. in that case i'd try an older kernel (probably via an older system image)00:48
- savasten (QUIT: Ping timeout: 240 seconds) (~savasten@64.39.201.193)00:57
- chomwitt (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:587:7a09:1500:1ac0:4dff:fedb:a3f1)00:57
- mtm (QUIT: Ping timeout: 246 seconds) (~textual@47.202.75.129)01:04
+ mtm (~textual@47.202.75.129)01:05
+ savasten (~savasten@64.39.201.193)01:08
savastenI have tried the current system image I am not sure how old that one is. I will try external again with that image.01:10
savastenThank you for the suggestion.01:10
+ colinsane (~colinunin@97-126-3-249.tukw.qwest.net)01:19
+ savasten80 (~savasten@64.39.201.193)01:23
- savasten (QUIT: Ping timeout: 240 seconds) (~savasten@64.39.201.193)01:24
chi think there's a new one every day or so?01:29
- colinsane (QUIT: Quit: bye) (~colinunin@97-126-3-249.tukw.qwest.net)01:37
+ colinsane (~colinunin@97-126-3-249.tukw.qwest.net)01:41
- savasten80 (QUIT: Ping timeout: 240 seconds) (~savasten@64.39.201.193)01:41
+ savasten (~savasten@64.39.201.193)01:51
- colinsane (QUIT: Ping timeout: 244 seconds) (~colinunin@97-126-3-249.tukw.qwest.net)01:57
+ colinsane (~colinunin@97-113-68-157.tukw.qwest.net)02:12
- jacqueline (QUIT: Ping timeout: 244 seconds) (~jacquelin@user/jacqueline)03:06
+ jacqueline (~jacquelin@user/jacqueline)03:06
- mjw (QUIT: Quit: Leaving) (~mjw@gnu.wildebeest.org)03:19
- simba (QUIT: Ping timeout: 248 seconds) (~simba@ppp-185-145-220-148.pool13.filstalnetz.de)03:26
- nsc (QUIT: Ping timeout: 272 seconds) (~nicolas@i5C74DC6E.versanet.de)04:02
+ nsc (~nicolas@i5C74DE84.versanet.de)04:04
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)04:58
- savasten (QUIT: Quit: Client closed) (~savasten@64.39.201.193)05:05
- colinsane (QUIT: Read error: Connection reset by peer) (~colinunin@97-113-68-157.tukw.qwest.net)05:14
+ colinsane (~colinunin@97-126-4-196.tukw.qwest.net)05:33
- aloo_shu (QUIT: Ping timeout: 246 seconds) (~aloo_shu@90.166.98.45)06:42
+ aloo_shu (~aloo_shu@85.51.16.136)06:44
- ptrc (QUIT: Remote host closed the connection) (~ptrc@ptrc.gay)08:49
+ ptrc (~ptrc@ptrc.gay)08:50
+ gustav28 (~gustav@c-78-82-52-175.bbcust.telenor.se)09:20
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.16.136)09:53
+ aloo_shu (~aloo_shu@85.51.17.201)09:56
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:04
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:04
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.17.201)10:50
+ aloo_shu (~aloo_shu@85.51.18.235)11:13
joschch: no, the system image is only regenerated when somebody presses the button in gitlab11:20
joschthe reform-debian-packages repo is scheduled to rebuild once per week11:21
joschI also just successfully tested reform-tools 1.65 on imx8mq -- does anybody else want to put stuff into this release?11:21
joschplomlompom: what's the state of https://source.mnt.re/reform/reform-tools/-/merge_requests/107 -- is it ready from your perspective?11:22
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.18.235)11:27
+ aloo_shu (~aloo_shu@85.51.18.57)11:30
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.18.57)12:18
+ aloo_shu (~aloo_shu@85.51.18.109)12:21
- mtm (QUIT: Ping timeout: 244 seconds) (~textual@47.202.75.129)13:02
+ mtm (~textual@47.202.75.129)13:05
+ mjw (~mjw@gnu.wildebeest.org)13:45
joschi did more tests and added a few more fixes to https://source.mnt.re/reform/reform-tools/-/merge_requests/10813:46
joschunless anybody speaking up, i plan to release this tonight13:46
josch(or earlier if minute tells me to just go ahead and do it :D)13:46
chexecute_after_dh_install ugh :P14:46
chbut i guess it works14:46
chi wonder if a Conflicts: fwupd (<< 2.0.3-1~)  would make sense to force upgrades of fwupd14:47
ch(to a version that can update, even if it needs the workaround)14:47
- aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@85.51.18.109)15:07
+ aloo_shu (~aloo_shu@85.51.17.1)15:09
minutejosch: looks like a great release to me!15:16
sevanhello, I veered off into powerpc land recently and not looked at anything else, but I'll pick up the ball on the LPC / v4 keyboard stuff tonight again. The cable to connect to the header on the motherboard turned sometime back.15:44
sevanminute: can MR 76 to 78 land in the reform repo (for reform2-keyboard4-fw)15:46
- aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@85.51.17.1)15:56
joschch: do you have a suggestion that is more pleasing to the eye?15:57
+ aloo_shu (~aloo_shu@85.51.18.52)15:58
chjosch: what was wrong with a normal file + add it to .install?16:00
joschch: i'm reading d/rules much more often than an .install file. Putting it into rules will make me annoyed every time i'm reading it and thus will make me periodically check whether this is still needed.16:01
chok, if that was the goal (:16:02
joschit's only a temporary hack, no?16:05
- jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)16:14
chyeah16:21
minutesevan: can you remind me to check on monday? now off for the weekend16:31
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)16:38
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)16:38
* bkeys1 -> bkeys16:41
sevanminute: derp, weekend, right. (sorry) :) yep, no problem.16:51
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)17:49
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)17:49
* bkeys1 -> bkeys17:52
BoostisBetterminute: had the pocket using posuspend and came and saw that the oled was saying that the keyboard had been reset by the watchdog. The kb worked the whole time, and I have used psuspend about 4 times so far. Good stuff so far. If the reset thing is part of the changes to the firmware that was genuis. Thanks!17:57
minuteBoostisBetter: yes it is! so maybe the kbd firmware update didn't work for you before?18:00
BoostisBetterI flashed it on there the first a couple of weeks ago, and it did have a crash right then, but that was with an older version of psuspend that was using leds. Now I am using a new version of psuspend and I have the led stuff disabled and instead of using the display hook in it, am just using swayidle. Seems to work much better. I will let you know though if I have a kb crash.18:03
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)18:08
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)18:08
* bkeys1 -> bkeys18:11
chidle thought: does the usb hub become unhappy when the soc suspends?18:11
minutech: it's possible. also, we have to make sure the hub is properly reset in uboot on all the platforms18:12
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)18:13
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)18:13
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)18:17
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)18:18
- bkeys (QUIT: Ping timeout: 244 seconds) (~Thunderbi@38-146-94-247.echocast.zone)18:29
+ bkeys (~Thunderbi@173.16.175.75)18:34
+ mark_ (~mjw@gnu.wildebeest.org)18:57
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)18:59
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@173.16.175.75)19:06
+ bkeys (~Thunderbi@173.16.175.75)19:22
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.18.52)19:27
+ aloo_shu (~aloo_shu@90.166.99.151)19:29
- bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@173.16.175.75)19:59
- aloo_shu (QUIT: Ping timeout: 245 seconds) (~aloo_shu@90.166.99.151)20:01
+ aloo_shu (~aloo_shu@85.51.18.196)20:03
+ savasten (~savasten@64.39.201.193)20:19
savastenGood day all.20:26
savastenI am back to try and find a solution to the blank display after the latest system controller update. I am curious should the "Disp_reset_1v8"  supposed to be held at 1.7ish Volts with power on? I am thinking that GPIO2 is held on/high on the system controller causing the display to stay off.20:31
savastenAm I way off in this direction?20:32
BoostisBettersavasten: have we already ruled out that your display is not defective?20:34
savastenIt was perfect prior to the update and was another users. It is possible but unlikely.20:36
chha20:43
ch'probably not'20:45
minutesavasten: reset is active low20:45
chbut i think the old fw also did this20:45
minutesavasten: are you positive it's the sysctl fw? could you go back to an older version?20:46
minutei think it's more likely kernel related, for example the thing we changed at 38c3 to get your display back up after reboot ch20:47
chwhat was the story with the PIN_DISP_EN? why can it now always be PWM even for disp fw1?20:47
chi think savasten's display turns on when sway starts? 20:48
chso it sounds like the "inverse" of my display :)20:48
minuteah let me see if i did a bad thing20:49
minute80% brightness max comes to mind20:49
chyes20:49
chthat seems like maybe a problem20:49
minuteah that was dumb20:50
savastench The display never turns on or flickers. External display works fine after Sway20:52
chah external20:52
minutesavasten: sorry i recently introduced a bug. this should fix it https://source.mnt.re/reform/pocket-reform/-/commit/a98e2bd326a7696c282757d4fc87b3f59974cef720:54
minute(once it's done building)20:55
minutesavasten: if you go back to this one, it should probably also be ok? https://source.mnt.re/reform/pocket-reform/-/jobs/7315/artifacts/browse/pocket-reform-sysctl-fw/build/20:56
savastenSounds good, Thank you, I am amazed everyday by this community.21:04
joschand it's even saturday o021:07
- savasten (QUIT: Ping timeout: 240 seconds) (~savasten@64.39.201.193)21:21
- digitalrane (QUIT: Read error: Connection reset by peer) (~rane@user/digitalrane)21:25
joschreform-tools 1.65 is tagged and merged21:27
joschturns out this was a bit of a bigger release: https://source.mnt.re/reform/reform-tools/-/merge_requests/10821:27
+ digitalrane (~rane@user/digitalrane)22:14
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-175.bbcust.telenor.se)22:15
BoostisBetterminute: it is super awesome but the kb has gone almost a full day without any kind of resets or crashes. 22:16
BoostisBetterI think we may be cooking with grease now. (sorry just an expression)22:16
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)23:09
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.18.196)23:50
+ aloo_shu (~aloo_shu@85.51.18.252)23:52

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