Re: BeagleBoard stops at booting kernel with 2.6.37-rc5

2010-12-16 Thread Robert Nelson
On Thu, Dec 16, 2010 at 2:19 PM, Elvis Dowson elvis.dow...@mac.com 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 8200 ...
   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..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: BeagleBoard stops at booting kernel with 2.6.37-rc5

2010-12-16 Thread Nishanth Menon

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.dow...@mac.com 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 8200 ...
  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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: BeagleBoard stops at booting kernel with 2.6.37-rc5

2010-12-16 Thread David Anders

Elvis,

please enable earlyprintk in your kernel config and add earlyprintk 
to your boot args. this will provide a more detailed boot log even if 
the tty is incorrect.


Dave

On 12/16/2010 02:19 PM, Elvis Dowson 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 8200 ...
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.


Elvis Dowson

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


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


Re: BeagleBoard stops at booting kernel with 2.6.37-rc5

2010-12-16 Thread Elvis Dowson
Hi,

On Dec 17, 2010, at 12:25 AM, Robert Nelson wrote:

 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..

Thanks, that fixed the problem. I changed to ttyO2. 

Elvis


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