On Mon, 2007-10-01 at 15:25 +0100, Konstantinos Pachopoulos wrote:
> Hi,
> i have a Xeon on an Intel SE7520BD2 board. The
> motherboard has EFI -the "next generation BIOS...",
> however EFI has legacy support for the classical
> bootloaders and the MBRs. I have confirmed this by
> sometimes getting Grub errors, when editing the
> configuration file; that means that Grub is executed.
>
> I have installed Debian Etch 2.6.18-5-amd64 on
> /dev/sda or the first SCSI drive otherwise (on an
> Adaptec card) and runs OK. The only problem is that
> the booting output (the dmesg output) cannot be seen
> in the beginning -blank screen; i only see the last
> lines and the line asking for the username. I do not
> know why this happens.
My guess is something to do with the kernel framebuffer drivers not
initialising the display correctly.
> I then installed 2.6.18-5-vserver-amd64 -did "apt-get
> install vserver-utils linux-image-2.6.18-5
> -vserver-amd64"- on the same drive, the grub
> configuration file (menu.lst) got automatically
> updated, i edited the conf file changing the default
> booting kernel to the vserver one and i rebooted the
> system. After rebooting i ended up waiting on a blank
> screen. I am still waiting...
>
> I suspect it has to do with missing modules, SCSI,
> vserver kernel constraints, etc. In which way is the
> default vserver kernel different than the non-vserver
> one?
Both of the kernel package should contain kernel config files so you
should be able to compare them and see what the difference are.
> Will i have to create an image on my own?
That seems unnecessary if the only problem is not being able to see the
kernel output. Altering the kernel boot parameters to avoid problematic
video mode or redirecting the output to the serial port should solve the
problem.
HTH
Cheers,
- Martin
Received on Mon Oct 1 17:00:13 2007