Cold and Warm (re)boot NVROM parsing
Posted: Sat Jul 30, 2011 9:24 am
Hello,
there seems to be some different behaviour with the parsing of NVROM (aka SYS:Kickstart/nvrom.txt) between cold and warm reboots.
Cold reboot:
The NVROM seems to be parsed, everyting's perfect. My variables can be seen in screenshot "kb.png".
Warm reboot:
Due to the fact that the kick modules aren't loaded (again) here - of course, it's a warm reboot - the NVROM didn't seem to get parsed. This leads to rather long reboot times, 'cos the kickstart is scanning the 3112-SATA bus for devices and doesn't seem to know anything about my NV variables. After the reboot my "variables" look like this (see "wb.png"). This is only an example, sometimes Ranger shows nothing here or total rubbish entries (like NAME "2????x323o0"/VALUE "ae22??..." ), maybe the corresponding memory area is trashed/overwritten...
there seems to be some different behaviour with the parsing of NVROM (aka SYS:Kickstart/nvrom.txt) between cold and warm reboots.
Cold reboot:
The NVROM seems to be parsed, everyting's perfect. My variables can be seen in screenshot "kb.png".
Warm reboot:
Due to the fact that the kick modules aren't loaded (again) here - of course, it's a warm reboot - the NVROM didn't seem to get parsed. This leads to rather long reboot times, 'cos the kickstart is scanning the 3112-SATA bus for devices and doesn't seem to know anything about my NV variables. After the reboot my "variables" look like this (see "wb.png"). This is only an example, sometimes Ranger shows nothing here or total rubbish entries (like NAME "2????x323o0"/VALUE "ae22??..." ), maybe the corresponding memory area is trashed/overwritten...