i made the mistake of updating to 19, since i have two rpi3’s and vc-1 files which don’t play well now. i plan to go back to v18 but since i use shared Mysql database, i will have to do that on not only the rpi3’s but also on the vero 4k+.
i liked the test build of v18 that worked well with 3d on the 4k+.
once i reinstall v18 on the 4k+, is the test build still an available update if i have the appropriate sources?
thank you.
i found the following site for previous versions of osmc that coincide with test build dates:
http://ftp.fau.de/osmc/osmc/apt/pool/main/v/?C=M;O=A
Any help here as far as getting the November 19 build to work? Here’s what I tried:
- wget “http://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero364-source-4.9.113-26-osmc/vero364-image-4.9.113-26-osmc_26_arm64.deb” -O mediacenter.deb
- wget “http://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero364-source-4.9.113-26-osmc/vero364-headers-4.9.113-26-osmc_26_arm64.deb” -O mediacenterheader.deb
- wget “http://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero364-source-4.9.113-26-osmc/vero364-source-4.9.113-26-osmc_26_all.deb” -O mediacentersource.deb
- sudo dpkg -i mediacenterheader.deb
- sudo dpkg -i mediacenter.deb
- sudo dpkg -i mediacentersource.deb
I’m sure there are programmers out there laughing at this, but i figured it was worth a try. I got the unhappy face.
Any help?
If you update the kernel you will also have userland components that need updating.
It won’t be trivial to run a v18 test build.
is there a way to run the vero 4k+ on v19 so that i get the 3d, while also using the last v18 stable build on the other devices (rpi3) that don’t require 3d? the server is on a pi3, and i’m using mysql. so as i see it, the main issue is different mysql versions.
can i have v18 on the pi3 and have the most recent version of mysql database that will match with v19? i do know more about database programming than other forms of programming so i’d be up for the challenge.
thank you.
Could you run everything on v18 and use the Pi for 3D?
thanks for the thought. that would be an option but i also use the vero 4k for atmos. the main reason i bought the vero 4k over other options was b/c of 3d AND atmos. a great combo.
still plugging away at this. thanks to sam’s suggestions, i got rid of the unhappy face by doing this:
sudo apt-get install vero3-userland-dev-osmc
after this, i was also able to play movies but only if i turned off HW acceleration. I saw a post here that dealt with an issue similar in which the poster had to update his bootloader to a secure bootloader. When i tried that, i got the error indicating that my /boot drive is not mounted. that was with bootloader 1.0.6.
i’ve tried fixing this by trying to mount it (including in fstab by un-commenting the line), but so far ran into a roadblock. i then used a more recent bootloader (1.7.0-1) that didn’t give any error messages using dpkg -i, but when checking the logs the root drive was still not mounted. and this didn’t fix the issue with HW acceleration.
i realize this is completely unsupported at this time, but if anyone wants to help i’m open for suggestions. otherwise i’ll see what i can do with my limited knowledge and try to post back here with any updates in case someone else is thinking of trying this to.
There is no /boot on an external partition on Vero 4K/4K+