Mailinglist Archive: opensuse-bugs (10061 mails)
| < Previous | Next > |
[Bug 470341] radeonhd[HD3300/RS780, ASUS m3a78-t Mainboard] Xserver terminates immediately
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Mon, 23 Nov 2009 13:33:52 +0000
- Message-id: <20091123133352.65425CC7CD@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=470341
http://bugzilla.novell.com/show_bug.cgi?id=470341#c32
--- Comment #32 from andreas bittner <abittner@xxxxxxxxxxxxxxxxxxxx> 2009-11-23
13:33:49 UTC ---
as i suspected when attaching my flatpanel monitor cable (vga, dsub15) directly
to the mainboards vga (dsub15) port, sax2 (not the vesa version) works as well
(at least partially) and brings up a 1280x1024 resolution, even though it
claims (shown in the gui) that it detected my 1680x1050 monitor (proper size)
and it offers me to test that resolution, but never manages to switch to that
resolution properly.
right now i am back in runlevel5 writhing this bug update, and my flatpanel
onscreen display shows me 1280x1024 at 60hz, the whole screen is out of the
screen edges to the left. so this might be some other related bug in the
radeonhd.
interesting thing this time is in the sax log:
Card0 => RandR : VGA_1 connected%DVI-D_1 connected
..
..
Section "Device"
BoardName "ATI Radeon HD Graphics"
Driver "radeonhd"
Identifier "Device[0]"
Option "monitor-VGA_1" "Monitor[0]"
VendorName "ATI"
EndSection
......
in contrast to before when the vga signal went through the kvm switch.
so this time it actually talks about the vga port being connected, and dvi as
well, although that dvi port is still disconnected, nothing here, but maybe
thats just a cosmetic bug, who knows.....
sax2 log also says:
Section "Monitor"
DisplaySize 474 296
HorizSync 30-83
Identifier "Monitor[0]"
ModelName "LG ELECTRONICS L227W"
Option "DPMS"
Option "PreferredMode" "1680x1050"
VendorName "GSM"
VertRefresh 43-75
UseModes "Modes[0]"
EndSection
but it somehow doesnt manage to setup the 1680x1050 even though the sax2 gui
said that that was being chosen and actived.....
any more help needed?
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=470341#c32
--- Comment #32 from andreas bittner <abittner@xxxxxxxxxxxxxxxxxxxx> 2009-11-23
13:33:49 UTC ---
as i suspected when attaching my flatpanel monitor cable (vga, dsub15) directly
to the mainboards vga (dsub15) port, sax2 (not the vesa version) works as well
(at least partially) and brings up a 1280x1024 resolution, even though it
claims (shown in the gui) that it detected my 1680x1050 monitor (proper size)
and it offers me to test that resolution, but never manages to switch to that
resolution properly.
right now i am back in runlevel5 writhing this bug update, and my flatpanel
onscreen display shows me 1280x1024 at 60hz, the whole screen is out of the
screen edges to the left. so this might be some other related bug in the
radeonhd.
interesting thing this time is in the sax log:
Card0 => RandR : VGA_1 connected%DVI-D_1 connected
..
..
Section "Device"
BoardName "ATI Radeon HD Graphics"
Driver "radeonhd"
Identifier "Device[0]"
Option "monitor-VGA_1" "Monitor[0]"
VendorName "ATI"
EndSection
......
in contrast to before when the vga signal went through the kvm switch.
so this time it actually talks about the vga port being connected, and dvi as
well, although that dvi port is still disconnected, nothing here, but maybe
thats just a cosmetic bug, who knows.....
sax2 log also says:
Section "Monitor"
DisplaySize 474 296
HorizSync 30-83
Identifier "Monitor[0]"
ModelName "LG ELECTRONICS L227W"
Option "DPMS"
Option "PreferredMode" "1680x1050"
VendorName "GSM"
VertRefresh 43-75
UseModes "Modes[0]"
EndSection
but it somehow doesnt manage to setup the 1680x1050 even though the sax2 gui
said that that was being chosen and actived.....
any more help needed?
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.
| < Previous | Next > |