Skip to contentSkip to conversation

Kernel 2.6.16 hangs after start booting with U-Boot 1.1.2

DISCUSSION Martin Margraf 3 participants 3 messages May 24, 2006 – May 26, 2006

lore
Share & tools
lore
#0 lore raw

hi,

my problem is that after updating u-boot from 1.1.1 to 1.1.2 and after patching /arch/arm/boot/compressed/makefilfe and head-omap.S the kernel is hanging up at start. i use the latest kernel (2.6.16.18) and patched it with the 2.6.16-omap1 patch.

the second problem is in hyperterminal or minicom.
i try to setenv bootargs... but at the end of line there is no jump to the next line (if i press enter then there is a new line) so i cant set all bootargs in one row.
does anybody else has this problem?

im going insane :)

regards

martin
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

#1 lore raw
Quoted 2 lines · Martin Margraf

my problem is that after updating u-boot from 1.1.1 to 1.1.2 and after patching /arch/arm/boot/compressed/makefilfe and head-omap.S the kernel is hanging up at start. i use the latest kernel (2.6.16.18) and patched it with the 2.6.16-omap1 patch.

You don't tell us which board you use, which patches you applied to makefile and head-omap.S and where kernel hangs.

Try to enable

Kernel hacking -> Kernel debugging -> Kernel low-level debugging functions

for debugging.

Often made mistake are wrong parameters passed from u-boot to kernel (e.g. board ID) after u-boot update.

Why do you update to u-boot 1.1.2 and not latest one (1.1.4)?

Cheers

Dirk

#2 lore raw
Quoted 14 lines · Dirk Behme
Quoted 4 lines · Martin Margraf

my problem is that after updating u-boot from 1.1.1 to 1.1.2 and after patching /arch/arm/boot/compressed/makefilfe and head-omap.S the kernel is hanging up at start. i use the latest kernel (2.6.16.18) and patched it with the 2.6.16-omap1 patch.

You don't tell us which board you use, which patches you applied to makefile and head-omap.S and where kernel hangs.

Try to enable

Kernel hacking -> Kernel debugging -> Kernel low-level debugging functions

Quoted 6 lines

for debugging.

Often made mistake are wrong parameters passed from u-boot to kernel (e.g. board ID) after u-boot update.

Why do you update to u-boot 1.1.2 and not latest one (1.1.4)?

Is this perhaps the memory timing issue also?

Tony