PDA

View Full Version : buildpkg fails on hardy


good945
01-21-2008, 02:46 PM
hi all,
i just rried to install 8.01 on a hardy testinstall, but the installer can't generate the appropriate packages. has someone a hint?

here's the output:

ulrich@rockarolla:/usr/src$ sudo sh ./ati-driver-installer-8-01-x86.x86_64.run --buildpkg Ubuntu/hardy
Created directory fglrx-install.T17267
Verifying archive integrity... All good.
Uncompressing ATI Proprietary Linux Driver-8.452.1........................................... .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. ....
==================================================
ATI Technologies Linux Driver Installer/Packager
==================================================
Generating package: Ubuntu/hardy
Package build failed!
Package build utility output:
...
[snip cause the output is too much for the forum ;) ]
...
#dh_installchangelogs
dh_link
dh_strip
dh_compress
dh_makeshlibs
dh_installdeb
LD_PRELOAD= dh_shlibdeps
dpkg-shlibdeps: warning: symbol XQueryFont used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol _XEatData used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFillRectangle used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol _XReadPad used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFreeGC used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFree used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XGetErrorDatabaseText used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XAddToExtensionList used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol _XFlush used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: symbol dlsym used by debian/xorg-driver-fglrx/usr/lib/libGL.so.1.2 found in none of the libraries.
dpkg-shlibdeps: warning: 22 other similar warnings have been skipped (use -v to see them all).
dpkg-shlibdeps: warning: debian/xorg-driver-fglrx/usr/bin/fglrxinfo shouldn't be linked with libXext.so.6 (it uses none of its symbols).
dpkg-shlibdeps: warning: symbol XauFileName used by debian/xorg-driver-fglrx/usr/sbin/atieventsd found in none of the libraries.
dpkg-shlibdeps: warning: debian/xorg-driver-fglrx/usr/sbin/atieventsd shouldn't be linked with libXrender.so.1 (it uses none of its symbols).
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to set LD_LIBRARY_PATH.
dh_shlibdeps: command returned error code 512
make: *** [binary] Error 1
dpkg-buildpackage: failure: debian/rules binary gave error exit status 2
Removing temporary directory: fglrx-install.T17267

any hint is mucho appreciated! thanks!

BurningDiesel
01-21-2008, 07:35 PM
I'm getting the same error on a fresh hardy install with an X800.

sandain
01-21-2008, 10:26 PM
This looks like the problem I was having in Debian/lenny. I bet my solution will work for you: http://www.phoronix.com/forums/showthread.php?t=7431

good945
01-22-2008, 05:12 AM
This looks like the problem I was having in Debian/lenny. I bet my solution will work for you: http://www.phoronix.com/forums/showthread.php?t=7431
you bet it worked ;) much thanks for the hint!

the only thing to evaluate now is:
should i install a driver that's so poorly packaged or should i buy a 8800?
but *thats* another story....

thanks again!

Porter
01-22-2008, 09:41 AM
you bet it worked ;) much thanks for the hint!

the only thing to evaluate now is:
should i install a driver that's so poorly packaged or should i buy a 8800?
but *thats* another story....

thanks again!

The driver isn't poorly packaged, it works very well. It is specified for a particular set of distributions, and you aren't using one of those. I'm not sure how you can construe that as a failing on the part of ATI.

Kano
01-22-2008, 12:10 PM
My script has a workaround for the issue, just use it.

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

Michael
01-22-2008, 12:13 PM
At Phorogit.com are updated Ubuntu scripts.

Kano
01-22-2008, 02:20 PM
I highly doubt that these work. Did not try it on hardy but on AMD64 sid. Debian target is also broken with "normal" use.

good945
01-24-2008, 05:40 AM
The driver isn't poorly packaged, it works very well. It is specified for a particular set of distributions, and you aren't using one of those. I'm not sure how you can construe that as a failing on the part of ATI.

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.

it's just frustrating that, while i'm in the process of buying a new computer, i thought i would get a 3850, cause this card is a good bang for the buck. but: i use linux 99% of the time (windows/gaming is just a small part of my digital life), and it's no fun seeing that many flaws coming with the drivers.
i think i should switch. even if the alternative is way more expensive...

Kano
01-24-2008, 07:26 AM
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.

Porter
01-24-2008, 09:19 AM
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
01-24-2008, 09:26 AM
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
01-29-2008, 06:30 AM
@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
01-29-2008, 06:39 AM
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
01-29-2008, 09:05 AM
@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
01-29-2008, 12:41 PM
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
01-29-2008, 02:14 PM
What's in the Hardy repository? Amdccle reports it as 8.45.1. Isn't that 8.01?

Kano
01-29-2008, 02:41 PM
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
03-13-2008, 12:43 AM
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
03-13-2008, 04:52 AM
For gutsy - or hardy with fglrx enabled xorg.conf try this:

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

apostille
04-06-2009, 12:52 PM
I found 2 solutions:
Solution A:
Instead of sudo sh ati-driver-installer-8-5-x86.x86_64.run --buildpkg Ubuntu/hardy
Use sudo sh ati-driver-installer-8-5-x86.x86_64.run --buildpkg Ubuntu/8.04
Solution B:
doing little googling and found a solution:
Extract the archive and navigate to the new folder:
sudo sh ati-driver-installer-8-5-x86.x86_64.run --extract driver
cd driver
Navigate to where the libs are for 64 bit and make a symlink
cd arch/x86_64/usr/X11R6/lib64
ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
Build the package(the command doesn't contain errors the script just behaves wrongly)
cd ../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
It built the packages and they installed. But after reboot the monitor goes black. I switch to a console, login and do a "dmesg|grep fglrx". 5-10 lines come up and they that the driver is loaded and working!!!
I found the solution for that too. But for me is a bit strange:
sudo modprobe -r radeon
sudo modprobe fglrx
I restarted X and it worked!!! And I only had to do it once(why?!?!?)
But I have another problem:
It displayed everything in 1920*1080. My monitor's manual says that it can go only up to 1024*768. Even the Catalyst for Windows recognize it up to 1024*768. Even older versions of Linux catalyst.
What lines should I put to my xorg.conf file to limit the available resolutions to 1024*768?