Post B9Yi0g7nhyLTBlI1Ts by mntmn@mastodon.social
(DIR) More posts by mntmn@mastodon.social
(DIR) Post #B9WxMWXx8jiJqmtDsm by mntmn@mastodon.social
0 likes, 0 repeats
PSA I've updated the instructions for MNT Pocket Reform kernel+firmware udgrades in a consolidated post including the 2 most important recovery options. Please tell me if something is wrong or if some wording should be improved for clarity: https://community.mnt.re/t/important-note-about-the-new-mnt-pocket-reform-kernel-and-firmware-updates-20260819-updated/4534
(DIR) Post #B9WzbgyspLrWSpqYj2 by cararemixed@mastodon.social
0 likes, 0 repeats
@mntmn reading through. I noticed this seems to be cut off for me:> You updated the system controller and keyboard firmware to 20260819 (you can verify this by pressingOtherwise it seems to be clear to me.
(DIR) Post #B9XHZuOdmCBefQC4Dg by mewe@todon.eu
0 likes, 0 repeats
@mntmn got a failed to detach: failed to wait for detach replug: device 377eb704f59a32dc0c615859a9e7bb66246a732d did not come backnow the battery charging aint working anymoreedit rk shipset, new batteryboard, crowdsupply version
(DIR) Post #B9XK0ybESPN9Qi7NAm by mntmn@mastodon.social
0 likes, 0 repeats
@mewe ok, can you leave it in that state (don't turn off!)? can you show what you see on the little OLED when you press hyper+enter and then S for system status?
(DIR) Post #B9XLDQMHB09gx2cbiq by mewe@todon.eu
0 likes, 0 repeats
@mntmn Too late wated to safe power cause it wasn't loading anymore, but the oled was partly unresponsible in that state I remember... now it says nothing to update, but no charging and am down to 6%
(DIR) Post #B9XWVdAdNX5VOc3oJM by mntmn@mastodon.social
0 likes, 0 repeats
@mewe ok thanks, so the keyboard firmware was updated, but the system controller fw wasn't updated yet (says version 20251118). can you try again with "fwupdmgr update"? if that doesn't work, please show me the output of "lsusb"
(DIR) Post #B9YTfjZ8LorFQCbcaO by mewe@todon.eu
0 likes, 0 repeats
@mntmn good morning, still the same, sorry and thx!Perform operation? [Y|n]: yRestarting device… ▕⣤ ▏failed to detach: failed to wait for detach replug: device 377eb704f59a32dc0c615859a9e7bb66246a732d did not come backXXXX@XXXX:~$ sudo lsusbBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port HubBus 002 Device 003: ID 1209:6d06 Generic Pocket Reform Input 2.0Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubBus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubBus 004 Device 002: ID 8087:0032 Intel Corp. AX210 BluetoothBus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 005 Device 003: ID 2e8a:0003 Raspberry Pi RP2 BootBus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubBus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubBus 008 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
(DIR) Post #B9Yi0g7nhyLTBlI1Ts by mntmn@mastodon.social
0 likes, 0 repeats
@mewe ok, very strange behavior from fwupd there. but we can see in the lsusb output that the rp2040 goes into bootsel mode where it can be flashed: "Raspberry Pi RP2 Boot". please download https://source.mnt.re/reform/pocket-reform/-/jobs/23936/artifacts/raw/pocket-reform-sysctl-fw/build/sysctl.uf2and then if you are in this state again, do "cd Downloads", then "sudo picotool load sysctl.uf2" and then "sudo picotool reboot".
(DIR) Post #B9Z2gv8yFzCD0yG024 by mewe@todon.eu
0 likes, 0 repeats
@mntmn THX! It worked fine....as often a but follows, sorry: the keyboard backlight stays on after shutdown, I need to use the 0 in the oled menu, in this state pressing 1 for powering up again seems to be ignored/has no vissible effect...And I got display flickering on dark grey best to see...KDE and gnome are stuck by displaying battery 6% permantly, saying not charging, the oled works fine and charging also works, so it is good usable
(DIR) Post #B9ZGRw0QATt2he0RlI by mntmn@mastodon.social
0 likes, 0 repeats
@mewe ok the 6% and not shutting down properly sounds like mnt-sc driver is not communicating with the firmware. can you confirm that the fw is updated now (on oled screen -> system status), and do you have the latest linux-image-mnt-reform-arm64 and reform-tools apt packages installed?
(DIR) Post #B9aiGQgKvOj1SHhhM8 by mewe@todon.eu
0 likes, 0 repeats
@mntmn oled says correct 20260819 - both :-Dto be shure run the apt from your instructions again:reform-tools is already the newest version (1.88-1).linux-image-mnt-reform-arm64 is already the newest version (7.0.10-1+reform20260602T222813Z).hyfetch-partly says:OS: Debian GNU/Linux forky/sid (forky) aarch64 Host: MNT Pocket Reform with RCORE RK3588 Module Kernel: 7.0.10-mnt-reform-arm64
(DIR) Post #B9bnqzjaltr7WSRRIG by mntmn@mastodon.social
0 likes, 0 repeats
@mewe ok so the kernel you have is outdated (linux-image-mnt-reform-arm64). the current version is 7.1.8, but you have 7.0.10 from june. did you do a "sudo apt update" before? does that give you any errors?but the firmwares look good. they're just incompatible with that old kernel.are you using the official MNT system (debian unstable)? or debian stable?
(DIR) Post #B9dOjMY1xUH7QHDYWG by mewe@todon.eu
0 likes, 0 repeats
@mntmn Ups my "fault" forgot to change all back after experimenting, THX for pointing out and the fast helping, now all seems fine; THX a lot