|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation crash / ends abruptly | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | rob welch <robwelch100> |
| Component: | Installation | Assignee: | Steffen Winterfeldt <snwint> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 5 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
hwinfo output
Yast2 logs |
||
|
Description
rob welch
2006-02-28 05:26:12 UTC
++++++++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 |