[Bug 220197] New: monitor settings not properly detected; cannot continue installation
https://bugzilla.novell.com/show_bug.cgi?id=220197 Summary: monitor settings not properly detected; cannot continue installation Product: openSUSE 10.2 Version: Beta 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: francisg@gmail.com QAContact: jsrain@novell.com I tested a beta1 install on this machine, and things were ok, so this must be new in beta2. The whole actual package installation goes fine, and I'm able to make my user and set the pass. SuSEconfig is run, and then it appears that it's getting to the hardware (i.e. Monitor, Graphics card) detection and the screen goes blank. <Esc> does nothing, and/or leaving it for a long time (couple of minutes) does nothing, too. Some info: root@suse /h/francis> lspci 00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) 00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6200] (rev a1) root@suse /h/francis> hwinfo --monitor 33: None 00.0: 10000 Monitor [Created at monitor.93] Unique ID: rdCR.GcJJsNDmHr6 Hardware Class: monitor Model: "LM19T" Vendor: GRE Device: eisa 0x0000 "LM19T" Serial ID: "0" Resolution: 720x400@70Hz Resolution: 640x480@60Hz Resolution: 640x480@72Hz Resolution: 640x480@75Hz Resolution: 800x600@56Hz Resolution: 800x600@60Hz Resolution: 800x600@72Hz Resolution: 800x600@75Hz Resolution: 1024x768@60Hz Resolution: 1024x768@70Hz Resolution: 1024x768@75Hz Resolution: 1280x1024@75Hz Resolution: 1280x1024@60Hz Size: 359x287 mm Driver Info #0: Max. Resolution: 1280x1024 Vert. Sync Range: 50-76 Hz Hor. Sync Range: 30-80 kHz Bandwidth: 108 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |francisg@gmail.com ------- Comment #1 from aj@novell.com 2006-11-11 07:34 MST ------- So, what's happening? Is it still hanging? Do you have the yast log files for us and the output of dmesg? We need some more debugging information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 francisg@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #2 from francisg@gmail.com 2006-11-11 08:49 MST ------- Created an attachment (id=104796) --> (https://bugzilla.novell.com/attachment.cgi?id=104796&action=view) dmesg output from chroot I'm not sure if it hangs or it's just incorrectly detected settings (which my monitor shouldn't be having). Screen is black. Yast logs: http://www.youmortals.com/suse/logs/yast2logs.tar Not sure how to properly get the dmesg output, but I tried chrooting and running dmesg there (not sure if that's right). Attached, anyhow. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |ms@novell.com |screening@forge.provo.novell| |.com | Status|ASSIGNED |NEW -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |francisg@gmail.com ------- Comment #3 from ms@novell.com 2006-11-11 10:42 MST ------- could you reproduce this by calling init 3 sax2 -r your report doesn't tell me if you were able to use the newly installed system. With this question I assume you are running the current beta2 and you could login to the system calling the commands listed above Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 francisg@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|francisg@gmail.com | ------- Comment #4 from francisg@gmail.com 2006-11-11 10:54 MST ------- Hi, Nope, I'm not running beta2 at the moment because of the above problem. Can't progress any further, even though I'm near the end of the installation. <Ctrl><Alt><Backspace> doesn't help, and I can't get to a console session with ctrl+alt+f1 either. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #5 from jim@bouncingayatollah.co.uk 2006-11-11 14:13 MST ------- I had a similar thing happen last night installing Beta2 on 32-bit Athlon XP 2400+ AsRock K7S8X r3.0 m/b + nVidia Geforce 6200 (rev a1) + Philips 107MB CRT At the installation's hardware detection stage: Hardware detection process started. Graphical screen vanished, briefly revealing the text screen that has the YaST Starting message at the bottom (terminal 1?). Screen went black, but no loss of video signal as the monitor stayed on. Could not access any terminals with Ctrl-Alt-F1/F2/F3 etc. to log in, BUT when flipping to where the graphical screen should be (Ctrl-Alt-F7) the colour of the screen changed slightly to very dark grey (so it seemed flipping was working, just the screens were obscured). After some time (20-30 secs) the floppy and hard disks chugged so the hardware detection was working but I could not see the display. I waited maybe two minutes. Did a hard reset and the installer picked up from where it left off. At the hardware detection stage the graphical screen disappeared briefly as before but reappeared so I could continue the install (I had to enter a different normal user as the previous one was still existing but the install worked). http://www.bouncingayatollah.co.uk/suse/SaX.log http://www.bouncingayatollah.co.uk/suse/Xorg.0.log http://www.bouncingayatollah.co.uk/suse/Xorg.0.log.old http://www.bouncingayatollah.co.uk/suse/Xorg.99.log http://www.bouncingayatollah.co.uk/suse/Xorg.99.log.old http://www.bouncingayatollah.co.uk/suse/xorg.conf http://www.bouncingayatollah.co.uk/suse/xorg.conf.install http://www.bouncingayatollah.co.uk/suse/xorg.conf.saxsave http://www.bouncingayatollah.co.uk/suse/y2logs.tgz -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #6 from francisg@gmail.com 2006-11-12 06:52 MST ------- I figured I'd try specifying a completely new user, too (instead of specifying one already in my /home) and I noticed this time round that there is certainly some monitor output, as the gentleman above noted. If I raise my screen's brightness to near-max I can very faintly make out some of the graphics (very hard to make out, but just about can). Enough to just about complete the installation, and verify that even if X is killed, things remain precisely the same. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |sndirsch@novell.com Status|ASSIGNED |NEW ------- Comment #7 from ms@novell.com 2006-11-12 09:59 MST ------- I'm pretty sure this is not a configuration issue -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |francisg@gmail.com ------- Comment #8 from sndirsch@novell.com 2006-11-12 10:12 MST ------- I don't understand this. As long as you don't have a dualcard system, SaX2 does not do any graphics hardware probing automatically, so no second Xserver with native driver is started. Do you press the test button for the graphics configuration? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 francisg@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|francisg@gmail.com | ------- Comment #9 from francisg@gmail.com 2006-11-12 10:36 MST ------- Nope, I don't get to. As soon as it shows a flash of the whole hardware configuration window loading up, things go out. Isn't this not an X (even sax?) issue though since even after killing the X-server (with rcxdm stop, which I eventually could do -- brightness adjusting, which helped very little) things stay just as blacked out as they are. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #10 from sndirsch@novell.com 2006-11-12 11:20 MST ------- Ok. I'll try to reproduce this issue with one of our 6200 cards. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |mhopf@novell.com ------- Comment #11 from sndirsch@novell.com 2006-11-13 05:18 MST ------- Matthias will test. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 mhopf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|mhopf@novell.com | ------- Comment #12 from mhopf@novell.com 2006-11-16 08:59 MST ------- Just tested an installation with SL10.2 Beta2+. The nv driver works out-of-the-box for my 6200: VGA compatible controller: nVidia Corporation NV43 [GeForce 6200] (rev a2) PCIId: 10de:014f VideoBIOS: 05.43.02.27.ad You might have to consider that your card is actually broken, but only exhibits this behavior with the newest X.org. The change from beta 1 to beta 2 was pretty large with respect to X. The card I have e.g. behaves completely normal, until you use OpenGL, when its display goes completely berserk. We finally came to the conclusion that this is broken hardware. You should probably test the binary only driver from NVidia, though not being able to complete the installation in graphical mode is surly bad. OTOH - the reporters all seem to have a (rev a1) card, while I only have a (rev a2) - maybe this is a hint? Stefan, close as WORKSFORME, or add someone from NVidia? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Comment #13 from sndirsch@novell.com 2006-11-16 09:21 MST ------- Trying WORKSFORME. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
You might have to consider that your card is actually broken, but only exhibits
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #14 from francisg@gmail.com 2006-11-16 12:43 MST ------- Created an attachment (id=105851) --> (https://bugzilla.novell.com/attachment.cgi?id=105851&action=view) dark screen with full brightness, from a camera this behavior with the newest X.org. Ok, I just tested a clean 10.1 install which I upgraded to 10.2. beta2 and the problem is not there. In which case it seems to deal fine with the card both (i) with the default free driver, and (ii) with the nvidia driver.
The card I have e.g. behaves completely normal, until you use OpenGL, when its display goes completely berserk. We finally came to the conclusion that this is broken hardware.
Ok, but I use OpenGL on this card daily. So I did *another* fresh install to check this. This time with no extra configuration, not saving my old /home and I'm sorry but this problem is *definitely* there. I've attached a picture showing what it's like. As you can see, if I put my brightness to near-max, then some text does indeed become viewable. Since I can navigate around a bit now I hit "Test Configuration" and voila. Everything is detected just fine, and from here on everything works perfectly. Suffice it to say that's a pretty bad/tough workaround. Since I'm in I can now also provide any info you'd require. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #15 from jim@bouncingayatollah.co.uk 2006-11-16 20:41 MST ------- In case it's any help I did notice the following oddities in the X org logs: My monitor refresh rates are (from the PDF manual I just found): 30-86 kHz horizontal 50-160 Hz vertical I notice in either Xorg.99 log (.log or .log.old) @ lines 412-413 (II) NV(0): Monitor[0]: Using hsync range of 30.00-33.00 kHz (II) NV(0): Monitor[0]: Using vrefresh range of 43.00-72.00 Hz <--- 43 ? and from either Xorg.0 log @ lines 499-500 (II) NV(0): Monitor[0]: Using hsync range of 30.00-86.00 kHz (II) NV(0): Monitor[0]: Using vrefresh range of 50.00-160.00 Hz (OK) but @ line 566 (**) NV(0): Default mode "928x696": 109.2 MHz, 86.4 kHz, 60.1 Hz (D) So is it possible that with an unlucky/rare selection of mode the monitor is being pushed JUST outside its range? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 francisg@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Comment #16 from francisg@gmail.com 2006-11-23 06:18 MST ------- Problem still here in RC1. James, will you be testing it as well by any chance? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |jim@bouncingayatollah.co.uk -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 jim@bouncingayatollah.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jim@bouncingayatollah.co.uk | ------- Comment #17 from jim@bouncingayatollah.co.uk 2006-11-24 20:08 MST ------- Well, yes, the problem still happens here in RC1. As Francis suggested, if I max the brightness on my monitor after hardware detection and Test Configuration, sax2 chooses Screen[0] 1280x1024 @ 80KHz : 75Hz and the display comes back fine. Before that, the monitor reports 1280x1024, 64kHz, 60Hz, even when the display has darkened. I also installed in 1024x768 with F3 from the initial CD menu (monitor reports 1024x768, 48kHZ, 60Hz) but the display still goes dark at hardware detection. Test Configuration fixes it as above. Thankfully, after logging in everything is fine. Maybe this will disappear with Xorg7.2 if 10.2 ships with that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #18 from sndirsch@novell.com 2006-11-24 21:06 MST -------
My monitor refresh rates are (from the PDF manual I just found):
30-86 kHz horizontal 50-160 Hz vertical
I notice in either Xorg.99 log (.log or .log.old) @ lines 412-413
(II) NV(0): Monitor[0]: Using hsync range of 30.00-33.00 kHz (II) NV(0): Monitor[0]: Using vrefresh range of 43.00-72.00 Hz <--- 43 ? These are default values, because the monitor could not be detected. I cannot see any mode selected with vrefresh < 50 Hz in the logfile. This is the default mode, which should be ok.
(--) NV(0): Virtual size is 640x480 (pitch 640) (**) NV(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
and from either Xorg.0 log @ lines 499-500
(II) NV(0): Monitor[0]: Using hsync range of 30.00-86.00 kHz (II) NV(0): Monitor[0]: Using vrefresh range of 50.00-160.00 Hz (OK)
but @ line 566
(**) NV(0): Default mode "928x696": 109.2 MHz, 86.4 kHz, 60.1 Hz (D)
So is it possible that with an unlucky/rare selection of mode the monitor is being pushed JUST outside its range?
The default mode is the following, which is inside the monitor ranges. (**) NV(0): *Driver mode "1280x1024": 135.0 MHz, 80.0 kHz, 75.0 Hz (II) NV(0): Modeline "1280x1024" 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |francisg@gmail.com ------- Comment #19 from sndirsch@novell.com 2006-11-24 21:10 MST ------- Marcus, what kind of graphics hardware/monitor probing is done, when YaST2 reaches the hardware configuration dialog? Does SaX2 start an Xserver for probing any values required for configuration. I wonder because it's a single head setup. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|francisg@gmail.com |ms@novell.com ------- Comment #20 from sndirsch@novell.com 2006-11-24 21:12 MST ------- BTW, the problem can probably workaround by specifying acceleratedx=1 as boot option during installation. Then the nv driver is already used during installation instead of fbdev driver. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #21 from sndirsch@novell.com 2006-11-24 21:13 MST ------- Marcus, see my comment #19. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #22 from jim@bouncingayatollah.co.uk 2006-11-24 22:55 MST ------- Using acceleratedx=1 during initial install and more importantly after first reboot works. Thanks. Using this option animated splash screens are 1280x1024 64kHz 60Hz, installation GUIs are 800x600 38kHz 60Hz. At hardware detection, the GUI disappears, the "Starting YAST" screen is revealed, there's a brief black screen then the 800x600 GUI reappears with everything correctly detected so I can continue. Another small detail: if the dark screen issue occurs and Test Configuration is used - upon returning from Test a copy of the original (?) mouse pointer is left on screen as well as the active mouse pointer. The copy looks as if its number of colours has been reduced and it is frozen on the backdrop. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #23 from francisg@gmail.com 2006-11-25 04:18 MST ------- I can test the acceleratedx=1 during install as well, but only possibly tomorrow I'm afraid (out now). With regard to the mouse pointer being left on the screen in the corner -- I did experience that as well, but it disappeared as soon as KDE started up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #25 from robin.knapp@fujitsu-siemens.com 2006-11-25 14:17 MST ------- I can even reproduce this after installation: 1. configure xorg to use fbdev, for example: # sax2 -r -a -m 0=fbdev 2. restart x server (ctrl-alt-backspace) - now a copy of the mouse cursor stays on top of console AND X display - display mode is 64.0khz, 60hz, PP (reported by monitor osd) 3. from konsole, let sax2 re-probe the hardware: # sax2 -r what happens: - screen fb console appears - screen goes garbled further info: * Calling sax2 without "-r", everythingok * Calling "sax2 -r" from "nv" x-server, the virtual framebuffer console appears, then output gets garbled followed by switching back to the "nv" x-server which corrects the display * Tried to make a screenshot but it looks ok. => Problem with fbdev driver? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |semigroup@yahoo.co.kr ------- Comment #26 from sndirsch@novell.com 2006-11-26 09:00 MST ------- *** Bug 223783 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ms@novell.com | ------- Comment #27 from ms@novell.com 2006-11-27 01:28 MST ------- In reply to comment #19: Stefan yes sax calls an X-server with -probeonly to detect the amount of videoram. This happens in any case because people complained about the wrong detected videoram. Unfortunately I see no other way to get that value. The value is used for some checks but not a "must have" value. It would be a poor solution to remove this detection again just because the driver is broken. But to avoid a blocker it would be possible with some effort to remove the probeonly call -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #28 from sndirsch@novell.com 2006-11-27 03:20 MST ------- (In reply to comment #27)
Stefan yes sax calls an X-server with -probeonly to detect the amount of videoram. This happens in any case because people complained about the wrong detected videoram. Unfortunately I see no other way to get that value.
I'm afraid there is simply no other way. :-(
The value is used for some checks but not a "must have" value. It would be a poor solution to remove this detection again just because the driver is broken. But to avoid a blocker it would be possible with some effort to remove the probeonly call
Which kind of checks are this? Could you prepare a patch for removing this feature, so we can make a review? Probably some register values are not saved/restored when -probeonly is used. Fixing this - especially for the nv driver - would be very hard. Possibly only NVIDIA can do this. :-( My proposal would be to disable the -probeonly feature for 10.2 and try to fix the issue in the nv driver for 10.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #30 from sndirsch@novell.com 2006-11-27 05:26 MST ------- Ok. It's the "-probeonly" thing, which is broken. I verified this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #31 from sndirsch@novell.com 2006-11-27 05:33 MST ------- X (nv driver) without "-probeonly" restores the old settings. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #32 from mhopf@novell.com 2006-11-27 08:04 MST ------- Just for info: I just tried to remove libddc.so, so no DDC probing is done - no effect. This bug might be related to bug #160812. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #33 from sndirsch@novell.com 2006-11-27 11:04 MST ------- Looks like this issue only occurs only on GF 7XXX GPUs. At least I can't reproduce it on a GF 6600 and Matthias couldn't reproduce it on a GF 6200. Anyway, meanwhile 7XXX GPUs are very common ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #34 from robin.knapp@fujitsu-siemens.com 2006-11-27 12:54 MST ------- (In reply to comment #33)
Looks like this issue only occurs only on GF 7XXX GPUs. At least I can't reproduce it on a GF 6600 and Matthias couldn't reproduce it on a GF 6200. Anyway, meanwhile 7XXX GPUs are very common ...
mhh, two people here reported this on a Geforce 6200 (reporter and comment #5), so it maybe depends on the gfx card BIOS or something else. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Major Priority|P5 - None |P2 - High ------- Comment #35 from sndirsch@novell.com 2006-11-28 03:11 MST ------- Marcus disabled the "-probeonly" call for memory detection for now. Lowering severity therefore. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #36 from sndirsch@novell.com 2006-11-28 05:07 MST ------- First results of investigating this issue by Egbert: nv_setup.c:195 register 610 is changed but not restored ... but there are more issues. :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #37 from sndirsch@novell.com 2006-11-28 05:23 MST ------- Created an attachment (id=107179) --> (https://bugzilla.novell.com/attachment.cgi?id=107179&action=view) xf86-video-nv-probeonly.diff Egert fixed it! :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #38 from mhopf@novell.com 2006-11-28 08:08 MST ------- Hm - I think pNv->PRAMDAC0[0x0608/4] &= 0x0000EFFF; could be nuked. Also, What do you think about register 0x0610? That one isn't saved at all... That's what I mean with I wouldn't change this for the final RC. Though things could probably only get better, not worse :-] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #40 from eich@novell.com 2006-11-28 11:06 MST ------- As it turns out 0x610 doesn't need to be restored. Neither copy in the output == TRUE case. The line setting the top 17 bits to 0 could probably be removed. I did not print out the register values at the time - would be interesting to do this and to find out which bit really made the difference. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #41 from sndirsch@novell.com 2006-11-29 03:54 MST ------- (In reply to comment #35)
Marcus disabled the "-probeonly" call for memory detection for now. Lowering severity therefore. Just gave RC3 installation a try - which includes this sax2 change - and it worked perfectly!
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #107179|0 |1 is obsolete| | ------- Comment #43 from sndirsch@novell.com 2006-11-30 22:45 MST ------- Created an attachment (id=107796) --> (https://bugzilla.novell.com/attachment.cgi?id=107796&action=view) xf86-video-nv-bug220197.diff Patch by NVIDIA (Aaron Plattner). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #44 from sndirsch@novell.com 2006-11-30 22:52 MST ------- fixed for STABLE (openSUSE 10.3). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 ------- Comment #45 from lfriedman@nvidia.com 2006-12-01 08:16 MST ------- http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-nv.git;a=commitdiff;... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=220197 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |f.de.kruijf@hetnet.nl ------- Comment #46 from sndirsch@novell.com 2006-12-19 14:44 MST ------- *** Bug 223516 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com