Bugzilla – Bug 157376
Computer freezes when using other mode then VESA (or text)
Last modified: 2006-03-24 11:43:43 UTC
When I try to install, I can't use the 1024x768-mode (my default monitor resolution). Using VESA works well, but it is not pretty if customers will find out they have to do it 'that way'. Some more info: GeForce2 Pro, legacy-drivers not supported in the newest kernel. There is allready a bugreport about that and NVidia said they were working on it (no ETA given). Don't know if that is usefull information but hey....I don't hurt if it is not. *while running hwinfo my cursor disappeared. Normal of another bugreport (if not allready reported)?
Created attachment 72390 [details] dmsg log (cat /proc/kmsg)
Created attachment 72391 [details] y2start.log Just kept giving the command 'save_y2logs /mounted/log.tar.gz' until the system did not respond anymore, so it could be that the last step is missing (don't think so)
Maybe, this is related to: https://bugzilla.novell.com/show_bug.cgi?id=147009 Maybe not, but then this one can be deleted.
How and when exactly does the machine freeze, what systems are affected (YaST installation, X11, ...)? The Geforce2 is a really stone-aged GPU and I can impress Nvidia dropped the support for these cards years ago. Does the card work with the unaccelerated module `nv'?
How and when exactly does the machine freeze? - Start install, select 1024x768, run until you see something about 'columns found', that is the last thing I can see. VESA is not affected at all, so it is really a problem of using 'not VESA' probably in combination with the older card. Won't do it again for testing have resetted my machine allready to many times now :D I am using it with 'nv' at the moment so yes that works.
And how: blank screen, nothing happens and nothing will happen cause everything is blocked. My screen goes into sort of standby-mode....
So this problem only occurs during the installation, can you configure and start X11 in the installed system with the `nv'-module? This still could be a problem with the detection of your screen and a wrong refresh-rate. Boot with `hwprobe=-gfx' and see what happens. Attach the output of `hwinfo --monitor' here.
*** Bug 157881 has been marked as a duplicate of this bug. ***
Booting with 'hwprobe=-gfx' changes nothing. I think it is not a problem of the monitor: If the monitor can't handle the selected resolution it prompts a message. This is not what I see in this case, the monitor simply switches to standby. I also can't change the terminals after that. The key combinations of YaST work as expected: I can install the system provided the fact I know the keys to press by heart. ;) I tested also with an ATI Rage 128 which does not show this problem.
It's possible that a CRT-screen switches completely off at too high frequencies as a protection mechanism. Please attach `hwinfo --monitor', is this data correct? There might be a difference between `hwprobe=-gfx' and `hwprobe=-gfxcard', you should also try the latter.
"Please attach `hwinfo --monitor'" How do I do so when the PC freezes?
From your initial comment: > Using VESA works well, but it is not pretty if customers will find > out they have to do it 'that way'. So use VESA again and call hwinfo ;-)
I´ll try with b8 so if you have a minute I download it :)
OK it has been released for some time now. Please reopen this report if you still encounter that problem and provide the information asked for.
"here might be a difference between `hwprobe=-gfx' and `hwprobe=-gfxcard', you should also try the latter." Does not change a bit. Have attached the output from hwinfo --monitor and hwinfo --gfxcard.
Created attachment 74822 [details] output hwinfo --monitor
Created attachment 74823 [details] output hwinfo --gfxcard
The info seems to be correct, looking at the specs given by Dell: http://support.dell.com/support/edocs/monitors/819et/en/spec/spec.htm The max. resolution is sort of 'not supported'. "Addressable means the monitor will sync up to this mode. However, Dell does not guarantee the image will be sized and centered correctly."
Reopened cause off the new information
*** This bug has been marked as a duplicate of 155018 ***
Could you please make 155018 public? If not then just don't respond :D
155018 is public...