HI --

The other day I tried to recompile a new kernel for my machine and I got the same error. I ignored it then, booted to new kernel and it was all busted. Of course.

Had to fix a little of each other kernel as well after a reboot -- tell it where my cd-roms were.

Anyway, forgive me, this has been asked a million times, I know -- my kids don't give me much time to search that hard.

So, I recompiled -these steps:
got source
cd/usr/src/linux
saved .config copy --
make mrproper
make menuconfig
unchecked stuff I know I don't have
make BzImage ( no dice)
make modules
make modules_install
make install


Saw some warnings -- whoopie. Here is the final error, it's initrid --
======================================================
LD arch/i386/boot/setup
AS arch/i386/boot/compressed/head.o
CC arch/i386/boot/compressed/misc.o
OBJCOPY arch/i386/boot/compressed/vmlinux.bin
GZIP arch/i386/boot/compressed/vmlinux.bin.gz
LD arch/i386/boot/compressed/piggy.o
LD arch/i386/boot/compressed/vmlinux
OBJCOPY arch/i386/boot/vmlinux.bin
HOSTCC arch/i386/boot/tools/build
BUILD arch/i386/boot/bzImage
Root device is (3, 6)
Boot sector 512 bytes.
Setup is 5029 bytes.
System is 1225 kB
Kernel: arch/i386/boot/bzImage is ready
sh /usr/src/linux-2.6.3-15mdk/arch/i386/boot/install.sh 2.6.3-15mdkcustom arch/i386/boot/bzImage System.map ""
No dep file found for kernel 2.6.3-15mdkcustom
No dep file found for kernel 2.6.3-15mdkcustom
There was an error when generating initrd. Try to do a :
/sbin/mkinitrd /boot/initrd-2.6.3-15mdkcustom.img 2.6.3-15mdkcustom
to see the errors
looks like there is a problem, the default vmlinuz version is not the same
as the initrd
which means you have a mdk kernel and not a mdk initrd wich may give you trouble
======================================================

SO, I figure I have got to make a file and put it somewhere, ey?

Some down and dirty quick help. Please? I still have the console open, i have done nothing except come here since I ran
make install

===========root folder contents=================
[root@localhost boot]# ls
boot.0300 diag2.img kernel.h-2.6.3-15mdk System.map@ vmlinuz-2.6.3-15mdk
config@ grub/ kernel.h-2.6.3-7mdk System.map-2.6.3-15mdk vmlinuz-2.6.3-15mdkcustom
config-2.6.3-15mdk initrd-2.6.3-15mdk.img map System.map-2.6.3-15mdkcustom vmlinuz-2.6.3-7mdk
config-2.6.3-15mdkcustom initrd-2.6.3-7mdk.img message@ System.map-2.6.3-7mdk vmlinuz.old@
config-2.6.3-7mdk initrd.img@ message-graphic us.klt
diag1.img kernel.h@ message-text vmlinuz@
================================================
so, the stuff is there. I just modified lilo.conf to include the initrd location for my custom kernel....I need to see if it works...

I am currently reading: digital hermit's how-to the:
mkinitrd /boot/initrd-2.6.3-15.img 2.6.3-15 (errored-no directory)


Thanks for some advice.

machiner

make BzImage ( no dice)


THIS should be.......use a small "b" not large "B"



===============

and you should have done this.............

Thank you for your response.

OS, I ended up doing something else. I knew that I would have to repeat the make procesesees, so I moved onto something else.

I already installed Nvidias 3d accellerator in 2.6.3-7. What I wanted to know was -- is there one x86config-4 file that rules them all -- or /per kernel.

I figured one, but I went ahead and (tried) installed the nvidia drivers in the booting 2.6.3-15 (not the custom 1 I blew) kernel. Just as I figured - error - the driver is already installed, as well -keeping on -- A Riva driver was already installed, I changed the "nv" to "nvidia" in xf86config-4, and I figured -- just do it. -- The mandrake 10.0 install flies in at about 10 mins on my box -- a reinstall is no real problem.

I saw the warning - and went ahead anyway. The process said it would make the nvidia driver anyway but I'd prolly have problems. No sh#(.

I had a problem. The process hung at 100%...I waited... - I reset -- no X. Ok -- So, how do I change the xf86config back -- I thought the reference to "nvidia" instead of "nv" would be ebough. I also wanted to restore, or edit current files.

I ran Vim. Wooooaah!!! ok what do I do -- I want to edit files. --help wasn't...

I did not run mc. I wanted that in the first place, but didn't know the command was mc. I do now.

So -- I couldn't figure how to open and edit a file -- I never passed this stage, so I didn't even progress to copy (restore orig file(s)).

I reinstalled mandrake. Of course I couldn't boot into any kernel. Ya -- I tried x86config-4 ...saved as...didn't work.

When I was finished rebuilding the kernel I did check to see if files were where they needed to be. In your reference you tell me to make sure some of the following files are in this folder:

[root@localhost boot]# ls <=====
boot.0300
diag2.img kernel.h-2.6.3-15mdk
System.map@
vmlinuz-2.6.3-15mdk
config@ grub/ kernel.h-2.6.3-7mdk
System.map-2.6.3-15mdk
vmlinuz-2.6.3-15mdkcustom
config-2.6.3-15mdk
initrd-2.6.3-15mdk.img map
System.map-2.6.3-15mdkcustom
vmlinuz-2.6.3-7mdk
config-2.6.3-15mdkcustom
initrd-2.6.3-7mdk.img message@
System.map-2.6.3-7mdk
vmlinuz.old@
config-2.6.3-7mdk
initrd.img@
message-graphic us.klt
diag1.img kernel.h@
message-text vmlinuz@

that was my last command...ls. I had a reference when I was rebuilding the kernel, so I had something to follow along. WHen I was checking off modules I knew I didn't have hardware for, I thought -- hey, this is pretty easy. Running the make commands is easy --- I thought the whole process was pretty easy. But it failed, nonetheless. Prolly for simple reasons that I might have misunderstood, or not - or otherwise paid no attention to...or not.

IN windows I might know that I needed a certain dll of other file to make a proggy work -- so in the installation or further configuration I would install/enable or otherwise make ready a component that might serve another component.

In the kernel, I might not know which, if any, modules-- obscurely named or not -- might be needed for another to work. SO, I just ran down lists -- nope, don't have that -- uncheck . I thought I was building this lean, mean kernel -- just for my box.

Nope.

So, thanks for your response, I have it for reference. I thought my playing around could serve some bigger purpose.

machiner

So -- this is what I've got:

I Installed the source to 2.6.3-15 through Mandrakes ?drak install GUI.

I logged out - back in, opening konsole.

su -
cd /usr/src/linux
make mrproper
make menuconfig
make bzImage -- I should do this step, ey?
make modules
make modules_install
make install
I did try this command:
mkinitrd /boot/initrd---my version--img --myversion--
(mkinitrd -k vmlinux-VERSION -i initrd-VERSION)
esp because I saw an error -- that an intrd conflicted with an image.
it didn't work.

I never did the following:
$ cp arch/i386/boot/bzImage /boot/bzImage-KERNEL_VERSION
$ cp System.map /boot/System.map-KERNEL_VERSION
$ ln -s /boot/System.map-KERNEL_VERSION /boot/System.map

BUt I did check that location to see if the files were already there -- they were so I never ran that step. IN your response, 320MB, you said to do the above steps as well.

Now -- I should be good to go, ey.

When I reboot from here, mandrake will configure lilo for me, the entry will be there when I reboot, I should be able to boot into the lean mean kernel I just built???

Must I run xf86config before I reboot?

machiner