Reform-hw-setup error on boot

MNT Pocket Reform
1

Seeing an error during boot, checking afterwards:

$ sudo systemctl status reform-hw-setup                                         
× reform-hw-setup.service - MNT Reform Hardware Defaults Setup
     Loaded: loaded (/usr/lib/systemd/system/reform-hw-setup.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2025-07-30 19:54:30 BST; 3min 6s ago
 Invocation: 3021137723a4428c982cb8b4372d9ad5
       Docs: man:reform-hw-setup(1)
    Process: 17531 ExecStart=/usr/bin/reform-hw-setup (code=exited, status=1/FAILURE)
   Main PID: 17531 (code=exited, status=1/FAILURE)
   Mem peak: 2.2M
        CPU: 90ms

Jul 30 19:54:29 skydancer systemd[1]: Starting reform-hw-setup.service - MNT Reform Hardware Defaults Setup...
Jul 30 19:54:30 skydancer reform-hw-setup[17550]: amixer: Unable to find simple control 'Speaker Driver',0
Jul 30 19:54:30 skydancer systemd[1]: reform-hw-setup.service: Main process exited, code=exited, status=1/FAI>
Jul 30 19:54:30 skydancer systemd[1]: reform-hw-setup.service: Failed with result 'exit-code'.
Jul 30 19:54:30 skydancer systemd[1]: Failed to start reform-hw-setup.service - MNT Reform Hardware Defaults >

… and there is no Speaker

$ amixer -i scontrols                                                          
Simple mixer control 'Master',0
Simple mixer control 'Capture',0

However, GNOME shows speaker and headphone volume controls.

What did I break?

2

I think you had an RK3588 Pocket Reform?

@minute If I don’t misremember I think you said that the init_tlv320aic3100 should be removed from reform-hw-setup now that the UCM2 profiles are a thing?

3

Yes, I’m sorry I should have said that, I do indeed have the RK3588 now.

It has been through various rolling software updates so I’m not completely sure on what iterations of setup scripts etc.

4

I also noticed that I intermittently see the reform-hw-setup unit fail (although, anecdotally it errors out more often than not).

For example, my previous boot:

$ sudo journalctl -u reform-hw-setup.service -b -1

Aug 24 11:26:14 *** systemd[1]: Starting reform-hw-setup.service - MNT Reform Hardware Defaults Setup...
Aug 24 11:26:15 *** reform-hw-setup[1254]: amixer: Unable to find simple control 'Speaker Driver',0
Aug 24 11:26:15 *** systemd[1]: reform-hw-setup.service: Main process exited, code=exited, status=1/FAILURE
Aug 24 11:26:15 *** systemd[1]: reform-hw-setup.service: Failed with result 'exit-code'.
Aug 24 11:26:15 *** systemd[1]: Failed to start reform-hw-setup.service - MNT Reform Hardware Defaults Setup.

And the current boot:

$ sudo journalctl -u reform-hw-setup.service -b

Aug 24 20:07:31 *** systemd[1]: Starting reform-hw-setup.service - MNT Reform Hardware Defaults Setup...
[...skipped for brevity...]
Aug 24 20:07:33 *** systemd[1]: reform-hw-setup.service: Deactivated successfully.
Aug 24 20:07:33 *** systemd[1]: Finished reform-hw-setup.service - MNT Reform Hardware Defaults Setup.

Despite no changes or updates to installed packages. The last apt operation was before boot -1:

$ cat /var/log/apt/history.log | tail -n 5

Start-Date: 2025-08-24  09:49:36
Commandline: apt autoremove
Requested-By: ***
Remove: ***
End-Date: 2025-08-24  09:49:38
5

reform-tools 1.77 is now in the MNT repositories and fixes the amixer: Unable to find simple control problem in reform-hw-setup.

6

Thanks for the heads up!

Out of curiosity, I took a peek at the what changed from v1.76 to v1.77 and it doesn’t look like anything changed related to the MNT Pocket Reform with the RK3588 module (which is what I have - and I don’t know if it matters, but I got the RCORE Carrier Board board upgrade).

Either way, I’ll give it a shot and see if it resolves the boot issues and report back.

7

Indeed. The changes in 1.77 only addressed the issues on RK3588 classic Reform. This commit is doing the same but for the pocket:

1 Like
8

Nice! That did the trick. I guess reform-hw-setup sometimes worked because the order of the ALSA cards was not deterministic.