1 |
On Sun, 21 Jun 2009 14:54:36 -0400 |
2 |
John P. Burkett wrote: |
3 |
|
4 |
> David Relson wrote: |
5 |
> > On Sun, 21 Jun 2009 13:55:10 -0400 |
6 |
> > Drake Donahue wrote: |
7 |
> > |
8 |
> >> <snip> |
9 |
> >> |
10 |
> >> I'm guessing you did an "emerge --depclean" sometime after |
11 |
> >> compiling the 2.6.22-r2 kernel and after emerging a new |
12 |
> >> gentoo-sources that erased your make files, This is something |
13 |
> >> depclean loves to do while leaving 99% of the older kernel source |
14 |
> >> files intact. I think depclean leaves your .config file in place. |
15 |
> >> Been a few weeks since I burned myself last with this one. |
16 |
> >> If you were following directions back in 2007 you should have a |
17 |
> >> stored 2.6.22-r2 config in the /boot directory. |
18 |
> >> |
19 |
> >> Try "emerge =sys-kernel/gentoo-sources-2.6.22-r2 to re-emerge the |
20 |
> >> old package and regain the make files. What the osmp is about |
21 |
> >> beats me. |
22 |
> >> |
23 |
> >> or |
24 |
> >> |
25 |
> >> Emerge a new gentoo-sources, eselect it, configure, compile, |
26 |
> >> install a new (current) kernel. |
27 |
> > |
28 |
> > My understanding is that ati-drivers expects /usr/src/linux to |
29 |
> > contain the source of the currently running kernel. |
30 |
> > |
31 |
> > I'm running a 2.6.28 kernel. I have downloaded 2.6.30 and built |
32 |
> > that but have not yet rebooted. "emerge ati-drivers" failed with |
33 |
> > 2.6.30 in /usr/src/linux. Changing directory names allowed |
34 |
> > ati-drivers to build happily. |
35 |
> > |
36 |
> |
37 |
> David, thank you for sharing your experience. On my system, doing |
38 |
> "uname -r" gets the response "2.6.22-gentoo-r2-osmp". In |
39 |
> my /usr/src/linux directory I currently have a .config file starting |
40 |
> with the lines # Automatically generated make config: don't edit |
41 |
> # Linux kernel version: 2.6.22-gentoo-r2 |
42 |
> # Mon Sep 3 21:48:37 2007 |
43 |
> Can you suggest how to change directory names to allow the ati-drivers |
44 |
> to build? |
45 |
> |
46 |
> Best regards, |
47 |
> John |
48 |
|
49 |
John, |
50 |
|
51 |
/usr/src/linux is what I'd want to see. Do you have just a few files |
52 |
(like .config) or the full kernel source? It's my understanding that |
53 |
ati-drivers need the full kernel source. Likely they use (or check) |
54 |
some of the kernel's internal header files to "match up" the driver |
55 |
with the kernel it's running against. |
56 |
|
57 |
If you've got the full kernel source, then all I can suggest is |
58 |
getting source for the newest kernel, building it (using your |
59 |
old .config as the starting point), rebooting, and (finally) emerging |
60 |
ati-drivers. The steps up to and including rebooting should provide a |
61 |
consistent kernel version and source tree and make ati-drivers happy. |
62 |
|
63 |
HTH, |
64 |
|
65 |
David |