[Mut@nt HD2400] feeds and status-message.php for self built 6.8.007 ?

[adennisa15]

What type of support thread are you creating?

Support question

What OpenViX Image build number are you using?

6.8.007

Have you tried re-flashing WITHOUT settings restore?

NO

Have you tried re-flashing WITH a settings restore?

YES

Hi, I've recently found the 6.8 OpenVIX release and as there's no build for the Mut@nt HD2400, I've built a release build myself instead.

I started with just an enigma2-image build, but on installing it, it complained about missing feeds and restored plugins from the backup instead.

So I built the feeds and then image builds too.

As mentioned in other forum posts. I've symlinked the built tmp/deploy/ipk dirs into /feeds/openvix/release/6.8/hd2400/ in my local webserver docroot, fixed all the permissions and checked Packages.gz etc can be downloaded from the cli (curl/wget) on the receiver - all no problem.

I'd replaced http://www.openvix.co.uk/ in DISTRO_FEED_URI in meta-oe/conf/distro/openvix.conf with my server host instead - obviously before building the image.

As there was also an http://www.openvix.co.uk/ in STATIC_DISTRO_FEED_URI, I replaced that with my server host too.

After all of that, I was somewhat disappointed that on (re)install, it was still complaining about feed problems!

Access logs on the webserver look like this...

192.168.1.19 - - [03/May/2026:07:13:37 +0100] "GET /feeds/openvix/release/6.8/hd2400/hd2400/Packages.gz HTTP/1.1" 200 89450 "-" "Python-urllib/3.13"
192.168.1.19 - - [03/May/2026:07:13:37 +0100] "GET /status-message.php?machine=mutant2400&version=6.8&build=007 HTTP/1.1" 404 209 "-" "Python-urllib/3.13"

192.168.1.19 - - [03/May/2026:07:13:39 +0100] "GET /feeds/openvix/release/6.8/hd2400/all/Packages.gz HTTP/1.1" 200 57575 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:39 +0100] "GET /feeds/openvix/release/6.8/hd2400/hd2400/Packages.gz HTTP/1.1" 200 89487 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:39 +0100] "GET /feeds/openvix/release/6.8/hd2400/mips32el/Packages.gz HTTP/1.1" 200 741771 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:40 +0100] "GET /feeds/openvix/release/6.8/hd2400/mutant2400/Packages.gz HTTP/1.1" 200 15749 "-" "Wget/1.25.0"

192.168.1.19 - - [03/May/2026:07:13:40 +0100] "GET /feeds/openvix-static/6.8/static-all/Packages.gz HTTP/1.1" 404 530 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:40 +0100] "GET /feeds/openvix-static/6.8/static-hd2400/Packages.gz HTTP/1.1" 404 530 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:40 +0100] "GET /feeds/openvix-static/6.8/static-mips32el/Packages.gz HTTP/1.1" 404 530 "-" "Wget/1.25.0"

192.168.1.19 is the receiver. It's successfully retrieving the four Packages.gz files (200 results).

Fairly unsurprisingly, it's getting 404 errors for the /feeds/openvix-static/6.8/static-*/Packages.gz - as there's no symlinks for those - but also for the status-message.php too - as that doesn't exist either.

I'm guessing they should exist, but where do they come from?

And supplementary questions...

Can I put the image zip file somewhere in the webserver and somehow reconfigure the Software Manager to look on the local webserver for updates, rather than https://www.openvix.co.uk/index.php/downloads/mutant-images/hd2400/ etc? Where/how etc?

When 6.8.008+ etc is eventually released, is it just a case of doing ... make update then ... make image again, or is it better/necessary to blow it all away and start again (maybe ... make clean?) [not covered in the https://github.com/OpenViX/enigma2/blob/Release/README.md instructions]

Does http://www.openvix.co.uk/status-message.php?machine=mutant2400&version=6.7&build=020 need updating to direct users to the v6.8 release notice, specifically the lack of ongoing builds for this (and presumably other) receiver(s)? It currently says...

There are no more updates for 6.7 series images.

Feeds for 6.7 will soon be removed.

Please install/flash with the latest OpenViX version.
Using Image Manager to do this is the easiest method.

Blue > Vix > Image Manager
Yellow to download an image
Select the image you want
Blue to flash the highlighted image

You can then restore settings and plugins after flashing the new image.
You won't have to set eveything up again.
Whole process should take you roughly 10 minutes.

If you want to flash by USB, go to following site for downloads:
www.openvix.co.uk

For support, visit
www.world-of-satellite.com

... Using Image Manager is certainly no longer possible!

Finally, If it's any interest, I actually successfully built on Debian (v12.13 aka "Bookworm"), rather than Ubuntu 24.04/26.04. There were a small number of warnings (approx 10-20) during the build that didn't sound too serious, but nothing failed. The image produced seemed to flash and boot ok and limited testing looks as though it's functional (so far). If any of the details are interesting/useful, I can supply those.

As a seasoned Software Developer, building this from just the build instructions was more or less "bread and butter" stuff, so wasn't too tricky, but without that background I'd have said that "... please build version 6.8 yourself. There are instructions in our enigma2 repo and we are happy to support you with this on the forum." would be pretty tough going for most regular users!

Thanks

 

[Huevos]

Static feeds are not part of the build. They are something I build as an extra to give some boxes access to qt_stalker, kodi, nodejs and some closed source third party plugins. So just delete the opkg.conf files for static and remove them from your build for the future.

 

[Huevos]

Also, hosting your feeds on a server is not mandatory, you could also host them on a USB stick. Just change the conf files to point at the stick.

 

[el bandido]

Hi, I've recently found the 6.8 OpenVIX release and as there's no build for the Mut@nt HD2400, I've built a release build myself instead.

I started with just an enigma2-image build, but on installing it, it complained about missing feeds and restored plugins from the backup instead.

So I built the feeds and then image builds too.

As mentioned in other forum posts. I've symlinked the built tmp/deploy/ipk dirs into /feeds/openvix/release/6.8/hd2400/ in my local webserver docroot, fixed all the permissions and checked Packages.gz etc can be downloaded from the cli (curl/wget) on the receiver - all no problem.

I'd replaced http://www.openvix.co.uk/ in DISTRO_FEED_URI in meta-oe/conf/distro/openvix.conf with my server host instead - obviously before building the image.

As there was also an http://www.openvix.co.uk/ in STATIC_DISTRO_FEED_URI, I replaced that with my server host too.

After all of that, I was somewhat disappointed that on (re)install, it was still complaining about feed problems!

Access logs on the webserver look like this...

192.168.1.19 - - [03/May/2026:07:13:37 +0100] "GET /feeds/openvix/release/6.8/hd2400/hd2400/Packages.gz HTTP/1.1" 200 89450 "-" "Python-urllib/3.13"
192.168.1.19 - - [03/May/2026:07:13:37 +0100] "GET /status-message.php?machine=mutant2400&version=6.8&build=007 HTTP/1.1" 404 209 "-" "Python-urllib/3.13"

192.168.1.19 - - [03/May/2026:07:13:39 +0100] "GET /feeds/openvix/release/6.8/hd2400/all/Packages.gz HTTP/1.1" 200 57575 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:39 +0100] "GET /feeds/openvix/release/6.8/hd2400/hd2400/Packages.gz HTTP/1.1" 200 89487 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:39 +0100] "GET /feeds/openvix/release/6.8/hd2400/mips32el/Packages.gz HTTP/1.1" 200 741771 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:40 +0100] "GET /feeds/openvix/release/6.8/hd2400/mutant2400/Packages.gz HTTP/1.1" 200 15749 "-" "Wget/1.25.0"

192.168.1.19 - - [03/May/2026:07:13:40 +0100] "GET /feeds/openvix-static/6.8/static-all/Packages.gz HTTP/1.1" 404 530 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:40 +0100] "GET /feeds/openvix-static/6.8/static-hd2400/Packages.gz HTTP/1.1" 404 530 "-" "Wget/1.25.0"
192.168.1.19 - - [03/May/2026:07:13:40 +0100] "GET /feeds/openvix-static/6.8/static-mips32el/Packages.gz HTTP/1.1" 404 530 "-" "Wget/1.25.0"

192.168.1.19 is the receiver. It's successfully retrieving the four Packages.gz files (200 results).

Fairly unsurprisingly, it's getting 404 errors for the /feeds/openvix-static/6.8/static-*/Packages.gz - as there's no symlinks for those - but also for the status-message.php too - as that doesn't exist either.

I'm guessing they should exist, but where do they come from?

And supplementary questions...

Can I put the image zip file somewhere in the webserver and somehow reconfigure the Software Manager to look on the local webserver for updates, rather than https://www.openvix.co.uk/index.php/downloads/mutant-images/hd2400/ etc? Where/how etc?

When 6.8.008+ etc is eventually released, is it just a case of doing ... make update then ... make image again, or is it better/necessary to blow it all away and start again (maybe ... make clean?) [not covered in the https://github.com/OpenViX/enigma2/blob/Release/README.md instructions]

Does http://www.openvix.co.uk/status-message.php?machine=mutant2400&version=6.7&build=020 need updating to direct users to the v6.8 release notice, specifically the lack of ongoing builds for this (and presumably other) receiver(s)? It currently says...

There are no more updates for 6.7 series images.

Feeds for 6.7 will soon be removed.

Please install/flash with the latest OpenViX version.
Using Image Manager to do this is the easiest method.

Blue > Vix > Image Manager
Yellow to download an image
Select the image you want
Blue to flash the highlighted image

You can then restore settings and plugins after flashing the new image.
You won't have to set eveything up again.
Whole process should take you roughly 10 minutes.

If you want to flash by USB, go to following site for downloads:
www.openvix.co.uk

For support, visit
www.world-of-satellite.com

... Using Image Manager is certainly no longer possible!

Finally, If it's any interest, I actually successfully built on Debian (v12.13 aka "Bookworm"), rather than Ubuntu 24.04/26.04. There were a small number of warnings (approx 10-20) during the build that didn't sound too serious, but nothing failed. The image produced seemed to flash and boot ok and limited testing looks as though it's functional (so far). If any of the details are interesting/useful, I can supply those.

As a seasoned Software Developer, building this from just the build instructions was more or less "bread and butter" stuff, so wasn't too tricky, but without that background I'd have said that "... please build version 6.8 yourself. There are instructions in our enigma2 repo and we are happy to support you with this on the forum." would be pretty tough going for most regular users!

Thanks

I prefer to edit meta-local whenever possible. Find: /build-enviroment/meta-local/conf
I edit layer.conf then add my feeds conf. I have attached what I use as examples. Edit them to what you need and rename them if you want.
In the receiver, look in /etc/opkg. There you will see where your linked to for feeds. Edit directly here as a temporary work-around.

I have a crontab set for this OpenVix distro so it runs and updates automatically. Everything works fine for me using Ubuntu 22.

 

[Huevos]

Note, everytime you edit layer.conf it forces a complete rebuild. Probably better to edit site.conf.

 

[el bandido]

I keep every edit I can inside metal-local. I have found over the years this works best for me and my limited memory. All edits in one place makes it easier to move too.

We want a working Image Manager in our Home Builds. My solution for that is attached. Unzip it and set the folder beside conf in meta-local, then edit according to your needs. Remove any unwanted or useless files. Edit as wanted or needed.

 

[adennisa15]

Thanks @Huevos for your comments and pointers and @el bandido for your customised config, I'll take a look at those in more detail when I can find some time to play around with this again, hopefully in the not too distant future!