Front panel boot progress for U4

[prl]

You can get the Loading NN% boot progress on the U4 front panel with the following two changes:

Code: Select all

root@beyonwizu4:~# diff -u /etc/init.d/rc.bak /etc/init.d/rc
--- /etc/init.d/rc.bak
+++ /etc/init.d/rc
@@ -33,6 +33,8 @@
         echo $(($progress / 2)) > /proc/progress
     elif [ $progress -gt 0 -a -e /proc/vfd ]; then
         echo Loading $(($progress / 2))% > /proc/vfd
+    elif [ $progress -gt 0 -a -e /dev/dbox/oled0 ]; then
+        echo Loading $(($progress / 2))% > /dev/dbox/oled0
     elif [ $progress -gt 0 -a -e /usr/bin/displayvfd ]; then
         displayvfd -s 18 -t "Booting $progress"
     elif [ $progress -gt 0 -a -e /dev/mcu ]; then
root@beyonwizu4:~#

Code: Select all

Cambyses:python prl$ git diff Tools/Profile.py 
diff --git a/lib/python/Tools/Profile.py b/lib/python/Tools/Profile.py
index fc1f2076f..556261186 100644
--- a/lib/python/Tools/Profile.py
+++ b/lib/python/Tools/Profile.py
@@ -47,6 +47,8 @@ def profile(id):
                dev_fmt = ("/dev/mcu", "%d  \n")
        elif box_type == "ebox5000":
                dev_fmt = ("/proc/progress", "%d")
+       elif box_type == "beyonwizu4":
+               dev_fmt = ("/dev/dbox/oled0", "Loading %d%%\n")
        elif getMachineBuild() in ("inihdp", "inihdx"):
                dev_fmt = ("/proc/vfd", "Loading %d%%\n")
        else:
Cambyses:python prl$

Where do I submit the changes for /etc/init.d/rc?

[adoxa]

I thought a year ago that it was part of sysvinit, so it would be up to peteru to change.

[adoxa]

Where do I submit the changes for /etc/init.d/rc?

oe-alliance-core by the looks.

[prl]

Looks like. I don't see a pull request there though. Peteru has already merged the changes to Tools.Profile.

[Grumpy_Geoff]

Looks like. I don't see a pull request there though. Peteru has already merged the changes to Tools.Profile.

The 20190715 update has the loading progress on the U4 now, in case you didn't know.

[peteru]

Both changes rolled out in beta release from last night.

[prl]

Looks like. I don't see a pull request there though. Peteru has already merged the changes to Tools.Profile.

The 20190715 update has the loading progress on the U4 now, in case you didn't know.

I'd only done the upgrade on my test V2. I've upgraded the U4 now, and you're quite right.

[Gully]

Both changes rolled out in beta release from last night.

Haven't tried this yet but out of interest are there any fixes for the problem with the 19.3 20190630 firmware hanging on the previous online update or is the only solution a USB "upgrade" of that version to 19.3 20190712?

[prl]

Haven't tried this yet but out of interest are there any fixes for the problem with the 19.3 20190630 firmware hanging on the previous online update or is the only solution a USB "upgrade" of that version to 19.3 20190712?

Not that I know of. I've done all subsequent online updates from a 20190712 USB upgrade base.

I wouldn't have confidence in doing online updates from a 20190630 base.

[Gully]

Not that I know of. I've done all subsequent online updates from a 20190712 USB upgrade base.

So have I now (AFAIK there has only been this one).

I wouldn't have confidence in doing online updates from a 20190630 base.

I wouldn't take the chance either but I asked the question as I hadn't seen it addressed it so far.

[peteru]

The existing firmware has an issue that prevents it from completing the update. So, there's no easy fix for the existing systems, other than doing a USB update to ensure a good install.

It would be good to track down why the update is failing and fix the cause, so that future updates don't fail the same way, but I don't have the time to do that. I'd be quite happy if someone else did at least the initial investigation to narrow it down - preferably in it's own thread.

[Gully]

The existing firmware has an issue that prevents it from completing the update. So, there's no easy fix for the existing systems, other than doing a USB update to ensure a good install.

It would be good to track down why the update is failing and fix the cause, so that future updates don't fail the same way, but I don't have the time to do that. I'd be quite happy if someone else did at least the initial investigation to narrow it down - preferably in it's own thread.

Thanks for the clarification.