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

Tue Jun 23 14:01:58 EDT 2020

Just to update everyone...

I waited for a USB keyboard to come in the mail. Plugged in the USB
keyboard and it worked just fine. Weirdly something about running the
ELRepo drivers screwed up my NetworkManager so I had to manually add
nameservers in order to actually get access to any repositories.

I tried reinstalling the current kernel but I got this:

      [root at localhost ~]# yum reinstall kernel-4.18.0-147.8.1_el8_1.x86_64
      Last metadata expiration check: 0:00:10 ago on Tue 23 Jun 2020
01:31:07 PM EDT.
      Installed package *kernel-4.18.0-147.8.1.el8_1.x86_64* (from BaseOS)
not available.
      Error: No packages marked for reinstall.

I tried running "yum remove" and the kernel, and then running "yum
install." It removed the kernel as expected but then said:

      [root at localhost ~]# yum install kernel-4.18.0-147.8.1_el8_1.x86_64
      Last metadata expiration check: 0:05:28 ago on Tue 23 Jun 2020
01:31:07 PM EDT.
      No match for argument: *kernel-4.18.0-147.8.1.el8_1.x86_64*
      Error: Unable to find a match: kernel-4.18.0-147.8.1.el8_1.x86_64

So.... no, I can't reinstall the kernel as you suggested, Phil. It looks
like that kernel disappeared somehow!

>From there I thought, "What the heck? I'll update to the newest kernel and
see what happens."

It updated as expected, but with the new kernel I still can't access my
laptop's actual keyboard — *and* my WiFi (Broadcom) driver stopped working.
(I was actually expecting the WiFi to not work, since I was warned I'd need
to repeat the process every time I upgrade a kernel).

At this point, unless someone here has any other suggestions, I'm just
going to back up my data, wipe the machine and reinstall CentOS.

To sum up, as soon as I installed ELRepo's Nvidia Graphics driver:
        1) I can no longer use my laptop's keyboard after I leave the grub
menu, I can only use a USB keyboard
        2) It screwed up my NetworkManager so I had to manually add
nameservers

....anyone have any idea why it did this???

— Jeremy

On Tue, Jun 16, 2020 at 7:08 PM Jeremy Yocum <oceanjeremy at gmail.com> wrote:

> Thanks Manuel—
>
> One note:
>
> I type "exit" and it says "Warning: Not all disks have been found.
>>> Warning: You might want to regenerate your initramfs." (So maybe initramfs
>>> is the problem?) Then it sits after those error messages indefinitely,
>>> hours if I let it.
>>
>> In this stage it just waits indefinitely for your input. You should,
>> indeed, regenerate the initramfs.
>
>
> It is definitely *NOT* waiting for my input. It will not accept any input.
> The system isn't frozen — one time I plugged in the install ISO USB so I
> could reboot into recovery mode that way and it spilled out information
> saying it detected a USB drive device / etc / etc. So the system's still
> live, it just won't take any input from me (except for Ctrl-Alt-Del). So in
> this mode (emergency mode from the oldest / recovery kernel) it still
> "hears" the keyboard, but at that stage ("You might want to regenerate your
> initramfs") it isn't asking for input.
>
> I did go into recovery mode and try to rebuild initramfs for the newest
> kernel version: "dracut --kver {my kernel version} --force"
>
> It said it rebuilt the initramfs so I rebooted, but no dice. Still no
> keyboard input.
>
>
> — Jeremy
>
>
>
>
> On Tue, Jun 16, 2020 at 6:17 PM Manuel Wolfshant <wolfy at nobugconsulting.ro>
> wrote:
>
>> On 6/17/20 12:40 AM, Jeremy Yocum wrote:
>>
>> Thanks everyone for the input!
>>
>> On 6/16/20 7:21 PM, Phil Perry wrote:
>> > Hi Jeremy,
>> >
>> > Are all kernels affected?
>> >
>> Yes, kind of? The two most recent kernels on my grub boot have the same
>> issue — the keyboard stops working right after I leave the grub menu.
>>
>> This *doesn't* happen on the third / oldest / rescue kernel. There the
>> keyboard keeps working, but then I get 2.5 full screens' worth of
>> dracut-initqueue-timeout errors then it drops me into emergency mode with a
>> "dracut:/#" prompt.
>>
>> I saved a file of the rdsosreport.txt file it makes on a USB, but I don't
>> know what to make of it. (This is where my two months of Linux experience
>> really shows itself.)
>>
>> I type "exit" and it says "Warning: Not all disks have been found.
>> Warning: You might want to regenerate your initramfs." (So maybe initramfs
>> is the problem?) Then it sits after those error messages indefinitely,
>> hours if I let it.
>>
>> In this stage it just waits indefinitely for your input. You should,
>> indeed, regenerate the initramfs.
>>
>>
>> Shockingly it lets me force a reboot with Ctrl-Alt-Del (but I have to
>> press it seven times).
>>
>>
>> > Are you able to uninstall affected kernel(s) and reinstall them.
>> >
>> No — because I can't access internet in recovery mode now for some
>> reason. I tried to download the most recent kernel package I was using on
>> another computer and bring it to the problem machine via USB, but I can't
>> find the .rpm for the kernel I was last using. There are apparently some
>> newer kernels, but I don't want to try to upgrade the kernel while I'm
>> still having so many issues!
>>
>> The kernels from CentOS 8.1 which I presume that you were using ( 8.2 was
>> released 2 days ago ) are now available at
>> http://vault.centos.org/8.1.1911/BaseOS/x86_64/os/Packages/
>>
>>
>>
>>
>>
>> > Are you able to try plugging in a USB keyboard to see if that works.
>> >
>> I don't have a USB keyboard. :(  I'm torn between ordering a USB
>> keyboard to try it out and just reinstalling CentOS 8 and starting from
>> scratch. But I do really, really want to figure out how to fix the issue
>> because I want to better understand Linux and how it interacts with
>> hardware.
>>
>>
>>
>> > To be honest, other than this seems to have been triggered when you
>> > installed the nvidia drivers, this doesn't look like an elrepo issue
>> > and I'm struggling to know what the issue may be or suggest things
>> > that may help.
>> I appreciate your help! No one on the CentOS forums has responded to the
>> issue — I think folks think it's an ELRepo issue. Or they just don't know
>> what to suggest.
>>
>> I'd bet on the last one
>>
>>
>>
>> I *did* come to this mailing list because the keyboard issue appeared
>> immediately after the Nvidia driver install, so at the very least I hoped
>> you might know what in the ELRepo install process might have caused the
>> error.
>>
>> afaik you are the first one to report such an issue. normally the video
>> drivers should not interfere with the kbd. and elrepo does nothing else but
>> repackage in a smarter way the binary drivers provided by Nvidia.
>>
>>
>> — do you think I should try and reinstall my most recent kernel if I can
>> find the .rpm online somewhere?
>>
>> it is certainly worth a shot. You could even boot in rescue mode from a
>> CD or USB stick, chroot to the existing installation and yum [re]install
>> the rpm that already exists in the installation kit.
>>
>>
>> wolfy
>> _______________________________________________
>> elrepo mailing list
>> elrepo at lists.elrepo.org
>> http://lists.elrepo.org/mailman/listinfo/elrepo
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20200623/0818afb4/attachment.html>