[elrepo] Keyboard ceases functioning after install of kmod-nvidia-340xx

[Manuel Wolfshant]

On 6/24/20 2:19 AM, Jeremy Yocum wrote:
> Thanks Phil—
>
> Unfortunately there's nothing in my /etc/yum.repos.d/CentOS-Vault.repo 
> file.

Then this config file is broken on your system. You might be able to fix 
it by using yum update centos-release. Alternatively you can just 
download the centos-release.rpm from any centos mirror and extract the 
the CentOS-Vault.repo file from it



> I just read on an old post that it can take quite some time before old 
> kernels get moved to the vault repo, so this is probably another dead end.

Whatever post you read is either wrong or you misinterpreted what it 
said. The content is in vault , you can easily verify by going 
tohttp://vault.centos.org/8.1.1911/BaseOS/x86_64/os/Packages/ . There 
never was a distinction between kernel packages and the other packages. 
All the content it relocated as a whole.

And, with my had of member of the centos qa team on, I can tell you 
this: the content on the mirrors is/was NEVER removed prior to being 
copied to the vault so you would find the required content either in the 
original place (i.e. on the mirrors ) or in the vault. They even do 
overlap for a short period of time, existing in both places in the same 
time.

To be very pedantic, It might be needed, though, to adjust the path in 
CentOS-Base to point to the path where the older minor release resides 
instead of using %releasever, as it normally is defined. This however is 
needed in a very few extreme cases and should probably never be used by 
regular users.


>
> I'm really at a loss here. The keyboard was working *fine* until I 
> installed the ELRepo .rpms, and now nothing I do will bring it back. 
> The keyboard doesn't work when I go back to 4.18.0-147.el8.x86_64, the 
> previous kernel, either, so I fail to see how reinstalling 
> 4.18.0-147.8.1.el8_1.x86_64 will make it work.
>
> I really want to understand what happened so I can avoid running into 
> the same problem in the future. Seeing as I'm new to Linux it's an 
> uphill battle.

I can feel you pain. Really. The short way out is a reinstall but I 
would very much like to find the root cause of your issues.


>
> But this was 100% caused by the ELRepo packages. Literally nothing 
> else changed from when the keyboard worked to when it didn't. I 
> powered the machine on, I installed the ELRepo packages, I rebooted 
> and now the keyboard doesn't work. There weren't any other changes 
> made. Nothing.

Except for the fact that the elrepo packages you have installed do not 
touch the keyboard settings. Basically they just place the driver files 
provided by NVidia in the apropriate kernel directories and respectively 
in X's directories, instruct the system to use them and that's pretty 
much all.

And certainly they should not have any effect post install.


>
> I'm happy to do homework and troubleshoot, but I need some pointers 
> because googling gets me nowhere. No combination of keywords sheds any 
> light on it at all. Every search result brings me to someone who has 
> an issue with their keyboard *and* the touchpad — but my touchpad 
> works fine!

Heh. I had a similar issue with a Lenovo laptop last week. Except that 
in my case the kbd was functional but the touchpad was not.



> No one has an issue where the machine's keyboard doesn't work, but the 
> trackpad *does* work and the external USB keyboard
> *does* work.
>
> Does anyone have any insight? At all? Where I could even *start* 
> diagnosing and troubleshooting? Even someone I could ask for advice from?

I am a bit worried by the fact that your 
/etc/yum.repos.d/CentOS-Vault.repo is empty. To me this looks like 
another issue with the system, which might have been triggered when you 
installed the elrepo packages but is definitely not caused by those 
packages themselves. Except for the elrepo-release package, no elrepo 
package touches /etc/yum*



>
> Or should I just reinstall CentOS — and then steer far far clear of 
> ELRepo for the rest of my days?

Or you could start fresh and try to reproduce. I am quite sure that 
unless the drivers hit some odd BIOS bug ( which is not impossible -- 
you really do not want to get me started on the various BIOS bugs I met 
over time ) , what you see as explanation for what happened is not 
actually correct


>
> I really, really don't want that to be my only answer. ELRepo seems 
> like an invaluable toolbox maintained by some very dedicated people! I 
> don't want to have to be afraid of it.

Well, you should not. But, what can I say ? I fiddle with my own daemons 
and it seems that IBM and xen have a fang against me :)



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20200624/60c7ea43/attachment-0001.html>