fglrx (8.600) crashes on X1600 mobility

Bug #354308 reported by Patrick Cornelissen
4
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

I've upgraded to Jaunty, but the fglrx that was supposed to work (regarding the blog entries concerning fglrx) doesn't.

The system freezes when I start X. BTW: I am using Dualhead.
The radeon driver is slow as hell, so it's not an alternative.

My Hardware:

ATI Technologies Inc M56P [Radeon Mobility X1600] rev 0, ChipID = 0x71c5

The radoen driver also said this in xorg.log

(II) RADEON(0): ATOM BIOS Rom:
        SubsystemVendorID: 0x103c SubsystemID: 0x309f
        IOBaseAddress: 0x4000
        Filename: BR21601.BIN
        BIOS Bootup Message:
HP AngelFire3.0(EFL80) M56-P 256M ATOM BIOS 425e/378m

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi cornelis-p-c-software,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: crash
tags: added: needs-xorglog
tags: added: needs-lspci-vvnn
Changed in fglrx-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
Patrick Cornelissen (patrickcornelissen) wrote :

I used several xorg.conf files, the default one resulted also in a crash.
I have attached the lspci output.

When I'm at home from work I'll reproduce the xorg.log After I switched back to the radeon driver the old logfiles got overwritten.

Revision history for this message
Patrick Cornelissen (patrickcornelissen) wrote :

Argh, sorry. I have reinstalled my system with 8.10...
I won't have time today for another reinstall cycle, so I'll postpone the log file to tomorrow.

Revision history for this message
Patrick Cornelissen (patrickcornelissen) wrote :

upgrade did not succeed, there is a broken repository...
I think I'll try again next week after the holidays...

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

Other bug subscribers

Bug attachments

Remote bug watches

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