Bugzilla – Bug 154037
Installation crash / ends abruptly
Last modified: 2006-05-08 12:48:27 UTC
My installation attempts of SuSE OSS 10.1 have failed everytime. I have tried the normal installation, ACPI disabled, and safe settings all of which produced an error that caused my screen to go blank and my monitor indicating there is no longer any input. During the install I pressed F2 and watched the boot. The last known item to load successfuly is klogd. The last line written before the crash is that there was a linux console located at /dev/... (I couldn't read the rest of the location before the crash). As a side note I had the same problem with my attempts at trying an internet installation. system information: Iwill XP333 motherboard AMD athlon XP 1800+ processor 512 mb ram 2x 60GB IDE hard drives 2x 32GB SCSI hard drives Lynksys network card Nvidia Geforce2 MX 32mb ram usb mouse ps2 kbd Sylvania 1024x768 lcd monitor (Quad boot system with SuSE 10.0 beta 4, Kanotix 2005-4, Windows XP, one vacant for testing)
++++++++CORRECTION++++++++++++ the last information to be displayed at boot before crash is: starting yast... Probing connected terminal... Initializing virtual console... Found a Linux console terminal on /dev/console (93 columns x 45 lines) Shortly after this last message appears the crash takes place and the screen goes blank and I lose video feed.
You did try "failsafe" installation ? Did you also try entering "textmode=1" at the boot prompt ?
Klaus, he tried failsafe. Rob: Is it possible that YaST starts with the wrong video mode? `You lose video feed', what does that mean? Is your display showing you a message about an incompatible signal? Try hitting F3 twice at the boot screen and select the correct resolution for your screen. You can also try booting with `hwinfo=-monitor'.
Created attachment 70729 [details] hwinfo output
Created attachment 70730 [details] Yast2 logs
OK I got 10.1 to install. Here's what I did. I tried to f3 x2 but it did not work, then I f3 x2 and selected VESA and entered the option hwinfo=-monitor as per comment #3. Yast2 loaded graphically and I was able to install. Opon reboot after disk 1 the installation continued via Ncurses but everything installed fine. Above you will find my hwinfo and Yast2 logs if anyone is interested. Thanks for the help. Rob
It was not hwinfo=... because it's actually hwprobe=-monitor ;) So selecting the correct resolution for your screen led to success. The second part falls back to ncurses in beta5, this is a known issue that should be fixed with beta6 (will be released today). However if you attach `hwinfo -monitor' seperately and tell us the correct resolution and frequency for that machine, we cann add/fix support.
What is the resolution the boot loader originally selects (press F3)?
if you see anything with rc5, reopen