8.37.6+feisty big problem. help plz

[sledgehammer_999]

hi I tried this guide in order to install the ATI driver. This guide worked for me perfectly for Dapper and Edgy. But for feisty nothing works.

I followed every step in the guide and had these problems:

1. when doing "sudo aticonfig --initial" I would get "segmentation fault(core dumped)"
It worked if I used "sudo aticonfig --initial --force"

2. Same thing goes for "sudo aticonfig --overlay-type=Xv"

3. When I reboot "fglrxinfo" shows that I am using Mesa.

4. After each reboot the symbolic link created by this command "sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko" doesn't exist/gets deleted.

Bottom line is that the drivers don't seem to work with Feisty. The restricted drivers(8.34.8) work just fine but I want to install the latest drivers.

Plz help me.

[Septor]

You need to add fglrx to /etc/defaults/linux-restricted-kernel-modules, build your fglrx.ko module, run "depmod -a" then reboot. That should help.

[sledgehammer_999]

do you mean /etc/default/linux-restricted-modules-common? I have already done this. To build fglrx.ko module I need to do the "sudo module-assistant prepare/update/build fglrx/install fglrx" right? I have already done this(the guide says it all). But I still have Mesa drivers and the symbolic link gets deleted.

[aga]

Not that it helps you, but your symptoms are very similar to mine on Kubuntu feisty with 8.36.5. Aticonfig faults and the link disappears, but I don't finish up on Mesa but with a black screen when X starts. Only ctrl/del works.

Maybe I should advance to 8.37 instead of abandoning fglrx? One last chance.

aga

aga

[Septor]

read your /var/log/Xorg.0.log then... it should say something about "failed to load fglrx" no doubt. Meaning that there is a problem with the kernel module not being built or installed properly. After running module-assistant, make sure run "depmod -a" otherwise you might have problems. Also you could just try "modprobe fglrx" and check "dmesg" output to see if it loaded. I am using Feisty with no problems with this driver.

[aga]

Hi Septor

Don't know if your reply was to the OP or to me. His fglrx loads as he can do fglrxinfo and it says he's on Mesa. My fglrx starts, there's no message about a kernel problem and modprobe fglrx shows it loaded. It just blackscreens at X start with no error in xorg.0.log, after the raw hex EDID data.

aga

[sledgehammer_999]

Well I haven't used your script yet. I have followed the guide mentioned on my first post which gives me a command to make a symbolic link

sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko

But this link gets deleted after each boot.

Anyway I will try your script but tell where should I place my ati-driver-installer. I don't want to re-download it.

[KanoTheMaster]

The instructions you followed are completely crap. The installer should be in /usr/src. The position you mentioned for the fglrx module is in a RAMDISK created by the linux-restricted-modules package. It is absolutely useless to symlink or do anything there. The correct way is to delete there, disable fglrx in /etc/default/linux-restricted-modules-common, install the ati kernel source package and compile that using m-a build/install fglrx-kernel-source. To be sure depmod -a would never hurt. All that is done by my script...

[sledgehammer_999]

well I tried your script. But after your script started GDM and after my reboot "fglrxinfo" tells that I am using the Mesa drivers.

I noticed something on the output of your sript(I don't think it is important). It said that it is making packages for "Ubuntu/edgy". Well I am using Feisty. And if it makes any difference the Feisty AMD64 flavor.

[KanoTheMaster]

There is no diff between edgy and feisty - I select the target depending on the xorg release because lsb-release can be wrong. Can not test AMD64 packages right now - no 64 bit system with ATI gfx card here. Could only remotely check it. Maybe you did too many manual changes... Show me the howto you had done before.

[sledgehammer_999]

the howto is linked in my first post.

If it's not big trouble could you post the steps your script takes?(I can't undestand scripts)

[zlatan]

I have the same issue... I have not found any way to fix this
I've tried installing the driver manually. Then I've tried ENVY...
My log is the same.
My System is Feisty 32bit. Nforce2 chipset + Sapphire X1600Pro 512MB
I've searched so many forums but nothing helps.
Maybe I'll just wait for the next driver version as usual... at least this time I've got 2D acceleration

[sledgehammer_999]

well I have this problem with 8.37.6 and the previous one(8.36.5). I will go back to 8.34.8(the ones from the repositories) which works great. I hope the next release will work.

By the way my chipset is nforce4 and my GPU is x1800xl 256MB

[KanoTheMaster]

@zlatan

Tested now kubuntu feisty 32 bit desktop (before gutsy desktop) live mode using my script from above. (I dislike GNOME, but the script does not require KDE.) The one and only change I did was:

deb http://archive.ubuntu.com/ubuntu feisty universe

^ remove # in front from /etc/apt/sources.list to be able to install module-assistant.

infobash output (installed externally):

Host/Kernel/OS "ubuntu" running Linux 2.6.20-15-generic i686 [ Ubuntu 7.04 ]
CPU Info AMD Athlon XP 2800+ clocked at [ 2088.112 MHz ]
Videocard ATI Radeon R350 [Radeon 9800 Pro] X.Org 7.2.0 [ 1280x1024 @75hz ]
Processes 112 | Uptime 8min | Memory 183.3/1011.5MB | HDD Size 80GB (0%used) | GLX Renderer RADEON 9800 PRO | GLX Version 2.0.6473 (8.37.6)

As you see it is not the newest card, but it works with the driver. So maybe it is a card specific problem. 64 bit I still could not test.

[KanoTheMaster]

Today I wanted to try my script with a Sapphire X1050 PCI-E card on Intel Bearlake G33 chipset. No go with any Kubuntu live cd (tested 32+64 bit, feisty+gutsy). No problem with my own live cd (Xorg 7.1.1) and another one with Xorg 1.3.0 (Debian based). I don't know that the problem should be, the same kernel (from gutsy) recompiled for etch works fine on Debian hd installs - the same Kubuntu 32 bit live cds worked with my old system and the same script. Also I needed to use a DVI-VGA adapter for a Xorg 1.3.0 live cd on 64 bit. Seems to be a really problematic card - tested with different driver releases. At least I could run the card with free ati driver too

Btw. I added a little patch for 64 bit and 2.6.22 kernel (like used in gutsy) to bypass the little missing header error and added installation of ia32-libs (Ubuntu universe) to get amdcccle working.

[zlatan]

I've Posted this bug to http://ati.cchtml.com/show_bug.cgi?id=698
Please anyone confirm.

Thanks kano for your intrest.

[KanoTheMaster]

Well when this is STILL your current /var/log/Xorg.0.log then the thing is absolutely clear. You use wrong or no fglrx kernel module. I told you already that the guide you followed is wrong in that way.

Hint: When you install Ubuntu, then the fglrx driver (maybe using my script) and then you dist-upgrade (maybe via autoupdate), then after reboot you have got no fglrx module as a new kernel is in the update. Just rerun my script in that case. When you would do the same with nvidia then you would not get X on a Debian install, Ubuntu added a fallback to redetect drivers.