1 |
i admit i dont know how to check for those, if i would it was a none |
2 |
issue, from what i read i agree that it is binary driver issue, i talked |
3 |
with seemant about it, but don't want to work on his ebuild more than |
4 |
adding the line spanky suggested from 56702 |
5 |
this will keep things sane till he comes up with a permanent fix |
6 |
|
7 |
or more likely till nvidia comes out with newer drivers , everyone jumps |
8 |
on those and problem goes magically away |
9 |
|
10 |
binaries are always fun |
11 |
|
12 |
|
13 |
|
14 |
Luke-Jr wrote: |
15 |
|
16 |
>On Monday 13 September 2004 12:33 am, Daniel Goller wrote: |
17 |
> |
18 |
> |
19 |
>>added -mno-sse2 conditionally to xorg CFLAGS with gcc 3.4 till this is |
20 |
>>sorted out, since we have pentium4, pentium-m and amd64 users with |
21 |
>>problems and all three of those cpus have sse2 |
22 |
>> |
23 |
>> |
24 |
> |
25 |
>xorg working fine w/ amd64 here... reading the comments, it seems that this is |
26 |
>a nVidia-binary-related bug, not really so much an xorg bug. Perhaps somehow |
27 |
>make it conditional on usage of such drivers? |
28 |
> |
29 |
> |
30 |
> |
31 |
>>Mike Frysinger wrote: |
32 |
>> |
33 |
>> |
34 |
>>>On Sunday 12 September 2004 07:49 pm, Patrick Dawson wrote: |
35 |
>>> |
36 |
>>> |
37 |
>>>>It seems to affect many/most using xorg-x11 with -march=pentium4. |
38 |
>>>> |
39 |
>>>> |
40 |
>>>it's sse2 code, not pentium4 |
41 |
>>>-mike |
42 |
>>> |
43 |
>>> |
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |