Topic: V1.11 Now takes 2m 37s to boot. Normal? | Allen & Heath Digital Community

V1.11 Now takes 2m 37s to boot. Normal?

This topic contains 6 replies, has 4 voices, and was last updated by antonyja 11 years, 1 month ago.

Viewing 7 posts - 1 through 7 (of 7 total)

Author

Posts
2013/03/20 at 2:33 am #23684

John-S
Participant

I updated my GLD from V1.10 to V1.11 tonight. now it needs 2 min 37 sec to boot every time. There is nothing connected to the surface beside the power cord. I have not played with the network settings. It is default from the factory.

For over a minute there is a flashing dash in the upper left of the screen.

I performed three proper shut downs and restarts thinking it needed to reflash something inside but it always is 2m 37s to boot.

Is this the new normal?

Thank you,

John

2013/03/20 at 2:53 am #33515

John-S
Participant

So I re-downloaded the V1.11 firmware, formatted my usb drive and reflashed the GLD80 with v1.11 firmware. The first reboot took 2m 43s. The second reboot took 2m 37s.

I used a 2Gig usb device that I have used for years on many projects.

The touch screen is very unresponsive too.

I looked for V1.10 to down revision and see if there is a performance difference but could not find V1.10 on the A&H site. Can I receive V1.10 to down rev and test please?

The long reboot worries me. It does seem to wake up ready to work but I do not know for sure.

John

2013/03/20 at 4:05 am #33516

John-S
Participant

I read elsewhere that if DHCP was enabled the boot times are very long. I checked to find that DHCP was set to ON after the update. I turned it off and the boot times returned to normally fast.

Be warned all my fellow updaters. Check the DHCP
Setup/Config/Network/DHCP Enabled must NOT be green.

John

2013/03/20 at 5:01 am #33517

Chris93
Participant

It may be because it’s trying to update the firmware on the input racks during the boot process, but it can’t see any.

Chris

2013/03/20 at 2:41 pm #33521

John-S
Participant

deleted content of response. John

2013/03/20 at 10:21 pm #33522

gilparente
Participant

Its just a DHCP thing.
The firmware update automatically enables DHCP. And i guess the console just takes that long to either acquire address or realize it doesnt have to.
Had that happen to 2 clients and the one we have.

Gil Parente
Design & Integration
Entertainment Arts, Inc.
iLive 176, T112
iDR48 , iDR16, iDR10
Multiple iPads
Dante
Etc..

2013/03/21 at 8:25 am #33524

antonyja
Participant

This is getting very strange. We don’t know how DHCP would be getting enabled from a firmware update. The network settings live in a standard Ubuntu file /etc/network/interfaces, this file should not be touched during a firmware update. What is more, for it to change to DHCP it would need to have a line in this file changed from “iface eth0 inet static” to “iface eth0 inet dhcp”, so as you can see it is not just a simple boolean. We do many firmware updates here and have never had this issue, but too many of you are now reporting it to be coincidence, so if any of you experience this in the future could you give technical support detailed information, i.e. network settings prior to firmware update, firmware updating from and to, does it retain the setting for static setup, or does it change to some sort of default?

Antony Jackson
Software Manager
Allen & Heath Limited
Author

Posts