<div dir="ltr">Thanks Manuel—<div><br></div><div>One note:</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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.</blockquote>In this stage it just waits indefinitely for your input. You should, indeed, regenerate the initramfs.</blockquote><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div style="color:rgb(0,0,0);font-size:12.8px">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.</div><div style="color:rgb(0,0,0);font-size:12.8px"><br></div><div style="color:rgb(0,0,0);font-size:12.8px">I did go into recovery mode and try to rebuild initramfs for the newest kernel version: "dracut --kver {my kernel version} --force"</div><div style="color:rgb(0,0,0);font-size:12.8px"><br></div><div style="color:rgb(0,0,0);font-size:12.8px">It said it rebuilt the initramfs so I rebooted, but no dice. Still no keyboard input.</div><div style="color:rgb(0,0,0);font-size:12.8px"><br></div><div style="color:rgb(0,0,0);font-size:12.8px"><br>— Jeremy</div></div><div style="color:rgb(0,0,0);font-size:12.8px"><br></div><div style="color:rgb(0,0,0);font-size:12.8px"><br></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 16, 2020 at 6:17 PM Manuel Wolfshant <<a href="mailto:wolfy@nobugconsulting.ro">wolfy@nobugconsulting.ro</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>On 6/17/20 12:40 AM, Jeremy Yocum
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">Thanks everyone for the input!
<div><br>
</div>
<div><span style="color:rgb(80,0,80)">On 6/16/20 7:21 PM, Phil
Perry wrote:</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">> Hi Jeremy,</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">></span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">> Are all kernels
affected?</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">></span></div>
<div><font color="#000000">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.</font></div>
<div><font color="#000000"><br>
</font></div>
<div><font color="#000000">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.</font></div>
<div><font color="#000000"><br>
</font></div>
<div><font color="#000000">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.)</font></div>
<div><span style="color:rgb(0,0,0)"><br>
</span></div>
<div><span style="color:rgb(0,0,0)">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?) </span><span style="color:rgb(0,0,0)">Then it sits after those error
messages indefinitely, hours if I let it.</span></div>
</div>
</div>
</blockquote>
<p>In this stage it just waits indefinitely for your input. You
should, indeed, regenerate the initramfs.<br>
</p>
<p><br>
</p>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div><span style="color:rgb(0,0,0)"> Shockingly it lets me
force a reboot with Ctrl-Alt-Del (but I have to press it
seven times).</span></div>
<div><font color="#000000"><br>
</font></div>
<div><font color="#000000"><br>
</font></div>
<div><span style="color:rgb(80,0,80)">> Are you able to
uninstall affected kernel(s) and reinstall them.</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">></span></div>
<div><font color="#000000">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!</font></div>
</div>
</div>
</blockquote>
<p>The kernels from CentOS 8.1 which I presume that you were using (
8.2 was released 2 days ago ) are now available at
<a href="http://vault.centos.org/8.1.1911/BaseOS/x86_64/os/Packages/" target="_blank">http://vault.centos.org/8.1.1911/BaseOS/x86_64/os/Packages/</a></p>
<p><br>
</p>
<br>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div><font color="#000000"><br>
</font></div>
<div><font color="#000000"><br>
</font></div>
<div><span style="color:rgb(80,0,80)">> Are you able to try
plugging in a USB keyboard to see if that works.</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">></span></div>
<div><font color="#000000">I don't have a USB keyboard. :( </font><span style="color:rgb(0,0,0)">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.</span></div>
<div><span style="color:rgb(0,0,0)"><br>
</span></div>
</div>
</div>
</blockquote>
<br>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div><span style="color:rgb(0,0,0)"><br>
</span></div>
<div><span style="color:rgb(80,0,80)">> To be honest, other
than this seems to have been triggered when you</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">> installed the nvidia
drivers, this doesn't look like an elrepo issue</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">> and I'm struggling to
know what the issue may be or suggest things</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">> that may help.</span></div>
<div><font color="#000000">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.</font></div>
</div>
</div>
</blockquote>
<p>I'd bet on the last one</p>
<p><br>
</p>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div><font color="#000000"><br>
</font></div>
<div><font color="#000000">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.</font></div>
</div>
</div>
</blockquote>
<p>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.<br>
</p>
<p><br>
</p>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div><font color="#000000"> — do you think I should try and
reinstall my most recent kernel if I can find the .rpm
online somewhere?</font></div>
</div>
</div>
</blockquote>
<p>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.</p>
<p><br>
</p>
<p>wolfy<br>
</p>
</div>
_______________________________________________<br>
elrepo mailing list<br>
<a href="mailto:elrepo@lists.elrepo.org" target="_blank">elrepo@lists.elrepo.org</a><br>
<a href="http://lists.elrepo.org/mailman/listinfo/elrepo" rel="noreferrer" target="_blank">http://lists.elrepo.org/mailman/listinfo/elrepo</a><br>
</blockquote></div>