Quantcast
Channel: Linux Device Hacking
Viewing all articles
Browse latest Browse all 47589

Re: Can boot, but cannot reboot

$
0
0
Sherman,

It's likely that the brand of your USB stick. Some takes longer to be reset. In the past, people have discovered this problem, some sticks are OK with cold boot, but have problem with warm boot. The most reliable brand is Sandisk (based on my own experience, and other reports). Your log showed that in the warm boot, the USB stick was timed out during "usb start".

However, there is a work around to try and see it will get around this USB stick slow reset. You can try it before resorting to switching to a different USB thumb.

In your uBoot envs:
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset
the workaround is to change it to have 3 "usb start"
bootcmd=usb start; usb start; usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset

Be careful when you set this in Debian (typo would prevent booting) using the fw_setenv command:
fw_setenv bootcmd 'usb start; usb start; usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset'

I should note that: adjust your current bootcmd to have 3 "usb start". Yours might be different than my bootcmd above.


You should make sure that you can interrupt netconsole and issue commands before trying this (in case any unforseen problem occur then you can fix it in uBoot command prompt)

Viewing all articles
Browse latest Browse all 47589

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>