Kernel recompile, LILO warning and Kernel-panic
I'm having trouble with compiling my own kernel(2.6.22.1 to be exact). I download the source, extract it to /usr/src, fix /usr/src/linux symlink to point to the new kernel tree, copy .config from old (Slack12 original)kernel to my new kernel, run make menuconfig to add some ACPI stuff to it and compile, make returns no errors, so doesn't make modules_install, but then I run make install witch installs the kernel corectly only LILO returns an warning:
Code:
root@xendria:~# lilo Code:
# LILO configuration file LILO is located/installed on hda2 not on MBR. And I really don't have any idea what's going on. |
Did you make sure that the ext3 filesystem was compiled into the kernel and not as a module?
You will need an initrd if ext3 was compiled as a module. Also, are you saying you did or didn't do make modules_install? |
i like this way:
Code:
$make menuconfig # change options, especially compile in fs support You can recompile with these things built in, or make an initrd for fs support. Code:
#mkinitrd -c -k 2.6.22.1 -m jbd:ext3 -o /boot/initrd-2.6.22.1.gz Code:
initrd=/boot/initrd.gz hth |
Quote:
I've checked the File Systems part in te menu again and ext3 was compiled as module yes, and no I didn't have a initrd, but I did make modules_install I've compiled ext3 fs support not as a module, I'll reboot and report. Thank you. |
:twocents:
Sometimes it doesn't hurt to do Code:
make mrproper LFS recomends make mrproper: Quote:
again, my :twocents: Btw i have a similar lilo warning, still not sure how to fix it: Code:
/sbin/lilo |
Quote:
Quote:
Quote:
|
Thanks onebuck, i don't wanna hijack this thread; i added lba32 compact, but still the same. Maybe something wrong w/kernel .config. Will keep and eye in here and here
Anyway i still left lba32 & compact in lilo.conf, Thanks again |
Quote:
What about your BIOS? It sounds like a geometric problem. Is your BIOS current? |
When you put the .config from 2.6.21.5 into the 2.6.22.1 directory,
did you run "make oldconfig" first thing? Also, have a look at /boot/README.initrd I had to make an initrd.gz to get my 2.6.21.7 slimmed-down kernel to boot. Good info on lba32, I was wondering about that myself. |
The kernel works, but I'm stuck with 2.6.21.5 still because I have trouble finding a working rt2500 driver. When I compile it I always get that "mac" is not a member of some struct, forgot the name, but when if I comment out the line where it calls for mac from that struct the driver just doesn't work later. Oh well. Will try to download newer version and play with it a bit more, but problem in this thread was solved. Thank you everyone.
************* Edit: Fix that problem as well. |
Hi,
Quote:
|
The problem with the kernel-panic. Because I didn't compile ext3 support into the kernel, but I've compiled it as a module and didn't create a initrd.
But when I've fixed that my rt2500 Wireless driver wouldn't build, so I downloaded the newest daily-CVS package from http://rt2x00.serialmonkey.com and compiled it, installed it and now I'm loving it. |
Well, since it seems op Tux-Slack solved his problem...
@onebuck: Quote:
No more lba32 issues, but still the: Code:
/proc/misc: No entry for device-mapper found Code:
Device Drivers -> Multi-device support (RAID and LVM) -> Device mapper support |
Quote:
Glad too see you got it up and flying. I like to document everything that I do for any system that I work on. That way I have a trail to backtrack when needed. Unlike a computer that has a memory failure mine doesn't get replaced easily. |
more thread hijaaking
Slackware 12: I'm compiling a kernel with no support at all (intentionally) for RAID or LVM. I get this when I run lilo:
Code:
/proc/misc: No entry for device-mapper found Should I do anything to remove this spurious warning? |
All times are GMT -5. The time now is 11:00 PM. |