-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John P. Burkett wrote: >> 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:
The latest gentoo kernel is 2.6.29-gentoo-r5, AFTER this problem is solved, probably you can consider upgrading the kernel as well (we don't want kernel upgrade problems get compounded with gcc problem, do we?). For now, perhaps you can recompile with the same (working -- I assumed) .config (we also don't want configuration mistakes compounding compile problem for now) > -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. I guess, maybe portage re-emerge'd the source at Jun 8 >> 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? You can do: $ cat /proc/version however I doubt that since your `ls -l` showed that vmlinux and System.map's date is Sep 4 2007. vmlinux is the uncompressed kernel executable that is made when compiling the kernel (the compressed kernel and the one generally used is in arch/x86_64/boot/bzImage) > 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 > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkovNkQACgkQqC3FTmXeMUYGUACcCRGbV4uuFlyjLlguyfZFJGwV xrsAnj9+LaEgmemGUfPHjU9won3cw2P1 =MFxo -----END PGP SIGNATURE-----
