Post B9Og7lWPvYYPSxrvcW by mntmn@mastodon.social
 (DIR) More posts by mntmn@mastodon.social
 (DIR) Post #B9OaX3HGRxt035SIbo by mntmn@mastodon.social
       0 likes, 1 repeats
       
       so... did anyone have success installing the new firmware version + kernel combination on MNT Pocket Reform? i know two instances where it went badly, both were on the unofficial Debian stable/trixie image. would be good to hear if it went smoothly for you and on which hardware.
       
 (DIR) Post #B9OaisXwApl6F3tSrY by johl@mastodon.xyz
       0 likes, 0 repeats
       
       @mntmn It was so smoothly and boringly successful that I became paranoid about missing something for a moment.
       
 (DIR) Post #B9OauC0CB5stlhVQjQ by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @johl omg nice. rk3588 iirc.
       
 (DIR) Post #B9Ob1Bag6fLeWEuBDE by cararemixed@mastodon.social
       0 likes, 0 repeats
       
       @mntmn My own initial issue was some amount of caching seemed to give old firmware until many hours after release (refresh --force didn't see the new firmware and I was dumb and didnt notice it rolled me back from my own self-compiled firmware to 2025 releases). The following morning I used a rescue SD, repeated refresh, and it saw the 2026 firmware and installation worked. Booting was otherwise completely broken (couldn't get to an interactive tty).
       
 (DIR) Post #B9ObDccnQ69nq4pG3U by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @cararemixed hmm, damn about the cache. and sounds like i should look into what fails when booting the new kernel(s) with old firmware.
       
 (DIR) Post #B9Obo220R6OP3qylCS by cararemixed@mastodon.social
       0 likes, 0 repeats
       
       @mntmn failsafe operation to get to a shell would be a big win, though a boot menu with barebox might be the way to go.
       
 (DIR) Post #B9Oc0zTlEkiquT8lRg by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @cararemixed yeah, we solved this with barebox, although only on rk3588. imx8mp u-boot shows some logo on hdmi, it seems like it shouldn't be too hard to get a console/menu there as well. no dice on a311d though
       
 (DIR) Post #B9Oc8NiTWOd06jXyy0 by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @mtjm great to hear, thanks!
       
 (DIR) Post #B9OcJfDUnPm7ZMR7rc by cararemixed@mastodon.social
       0 likes, 0 repeats
       
       @mntmn its on my list of things to switch to so I can dual boot openbsd. For now I'm still rolling with uboot.
       
 (DIR) Post #B9Ocw6XPfGdzJD5BFg by nikola@mathstodon.xyz
       0 likes, 0 repeats
       
       @mntmn I `apt full-upgrade`d mine yesterday afternoon (i.MX8MP, standard out-of-the-box Debian unstable image), and I did notice quite an increase in errors during boot. Most notably, the battery seems to have stopped reporting its status to the kernel. It seemed to work well otherwise.Haven't had too much time to look into it & debug, but happy to provide any details if useful.
       
 (DIR) Post #B9Oe9nECM4lxQdBbM0 by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @deshipu ok, the efi stuff is normal, basically a bug in fwupd that always assumes efi must be there. but that's harmless.the 0% battery is strange if everything else works. feel free to reach out to me once you have the energy to look into this (no rush).
       
 (DIR) Post #B9OeIpIq0hE4TBfDKi by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @nikola it's good to know that booting on imx8mp still works, even if it sounds like you didn't update the firmware yet. we'll have to add an automatic hint to the system for this, as not everybody is checking community.mnt.re.
       
 (DIR) Post #B9OfApCCclF1m8JBoG by rick@a.n0id.space
       0 likes, 0 repeats
       
       @mntmn worked perfectly well, out of the box ^^rk on pocket ^^
       
 (DIR) Post #B9OfmwK2ZoZ2sj9Jaq by nikola@mathstodon.xyz
       0 likes, 0 repeats
       
       @mntmn Ah, right, I indeed haven't updated the firmware. I'm not in the habit of checking the forums too often. I'll give it a shot!
       
 (DIR) Post #B9Og6quCQSi1sDYcHA by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @nikola ok, hope it works, otherwise feel free to reach out! (can't promise i can help effectively before monday though)
       
 (DIR) Post #B9Og7lWPvYYPSxrvcW by mntmn@mastodon.social
       1 likes, 0 repeats
       
       @rick great, thank you!
       
 (DIR) Post #B9Oh05sWSTRWEq78fg by nikola@mathstodon.xyz
       0 likes, 0 repeats
       
       @mntmn Well, I can report that an `apt full-upgrade` followed by `fwupdmgr update` & reboot worked! The Pocket Reform boots normally, and I'm happy to say that the battery status reporting seems to be working again as well. šŸŽ‰ Thanks!
       
 (DIR) Post #B9Oh3rnIlUIziPTH1M by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @nikola awesome, good to hear a success story about this on imx8mp!
       
 (DIR) Post #B9OhoGi8SQdUJWBGtc by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @computergripe many thanks, good to hear!
       
 (DIR) Post #B9On9xBwD5FBuwHRLc by elb@social.sdf.org
       0 likes, 0 repeats
       
       @mntmn I had success with no significant roadblocks.HW: MB 1.0 RK3588, KB 1.0, Charging 2.0, Display V2OS: official Debian UnstableI installed barebox first, which took two tries (I think I had a bad SD write the first time) but went fine.I then did OS update w/ apt and firmware update w/ fwupd according to your instructions.I then flashed my customized keyboard firmware (just matrix changes at this point).As far as I can tell, everything is working normally with no fuss.  Great work!
       
 (DIR) Post #B9OolUBGcUPKtsQXYG by rpm@librem.one
       0 likes, 0 repeats
       
       @mntmn I have a a311d (since CrowdSupply forgot about me and my RK3588 upgrade order) and as you know from the other forum posters it wasn't so smooth. Lots of complications, new firmware doesn't like my main Anker charger (that I have in multiple places in my house :( ), but here currently screen won't show anything after multiple boot attempts. (This started after my apt upgrade last night to try to get the charger to work, even though I think that's just a system firmware complication).
       
 (DIR) Post #B9OyvmZC7D0kMQAREW by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @rpm uff, sorry to hear that! hmm i use anker to test, among others! which model exactly?[about rk3588, it's possible that CS/mouser oversold and didn't restock from us. i recommend to cancel that and order from MNT shop instead, or go for quasar qcs6490.]can you show a photo of the "system status" screen in OLED menu? i'd like to confirm the numbers.are you on our normal "unstable" debian distro?
       
 (DIR) Post #B9P9Jty9FAeLoJykzo by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @dartov yay, glad to hear!
       
 (DIR) Post #B9PAxqjqm42ZKQu5mi by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @chrmills awesome, great to hear!
       
 (DIR) Post #B9PF7zVjPhdbFQOJKS by kop316@fosstodon.org
       0 likes, 0 repeats
       
       @mntmn I installed both and didn't notice a difference. I am presuming that means it went well.Display v2,  Charger v2, mainboard v1, keyboard v1, rk3588
       
 (DIR) Post #B9PKOszFQEXphx4YbI by robinheghan@snabelen.no
       0 likes, 0 repeats
       
       @mntmn went smoothly for me!Got my pocket reform in june, with RK3588.I did wait a few days, just in case, and based on the community thread I’m glad I did šŸ˜…
       
 (DIR) Post #B9PMT2MKiYn5qHyg7s by ewolff@mastodon.social
       0 likes, 0 repeats
       
       @mntmn rk3588, 32GB, battery and headset board 2.0. Updated kernel and firmware this morning. Used it for quite some time then. Had a lock up and some problems during boot, during some boots I was unable to enter the password for the encrypted SSD. So pretty stable.
       
 (DIR) Post #B9Pge43OkuofMnemC8 by rpm@librem.one
       0 likes, 0 repeats
       
       @mntmn I was the one that asked if you thought the RK3588 from restock to crowd supply or the qcs6490 was going to arrive sooner and you thought it would probably be the crowd supply and I thought you mentioned that you were talking with them about that shipment. 2 months later I haven't heard a thing. I was also trying to keep my pre-increase US pricing. We can continue this debugging on the current thread in your forum.
       
 (DIR) Post #B9PleTtbAwc7Hj5hw0 by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @rpm yep, back then we had everything set up but they didn't get back to us on the offer, idk why
       
 (DIR) Post #B9PpCRAS7nxiX2rDzk by rpm@librem.one
       0 likes, 0 repeats
       
       @mntmn Oh I'm sorry they left you hanging, but thank you for letting me know. I'll cancel that order and go direct! Also you should be sleeping! I wasn't expecting to hear anything back until Monday!
       
 (DIR) Post #B9QjfSISbIP5rh15sG by joo@layer8.space
       0 likes, 0 repeats
       
       @mntmn debian unstable, rk3588, display v2. Did apt full-upgrade without checking the forums, and thought about checking for new firmware but forgot about it before rebooting. Ran into the issue with battery status reporting on next boot. I had my SD card with stock image, booted from that, updated the firmware and everything works as expected again. :)
       
 (DIR) Post #B9QlulEWg2D8qcbPMG by mntmn@mastodon.social
       0 likes, 0 repeats
       
       @joo cool, thanks for the report!