Re: BeagleBoard stops at booting kernel with 2.6.37-rc5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Robert Nelson had written, on 12/16/2010 02:25 PM, the following:
On Thu, Dec 16, 2010 at 2:19 PM, Elvis Dowson <elvis.dowson@xxxxxxx> wrote:
Hi,
       I'm working with linux mainline 2.6.37-rc5 and my custom beagleboard based platform stops at booting the kernel. Is there a fix for this?

reading uImage

2432692 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
  Image Name:   Linux-2.6.37-rc5
  Image Type:   ARM Linux Kernel Image (uncompressed)
  Data Size:    2432628 Bytes =  2.3 MB
  Load Address: 80008000
  Entry Point:  80008000
  Verifying Checksum ... OK
  Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


If it stops there, double check your bootarg's as with 2.6.37+ you
might be using the omap-serial vs the old generic serial driver...
"ttyO2" (O in Omap) vs "ttyS2"..

one more thing: in fs - getty dependency might exist - you could choose something similar to what I did on my bare busybox install:
http://nishanthmenon.blogspot.com/2010/10/tired-of-ttysx-and-ttyox.html

--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux