Re: [gentoo-user] AMD Opteron microcode updates for spectre
On Thu, Apr 12, 2018 at 9:20 PM, taii...@gmx.comwrote: > When is gentoo going to receive these? > Has AMD actually released anything publicly? I find AMD's microcode updates to be horribly documented in general, unless there is some website somewhere published by AMD that somebody could be helpful enough to point out... Typically these work their way into linux-firmware, somehow, usually without any indication as to what they actually do. Back when Spectre first was discovered there was a microcode update being circulated that many thought addressed Spectre but my understanding is that it turned out to have nothing to do with it. Not that you would necessarily know one way or another as it is just a binary blob devoid of any kind of release notes. I've always been an AMD fan but they'd do their customers a great service if they just posted a website with links to various versions of their microcode and even a sentence or two describing why each was released. All that said, once you do get updated microcode it can be loaded following some instructions on the wiki (easiest way is to embed the microcode in the kernel and there might be a kernel option you need to toggle). Looking at the linux-firmware upstream git I don't see any recent AMD-related commits there. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/ In any case, if somebody spots a blob from someplace reasonably credible I'm sure the linux-firmware maintainers wouldn't object to filing a bug... -- Rich
[gentoo-user] AMD Opteron microcode updates for spectre
When is gentoo going to receive these? 0xDF372A17.asc Description: application/pgp-keys
[gentoo-user] Re: x11-drivers/nvidia-drivers-391+ does not support latest GPU?
On 13/04/18 01:37, tu...@posteo.de wrote: On 04/13 01:29, Nikos Chantziaras wrote: Do you have something specific in mind? I'm not aware of software that requires a non-LTS kernel right now, or a beta X.Org driver, or a beta nvidia-driver. I think of security incidents like meltdown/spectre for example... It's an LTS kernel. "Long-Term Support." It gets all the security fixes and bugfixes for years to come, while kernels like 4.15 and 4.16 will stop getting updated after a short while. LTS kernels on the other hand are updated for years.
Re: [gentoo-user] Re: x11-drivers/nvidia-drivers-391+ does not support latest GPU?
> I think of security incidents like meltdown/spectre for example... > LTS kernels are maintained, so they get all the required patches.
Re: [gentoo-user] Re: x11-drivers/nvidia-drivers-391+ does not support latest GPU?
On 04/13 01:29, Nikos Chantziaras wrote: > On 13/04/18 01:18, tu...@posteo.de wrote: > > On 04/12 10:01, Nikos Chantziaras wrote: > > > On 12/04/18 16:31, Alexey Eschenko wrote: > > > > Is this some kind of maintainer's mistake or does NVIDIA really messed > > > > up with drivers again? > > > > > > Before updating the nvidia driver, you should always check here: > > > > > >http://www.nvidia.com/Download/Find.aspx > > > > > > and see if the version you're updating to is a beta driver or not. > > > > > > As a long time nvidia-drivers user, I really recommend to: > > > > > >1. Use an LTS kernel series (latest LTS series is 4.14.x.) > > >2. Do not install nvidia beta drivers. > > >3. Do not use X.Org pre-releases. > > > > > > Currently, that means these in package.mask: > > > > > >>=sys-kernel/gentoo-sources-4.15 > > >>=x11-drivers/nvidia-drivers-391 > > >>=x11-base/xorg-server-1.19.99 > > > > > > Unless you're using Chrome, where 390 has a bug that makes it unusable > > > slow, > > > so you need: > > > > > >>=x11-drivers/nvidia-drivers-385 > > > > > > You need to check on the available versions these packages manually from > > > time to time to see if it's safe to update them. > > > > > > Also, nvidia driver version can be confusing. 390 is the latest stable > > > series, while 384 is the "LTS-like" stable series. To be frank, I find it > > > impossible to tell what's happening with driver releases from nvidia if I > > > don't read phoronix.com news. > > > > > > In any event, the TL;DR is that sticking to non-beta drivers and non-beta > > > xorg and the latest LTS kernel will result in avoiding the majority of > > > breakages. > > > > > > > > > > hi Alexey, > > > > which in turn is, what I said before: > > I will be bound to older versions of software. > > It is, what I try to avoid. > > Do you have something specific in mind? I'm not aware of software that > requires a non-LTS kernel right now, or a beta X.Org driver, or a beta > nvidia-driver. > > I think of security incidents like meltdown/spectre for example...
[gentoo-user] Re: x11-drivers/nvidia-drivers-391+ does not support latest GPU?
On 13/04/18 01:18, tu...@posteo.de wrote: On 04/12 10:01, Nikos Chantziaras wrote: On 12/04/18 16:31, Alexey Eschenko wrote: Is this some kind of maintainer's mistake or does NVIDIA really messed up with drivers again? Before updating the nvidia driver, you should always check here: http://www.nvidia.com/Download/Find.aspx and see if the version you're updating to is a beta driver or not. As a long time nvidia-drivers user, I really recommend to: 1. Use an LTS kernel series (latest LTS series is 4.14.x.) 2. Do not install nvidia beta drivers. 3. Do not use X.Org pre-releases. Currently, that means these in package.mask: >=sys-kernel/gentoo-sources-4.15 >=x11-drivers/nvidia-drivers-391 >=x11-base/xorg-server-1.19.99 Unless you're using Chrome, where 390 has a bug that makes it unusable slow, so you need: >=x11-drivers/nvidia-drivers-385 You need to check on the available versions these packages manually from time to time to see if it's safe to update them. Also, nvidia driver version can be confusing. 390 is the latest stable series, while 384 is the "LTS-like" stable series. To be frank, I find it impossible to tell what's happening with driver releases from nvidia if I don't read phoronix.com news. In any event, the TL;DR is that sticking to non-beta drivers and non-beta xorg and the latest LTS kernel will result in avoiding the majority of breakages. hi Alexey, which in turn is, what I said before: I will be bound to older versions of software. It is, what I try to avoid. Do you have something specific in mind? I'm not aware of software that requires a non-LTS kernel right now, or a beta X.Org driver, or a beta nvidia-driver.
Re: [gentoo-user] Re: x11-drivers/nvidia-drivers-391+ does not support latest GPU?
On 04/12 10:01, Nikos Chantziaras wrote: > On 12/04/18 16:31, Alexey Eschenko wrote: > > Is this some kind of maintainer's mistake or does NVIDIA really messed > > up with drivers again? > > Before updating the nvidia driver, you should always check here: > > http://www.nvidia.com/Download/Find.aspx > > and see if the version you're updating to is a beta driver or not. > > As a long time nvidia-drivers user, I really recommend to: > > 1. Use an LTS kernel series (latest LTS series is 4.14.x.) > 2. Do not install nvidia beta drivers. > 3. Do not use X.Org pre-releases. > > Currently, that means these in package.mask: > > >=sys-kernel/gentoo-sources-4.15 > >=x11-drivers/nvidia-drivers-391 > >=x11-base/xorg-server-1.19.99 > > Unless you're using Chrome, where 390 has a bug that makes it unusable slow, > so you need: > > >=x11-drivers/nvidia-drivers-385 > > You need to check on the available versions these packages manually from > time to time to see if it's safe to update them. > > Also, nvidia driver version can be confusing. 390 is the latest stable > series, while 384 is the "LTS-like" stable series. To be frank, I find it > impossible to tell what's happening with driver releases from nvidia if I > don't read phoronix.com news. > > In any event, the TL;DR is that sticking to non-beta drivers and non-beta > xorg and the latest LTS kernel will result in avoiding the majority of > breakages. > > hi Alexey, which in turn is, what I said before: I will be bound to older versions of software. It is, what I try to avoid. Cheers! Meino
Re: [gentoo-user] Kernel module signature now shown on modinfo
This has been broken for almost two years; the signature format switched to PKCS#7 and modinfo doesn't support it. It's not as simple as just patching kmod because evidently the kernel change regressed or disrespected the relevent structure in the modules in a way that makes it impossible for kmod to even make sense of. Details here: https://github.com/coreos/bugs/issues/1054 -David On Wed, Apr 11, 2018 at 4:39 PM, Ben Mezgerwrote: > Greetings, > > I have enabled module signature verification on my kernel, and it does > seem to be enabled upon boot: > > $ dmesg | grep -i 'x.*509' > [1.259988] Asymmetric key parser 'x509' registered > [1.811026] Loading compiled-in X.509 certificates > [1.813833] Loaded X.509 cert 'Build time autogenerated kernel key: > 77e716fc52a6293567d953cd24a5977e55b41a5e' > > and doing a cat /proc/keys seems to show the key enabled: > > $ cat /proc/keys > ... > 37c67374 I-- 1 perm 1f03 0 0 asymmetri Build time > autogenerated kernel key: 77e716fc52a6293567d953cd24a5977e55b41a5e: > X509.rsa 55b41a5e [] > ... > > However, if I do a modinfo to see the key on a module, it seems empty: > > $modinfo ntfs > filename: /lib/modules/4.9.76-gentoo-r1/kernel/fs/ntfs/ntfs.ko > license:GPL > version:2.1.32 > description:NTFS 1.2/3.x driver - Copyright (c) 2001-2014 Anton > Altaparmakov and Tuxera Inc. > author: Anton Altaparmakov > alias: fs-ntfs > srcversion: 0D7ACE93F603E9350827FB8 > depends: > intree: Y > vermagic: 4.9.76-gentoo-r1 SMP mod_unload > signat: PKCS#7 > signer: > sig_key: > sig_hashalgo: md4 > > And hex dump does show me the digital signature appended at the end: > > $ hexdump -C /lib64/modules/4.9.76-gentoo-r1/kernel/fs/ntfs/ntfs.ko| tail > 0004e8c0 e3 dd 54 9d 5e f1 1a 12 56 47 4e 54 91 b9 fa ce > |..T.^...VGNT| > 0004e8d0 e6 01 db 37 eb 83 f3 77 10 f0 b5 f8 11 fd 4e 86 > |...7...w..N.| > 0004e8e0 6c 81 8a 61 c2 15 6d 5a 35 93 8b 33 c0 32 2f e4 > |l..a..mZ5..3.2/.| > 0004e8f0 8c 15 71 de c8 c5 39 58 cc e8 65 e1 be 36 e6 02 > |..q...9X..e..6..| > 0004e900 b0 75 b5 a2 73 d8 4d 22 e7 2f 53 1f 42 fb ee 58 > |.u..s.M"./S.B..X| > 0004e910 f2 65 44 13 26 30 7b 31 1c 58 12 5a f2 5d b1 45 > |.eD.&0{1.X.Z.].E| > 0004e920 3a f0 a5 79 74 f4 00 00 02 00 00 00 00 00 00 00 > |:..yt...| > 0004e930 02 9e 7e 4d 6f 64 75 6c 65 20 73 69 67 6e 61 74 |..~Module > signat| > 0004e940 75 72 65 20 61 70 70 65 6e 64 65 64 7e 0a|ure > appended~.| > 0004e94e > > My question is: why doesn't modinfo show me the key fingerprint? > > -- > Kind regards, > Met een vriendelijke groet, > > Ben Mezger > https://seds.nl > PGP: C473 DDC9 D1B1 40AF 2051 1CF6 18C4 6052 1688 92F7 > >
[gentoo-user] Re: x11-drivers/nvidia-drivers-391+ does not support latest GPU?
On 12/04/18 16:31, Alexey Eschenko wrote: Is this some kind of maintainer's mistake or does NVIDIA really messed up with drivers again? Before updating the nvidia driver, you should always check here: http://www.nvidia.com/Download/Find.aspx and see if the version you're updating to is a beta driver or not. As a long time nvidia-drivers user, I really recommend to: 1. Use an LTS kernel series (latest LTS series is 4.14.x.) 2. Do not install nvidia beta drivers. 3. Do not use X.Org pre-releases. Currently, that means these in package.mask: >=sys-kernel/gentoo-sources-4.15 >=x11-drivers/nvidia-drivers-391 >=x11-base/xorg-server-1.19.99 Unless you're using Chrome, where 390 has a bug that makes it unusable slow, so you need: >=x11-drivers/nvidia-drivers-385 You need to check on the available versions these packages manually from time to time to see if it's safe to update them. Also, nvidia driver version can be confusing. 390 is the latest stable series, while 384 is the "LTS-like" stable series. To be frank, I find it impossible to tell what's happening with driver releases from nvidia if I don't read phoronix.com news. In any event, the TL;DR is that sticking to non-beta drivers and non-beta xorg and the latest LTS kernel will result in avoiding the majority of breakages.
Re: [gentoo-user] x11-drivers/nvidia-drivers-391+ does not support latest GPU?
On 04/12 01:21, Dale wrote: > tu...@posteo.de wrote: > > 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 > > > > I'm not sure on having to buy a new card. Mine is older, GT220 BUT I'm > still using kernel version 4.5.2. I've got a newer kernel available, I > just haven't rebooted in many months. I just tried, the version I'm > using won't build with newer kernels, 4.9.34. So, you have a > interesting question. > > I seem to recall having to set up a overlay for a slightly older version > because the newer version for my series would build with current 4.5 > kernel but my screen was all messed up. I had trouble getting logged in > so that I could kill X to even get the console to work. So I'm using a > version of nvidia that isn't even in the tree any longer as it is. > > I may have to check into this more later. Funny thing is, I was looking > at newer video cards just the other day. I was just wanting a spare, in > case the current one burnt out. I wasn't thinking about the software > not working. > > Dale > > :-) :-) > Hi Dale, h...sticking to old cards has a couple of drawbacks in my case: -- I am using Blender a lot. Blender loves CUDA (and recentlu becomes better with AMD cards, which has more to do with AMD than with Blender as far as I can remember) to render on the GPU instead with CPU, which is much more faster. Even Blender becomes more power hungry (CPU power, not necessarily electrical power ;) because it get more and more features (Physical based shading technics for example). So from time to time I need a new graphics card. But I dont like it if nvidia is dictating me what to buy when. The opensourced nvidia driver of the kernel by far is not that capable when it comes to GPU rendering as far as I know. So no option here. -- Not only because of meltdown and spectre I dont want to stick with old kernels. As the kernel is the heart of my system, I want to update the kernel as soon as possible. Due the problem with the nvidia-drivers currentlu I am urged to stick with linux-15.15 currently. -- I have two graphic cards in my system: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) NVIDIA Corporation GF108 [GeForce GT 430] (rev a1) The smaller one is for the desktop, the newer one for rendering. If one renders with the same card as being used for the desktop, it makes the desktop quite stuttering while a render process is running. Rendering animations can
Re: [gentoo-user] x11-drivers/nvidia-drivers-391+ does not support latest GPU?
tu...@posteo.de wrote: > 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 > I'm not sure on having to buy a new card. Mine is older, GT220 BUT I'm still using kernel version 4.5.2. I've got a newer kernel available, I just haven't rebooted in many months. I just tried, the version I'm using won't build with newer kernels, 4.9.34. So, you have a interesting question. I seem to recall having to set up a overlay for a slightly older version because the newer version for my series would build with current 4.5 kernel but my screen was all messed up. I had trouble getting logged in so that I could kill X to even get the console to work. So I'm using a version of nvidia that isn't even in the tree any longer as it is. I may have to check into this more later. Funny thing is, I was looking at newer video cards just the other day. I was just wanting a spare, in case the current one burnt out. I wasn't thinking about the software not working. Dale :-) :-)
Re: [gentoo-user] x11-drivers/nvidia-drivers-391+ does not support latest GPU?
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
[gentoo-user] Re: Wrong instructions when installing Oracle JRE
On 2018-04-11 01:08, R0b0t1 wrote: > Can we stop using Oracle's JVM? An ever recurring question, and of course one that should be asked. What is the alternative? icedtea is the _same_ VM, just built differently. And building it from source requires cups, which I don't want on my system. Also, at this point I don't feel any better about using a RH backed package than an Oracle one. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.
Re: [gentoo-user] x11-drivers/nvidia-drivers-391+ does not support latest GPU?
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 :-) :-)
[gentoo-user] x11-drivers/nvidia-drivers-391+ does not support latest GPU?
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? -- Kind regards, Alexey Eschenko https://skobk.in/
[gentoo-user] x11-drivers/nvidia-drivers-391+ does not support latest GPU?
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? -- Kind regards, Alexey Eschenko https://skobk.in/