1 |
No, you can't. |
2 |
|
3 |
Not this way, try something like sending a e-mail to: |
4 |
|
5 |
gentoo-amd64+unsubscribe@l.g.o |
6 |
|
7 |
|
8 |
Good Luck |
9 |
|
10 |
On 22-03-2012 13:42, redspot wrote: |
11 |
> unsubscribe |
12 |
> |
13 |
> On Wed, Mar 21, 2012 at 5:03 AM,<gentoo-amd64+help@l.g.o> wrote: |
14 |
> |
15 |
>> Topics (messages 13110 through 13125): |
16 |
>> |
17 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
18 |
>> 13110 - Frank Peters<frank.peters@×××××××.net> |
19 |
>> |
20 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
21 |
>> 13111 - Mark Knecht<markknecht@×××××.com> |
22 |
>> |
23 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
24 |
>> 13112 - Frank Peters<frank.peters@×××××××.net> |
25 |
>> |
26 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
27 |
>> 13113 - Cheng Renquan<crquan@×××××.com> |
28 |
>> |
29 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
30 |
>> 13114 - Mark Knecht<markknecht@×××××.com> |
31 |
>> |
32 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
33 |
>> 13115 - Mark Knecht<markknecht@×××××.com> |
34 |
>> |
35 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
36 |
>> 13116 - Frank Peters<frank.peters@×××××××.net> |
37 |
>> |
38 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
39 |
>> 13117 - Mark Knecht<markknecht@×××××.com> |
40 |
>> |
41 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
42 |
>> 13118 - Paul Hartman<paul.hartman+gentoo@×××××.com> |
43 |
>> |
44 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
45 |
>> 13119 - Barry Schwartz<chemoelectric@×××××××××××××.org> |
46 |
>> |
47 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
48 |
>> 13120 - Mark Knecht<markknecht@×××××.com> |
49 |
>> |
50 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
51 |
>> 13121 - Barry Schwartz<chemoelectric@×××××××××××××.org> |
52 |
>> |
53 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
54 |
>> 13122 - Frank Peters<frank.peters@×××××××.net> |
55 |
>> |
56 |
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers |
57 |
>> 13123 - Barry Schwartz<chemoelectric@×××××××××××××.org> |
58 |
>> |
59 |
>> [gentoo-amd64] Re: Kernel-3.3.0 and Nvidia-drivers |
60 |
>> 13124 - Duncan<1i5t5.duncan@×××.net> |
61 |
>> 13125 - Duncan<1i5t5.duncan@×××.net> |
62 |
>> |
63 |
>> |
64 |
>> |
65 |
>> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled |
66 |
>> the plain vanilla source. |
67 |
>> |
68 |
>> After rebooting to the command console, and before starting X, I needed |
69 |
>> to re-install the nvidia-driver module for the new kernel. Doing |
70 |
>> "emerge nvidia-drivers" gave me the following error (the entire build log |
71 |
>> is attached): |
72 |
>> |
73 |
>> |
74 |
>>>>> Source prepared. |
75 |
>>>>> Configuring source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ... |
76 |
>>>>> Source configured. |
77 |
>>>>> Compiling source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ... |
78 |
>>>>> |
79 |
>> Preparing nvidia module |
80 |
>> make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module |
81 |
>> |
82 |
>> *** Unable to determine the target kernel version. *** |
83 |
>> |
84 |
>> make: *** [select_makefile] Error 1 |
85 |
>> emake failed |
86 |
>> ERROR: x11-drivers/nvidia-drivers-295.20-r1 failed (compile phase): |
87 |
>> Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=-m elf_x86_64 IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module |
88 |
>> |
89 |
>> Call stack: |
90 |
>> ebuild.sh, line 85: Called src_compile |
91 |
>> environment, line 3711: Called linux-mod_src_compile |
92 |
>> environment, line 2668: Called die |
93 |
>> The specific snippet of code: |
94 |
>> eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" |
95 |
>> |
96 |
>> |
97 |
>> The first part of the build log (see attached file) indicates that the |
98 |
>> kernel source was correctly found (at /usr/src/linux), but for some |
99 |
>> reason the make process fails. |
100 |
>> |
101 |
>> Could this be due to some changes in the kernel-3.3.0 tree? |
102 |
>> |
103 |
>> Frank Peters |
104 |
>> |
105 |
>> |
106 |
>> On Mon, Mar 19, 2012 at 9:12 AM, Frank Peters<frank.peters@×××××××.net> wrote: |
107 |
>> |
108 |
>>> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled |
109 |
>>> the plain vanilla source. |
110 |
>>> |
111 |
>>> |
112 |
>> <SNIP> |
113 |
>> |
114 |
>>> The first part of the build log (see attached file) indicates that the |
115 |
>>> kernel source was correctly found (at /usr/src/linux), but for some |
116 |
>>> reason the make process fails. |
117 |
>>> |
118 |
>>> Could this be due to some changes in the kernel-3.3.0 tree? |
119 |
>>> |
120 |
>>> Frank Peters |
121 |
>>> |
122 |
>>> |
123 |
>> Possibly this from Google will help? |
124 |
>> |
125 |
>> Good luck& post back, |
126 |
>> Mark |
127 |
>> |
128 |
>> On Mon, 19 Mar 2012 09:35:34 -0700 |
129 |
>> Mark Knecht<markknecht@×××××.com> wrote: |
130 |
>> |
131 |
>> |
132 |
>>> Possibly this from Google will help? |
133 |
>>> |
134 |
>>> |
135 |
>> Did you intend to include a link? If so, it must have gotten |
136 |
>> lost somewhere. |
137 |
>> |
138 |
>> Frank Peters |
139 |
>> |
140 |
>> |
141 |
>> I have switched to nouveau driver, for over 1 year, |
142 |
>> using with gnome3 interface, no performance issue, and quite stable, |
143 |
>> |
144 |
>> enjoying every mainline kernel 3.0, 3.1, 3.2, 3.3, no building issue |
145 |
>> |
146 |
>> |
147 |
>> I think it's time for everyone to give up nvidia-drivers, the blob of binary |
148 |
>> |
149 |
>> On Mon, Mar 19, 2012 at 9:12 AM, Frank Peters<frank.peters@×××××××.net> wrote: |
150 |
>> |
151 |
>>> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled |
152 |
>>> the plain vanilla source. |
153 |
>>> |
154 |
>>> After rebooting to the command console, and before starting X, I needed |
155 |
>>> to re-install the nvidia-driver module for the new kernel. Doing |
156 |
>>> "emerge nvidia-drivers" gave me the following error (the entire build log |
157 |
>>> is attached): |
158 |
>>> |
159 |
>>> |
160 |
>>>>>> Source prepared. |
161 |
>>>>>> Configuring source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ... |
162 |
>>>>>> Source configured. |
163 |
>>>>>> Compiling source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ... |
164 |
>>>>>> |
165 |
>>> Preparing nvidia module |
166 |
>>> make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module |
167 |
>>> |
168 |
>>> *** Unable to determine the target kernel version. *** |
169 |
>>> |
170 |
>> On Mon, Mar 19, 2012 at 12:05 PM, Frank Peters<frank.peters@×××××××.net> wrote: |
171 |
>> |
172 |
>>> On Mon, 19 Mar 2012 09:35:34 -0700 |
173 |
>>> Mark Knecht<markknecht@×××××.com> wrote: |
174 |
>>> |
175 |
>>> |
176 |
>>>> Possibly this from Google will help? |
177 |
>>>> |
178 |
>>>> |
179 |
>>> Did you intend to include a link? If so, it must have gotten |
180 |
>>> lost somewhere. |
181 |
>>> |
182 |
>>> Frank Peters |
183 |
>>> |
184 |
>>> |
185 |
>>> |
186 |
>> Gadzooks, yes I did. Sorry! |
187 |
>> |
188 |
>> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/ |
189 |
>> |
190 |
>> To be clear, I have no idea if it will solve your exact problem. It |
191 |
>> didn't for all. |
192 |
>> |
193 |
>> My experience with nvidia is pretty good if you give them a couple of |
194 |
>> days, but very spotty on the first or second day a new kernel minor |
195 |
>> rev is released. Nominally I use this page: |
196 |
>> |
197 |
>> http://www.nvidia.com/Download/indexsg.aspx?lang=en-us |
198 |
>> |
199 |
>> and then search out my specific card to determine what _exact_ driver |
200 |
>> they want me to run. It almost always requires i run ~amd64. |
201 |
>> |
202 |
>> HTH, |
203 |
>> Mark |
204 |
>> |
205 |
>> On Mon, Mar 19, 2012 at 12:14 PM, Cheng Renquan<crquan@×××××.com> wrote: |
206 |
>> |
207 |
>>> I have switched to nouveau driver, for over 1 year, |
208 |
>>> using with gnome3 interface, no performance issue, and quite stable, |
209 |
>>> |
210 |
>>> enjoying every mainline kernel 3.0, 3.1, 3.2, 3.3, no building issue |
211 |
>>> |
212 |
>>> |
213 |
>>> I think it's time for everyone to give up nvidia-drivers, the blob of binary |
214 |
>>> |
215 |
>>> |
216 |
>> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau |
217 |
>> support all the CUDA stuff? |
218 |
>> |
219 |
>> Cheers, |
220 |
>> Mark |
221 |
>> |
222 |
>> On Mon, 19 Mar 2012 09:35:34 -0700 |
223 |
>> Mark Knecht<markknecht@×××××.com> wrote: |
224 |
>> |
225 |
>> |
226 |
>>> Possibly this from Google will help? |
227 |
>>> |
228 |
>>> |
229 |
>> OK, I think I've found the URL that you may have intended: |
230 |
>> |
231 |
>> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/ |
232 |
>> |
233 |
>> I followed the second fix that is described and now the nvidia-drivers |
234 |
>> emerge and work nicely with linux kernel-3.3. |
235 |
>> |
236 |
>> Thanks for the hint. |
237 |
>> |
238 |
>> There are changes to the kernel-3.3 tree that will have to addressed |
239 |
>> by the gentoo nvidia-drivers or other users will hit this problem |
240 |
>> as well. |
241 |
>> |
242 |
>> Frank Peters |
243 |
>> |
244 |
>> |
245 |
>> On Mon, Mar 19, 2012 at 12:30 PM, Frank Peters<frank.peters@×××××××.net> wrote: |
246 |
>> |
247 |
>>> On Mon, 19 Mar 2012 09:35:34 -0700 |
248 |
>>> Mark Knecht<markknecht@×××××.com> wrote: |
249 |
>>> |
250 |
>>> |
251 |
>>>> Possibly this from Google will help? |
252 |
>>>> |
253 |
>>>> |
254 |
>>> OK, I think I've found the URL that you may have intended: |
255 |
>>> |
256 |
>>> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/ |
257 |
>>> |
258 |
>>> I followed the second fix that is described and now the nvidia-drivers |
259 |
>>> emerge and work nicely with linux kernel-3.3. |
260 |
>>> |
261 |
>>> Thanks for the hint. |
262 |
>>> |
263 |
>>> There are changes to the kernel-3.3 tree that will have to addressed |
264 |
>>> by the gentoo nvidia-drivers or other users will hit this problem |
265 |
>>> as well. |
266 |
>>> |
267 |
>>> Frank Peters |
268 |
>>> |
269 |
>>> |
270 |
>>> |
271 |
>> Glad you found it. That is the link I just sent along and good to know |
272 |
>> it helped a bit. |
273 |
>> |
274 |
>> As I said, on kernel revision number changes I ALWAYS wait a minimum |
275 |
>> of 3-5 days before trying to upgrade. nvidia always seems to need at |
276 |
>> least a few days to catch up with a new release, or that's been my |
277 |
>> experience in the past anyway. |
278 |
>> |
279 |
>> Cheers, |
280 |
>> Mark |
281 |
>> |
282 |
>> On Mon, Mar 19, 2012 at 3:08 PM, Mark Knecht<markknecht@×××××.com> wrote: |
283 |
>> |
284 |
>>> As I said, on kernel revision number changes I ALWAYS wait a minimum |
285 |
>>> of 3-5 days before trying to upgrade. nvidia always seems to need at |
286 |
>>> least a few days to catch up with a new release, or that's been my |
287 |
>>> experience in the past anyway. |
288 |
>>> |
289 |
>> Same here, nvidia-drivers and vmware-modules are why I usually wait |
290 |
>> until the .1 release on a new kernel series. :) |
291 |
>> |
292 |
>> Mark Knecht<markknecht@×××××.com> skribis: |
293 |
>> |
294 |
>>> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau |
295 |
>>> support all the CUDA stuff? |
296 |
>>> |
297 |
>> I think they may have reverse engineered CUDA, but whether it is |
298 |
>> implemented I dont know, and I wouldnt want to be the one to test |
299 |
>> it, either. :) |
300 |
>> |
301 |
>> Im donating processor time with boinc and thats good enough reason |
302 |
>> to use the binary driver if it gives me more processor to donate. |
303 |
>> |
304 |
>> (Waiting before installing anything new is painful, I know, because |
305 |
>> with Gentoo you always feel like you want it to be doing something, or |
306 |
>> at least thats my experience. :) ) |
307 |
>> |
308 |
>> On Mon, Mar 19, 2012 at 2:28 PM, Barry Schwartz |
309 |
>> <chemoelectric@×××××××××××××.org> wrote: |
310 |
>> |
311 |
>>> Mark Knecht<markknecht@×××××.com> skribis: |
312 |
>>> |
313 |
>>>> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau |
314 |
>>>> support all the CUDA stuff? |
315 |
>>>> |
316 |
>>> I think they may have reverse engineered CUDA, but whether it is |
317 |
>>> implemented I dont know, and I wouldnt want to be the one to test |
318 |
>>> it, either. :) |
319 |
>>> |
320 |
>>> Im donating processor time with boinc and thats good enough reason |
321 |
>>> to use the binary driver if it gives me more processor to donate. |
322 |
>>> |
323 |
>>> (Waiting before installing anything new is painful, I know, because |
324 |
>>> with Gentoo you always feel like you want it to be doing something, or |
325 |
>>> at least thats my experience. :) ) |
326 |
>>> |
327 |
>>> |
328 |
>> I have no problem with you or anyone else running nouveau. None at all. |
329 |
>> |
330 |
>> I do have a problem with someone saying 'it's time for everyone to |
331 |
>> give up nvidia-drivers' without demonstrating they know the full |
332 |
>> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe |
333 |
>> people who don't need anything other than basic X capabilities should |
334 |
>> consider running nouveau' I wouldn't have even chimed in. |
335 |
>> |
336 |
>> And thanks for running boinc. It's good of you and good for you. |
337 |
>> |
338 |
>> Cheers, |
339 |
>> Mark |
340 |
>> |
341 |
>> Mark Knecht<markknecht@×××××.com> skribis: |
342 |
>> |
343 |
>>> I do have a problem with someone saying 'it's time for everyone to |
344 |
>>> give up nvidia-drivers' without demonstrating they know the full |
345 |
>>> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe |
346 |
>>> people who don't need anything other than basic X capabilities should |
347 |
>>> consider running nouveau' I wouldn't have even chimed in. |
348 |
>>> |
349 |
>> Sage Notebook (sage-on-gentoo overlay) can use CUDA as well. I think |
350 |
>> you don't have to worry that nvidia-drivers would go away; in the |
351 |
>> worst case it would end up in a good overlay. That's unlikely IMO, and |
352 |
>> would mostly likely be if there were an established alternative |
353 |
>> implementation of CUDA. |
354 |
>> |
355 |
>> On Mon, 19 Mar 2012 14:40:34 -0700 |
356 |
>> Mark Knecht<markknecht@×××××.com> wrote: |
357 |
>> |
358 |
>> |
359 |
>>> I have no problem with you or anyone else running nouveau. None at all. |
360 |
>>> |
361 |
>>> I do have a problem with someone saying 'it's time for everyone to |
362 |
>>> give up nvidia-drivers' without demonstrating they know the full |
363 |
>>> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe |
364 |
>>> people who don't need anything other than basic X capabilities should |
365 |
>>> consider running nouveau' I wouldn't have even chimed in. |
366 |
>>> |
367 |
>>> |
368 |
>> I think the main complaint is that the Nvidia drivers are closed |
369 |
>> binary blobs while Nouveau is an attempt to create an entirely |
370 |
>> open source driver. The spirit of free software demands that we |
371 |
>> support these open initiatives. |
372 |
>> |
373 |
>> Actually, until recently, I was very happy using the legacy open |
374 |
>> source xorg nvidia driver known simply as as "nv." It is still |
375 |
>> available in Gentoo as x11-drivers/xf86-video-nv. |
376 |
>> |
377 |
>> Since I do not do gaming or other intensive graphic activities, |
378 |
>> I could get by nicely with just nv. However, the nv driver does |
379 |
>> not seem to support the latest hardware too well. On one of |
380 |
>> my machines I have a card based on Nvidia GeForce 210. Although |
381 |
>> the nv driver works with this card, it does not enable the Xv |
382 |
>> extension and consequently the graphic response is poor. |
383 |
>> |
384 |
>> On older cards nv does work quite well for ordinary purposes. |
385 |
>> |
386 |
>> Frank Peters |
387 |
>> |
388 |
>> |
389 |
>> Frank Peters<frank.peters@×××××××.net> skribis: |
390 |
>> |
391 |
>>> I think the main complaint is that the Nvidia drivers are closed |
392 |
>>> binary blobs while Nouveau is an attempt to create an entirely |
393 |
>>> open source driver. |
394 |
>>> |
395 |
>> Unfortunately the nvidia drivers are needed not only for graphics but |
396 |
>> also to use the GPU for scientific calculations, including for |
397 |
>> donating processor time to medical research, for instance. |
398 |
>> |
399 |
>> |
400 |
>> Frank Peters posted on Tue, 20 Mar 2012 00:03:06 -0400 as excerpted: |
401 |
>> |
402 |
>> |
403 |
>>> Actually, until recently, I was very happy using the legacy open source |
404 |
>>> xorg nvidia driver known simply as as "nv." It is still available in |
405 |
>>> Gentoo as x11-drivers/xf86-video-nv. |
406 |
>>> |
407 |
>>> Since I do not do gaming or other intensive graphic activities, I could |
408 |
>>> get by nicely with just nv. However, the nv driver does not seem to |
409 |
>>> support the latest hardware too well. |
410 |
>>> |
411 |
>> FWIW, the old nv driver is legacy, now, and won't be supporting new |
412 |
>> hardware. AFAIK older hardware should be switching as well, for support |
413 |
>> with current software, as nv won't be updated for that any longer, either. |
414 |
>> |
415 |
>> The same thing happened to it as happened to nvidia's proprietary network |
416 |
>> driver some years ago; pretty much everyone involved, including the |
417 |
>> distros that used to ship nv and nvidia itself, seems to have recognized |
418 |
>> that the reverse-engineered work is now better than nvidia's basic |
419 |
>> freedomware stub driver, nv, and nouveau has officially taken its place. |
420 |
>> |
421 |
>> -- |
422 |
>> Duncan - List replies preferred. No HTML msgs. |
423 |
>> "Every nonfree program has a lord, a master -- |
424 |
>> and if you use the program, he is your master." Richard Stallman |
425 |
>> |
426 |
>> |
427 |
>> Barry Schwartz posted on Tue, 20 Mar 2012 01:20:13 -0500 as excerpted: |
428 |
>> |
429 |
>> |
430 |
>>> Unfortunately the nvidia drivers are needed not only for graphics but |
431 |
>>> also to use the GPU for scientific calculations, including for donating |
432 |
>>> processor time to medical research, for instance. |
433 |
>>> |
434 |
>> My donation ends where their disrespect for human freedom begins. (Over |
435 |
>> a decade ago, back on MS, I used to run distributed.net. However, they |
436 |
>> don't have a freedomware client, or at least didn't back then, and while |
437 |
>> I understand the reasons why -- someone cheating and saying they did the |
438 |
>> work when they didn't, just to get the stats -- that didn't change the |
439 |
>> fact that I wasn't going to run servantware. But as they say, YMMV.) |
440 |
>> |
441 |
>> -- |
442 |
>> Duncan - List replies preferred. No HTML msgs. |
443 |
>> "Every nonfree program has a lord, a master -- |
444 |
>> and if you use the program, he is your master." Richard Stallman |
445 |
>> |
446 |
>> |
447 |
>> |
448 |
> |
449 |
> |