| 1 |
Zhu Sha Zang wrote: |
| 2 |
> <<SNIP>> |
| 3 |
> |
| 4 |
> My problems: |
| 5 |
> |
| 6 |
> 1) Gentlemen, with this hardware when i try to compile some "nice" |
| 7 |
> software like chromium, pyside or openoffice my system "freeze". I |
| 8 |
> can't do anything like use keyboard, mouse or switch betwenn windows. |
| 9 |
> How can i find the motive to this strange (???) problem? I've used |
| 10 |
> --load-average in MAKEOPTS with the same result. |
| 11 |
> |
| 12 |
> 2) The source x11-drivers/nvidia-drivers-256.53 don't compile against |
| 13 |
> kernel-2.6.36-r3 and upgrading to nvidia-drivers-260.19.21 my X don't |
| 14 |
> start using the same LG FLATRON W2043S. Appears to be a resolution |
| 15 |
> problem, cos the light that monitor blink and the screen keep black. A |
| 16 |
> bug? |
| 17 |
> |
| 18 |
> Att |
| 19 |
|
| 20 |
For #1. Mine does this at times when compiling OOo too. I think it |
| 21 |
hits spots in the compile process that are really using the CPU and it |
| 22 |
just crams it through. I had it do it on my current machine and on |
| 23 |
another machine I installed OOo on. I don't think this is to out of the |
| 24 |
norm. I guess if you have fast enough processor that you won't be able |
| 25 |
to tell it tho. |
| 26 |
|
| 27 |
I haven't' noticed this in the other packages tho. I don't use chromium |
| 28 |
and don't think I use pyside either. |
| 29 |
|
| 30 |
For #2. I have a older card and sometimes I have to unmask a newer |
| 31 |
nvidia driver to get it to work. Sometimes, I have to use a somewhat |
| 32 |
older kernel until nvidia gets the driver updated to work with the new |
| 33 |
kernel, usually not to long tho. You use a newer driver but still may |
| 34 |
have to check and make sure the driver works with that kernel. Gentoo |
| 35 |
is bleeding edge sometimes. ;-) |
| 36 |
|
| 37 |
Dale |
| 38 |
|
| 39 |
:-) :-) |
Archives