6 minutes ago, tmorse305 said:

I'm running 5.3.0 and 3.0.41.  I saw the upgrade message in the AC regarding the newer version for IoP.  I'm so glad I checked the forum before pushing the button.  I have version 100 of the Bios.  Should I just wait for the dust to settle a little more before upgrading?  One concern, I know there are new versions of the NSs I'm using out there.  Some require 5.4.0.  If I have to reboot a NS or Polisy will the NS update even though it's not compatible with my current version of IoP?

Thank you

I have an early version Polisy, I think from the second shipping.  I upgraded via the ssh method and got busy with other things for a long time and didn't pay much attention. (My Polisy is downstairs near the ceiling and requires a ladder of stool to push buttons or see the lights... so I paid no attention to them or beeps).  At the end of the process the Polisy rebooted on it's own, (after the ISY restart)... and all was well. 

The moral of the story is don't intervene... just let it do it's thing.  If you think you need to intervene, open a ticket and ask before pulling the plug.

Michel indicates above that if you were one of the first 30 shipped there might be an issue... that batch was probably the ones where a board was dislodged during shipment and Polisy had to be opened to re-seat it.

@tmorse305 Don't confuse "version 100" with bios ver: 1.0.0  which is what we're upgrading from and bios ver: 1.1.3 is where we're headed to.

9 minutes ago, mmb said:

Don't confuse "version 100" with bios ver: 1.0.0  which is what we're upgrading from and bios ver: 1.1.3 is where we're headed to.

 @mmbAren't they both referencing the same thing?

@tmorse305 yes, this is the full context.

Tue Mar  8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0  
Tue Mar  8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded  
Tue Mar  8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: starting forcing bios update  
Tue Mar  8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices  
Tue Mar  8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy  
Tue Mar  8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0  

flashrom  on FreeBSD 13.0-RELEASE-p6 (amd64)
flashrom is free software, get the source code at https://flashrom.org

Using default programmer "internal" with arguments "".
Using clock_gettime for delay loops (clk_id: 4, resolution: 2ns).
coreboot table found at 0xcfec5000.
Found chipset "AMD FCH".
Enabling flash write... OK.
Found Adesto flash chip "AT25SF641" (8192 kB, SPI) mapped at physical address 0x00000000ff800000.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.
Tue Mar  8 16:30:44 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios update ... rebooting  

[blah blah blah]

Tue Mar  8 16:32:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices  
Tue Mar  8 16:32:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy  
Tue Mar  8 16:32:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3  
Tue Mar  8 16:32:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version  

 

 @mmbAren't they both referencing the same thing?

Yup. Version 100 appears to be the shortcut message the Bios writing code was installed with to describe v1.0.0 when the bios upgrade fails.




Sent from my SM-G781W using Tapatalk

@larryllix Sorry I find this thread interesting.  Can you tell from the logs where your update fails? 

Fyi I posted my successful update above.

1 hour ago, mmb said:

Don't confuse "version 100" with bios ver: 1.0.0  which is what we're upgrading from and bios ver: 1.1.3 is where we're headed to.

 

1 hour ago, mmb said:

yes, this is the full context.

@mmb, So what exactly should I not be confused about?

@larryllix Sorry I find this thread interesting.  Can you tell from the logs where your update fails? 
Fyi I posted my successful update above.

Yup. Software tries and retries to erase chip using techniques for 4K, 8k, 16k, 32k etc.. size chips. When it cannot find a space left in the chip the flash process cannot continue.

It then reports that the version 100 needs to be replaced. Then a partial v5.4 1 becomes unstable and refuses to function properly.

Likely if I could reload an older IoP I could get back up but it contained so many crippling bugs, so I tried my polisy spare. It seemed to function for a while but got bad when I rebooted it. That one upgraded the bios ok but no previous version is available to manually load.

Back to ISY994.

In the words of Johann Sebastian....
...I'll be Bach!

Sent from my SM-G781W using Tapatalk

I received my Polisy in January and I believe that it already had UEFI installed, because I was able to go into the TPM setting to set a password in Administrative Console (I didn't set one yet) prior to the latest update which forced UEFI.

 

@tmorse305 You said I have version 100 of the Bios.  Should I just wait for the dust to settle a little more before upgrading? 

I'm saying this is the expected notification of bios version before upgrading.

So should you wait for the dust to settle?

Up to you but it is the path forward.

@larryllix Very interesting, thanks for the information.

 

@brians You can confirm by checking the log file as Michel noted and if you're comfortable with SSH.

5 minutes ago, mmb said:

@brians You can confirm by checking the log file as Michel noted and if you're comfortable with SSH.

I already did that to confirm, was meaning that I believe it was already installed from time of purchase. Prior to 5.4.1 we could determine if had UEFI by whether or not the TPM option was enabled and mine was. If new people are reading this looking at Polisy but are a bit hesitant because of some of the issues, then they shouldn't have to if UD is in fact shipping them out brand with with UEFI.

Edited March 11, 20223 yr by brians

@tmorse305 You said I have version 100 of the Bios.  Should I just wait for the dust to settle a little more before upgrading? 
I'm saying this is the expected notification of bios version before upgrading.
So should you wait for the dust to settle?
Up to you but it is the path forward.

I think it is not the bios firmware, but rather the size of the early bios chips not being able accommodate both bioses until the flash burning is done and the old bios can be erased....or hidden?

Sent from my SM-G781W using Tapatalk

1 hour ago, larryllix said:

I think it is not the bios firmware, but rather the size of the early bios chips not being able accommodate both bioses
 

Could be, I've done a lot of manual flashes and the likelihood of pooching the flash memory is definitely a concern. Hope you get yours straightened out...

I was getting ready to update from 5.4.0 but ran "sudo cat /var/udx/logs/log | grep bios" first.  I am wondering if anyone else's came up with "wrong part?"  I am a little worried about whether I should upgrade or not.

[admin@polisy ~]$ sudo cat /var/udx/logs/log | grep bios
Password:
Sat Feb 19 08:51:51 PST 2022: bios mfr:
Sat Feb 19 08:51:51 PST 2022: bios product:
Sat Feb 19 08:51:51 PST 2022: bios has wrong mfr/product
Sat Feb 19 09:05:24 PST 2022: bios mfr:
Sat Feb 19 09:05:24 PST 2022: bios product:
Sat Feb 19 09:05:24 PST 2022: bios has wrong mfr/product
Sat Feb 19 11:20:10 PST 2022: bios mfr:
Sat Feb 19 11:20:10 PST 2022: bios product:
Sat Feb 19 11:20:10 PST 2022: bios has wrong mfr/product
Sun Feb 27 06:54:52 PST 2022: bios mfr:
Sun Feb 27 06:54:52 PST 2022: bios product:
Sun Feb 27 06:54:52 PST 2022: bios has wrong mfr/product
Sun Feb 27 16:03:24 PST 2022: bios mfr:
Sun Feb 27 16:03:24 PST 2022: bios product:
Sun Feb 27 16:03:24 PST 2022: bios has wrong mfr/product
Sun Mar  6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Sun Mar  6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Sun Mar  6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0
Sun Mar  6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded
Sun Mar  6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Sun Mar  6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Sun Mar  6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0
Sun Mar  6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded
Sun Mar  6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Sun Mar  6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Sun Mar  6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0
Sun Mar  6 06:42:26 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded
[admin@polisy ~]$

 

29 minutes ago, TJF1960 said:

I was getting ready to update from 5.4.0 but ran "sudo cat /var/udx/logs/log | grep bios" first.  I am wondering if anyone else's came up with "wrong part?"  I am a little worried about whether I should upgrade or not.

[admin@polisy ~]$ sudo cat /var/udx/logs/log | grep bios
Password:
Sat Feb 19 08:51:51 PST 2022: bios mfr:
Sat Feb 19 08:51:51 PST 2022: bios product:
Sat Feb 19 08:51:51 PST 2022: bios has wrong mfr/product
Sat Feb 19 09:05:24 PST 2022: bios mfr:
Sat Feb 19 09:05:24 PST 2022: bios product:
Sat Feb 19 09:05:24 PST 2022: bios has wrong mfr/product
Sat Feb 19 11:20:10 PST 2022: bios mfr:
Sat Feb 19 11:20:10 PST 2022: bios product:
Sat Feb 19 11:20:10 PST 2022: bios has wrong mfr/product
Sun Feb 27 06:54:52 PST 2022: bios mfr:
Sun Feb 27 06:54:52 PST 2022: bios product:
Sun Feb 27 06:54:52 PST 2022: bios has wrong mfr/product
Sun Feb 27 16:03:24 PST 2022: bios mfr:
Sun Feb 27 16:03:24 PST 2022: bios product:
Sun Feb 27 16:03:24 PST 2022: bios has wrong mfr/product
Sun Mar  6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Sun Mar  6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Sun Mar  6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0
Sun Mar  6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded
Sun Mar  6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Sun Mar  6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Sun Mar  6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0
Sun Mar  6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded
Sun Mar  6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Sun Mar  6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Sun Mar  6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0
Sun Mar  6 06:42:26 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded
[admin@polisy ~]$

 

Upgrading the bios is part of the upgrade. Most who have done the upgrade have had no problems. The few that have, were part of a group that took delivery of very early Polisy. A few post above is an in depth explanation from Michel at UD.

I have upgraded two Polisy using ssh with no issue with the bios not upgrading.

Hi @DennisC, I have read the this thread. My major concern is that I hadn't seen anyone mention getting the "wrong part" listed in the console. I don't want to upgrade and take a chance of being in the same boat as Larry above. Also, I don't know what the time frame is for the early units that was referred to? I think I bought mine in the first half of last year.

6 minutes ago, TJF1960 said:

I don't know what the time frame is for the early units that was referred to?

the first 30 shipped, the very first batch.  so not yours.

I suspect, but it's only a guess, is that the error message you're seeing is based on the fact the bios version has been replaced, therefor the version installed is now "wrong"...

Edited March 12, 20223 yr by MrBill

Awesome, thank you @DennisC and @MrBill for putting my mind at ease!

Here  I go, No guts no glory, as they say.

9 minutes ago, TJF1960 said:

Awesome, thank you @DennisC and @MrBill for putting my mind at ease!

Here  I go, No guts no glory, as they say.

Just don't give up too soon.  Let it be... it takes awhile... don't interrupt it.

Success! From start to finish was 8 minutes.

Thank you both very much!

 

Sat Mar 12 07:10:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: starting forcing bios update
Sat Mar 12 07:10:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Sat Mar 12 07:10:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Sat Mar 12 07:10:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0
Sat Mar 12 07:10:47 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios update ... rebooting
Sat Mar 12 07:12:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Sat Mar 12 07:12:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Sat Mar 12 07:12:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3
Sat Mar 12 07:12:05 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version

 

 

@Michel Kohanim

I have two Polisy running, one on version 5.4.1.1 and one on 5.4.1_2.

The one running v5.4.1.1 is at my second location and handled the change to Daylight Saving Time without a problem, however, it has sunrise at 08:12:30 am and sunset at 08:00:17 pm.

The one at my main location running 5.4.1._2 had an issue with the change to Daylight Saving Time. None of the scheduled programs ran this morning. A check of next run time indicate none of my scheduled programs were to run today. They were all set to run tomorrow. A reboot of Polisy corrected this issue.

However, it has sunrise at 08:12:30 am and sunset at 08:00:17 pm. On both Polisy, the sunrise and sunset readings are taken from the banner at the top of the page.

According to google, sunrise today was at  07:11 am and sunset is at 07:01 pm.

Both Polisy have the correct time and the correct DST rule set in location on the Configuration page. 

Checking my programs that are scheduled to run off of sunset indicate the correct next run time based on google's time of sunset.

My ISY994 has the correct time for sunrise/sunset (v 5.3.4), and my IoP has sunrise/sunset an hour later (v 5.4.1_2).  The 'date' command on my Polisy indicates that the time on the machine is correct.

59 minutes ago, DennisC said:

@Michel Kohanim

I have two Polisy running, one on version 5.4.1.1 and one on 5.4.1_2.

The one running v5.4.1.1 is at my second location and handled the change to Daylight Saving Time without a problem, however, it has sunrise at 08:12:30 am and sunset at 08:00:17 pm.

The one at my main location running 5.4.1._2 had an issue with the change to Daylight Saving Time. None of the scheduled programs ran this morning. A check of next run time indicate none of my scheduled programs were to run today. They were all set to run tomorrow. A reboot of Polisy corrected this issue.

However, it has sunrise at 08:12:30 am and sunset at 08:00:17 pm. On both Polisy, the sunrise and sunset readings are taken from the banner at the top of the page.

According to google, sunrise today was at  07:11 am and sunset is at 07:01 pm.

Both Polisy have the correct time and the correct DST rule set in location on the Configuration page. 

Checking my programs that are scheduled to run off of sunset indicate the correct next run time based on google's time of sunset.

Have the same problem and cannot find the combination to change.  Yesterday my time zone was set at -5 which is correct.  This morning for the same lat and long it is -4.