question

jbakuwel avatar image

Updating/installing packages on VenusGX running Venus 2.70~3-large-10 broken

Hi Jeroen, Matthijs,

root@beaglebone:~# opkg update
Downloading https://updates.victronenergy.com/feeds/venus/release/packages/zeus/all/Packages.gz.
Downloading https://updates.victronenergy.com/feeds/venus/release/packages/zeus/cortexa8hf-neon/Packages.gz.
Downloading https://updates.victronenergy.com/feeds/venus/release/packages/zeus/beaglebone/Packages.gz.
Collected errors:
* opkg_download_backend: Failed to download https://updates.victronenergy.com/feeds/venus/release/packages/zeus/all/Packages.gz, wget returned 8.
* opkg_download_backend: Failed to download https://updates.victronenergy.com/feeds/venus/release/packages/zeus/cortexa8hf-neon/Packages.gz, wget returned 8.
* opkg_download_backend: Failed to download https://updates.victronenergy.com/feeds/venus/release/packages/zeus/beaglebone/Packages.gz, wget returned 8.

/etc/opkg/venus.conf refers to zeus; should this be rocko?

In any case, I've downloaded the packages I needed from packages/rocko/cortexa8hf-neon and installed those; working beautifully.

Kind regards,
Jan


Venus OSVenus GX - VGX
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

4 Answers
mvader (Victron Energy) avatar image
mvader (Victron Energy) answered ·

This is what it is, will be fixed once v2.70 is officially in candidate

1 comment
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Hi Matthijs. Thanks for the prompt response. Jan


jordash184 avatar image
jordash184 answered ·

Could someone let me know how to manually install the packages. I'm trying to follow this guide: https://github.com/aaronsb/victronvenussupport/blob/master/venus_rpi_enablement.md

but now that the opkg update doesn't work I need some help getting the touchscreen set up, etc.


Thanks in advance.

7 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

They’re not available at the moment.


what I could perhaps do is make them all pre-installed.


does anyone know if there are any disadvantages of installing those packages always? Perhaps for systems with no screen or systems with a normal screen (no touch)?

jordash184 avatar image jordash184 mvader (Victron Energy) ♦♦ ·

Is there a manual workaround for now?

Hi @Jordash184,

You could download packages from

https://updates.victronenergy.com/feeds/venus/release/packages/rocko/cortexa7hf-neon-vfpv4/

or

https://updates.victronenergy.com/feeds/venus/release/packages/rocko/cortexa8hf-neon/

or

https://updates.victronenergy.com/feeds/venus/release/packages/rocko/cortexa9hf-neon/

depending on your architecture and then install them with:

opkg install <package>

That worked for me when I needed a specific package.

cheers,
Jan

OK thanks, I'm afraid I'm a real beginner at this. So I'm not even sure what commands to use and where to download onto my RPi. This is a fresh install of the 'large' version.

OK, I think I figured it out. I went to venus.conf in the /etc/opkg and changed the address from Venus to Rocko. opkg seems to be working.


Thanks to those who took the time to answer my earlier questions, really appreciate it.

ok, good that that works; careful though: the (rocko) repository you're system is now downloading packages from was (a) built with/for a different kernel version, and (b) different openembedded version.

Conclusion of that: for everything that works, be happy. And everything that doesn't work: don't be surprised that things don't work. :)

jordash184 avatar image jordash184 mvader (Victron Energy) ♦♦ ·

Ah OK, thanks for the heads up. I suppose as and when the 2.70 Large is released I can update the firmware and change that file back to original.

mvader (Victron Energy) avatar image
mvader (Victron Energy) answered ·

Hey all, short update: v2.70 is in candidate now; and today we released v2.70~9, which fixes an issue with the opkg-es. They work again.

2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

code-chief avatar image
code-chief answered ·

Although the packages are not published in the release path you can correct it. They do appear to be published by Victron in the other parent directories corresponding to the image type (development, testing or release).

For example, in VenusOS v2.80 test release 22 I had to change three lines from ".../release/packages/..." to ".../testing/packages/...".

nano /etc/opkg/venus.config

Correct paths, press CTRL+O, ENTER to save then CTRL+X to exit.

opkg update

It would be nice if the VenusOS image included a variable and used it here, then it would be fully automatic so long as the build system configures it automatically. Alternatively, just correct these paths as part of the build, but a variable would be better, then other people could use it.

4 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Hi, what we advise is to follow the instructions in the manual ;o).


see set-feed.sh


https://github.com/victronenergy/venus/wiki/commandline-introduction#opkg

code-chief avatar image code-chief mvader (Victron Energy) ♦♦ ·

Thanks, that works and is much cleaner than hacking files. Have you thought about automatically setting the correct feed as you build and release the test images? That would make testing more intuitive especially for people testing 3rd party hardware and software add-ons or automation (the first thing we need to do is install packages).

Yes a bit, but as its now a readonly rootfs, its not so straightforward


Ps better don’t use the testing feed. And stick to candidate or release.