I attempted to compile the 2.6.0-test11 kernel last night on my SuSE 9 laptop. Unsuccessfully I might add (I am patient). But I have a few questions who's answers might break some bad habits of mine.

First of all what changed in the standard kernel build process. I used to recompile on RedHat machines with a set of instructions looking something like

make mrproper
make xconfig
make dep
make clean
make bzimage
make modules
make modules_install

and then I would hand edit grub.conf to add the new kernel as an option, without borking my old one in case the first boot failed.

Now I am attempting a similar feat in SuSE and the instructions say that Grub will auto detect the new kernel. WTF? Is this true? And does that mean the generic "Linux" entry on the pretty SuSE grub screen is all I get? I really like having a test kernel and a stable kernel (to fall back on).

When I finished last night there was no initrd file for the new kernel and all I got on boot was a blank screen. Zoinkes!

Is an initrd file needed for each kernel on the system, or will 1 suffice?

As long as I patch the kernel sources for my hardware, is there any other stuff SuSE puts in their default kernel that I would lose by going with the kernel source from kernel.org?

Can someone enlighten me a bit on kernel compiling in SuSE 9 please?

"Now I am attempting a similar feat in SuSE and the instructions say that Grub will auto detect the new kernel. WTF? Is this true? And does that mean the generic "Linux" entry on the pretty SuSE grub screen is all I get? I really like having a test kernel and a stable kernel (to fall back on)."

I don't think so. Keep doing it your old way until events prove your old way wrong.

"Is an initrd file needed for each kernel on the system, or will 1 suffice?"

Each kernel needs its own initrd. SuSE compiles a lot of modules as m. Then it puts the modules that have to be loaded with the kernel at boot in initrd. Which modules are in initrd vary with your kernel configuration.

I suggest that you dispense with initrd for kernels you compile yourself. Make all modules necessary for accessing your / partition y. Then you do not need an initrd.

"When I finished last night there was no initrd file for the new kernel and all I got on boot was a blank screen."

In addition to accessing the / partition also make sure that any framebuffer modules that you use are y.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Thanks Jailbait, that makes sense. I am going to try the compile again tonight and will check those settings. Your explanation of initrd files is great. I wasn't aware that that was their purpose. Thanks again.. I learn at least one new thing about Linux every time I come here. LQ rules..

For building the 2.6 kernel

Take and read the following:

http://ftp.kernel.org/pub/linux/ker...lloween-2.5.txt

You need to get the module-init-tools from the red hat repository.

Use lspci -v to help select you hardware. This will be helpful for configuring the 2.6 kernel.

make mrproper
make menuconfig
make
make modules_install
make install

Then modify you lilo.conf or grub.txt

make install installs vmlinuz into the boot directory along with System.map
It creates a symbolic link to you old vmlinuz -> vmlinuz.old and System.old

All you need to do is add entry for the old vmlinuz. I use lilo.conf

This is mine....

image=/boot/vmlinuz
initrd=/boot/initrd-2.6.0-test11
label=Linux2.6
read-only

** This would be you redhat config. **
image=/boot/vmlinuz.old
vga=791
append="hdc=scsi hdd=scsi apm=power-off nomce"
label=Linux2.4
initrd=/boot/initrd.gz
read-only

If you are using lilo, issue lilo -v or modify you menu.lst for grub.

Hope this helps. The more people use 2.6 the better.

Thanks Ghostwalker. But the link appears to be dead. I get a 404 on it. I will try the instructions above and see what happens. I tried again last night and again got a blank screen right after selecting the new kernel on Grubs menu.

Just out of curiosity, did you forget "make modules" above or has that step been removed like make dep?

make modules and make dep are no longer needed make creates you modules for you.

Try this link.

http://ftp.kernel.org/pub/linux/kern...loween-2.5.txt

- Blank screen after decompressing kernel?
Make sure your .config has
CONFIG_INPUT=y, CONFIG_VT=y, CONFIG_VGA_CONSOLE=y and CONFIG_VT_CONSOLE=y
A lot of people have discovered that taking their .config from 2.4 and
running make oldconfig to pick up new options leads to problems, notably
with CONFIG_VT not being set.

IT WORKED!!!!! Yay. You rule ghostwalker. Thanks alot. Now granted I forgot a few options I was supposed to include, but know that I am a little more familiar with the new build process that should be no big deal.

Question: During boot of the new kernel, I have no video display at all until the X server starts. No beautiful scrolling text that is the linux boot process. Is this something I forgot to compile in? Anyone know what that might be??

"During boot of the new kernel, I have no video display at all until the X server starts. "

You might be missing framebuffer support. Set framebuffers to y

---------------
Steve Stites

You are possibly including vga=791 just comment that out or include it with you 2.4 grub/lilo menu selection.

Under "File Systems" -> "Pseudo File Systems", pay attention. Enable /proc and /dev/pts

ftp://ftp.suse.com/pub/people/kraxel/README

On 9.0, you only need to add lvm2 & device-mapper from SuSE if you are using "lvm"

When your done with your kernel, run "mk_initrd" That will create your initrd file for you.

Also check out:

http://portal.suse.com/sdb/en/2002/01/ftpkernel.html