Duncan wrote: > "John P. Burkett" <burk...@uri.edu> posted 4a2ee4c1.8000...@uri.edu, > excerpted below, on Tue, 09 Jun 2009 18:40:01 -0400: > >> Doing "revdep-rebuild -p" elicited this response: Calculating >> dependencies... done! >> [ebuild R ] sci-libs/blas-atlas-3.8.0 >> [ebuild R ] app-emulation/emul-linux-x86-soundlibs-20080418 >> [ebuild R ] mail-client/evolution-2.24.5 >> [ebuild R ] x11-drivers/ati-drivers-8.552-r2 >> [ebuild R ] sci-libs/lapack-atlas-3.8.0 >> [ebuild R ] dev-lang/R-2.8.1 >> [ebuild R ] sci-mathematics/octave-3.0.3 >> >> That looked o.k., so I did "revdep-rebuild" The first 3 packages seem to >> have been handled fairly successfully. Problems arose with the >> ati-drivers. The final messages from revdep-rebuild read as follows: >>>>> Emerging (4 of 7) x11-drivers/ati-drivers-8.552-r2 >> * ati-driver-installer-8-11-x86.x86_64.run RMD160 SHA1 SHA256 size ;-) >> ... [ ok ] >> * checking ebuild checksums ;-) ... [ >> ok ] >> * checking auxfile checksums ;-) ... [ >> ok ] >> * checking miscfile checksums ;-) ... [ >> ok ] >> * Determining the location of the kernel source code >> * Found kernel source directory: >> * /usr/src/linux >> * Could not find a Makefile in the kernel source directory. >> * Please ensure that /usr/src/linux points to a complete set of Linux >> sources >> * >> * ERROR: x11-drivers/ati-drivers-8.552-r2 failed. > > As Josh says, it probably didn't get beyond this one. > > Drivers like this are a special case for a couple reasons. One is that > parts of them are closed source and simply may not build or work > correctly with the latest stuff. You're at the mercy of the ATI folks > for that, but particularly with the latest xorg, they may have issues, > and stabling xorg gets routinely delayed because neither ATI nor nVidia > have caught up yet. FWIW I won't run closed source, nor could I even if > I wanted, since I cannot and will not agree to the license they try to > enforce. Yes, that does limit my hardware choices a bit, but not as much > now that AMD/ATI is cooperating a bit better with the open source world. > But to each his own. Thank you, Duncan. I share your preference for open source programs. I'm not sure how the ati-drivers got on my machine or what they were doing. If my system functions without them, I'm happy to be rid of them.
> > However, that doesn't seem to be the issue here, which brings us to > reason #2. The ati-drivers include a kernel driver, which must be > compiled against a kernel that has been built so the proper parts of it > are exposed for the drivers to use. The kernel must reside at /usr/src/ > linux. If you look at the error above, it found the directory all right, > but it didn't find what it needed in it. Have you built your kernel > using those sources, with your new gcc, yet? Did you leave the working > files exposed for ati-drivers to use if so, or did you cleanup using make > clean, or something? Going to /usr/src and doing "ls -l" elicits the following: lrwxrwxrwx 1 root root 22 Sep 3 2007 linux -> linux-2.6.22-gentoo-r2 drwxr-xr-x 19 root root 1088 Jun 8 01:16 linux-2.6.22-gentoo-r2 So linux appears to be symbolic link to linux-2.6.22-gentoo-r2 Going to /usr/src/linux-2.6.22-gentoo-r2 and doing "ls -l" produces the following: -rw-r--r-- 1 root root 252456 Sep 4 2007 Module.symvers -rw-r--r-- 1 root root 1418737 Sep 4 2007 System.map drwxr-xr-x 4 root root 96 Jun 8 01:16 arch drwxr-xr-x 2 root root 752 Jun 8 01:16 block drwxr-xr-x 2 root root 6640 Jun 8 01:16 crypto drwxr-xr-x 35 root root 968 Jun 8 01:16 drivers drwxr-xr-x 35 root root 4936 Jun 8 01:16 fs drwxr-xr-x 5 root root 152 Jun 8 01:16 include drwxr-xr-x 2 root root 736 Jun 8 01:16 init drwxr-xr-x 2 root root 680 Jun 8 01:16 ipc drwxr-xr-x 5 root root 3832 Jun 8 01:16 kernel drwxr-xr-x 4 root root 4512 Jun 8 01:16 lib drwxr-xr-x 2 root root 2616 Jun 8 01:16 mm drwxr-xr-x 23 root root 856 Jun 8 01:16 net drwxr-xr-x 6 root root 320 Jun 8 01:16 scripts drwxr-xr-x 2 root root 208 Jun 8 01:16 security drwxr-xr-x 16 root root 904 Jun 8 01:16 sound drwxr-xr-x 2 root root 424 Jun 8 01:16 usr -rwxr-xr-x 1 root root 9388791 Sep 4 2007 vmlinux The June 8 date is a surprise to me because I did not intentionally do anything to this directory then. > > My guess is that you need to build your kernel with the new gcc, and then > ati-drivers will hopefully compile. Is there anyway to tell whether the kernel is built with the new gcc? At this point should I make another attempt at doing "emerge --emptytree world"? Yesterday when I tried that, the response started with 914 packages are being emerged! gcc-config: error: could not run/locate 'x86_64-pc-linux-gnu-gcc' make: *** [adler32.o] Error 1 With gcc now fixed, that error could presumably be avoided. Doing "emerge --pretend --emptytree" produces a list of about 915 packages, starting with [ebuild R ] sys-apps/portage-2.1.6.13 and ending with [ebuild R ] app-portage/genlop-0.30.8-r2 Thanks again for your continued help! -John -- John P. Burkett Department of Economics University of Rhode Island Kingston, RI 02881-0808 USA phone (401) 874-9195
