[TriLUG] New 2.6.8.1-10mdk Kernel Won't Boot

Joshua Gitlin josh at glowfilms.com
Thu Oct 21 10:52:32 EDT 2004


Ok, I figured part of the problem out... For some reason, LILO wouldn't 
boot my bzImage... I placed it in /boot/vmlinuz-josh-1, and for some 
reason, that caused problems. renaming it to 
/boot/vmlinuz-2.6.8.1-10mdkcustom solved the problem and the image 
mounted.

Now, however, the problem is trying to get the proper modules into my 
initrd... The new kernel won't boot because the ext3.ko module is the 
wrong version... Anyone know how to build a new initrd? I don't think 
I've ever had to do that before...

-Josh

> Hey TriLUG,
>
> I recently upgraded to mandrake Community 10.1 on my (ancient) Dell 
> laptop... To get my ACX-100 based wireless card working, I had to 
> recompile the kernel, which I've doon before... but this time, after 
> configuring the kernel, doing a 'make', 'make modules','make 
> modules_install' and a 'make bzImage', something went wrong. I 
> installed the new image in /boot and added it to LILO, rebooted, and I 
> got:
>
> Decompressing vmlinuz.............
> BIOS Data Check Successful.
>
> And then my machine rebooted. Finding this Odd, I changed my 
> configuration and recompiled. No dice.
>
> On a hunch, I cd'ed to /usr/src/linux and tried to execute 
> './vmlinux'... just to see what would happen.
>
> It segfaulted! Is this normal???
>
> I then ran gdb on my new kernel... when I told GDB to run, I got:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xc010000000 in startup_32()
>
> That's the whole backtrace. 0xc010000000 in startup_32(). It segfaults 
> the moment it loads! Which leads me to believe that's what happened 
> when I tried to boot my new kernel.
>
> So, now I'm stuck and don't know what I did wrong. Any thoughts?
>
> Thanks Guys!
>
> -Josh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://www.trilug.org/pipermail/trilug/attachments/20041021/58757bb6/attachment.pgp>


More information about the TriLUG mailing list