Since linux-2.6.22 went stable, this is the only (well, the best) ati driver to stabilize along with it. I know it's been nowhere near 30 days, but in this case I feel quick stabilization is warranted. Thank You, je_fro
Well at least 3d works as expected, other bugs on my side are related to my hardware, so Stable on x86
it doesn't work with emerge on my box. >>> Emerging (1 of 1) x11-drivers/ati-drivers-8.39.4 to / * ati-driver-installer-8.39.4-x86.x86_64.run RMD160 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run SHA1 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run SHA256 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking ati-driver-installer-8.39.4-x86.x86_64.run ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.22-gentoo-r4/build * Found sources for kernel version: * 2.6.22-gentoo-r4 >>> Unpacking source... gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory * * ERROR: x11-drivers/ati-drivers-8.39.4 failed. * Call stack: * ebuild.sh, line 1654: Called dyn_unpack * ebuild.sh, line 768: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * ati-drivers-8.39.4.ebuild, line 127: Called die * * manpage unzip failed * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-8.39.4/temp/build.log'. * * Messages for package x11-drivers/ati-drivers-8.39.4: * * ERROR: x11-drivers/ati-drivers-8.39.4 failed. * Call stack: * ebuild.sh, line 1654: Called dyn_unpack * ebuild.sh, line 768: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * ati-drivers-8.39.4.ebuild, line 127: Called die * * manpage unzip failed * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-8.39.4/temp/build.log'. * Portage 2.1.3.6 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.5-r4, 2.6.22-gentoo-r4 i686) ================================================================= System uname: 2.6.22-gentoo-r4 i686 Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz Gentoo Base System release 1.12.9 Timestamp of tree: Wed, 22 Aug 2007 03:00:01 +0000 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=prescott -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -march=prescott -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="candy distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LINGUAS="de" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/qip-portage" SYNC="rsync://ftp-stud.hs-esslingen.de/gentoo-portage" USE="X acl alsa apache2 bash-completion berkdb bitmap-fonts cli cracklib crypt cups dri dvdr fortran gdbm gif gpm gtk iconv ipv6 isdnlog jpeg midi mp3 mudflap mysql ncurses nls nptl nptlonly opengl openmp pam pcre perl png pppd python readline reflection session spl ssl tcpd truetype-fonts type1-fonts unicode usb vhosts x86 xinerama xorg zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse synaptics evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="fglrx i810 vesa fbdev" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS if i run the installer ati-driver-installer-8.39.4-x86.x86_64.run, it works without problems... also ati-drivers-8.35.5 merge correctly on my system. Any hints?
(In reply to comment #2) > it doesn't work with emerge on my box. > > >>> Emerging (1 of 1) x11-drivers/ati-drivers-8.39.4 to / > * ati-driver-installer-8.39.4-x86.x86_64.run RMD160 ;-) ... > > gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory On your system, is /bin/sh a symlink to /bin/bash ? Or do you have /var mounted on a separate partition with strange permissions? Your tree has today's timestamp, so I'm guessing you have the line: #Switching to a standard way to extract the files since otherwise no signature file #would be created sh "${src}" --extract "${S}" 2&>1 /dev/null around line 123 of the file: /usr/portage/x11-drivers/ati-drivers/ati-drivers-8.39.4.ebuild ?
(In reply to comment #3) > (In reply to comment #2) > > it doesn't work with emerge on my box. > > > > >>> Emerging (1 of 1) x11-drivers/ati-drivers-8.39.4 to / > > * ati-driver-installer-8.39.4-x86.x86_64.run RMD160 ;-) ... > > > > gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory > > On your system, is /bin/sh a symlink to /bin/bash ? > Or do you have /var mounted on a separate partition with strange permissions? 0 lrwxrwxrwx 1 root root 4 Aug 13 02:22 /bin/sh -> bash /var/tmp/portage was ramfs, but isn't anymore... no improvement... permissions in it follow: total 12 4 drwxrwxr-x 3 portage portage 4096 Aug 22 06:17 . 4 drwxrwxrwt 8 root root 4096 Aug 22 07:01 .. 4 drwxrwxr-x 3 portage portage 4096 Aug 22 06:17 x11-drivers > > Your tree has today's timestamp, so I'm guessing you have the line: > > #Switching to a standard way to extract the files since otherwise no > signature file > #would be created > sh "${src}" --extract "${S}" 2&>1 /dev/null > > around line 123 of the file: > > /usr/portage/x11-drivers/ati-drivers/ati-drivers-8.39.4.ebuild thats correct, i have these two lines in my ebuild. i had that situation with version 8.40.x, too.
Can you try with these FEATURES in your make.conf? FEATURES="collision-protect cvs digest strict multilib-strict parallel-fetch sandbox"
~ # FEATURES="collision-protect cvs digest strict multilib-strict parallel-fetch sandbox" emerge -av ati-drivers These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild U ] x11-drivers/ati-drivers-8.39.4 [8.35.5] USE="-acpi (-multilib) (-qt3%)" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] Yes >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) x11-drivers/ati-drivers-8.39.4 to / * ati-driver-installer-8.39.4-x86.x86_64.run MD5 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run RMD160 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run SHA1 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run SHA256 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run size ;-) ... [ ok ] >>> Creating Manifest for /usr/portage/x11-drivers/ati-drivers digest.assumed 10 digest-ati-drivers-8.27.10-r1::ati-driver-installer-8.27.10-x86.run digest-ati-drivers-8.27.10-r1::ati-driver-installer-8.27.10-x86_64.run digest-ati-drivers-8.28.8::ati-driver-installer-8.28.8.run digest-ati-drivers-8.32.5::ati-driver-installer-8.32.5-x86.x86_64.run digest-ati-drivers-8.33.6::ati-driver-installer-8.33.6-x86.x86_64.run digest-ati-drivers-8.33.6-r1::ati-driver-installer-8.33.6-x86.x86_64.run digest-ati-drivers-8.34.8::ati-driver-installer-8.34.8-x86.x86_64.run digest-ati-drivers-8.35.5::ati-driver-installer-8.35.5-x86.x86_64.run digest-ati-drivers-8.36.5::ati-driver-installer-8.36.5-x86.x86_64.run digest-ati-drivers-8.37.6::ati-driver-installer-8.37.6-x86.x86_64.run digest-ati-drivers-8.37.6-r1::ati-driver-installer-8.37.6-x86.x86_64.run digest-ati-drivers-8.40.4::ati-driver-installer-8.40.4-x86.x86_64.run * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking ati-driver-installer-8.39.4-x86.x86_64.run ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.22-gentoo-r4/build * Found sources for kernel version: * 2.6.22-gentoo-r4 >>> Unpacking source... gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory * * ERROR: x11-drivers/ati-drivers-8.39.4 failed. * Call stack: * ebuild.sh, line 1654: Called dyn_unpack * ebuild.sh, line 768: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * ati-drivers-8.39.4.ebuild, line 127: Called die * * manpage unzip failed * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-8.39.4/temp/build.log'. * * Messages for package x11-drivers/ati-drivers-8.39.4: * * ERROR: x11-drivers/ati-drivers-8.39.4 failed. * Call stack: * ebuild.sh, line 1654: Called dyn_unpack * ebuild.sh, line 768: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * ati-drivers-8.39.4.ebuild, line 127: Called die * * manpage unzip failed * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-8.39.4/temp/build.log'. *
Hmmmm.... I'm stumped. Let me sleep on it.
looks like i have an MD5 checksum-error, too... amy ~ # cd /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work/ amy work # ls 1 amy work # cat 1 Warning: target directory exists /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work Verifying archive integrity...Error in MD5 checksums: cda1adeee47f0c6e83b6e1a0ee6a4abf is different from 93e8e0aaecc82bceed72dccdaf0a516e the funny thin is, if i run this .run-file manually, it works...
(In reply to comment #8) Would you try emerging the package after deleting /usr/portage/distfiles/ati* ?
* checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking ati-driver-installer-8.39.4-x86.x86_64.run ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.22-gentoo-r4/build * Found sources for kernel version: * 2.6.22-gentoo-r4 >>> Unpacking source... gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory * * ERROR: x11-drivers/ati-drivers-8.39.4 failed. * Call stack: * ebuild.sh, line 1654: Called dyn_unpack * ebuild.sh, line 768: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * ati-drivers-8.39.4.ebuild, line 127: Called die * * manpage unzip failed * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-8.39.4/temp/build.log'. * * Messages for package x11-drivers/ati-drivers-8.39.4: * * ERROR: x11-drivers/ati-drivers-8.39.4 failed. * Call stack: * ebuild.sh, line 1654: Called dyn_unpack * ebuild.sh, line 768: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * ati-drivers-8.39.4.ebuild, line 127: Called die * * manpage unzip failed * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-8.39.4/temp/build.log'. * amy ~ # cat /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work/1 Warning: target directory exists /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work Verifying archive integrity...Error in MD5 checksums: cda1adeee47f0c6e83b6e1a0ee6a4abf is different from 93e8e0aaecc82bceed72dccdaf0a516e amy ~ # sha1sum /usr/portage/distfiles/ati-driver-installer-8.39.4-x86.x86_64.run 2b1b66169df36c3e6c811562b63642ff4dce2b1d /usr/portage/distfiles/ati-driver-installer-8.39.4-x86.x86_64.run --- amy ~ # sh /usr/portage/distfiles/ati-driver-installer-8.39.4-x86.x86_64.run Created directory fglrx-install.JTdUn9 Verifying archive integrity... All good. Uncompressing ATI Proprietary Linux Driver-8.39.4..................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... ================================================== ATI Technologies Linux Driver Installer/Packager ================================================== Detected configuration: Architecture: i686 (32-bit) X Server: X.Org 7.1 and later releases --- and after i close the window, that appears next: Removing temporary directory: fglrx-install.JTdUn9 --- re-downloading doesn't change a thing, i suppose...
(In reply to comment #10) > * checking ebuild checksums ;-) ... [ ok > ] > * checking auxfile checksums ;-) ... [ ok > ] > * checking miscfile checksums ;-) ... [ ok > ] > * checking ati-driver-installer-8.39.4-x86.x86_64.run ;-) ... [ ok > ] > * Determining the location of the kernel source code > * Found kernel source directory: > * /usr/src/linux > * Found kernel object directory: > * /lib/modules/2.6.22-gentoo-r4/build > * Found sources for kernel version: > * 2.6.22-gentoo-r4 > >>> Unpacking source... > gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory > * > * ERROR: x11-drivers/ati-drivers-8.39.4 failed. > * Call stack: > * ebuild.sh, line 1654: Called dyn_unpack > * ebuild.sh, line 768: Called qa_call 'src_unpack' > * ebuild.sh, line 44: Called src_unpack > * ati-drivers-8.39.4.ebuild, line 127: Called die > * > * manpage unzip failed > * If you need support, post the topmost build error, and the call stack if > relevant. > * A complete build log is located at > '/var/tmp/portage/x11-drivers/ati-drivers-8.39.4/temp/build.log'. > * > > * Messages for package x11-drivers/ati-drivers-8.39.4: > > * > * ERROR: x11-drivers/ati-drivers-8.39.4 failed. > * Call stack: > * ebuild.sh, line 1654: Called dyn_unpack > * ebuild.sh, line 768: Called qa_call 'src_unpack' > * ebuild.sh, line 44: Called src_unpack > * ati-drivers-8.39.4.ebuild, line 127: Called die > * > * manpage unzip failed > * If you need support, post the topmost build error, and the call stack if > relevant. > * A complete build log is located at > '/var/tmp/portage/x11-drivers/ati-drivers-8.39.4/temp/build.log'. > * > > amy ~ # cat /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work/1 > Warning: target directory exists > /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work > Verifying archive integrity...Error in MD5 checksums: > cda1adeee47f0c6e83b6e1a0ee6a4abf is different from > 93e8e0aaecc82bceed72dccdaf0a516e > > amy ~ # sha1sum > /usr/portage/distfiles/ati-driver-installer-8.39.4-x86.x86_64.run > 2b1b66169df36c3e6c811562b63642ff4dce2b1d > /usr/portage/distfiles/ati-driver-installer-8.39.4-x86.x86_64.run > --- > > amy ~ # sh /usr/portage/distfiles/ati-driver-installer-8.39.4-x86.x86_64.run > Created directory fglrx-install.JTdUn9 > Verifying archive integrity... All good. > Uncompressing ATI Proprietary Linux > Driver-8.39.4..................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... > ================================================== > ATI Technologies Linux Driver Installer/Packager > ================================================== > Detected configuration: > Architecture: i686 (32-bit) > X Server: X.Org 7.1 and later releases > --- > and after i close the window, that appears next: > > Removing temporary directory: fglrx-install.JTdUn9 > > > --- > re-downloading doesn't change a thing, i suppose... > If you would please change this line in the ebuild ... sh "${src}" --extract "${S}" 2&>1 /dev/null to sh "${src}" --extract "${S}" This will tell ya if it is extracting the files as expected. If it is not you have permission issues elsewhere.
>>> Emerging (1 of 1) x11-drivers/ati-drivers-8.39.4 to / * ati-driver-installer-8.39.4-x86.x86_64.run MD5 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run RMD160 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run SHA1 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run SHA256 ;-) ... [ ok ] * ati-driver-installer-8.39.4-x86.x86_64.run size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking ati-driver-installer-8.39.4-x86.x86_64.run ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.22-gentoo-r4/build * Found sources for kernel version: * 2.6.22-gentoo-r4 >>> Unpacking source... Warning: target directory exists /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work Verifying archive integrity...Error in MD5 checksums: cda1adeee47f0c6e83b6e1a0ee6a4abf is different from 93e8e0aaecc82bceed72dccdaf0a516e gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory --- well, still that checksum-error..
(In reply to comment #12) > >>> Emerging (1 of 1) x11-drivers/ati-drivers-8.39.4 to / > * ati-driver-installer-8.39.4-x86.x86_64.run MD5 ;-) ... > > [ ok ] > * ati-driver-installer-8.39.4-x86.x86_64.run RMD160 ;-) ... > > [ ok ] > * ati-driver-installer-8.39.4-x86.x86_64.run SHA1 ;-) ... > > [ ok ] > * ati-driver-installer-8.39.4-x86.x86_64.run SHA256 ;-) ... > > [ ok ] > * ati-driver-installer-8.39.4-x86.x86_64.run size ;-) ... > > [ ok ] > * checking ebuild checksums ;-) ... > > [ ok ] > * checking auxfile checksums ;-) ... > > [ ok ] > * checking miscfile checksums ;-) ... > > [ ok ] > * checking ati-driver-installer-8.39.4-x86.x86_64.run ;-) ... > > [ ok ] > * Determining the location of the kernel source code > * Found kernel source directory: > * /usr/src/linux > * Found kernel object directory: > * /lib/modules/2.6.22-gentoo-r4/build > * Found sources for kernel version: > * 2.6.22-gentoo-r4 > >>> Unpacking source... > Warning: target directory exists > /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work > Verifying archive integrity...Error in MD5 checksums: > cda1adeee47f0c6e83b6e1a0ee6a4abf is different from > 93e8e0aaecc82bceed72dccdaf0a516e > gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory > > --- > well, still that checksum-error.. > You have bigger issue then the ebuild not finding the man page it is failing to unpack the entire archieve. Only way you will be able to figure out what is causing the problem is to remove the distfiles work dir and the Manifest from the tree and redigest it once more. I have tested this over and over and all is fine with the ebuild.
Ebuild and driver work fine for me on amd64 with kernel 2.6.22-gentoo-r5 on a FireGL 5250. amdcccle still segfaults however.
(In reply to comment #13) > (In reply to comment #12) > > >>> Emerging (1 of 1) x11-drivers/ati-drivers-8.39.4 to / > > * ati-driver-installer-8.39.4-x86.x86_64.run MD5 ;-) ... > > > > [ ok ] > > * ati-driver-installer-8.39.4-x86.x86_64.run RMD160 ;-) ... > > > > [ ok ] > > * ati-driver-installer-8.39.4-x86.x86_64.run SHA1 ;-) ... > > > > [ ok ] > > * ati-driver-installer-8.39.4-x86.x86_64.run SHA256 ;-) ... > > > > [ ok ] > > * ati-driver-installer-8.39.4-x86.x86_64.run size ;-) ... > > > > [ ok ] > > * checking ebuild checksums ;-) ... > > > > [ ok ] > > * checking auxfile checksums ;-) ... > > > > [ ok ] > > * checking miscfile checksums ;-) ... > > > > [ ok ] > > * checking ati-driver-installer-8.39.4-x86.x86_64.run ;-) ... > > > > [ ok ] > > * Determining the location of the kernel source code > > * Found kernel source directory: > > * /usr/src/linux > > * Found kernel object directory: > > * /lib/modules/2.6.22-gentoo-r4/build > > * Found sources for kernel version: > > * 2.6.22-gentoo-r4 > > >>> Unpacking source... > > Warning: target directory exists > > /var/tmp/portage/x11-drivers/ati-drivers-8.39.4/work > > Verifying archive integrity...Error in MD5 checksums: > > cda1adeee47f0c6e83b6e1a0ee6a4abf is different from > > 93e8e0aaecc82bceed72dccdaf0a516e > > gzip: common/usr/share/man/man8/atieventsd.8.gz: No such file or directory > > > > --- > > well, still that checksum-error.. > > > > You have bigger issue then the ebuild not finding the man page it is failing to > unpack the entire archieve. Only way you will be able to figure out what is > causing the problem is to remove the distfiles work dir and the Manifest from > the tree and redigest it once more. I have tested this over and over and all is > fine with the ebuild. > ok... i have deleted all contents of /var/tmp/portage, i have deleted all contents of /usr/portage/x11-drivers/ati-drivers/files/, I have deleted my Manifest file i have erased my downloaded distfiles. Further i did ebuild /usr/portage/x11-drivers/ati-drivers/ati-drivers-8.39.4.ebuild then portage downloaded all distfiles about ati-drivers from my mirror. After that i tried to emerge it again. Same result... I even downloaded the latest .run-file from ati website (its 8.40.4 now) and tried to emerge it after I erased that files mentioned above... same result. All drivers run stand alone without problems. Really all of it. so i can say, there is nothing broken with the driver-files themselves. Any options left, i haven't tried? Maybe there is one little tool different on my box?
Uh, uh, uh ... Dont't think stabilizing 8.39.4 for x86 has been a good idea! I have a X1400 card in a Thinkpad R60 running gentoo x86 (2007.0) and kernel 2.6.22-gentoo-r5. Whereas 8.35.5 works OK including direct rendering support, 8.39.4 crashes frequently (destorted screen, blank console, no keyboard input) on my system. It's clear that gentoo can't do anything to fix the binary package from ati/amd, but you could mask (at least not stabilize) a package that is known to not work as per user feedback... :-) Meanwhile I'll give 8.37.6-r1 a shot for it should work on kernel 2.6.22, too. Thanks, Axel
(In reply to comment #16) > Whereas 8.35.5 works OK including direct rendering support, 8.39.4 crashes > frequently (destorted screen, blank console, no keyboard input) on my > system. > > It's clear that gentoo can't do anything to fix the binary package from > ati/amd, but you could mask (at least not stabilize) a package that is > known to not work as per user feedback... :-) > > Meanwhile I'll give 8.37.6-r1 a shot for it should work on kernel 2.6.22, too. > > Thanks, > Axel Or you could try 8.40.4 also... Thanks
ok, guys, sorry for the noise. I had a link of /bin/md5sum and /bin/sha1sum on busybox 1.4.2. Portage first looks for binaries in /bin/ and got these links. if i do that manually, the pointers are right to /usr/bin/md5sum and /usr/bin/sha1sum according to what which says. hopefully i have fixed my "bb --install-symlinks" issue now.
(In reply to comment #17) > Or you could try 8.40.4 also... As of your suggestion I've tried "8.40.4" instead of "8.37.6-r1" and so far everything looks good, though I haven't found anything in ati/adm's release notes for 8.40.4 that looks like a fix for my problem ... On the other hand these "release notes" seem to be generally incomplete and sometimes even incorrect. Or how would you call a "fixed in 8.40.4 issue" (737-28847) that -- when you lookup the details -- suggests to update to 8.39.4 or later ... I'm getting sick of these binary-only, propietary drivers ... But I still don't think that the open source drivers already support X1400 (at least for 2D accelartion) or do they? Cheers, Axel
(In reply to comment #19) > (In reply to comment #17) > > Or you could try 8.40.4 also... > As of your suggestion I've tried "8.40.4" instead of "8.37.6-r1" and so far > everything looks good, though I haven't found anything in ati/adm's release > notes for 8.40.4 that looks like a fix for my problem ... > OK, 8.40.4 seems to be working for me ... So I've reinstalled 8.39.4 to figure out what might have gone wrong, and I've found an interesting kernel message .... When starting X either by running "startx" or by running "/etc/init.d/xdm start" the following modules are already loaded (I've skipped some [...]): ---------------------------------------------------------------- Module Size Used by [...] fglrx 730976 17 i2c_i801 7568 0 i2c_core 19840 1 i2c_i801 intel_agp 21332 0 agpgart 27080 2 fglrx,intel_agp ---------------------------------------------------------------- Immediately when X comes up the following kernel messages are written ---------------------------------------------------------------- Aug 27 12:32:32 solarfire Uhhuh. NMI received for unknown reason a0 on CPU 0. Aug 27 12:32:32 solarfire You have some hardware problem, likely on the PCI bus. Aug 27 12:32:32 solarfire Dazed and confused, but trying to continue Aug 27 12:32:32 solarfire ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Aug 27 12:32:33 solarfire [fglrx] total GART = 130023424 Aug 27 12:32:33 solarfire [fglrx] free GART = 114032640 Aug 27 12:32:33 solarfire [fglrx] max single GART = 114032640 Aug 27 12:32:33 solarfire [fglrx] total LFB = 134086656 Aug 27 12:32:33 solarfire [fglrx] free LFB = 126038016 Aug 27 12:32:33 solarfire [fglrx] max single LFB = 126038016 Aug 27 12:32:33 solarfire [fglrx] total Inv = 0 Aug 27 12:32:33 solarfire [fglrx] free Inv = 0 Aug 27 12:32:33 solarfire [fglrx] max single Inv = 0 Aug 27 12:32:33 solarfire [fglrx] total TIM = 0 ---------------------------------------------------------------- To me it seems that the ati-driver doesn't properly initialize the display adapter, though -- of course -- a hardware problem can not be ruled out entirely ... It would be interesting to know, if others running 8.39.4 can also spot this "Uhhuh" message. Possibly it does only occur on X1400 and/or Thinkpad laptops ... Furthermore I've found a way to reproduce the crash with a certain reliability: Run "fgl _fglxgears" and switch between powerstates, i. e. > aticonfig --set-powerstate=1 > aticonfig --set-powerstate=3 > aticonfig --set-powerstate=1 > aticonfig --set-powerstate=3 > aticonfig --set-powerstate=1 > ... Axel
Please stabilize xorg-server-1.3.0.0 with ati-drivers on amd64. This is for bug #191615. Thanks
amd64 stable
