RubisDrake
Member
- Joined
- Apr 26, 2012
- Messages
- 38
Now that Firefox requires PulseAudio, I can see why that would be needed, not just for WebRTC voice calls, but IM applications like Skype, Discord, etc...
4th post in this thread, aTc gives some directions. While it does work it's not really optimized to work on the Pandora. Also never tested the current Stretch release on the Pandora, but it should work.Please provide instructions on how to install pyra Debian Stretch on Pandora.
So if I extract the "http://next.openpandora.org/pyra-rootfs-pnd.tgz" on top of the Pyra latest Debian Stretch image, it will work?4th post in this thread, aTc gives some directions. While it does work it's not really optimized to work on the Pandora. Also never tested the current Stretch release on the Pandora, but it should work.
Nubs should work, but you need to manually run a command to enable them in the right mode. Also the keymap is likely wrong too, think I had to migrate the xmodmap from the Pandora.For me the touchscreen didn't work at all though, nor nubs. So it's a bit hard to use.
Booting with b) works (sda1 or sda2), but no network, no hdmi output, no usb devices found
What have i to check?
ALSA miraculously started working again with FF. It's probably still deactivated at compile time by default, though - Arch explicitly enables ALSA support for their FF packages so it 'just works' for me. I just hope that the audio framework was not part of the big overhaul that comes with version 57... (Edit: Nope, ALSA is still working with FF 57 - still one hell of an awful update, though)Now that Firefox requires PulseAudio
apulse is very specific and works only with a certain collection of applications, it was not developed to be an universal translation layer. When the time came that Mozilla kicked out the ALSA support entirely its Firefox compatibility was already broken again.There is 'apulse' wrapper for alsa which gives a PA sink for programs that need it.