Did you do a emerge @module-rebuild after updating your kernel?

On Tue, Mar 29, 2016, 04:26 <cov...@ccs.covici.com> wrote:

> Philip Webb <purs...@ca.inter.net> wrote:
>
> > 160329 cov...@ccs.covici.com wrote:
> > > With 4.1.20 the nvidia drivers I am using get an invalid argument
> > > when trying to modprobe it.  Its version 355.11-r4.
> > > If I try the latest version, I get modeset errors,
> > > although it stops giving me the invalid argument.
> >
> > I had a problem with 358 + 361 , but the solution was simple :
> > I have "-*" to start the list of USE flags in  make.conf
> > -- yes, I know ... ! -- & there were  3  new USE flags
> > which I needed to set properly --  driver gtk3 kms  -- to make it work.
> >
> > Check your Nvidia USE flags, just in case.
> >
> > HTH
> Thanks for your quick response.
>
> Version 358.16-r5 still gives invalid argument, with no driver use flag
> available and the latest version 361.28-r2 gives me modeset errors, so I
> am sort of stuck.  The use flags you mentioned are all mandatory in that
> version.
>
>
> --
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
>
>          John Covici
>          cov...@ccs.covici.com
>
>

Reply via email to