Re: [SLE] grub: cannot floppy boot 8.1
Hi, Boot with the DVD, and go into Yast to make a new bootdisk. You find that option under System. Make sure that the floppy is new or not corrupted before making the bootdisk. A good resource for configuring Grub: http://www.linuxjournal.com/article.php?sid=4622 Regards, Jostein On Sunday 10 November 2002 05:30, SuSEnixER wrote:
I have installed 8.1 from dvd successfully, but...
I boot from floppy and my floppy is an ide.device, hdb. It is an ls120 drive. I have no problems with 7.3 and lilo.
The installation of 8.1 did not make a floppy boot image, complained that there was no /dev/fd0, correctly. So I cd /boot/grub and grub-install '(hd1)'
An image was written to the floppy disk, but when I try to boot, I get the text messages progressing to "GRUB" and the cursor advances one more space on the same line and everything stops. The keyboard is still accessable and I can ctrl-alt-del reboot but other keystrokes are not presented to the display and only fill the keyboard-buffer, then click.
Grub is new to me. I have perused the red-hat help files, the suse info files and the included manuals but to no avail.
I can boot with the install dvd, but that is time consuming and requires that I make a change in the cmos from floppy --> cdrom. I need to go back and forth until I get 8.1 parameters set (mail, fetchmail, procmail, etc)
Any help will be gracefully appreciated.
tks,
-------------------------------------------------------
* Jostein Berntsen
On Sunday 10 November 2002 05:30, SuSEnixER wrote:
I have installed 8.1 from dvd successfully, but...
I boot from floppy and my floppy is an ide.device, hdb. It is an ls120 drive. I have no problems with 7.3 and lilo.
The installation of 8.1 did not make a floppy boot image, complained that there was no /dev/fd0, correctly. So I cd /boot/grub and grub-install '(hd1)'
An image was written to the floppy disk, but when I try to boot, I get the text messages progressing to "GRUB" and the cursor advances one more space on the same line and everything stops. The keyboard is still accessable and I can ctrl-alt-del reboot but other keystrokes are not presented to the display and only fill the keyboard-buffer, then click.
Grub is new to me. I have perused the red-hat help files, the suse info files and the included manuals but to no avail.
I can boot with the install dvd, but that is time consuming and requires that I make a change in the cmos from floppy --> cdrom. I need to go back and forth until I get 8.1 parameters set (mail, fetchmail, procmail, etc)
Boot with the DVD, and go into Yast to make a new bootdisk. You find that option under System. Make sure that the floppy is new or not corrupted before making the bootdisk.
I cannot make a floppy with Yast. Yast will not recognize that the floppy drive is /dev/hdb0, not /dev/fd0
A good resource for configuring Grub: http://www.linuxjournal.com/article.php?sid=4622
More: I have an add-on pci-ide 100x adapter with a 100gb (/dev/hde/) attached. Also hda is 100gb and hdd is 24gb, hdc is a dvd/cd-rw (plextor). hdb is an ls120 ide floppy drive. Previously I used lilo, maybe I will have to use lilo for suse 8.1 ?? -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
It sounds strange that your floppy disk is assigned to hdb. What is the output of 'less /var/log/boot.msg | grep fd0' and 'less /var/log/boot.msg | grep hdb'? Could you post the output of 'less /etc/fstab'? Regards, Jostein
Boot with the DVD, and go into Yast to make a new bootdisk. You find that option under System. Make sure that the floppy is new or not corrupted before making the bootdisk.
I cannot make a floppy with Yast. Yast will not recognize that the floppy drive is /dev/hdb0, not /dev/fd0
A good resource for configuring Grub: http://www.linuxjournal.com/article.php?sid=4622
More: I have an add-on pci-ide 100x adapter with a 100gb (/dev/hde/) attached. Also hda is 100gb and hdd is 24gb, hdc is a dvd/cd-rw (plextor). hdb is an ls120 ide floppy drive.
Previously I used lilo, maybe I will have to use lilo for suse 8.1 ??
* Jostein Berntsen
Boot with the DVD, and go into Yast to make a new bootdisk. You find that option under System. Make sure that the floppy is new or not corrupted before making the bootdisk.
I cannot make a floppy with Yast. Yast will not recognize that the floppy drive is /dev/hdb0, not /dev/fd0
A good resource for configuring Grub: http://www.linuxjournal.com/article.php?sid=4622
More: I have an add-on pci-ide 100x adapter with a 100gb (/dev/hde/) attached. Also hda is 100gb and hdd is 24gb, hdc is a dvd/cd-rw (plextor). hdb is an ls120 ide floppy drive.
Previously I used lilo, maybe I will have to use lilo for suse 8.1 ??
It sounds strange that your floppy disk is assigned to hdb. What is the output of 'less /var/log/boot.msg | grep fd0' and 'less /var/log/boot.msg | grep hdb'?
Could you post the output of 'less /etc/fstab'?
/dev/hdb /media/floppy auto rw,noauto,user,sync 0 0 There is no instance of fd0 or hdb in boot.msg because I have been booting from the install cd. -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
Hi, During the SuSE 8.1 professional install a resolution of 1280 x 1024 was chosen and xwindows would not start. The external symptom was the monitor LED light went to orange and the screen remained blank. Internally I saw a message, "could not open the display" and I did see the resolution mentioned above. I ran SAX2. I have a Digiview JD166P monitor. The manufacturer, Digiview, was listed but not the model. I have no manufacturer disk. On page 123 of the Administration Guide, it says, "If the monitor is not included in the list, switch tabs to 'Frequency' and enter the appropriate frequency ranges for your monitor for the horizontal and the vertical deflection frequency in the corresponding fields". I did this and when I went on, I got the message "Monitor couldn't be detected. Don't have a monitor selected." So I was not able to enter in the resolution and frequencies without selecting a manufacturer/monitor. What I ended up doing was selecting any manufacturer/model combination and then changing the resolution and frequency for that one and saving it. Did I miss a step in defining the monitor? Is this a failing of SAX2? Thank you. -- __________________________ DJ mailto: linux_programmer@hotmail.com
participants (3)
-
DJ
-
Jostein Berntsen
-
SuSEnixER