1 |
On Sun, 21 Jun 2009 15:19:53 -0400 |
2 |
John P. Burkett wrote: |
3 |
|
4 |
> David Relson wrote: |
5 |
> > On Sun, 21 Jun 2009 14:54:36 -0400 |
6 |
> > John P. Burkett wrote: |
7 |
> > |
8 |
> >> David Relson wrote: |
9 |
> >>> On Sun, 21 Jun 2009 13:55:10 -0400 |
10 |
> >>> Drake Donahue wrote: |
11 |
> >>> |
12 |
> >>>> <snip> |
13 |
> >>>> |
14 |
> >>>> I'm guessing you did an "emerge --depclean" sometime after |
15 |
> >>>> compiling the 2.6.22-r2 kernel and after emerging a new |
16 |
> >>>> gentoo-sources that erased your make files, This is something |
17 |
> >>>> depclean loves to do while leaving 99% of the older kernel source |
18 |
> >>>> files intact. I think depclean leaves your .config file in place. |
19 |
> >>>> Been a few weeks since I burned myself last with this one. |
20 |
> >>>> If you were following directions back in 2007 you should have a |
21 |
> >>>> stored 2.6.22-r2 config in the /boot directory. |
22 |
> >>>> |
23 |
> >>>> Try "emerge =sys-kernel/gentoo-sources-2.6.22-r2 to re-emerge the |
24 |
> >>>> old package and regain the make files. What the osmp is about |
25 |
> >>>> beats me. |
26 |
> >>>> |
27 |
> >>>> or |
28 |
> >>>> |
29 |
> >>>> Emerge a new gentoo-sources, eselect it, configure, compile, |
30 |
> >>>> install a new (current) kernel. |
31 |
> >>> My understanding is that ati-drivers expects /usr/src/linux to |
32 |
> >>> contain the source of the currently running kernel. |
33 |
> >>> |
34 |
> >>> I'm running a 2.6.28 kernel. I have downloaded 2.6.30 and built |
35 |
> >>> that but have not yet rebooted. "emerge ati-drivers" failed with |
36 |
> >>> 2.6.30 in /usr/src/linux. Changing directory names allowed |
37 |
> >>> ati-drivers to build happily. |
38 |
> >>> |
39 |
> >> David, thank you for sharing your experience. On my system, doing |
40 |
> >> "uname -r" gets the response "2.6.22-gentoo-r2-osmp". In |
41 |
> >> my /usr/src/linux directory I currently have a .config file |
42 |
> >> starting with the lines # Automatically generated make config: |
43 |
> >> don't edit # Linux kernel version: 2.6.22-gentoo-r2 |
44 |
> >> # Mon Sep 3 21:48:37 2007 |
45 |
> >> Can you suggest how to change directory names to allow the |
46 |
> >> ati-drivers to build? |
47 |
> >> |
48 |
> >> Best regards, |
49 |
> >> John |
50 |
> > |
51 |
> > John, |
52 |
> > |
53 |
> > /usr/src/linux is what I'd want to see. Do you have just a few |
54 |
> > files (like .config) or the full kernel source? |
55 |
> Thanks for your continuing help with the ati-driver problem. Doing |
56 |
> "ls -al" in my /usr/src/linux directory produces the following list: |
57 |
> total 28451 |
58 |
> drwxr-xr-x 19 root root 1088 Jun 8 01:16 . |
59 |
> drwxr-xr-x 3 root root 136 Jun 8 01:19 .. |
60 |
> -rw-r--r-- 1 root root 440 Sep 4 2007 ..tmp_kallsyms1.o.cmd |
61 |
> -rw-r--r-- 1 root root 440 Sep 4 2007 ..tmp_kallsyms2.o.cmd |
62 |
> -rw-r--r-- 1 root root 636 Sep 4 2007 ..tmp_vmlinux1.cmd |
63 |
> -rw-r--r-- 1 root root 652 Sep 4 2007 ..tmp_vmlinux2.cmd |
64 |
> -rw-r--r-- 1 root root 47220 Jun 21 13:34 .config |
65 |
> -rw-r--r-- 1 root root 47220 Sep 3 2007 .config.old |
66 |
> -rw-r--r-- 1 root root 365 Sep 4 2007 .missing-syscalls.d |
67 |
> -rw-r--r-- 1 root root 1418737 Sep 4 2007 .tmp_System.map |
68 |
> -rw-r--r-- 1 root root 1578817 Sep 4 2007 .tmp_kallsyms1.S |
69 |
> -rw-r--r-- 1 root root 735072 Sep 4 2007 .tmp_kallsyms1.o |
70 |
> -rw-r--r-- 1 root root 1578817 Sep 4 2007 .tmp_kallsyms2.S |
71 |
> -rw-r--r-- 1 root root 735072 Sep 4 2007 .tmp_kallsyms2.o |
72 |
> drwxr-xr-x 2 root root 10176 Sep 4 2007 .tmp_versions |
73 |
> -rwxr-xr-x 1 root root 9069262 Sep 4 2007 .tmp_vmlinux1 |
74 |
> -rwxr-xr-x 1 root root 9388791 Sep 4 2007 .tmp_vmlinux2 |
75 |
> -rw-r--r-- 1 root root 2 Sep 4 2007 .version |
76 |
> -rw-r--r-- 1 root root 640 Sep 4 2007 .vmlinux.cmd |
77 |
> -rw-r--r-- 1 root root 252456 Sep 4 2007 Module.symvers |
78 |
> -rw-r--r-- 1 root root 1418737 Sep 4 2007 System.map |
79 |
> drwxr-xr-x 4 root root 96 Jun 8 01:16 arch |
80 |
> drwxr-xr-x 2 root root 752 Jun 8 01:16 block |
81 |
> drwxr-xr-x 2 root root 6640 Jun 8 01:16 crypto |
82 |
> drwxr-xr-x 35 root root 968 Jun 8 01:16 drivers |
83 |
> drwxr-xr-x 35 root root 4936 Jun 8 01:16 fs |
84 |
> drwxr-xr-x 5 root root 152 Jun 8 01:16 include |
85 |
> drwxr-xr-x 2 root root 736 Jun 8 01:16 init |
86 |
> drwxr-xr-x 2 root root 680 Jun 8 01:16 ipc |
87 |
> drwxr-xr-x 5 root root 3832 Jun 8 01:16 kernel |
88 |
> drwxr-xr-x 4 root root 4512 Jun 8 01:16 lib |
89 |
> drwxr-xr-x 2 root root 2616 Jun 8 01:16 mm |
90 |
> drwxr-xr-x 23 root root 856 Jun 8 01:16 net |
91 |
> drwxr-xr-x 6 root root 320 Jun 8 01:16 scripts |
92 |
> drwxr-xr-x 2 root root 208 Jun 8 01:16 security |
93 |
> drwxr-xr-x 16 root root 904 Jun 8 01:16 sound |
94 |
> drwxr-xr-x 2 root root 424 Jun 8 01:16 usr |
95 |
> -rwxr-xr-x 1 root root 9388791 Sep 4 2007 vmlinux |
96 |
> |
97 |
> Does that appear to have what ati-drivers should need? |
98 |
> |
99 |
> Best regards, |
100 |
> John |
101 |
|
102 |
John, |
103 |
|
104 |
That looks like what I've got. If you're up to some debugging, here's |
105 |
some more info: |
106 |
|
107 |
When I deliberating have the wrong kernel source in /usr/src/linux, my |
108 |
build fails the last few lines printed are: |
109 |
|
110 |
If you need support, post the topmost build error, and the call stack |
111 |
if relevant. |
112 |
* A complete build log is located at |
113 |
'/var/log/portage/x11-drivers:ati-drivers-8.552-r2:20090621-200106.log'. |
114 |
* The ebuild environment file is located at |
115 |
'/var/tmp/portage/x11-drivers/ati-drivers-8.552-r2/temp/environment'. |
116 |
|
117 |
|
118 |
Looking at file .../temp/environment I see it's a bash script and |
119 |
contains line 2536 is |
120 |
|
121 |
get_version || die "Unable to calculate Linux Kernel version"; |
122 |
|
123 |
which is the message in your original post. Evidently function |
124 |
get_version() is failing and causing the "die" command to be executed. |
125 |
I have function get_version() at line 2326 of .../environment. Take a |
126 |
look at that and see if you can figure out where it might be dying. |
127 |
Running the script in debug mode, i.e. using "sh -x environment", will |
128 |
give you detailed information about the script is finding and doing. |
129 |
|
130 |
|
131 |
HTH, |
132 |
|
133 |
David |