-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John P. Burkett wrote: > Lie Ryan wrote: >> 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) > > Thank you, Lie. Learning to upgrade the kernel is on my to-do list. When > you say recompile with the same .config, are you referring to > recompiling the kernel? Several .config files are on my system. My > first guess is that the relevant one is > /usr/src/linux-2.6.22-gentoo-r2/.config > Its first lines are the following: > # Automatically generated make config: don't edit > # Linux kernel version: 2.6.22-gentoo-r2 > # > # Tue Sep 4 10:25:14 2007 > CONFIG_X86_64=y > CONFIG_64BIT=y
Yes, as you have found out, there is a file named ".config" inside the kernel sources' directory; you usually edit this with "make menuconfig" or one of the GUI config tools. After configuration is done just do "make all", "make modules_install", and install it on the /boot partition (for full tutorial see the gentoo documentation) >>> -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 > Doing that produces the following response: > Linux version 2.6.22-gentoo-r2-osmp (r...@microway) (gcc version 4.1.2 > (Gentoo 4.1.2)) #2 SMP Mon Sep 3 21:52:26 EDT 2007 > > Doing "gcc -v" produces output whose final line is > gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) > > I take this to mean that the kernel is not built with the new gcc. > Should I now try to rebuild the kernel with the new gcc? Never having > rebuilt a kernel, I'd welcome advice about how to do it. Before rebuilding your kernel, make sure to have a spare Live CD and always a spare working kernel in /boot. For first time building, be conservative on changing the .config; the priority would be to identify which options are required to have a kernel that (at least) boots. For a successful boot, the most important options are the ones related to your harddisk and filesystem... Configuring the kernel is kind of guesswork at first, although a more intelligent guessess can be made by looking at lsmod, lspci, lshw, and /proc/cpuinfo on a working kernel. Tips: change the CONFIG_LOCAL_VERSION (General Setup -> Local Version - append to kernel release) for every recompilation. By having a unique version string for each recompiling, kernel modules from previous recompilation of the same kernel version wouldn't get mixed up with the new recompilation. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEUEARECAAYFAkov+CQACgkQqC3FTmXeMUYWIwCY93aLwAX1yxsxi/4Mo171hiMd jgCdHDorDkavLjt+BwxG/EmyAKXqwLU= =wiOF -----END PGP SIGNATURE-----
