Does the Image Repo for firmware versions not go back further?
Well, while I know I've already mentioned this on the other chat, it's the section on setting up the background 'pulseaudio', since commands are outdated on the device. I know that it may be excessive to think of downgrading to a "compatible" version, but I've been having little success finding alternatives or replacements for commands originally used like said 'udevd'.
@Scruffy I just looked at the doc and it does seem to be out of date. I personally do not use sound on any of my devices so I don't use pulse audio, however a took a quick look at the build system and the repos and it seems you should just be able to install pulseaudio-daemon-avahi to get a functioning daemon.
Edit /etc/opkg/disfeeds.conf and uncomment lines 2 and 5
opkg install pulseaudio-daemon-avahi
Restart your system. The daemon code relies upon the existence of some device files related to the sound device so this tells me the you will need to have the bluetooth and audio expansions connected so that the drivers will load and create the device files.
Others may have more experience with pulseaudio, I prefer quiet machines
@crispyoz Currently at the daemon installation. There seems to be several data file clashes with what's already on the device.
Files it wants to install: libavahi-common.so.3, libavahi-common.so.3.5.3, libavahi-core.so.7, libavahi-core.so.7.0.2. These are all under /usr/lib/.
It says these files are already provided in the package labelled 'libavahi-nodbus-support'. Is this one perhaps under one of the uncommented packages? I don't know whether one should go in and just delete them, or if the files necessary are already installed for progression.
@Scruffy just use the --force-overwrite option for opkg:
opkg --force-overwrite install pulseaudio-daemon-avahi
Part of building stuff is about breaking stuff, you focus on what you are trying to get running and once you're successful in that then you step back and look at the larger picture of what your final device firmware will look like. Worst case scenario is something stops running and you have to do a factory reset. Don't be shy to test the boundaries, I promise you that no software you install on your Omega will cause an atomic mushroom cloud
This post is deleted!
@crispyoz Okay. It needed to refresh the updates once before, but after that, it replaced the existing files without any trouble this time.
@Scruffy Always a good idea to run opkg update before doing any install or upgrade. opkg only knows about what it has indexed and it only updates its index when you update. It's a little rudimentary but that's how it works.
@crispyoz Proceeding from there, I was seeing if it could work with pulseaudio yet, though it fails to load or detect the module. Not sure if that was the correct process of events.
@Scruffy pulseaudio daemon expects to find the device files, if they don't exist it will fail.
If you run:
what is the output?
Since pulse audio is dependent upon the device files, and the device files are created by the device modules, this should inform the resolution
chown: /dev/mixer: No such file or directory
chown: /dev/dsp: No such file or directory
chmod: /dev/mixer: No such file or directory
chmod: /dev/dsp: No such file or directory
This followed opkg update. Could there still be crucial files missing, or commented packages that should be activated?
@Scruffy I wanted to chime in here on the repo question
The older firmware images can be found here: http://repo.onion.io/omega2/images/
This repository has all of the 0.1.x and 0.2.x firmware images (2018 and earlier).
The new repository is here: http://repo.onioniot.com/
We switched to that in early 2019 and it has all of the 0.3.x firmware images
You can use NCM to upgrade the firmware on many devices in one operation. Because security fixes are distributed as new firmware revisions, upgrading firmware helps network administrators correct security vulnerabilities.
The firmware image repo appears to be down for me, however I need a copy of the firmware as I managed to corrupt the one on my device. Does anyone happen to have a mirror?
I end up getting some kind of error
It just doesn't work in Firefox. Worked in edge fine.
@Cartographer So you're the one who uses Edge. I knew there must be at least one person
Firefox has a lot of security options, I just checked on Firefox 79.0 (64-bit), Win10 x64, worked fine. Also Firefox on my Ubuntu 18 box, also worked fine.
I need a copy of the firmware
Figured it out, some plugin was just causing it to fail on firefox.
Thanks for the help I'm up and running again on my device.