buildpkg fails on hardy

[Porter]

well... i KNOW what i speak off, cause i use ATI hardware for a couple of years now with linux. to be specific, since redhat 9, which came out in 2003. so then let me conclude, that i am perfectly aware of what to expect when dealing with ATI GPUs in linux.

You missed my point. I was pointing out that you said you are frustrated that the script doesn't work on Hardy Heron, but ATI never claimed it would work on Hardy. It's specified to work on Gutsy... which you're not using. Therefore, I fail to see why you can legitimately be upset with ATI about that.

[Michael]

You missed my point. I was pointing out that you said you are frustrated that the script doesn't work on Hardy Heron, but ATI never claimed it would work on Hardy. It's specified to work on Gutsy... which you're not using. Therefore, I fail to see why you can legitimately be upset with ATI about that.

Not to mention that all packaging scripts outside of the RHEL/RF/SuSE umbrella are all maintained by the community and not ATI...

[good945]

@Kano

You can get rid of many problems if you don't use a xserver 1.4 based distro. My own distribution (KANOTIX) has even only Xorg 7.1.1 (etch) and is much more stable than lots of others - just don't try beryl with ATI there... ATI drivers really dislike anything newer than Xserver 1.3 - so gutsy would be one possibility. hardy or sid is currently no good choice.

i'm aware that hardy is not ready for prime time, i only use it as a testing ground. but the missing symlink is in the package, not in hardy.

@porter

You missed my point. I was pointing out that you said you are frustrated that the script doesn't work on Hardy Heron, but ATI never claimed it would work on Hardy. It's specified to work on Gutsy... which you're not using. Therefore, I fail to see why you can legitimately be upset with ATI about that.

if i specify --buildpkg Ubuntu/gutsy the script fails either. so whats the point? also, --listpackage shows hardy as an option. and as for the supported distros: do they get Xv video?

@Michael

Not to mention that all packaging scripts outside of the RHEL/RF/SuSE umbrella are all maintained by the community and not ATI...

i wasn't aware that all packaging regarding other distros is handled by the community! and i appreciate all the effort of all involved, really!
BUT (yes it has to be a big but): i think i can say i lost faith in ATI. though the sad part of the story is, that i still think that ATI delivers the better hardware. on the software/driver side, ATI just sucks.

[Kano]

Currently edgy=feisty and gutsy=hardy as target - so don't expect differnet behaviour. The new gutsy/hardy targets just use dkms. The only way is to patch those on the fly which my script does. The use of edgy as target is no real drawback because the use of module assistant has also some good side aspects like complete removal of the created modules on remove. The dkms variant leaves the built modules in the wild on remove - which can lead into problems when you want to switch manually from one driver to the other. As the hardy xorg.conf file is not fully written (no Driver line, no forced ColorDepth) it is not correclty modified by my current script, it works till gutsy without change but still can be used to install the driver - you just have to selfmodify the xorg.conf (after that delete the xorg.conf.1st file which is used as input for my script). Before I forget it: the override file for compiz is also only in the gutsy/hardy target, but modififing this manually is not that hard.

[Porter]

@porter

if i specify --buildpkg Ubuntu/gutsy the script fails either. so whats the point? also, --listpackage shows hardy as an option. and as for the supported distros: do they get Xv video?

The "hardy" option in the script is not yet implemented. What you're seeing is a placeholder for future evolution of the script.

The script does NOT support Hardy yet, and they say so right on the download page. I'm not sure how that could possibly have been misconstrued.

[Kano]

Well I am sure you can prove what you said, do you? Here how to check:

sh ati-installer.sh --extract ati
cd ati
grep -i hardy -R *

packages/Ubuntu/ati-packager.sh:HARDY="hardy 8.04"
packages/Ubuntu/ati-packager.sh: echo $DAPPER $EDGY $FEISTY $GUTSY $HARDY
packages/Ubuntu/ati-packager.sh: hardy|8.04) X_DIR=x710; X_NAME=hardy;;


$X_NAME is used later to switch to the packages/Ubuntu/dists/$X_NAME dir. Ok, feisty is a tiny bit different to edgy, it begins with the compiz override. For hardy this is useless as the current fglrx driver does not support it anyway with Xserver 1.4. The only diff for hardy is the missing libstdc++5 depend... what a huge change.

[rbmorse]

What's in the Hardy repository? Amdccle reports it as 8.45.1. Isn't that 8.01?

[Kano]

Yes that's correct.

awk '/^label=/' ati-driver-installer-8-01-x86.x86_64.run
label="ATI Proprietary Linux Driver-8.452.1"

[Patrick-Steven]

Ubuntu fails to recognize ATI Radeon HD 2600 Pro graphics card (512 MB, 800 mHz PCIe card). I checked the incompatibility list and I've seen others with the same issue, but no resolution. When I install the restricted fglrx drivers for it and reboot, the screen goes black and freezes, and I must reboot and reconfigure the xorg file manually.

I was wondering if anyone found a solution to get these ATI cards to work. I really want to use 3D desktop effects (compiz-fusion, games, etc.). Is there a solution on Ubuntu or is there another distro where it does work?

[Kano]

For gutsy - or hardy with fglrx enabled xorg.conf try this:

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