G
Guest
Guest
Archived from groups: alt.comp.periphs.mainboard.gigabyte (More info?)
I upgraded my Gigabyte K8VT800 Pro board to F10 bios. But with the F10 bios the GRUB Linux boot loader will not start.
The GRUB version is 0.94.
GRUB only loads a command line with
GRUB>
where I can type some commands.
With the old bios I was able to select HD0, HD1, CDROM...
The new bios has a new method: In the boot order is only HD, CDROM, ... shown. In a second menu You can set the order of the disks and the SCSI-Devices.
In a hirarchical view it would look like:
1st: HD
- Samsung SP1614N
- WD600AB
- SCSI-Devices
2nd: CDROM
3rd: USB-Disk
4th: USB-Memorystick
The old view looked like
1st: HD0
2nd: HD1
3rd: SCSI-Device
4th: CDROM
But I don't understand, that this should be any influence to the GRUB boot loader. And GRUB seems to be loaded, because I get the GRUB> input command line. But I'm not very experienced with the GRUB command line;-(
Moritz
--
I upgraded my Gigabyte K8VT800 Pro board to F10 bios. But with the F10 bios the GRUB Linux boot loader will not start.
The GRUB version is 0.94.
GRUB only loads a command line with
GRUB>
where I can type some commands.
With the old bios I was able to select HD0, HD1, CDROM...
The new bios has a new method: In the boot order is only HD, CDROM, ... shown. In a second menu You can set the order of the disks and the SCSI-Devices.
In a hirarchical view it would look like:
1st: HD
- Samsung SP1614N
- WD600AB
- SCSI-Devices
2nd: CDROM
3rd: USB-Disk
4th: USB-Memorystick
The old view looked like
1st: HD0
2nd: HD1
3rd: SCSI-Device
4th: CDROM
But I don't understand, that this should be any influence to the GRUB boot loader. And GRUB seems to be loaded, because I get the GRUB> input command line. But I'm not very experienced with the GRUB command line;-(
Moritz
--