Re: [Gumstix-users] Bootable SD card for Overo Fire

[sturnfie <stu...@gm...>]

McPherson, Charles A wrote
> 
> I won't get back into work until Monday or Tuesday, but where can I find
> the u-boot variables?
> 
> Thanks,
> Charles
> 

Hi Charles,

Typically, the u-boot variables are read from the NAND (even if you are
booting u-boot from an MMC). Most convenient access method is found during
boot. If you have a serial console during boot, you're likely to see x-load,
then u-boot starting, then a countdown, then the beginning of the extraction
of the linux kernel. 

During the countdown, send a keystroke to interrupt the countdown and you'll
be at a command line running in something of a u-boot shell. The command
"printenv" will list the u-boot variables.

There are plenty of things that are configurable. See the following list:
http://www.denx.de/wiki/DULG/UBootEnvVariables

I'm surprised to see a runlevel 1 boot. It, however, might be due to some
way the system is set to configure itself on first boot. The runlevel 1
would be configured in the "bootargs" variable; the configuration passed to
the kernel. 

Runlevels are more of a convention than a hard-rule, but typically a system
with full functionality enabled uses a runlevel of 3 or 5.  Check your
/etc/init.d to see what is set to run in runlevel 1, and compare that to see
what is running at runlevel 5.

The error to me read that there was nothing starting at runlevel 1, so the
system halted. Passing a "5" at the end of the bootargs string would be
sufficient to set the proper runlevel, if this is indeed the cause of the
error..

Reference:
http://en.wikipedia.org/wiki/Runlevel
http://www.ghacks.net/2009/04/04/get-to-know-linux-the-etcinitd-directory/

Lucas

-----
-- 
Lucas Sturnfield
stu...@gm...

--
View this message in context: http://gumstix.8.n6.nabble.com/Bootable-SD-card-for-Overo-Fire-tp1799422p1883139.html
Sent from the Gumstix mailing list archive at Nabble.com.