1 |
On Wednesday 18 June 2008, Enrico Weigelt wrote: |
2 |
> Hi, |
3 |
> |
4 |
> |
5 |
> I've made the big mistake of bying an notebook w/ geforce go 6100. |
6 |
> |
7 |
> The proprietary drivers *never* worked for me - the binary kernel |
8 |
> modules crashed the whole kernel (complete lockup) after a several |
9 |
> seconds (doesnt even need X to come up for that). |
10 |
> |
11 |
> I've analyzed their module a bit and seen really bad things. |
12 |
> Looks it's a hand-written bunch of assembler code with massive |
13 |
> code obfuscation, just like Skype ;-o |
14 |
> |
15 |
> IMHO, if someone spends so much work into machine code obfuscation, |
16 |
> he *really* has something to hide. Not just some "intellectual |
17 |
> property" (which is outdated alfter a few months). |
18 |
> |
19 |
> Of course, opensource 3D support is (almost) not existing, |
20 |
> (2D works very fine), and NVidia repeatedly states that they |
21 |
> will NOT do the slightest attempt to improve the situation. |
22 |
> |
23 |
> So I strongly suggest, NOT to buy NV cards. |
24 |
> |
25 |
> (BTW: a few month ago, I managed to stop a customer from buying |
26 |
> several hundreds of NV cards - yes, consulting jobs sometimes |
27 |
> make really fun this way ;-P) |
28 |
> |
29 |
|
30 |
and what do you recommend? |
31 |
|
32 |
|
33 |
ATI? Which 3d drivers are as bad as nvidia from 'obfuscation' point of view |
34 |
and a lot worse if you compare the horror stories? Ati, whose drivers even |
35 |
suck in windows? |
36 |
|
37 |
Btw, most of the time people have problems with nvidia its either the cards |
38 |
bios or the mobos. |
39 |
|
40 |
Or Intel? With no 3d power at all? |
41 |
-- |
42 |
gentoo-user@l.g.o mailing list |