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 ?