ALSA looks for wrong device name when using U-Boot
<!-- Thank you for using postmarketOS! In order to speed up process of resolving your issue, we would like you to fill in the following form. *** NOTE FOR CONFIDENTIAL ISSUES: *** A lot of people can read confidential pmaports issues! If you want to submit something that only the postmarketOS Core Team can see, write to team@postmarketos.org instead of opening an issue here! --> ### Describe your issue #### What's the expected behaviour? ALSA finds `Fairphone 5.conf` #### What's the current behaviour? ALSA looks for `fairphone-Fairphone5-.conf`, doesn't find it, and results in no audio. #### How to reproduce your issue? Flash uboot on either fp5 or Shift6 axolotl, observe no audio. ### What device are you using? <!-- Leave name of your device in vendor-codename format. If unsure, check name in the device package or leave full name of device PinePhone: which revision exactly? See https://wiki.pine64.org/index.php/PinePhone#Hardware_revisions --> fairphone-fp5 ### On what postmarketOS version did you encounter the issue? <!-- Replace space inside `[ ]` with `x` to fill the checkbox --> * [x] edge (`master` branch) * [ ] `v25.12` * [x] I confirm that the issue still is present after running `sudo apk upgrade -a` ### On what environment did you encounter the issue? #### Environments * [ ] COSMIC * [x] GNOME Shell on Mobile * [x] Phosh * [ ] Plasma Mobile * [ ] Sxmo (Wayland/Sway) **Please post the output of `sxmo_version.sh`** * [ ] Other: **Please fill out** ### Which init system are you using? * [ ] OpenRC * [ ] systemd ### How did you get postmarketOS image? * [ ] from https://images.postmarketos.org * [x] I built it using pmbootstrap * [ ] It was preinstalled on my device ### What's the build date of the image? (in yyyy-mm-dd format) <!-- Notes: can be left empty if unsure If you downloaded image from images.postmarketos.org, date will be in yyyymmdd format --> ### Additional information <!-- logs, etc. -- make use <details> for long listings If your device displays an error message on boot or drops to the debug shell, attaching it to your PC with a USB cable may show a removable USB drive. You can drag and drop the .tar.gz file or otherwise upload it here. Refer to the README file on the device for more information. --> Using `strace -f alsaucm reload` you can find which wrong file it's trying to load, then symlimk the correct one to that path in order to work around this issue. For fp5: ``` sudo ln -s /usr/share/alsa/ucm2/conf.d/qcm6490/{Fairphone\ 5.conf,fairphone-Fairphone5-.conf} ```
issue