Re: Problems with bootimg (wish to be personally CC'ed the answers/comments posted to the list in response to this posting)

From: Erik Mouw (J.A.K.Mouw@its.tudelft.nl)
Date: Thu Feb 06 2003 - 20:27:55 EST

On Tue, Feb 04, 2003 at 04:33:24PM -0800, Sowmya.Krishnaswamy@nokia.com wrote:
> We are trying to use bootimg for dual boot:
>
> # bootimg -f bzImage -n -i ram40.img.gz -v console=ttyS0,115200n8 ramdisk_size=131072 root=/dev/ram
>
> bzImage "2.4.17_MVL21CGENOKIA_4-cpi1-lb-arun (abalasub@mvaserg011) #5 SMP Wed Nov 27 17:27:00 PST 2002"
>
> 1439613 bytes (352 pages) 0x4109cc08-0x411fcc07 -> 0x100000-0x25fff
> 16161140 bytes (3946 pages) 0x40131008-0x4109b007 -> 0x8668c-0xff068b
> 4096 bytes (1 page) 0x804b908-0x804c907 -> 0x90000-0x90fff
>
> Total 4299 pages, start address is 0x100000
>
> Loading Kernel Image vmlinuz
> Running boot code at 0x03011000
>
> SYSTEM STOPS PRINTING MESSAGES AND HANGS. Has anyone faced a similar problem before. Any Suggestions?

I'd say you selected support for the wrong CPU (a P3 optimised kernel
won't run on a PII, for example). I have no idea how bootimg works, so
it could still be a problem with your bootimg setup.

Erik 

-- 
J.A.K. (Erik) Mouw
Email: J.A.K.Mouw@its.tudelft.nl  mouw@nl.linux.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Fri Feb 07 2003 - 22:00:22 EST