[Bug 210923] New: unable to configure X
https://bugzilla.novell.com/show_bug.cgi?id=210923 Summary: unable to configure X Product: openSUSE 10.2 Version: Alpha 5 Platform: PC OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: gholmer@ameritech.net QAContact: sndirsch@novell.com With 10.2 alpha 5, I'm completely unable to configure X. When sax starts up, I get "out of range" error on the monitor and have to ctrl-alt-bksp. sax2 -l from the command line is unusable because not enough of the screen shows to be able to make selections. I was eventually able to get sax to run by "sax2 -V 0:1280x1024@60", but still couldn't come up with a combination that would produce any output when the test runs, even by specifying the frequencies from the monitor's spec sheet. This is with ATI RV250 card and Benq FP731 LCD monitor (which was auto-detected). -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |gholmer@ameritech.net ------- Comment #1 from sndirsch@novell.com 2006-10-09 04:31 MST ------- Could you attach /var/log/SaX.log after configuring (without the test!) with "sax2 -V 0:1280x1024@60"? 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=210923 ------- Comment #2 from gholmer@ameritech.net 2006-10-09 04:52 MST ------- Created an attachment (id=100949) --> (https://bugzilla.novell.com/attachment.cgi?id=100949&action=view) /var/log/SaX.log SaX log starting with "sax2 -V 0:1280x1024@60" I accepted the SaX configuration without making any changes, and X did come up afterward with "init 5", but not all of the screen was visible in the vertical direction (KDE and GNOME panels on the bottom mostly hidden, even after pressing the auto adjust button on the monitor). I didn't mention it in the original report, but this combination of hardware works fine in 10.1. -- 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=210923 ------- Comment #3 from sndirsch@novell.com 2006-10-09 05:06 MST ------- Well, looks like you have a notebook and the internal display is autodetected by the driver (1400x1050). Did you check the dualhead button in SaX2 to make sure the internal and external display is used? -- 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=210923 ------- Comment #4 from gholmer@ameritech.net 2006-10-09 17:28 MST ------- No, it's a Dell OptiPlex GX260. The monitor was correctly detected as a Benq FP731. The monitor's spec sheet says 1280x1024. -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|gholmer@ameritech.net | -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |gholmer@ameritech.net ------- Comment #5 from sndirsch@novell.com 2006-10-10 07:22 MST ------- I just updated the radeon driver for openSUSE 10.2. Please test again with Beta1. 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=210923 ------- Comment #6 from sndirsch@novell.com 2006-10-27 09:19 MST ------- openSUSE 10.2 Beta1 has just been released. -- 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=210923 gholmer@ameritech.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|gholmer@ameritech.net | ------- Comment #7 from gholmer@ameritech.net 2006-10-28 01:33 MST ------- Same symptom in beta 1 (monitor shows "No signal detected"). -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |gholmer@ameritech.net ------- Comment #8 from sndirsch@novell.com 2006-10-28 03:29 MST ------- Could you attach /etc/X11/xorg.conf and /var/log/Xorg.0.log for Beta1? 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=210923 gholmer@ameritech.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #9 from gholmer@ameritech.net 2006-10-28 06:46 MST ------- Created an attachment (id=102931) --> (https://bugzilla.novell.com/attachment.cgi?id=102931&action=view) requested files tarred/gzipped -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |gholmer@ameritech.net ------- Comment #10 from sndirsch@novell.com 2006-10-28 07:05 MST ------- Hmm. This is still the fbdev configuration from the installation. Can't you create a real one with SaX2? If it's not possible, try again "sax2 -V 0:1280x1024@60". -- 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=210923 gholmer@ameritech.net changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #102931|0 |1 is obsolete| | ------- Comment #11 from gholmer@ameritech.net 2006-10-28 08:13 MST ------- Created an attachment (id=102937) --> (https://bugzilla.novell.com/attachment.cgi?id=102937&action=view) same files after running SaX manually As before, SaX2 won't start from runlevel 3 without using "sax2 -V 0:1280x1024@60", and I couldn't come up with a workable configuration except to leave the initial suggestion as is. The results are the same as in comment #2. -- 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=210923 gholmer@ameritech.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|gholmer@ameritech.net | ------- Comment #12 from gholmer@ameritech.net 2006-10-28 08:13 MST ------- Reverting from NEEDINFO to ASSIGNED. -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |gholmer@ameritech.net ------- Comment #13 from sndirsch@novell.com 2006-10-28 09:45 MST -------
(**) RADEON(0): Default mode "1400x1050": 122.0 MHz, 64.9 kHz, 60.0 Hz Is this the correct size of your monitor? What's the official resolution of your monitor?
-- 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=210923 gholmer@ameritech.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|gholmer@ameritech.net | ------- Comment #14 from gholmer@ameritech.net 2006-10-28 12:22 MST ------- The monitor specs are: maximum resolution: 1280x1024 maximum refresh rate: 75Hz horizontal frequency: 31-81 kHz vertical frequency: 56-76 Hz Also, it is a 17" monitor, but YaST says 15". -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com, eich@novell.com ------- Comment #15 from sndirsch@novell.com 2006-10-28 14:12 MST ------- The drivers seems to make very strange assumptions. I have no idea, why it configures a 1400x1050 resolution, when only a 1280x1024 resolution is specified in config file. You could try to remove all the modelines in Modes section of /etc/X11/xorg.conf, but I doubt that this would help. :-( -- 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=210923 ------- Comment #16 from gholmer@ameritech.net 2006-10-29 05:27 MST ------- Yes, I suppose I could edit the X config file by hand the way we did 10 years ago, but what concerns me about this issue is the fact that this combination of hardware works fine with SUSE 10.1. -- 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=210923 ------- Comment #17 from sndirsch@novell.com 2006-10-29 12:41 MST -------
Yes, I suppose I could edit the X config file by hand ... This is only for testing purposes.
-- 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=210923 ------- Comment #18 from gholmer@ameritech.net 2006-10-29 13:18 MST ------- Amazingly, that worked: 97,100c97,100 < Modeline "1280x1024" 24.09 1280 1248 1368 1456 1024 1025 1028 1034 < Modeline "1152x864" 24.40 1152 1136 1240 1328 864 865 868 875 < Modeline "1024x768" 24.34 1024 1016 1112 1200 768 769 772 780 < Modeline "800x600" 24.61 800 808 888 976 600 601 604 615 ---
# Modeline "1280x1024" 24.09 1280 1248 1368 1456 1024 1025 1028 1034 # Modeline "1152x864" 24.40 1152 1136 1240 1328 864 865 868 875 # Modeline "1024x768" 24.34 1024 1016 1112 1200 768 769 772 780 # Modeline "800x600" 24.61 800 808 888 976 600 601 604 615
I now have a usable display with the entire screen showing :) -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |ms@novell.com ------- Comment #19 from sndirsch@novell.com 2006-10-29 13:58 MST ------- Indeed, the modelines are completely bogus. 24 Mhz pixelclock ?!? Marcus? -- 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=210923 ------- Comment #20 from ms@novell.com 2006-10-30 01:41 MST ------- Hmm, don't know why this happens. Is there a way for me to reproduce this .. ssh login ? anyway if you can reproduce the wrong configuration by calling init 3 cp /etc/X11/xorg.conf /etc/X11/xorg.conf.working sax2 -r -a ---> send the /var/log/SaX.log file this would help as well -- 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=210923 gholmer@ameritech.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #21 from gholmer@ameritech.net 2006-10-30 02:47 MST ------- Created an attachment (id=103009) --> (https://bugzilla.novell.com/attachment.cgi?id=103009&action=view) /var/log/SaX.log after starting in runlevel 3 and running "sax2 -r -a" -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |ms@novell.com ------- Comment #22 from sndirsch@novell.com 2006-10-30 03:07 MST ------- Marcus, does this help? -- 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=210923 ------- Comment #23 from ms@novell.com 2006-10-30 03:22 MST ------- yes, your monitor reports wrong DDC values. I don't know what other distribution do but we care for the data of the monitor. In your case it is more than wrong: standard DDC said your display is: 1280x1024 is this correct ? enhanced DDC timing said: Card0 => Dacspeed[2]: 25 Card0 => Modeline : 640 656 752 800 350 387 389 449 -/+ Card0 => Modeline[2]: 640 656 752 800 350 387 389 449 -/+ which is completely wrong and the cause for the "wrong" modelines. These timings say your monitor can do 640x350 at a maximum bandwidth of 25Mhz. Maybe the following patch makes sense. But I cannot test it here because I don't have that bad hardware ;) Stefan what do you think ? Index: lib/hw/monitor.c =================================================================== --- lib/hw/monitor.c (revision 1222) +++ lib/hw/monitor.c (working copy) @@ -112,8 +112,10 @@ for(di = di0, i = 0; di; di = di->next, i++) { if (di->any.type == di_display) { if (di->display.bandwidth) { + if (di->display.bandwidth >= 100) { display->bandwidth = di->display.bandwidth; } + } if (di->display.max_hsync) { display->hsync_max = (int)di->display.max_hsync; } @@ -124,7 +126,7 @@ bestX = di->display.width; bestY = di->display.height; } - if (di->display.hdisp) { + if ((di->display.hdisp) && (display->bandwidth)) { sprintf (display->modeline, "%4u %4u %4u %4u %4u %4u %4u %4u %c/%c", di->display.hdisp, -- 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=210923 ------- Comment #24 from sndirsch@novell.com 2006-10-30 03:58 MST ------- What's the fallback, when di->display.bandwidth < 100? Maybe we can detect the monitor instead and use vald values instead? -- 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=210923 ------- Comment #25 from sndirsch@novell.com 2006-10-30 03:59 MST -------
Maybe we can detect the monitor instead and use vald values instead? See comment #14.
-- 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=210923 ------- Comment #26 from ms@novell.com 2006-10-30 04:07 MST ------- if no bandwidth is available the clock is calculated from the given standard DDC information. This means the enhanced data is simply not used and the hsync/vsync range decides for the bunch of modelines and the clock used. For this example everything should work because the standard data is correct (1280x1024) and the hsync/vsync values fits but as I already said I cannot test this without having access to the broken data. In reply to comment #4: default values are only needed if the complete record is broken. Which means the resolution information AND the hsnyc/vsync information is wrong. In such a case we overwrite the values according to the DDC-ID with the correct specs. This is not needed in your case because some of the data are pretty well -- 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=210923 ------- Comment #27 from sndirsch@novell.com 2006-10-30 04:23 MST ------- Ok. Marcus, could you rebuild SaX2 and atttach the RPM for testing? -- 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=210923 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal ------- Comment #28 from ms@novell.com 2006-10-30 06:54 MST ------- I checked it into openSuSE. once the package has built you can refer to http://ftp.opensuse.org/pub/opensuse/repositories/SaX2/SL10.2 status: SL10.2 x86_64 building SL10.2 i586 building -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|ms@novell.com |gholmer@ameritech.net ------- Comment #29 from sndirsch@novell.com 2006-10-30 06:59 MST ------- Glenn, please check these packages one they have a date of Oct 30. -- 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=210923 ------- Comment #30 from mhopf@novell.com 2006-10-30 10:45 MST ------- (In reply to comment #23)
These timings say your monitor can do 640x350 at a maximum bandwidth of 25Mhz.
Maybe the following patch makes sense. But I cannot test it here because I don't have that bad hardware ;)
Marcus, don't test for bandwidth, that could always involve some arbitrary value that seems to fall from the stars. A monitor with maximum resolution 1024x768 in 60Hz (they still exist) e.g. has a maximum bandwidth of 60MHz. What would make more sense is to calculate the refresh frequency, and if it is out of bounds of the DDC spec to ignore the maximum bandwidth (which I have been told is often wrong). I have a monitor here that works only with special options in its optimal resolution, even with the NVIDIA driver, due to the same 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=210923 ------- Comment #31 from ms@novell.com 2006-10-31 03:45 MST ------- I'm sorry I have to test for the bandwidth and the mode timings of the enhanced DDC specs. There are so many devices which works only with the timings given in that record. Think about this crappy Philips Monitor the company bought and spreads over the world. Yes it's cheap hardware and it's crap. - what you suggested is done that way. The problem here is that the bandwidth is ok for a resolution of 640x350 but why are there timings for this resolution it doesn't make sense. According to the standard the timings and bandwidth data must correspond to the preferred resolution of the device which is somethng the vendor decides. I'm pretty sure 640x350 doesn't correspond to 1280x1024. Is this my fault no it isn't. So what makes sense ? accept timings for the maximum resolution only but this will work on TFT's only and is still buggy if the vendor doesn't take care for its data. I think any workaround we can add here has race conditions - if you have such a special monitor you could tell me the options to be able to store them in sax ;) -- 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=210923 ------- Comment #32 from gholmer@ameritech.net 2006-10-31 05:17 MST ------- I installed the following RPMs: sax2-8.1-126.1.i586.rpm sax2-gui-8.1-126.1.i586.rpm sax2-ident-8.1-126.1.i586.rpm sax2-libsax-8.1-126.1.i586.rpm sax2-libsax-perl-8.1-126.1.i586.rpm sax2-tools-8.1-126.1.i586.rpm But I get the following error seven times: "ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199.". Then he proceeds, but gives up with "xc: sorry could not satrt configuration server". Did I miss an RPM somewhere? Attaching /var/log/SaX.log. -- 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=210923 gholmer@ameritech.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #33 from gholmer@ameritech.net 2006-10-31 05:18 MST ------- Created an attachment (id=103159) --> (https://bugzilla.novell.com/attachment.cgi?id=103159&action=view) see comment #32 -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com AssignedTo|sndirsch@novell.com |ms@novell.com Status|ASSIGNED |NEW ------- Comment #34 from sndirsch@novell.com 2006-10-31 05:25 MST ------- Reassigning to Marcus. -- 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=210923 ------- Comment #35 from gholmer@ameritech.net 2006-10-31 05:35 MST ------- Comment #32 was from sax2 in runlevel 3. I think the errors may be because I moved xorg.conf out of the way before starting. If I come to runlevel 5 using the xorg.conf like in comment #18, then start yast2 "Hardware / Graphics Card and Monitor", I can get a successful configuration, although sax2 will still not start from runlevel 3 afterwards. Let me know if you want any additional logs. -- 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=210923 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |sndirsch@novell.com ------- Comment #36 from ms@novell.com 2006-10-31 06:35 MST ------- you have the binary only fglrx driver installed: (II) LoadModule: "fglrx" (II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so (II) Module fglrx: vendor="FireGL - ATI Technologies Inc." compiled for 7.1.0, module version = 8.28.8 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.0 [R200Setup] X version mismatch - detected X.org 7.2.-1.2, required X.org 7.1.0.0 (II) UnloadModule: "fglrx" (EE) No devices detected It seems your installation is broken -- 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=210923 ------- Comment #37 from sndirsch@novell.com 2006-10-31 06:56 MST ------- Indeed. Could you uninstall this driver? It cannot work on openSUSE 10.2. 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=210923 ------- Comment #38 from gholmer@ameritech.net 2006-10-31 17:55 MST ------- You are right, I had tried something else out of desperation :) I did a clean install from the beta1 DVD. After network setup, the installer went right to a KDM login. I dropped back to runlevel 3 and installed the RPMs listed above, then rebooted. The installer came up and asked if I wanted to continue; this time I was able to configure the monitor without any problems. It's beautiful! Thank you so much! -- 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=210923 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |ms@novell.com ------- Comment #39 from sndirsch@novell.com 2006-10-31 21:06 MST ------- Thanks for testing again. Reassigning to Marcus (again) to add the workaround to SaX2 and close this bugreport afterwards. -- 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=210923 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #40 from ms@novell.com 2006-11-02 02:47 MST ------- done :-) -- 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