chartreuse | vagrantc, maybe a mod you could do would be adding another LED to the bottom that the LPC or keyboard controls that shows the charge current state | 00:25 |
---|---|---|
- S0rin (QUIT: Ping timeout: 255 seconds) (~S0rin@user/s0rin) | 00:29 | |
+ S0rin (~S0rin@user/s0rin) | 00:29 | |
pandora[m] | maybe even two RGB LEDs (one for each pouch cell on the pocket or one for each side on the big boy) | 00:34 |
- sevan (QUIT: Changing host) (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4) | 00:34 | |
+ sevan (~sevan@user/venture37) | 00:34 | |
pandora[m] | color shows the state of charge | 00:34 |
chartreuse | Or even just a bicolor LED to show charging/charged/powered | 00:49 |
- mtm (QUIT: Ping timeout: 252 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 01:02 | |
vagrantc | i love that the mnt/reform is hackable enough to even consider modding in some LEDs :) | 01:06 |
vagrantc | although i really love to see the percentage and amperage :) | 01:06 |
minute | pocket has a status rgb led on the mobo | 01:15 |
+ murmr____ (sid433686@id-433686.helmsley.irccloud.com) | 01:19 | |
murmr____ | Hi, I tried following the steps for uboot + OBSD, but I can't get to step 4 (black screen on boot, OBSD + DTB file on SD, flash.bin on eMMC). Any ideas on how to troubleshoot? I can still boot from another SD card. | 01:21 |
vagrantc | dropping the need for arm-trusted-firmware for imx8: https://lists.denx.de/pipermail/u-boot/2023-January/503312.html ... will be a talk at fosdem, apparently. | 02:10 |
- eery (QUIT: Quit: leaving) (~eery@172.97.103.152) | 02:45 | |
- Guest1610 (QUIT: Ping timeout: 260 seconds) (~nicolas@220-49-142-46.pool.kielnet.net) | 03:07 | |
+ nsc (~nicolas@240-48-142-46.pool.kielnet.net) | 03:08 | |
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 03:09 | |
* nsc -> Guest8881 | 03:09 | |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 03:50 | |
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 04:03 | |
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 04:04 | |
- ex-parrot (QUIT: Quit: _b) (~fincham@user/ex-parrot) | 04:47 | |
+ ex-parrot (~fincham@user/ex-parrot) | 04:47 | |
josch | Hi, I need some help with figuring out a problem I'm having with my reform for the past couple of weeks. Since suspend doesn't work for me, I have my reform on 24/7. Sometimes (maybe twice per week? i didn't properly document this yet but not reliably reproducible) I would come back to my reform in the morning and its display would be off (no surprise because I have swayidle set to run "output * dpms | 07:02 |
josch | off") but even when moving the mouse it would not come back on. So is this just a failure of the display being off but the rest being alright? I don't think so, because: | 07:02 |
josch | 1) the system is not reachable via ssh and not pingable | 07:02 |
josch | 2) the oled screen shows the system as "On" but when i disconnect the power cord it shows a draw of 0.25A which doesn't make any sense because if i switch my display off manually the power draw is 0.20A -- so something else is happening or stuck? | 07:04 |
josch | 3) i have some hotkeys configured to run swaymsg "output * dpms on" but pressing them does nothing | 07:05 |
josch | since the problem is unreproducible and since the reform is my main machine, i didn't yet test whether the problem can be reproduced with a vanilla rescue system from sd-card | 07:06 |
josch | did anybody ever see this kind of issue? any tips in how to debug it? | 07:06 |
- leonardo (QUIT: Remote host closed the connection) (~leonardo@user/leonardo) | 09:37 | |
+ leonardo (~leonardo@user/leonardo) | 09:37 | |
* Guest8881 -> nsc | 09:45 | |
+ bgs (~bgs@212-85-160-171.dynamic.telemach.net) | 09:59 | |
- jjbliss (QUIT: Remote host closed the connection) (~jjbliss@1464766-static.elnsmiaa.metronetinc.net) | 10:00 | |
+ jjbliss (~jjbliss@1464766-static.elnsmiaa.metronetinc.net) | 10:13 | |
violet | josch: so i dont have a reform but i can give some general tips I would take | 11:08 |
violet | the best option is if you have some way to attach to the serial console (a usb to serial adapter or raspberry pi will do), see https://mntre.com/reform2/handbook/advanced.html which mentions SER1 on the motherboard | 11:09 |
violet | from there, you want to configure your install to send dmesg output to that serial console if it is not already configured that way (this is set via `console=ttyWHATEVER,115200` as a kernel boot arg) | 11:10 |
violet | and then if a kernel error happens you'll have the best chance of actually seeing it because there's no network connection or disk between you and the kernel log, its just direct out from kernel to the serial, which usually lasts long enough to get some information before a panic | 11:11 |
violet | (if it is indeed a kernel panic) | 11:11 |
josch | i considered to send dmesg output to another machine via network but indeed sending it over serial should be more reliable | 11:11 |
josch | that's a good idea, thank you! | 11:11 |
violet | sure thing! | 11:12 |
+ dustfinger (~user@d75-159-228-218.abhsia.telus.net) | 11:36 | |
josch | flowy: you can try out ffmpeg with v4l2 request+drmprime patches by adding this to your /etc/apt/sources.list: | 12:32 |
josch | deb [trusted=yes] https://source.mnt.re/reform/reform-debian-packages/-/jobs/1126/artifacts/raw/repo reform main | 12:33 |
josch | h264 hardware decoding works (with only very few artifacts) in mpv by running it with -vo=dmabuf-wayland --hwdec=drm | 12:33 |
josch | h265 is still completely broken (just errors out) | 12:34 |
josch | and mpv does not draw its gui overlay with -vo=dmabuf-wayland | 12:34 |
josch | so software decoding with mpv is still superior | 12:34 |
josch | but if you want to try yourself, you now have a repo with the patched packages in it :) | 12:34 |
- tarxvf (QUIT: Ping timeout: 260 seconds) (~tarxvf@mail.tarxvf.tech) | 13:00 | |
+ tarxvf (~tarxvf@mail.tarxvf.tech) | 13:00 | |
- violet (QUIT: Ping timeout: 260 seconds) (~vi@user/violet) | 13:01 | |
+ violet (~vi@user/violet) | 13:03 | |
- mtm (QUIT: Ping timeout: 252 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 13:03 | |
* wielaard -> mjw | 13:45 | |
minute | josch: is the backlight still on? | 13:57 |
josch | minute: nope | 13:57 |
josch | the backlight was switched off by my swayidle command and nothing switched it on again | 13:58 |
minute | josch: ok, would you be ok to disable the dpms thing for a while and just turn the brightness down to 0 when you don't use the device? this way we could narrow it down to dpms | 13:59 |
josch | sure thing! | 13:59 |
josch | but if it was just about dpms, then i would still be able to reach the unit via ssh even if the display doesn't come on again | 13:59 |
minute | yeah, i mean there could be a kernel lockup in there related to dpms functionality | 14:00 |
minute | something power mgmt related perhaps | 14:00 |
minute | but yeah, externally monitoring your dmesg is also a good idea, to see if something suspicious happens | 14:00 |
minute | that said, i do have encountered 2 or 3 system lockups that are GPU or OOM related, but then the display is not off | 14:01 |
minute | btw my work PC behaves like your reform... every day | 14:01 |
josch | for me this also only ever happened at night so far | 14:01 |
minute | i come to the office and it is locked up and i have to hard reset it | 14:01 |
josch | never happened while i was actively working with it | 14:01 |
minute | every morning basically | 14:01 |
josch | at least for you it's reproducible XD | 14:01 |
minute | lol yeah | 14:02 |
minute | but no idea what the cause is, intel mysteries | 14:02 |
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 15:09 | |
sigrid | this happens to my ryzen laptop if I put it to sleep | 16:48 |
sigrid | did not happen before linux 6.x :( | 16:48 |
minute | ha. maybe a linux 6.x problem after all | 16:57 |
flowy | guess i'm lucky. i've had my reform lock up maybe once every six months. i regularly have uptime for weeks, until a moment of forgetfulness where i let the battery drain | 17:00 |
flowy | current uptime of 5 days with 6.1.0-reform2-arm64, not sure how long i've been running 6.x | 17:01 |
flowy | i never use suspend, i always just put the display brightness down when i leave the machine | 17:01 |
sigrid | eh, why not blank it altogether? | 17:03 |
sigrid | mine blanks in 5 minutes | 17:04 |
flowy | no reason! the brightness hotkeys were mapped with the reform sysimage, i don't think swayidle or some key to turn off the display came with | 17:05 |
flowy | just anecdata | 17:06 |
+ mntrkx7 (~root@p509936c9.dip0.t-ipconnect.de) | 17:39 | |
mntrkx7 | hi from rkx7/risc-v with kintex-7 160t | 17:39 |
- mntrkx7 (QUIT: Ping timeout: 246 seconds) (~root@p509936c9.dip0.t-ipconnect.de) | 17:45 | |
+ gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es) | 17:47 | |
- gnou_liber (QUIT: Quit: Leaving) (~gnou_libe@223.pool85-50-3.static.orange.es) | 17:53 | |
Boostisbetter | minute, you are a super starr, keep up the great work. And uh... send me a Pocket Reform when you got a chance. Hahahaha+ | 18:02 |
minute | hehe | 18:21 |
josch | yes, it could be a linux 6.x problem -- i didn't record the timing but i upgraded to 6.1 in the beginning of january... | 18:38 |
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:40) | 19:21 | |
- mjw (QUIT: Killed (NickServ (GHOST command used by markw!~wielaard@gnu.wildebeest.org))) (~mjw_@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 19:28 | |
+ wielaard (~mjw_@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 19:28 | |
josch | flowy: so you use "brightnessctl set 0" and not "swaymsg output * dpms off"? | 19:30 |
josch | sigrid: which method of "blanking" the screen did you mean in your method? | 19:30 |
josch | *in your message | 19:30 |
sigrid | "echo blanktime 5 > /dev/mousectl" :) | 19:31 |
sigrid | guess it's not very helpful, because it's 9front | 19:32 |
josch | ah :) | 19:41 |
josch | and if this is a linux bug then obviously you don't see it XD | 19:41 |
minute | we have a reform here that is up for 27 days and runs linux 6.0.0 | 19:46 |
josch | i'd suspect 6.1 because i had 6.0 running in december and didn't have the problem back then | 19:47 |
josch | i still have a 6.0 kernel installed that i can switch to using the u-boot boot menu now -- i can try running 6.0 for a while as well and see what happens :) | 19:48 |
minute | josch: cool, i wonder how that goes! | 20:07 |
- bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net) | 20:42 | |
- ec0 (QUIT: Ping timeout: 268 seconds) (~ec0@vps-446f4f39.vps.ovh.ca) | 20:50 | |
+ ec0 (~ec0@vps-446f4f39.vps.ovh.ca) | 20:50 | |
flowy | josch: yeah basically. i just use the default hot keys | 20:50 |
flowy | which do that | 20:51 |
josch | flowy: you mean mod+f1 and mod+f2? | 21:38 |
sigrid | speaking of which, with the latest kbd fw hyper+f1 and hyper+f2 give proper brightness down/up events out of the box | 21:41 |
sigrid | in addition to the rest of media keys, that is | 21:41 |
josch | i'm still at a loss what i want to use the hyper key for... the super and ctrl keys already give me three different actions per F-key -- i haven't found myself needing more than that yet | 21:44 |
minute | in the future, hyper+cursors will do home/end/pgup/pgdn, for example | 22:12 |
minute | and on pocket there are no f-keys, so hyper+numbers = f-keys | 22:12 |
+ cwebber (~user@user/cwebber) | 22:25 | |
Boostisbetter | The pocket reform is going to be awesome on so many levels! | 22:29 |
josch | has anybody been upgrading to Debian unstable yesterday or today and can confirm that somehow video output hangs after a few seconds -- even in the browser? | 23:11 |
minute | josch: maybe an audio issue? | 23:35 |
minute | josch: btw do you use pipewire and wireplumber and pipewire-pulse? | 23:35 |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40) | 23:55 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!