[Gutsy] after ati driver update, only a black screen (light is on)

Bug #141547 reported by MyName
4
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Since last update of my system (19 sep. 2007), X doesnt work. The tty 1-6 are working. But when i try to start X the screen stay black.
RecoveryMode > $ startx = black screen
RecoveryMode > $ /etc/init.d/kdm start = black screen

Also tried dpkg-reconfigure xserver-xorg, but no luck. Reconfiguring xserver-xorg with "vesa" X works.

Laptop (Samung P35): gutsy kubuntu - 2.6.22 - ati radeon 9700m - last open repo driver

Revision history for this message
MyName (rk.) wrote :
Revision history for this message
MyName (rk.) wrote :
description: updated
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Does it work if you change the driver to vesa? Looks like a dupe of bug 132716.

Changed in xserver-xorg-video-ati:
status: New → Incomplete
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

also, try running "xrandr -q -d :0" on a virtual console (ctrl-alt-f1), and attach the output.

Revision history for this message
MyName (rk.) wrote :

Yes vesa works.

Before I start my system. I attach an external Monitor to the vga output, the monitor turn on and X start normaly on the external Monitor. Now I can swich the Output with "FN+F4" back to the notebook screen (LVDS).

I think the only problem i now that the system turn on the WRONG display. It does it also if NO external montior is attached.

Revision history for this message
MyName (rk.) wrote :

I tried now: xrandr -q -d :0

> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified

> Can't open display :0

Revision history for this message
MyName (rk.) wrote :

After doing the steps i discribed above:

With attached external Monitor:

Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 2560 x 1200
VGA-0 connected (normal left inverted right)
   1280x1024 60.0 + 75.0 59.9
   1152x864 75.0
   1024x768 74.9 75.1 60.0
   832x624 74.6
   800x600 75.0 74.9 60.3
   640x480 75.0 74.8 60.0
   720x400 70.1
LVDS connected 1400x1050+0+0 (normal left inverted right) 0mm x 0mm
   1400x1050 60.2*+
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right)

After disconnecting external Monitor (Lvds active and working)

Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 2560 x 1200
VGA-0 disconnected (normal left inverted right)
LVDS connected 1400x1050+0+0 (normal left inverted right) 0mm x 0mm
   1400x1050 60.2*+
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right)

Revision history for this message
MyName (rk.) wrote :

i don't know what was fixed or what was the cause for the failure, but since last update (xserver-xorg-video-ati) the driver works (Xorg) again.

Revision history for this message
Dietmar Rehberg (dietmar-rehberg-uni-due) wrote :

For me it doesn't work at all. But I realized, it is because my CRT Monitor was connected at the DVI port.
I use a Readeon 9800 Pro with VGA + DVI port. Connecting the Monitor back to VGA the Xorg driver works, but not on the DVI. VESA and original ATI fglrx drivers work on both ports.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Marking as fixed.

Dietmar, if you have issues with the current driver, please open a new bug report.

Changed in xserver-xorg-video-ati:
importance: Undecided → High
status: Incomplete → Fix Released
Revision history for this message
Oliver (oliver-mross) wrote :

At first, vesa works for me, but i do not want the vesa driver, because the video qualtiy is in comparison with the ati/radeon driver bad and it does not support 3D.
My video card is an ATI Radeon 9000 (RV250). Sometimes, but rarely, Gutsy works with the standard xorg.conf, i don't know why, (Fuzzy Logic).
Now we have 2007-11-15 and the driver is still buggy. Now i use feisty again.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.