Backport of fglrx to Feisty needed for radeon x1300 support

Bug #117013 reported by ChrisN_uk
12
Affects Status Importance Assigned to Milestone
Feisty Backports
Won't Fix
Undecided
Unassigned
Ubuntu
Fix Released
Undecided
Unassigned

Bug Description

Installing Feisty was not a problem, everything works fine until I try to use the restricted drivers. Then when I reboot, the screen freezes black.
I'm using an ATI radeon x1300 which is working with the vesa drivers and I have tried many guides to get fglrx working, though none help.
also:

$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (1.5 Mesa 6.5.2)

Tags: fglrx x1300
Revision history for this message
ChrisN_uk (chris-nicholls) wrote :
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. The 'xorg.conf' file you posted has the vesa driver. Could you please post your 'xorg.conf' file you use with fglrx? Thanks in advance.

Revision history for this message
ChrisN_uk (chris-nicholls) wrote :

Ok, this is my xorg.conf at the moment. I have ubuntu up and running with the vesa driver, but I've just enabled the fglrx in the restricted driver modules. At this point, if i restart, Feisty freezes on startup. Is there a log file it would be usefull to post?

Revision history for this message
Brian Murray (brian-murray) wrote :

The log file '/var/log/Xorg.0.log' or '/var/log/Xorg.0.log.old' would be useful. Thanks again.

Revision history for this message
ChrisN_uk (chris-nicholls) wrote :

OK, here they are as they stand. I'll restart, get to black screen, reboot into recovery and save the files then edit drivers and post the new ones too!

Revision history for this message
ChrisN_uk (chris-nicholls) wrote :
Revision history for this message
ChrisN_uk (chris-nicholls) wrote :

Ok, here are the new files.

The line
(WW) fglrx: No matching Device section for instance (BusID PCI:3:0:1) found

looks interesting...

Revision history for this message
acron_bn (acron-bn) wrote :

Hello,
I have the same problem as ChrisN_uk , this is my story: I installed a Kubuntu Feisty, and then a tried the restricted fglrx driver (v.8.37), and modified the xorg.conf ( "Driver" "fglrx", "Composite" "0"), I did the aticonfig --initial and aticonfig --overlay-type=Xv but It just messed up my xorg.conf so I did manually. After reboot all I got was a black screen. I took a look to the Xorg.0.log and most of the time it got stuck when loading the fglrxdrm. I had the same problem with a Debian Etch distro, It only worked out with the fglrx v8.28 from the debian repositories.
Anyway, but taking a look to the Xorg.0.log.error.The line
(WW) fglrx: No matching Device section for instance (BusID PCI:3:0:1) found
 This error usually appears when the driver doesn´t support your card GPU.

Revision history for this message
ChrisN_uk (chris-nicholls) wrote :

So are things working for you now?

Revision history for this message
acron_bn (acron-bn) wrote :

I did install a fglrx driver 8.28 from the debian repositories and it worked fine, but in a debian distro. And when I tried to install a later than 8.28 version in that same Debian I got the same error you have here.

(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
 compiled for 7.1.0, module version = 8.34.8
 ABI class: X.Org Server Extension, version 0.3

Aparently, the kernel "dies" when it loads this module. A friend told me that maybe the kernel is not compile with the same driver that it is loading, he also explained me a way to do it. But I don't remember how, all I know is that we need the kernel sources and then we go to /usr/src and do a make ...and few more things. I have been told that we don't need the kernel sources since we have the kernel headers, and when we do a module-assistant prepare, build and install, all this procedure compiles the kernel with the driver.
Finally, since the module-assistant way doesn't work, maybe we have to tried the old fashion way. I'm gonna find out how to compile the kernel and also how to erase any fglrx old driver from the system. If anyone in here knows all this, could be a very good help.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. However, this bug is a duplicate of bug 96279 and is being marked as such. Incidentally, new fglrx drivers supporting your card have been added to Gutsy. Feel free to submit any future bugs you may find.

Revision history for this message
Jeff Rasmussen (jeffrasmussen) wrote :

I'm also experiencing this problem on a x1300 card for a Dell PC. I am not using the Radeon Mobility x1300.

When trying to load fglrx I get this message 'sudo modprobe fglrx'
    FATAL: Error running install command for fglrx

I'm able to get my card to work with Feisty kernel version 2.6.20-15-generic. I only have this problem on 2.6.20-16-generic.

If Feisty does need a newer fglrx driver I would like to see a backport of some type.

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

Assigning to feisty-backports. A gutsy version of fglrx that fixes radeon x1300 has been uploaded and confirmed to fix.

Jeff, Chris, and acron, please verify the feisty debs I've provided solve the issue, and also if you could, please work directly with the feisty-backport team to get this added to feisty.

Revision history for this message
ChrisN_uk (chris-nicholls) wrote :

Sorry for the stupid question but which debs do I need to install and how? I'm more than happy to help any way i can, I just don't really know what I'm doing.

Revision history for this message
Jeff Rasmussen (jeffrasmussen) wrote :

The most recent update to the fglrx driver seems to work for me under the 2.6.20-16-generic kernel around the 6/29/07 timeframe.

/var/log/dpkg
upgrade fglrx-control 8.34.8+2.6.20.5-16.28 8.34.8+2.6.20.5-16.29
upgrade xorg-driver-fglrx 7.1.0-8.34.8+2.6.20.5-16.28 7.1.0-8.34.8+2.6.20.5-16.29
upgrade linux-restricted-modules-2.6.20-16-generic 2.6.20.5-16.28 2.6.20.5-16.29

Is anyone else seeing this improvement?

Revision history for this message
John Dong (jdong) wrote :

this is a kernel module, which the Backports team cannot handle.

Changed in feisty-backports:
status: New → Won't Fix
Revision history for this message
Nizar Kerkeni (nizarus) wrote :

Same card and same problem, black screen with fglrx driver, in amd64 architecture.

Revision history for this message
ChrisN_uk (chris-nicholls) wrote :

I just tried the new updates, 8.39.4, but still get the black screen no matter what I try...

Revision history for this message
Nizar Kerkeni (nizarus) wrote :

ATI driver 8.39.4 successfully installed on feisty (amd64) following this installation guide (Method 2) : http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide#Method_1:_Install_the_Driver_the_Ubuntu_Way

But no success on gutsy (amd64)

Revision history for this message
Max Bowsher (maxb) wrote :

As the exisitng information in this bug states that it is fixed in Gutsy, I am setting the Ubuntu bugtask's status to "Fix Released".

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.