As the hardware does not seem to be recognised, I would try a live image of Trixie first, to see if it "just works".
https://cdimage.debian.org/cdimage/week ... so-hybrid/
If it does, then you know that there is a kernel update, or use case management update, or firmware update that has added support for your hardware (and won't, unfortunately, be added to Bookworm).
If it does work, but you don't want to use Debian Testing, your options are..
1. Try a newer kernel from backports:
https://backports.debian.org/Instructions/
2. Try a newer alas-ucm-conf which contains "configuration of audio input/output names and routing for specific audio hardware". Obviously, if alsa doesn't have this information, your hardware won't work.
Usually, adding newer packages to Stable is a bad idea, but in this case it may a) work b) be safe c) be the only way to get your hardware working.
Options are to install alas-ucm-conf (manually) from sid, or directly from the alsa project. I am not aware of any issues doing this in Bookworm. There was a reason why it wouldn't work in Bullseye, which I wrote about here:
viewtopic.php?t=153813
However, some users have managed to get hardware working in Bookworm with this method:
viewtopic.php?p=785491#p785491
viewtopic.php?t=155566
3. Check with dmesg again and see if the firmware is loading correctly. If not, try the firmware form Sid too.
viewtopic.php?t=153813
https://cdimage.debian.org/cdimage/week ... so-hybrid/
If it does, then you know that there is a kernel update, or use case management update, or firmware update that has added support for your hardware (and won't, unfortunately, be added to Bookworm).
If it does work, but you don't want to use Debian Testing, your options are..
1. Try a newer kernel from backports:
https://backports.debian.org/Instructions/
2. Try a newer alas-ucm-conf which contains "configuration of audio input/output names and routing for specific audio hardware". Obviously, if alsa doesn't have this information, your hardware won't work.
Usually, adding newer packages to Stable is a bad idea, but in this case it may a) work b) be safe c) be the only way to get your hardware working.
Options are to install alas-ucm-conf (manually) from sid, or directly from the alsa project. I am not aware of any issues doing this in Bookworm. There was a reason why it wouldn't work in Bullseye, which I wrote about here:
viewtopic.php?t=153813
However, some users have managed to get hardware working in Bookworm with this method:
viewtopic.php?p=785491#p785491
viewtopic.php?t=155566
3. Check with dmesg again and see if the firmware is loading correctly. If not, try the firmware form Sid too.
viewtopic.php?t=153813
Statistics: Posted by FreewheelinFrank — 2024-01-04 22:27 — Replies 11 — Views 235