Can someone explain why 8.12 still does not work under Ubuntu Intrepid?

[Porter]

The ATI script-built packages still do not function on a fresh install of Intrepid, on two different PCs for me.

Here's what I am doing:

I run the script with --buildpkg Ubuntu/intrepid.

I then install all of the created packages.

I then run sudo aticonfig -f --initial to create the default configuration.

I then check the xorg.conf file to verify that everything looks as it should.

Then I reboot... and after the Ubuntu splash screen, the display goes blank.

Then I beat my head against the wall for awhile. ;)



The logs indicate everything is loading up as normal, though I notice that it is defaulting to XAA rendering and there are a long string of warnings toward the end indicating "AIGLX: 3D DRIVER CLAIMS NOT TO SUPPORT VISUAL 0x23" (and 0x24, 0x25, etc). At the very end of the log it says "AIGLX: Suspending AIGLX clients for VT switch" but I think that's from me dropping to console using Ctrl-Alt-F1.


Does anyone have any advice for me? Thanks if so!

[Porter]

Hello? Can anyone help?

Thank you in advance if so! I could really use a hand with this one, I'm at the end of my rope with it and would rather not have to switch to an Nvidia solution for this box!

[Nighthog]

I have had problems installing the 8.12 drivers on Ubuntu Intrepid as well. Currently on hold on trying to get it to install.

I have a HD3200 on the GA-MA78GPM-DS2H motherboard.

I tried the manual install method described here:
http://wiki.cchtml.com/index.php/Ubuntu_Intrepid_Installation_Guide

I had problems whit that I didn't have the ia32libs installed as I had the 64bit Intrepid. Had a clean install and they weren't installed this time around and I can't get them to install (the ia32libs). I get errors whit apt-get et.c. and I can't figure out what I need to do to get them installed.
I've used these manual guides on all my FGLRX and Ubuntu installs with the 64bit versions and every each off them always said in the guide to make sure the ia32libs or similar where installed beforehand but with Ubuntu 7.04, 7.10 & 8.04 I never needed to install the ia12libs with just a fresh install as they seemingly already where there, I always just went straight to installing and didn't get errors as they worked right off the bat.
But Ubuntu 8.10 isn't as easy to my dismay.

[bridgman]

Porter, are you running the 32- or 64-bit version of Intrepid ?

[Kano]

Which gfx card do you use?

[questioneer]

8.12 worked instantly for me on intrepid. better head over to ubuntuforums.org

[Ostsol]

Worked for me using Kano's script (64-bit Kubuntu 8.10 Intrepid Ibex, RadeonHD 4870). I haven't tried ATI's built-in package-building script, though.

[Nighthog]

So someone feel like pointing to the thread/link where they say how to get it to work? Going in detail on every task/point you need to do in each step?

questioneer I've checked around ubuntuforums.org but had no luck, the ones who got it working where 32bit users, didn't find anything about 64bit users. Seems people just use the 8.10 drivers mostly as well... (to much hassle to try the manual install it seems which you need to do to install the 8.12 ones)

Ostsol I read about the Kano scripts somewhere but I didn't get much sense off what I actually needed to do whit it(the people already seemingly knew and never described or talked about how they used the script,(like I was, if I copy the script.. what the heck next? how do I run it or whatever??)
I'm not all to knowledgeable about scripts and the likes in linux/Ubuntu.

[Kano]

Well it would be good to know which gfx card you use first as serveral ppl reported issues with R300 cards. Basically for 8-12 it does not really matter if you use my script or create the packages using the installer, there is only a minor glitch in packageing which would not stop it from running.

[adamk]

So someone feel like pointing to the thread/link where they say how to get it to work? Going in detail on every task/point you need to do in each step?

questioneer I've checked around ubuntuforums.org but had no luck, the ones who got it working where 32bit users, didn't find anything about 64bit users. Seems people just use the 8.10 drivers mostly as well... (to much hassle to try the manual install it seems which you need to do to install the 8.12 ones)


I got it working on 32bit and 64bit installations on my x1950. Just downloaded the latest driver, ran "./ati-driver-installer-8-12-x86.x86_64.run --buildpkg Ubuntu/8.10", installed the packages, ran 'aticonfig --initial' and rebooted.

Adam

[gururise]

I got 8.12 working on my 64-bit Intrepid install with my 780g motherboard graphics. I used the AMD installer w/o problems. Now if AMD would fix fast user switching in fglrx, I would be a happy camper!

[Porter]

Porter, are you running the 32- or 64-bit version of Intrepid ?
Standard 32-bit desktop installation. Installed from scratch, performed normal package updates, then installed Catalyst using the packages created by the ATI script. I used the Ubuntu/intrepid switch, should I try again with the Ubuntu/8.10 switch?

Which gfx card do you use?
It is an X1550 (R500) card. Specifically, an MSI RX1550-TD256EH, which is a PCIe card.

[Porter]

Anybody else out there? 'Ello?

[Porter]

Anyone? Bridgman?


This is a totally default install, folks. Can anyone tell me why this fails, or help me diagnose it?

[conholster]

Does the default restricted driver work?

[Porter]

Does the default restricted driver work?

It did not on this card and motherboard the last time I tried it. I really don't get it. The open source driver works... I don't get why the proprietary one would fail.

[bridgman]

I don't see logs anywhere, can you pls pastebin your log ? The ideal situation would be a fresh install of Ubuntu then switch to the driver loaded by the restricted driver manager, then post the log for that. Failing that just post the log for what you have now, but that's always hard to debug because we don't know what bits are running where after all the different install attempts.

[Kano]

You can even use the desktop live cd and run my script in live mode:

http://kanotix.com/files/install-fglrx-debian.sh

That would not change your hd install at all...

[DoDoENT]

The ATI script-built packages still do not function on a fresh install of Intrepid, on two different PCs for me.
(...)

Then I reboot... and after the Ubuntu splash screen, the display goes blank.

The logs indicate everything is loading up as normal, though I notice that it is defaulting to XAA rendering and there are a long string of warnings toward the end indicating "AIGLX: 3D DRIVER CLAIMS NOT TO SUPPORT VISUAL 0x23" (and 0x24, 0x25, etc). At the very end of the log it says "AIGLX: Suspending AIGLX clients for VT switch" but I think that's from me dropping to console using Ctrl-Alt-F1.

I think I've had the similar problem with Radeon 9550R (R300 chip) and catalyst 8.12. I fixed it by adding the following lines to the section "screen" in xorg.conf:
DefaultDepth 24
SubSection "Display"
Virtual 1024 768
Depth 24
EndSubSection

Note that "Virtual" might not be necessary for you. I need it because my gdm screen shows itself in 1600x1200 instead (which causes a lot of pain in the eyes on a 17-inch CRT monitor).

[Porter]

I don't see logs anywhere, can you pls pastebin your log ? The ideal situation would be a fresh install of Ubuntu then switch to the driver loaded by the restricted driver manager, then post the log for that. Failing that just post the log for what you have now, but that's always hard to debug because we don't know what bits are running where after all the different install attempts.

This is a fresh install of Ubuntu, no previous install attempts. Also, I posted the logs from the problem in a previous thread, which was based on the driver loaded by the restricted driver manager (Catalyst 8.10).

Here's the thread, with full logs... http://www.phoronix.com/forums/showthread.php?t=13686

The problem I'm having now is the same problem as before. The logs look almost identical.

[TechMage89]

@Porter

fglrx has no support for EXA, so it always runs XAA. The "AIGLX: 3D driver claims to not support visual xx" warnings always happen (for me anyhow) and don't mean that anything is broken. Also, AIGLX always shuts down when you switch to a text terminal.

Edit: oops, sorry about that, didn't read your post clearly the first time. My best guess is that your monitor is not being detected correctly. What is your monitor's supported resolution/refresh rate?

Edit 2:
...and I answered my own question. I did some research on your monitor (found it in the Xorg log) and found out that it has a flawed EDID chip (http://www.newegg.com/Product/Product.aspx?Item=N82E16889234025). This means that you will have to override the driver and set a manual modeline in xorg.conf, because your monitor isn't feeding the correct data on supported modes to your video card.

[Porter]

Edit 2:
...and I answered my own question. I did some research on your monitor (found it in the Xorg log) and found out that it has a flawed EDID chip (http://www.newegg.com/Product/Product.aspx?Item=N82E16889234025). This means that you will have to override the driver and set a manual modeline in xorg.conf, because your monitor isn't feeding the correct data on supported modes to your video card.

Mine is one of the later versions, it does 1080p perfectly. No EDID flaw on mine. The issue with the earlier builds was an improper EDID flash, it was actually the firmware from an entirely different model of monitor. The units that had the firmware problem were fixed with a flash upgrade.

Just to be clear... my monitor displays perfect 1080p using the radeon driver on this system, it's just fglrx that has a problem. It also works perfectly in 1080p when attached to a Blu-Ray player as well. You can take a look at the EDID log in my Xorg.0.log (http://jasonporter.us/ubuntu/troubleshooting/Xorg.0.log) if you are curious.

[nbi1]

Mine is one of the later versions, it does 1080p perfectly. No EDID flaw on mine. The issue with the earlier builds was an improper EDID flash, it was actually the firmware from an entirely different model of monitor. The units that had the firmware problem were fixed with a flash upgrade.

Just to be clear... my monitor displays perfect 1080p using the radeon driver on this system, it's just fglrx that has a problem. It also works perfectly in 1080p when attached to a Blu-Ray player as well. You can take a look at the EDID log in my Xorg.0.log (http://jasonporter.us/ubuntu/troubleshooting/Xorg.0.log) if you are curious.

Did you ever get this answered/resolved? I have the same issue trying to install 8.12 on Debian lenny.

[Porter]

Did you ever get this answered/resolved? I have the same issue trying to install 8.12 on Debian lenny.

No, I didn't. I've had to switch to the radeon driver to get a working display. I even submitted a support request directly to ATI on this issue, with no response.

Everyone seems to be scratching their heads on this, with no real information so far. I suspect that none of the developers have experienced this particular problem, or it would have been sorted out by now.

[themessenger]

8.12 doesn't exactly work great for me either (780G, ATI 3200) using the ati Intrepid/8.10 packager. GDM comes up distored, but I can still log in. When I log in, there is no mouse cursor (but links and such highlight when the phantom cursor hovers) and there is an annoying 2"x2" black square at the bottom corner.

Default restricted drivers work similarly but with more distortion.

Also, VT switching is impossible. When I try, the screen just slow blinks various colors.

[nbi1]

I eventually did get it working although that was mostly due to sheer luck. Here's the choronology of events upon the install of Intrepid (just the distro):

1. Immediately upon install I tried the official ATI. It didn't work.
2. Then I switched to radeonhd. It works, but poorly.
3. Being disgusted with that I spent time getting the stock Intrepid fglrx packages installed and working. I eventually succeeded with that, but the performance was lackluster.

It now occured to me that since the stock Intrepid fglrx was working getting the official 8.12 working shouldn't be that far of a stretch. My reasoning was that if the environment looked good in terms of libraries and softlinks then the 8.12 fglrx might just be happy. And it was. Not great, but definitely a big improvement over everything that preceded it. All types of screen updates are much faster and video playback is nearly free from artifacts (still see an occasional "tear" in a video frame which is not seen under Windows playback).

My theory is that something got hosed up in the initial install attempt and switching between the open and propietary drivers didn't help the situation (IMHO the install scripts should be robust enough to gracefully handle this though). Once I got the stock Intrepid fglrx installed the system was apparently primed for installation of 8.12.

The big stinker at this point is still the inability to use fglrx with a newer kernel under Intrepid. DKMS doesn't seem to be successful at rebuilding the driver and I need to find out why (if I can :rolleyes:).

[Porter]

Unfortunately, even the standard Intrepid package of fglrx from Canonical results in no display output. X fails to start with either an empty xorg.conf or an aticonfig-generated one. It's a real bummer.

[bridgman]

Is this off a fresh install or only after installing other drivers first ?

[xemc]

Hey, I'm having the same problem. I'm running debian (a fresh install) on a [gigabyte] motherboard with the 780G chipset.

There was a thread that mentioned increasing the amount of memory allocated to the graphics - I tried that, but it didn't help. I have to blindly go to a terminal (CTRL-ALT-F2) log in as root, apt-get remove fglrx-driver, and reboot before I can use my computer again.

Can you check /var/log/messages for anything suspicious?

[xemc]

Hey, I'm having the same problem. I'm running debian (a fresh install) on a [gigabyte] motherboard with the 780G chipset.

Sorry - I should add that there were some newer fglrx drivers available in debian/lenny that I upgraded to, and that's when it stopped working. (Gives the same result as using Ati's installer)

[Porter]

Is this off a fresh install or only after installing other drivers first ?

Fresh install. I've tried it both ways, actually. I'll try the new 9-1 to see if anything changes, and let you know.

[xemc]

Sorry - I should add that there were some newer fglrx drivers available in debian/lenny that I upgraded to, and that's when it stopped working. (Gives the same result as using Ati's installer)

Actually, I saw that there were some newer driver modules available in debian/lenny - and that seemed to fix it for me. I can even get wine working, mostly.