NotLikeSomeone
Active member
I updated (unfortunately almost at the same time) two boxes Ultimo4K: the result was both boxes stuck in the loading enigma2 step. I had to start in recovery mode and reflash the slot.
Two Ultimo4K stuck after today's update
- Thread starter NotLikeSomeone
- Start date
el bandido
Active member
The Problem is not everybody reads or sees your warning before updating online. And you have users of the OBH image that never visit this forum, or if they do, cannot understand the language the warning is written in.
Either build logic in the image that will not allow an update like this to be processed online, or even better, make a new branch for the 6.0.002 feeds. Else you will continue to have users with boxes that are stuck on boot or boxes that do not work correctly who will be blaming the image because they do not understand why it happened.
Either build logic in the image that will not allow an update like this to be processed online, or even better, make a new branch for the 6.0.002 feeds. Else you will continue to have users with boxes that are stuck on boot or boxes that do not work correctly who will be blaming the image because they do not understand why it happened.
There was a warning when 6.0 was released that it is still considered to be beta and therefore future updates may require reflashing rather than simple online updating.
It was also suggested that users should not update to OpenBh 6.0 if this could be an issue for them.
There is no option to build different branches or use different feeds for each update as you already know our resources are limited and we are doing the best we can with what we currently have.
I can't do anymore than I currently have done, I posted a warning 24+ hours before 002 was released, maybe it is better not to post any updates in future ?
It was also suggested that users should not update to OpenBh 6.0 if this could be an issue for them.
There is no option to build different branches or use different feeds for each update as you already know our resources are limited and we are doing the best we can with what we currently have.
I can't do anymore than I currently have done, I posted a warning 24+ hours before 002 was released, maybe it is better not to post any updates in future ?
el bandido
Active member
I understand the frustration. And figuring out what problems are real as compared to what problems are from an incorrect update is also a job in itself...
The problem is only a select few users of the image will ever see or read the warning messages. And even then, some will insist on doing something different, then complain about the results. It does not take membership or reading a forum to download, install, update OBH.
Limited Resources: The current feeds could be stripped of bloat and you would instantly have as an estimate, 3X-5X more space. But even with plenty of space, creating another feed branch is messy. A separate branch though stops the image update failures and errors in their tracks.
Here is something that can be done by simply altering the software.
Current Online Update system for OBH:
Press Update
↓
A few GUI checks
↓
Start opkg
↓
Hope everything works
↓
Reboot
A better Online Update approach:
Press Update
↓
Is this image allowed to update?
↓
Is the image too old?
↓
Is there enough free flash?
↓
Are there too many packages?
↓
Will dependencies resolve?
↓
Download everything first
↓
Install
↓
Verify important packages
↓
ONLY reboot if successful
Or a bare minimum, simply put a cap on allowed updates. If online updates exceed X amount then refuse to update. This will not be the last big update....
The problem is only a select few users of the image will ever see or read the warning messages. And even then, some will insist on doing something different, then complain about the results. It does not take membership or reading a forum to download, install, update OBH.
Limited Resources: The current feeds could be stripped of bloat and you would instantly have as an estimate, 3X-5X more space. But even with plenty of space, creating another feed branch is messy. A separate branch though stops the image update failures and errors in their tracks.
Here is something that can be done by simply altering the software.
Current Online Update system for OBH:
Press Update
↓
A few GUI checks
↓
Start opkg
↓
Hope everything works
↓
Reboot
A better Online Update approach:
Press Update
↓
Is this image allowed to update?
↓
Is the image too old?
↓
Is there enough free flash?
↓
Are there too many packages?
↓
Will dependencies resolve?
↓
Download everything first
↓
Install
↓
Verify important packages
↓
ONLY reboot if successful
Or a bare minimum, simply put a cap on allowed updates. If online updates exceed X amount then refuse to update. This will not be the last big update....
ATV has tried that in the past, users then just decide to do it in telnet to get around it, then cause the same issues anyway and still moan, so it's just lots of work for no gain.
el bandido
Active member
How many users understand telnet or how to run opkg update && opkg upgrade? Moot point anyway because logic can be added to keep opkg update from executing unless certain conditions are met Period. Telnet, Terminal, or other.
If you are looking for solutions, you will find them. Else continue battling the fires that will surely happen with every major update.
If you are looking for solutions, you will find them. Else continue battling the fires that will surely happen with every major update.
NotLikeSomeone
Active member
Yes, it's only our fault, as always: we don't have lives. So, even if we see the update symbol (and we do, in some case, since BH 2.1.x, so more than 12 years) we MUST pick up our PCs and check if it's safe or not to update, although, in these 12 and more years, it has occured maybe a couple of times that updating ny command line was unsafe.
Actually, more often we have been adviced of the opposite: better to update by command line instead of by GUI.
But, yes, we need to visit everyday the forum (which we don't visit only to ask but also to report and to answer other users, if possible) despite family, sons, parents, and work.
Actually, more often we have been adviced of the opposite: better to update by command line instead of by GUI.
But, yes, we need to visit everyday the forum (which we don't visit only to ask but also to report and to answer other users, if possible) despite family, sons, parents, and work.
el bandido
Active member
Everyone has lives to live and obligations to meet, even people who no longer work and are retired. And I would agree that updating online is better than using the receiver menus for the simple fact the update can be monitored and errors seen if a person watches the online update process closely. It cannot be ignored that there are OBH users who never visit this forum.
Online updates can be stopped or blocked if certain conditions are not met, same as the GUI update. Solutions exist, but it will be up to the image group to decide what if anything is done to correct the image update problem in the future.
Online updates can be stopped or blocked if certain conditions are not met, same as the GUI update. Solutions exist, but it will be up to the image group to decide what if anything is done to correct the image update problem in the future.
Ok so you want to go back to the old days of all updates being a full reflash then and remove the option of online updates ?
el bandido
Active member
NotLikeSomeone
Active member
No, I'd like to go to old days when, if prompted an online update was avalaible, we could trust it. Since 2013 I've lost the count of how many online updates I've done to BH and OBH and I remember of probably not more of a couple of cases they were faluty. And when it happened, the team apologised and immediately warned not to do it and, in a very short time it fixed it. That's the old days style.
Nobody's perfect but, when I make a mistake, I simply and honestly make amendments.
By the way: are we kindly allowed now to update?
Kind regards
Last edited:
Ok I repeat once again.
In the release post it states that it is beta and therefore future updates may require a full reflash due to changes constantly being made to the oe-a core.
WE do not control this and it happens in all images.
Other teams change things and it forces complete rebuilds of the image which then breaks online updates.
So if you see an update is available then that means there is an update, nothing more it does not mean an online update will work, these are beta images.
You have also been told the best thing to do, is to do a settings backup (you can add any files you want into the settings backup) then reflash either via usb or using the image manager to download and flash the update and then restore the backup after.
Sure it takes a little longer than just online updating (maybe 5 mins or so), but you won't loose anything and you will then have the latest updates.
You can't have it all ways, and we can not cover every eventuality.
The next update will be a full reflash again because more changes have corrupted the current feeds.
NotLikeSomeone
Active member
Yes, of course: I've always my daily backups, either full or personal...
el bandido
Active member
Corrupted feeds?? I do not see the feeds as being corrupted. They work fine after adjusting the user agent. Something in Telnet or Terminal like:
cp -p /etc/wgetrc /etc/wgetrc.bak 2>/dev/null
echo 'user_agent = Mozilla/5.0 (X11; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0' >> /etc/wgetrc
opkg update
The feeds work fine for me after that small edit.
And then for an online update after making that edit, I am greeted with 788 packages. An update of this size can be done online, but careful attention to the smallest details is needed and the update needs to run in terminal. In this example, a network update cut the ssh connection, which required a reset of the connection then again running the terminal upgrade. After the terminal upgrade finished, it was ran two or three more times until opkg list-upgradable came up empty.
On reboot after the 788 online package update, a python package along with alsa needed attention. The python package was causing an enigma2 crash and halted the boot sequence. Much easier to simply load an image...
Now I understand that this image is really a beta image that is listed as a release image, which might confuse some. There are people who do not read anything and press remote buttons instead. Consider how the online update menu is laid out and worded. If you look real hard at the screenshot shown below you will find the words "Reflash recommended!" for 788 packages which sort of sounds like “You can probably update, but flashing would be a little cleaner.”
A lot of users do not visit or read the forums. At minimum, the messaging could be better.
cp -p /etc/wgetrc /etc/wgetrc.bak 2>/dev/null
echo 'user_agent = Mozilla/5.0 (X11; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0' >> /etc/wgetrc
opkg update
Code:
pli@pli-Precision-T5610:~$ ssh root@192.168.1.2
Warning: Permanently added '192.168.1.2' (ED25519) to the list of known hosts.
root@192.168.1.2's password:
root@sf8008:~# opkg update
Downloading http://feeds.openbh.net/6.0/sf8008/all/Packages.gz.
error: opkg_download_backend: Failed to download http://feeds.openbh.net/6.0/sf8008/all/Packages.gz, wget returned 8.
Downloading http://feeds.openbh.net/6.0/sf8008/cortexa15hf-neon-vfpv4/Packages.gz.
error: opkg_download_backend: Failed to download http://feeds.openbh.net/6.0/sf8008/cortexa15hf-neon-vfpv4/Packages.gz, wget returned 8.
Downloading https://raw.githubusercontent.com/oe-alliance/enigma2-settings-feed/gh-pages/Packages.gz.
Updated source 'enigma2-settings-feed'.
Downloading https://raw.githubusercontent.com/oe-alliance/3rdparty-feed/gh-pages/Packages.gz.
Updated source 'oe-alliance-3rdparty-feed'.
Downloading http://feeds.openbh.net/extra/6.0//Packages.gz.
error: opkg_download_backend: Failed to download http://feeds.openbh.net/extra/6.0//Packages.gz, wget returned 8.
Downloading http://feeds.openbh.net/picons//Packages.gz.
Updated source 'openbh-picon-feed'.
Downloading http://feeds.openbh.net/6.0/sf8008/sf8008/Packages.gz.
error: opkg_download_backend: Failed to download http://feeds.openbh.net/6.0/sf8008/sf8008/Packages.gz, wget returned 8.
Downloading http://feeds.openbh.net/6.0/sf8008/static-all/Packages.gz.
error: opkg_download_backend: Failed to download http://feeds.openbh.net/6.0/sf8008/static-all/Packages.gz, wget returned 8.
Downloading http://feeds.openbh.net/6.0/sf8008/static-cortexa15hf-neon-vfpv4/Packages.gz.
error: opkg_download_backend: Failed to download http://feeds.openbh.net/6.0/sf8008/static-cortexa15hf-neon-vfpv4/Packages.gz, wget returned 8.
Downloading http://feeds.openbh.net/6.0/sf8008/static-sf8008/Packages.gz.
error: opkg_download_backend: Failed to download http://feeds.openbh.net/6.0/sf8008/static-sf8008/Packages.gz, wget returned 8.
root@sf8008:~# cp -p /etc/wgetrc /etc/wgetrc.bak 2>/dev/null
root@sf8008:~# echo 'user_agent = Mozilla/5.0 (X11; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0' >> /etc/wgetrc
root@sf8008:~# opkg update
Downloading http://feeds.openbh.net/6.0/sf8008/all/Packages.gz.
Updated source 'openbh-all'.
Downloading http://feeds.openbh.net/6.0/sf8008/cortexa15hf-neon-vfpv4/Packages.gz.
Updated source 'openbh-cortexa15hf-neon-vfpv4'.
Downloading https://raw.githubusercontent.com/oe-alliance/enigma2-settings-feed/gh-pages/Packages.gz.
Updated source 'enigma2-settings-feed'.
Downloading https://raw.githubusercontent.com/oe-alliance/3rdparty-feed/gh-pages/Packages.gz.
Updated source 'oe-alliance-3rdparty-feed'.
Downloading http://feeds.openbh.net/extra/6.0//Packages.gz.
Updated source 'openbh-extra-feed'.
Downloading http://feeds.openbh.net/picons//Packages.gz.
Updated source 'openbh-picon-feed'.
Downloading http://feeds.openbh.net/6.0/sf8008/sf8008/Packages.gz.
Updated source 'openbh-sf8008'.
Downloading http://feeds.openbh.net/6.0/sf8008/static-all/Packages.gz.
Updated source 'openbh-static-all'.
Downloading http://feeds.openbh.net/6.0/sf8008/static-cortexa15hf-neon-vfpv4/Packages.gz.
Updated source 'openbh-static-cortexa15hf-neon-vfpv4'.
Downloading http://feeds.openbh.net/6.0/sf8008/static-sf8008/Packages.gz.
Updated source 'openbh-static-sf8008'.
root@sf8008:~#The feeds work fine for me after that small edit.
And then for an online update after making that edit, I am greeted with 788 packages. An update of this size can be done online, but careful attention to the smallest details is needed and the update needs to run in terminal. In this example, a network update cut the ssh connection, which required a reset of the connection then again running the terminal upgrade. After the terminal upgrade finished, it was ran two or three more times until opkg list-upgradable came up empty.
On reboot after the 788 online package update, a python package along with alsa needed attention. The python package was causing an enigma2 crash and halted the boot sequence. Much easier to simply load an image...
Now I understand that this image is really a beta image that is listed as a release image, which might confuse some. There are people who do not read anything and press remote buttons instead. Consider how the online update menu is laid out and worded. If you look real hard at the screenshot shown below you will find the words "Reflash recommended!" for 788 packages which sort of sounds like “You can probably update, but flashing would be a little cleaner.”
A lot of users do not visit or read the forums. At minimum, the messaging could be better.
You will find various packages won't install because libs have changed that are not updated in the feeds.
So to avoid further issues, we pulled the feeds to stop online updates, so what is the point of you posting how to then fix the feeds when it will cause issue's for others again ?
el bandido
Active member
Geez you folks have problems!
See you later.
See you later.
I really don't understand what you are trying to do.
It was you that suggested we stop online updates from being possible if it would break the images.
So we did just that, and then you explain how to fix the feeds so that online update can be used and then explain it needs to be done in telnet for it to work, which is completely and utterly pointless and just creates more confusion and problems for no reason.