Firmware 19.3_20211010 update discussion

[BigbobOz]

I must admit the infobar is one of the best features of the GUI for me and I use it quite a lot, the fact that it displays so much info but doesn't take up as much of the screen is what appeals to me, we have several tvs in the house and I can honestly say the GUI interface of the T4 is miles ahead of any of our tvs and we have an LG, Sony and a Samsung. So well done to you all that have worked on it.

Completely agree

[MarkRaymond]

I have a four year old U4, currently running Version 17.5 (20190207), with Bootloader 2017-10-18 / Kernel 4.9.51.

It would seem I have missed a few updates, even though auto-check is on ... and now I can't upgrade, either online or via USB (note: I tried twice with the USB, once with the extracted folder in the root of the USB, and once (because the name of that folder was NOT (as per the manual) "beyonwiz") with the extracted sub-folder "beyonwiz" in the root of the USB (with the original sub-folder removed).

First question: do I need a new bootloader?
Second question: if "no" to Q1, what am I doing wrong with the USB upgrade process?
Third question: will this firmware upgrade fix my original problem, which is the total loss of function of both my ICE EPG and the 'native' EPG. Apart form the Channel Up and Channel Down buttons, the only way to change channel is Menu > Channels > All > (select+) OK ... so: no way to add a recording timer ... and now my channel numbers start at 365 ...????

[MrQuade]

It would seem I have missed a few updates, even though auto-check is on .

The auto check will update within the same "series" of firmware (so all the sub versions of 17.5 for your current install), but it will not upgrade from one series to the next (eg. you can go from 17.5 to 19.3 automatically).

First question: do I need a new bootloader?

Nope.

Second question: if "no" to Q1, what am I doing wrong with the USB upgrade process?

Potentially two things.
One is that the USB *must* be formatted as FAT32, not exFAT or NTFS.

Second, the USB stick must be USB1.1 compatible. Some newer USB2 and USB3 sticks are fully backward compatible, but many arent.

Try using an older, smaller capacity stick.

Third question: will this firmware upgrade fix my original problem, which is the total loss of function of both my ICE EPG and the 'native' EPG. Apart form the Channel Up and Channel Down buttons, the only way to change channel is Menu > Channels > All > (select+) OK ... so: no way to add a recording timer ... and now my channel numbers start at 365 ...????

Likely something has corrupted itself in your current firmware install.

When you install new firmware it will wipe all settings and software, so everything should work nicely with a clean start.
Don't restore your old settings.
There is a way to save your current timers and restore only those. I might leave Grumpy Geoff to contribute there. (there is a script you can run if you want).
You will not lose any of your existing recordings by installing the new firmware from scratch.

[Grumpy_Geoff]

There is a way to save your current timers and restore only those. I might leave Grumpy Geoff to contribute there. (there is a script you can run if you want).

Yep, but I see MarkRaymond mentions using IceTV so probably not much need.

[MarkRaymond]

Thank you for your help: I noticed that the original USB stick was USB 2.0, so I found a couple of older sticks (neither of which claimed to be newer than USB 1): a Lexar and a DSE. Both have driver dates of 21/6/2006. Neither of them worked, whether plugged into the front or rear USB slots.

I have followed the instructions in the manual to a "T" ... but I note that at "Step 3", the name of the extracted folder is not "beyonwiz". Again (with the Lexar stick), I tried renaming the top folder to "beyonwiz", and then making the next folder down (already called "beyonwiz") the op folder ... all to no avail.

As far as I can tell, I have the right gear, and done all the right things ... it just doesn't work.

[MrQuade]

I have followed the instructions in the manual to a "T" ... but I note that at "Step 3", the name of the extracted folder is not "beyonwiz". Again (with the Lexar stick), I tried renaming the top folder to "beyonwiz", and then making the next folder down (already called "beyonwiz") the op folder ... all to no avail.

I think that points to your problem then. If the zip was extrcted properly, there should be no "beyonwiz" folder under any other folder.

The zip structure is \beyonwiz\u4\<lotsa files>

So that is exactly what needs to be on the USB drive when you extract the files.

What you should have done when you found the second beyonwiz folder, was move that folder and all its contents to the root of the USB drive.

[MarkRaymond]

I have tried that ... no luck.

... as for "lotsa files" in the "u4" folder, I have only 6 ... ?

Also, why is it that every time I put a USB stick into my laptop that has just been in the u4, I get a message that the USB stick is in need of "repair"??

[prl]

I have tried that ... no luck.

So there is a beyonwiz directory at the top level of the USB stick's filesystem with a u4 directory contained inside it? Not just Windows Explorer's view of what's inside the .zip file?

... as for "lotsa files" in the "u4" folder, I have only 6 ... ?

6 is the correct number. It should have these files:

Code: Select all

prl@Xerxes BWFW % ls beyonwiz/u4
imageversion     noforce          rootfs.tar.bz2
kernel.bin       partition.update update.bin
prl@Xerxes BWFW %

Also, why is it that every time I put a USB stick into my laptop that has just been in the u4, I get a message that the USB stick is in need of "repair"??

Because you are removing it from the running U4 without unmounting it first?

[MarkRaymond]

So there is a beyonwiz directory at the top level of the USB stick's filesystem with a u4 directory contained inside it? Not just Windows Explorer's view of what's inside the .zip file?

... correct. The list of the six files is also correct. And I always remove the USB stick from the u4 when it is powered down (hard).

What else can we try?

[Paul_oz53]

I have tried that ... no luck.

... as for "lotsa files" in the "u4" folder, I have only 6 ... ?

Also, why is it that every time I put a USB stick into my laptop that has just been in the u4, I get a message that the USB stick is in need of "repair"??

Hi Mark Raymond,

In this post I set out the steps I follow to reflash my U4.

Step 7 is critical. If it doesn't work the first time rename the file "noforce" to "force" and try again.

And I usually ignore the repair message with my firmware USB sticks because the stick has not been written to. Heresy I know but I'm lazy.

[prl]

Step 7 is critical.

I was going to ask about that as my next question. In particular, whether POWER was being pressed on the front panel or on the remote.

[MarkRaymond]

... except that I can't get Step SIX to actually occur ... and I have used 3x USB sticks and used all 3 USB ports (front and rear) on the device ...

[Grumpy_Geoff]

... except that I can't get Step SIX to actually occur ... and I have used 3x USB sticks and used all 3 USB ports (front and rear) on the device ...

Huh?
You can't reboot the U4 with the USB thumb drive inserted?

[6] Reboot the U4. You can do this from Menu >> Power >>Reboot if it's working or by switching off, waiting 10 or so seconds and switching on. As prl notes, switching off and on a working unit is best done with the unit in shutdown.

[Grumpy_Geoff]

... except that I can't get Step SIX to actually occur ... and I have used 3x USB sticks and used all 3 USB ports (front and rear) on the device ...

Oh, you mean step 6 from https://beyonwiz.com.au/u4/HowToUpgrade ... U4v175.pdf
"The front display will advise that an update is available and the front power button will start to blink..."

Please show us the contents of the USB thumbdrive in a Windows Explorer session.

[MarkRaymond]

So that's another failure mode ... I was always doing a "hard reboot" with the power switch at the back, so I tried the Menu > Power > Reboot method, which has also failed. Regardless of method, the box refuses to 'notice' that there's an upgrade USB stick inserted during the boot process.

Windows Explorer session pic attached.

[Grumpy_Geoff]

So that's another failure mode ... I was always doing a "hard reboot" with the power switch at the back, so I tried the Menu > Power > Reboot method, which has also failed. Regardless of method, the box refuses to 'notice' that there's an upgrade USB stick inserted during the boot process.

Windows Explorer session pic attached.

Looks okay to me.

Rename the file named "noforce" to "force".
Ensure the USB thumbdrive is in FAT32 format.
Remove all other USB devices.
Reboot.

You can also use a USB hard drive - just create a small partition (e.g. 1GB) and ensure that it is formatted as FAT32.

[MrQuade]

So that's another failure mode ... I was always doing a "hard reboot" with the power switch at the back,

Just in general operation, don't ever do that to the Wiz. Yanking power can lead to filesystem corruption which could affect the installed software or settings. In that way, the Wiz is a lot like a normal PC in that you should always shut down before powering off.

This could potentially be the cause of your current EPG problems too.

It's also a good idea to make sure all other USB devices are unplugged when you are doing upgrades. So if you have the external USB tuner, best bet is to unplug that. It doesn't always cause problems, but I know my T2, would refuse to upgrade with an external tuner plugged in.

[MarkRaymond]

Thanks, Grumpy_Geoff! The "noforce" > "force" did the trick! Although, I wasn't prompted to press the 'soft' power on button at any point. And I noticed that there was no option to unmount the USB stick while the device was running *shrugs* Still, I'm now v19.3

Thanks also to Mr Quade, of course

I'm back up and running, but it reeeeeaaaaally should take this kind of tinkering about to get things to work: even the extraction process of the zip file download from the website produces an unusable result which has to be tinkered with to correct the format. Not a good look ...

[MrQuade]

Thanks, Grumpy_Geoff! The "noforce" > "force" did the trick! Although, I wasn't prompted to press the 'soft' power on button at any point.

You saw nothing on the TV screen or on the front panel at all?

And I noticed that there was no option to unmount the USB stick while the device was running *shrugs* Still, I'm now v19.3

The option is in the main menu under the heading "Simple UMount" on the left hand side.
It can also be accessed using the BLUE button on the remote from Live TV.
It is an easy thing to miss, so definitely not your fault there.

I'm back up and running, but it reeeeeaaaaally should take this kind of tinkering about to get things to work: even the extraction process of the zip file download from the website produces an unusable result which has to be tinkered with to correct the format. Not a good look ...

When I unzip the file, it produces the correct folder structure.
In Windows Explorer, I just open the zip, then drag the beyonwiz folder onto the thumb drive.

Are you unzipping it in a different fashion?

[Grumpy_Geoff]

You saw nothing on the TV screen or on the front panel at all?

I don't believe the TV screen display states what to do, only the front panel does and you’ve only got about 8 seconds to react and press the front panel power button to begin the update. I think this is a common failure.

And I noticed that there was no option to unmount the USB stick while the device was running *shrugs* Still, I'm now v19.3

The option is in the main menu under the heading "Simple UMount" on the left hand side.
It can also be accessed using the BLUE button on the remote from Live TV.

I think it got removed from live TV BLUE sub-menu long ago. It may still have been there for 17.5-series though.

[prl]

I don't believe the TV screen display states what to do,

Correct. At that point it just shows the Beyonwiz "button" screen and no text.

only the front panel does

And all it says is "Press Button".

and you’ve only got about 8 seconds to react and press the front panel power button to begin the update.

I timed it at about 5 seconds.

So not surprisingly:

I think this is a common failure.

[Grumpy_Geoff]

I timed it at about 5 seconds.

It got quicker
I just then timed it and matched your 5 secs.

[prl]

I timed it at about 5 seconds.

It got quicker
I just then timed it and matched your 5 secs.

Much quicker and U4 users will need to borrow Gully's TARDIS to do a USB update!

[MrQuade]

I think it got removed from live TV BLUE sub-menu long ago. It may still have been there for 17.5-series though.

Ahh yes, I vaguely recall that discussion when the plugin was updated!

[Gully]

Much quicker and U4 users will need to borrow Gully's TARDIS to do a USB update!

Sorry it is in use. Please come back last year when it will be available again!

[MarkRaymond]

"I just open the zip, then drag the beyonwiz folder onto the thumb drive."

With previous updates, I just unzipped the zip file on the USB itself, and it was all good to go. Either way, even doing the above (which I had tried many times) was insufficient: changing "noforce" to "force" was the only way through this time.

I really appreciate all your efforts, thank you

Cheers, Mark

[sddawson]

While I can’t definitively point to this firmware, I've had a networking problem since I updated my boxes to use it. I originally detailed this at viewtopic.php?f=43&t=15018, and thought I'd solved it by reflashing all the boxes. But the problem came back.

I have a T3, T4 and V2. I use network browser to create mount points so each of them can access each other's Movies folder. I use all the defaults for the mounts. My T3 could access the other two. My V2 could access the other two. But my T4 could only access the T3, not the V2. That mount got the "directory does not exist" error when I tried to access the mount via the autofs folder. I reflashed the T4 to no effect. Then I reflashed the V2, and the T4 could successfully access it again.

Since I've been through this process before, I'm not exactly confident this will be a permanent "fix". Does anyone have any ideas what's going on here? Thanks.

[MrQuade]

Do you use fixed IP addresses for all your Wiz boxes? Either fixed dhcp lease (preferred) or static assignment?

[sddawson]

Do you use fixed IP addresses for all your Wiz boxes? Either fixed dhcp lease (preferred) or static assignment?

Yep, all fixed.

[sddawson]

No more thoughts anyone?

[dRdoS7]

No more thoughts anyone?

Sorry, I was asleep.

I did think I'd like to buy the new Everest, when it's released.

[sddawson]

Sorry, I was asleep.

I did think I'd like to buy the new Everest, when it's released.

I, too, had some thoughts that had nothing to do with Beyonwiz. Strange eh?

Looking back, my “All fixed” comment might have been construed as saying my problem was fixed. However, it meant that all my IP addresses were fixed at the time of the problem.

[Grumpy_Geoff]

No more thoughts anyone?

Whilst using AUTOFS, show us the contents of /etc/auto.network

What happens if you go back to using FSTAB on the recalcitrant box(es).

[sddawson]

Whilst using AUTOFS, show us the contents of /etc/auto.network

What happens if you go back to using FSTAB on the recalcitrant box(es).

Right now, everything is working after the latest reflash. If it happens again I will do that. But, forgive my ignorance, what’s the best way of getting the contents of that file?

When the problem occurs, FSTAB mounts do work, and I can see the content of the mount. But if I try to play a recording, it plays very sporadically, continuously freezing.

Thanks for the help.

[MrQuade]

Looking back, my “All fixed” comment might have been construed as saying my problem was fixed. However, it meant that all my IP addresses were fixed at the time of the problem.

I figured that's what you meant, I just had no further suggestions.

If it is now working, the trick is to monitor the situation and take note of any changes that happen to your network and Beyonwiz environment.
Something seems to be ocurring that is triggering this to stop working for you, so it is a matter of figuring out what that is.

Take note of any router reboots, new plugins installed, changes to mount configurations, changes to SMB config files, new devices on the network, anything.

[sddawson]

.

Take note of any router reboots, new plugins installed, changes to mount configurations, changes to SMB config files, new devices on the network, anything.

Thanks - I’ll do my best. It’s a strange one!

[Grumpy_Geoff]

Whilst using AUTOFS, show us the contents of /etc/auto.network

What happens if you go back to using FSTAB on the recalcitrant box(es).

Right now, everything is working after the latest reflash. If it happens again I will do that. But, forgive my ignorance, what’s the best way of getting the contents of that file?

Probably the easiest method is to fetch it using OpenWebif from a browser - http://beyonwizt4/file?file=/etc/auto.network
Otherwise you can use File Commander to copy it off to a USB thumb drive or to an easily accessible network location (e.g. the "Movie" share), or use File Commander to view it (TEXT button) and take a screenshot.
The contents may not reveal any obvious errors, but let's have a gander just in case there's something funny there.

[sddawson]

Probably the easiest method is to fetch it using OpenWebif from a browser - http://beyonwizt4/file?file=/etc/auto.network
Otherwise you can use File Commander to copy it off to a USB thumb drive or to an easily accessible network location (e.g. the "Movie" share), or use File Commander to view it (TEXT button) and take a screenshot.
The contents may not reveal any obvious errors, but let's have a gander just in case there's something funny there.

Great - thanks. Now it’s a waiting game to see if it happens again…

[Grumpy_Geoff]

Great - thanks. Now it’s a waiting game to see if it happens again…

You can grab it now and attach it here, the contents won't change until you change a mount definition.

[sddawson]

You can grab it now and attach it here, the contents won't change until you change a mount definition.

Doesn't look like much to see at the moment. At the time of the last failure, "bedroom" couldn’t see "family", but "family" could see "bedroom".

[Grumpy_Geoff]

Doesn't look like much to see at the moment. At the time of the last failure, "bedroom" couldn’t see "family", but "family" could see "bedroom".

Yep, simple mounts.
So you don't have any computer shares you can also mount as a test (at time of failure)?
The next time one of the mounts plays up, see if you can open that same share via Windows command prompt -
e.g. for the "Movie" share on the "Theatre" Wiz -

Code: Select all

ping 192.168.0.221
start \\192.168.0.221\Movie

(the "start" command will open a File Explorer session on the share)
You can also enter the same URI in the File Explorer address bar (\\192.168.0.221\Movie).

So these IP addresses -
"Theatre" on 192.168.0.221
"Family" on 192.168.0.237
"Bedroom" on 192.168.0.234
...are all assigned by your router, using MAC-to-IP address (DHCP) reservation? That's what you mean by "fixed"?

Do you have any custom Wiz shares defined via file - /etc/samba/smb-user.conf on one or more of these Wizes?

[sddawson]

Yep, simple mounts.
So you don't have any computer shares you can also mount as a test (at time of failure)?
The next time one of the mounts plays up, see if you can open that same share via Windows command prompt -
e.g. for the "Movie" share on the "Theatre" Wiz -

Code: Select all

ping 192.168.0.221
start \\192.168.0.221\Movie

(the "start" command will open a File Explorer session on the share)
You can also enter the same URI in the File Explorer address bar (\\192.168.0.221\Movie).

Good idea. I use Mac, but I can usually mount the Movie folder. I’ll try it if/when the problem re-appears.

So these IP addresses -
"Theatre" on 192.168.0.221
"Family" on 192.168.0.237
"Bedroom" on 192.168.0.234
...are all assigned by your router, using MAC-to-IP address (DHCP) reservation? That's what you mean by "fixed"?

That’s correct.

Do you have any custom Wiz shares defined via file - /etc/samba/smb-user.conf on one or more of these Wizes?

No, I’ve never done that.

[Grumpy_Geoff]

Good idea. I use Mac, but I can usually mount the Movie folder. I’ll try it if/when the problem re-appears.

MacOS Finder will have the same sort of mechansism. That test prove the IP address is fine and also that the target SMB server is still running.
I'm clutching at straws.

[sddawson]

MacOS Finder will have the same sort of mechansism. That test prove the IP address is fine and also that the target SMB server is still running.
I'm clutching at straws.

Yeh. I’ll post back if it re-occurs. Thanks for the tips.

[sddawson]

MacOS Finder will have the same sort of mechansism. That test prove the IP address is fine and also that the target SMB server is still running.
I'm clutching at straws.

It's happening again:

T3 can see mounts on V2 and T4.
V2 can see mounts on T3 and T4.
T4 can see mounts on T3.
T4 CANNOT see mounts on V2 - "directory does not exist" error.

I tried mounting via Mac OS Finder, which is interesting:
T3 and T4 mount immediately.
V2 mounts, but only after a 30 second delay. I'm guessing the "directory does not exist" error happens after a shorter timeout than that.

As a test, I Ethernet-connected the laptop to the same switch as the T3:
The T3 connects to the V2 immediately.
The laptop still has a 30 second delay before it connects to the V2.

With the laptop Ethernet-connected to the same switch as the T4:
T4, as usual, can’t connect to the V2.
The laptop connects after 30 seconds.

I just don't know what to make of all this. I can find no logical explanation why only one of the 3 boxes can’t connect to the V2, or why the laptop has such a long delay connecting to it all the time, when the T3 connects to it perfectly.

I can say I've only seen this behaviour on the latest firmware, but who knows whether that has caused the problem. I sincerely hope someone can come up with a path to follow...

Thank you.

[Paul_oz53]

My T4 has been misbehaving for the last few weeks. Terrible network connectivity. Today I reflashed the firmware and set it up manually - didn't restore settings.

Recreated the network shares and now it works fine using FSTAB and samba 1.0.

[sddawson]

My T4 has been misbehaving for the last few weeks. Terrible network connectivity. Today I reflashed the firmware and set it up manually - didn't restore settings.

Recreated the network shares and now it works fine using FSTAB and samba 1.0.

I’ve reflashed in the past to fix the problem, but after some time it just comes back…

[Paul_oz53]

My T4 has been misbehaving for the last few weeks. Terrible network connectivity. Today I reflashed the firmware and set it up manually - didn't restore settings.

Recreated the network shares and now it works fine using FSTAB and samba 1.0.

I’ve reflashed in the past to fix the problem, but after some time it just comes back…

Have to agree that something about 20211010 resulted in flaky networking. OK for a while but then goes AWOL.

And I have had frustrating periods where one device can see another but the reverse is not true. Particularly the U4s. I tend to work around the flakiness.

[sddawson]

Have to agree that something about 20211010 resulted in flaky networking. OK for a while but then goes AWOL.

And I have had frustrating periods where one device can see another but the reverse is not true. Particularly the U4s. I tend to work around the flakiness.

Hard to work around when you’re better half is wondering why she suddenly can’t watch a recording that was done on another box. Apart from “give me half an hour and I’ll reflash a box and reinstall a plug-in”! It is very frustrating, doubly so when it’s so intermittent and not everyone seems to suffer from it. But it’s always nice to know it’s not just me. Thanks for the input.