use the asound.state from manjaro, it is updated. i've edited the installer to do so, see my patch in my sig.
for ...post install changes:
pull pinebookpro-post-install from manjaro
place asound.state in /var/lib/alsa
sudo alsactl nrestore
reboot (optional...)
configure in pavucontrol
if that doesn't work, alsamixer (f6 for default and es8316)
should work.
while your at it read the PKGBUILD from manjaro and consider the additional changes they have tested.
just pull the second firmware repo from manjaro and dump into /lib/firmware/brcm/ like the other. see my patch for a bunch of changes such as this.
for ...post install changes:
pull pinebookpro-post-install from manjaro
place asound.state in /var/lib/alsa
sudo alsactl nrestore
reboot (optional...)
configure in pavucontrol
if that doesn't work, alsamixer (f6 for default and es8316)
should work.
while your at it read the PKGBUILD from manjaro and consider the additional changes they have tested.
(02-17-2020, 03:35 AM)danielt Wrote:(02-14-2020, 07:18 PM)bsammon Wrote: I'm curious about the files in /lib/firmware --
two questions:
1) Where do they come from? - in case I want to download them again/check for new versions.
2) why aren't they package-ized, so I can poke at them with dpkg? Should/shouldn't they be? (Has this changed since a few weeks ago when I used the installer?)
Yes, they should be packaged... however ideally that should happen by the firmwares being pushed into the upstream linux-firmware repository (which may need help from Rockchip to sort of out the legal details). From they will flow into the Debian packages and eventually the existing not-packaged firmwares will be overwritten.
I don't really want to create (or maintain) a package that reduces the pressure to get it fixed properly.
just pull the second firmware repo from manjaro and dump into /lib/firmware/brcm/ like the other. see my patch for a bunch of changes such as this.