LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Help me! Kernel 2.6.7 on HP DL380 G3 (https://www.linuxquestions.org/questions/linux-software-2/help-me-kernel-2-6-7-on-hp-dl380-g3-213768/)

Tazzmanian 08-05-2004 09:37 AM

Help me! Kernel 2.6.7 on HP DL380 G3
 
Hello,

I am trying to load the kernel 2.6.7 on a HP DL380 G3 server.
I have compile numerous times with various otpions but with no success, I always get a blank screen when I choose the compiled version in the grub although the system seems to be loading in the background I cannot see a thing. I think that the parttions are not mounting because I cannot see anything in the logs. I am using SUSE Linux Enterprise version 8. Can anybody help me!

Thanks!

m_yates 08-05-2004 11:14 AM

If the framebuffer console is not working, you will get a blank screen. Try using a grub entry something like this:

title Linux, 2.6.7
root (hd0,0)
kernel /boot/vmlinuz-2.6.7 root=/dev/hda1 ro hdc=scsi video=vesafb:ywrap,mtrr vga=788
initrd /boot/initrd.img-2.6.7
savedefault
boot

The "video=" and "vga=" parts of the kernel line may help get the framebuffer working with the VESA driver, if you have the kernel configured to use it.

Tazzmanian 08-05-2004 12:40 PM

Thanks! Now I am getting video, but another problem has arised,
a get a kernel panic message mentionning that VFS: Unable to mount root fs on .......

Thanks!

m_yates 08-05-2004 12:56 PM

You probably need to create an initrd for your kernel. You need to run "mkinitrd" I believe you would need something like:
Code:

mkinitrd /boot/initrd-2.6.7.img 2.6.7
but I'm not sure.

Tazzmanian 08-05-2004 01:09 PM

Do I need to do this if I did not load nay modules, I loaded everything in the kernel..

Thanks!

m_yates 08-05-2004 01:25 PM

In theory you don't need it if you have support for your disks (IDE or SCSI) and filesystem built into the kernel. However, I never got the 2.6 kernel to work without an initrd, so I just use it. The Debian kernel comes with an initrd and it was simpler for me to just keep using the initrd when I compiled my custom kernel. When I was using the 2.4 kernel, I just built in support for my filesystem and IDE and I didn't need an initrd, but that didn't work the same way with the 2.6 kernel. I didn't spend a lot of time trying to figure out why. Perhaps there is some other module needed.


All times are GMT -5. The time now is 08:41 PM.