Hello, 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 consol with GRUB> where I can type some commands. I would like to use the F10 bios because of C'n'Q is automaticaly enabled e.g. when I'm in bios the CPU vcore is only 1.1V. Any ideas? Thanks, Moritz
* Moritz K?rten
Hello, 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 consol with GRUB> where I can type some commands.
Probably the boot order of your disks has changed - check that in the BIOS
I would like to use the F10 bios because of C'n'Q is automaticaly enabled e.g. when I'm in bios the CPU vcore is only 1.1V.
Any ideas?
Thanks, Moritz
--
Stefan Fent
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 consol [command line] with GRUB> where I can type some commands.
Probably the boot order of your disks has changed - check that in the BIOS
Yes, I checked this. But the boot order is the same like before. But Gigabyte changed the kind of setting the boot order. 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 -- +++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++ Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl
* Moritz Kuerten
Probably the boot order of your disks has changed - check that in the BIOS
Yes, I checked this. But the boot order is the same like before. But Gigabyte changed the kind of setting the boot order.
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;-(
This doesn't really help, where is your kernel located ? is / a different
partition ?
Are you sure that the disks in the second menue are correct (first Samsung,
then WD) ?
some words to the grub console:
"kernel (hdx,y)/
Moritz
-- +++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++ Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl
--
Stefan Fent
This doesn't really help, where is your kernel located ? is / a different partition ? I guess so. On HD0 (1st IDE channel, master, Samsung) GRUB is installed in MBR and Windows XP on NTFS. On HD1 (2nd channel, master, WD600) Linux is installed.
When I boot, normally the GRUB boot loader shows me a menu where I can select to boot Windows or Linux. This doesn't appear anymore with F10. I only get the GRUB command line.
Are you sure that the disks in the second menue are correct (first Samsung, then WD)?
Yes. But I will try to change it and look what happens.
some words to the grub console:
"kernel (hdx,y)/
/<vmlinuz>" where x is the disk, y the partition, both counted from _0_ should give no error
"initrd (hdx,y)/
/<initrd>" same as above
"root (hdx,y)"
same as above
"boot"
should boot your system. for x you may take 0 or 1
I will try this. Thanks, Moritz -- GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail +++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++
Op vrijdag 8 oktober 2004 09:02, schreef Moritz Kuerten:
This doesn't really help, where is your kernel located ? is / a different partition ?
I guess so. On HD0 (1st IDE channel, master, Samsung) GRUB is installed in MBR and Windows XP on NTFS. On HD1 (2nd channel, master, WD600) Linux is installed.
When I boot, normally the GRUB boot loader shows me a menu where I can select to boot Windows or Linux. This doesn't appear anymore with F10. I only get the GRUB command line.
Are you sure that the disks in the second menue are correct (first Samsung, then WD)?
Yes. But I will try to change it and look what happens.
some words to the grub console:
"kernel (hdx,y)/
/<vmlinuz>" where x is the disk, y the partition, both counted from _0_ should give no error
"initrd (hdx,y)/
/<initrd>" same as above
"root (hdx,y)"
same as above
"boot"
should boot your system. for x you may take 0 or 1
I will try this.
Thanks, Moritz
I've had a similar problem. The real problem was the change of order from the ata and sata controllers. hda became hde and hde became hda. The solution was to use Yast to reinstall grub. I hope this helps Luuk
After several trys of change the Bios settings to get GRUB boot up the system, I made a repair install of Suse. Yast found an error on HDC-1 and fixed it. Then I restartet again but GRUB still could not boot up the boot manager. Then I reinstalled the GRUB boot manager and rewrote the MBR, but nothing happens. At last, I made the repair install again, but changed from GRUB to Lilo boot manager. This was the right decision. Now, I can boot the system, choose between Windows and Linux and everything is like it was before the bios update. It seems, that there is a bug in GRUB 0.94. Moritz -- GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail +++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++
participants (4)
-
Luuk Oudejans -
Moritz Kuerten -
Moritz Kürten
-
Stefan Fent