Hello All, I installed OpenSuSe 10.1 beta with all the updates on a Dell Optiplex, with Windows XP on the first partition. Basically Windows was installed first, and then on the free space Open SuSE was installed. Now during reboot, I get just the Dell POST screen, it goes black, and then the Dell POST screen again, and this would go on forever if I let it. I know it hardly seems like an SuSe problem because it is barely getting to the boot process. I apologize in advance if this isn't the proper procedure for this type of thing, but I do not know how to create a bug report (if it is) and I am looking for help. Thank you in advance as well. BIOS has been put back to hard drive as first device as I booted from CD-ROM to install. Again, many apologies if needed as well as many thanks for any advice. AceMan
Am Sa Januar 28 2006 02:32 schrieb Kevin R. Garand:
Is there any message from Grub?
I know it hardly seems like an SuSe problem because it is barely getting to the boot process.
I don´t want to make you panic, but it reminds me of my first experience with my Laptop. In that case the harddisk was broken (from transport I think) and after 2 days of installing suddenly I could not boot anymore. Try mounting the harddisk from a Knoppix other Live-Distro to exclude this case.
I don´t think your BIOS has anything to do with that. To me it´s quite comfortable to have CD-ROM as first boot-device. Good Luck Peter
Peter Buschbacher wrote:
None, there are no messages
BIOS sees the hard drive so it is installed and working (and even worked fine before the reboot) I am thinking it's boot loader thing, how do I edit this?
I don´t think your BIOS has anything to do with that. To me it´s quite comfortable to have CD-ROM as first boot-device.
I agree, I just wanted to make sure I eliminated someone's response of "make the hard drive the first device." I am in IT, I know that much. lol
On Friday 27 January 2006 21:56, Kevin R. Garand wrote:
Sorry I don't have more time to explain, theres a foreign movie in my dvd player, and im supposed to be watching it right now with my gf :) Boot with Knoppix or other livecd. Edit your /boot/grub/grub.conf It should end up looking something like: default=0 timeout=10 splashimage=(hd0,2)/grub/splash.xpm.gz title SUSE 10 root (hd0,2) title Windows rootnoverify (hd0,0) Plenty more inbetween, but thats a rough idea. Google for grub or grub.conf, google.com/linux would probably be a good idea, and you should get enough info there. Joseph M. Gaffney aka CuCullin
You can try this: boot from an suse installation-cd (BIOS) in Grub choose Installation after some screens like the licence aand that stuff you are promted to install a newsystem or to upgrade an existing one. Choose others -> Automatic repair -> user defined -> bootloader the english dialogs might use different words. Peter Kevin R. Garand schrieb:
Hello, Am Samstag, 28. Januar 2006 02:32 schrieb Kevin R. Garand:
Does this mean you have a "reboot loop"? If yes: I had this in one of the early 10.0 betas, but it worked in the later ones and in final also. Maybe you have more luck with using lilo ;-) To change to lilo (and to verify it is really a bootloader problem): Boot from install CD, somewhere after the license, click the "other" button and change "boot installed system". Mount your harddisk to /mnt. If everything worked up to now, you have verified that it is a bootloader problem. Now chroot /mnt and call yast2 bootloader (maybe you need to install the lilo RPM before doing this). And please report this bug - see http://bugs.opensuse.org In this case, I'd recommend to append the YaST2 logs - see http://www.opensuse.org/Bug_Reporting_FAQ#YaST for information about how to get them. BTW: If you already have a login for opensuse.org or any Novell site, you can use it for bugzilla also. Regards, Christian Boltz PS: The grub configuration posted by Joseph looks broken to me ;-) Here's my working configuration in 10.0 [1] - of course you need to change it to your partitioning: --- /boot/grub/menu.lst --- color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,4)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 10.0 root (hd0,4) kernel /boot/vmlinuz root=/dev/hda5 vga=0x342 selinux=0 resume=/dev/hda2 splash=silent showopts # everything from kernel to showopts is _one_ line! initrd /boot/initrd PPS: From your other mail: > Again, I may have been wrong for posting this here, You are perfectly right here :-) - this list is for discussing alpha and beta versions. However, if you find something that is obviously a bug, you can go to bugzilla directly. [1] grub of 10.1 beta1 only shows the grub> prompt (bug #144688), but that seems to be a different bug ;-) -- 2 min spaeter... "Hach, so sind sie meine Jungens..." Lach... :-) Echt, wie die kleinen Bengels... Und nu kommt nicht mit "Mama, der hat aber angefangen und sich nicht an die Etikette gehalten". [Jessica Bleche in suse-linux]
Well update this morning is that it appears to be a Windows thing. I followed the instructions below, and fixed my installation. Booted into SUSE just fine. The problem occurs when you boot into Windows, and then restart. After this, you get the continuous Dell POST loop. Just an FYI, in case anyone has another solution. Thanks again in advance. Kevin On Jan 28, 2006, at 5:55 PM, Christian Boltz wrote:
I logged a similar bug, in fact sounds like the same thing against OpenSUSE 10 RC1 here : https://bugzilla.novell.com/show_bug.cgi?id=116333 According to the last comments it should of been fixed in grub-0.97-3, im not sure which version of Grub ships with the current SUSE 10.1 Beta's ? The 2 Current work around's Im aware of are as has been mentioned use Lilo which works fine. Or as I do create a separate small (200mb) /boot partition at the start of your HDD and get grub to boot from this. I actually do this now on all my Linux install's regardless of the Distro to avoid running into the problem again. Regards, Gareth.
Hello, Am Montag, 30. Januar 2006 16:27 schrieb Kevin R. Garand:
How do I switch from Grub to Lilo now that it's installed.
Start YaST2 and go to system - bootloader configuration. Go to the second tab (bootloader installation) and switch from GRUB to lilo.
grub-0.97-3 in beta2 (and in beta1 also) :-/ It seems you should reopen your bugreport... Regards, Christian Boltz -- Wer etwas "Narrensicher" nennt, unterschätzt die Narren. [Ratti in suse-linux]
participants (6)
-
Christian Boltz
-
Gareth Young
-
Joseph M. Gaffney
-
Kevin R. Garand
-
Peter Buschbacher
-
Silviu Marin-Caea