From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] x11-drivers/nvidia-drivers-391+ does not support latest GPU?
Date: Thu, 12 Apr 2018 19:47:19 +0200 [thread overview]
Message-ID: <20180412174719.jhgppzscuykwklk7@solfire> (raw)
In-Reply-To: <c9075f0e-7254-b08f-f7e4-bdc78a61683d@gmail.com>
On 04/12 10:54, Dale wrote:
> Alexey Eschenko wrote:
> > Hi.
> >
> > I've just read regular @world build log and found this:
> >
> >> * Messages for package x11-drivers/nvidia-drivers-396.18-r1:
> >>
> >> * ***** WARNING *****
> >> *
> >> * You are currently installing a version of nvidia-drivers that is
> >> * known not to work with a video card you have installed on your
> >> * system. If this is intentional, please ignore this. If it is not
> >> * please perform the following steps:
> >> *
> >> * Add the following mask entry to /etc/portage/package.mask by
> >> * echo ">=x11-drivers/nvidia-drivers-391.0.0" >
> >> /etc/portage/package.mask/nvidia-drivers
> >> *
> >> * Failure to perform the steps above could result in a non-working
> >> * X setup.
> >> *
> >> * For more information please read:
> >> * http://www.nvidia.com/object/IO_32667.html
> >
> > I'm very surprised because I have GTX 1080 GPU:
> >
> >> # lspci | fgrep VGA
> >> 42:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce
> >> GTX 1080] (rev a1)
> > Is this some kind of maintainer's mistake or does NVIDIA really messed
> > up with drivers again?
> >
>
> It looks to me like the 396 versions of nvidia-drivers is not compatible
> with your card. Most likely, you have to stick with the 391 series. I
> for example have a older card that requires the 340 series. I have to
> mask anything above that. You for example may need to mask anything 396
> or above.
>
> You should be able to go to the nvidia website and find out exactly what
> series of drivers you need and then mask anything above that. Once that
> is done, you shouldn't have this problem again.
>
> Hope that helps.
>
> Dale
>
> :-) :-)
>
Hi Dale,
I was also hit by this message...
For me it looks like that sticking to a certain version of the
nvidia-drivers will also bind me to an - then older - kernel version.
In my case I would be bound to the 390.* versions of that drivers.
This drivers compile fine with the linux-kernel 4.16.2 ... but the
boot throws me back to the console.
dmesg shows this then:
[ 32.227140] nvidia: Unknown symbol swiotlb_map_sg_attrs (err 0)
[ 32.281875] nvidia: Unknown symbol swiotlb_map_sg_attrs (err 0)
Do I really need to buy a new nvidia card (I am using Blender a lot)
just to be able to update the kernel??
Slightly alarmed
Meino
next prev parent reply other threads:[~2018-04-12 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 13:31 [gentoo-user] x11-drivers/nvidia-drivers-391+ does not support latest GPU? Alexey Eschenko
2018-04-12 15:54 ` Dale
2018-04-12 17:47 ` tuxic [this message]
2018-04-12 18:21 ` Dale
2018-04-12 18:57 ` tuxic
2018-04-12 19:01 ` [gentoo-user] " Nikos Chantziaras
2018-04-12 22:18 ` tuxic
2018-04-12 22:29 ` Nikos Chantziaras
2018-04-12 22:37 ` tuxic
2018-04-13 0:31 ` Adam Carter
2018-04-13 0:39 ` Nikos Chantziaras
2018-04-13 8:08 ` Alexey Eschenko
2018-04-13 6:07 ` [gentoo-user] " Arve Barsnes
-- strict thread matches above, loose matches on Subject: below --
2018-04-12 13:31 Alexey Eschenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180412174719.jhgppzscuykwklk7@solfire \
--to=tuxic@posteo.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox