1 |
I did and nvidia was installed, but modprobe nvidia in this kernel says |
2 |
invalid argument. |
3 |
|
4 |
Ian Bloss <ianlinkcd@×××××.com> wrote: |
5 |
|
6 |
> Did you do a emerge @module-rebuild after updating your kernel? |
7 |
> |
8 |
> On Tue, Mar 29, 2016, 04:26 <covici@××××××××××.com> wrote: |
9 |
> |
10 |
> > Philip Webb <purslow@××××××××.net> wrote: |
11 |
> > |
12 |
> > > 160329 covici@××××××××××.com wrote: |
13 |
> > > > With 4.1.20 the nvidia drivers I am using get an invalid argument |
14 |
> > > > when trying to modprobe it. Its version 355.11-r4. |
15 |
> > > > If I try the latest version, I get modeset errors, |
16 |
> > > > although it stops giving me the invalid argument. |
17 |
> > > |
18 |
> > > I had a problem with 358 + 361 , but the solution was simple : |
19 |
> > > I have "-*" to start the list of USE flags in make.conf |
20 |
> > > -- yes, I know ... ! -- & there were 3 new USE flags |
21 |
> > > which I needed to set properly -- driver gtk3 kms -- to make it work. |
22 |
> > > |
23 |
> > > Check your Nvidia USE flags, just in case. |
24 |
> > > |
25 |
> > > HTH |
26 |
> > Thanks for your quick response. |
27 |
> > |
28 |
> > Version 358.16-r5 still gives invalid argument, with no driver use flag |
29 |
> > available and the latest version 361.28-r2 gives me modeset errors, so I |
30 |
> > am sort of stuck. The use flags you mentioned are all mandatory in that |
31 |
> > version. |
32 |
> > |
33 |
> > |
34 |
> > -- |
35 |
> > Your life is like a penny. You're going to lose it. The question is: |
36 |
> > How do |
37 |
> > you spend it? |
38 |
> > |
39 |
> > John Covici |
40 |
> > covici@××××××××××.com |
41 |
> > |
42 |
> > |
43 |
> |
44 |
> ---------------------------------------------------- |
45 |
> Alternatives: |
46 |
> |
47 |
> ---------------------------------------------------- |
48 |
|
49 |
-- |
50 |
Your life is like a penny. You're going to lose it. The question is: |
51 |
How do |
52 |
you spend it? |
53 |
|
54 |
John Covici |
55 |
covici@××××××××××.com |