I did and nvidia was installed, but modprobe nvidia in this kernel says
invalid argument.
Ian Bloss wrote:
> Did you do a emerge @module-rebuild after updating your kernel?
>
> On Tue, Mar 29, 2016, 04:26 wrote:
>
> > Philip Webb wrote:
> >
> > > 160329 cov...@ccs.covici.com wrote:
> > > > W
Did you do a emerge @module-rebuild after updating your kernel?
On Tue, Mar 29, 2016, 04:26 wrote:
> Philip Webb 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.
> >
Philip Webb 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.
>
>
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 , bu
Hi. I normally do updates approximately monthly and I use the gnome
overlay, so I get the latest gnome. I am also using ~amd64 version of
gentoo.
Now, this time when I went from version 4.1.17 to 4.1.20 kernel and did
my monthly update at the same time, two things happened. On the 4.1.17
kerne
5 matches
Mail list logo