04-11-2024, 04:03 PM
(This post was last modified: 04-11-2024, 04:03 PM by Tim Curtis.)
(04-11-2024, 02:04 PM)TheOldPresbyope Wrote: Since this is a pre-release it's hard to know what is a genuine bug and what is still a work-in-progress.
1. In my case, booting ~pre3 on an RPi3BPlus and an RPI4B, I don't see the Headphone output device listed either in the webUI or using aplay -l.
2. On first boot of the Pi4B, my Creative Tech USB-BT adapter was correctly detected as a USB Audio device with no hardware volume control. With volume knob still set at 0, I started playing a radio station. Surprise---full volume output (to BT headphones NOT on ears!). Once I adjust the volume knob, I have normal 0-100 control volume. After rebooting, the behavior seems normal.
3. I have an official 7-in display on the RPi3BPlus and the X11 server isn't starting when I activate Local Display. Need my morning coffee before I look under the covers.
Still flashing images for two more test hosts: RPiZero2W and RPi5.
Early days yet but very promising we've gotten this far!
Regards,
Kent
For #1 and #3 I think the KMS driver (dtoverlay=vc4-kms-v3d) may be the cause. It's basically required and I can't find much info on it related to 1 and 3.
1. KMS driver: Looks like it does not show Headphone port, or could be an OS/kernel issue.
3. KMS driver: Local UI will prolly only work on >= Pi4. it won't start for me either on < Pi4.
2. This could be a configuration or sequencing issue during startup. I'll investigate
As always: WARNING about volumes with pre-release code, or just in general be careful and always have a downstream volume control that can be set at low level before testing.
