Devin Reade <gdr at gno.org> wrote:
>> Landon Curt Noll <soekris-mail at asthe.com> wrote:
>>
>> We recently received two net5501-70 units (S/N 229935 and 229936).
>> They experience problems on booting after the unit has been powered
>> down for a bit.
>
> I experienced a similar problem using large-ish SSD drives
> (Intel X25-V 40GB) where on a boot-from-lengthy-powerdown they
> would sometimes be unrecognised, but were fine during a regular
> cold or warm reboot.
>
> With the help of some on this list, I came to the conclusion that
> the SSDs needed more power-up time than the 5501s were giving them.
> I've avoided the problem now by a combination of the following:
>
> + increasing the boot delay in the combios to at least 15 seconds
The boot delay occurs after the memory scan and AFTER comBIOS fails to find a
master and slave drive.
In our case, boot delay occurs too late. The comBIOS believes we do not have
any disks:
comBIOS ver. 1.33 20070103 Copyright (C) 2000-2007 Soekris
Engineering.
net5501
0512 Mbyte Memory CPU Geode LX 500 Mhz
((comBIOS delays about 12 seconds and then prints:))
Pri Sla CHS -- Mbyte <<====
no Master or Slave drive
Slot Vend Dev ClassRev Cmd Stat CL LT HT Base1 Base2 Int
---
X Seconds to automatic boot. Press Ctrl-P for entering Monitor. <<===
this is where boot delay occurs
No Boot device available, enter monitor.
comBIOS Monitor. Press ? for help.
>
We tried your idea above. However it failed to solve the cold power-on boor
problem.
> + set BootDrive=80 80 80 80
A nice trick but ineffective in our case. Since comBIOS believes there is no
master drive,
asking comBIOS to try drive 80 4 times produced the same failed boot:
No Boot device available, enter monitor.
We tried your idea above. However it failed to solve the cold power-on boor
problem.
> + set PXEBoot=Disabled
In this case there is no F0 so PXEBoot has no effect. And moreover, the
failure of comBIOS
to find a Master and Slave drive happens well before any PXEBoot would occur
even if
F0 were in the BootDrive order.
We tried your idea above. However it failed to solve the cold power-on boor
problem.
> + ensuring that you have the newest combios version installed (1.33c)
> My boxes, which are only about a year or two old, still had
> 1.33.
We are running v1.33. Are there significant bug fixes between v1.33 and v1.33c?
You BIOS update suggestion here might be worth testing. Maybe v1.33c has a fix
we need?
Thanks for making some suggestions.
chongo (Landon Curt Noll) /\oo/\
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech
