| 1 |
130309 »Q« wrote: |
| 2 |
> 130309 Philip Webb <purslow@××××××××.net> wrote: |
| 3 |
>> Doing my usual Saturday system update, I saw a prominent msg |
| 4 |
>> telling me that 'module-init-tools' has been masked |
| 5 |
>> & to use 'kmod' or 'modutils' -- the msgs vary -- to replace it. |
| 6 |
>> When I did so (both), Nvidia wouldn't start, even after remerging it. |
| 7 |
>> Back with 'module-init-tools' -- now in 'package.unmask' -- all is well. |
| 8 |
>> Does anyone know what's going on ? -- did I miss a 'news' item ? |
| 9 |
> ISTR you start with USE="-*". |
| 10 |
|
| 11 |
Yes & I do need to remember to check the USE flags for sensitive pkgs. |
| 12 |
|
| 13 |
> When you built kmod, was it with the tools flag enabled ? |
| 14 |
> The virtual requires it. |
| 15 |
|
| 16 |
root:502 ~> emerge -pv kmod |
| 17 |
... |
| 18 |
sys-apps/kmod-12-r1 USE="-debug -doc -lzma -static-libs -tools zlib" ... |
| 19 |
|
| 20 |
Apparently not, so that's something to try. |
| 21 |
|
| 22 |
> I went with kmod because of what the masking comment |
| 23 |
> for module-init-tools said, and I haven't noticed any trouble. |
| 24 |
> I've got nvidia-drivers-310.32. |
| 25 |
|
| 26 |
Same here. |
| 27 |
|
| 28 |
The actual Xorg error was "can't find module Nvidia", |
| 29 |
so another question is whether it has to be listed somewhere for Kmod ? |
| 30 |
|
| 31 |
Thanks so far. It looks as if the change needs a 'news' msg. |
| 32 |
|
| 33 |
-- |
| 34 |
========================,,============================================ |
| 35 |
SUPPORT ___________//___, Philip Webb |
| 36 |
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto |
| 37 |
TRANSIT `-O----------O---' purslowatchassdotutorontodotca |
Archives