Hello, i tried to install from BDI-CD downloaded from BDIEMC. The CD boots correctly and the installation (using only the defaults) runs till the post installation. Then the X window crashes due to an anaconda problem/bug. Since my window is only a small one, i am not able to see the reason on the resulting text window. Booting afterwards show only GRUB and then nothing. Investigations with SUSE 8.2 rescue system shows that the menu.lst for grub is missing, hence grub is not installed properly. I do not know what i should do to repair this, since i am not familiar with the sequence of installation. Does anybody on this list can help me ?? Thanks in advance. Andreas
Hi Andreas There was never a 4.01 released in to the wild, so I assume you must be using 4.51.. On Monday 16 April 2007 18:03, Andreas Zippel wrote:
i tried to install from BDI-CD downloaded from BDIEMC. The CD boots correctly and the installation (using only the defaults) runs till the post installation. Then the X window crashes due to an anaconda problem/bug. Since my window is only a small one, i am not able to see the reason on the resulting text window.
Is this running the text interface (blue background, no GUI) ? If this is the case, I'm afraid you have hit on a known bug. Text mode usually kicks in with 64M of memory or less - If you can install more, 128M min, 256M prefered, the GUI installer should run.
Booting afterwards show only GRUB and then nothing. Investigations with SUSE 8.2 rescue system shows that the menu.lst for grub is missing, hence grub is not installed properly.
Assuming grub installed, there *should* be an assortment of files in /boot/grub, menu.lst is probably missing, but there should be a device.map - This lists the drives anaconda detected, and grub-install would have used it to install it's self. Assuming just menu.lst is missing, attached is a copy taken from one of my test boxes - If you can transfer it to the problem machine, all well and good. You may want to create a symlink, grub.conf pointing to menu.lst..
I do not know what i should do to repair this, since i am not familiar with the sequence of installation. Does anybody on this list can help me ??
Check /boot for an initrd.im-2.6.20-rtai file - If this is missing, we will have to guide you through using mkinitrd... Regards, Paul.
participants (2)
-
Andreas Zippel -
Paul