1 |
David Relson wrote: |
2 |
> On Sun, 21 Jun 2009 14:54:36 -0400 |
3 |
> John P. Burkett wrote: |
4 |
> |
5 |
>> David Relson wrote: |
6 |
>>> On Sun, 21 Jun 2009 13:55:10 -0400 |
7 |
>>> Drake Donahue wrote: |
8 |
>>> |
9 |
>>>> <snip> |
10 |
>>>> |
11 |
>>>> I'm guessing you did an "emerge --depclean" sometime after |
12 |
>>>> compiling the 2.6.22-r2 kernel and after emerging a new |
13 |
>>>> gentoo-sources that erased your make files, This is something |
14 |
>>>> depclean loves to do while leaving 99% of the older kernel source |
15 |
>>>> files intact. I think depclean leaves your .config file in place. |
16 |
>>>> Been a few weeks since I burned myself last with this one. |
17 |
>>>> If you were following directions back in 2007 you should have a |
18 |
>>>> stored 2.6.22-r2 config in the /boot directory. |
19 |
>>>> |
20 |
>>>> Try "emerge =sys-kernel/gentoo-sources-2.6.22-r2 to re-emerge the |
21 |
>>>> old package and regain the make files. What the osmp is about |
22 |
>>>> beats me. |
23 |
>>>> |
24 |
>>>> or |
25 |
>>>> |
26 |
>>>> Emerge a new gentoo-sources, eselect it, configure, compile, |
27 |
>>>> install a new (current) kernel. |
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 |
>> David, thank you for sharing your experience. On my system, doing |
37 |
>> "uname -r" gets the response "2.6.22-gentoo-r2-osmp". In |
38 |
>> my /usr/src/linux directory I currently have a .config file starting |
39 |
>> with the lines # Automatically generated make config: don't edit |
40 |
>> # Linux kernel version: 2.6.22-gentoo-r2 |
41 |
>> # Mon Sep 3 21:48:37 2007 |
42 |
>> Can you suggest how to change directory names to allow the ati-drivers |
43 |
>> to build? |
44 |
>> |
45 |
>> Best regards, |
46 |
>> John |
47 |
> |
48 |
> John, |
49 |
> |
50 |
> /usr/src/linux is what I'd want to see. Do you have just a few files |
51 |
> (like .config) or the full kernel source? |
52 |
Thanks for your continuing help with the ati-driver problem. Doing "ls |
53 |
-al" in my /usr/src/linux directory produces the following list: |
54 |
total 28451 |
55 |
drwxr-xr-x 19 root root 1088 Jun 8 01:16 . |
56 |
drwxr-xr-x 3 root root 136 Jun 8 01:19 .. |
57 |
-rw-r--r-- 1 root root 440 Sep 4 2007 ..tmp_kallsyms1.o.cmd |
58 |
-rw-r--r-- 1 root root 440 Sep 4 2007 ..tmp_kallsyms2.o.cmd |
59 |
-rw-r--r-- 1 root root 636 Sep 4 2007 ..tmp_vmlinux1.cmd |
60 |
-rw-r--r-- 1 root root 652 Sep 4 2007 ..tmp_vmlinux2.cmd |
61 |
-rw-r--r-- 1 root root 47220 Jun 21 13:34 .config |
62 |
-rw-r--r-- 1 root root 47220 Sep 3 2007 .config.old |
63 |
-rw-r--r-- 1 root root 365 Sep 4 2007 .missing-syscalls.d |
64 |
-rw-r--r-- 1 root root 1418737 Sep 4 2007 .tmp_System.map |
65 |
-rw-r--r-- 1 root root 1578817 Sep 4 2007 .tmp_kallsyms1.S |
66 |
-rw-r--r-- 1 root root 735072 Sep 4 2007 .tmp_kallsyms1.o |
67 |
-rw-r--r-- 1 root root 1578817 Sep 4 2007 .tmp_kallsyms2.S |
68 |
-rw-r--r-- 1 root root 735072 Sep 4 2007 .tmp_kallsyms2.o |
69 |
drwxr-xr-x 2 root root 10176 Sep 4 2007 .tmp_versions |
70 |
-rwxr-xr-x 1 root root 9069262 Sep 4 2007 .tmp_vmlinux1 |
71 |
-rwxr-xr-x 1 root root 9388791 Sep 4 2007 .tmp_vmlinux2 |
72 |
-rw-r--r-- 1 root root 2 Sep 4 2007 .version |
73 |
-rw-r--r-- 1 root root 640 Sep 4 2007 .vmlinux.cmd |
74 |
-rw-r--r-- 1 root root 252456 Sep 4 2007 Module.symvers |
75 |
-rw-r--r-- 1 root root 1418737 Sep 4 2007 System.map |
76 |
drwxr-xr-x 4 root root 96 Jun 8 01:16 arch |
77 |
drwxr-xr-x 2 root root 752 Jun 8 01:16 block |
78 |
drwxr-xr-x 2 root root 6640 Jun 8 01:16 crypto |
79 |
drwxr-xr-x 35 root root 968 Jun 8 01:16 drivers |
80 |
drwxr-xr-x 35 root root 4936 Jun 8 01:16 fs |
81 |
drwxr-xr-x 5 root root 152 Jun 8 01:16 include |
82 |
drwxr-xr-x 2 root root 736 Jun 8 01:16 init |
83 |
drwxr-xr-x 2 root root 680 Jun 8 01:16 ipc |
84 |
drwxr-xr-x 5 root root 3832 Jun 8 01:16 kernel |
85 |
drwxr-xr-x 4 root root 4512 Jun 8 01:16 lib |
86 |
drwxr-xr-x 2 root root 2616 Jun 8 01:16 mm |
87 |
drwxr-xr-x 23 root root 856 Jun 8 01:16 net |
88 |
drwxr-xr-x 6 root root 320 Jun 8 01:16 scripts |
89 |
drwxr-xr-x 2 root root 208 Jun 8 01:16 security |
90 |
drwxr-xr-x 16 root root 904 Jun 8 01:16 sound |
91 |
drwxr-xr-x 2 root root 424 Jun 8 01:16 usr |
92 |
-rwxr-xr-x 1 root root 9388791 Sep 4 2007 vmlinux |
93 |
|
94 |
Does that appear to have what ati-drivers should need? |
95 |
|
96 |
Best regards, |
97 |
John |
98 |
|
99 |
|
100 |
It's my understanding that |
101 |
> ati-drivers need the full kernel source. Likely they use (or check) |
102 |
> some of the kernel's internal header files to "match up" the driver |
103 |
> with the kernel it's running against. |
104 |
> |
105 |
> If you've got the full kernel source, then all I can suggest is |
106 |
> getting source for the newest kernel, building it (using your |
107 |
> old .config as the starting point), rebooting, and (finally) emerging |
108 |
> ati-drivers. The steps up to and including rebooting should provide a |
109 |
> consistent kernel version and source tree and make ati-drivers happy. |
110 |
> |
111 |
> HTH, |
112 |
> |
113 |
> David |
114 |
> |
115 |
> |
116 |
|
117 |
|
118 |
-- |
119 |
John P. Burkett |
120 |
Department of Economics |
121 |
University of Rhode Island |
122 |
Kingston, RI 02881-0808 |
123 |
USA |
124 |
|
125 |
phone (401) 874-9195 |