http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|470341 | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c2 --- Comment #2 from andreas bittner 2009-11-24 16:05:20 UTC --- Created an attachment (id=329247) --> (http://bugzilla.novell.com/attachment.cgi?id=329247) kvm attached, but kvm-port not being active, initial runlevel5 success, nonverbose Xorg.0.log asus m4a785d-m pro, 11.1, booting with kvm attached, but kvm-port not being selected/activated, initial runlevel5, nonverbose Xorg.0.log the pixels and graphics output came up fine, and this screen was once again in native flatpanel resolution 1680x1050 but at slightly off 59Hz instead of 60Hz what all the windows boxes show or what even the alt+f1 f2 etc.. screens show (always being shown in flatpanel hardware onscreen display). i booted this system with the older more fully xorg.conf file still being available (probably from sax2) from when i had the harddisk (actually always using the same harddisk but once in the one board, other time in the other board) attached to the ati hd3200 system. interesting thing is: in this "normally" working scenario, whenever i log into the kde logon screen, and log out of there again, it resets the whole xerver, and from there onwards, the screen is off-set slightly to the left and lower area, and the hardware onscreen display then shows only 1280x1024 or some non.native resolution from there on. after that when init 3 and X -logverbose or init 5 again or whatever else i do, i can never manage it back to the real native resolution again. so only during the real reboot without the kvm switchport being active and with this full xorg.conf file can i manage to use the almost perfect (1Hz refresh rate difference) native resolution with opensuse in the Xserver. all other following attempts fail to regain native resolution unless i reboot the whole machine. so setting resoltutions or that part of the driver might be an additional bug in the radeonhd or so i think. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c4 --- Comment #4 from andreas bittner 2009-11-24 16:09:42 UTC --- Created an attachment (id=329249) --> (http://bugzilla.novell.com/attachment.cgi?id=329249) then using runlevel3, minimal stefans xorg.conf and X -logverbose, Xorg.0.log asus m4a785d-m pro, 11.1, booting with kvm, but kvm-port notselected, runlevel3, minimal stefans xorg.conf, X -logverbose, Xorg.0.log the display works and pixels are being shown but the screen has an offset towards the lower left side, and its never the native resolution again once the xerver had been running before and has been restarted (at logout of kde4 desktop, etc...) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c6 --- Comment #6 from andreas bittner 2009-11-24 16:14:54 UTC --- Created an attachment (id=329253) --> (http://bugzilla.novell.com/attachment.cgi?id=329253) kvm attached, kvm-port active all the time, logverbose, runlevel3, but no pixels, blackscreen only asus m4a785d-m pro, 11.1, booting with kvm, bootup with kvm-port being activated/selected all the time, runlevel3, with minimal stefans xorg.conf, X -logverbose, produces only blankscreen nopixels as well, X process needs to be killed to end it, Xorg.0.log, logverbose -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #329248|application/octet-stream |text/plain mime type| | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c8 --- Comment #8 from andreas bittner 2009-11-24 16:52:35 UTC --- ok, now taking the hints from the other bug about re-activating the Option UseAtomBIOS "1" also in my minimal xorg.conf file now with this board/chipset the xserver seems to be working now in both scenarios: connecting through the kvm, and the kvm switch-port being both active and being non-active during initial system bios/POST/susebootup the X -logverbose now manages to display a 1024x768@60Hz screen in both of these scenarios. so enabling the UseAtomBIOS line does the trick, and now with my fully loaded xorg.conf with the additional UseAtomBIOS 1 line now even the whole system starts normally even in runlevel5 directly at the kde logon screen at 1680x1050@60Hz (not only 59Hz as before) right now im am inside kde and writing this update in firefox, and i will check if the screen still manages to stay at native resolution even when i logout of kde and the xserver apparently gets recycled at that time. up til now the screen was always off-set at that point in time. will report back and add the Xorg.0.log files from the various scenarios with UseAtomBIOS enabled just for the record, maybe somebody still can dig through the logs and make some use of it, or find out if its possible to make the screen output also work without the atombios stuff being enabled, if that makes sense. regards. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c10 --- Comment #10 from andreas bittner 2009-11-24 16:58:44 UTC --- Created an attachment (id=329266) --> (http://bugzilla.novell.com/attachment.cgi?id=329266) atombios activated in minimal xorg.conf, xserver outputs pixels at last, kvm with kvm switchport activated during boot asus-m4a785d-m pro, 11.1 booting with kvm, bootup with kvm switch-port being activated, runlevel3, minimal stefans xorg.conf but additionally with AtomBios being activated, X -logverbose finally shows pixels, AT LAST, xserver outputs pixels 1024x768x60Hz resolution, Xorg.0.log, logverbose -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c12 --- Comment #12 from andreas bittner 2009-11-24 17:03:15 UTC --- end results with 11.1 on this board: with UseAtomBIOS 1 this board not outputs pixels in all kinds of scenarios, no matter if kvm attached and kvm switchport was active during bootup of opensuse. its the same most likely on the other mainboard. will test it there as well and report back. some opensuse 11.2 postings can follow if needed. regards and thanks for the help with this bug. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #329267|text/x-log |text/plain mime type| | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c14 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eich@novell.com --- Comment #14 from Egbert Eich 2009-11-24 17:58:53 UTC --- Andreas, thanks for the logs: You said you can start X without UseAtomBIOS when you boot the machine with another machine selected at your KVM. Right? - Does this 'boot the machine' also include starting the Xserver or do you have to do this by hand? If I read everything correctly your Xserver starts fine always when you use UseAtomBIOS, is this correct? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|xorg-maintainer-bugs@forge. |eich@novell.com |provo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c17 --- Comment #17 from andreas bittner 2009-11-24 18:30:17 UTC --- i am back with this board and opensuse 11.2 results now: with the standard included rtm drivers of 11.2 dvd goldmaster iso the screen is always blank, with the minimal xorg.conf even with the useatombios line enabled. maybe thats because the 11.2 gold radeonhd driver is still the older one from october 2009. will try later with the newer ones from the separate repository. adding the logs for the 11.2 final situation first. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c19 --- Comment #19 from andreas bittner 2009-11-24 18:34:17 UTC --- Created an attachment (id=329285) --> (http://bugzilla.novell.com/attachment.cgi?id=329285) minimal xorg.conf with atombios enabled line, still arriving at black screen only, but not powerdown same holds true for simple xorg.conf with useatombios enabled line. also only arrives at a black screen, no pixels visible, but the screen apparently receives some kind of data as it doesnt go into sleep/powerdown mode as before in the earlier 11.1 scenario. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c21 --- Comment #21 from andreas bittner 2009-11-24 18:45:21 UTC --- Created an attachment (id=329286) --> (http://bugzilla.novell.com/attachment.cgi?id=329286) no xorg.conf file, only receiving black screen with newer radeonhd driver the hardware onscreen display actualy shows a resolution of 1024x768@60Hz or so during these black situations. i can normally exit this via ctrl+alt+backspace twice, and i always get an mtrr error on the commandline here, in both scenarios (the next logfile that i will upload), both with missing/empty xorg.conf or with basic minimal xorg.conf (with atombios enabled). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c23 --- Comment #23 from andreas bittner 2009-11-24 18:54:12 UTC --- tried more explicitly, this time again switching away from the suselinux boxes kvm switchport, waiting a while til it got booted. switching back the kvm switchport the the opensuse 11.2 machine, (using the minmal xorg.conf with atombios enabled line) i see the runlevel5 came up and a really low resolution like 1024 or even lower came up using this newer radeonhd driver. but when then going to alt+f2 and init 3, then X -logverbose never brings back the graphics that way any more. only the black screen again here (onscreen display menu shows 1024resolution). so in this scenario there is again the connection the kvm switch and its state during initial bios/POST/boot of the system and if it can bring up the initial runlevel5 graphics screen. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c25 --- Comment #25 from andreas bittner 2009-11-24 19:02:34 UTC --- kvm being watched all the time (switchport always switched to suse system): booting, runlevel5 switches again to black but this way screen hardware is going powerdown powersave mode. alt+f2 and init 3, and X -logverbose also produces same result, again black then quickly powersave mode. so this way there seem to be vga signals lacking completely on the vga port. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c27 --- Comment #27 from Egbert Eich 2009-11-25 09:27:26 UTC --- Please, not so fast :) At least give me a chance to reply to you and give you some guidance before you proceed as it may help avoid doing a lot of tests which are not really useful. (In reply to comment #16)

(In reply to comment #14)

...

You said you can start X without UseAtomBIOS when you boot the machine with another machine selected at your KVM. Right? - Does this 'boot the machine' also include starting the Xserver or do you have to do this by hand?

up til the situation without the atombios being enabled, i could start the whole machine only when being switched away to a different machine on the kvm switch. i was waiting a few minutes and only then switching back to the linux machine.

this way using the radeonhd driver it seemed to be always succeeding in setting a resolution and outputting pixels via the vga port.

so yes, i arrived normally at runlevel5 being presented with the kde logon screen.

but as soon as the kvm switch was activated during the whole bootprocess it never managed to activate the graphics. it was completely black (then the screen going into powerdown mode as it apparently didnt receive any pixels), or there were occasions when the xserver terminated and i arrived at the alt+f1 screen with the suse bootup log messages. please see my postings about when which situation occurred.

...

If I read everything correctly your Xserver starts fine always when you use UseAtomBIOS, is this correct?

yes, with radeonhd and useatombios enabled, it always works, no matter what the kvm switchport was being set to/activated.

OK, this gives me some hints already. Please do the following: Instead of using the line: Option UseAtomBIOS "True" Add the line Option AtomBIOS "crtc=on|off output=on|off pll=on|off" each of crtc, output and pll can have the value on|off. There are 7 combinations possible, one you have already tested: Option AtomBIOS "crtc=on output=on pll=on" which is equivalent to Option UseAtomBIOS "True" I don't need you to test all 6 remaining combinations. Could you please test: (a): Option AtomBIOS "crtc=off output=on pll=off" and (b): Option AtomBIOS "crtc=on output=on pll=off" and check if any of those give you a working picture on the analog output with the KVM switch connected? I would assume that at least (a) would work for you. I don't need any log files at the moment, should I need any, I'll get back to you and tell you exactly what I need. HINT: on 11.2 you need to specify the option '-retro' on the command line otherwise you will get a black screen only. (ie. X -logverbose 7 -retro) Thanks! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c29 --- Comment #29 from andreas bittner 2009-11-25 12:36:38 UTC --- i changed the line to UseAtomBios inside quotationmarks, so "UseAtomBios" "crtc=off output=on pll=off" and then the X -logverbose -retro works and brings teh grey pixeled classical display. mouse works as well on 11.2 so i just tested a) successfully from runlevel3. kvm was connected and screen/switchport visible all the time. c=off o=on p=off results in visible xserver testoutput. testing b) c=on o=on p=off also creates a visible grey screen with mousecursor. same situation, with kvm, kvmport acitaved all the time, runlevel3, opensuse 11.2, minimal-b xorg.conf file so both scenarios a) and b) are visible for me this way. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c31 --- Comment #31 from andreas bittner 2009-11-25 12:46:26 UTC --- update: ok i did some further debugging, my diffing the xorg logfiles when going for "UseAtomBios" in contrast to only using "AtomBios", the UseAtomBios logfile complained that UseAtomBios was expecting a boolean, so i re-did the tests with AtomBios and the parameters once again. but this time its the same, i get pixel output with both a) and b). the resolution on 11.2 here is only 1024x768@60Hz this way, so its not starting in the native resolution with these minimal xorg.conf files. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c33 --- Comment #33 from andreas bittner 2009-11-25 15:45:13 UTC --- i was experimenting with subsequent calls of X -logverbose and was diff-ing the logs, but they seem to be different at a lot of lines. is this normal? all kinds of different memory mappings and whatever little flags/values/registers or something..... just wondering. btw, i dont have any rdc_conntest, and google also only outputs rhd_conntest, but that doesnt really return much i think: lspci shows: 01:05.0 VGA compatible controller: ATI Technologies Inc Device 9710 01:05.1 Audio device: ATI Technologies Inc Device 970f and rhd_conntest -d 01:05.0 rhd_conntest: v1.3.0, non-git sources Unknown device: 0x1002:0x9710 (01:05.00). am i doing anything wrong? same output from inside running X/runlevel5 or console runlevel3 i think i actually came across this pci/bios dump stuff as of yesterday already on some other webpage and i once succeeded it dumping some pci config registers or whatever it was on either of these mainboards. maybe its some lspci parameter instead? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c35 --- Comment #35 from andreas bittner 2009-11-25 15:52:47 UTC --- Created an attachment (id=329494) --> (http://bugzilla.novell.com/attachment.cgi?id=329494) AtomBios crtc=off output=on pll=off, X -logverbose, display comes up at 1024x786@60Hz 11.2, running through kvm switch with kvm switch-port active all the time through bios/bootup. X -logverbose -retro, log-output. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c37 --- Comment #37 from Egbert Eich 2009-11-26 07:44:46 UTC --- Sorry, rhd_conntest hasn't been updated for the latest chipsets. I'm coing to push a fix ASAP. But you can also do dd if=/dev/mem bs=1024 skip=768 count=64 of=/tmp/VGA_BIOS.rom and mail me the resulting /tmp/VGA_BIOS.rom file. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c38 --- Comment #38 from Egbert Eich 2009-11-26 07:53:12 UTC --- It's clear to me now why you only get 1024x768 on the VGA output. You also have a monitor connected to the DVI input. This monitor is sensed but the driver isn't able to get DDC data from the monitor. So a 1024x768 default mode is picked. To run both heads at the same resolution this mode is cloned for both heads. If you unplug the DVI connector you should get the native resolution on VGA. Could you try this and see if the image is distorted and cannot be fixed with the monitors auto feature? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c40 --- Comment #40 from Egbert Eich 2009-11-26 10:56:08 UTC --- (In reply to comment #39)

(In reply to comment #38)

...

It's clear to me now why you only get 1024x768 on the VGA output. You also have a monitor connected to the DVI input. This monitor is sensed but the driver

thats not the case. there is nothing at the other ports of the mainboard(s). like i said right from the beginning on. i only have the normal standard dsub vga15 connected. either directly to the flatpanel or through the kvm switch.

i am not kidding. i can send you a picture of the testlab if neccessary or whatever you need to get convinced :)

Yeah, I believe you :) Would it be possible for you to connect something to the DVI port (only that not to the VGA port) and regenerate a verbose log file? The log file shows: (II) RADEONHD(0): rhdRROutputDetect: Output DVI-D_1 (II) RADEONHD(0): FUNCTION: RHDHPDCheck (II) RADEONHD(0): RHDHPDCheck returned: 1 mask: 1 Which is strange.

maybe its some crazy asus bios setting or such stuff. i dont know how bioses initialize the various ports of todays boards with onboard graphics, or maybe its some ati/gpu firmware (is that the atombios?) or something like that.

It could be that the bit is inverted on your system. I need to verify this and see if I can find this information somewhere in AtomBIOS. I think there is a way but I'm not sure any more how to find out. We could add another flag to the quirks table - but maybe there is a way to get this info from the BIOS. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c42 --- Comment #42 from andreas bittner 2009-11-26 12:32:45 UTC --- Created an attachment (id=329652) --> (http://bugzilla.novell.com/attachment.cgi?id=329652) dvi-d direct connection only, no vga whatsoever, minimal-a, native resolution works normally -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c44 --- Comment #44 from andreas bittner 2009-11-26 12:37:13 UTC --- somewhere over the recent years i think i heard about dual-head/multi-screen configs with various graphics-cards mainboards or so in general, and there were those cases that the graphics card outputs the same signal on all/most/many of its multiple outputs in general, or just on one/some of the connectors, and all this stuff about clone displays and all this stuff. maybe the mainboard has some settings in the bios? what i was wondering is that the other hd3200 mainboards seems to behave similarly. if im not mistaken, both boards have even a third port (hdmi) onboard for connecting displays, but i have no idea what part of the system/logic (bios/atombios?) actually decides what signals are being routed to what port and how all this works. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #329652|text/x-log |text/plain mime type| | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c46 --- Comment #46 from Egbert Eich 2009-11-26 16:21:03 UTC --- Exactly the same HPD results. HPD (Hot Plug Detection) is a bit that is set when the HPD line on the DVI connector is set to 5V. The 5V signal normally comes from the line which supplies the voltage for DDC on monitors. This voltage is provided by the GFX card as monitors need to provide DDC data also when they are powered off. HPD can be used to detect if a display device has been changed. I will blacklist your as HPD not working properly in the driver. Then it will fall back to DDC to detect a monitor. This will fix one of your issues with VGA. Thanks for the BIOS btw. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558054 http://bugzilla.novell.com/show_bug.cgi?id=558054#c48 --- Comment #48 from Stefan Dirsch 2010-08-14 17:49:49 UTC --- In case you're trying with openSUSE 11.3. What are the results on 11.3 with radeon driver instead (without boot option 'nomodeset'). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.