| 1 |
Donnie Berkholz wrote: |
| 2 |
> Dale wrote: |
| 3 |
> |
| 4 |
>>> root@smoker / # eselect set opengl nvidia |
| 5 |
>>> !!! Error: Can't load module set |
| 6 |
>>> exiting. |
| 7 |
>>> root@smoker / # |
| 8 |
>>> |
| 9 |
> |
| 10 |
> Bah, I just gave you the command in the wrong order. `eselect opengl set |
| 11 |
> nvidia` was the right one. Need to tell it which module, before the |
| 12 |
> action to use from that module. I see you figured that out below. |
| 13 |
> |
| 14 |
|
| 15 |
Oh, I see. I did the second one from memory. At least this time it |
| 16 |
worked out for the best. :-o |
| 17 |
> |
| 18 |
>> I assume this ain't good right. O_O OK, I logged out, stopped the GUI, |
| 19 |
>> rmmoded nvidia and reemerged all the nvidia stuff. Reloaded nvidia and |
| 20 |
>> ran the command. Now this is what I get: |
| 21 |
>> |
| 22 |
>> |
| 23 |
>>> root@smoker / # eselect opengl show |
| 24 |
>>> nvidia |
| 25 |
>>> root@smoker / # |
| 26 |
>>> |
| 27 |
>> So that works and then I get this: |
| 28 |
>> |
| 29 |
>> |
| 30 |
>>> root@smoker / # glxinfo |
| 31 |
>>> name of display: :0.0 |
| 32 |
>>> display: :0 screen: 0 |
| 33 |
>>> direct rendering: Yes |
| 34 |
>>> |
| 35 |
> |
| 36 |
> Sweet! |
| 37 |
> |
| 38 |
|
| 39 |
Yea, progress!!!! O_O I need that too. |
| 40 |
> |
| 41 |
>> That looks good to, still no worky and my screens are really slow. |
| 42 |
>> Sometimes even the mouse is slow. I also noticed that if I go to |
| 43 |
>> configure desktop and try to play with the screen saver settings, it |
| 44 |
>> hogs up a LOT of CPU time. Almost all of it yet it does not work at all. |
| 45 |
>> |
| 46 |
> |
| 47 |
> Odd. |
| 48 |
> |
| 49 |
> |
| 50 |
>> Are you out of ideas yet? I'm not sure what to do. The emerge -e world |
| 51 |
>> is still going though. 309 of 866 and counting. kdelibs went by a bit |
| 52 |
>> ago. It's on swig right now. I dunno what it is. |
| 53 |
>> |
| 54 |
> |
| 55 |
> This could be a problem, particularly if you have preemption off or |
| 56 |
> don't set PORTAGE_NICENESS. If you're running that in a screen session, |
| 57 |
> try a ^Z (ctrl-z) to suspend it for a bit and see whether that helps, |
| 58 |
> then `fg` to foreground it again. |
| 59 |
> |
| 60 |
|
| 61 |
I have nice set to 5. KDE runs at 0 so it should be OK. All this |
| 62 |
started when I upgraded xorg. I did create a new config file though. I |
| 63 |
also tried the old one just to test it. I couldn't tell any difference |
| 64 |
at all. |
| 65 |
> |
| 66 |
>> Any clue? Am I doing something wrong? Is this new xorg that bad? |
| 67 |
>> Should I unmask the newer xorg? I read the nvidia drivers are not ready |
| 68 |
>> yet. |
| 69 |
>> |
| 70 |
> |
| 71 |
> At this point it's not real clear what the problem is. You could try |
| 72 |
> running oprofile to see where all the time is being spent, then rebuild |
| 73 |
> that package with debugging support (Add -g to CFLAGS, remove |
| 74 |
> -fomit-frame-pointer) to get info on where in that program the time is |
| 75 |
> spent. |
| 76 |
> |
| 77 |
> < snip > |
| 78 |
> |
| 79 |
> Thanks, |
| 80 |
> Donnie |
| 81 |
> |
| 82 |
> |
| 83 |
|
| 84 |
I may have to try that when emege -ev world gets done. It has 480 to go |
| 85 |
yet and most of KDE has not been done. Maybe something got lost in the |
| 86 |
shuffle somewhere. |
| 87 |
|
| 88 |
If you think of something else, let me know. If I find anything out |
| 89 |
I'll post it too. |
| 90 |
|
| 91 |
Thanks |
| 92 |
|
| 93 |
Dale |
| 94 |
:-) :-) |
| 95 |
-- |
| 96 |
gentoo-user@g.o mailing list |
Archives