Keyboard stops working at login prompt, can't log in

creemy0cheesekake · 2022-08-14 21:40:38

Ever since an update on around the 4th of August, whenever I boot into Arch, I can't type anything. The little LED indicators on the num lock and caps lock keys are unresponsive, so I'm pretty sure my keyboard isn't working. It works fine at the GRUB menu though, and also works in (disgusting) Windows so the hardware is not an issue. It also works when booting into a live USB. I've tried downgrading all my packages to no avail. Everything looks completely normal until the keyboard just stops working. If you need any more information, I'd be happy to provide it to you.

seth · 2022-08-15 06:32:06

What keyboard? Internal notebook one? USB? Bluetooth?
Do you have a second one (in particular a USB one if the malfunctioning is the internal one of a notebook)?

We'll need a system journal from a bad boot, the problem is that you must not exit that boot w/ the HW power button or the journal won't be preserved.
=> You either need a functional (external?) keyboard or the ability to ssh into the system to conduct an orderly shutdown.

also works in … Windows

3rd link below, mandatory.
(Edit: no, that is not the fast boot setting in your BIOS)

Last edited by seth (2022-08-15 06:32:37)

creemy0cheesekake · 2022-08-15 22:50:38

seth wrote:

What keyboard? Internal notebook one? USB? Bluetooth?

All of the above

seth wrote:

Do you have a second one (in particular a USB one if the malfunctioning is the internal one of a notebook)?

Yes

seth wrote:

We'll need a system journal from a bad boot, the problem is that you must not exit that boot w/ the HW power button or the journal won't be preserved.
=> You either need a functional (external?) keyboard or the ability to ssh into the system to conduct an orderly shutdown.

I'm sorry, could you explain how to do that?

seth wrote:

3rd link below, mandatory.
(Edit: no, that is not the fast boot setting in your BIOS)

Thanks, I just did that

Last edited by creemy0cheesekake (2022-08-15 22:54:19)

seth · 2022-08-16 06:06:41

I'm sorry, could you explain how to do that?

https://wiki.archlinux.org/title/OpenSSH - you can setup that from a chroot.

Sanity check: the mouse/touchpad still works when the keyboard is non-responsive?
ctrl+alt+f1,2,3,… don't work either?

creemy0cheesekake · 2022-08-16 21:12:05

seth wrote:

I'm sorry, could you explain how to do that?
https://wiki.archlinux.org/title/OpenSSH - you can setup that from a chroot.

Thanks!

seth wrote:

Sanity check: the mouse/touchpad still works when the keyboard is non-responsive?
ctrl+alt+f1,2,3,… don't work either?

idk about the mouse/touchpad because I'm not using a GUI dm, so the cursor doesn't show up

No, I can't switch TTYs either.

creemy0cheesekake · 2022-08-17 04:04:04

When I try to SSH into the system from WSL on windows, I get this:

ssh: connect to host 192.168.86.68 port 22: No route to host

I'm assuming that means the system has to be on when I do so? If so how do I do this with only one device?

cfr · 2022-08-17 04:15:12

creemy0cheesekake wrote:

I'm assuming that means the system has to be on when I do so? If so how do I do this with only one device?

The system needs to be on and the ssh server has to be listening and reachable.
Do you have a phone or tablet, maybe, which can use `ssh`? I know there are apps for Android. Otherwise, can you borrow a device from somebody or use one in school/work/other?

seth · 2022-08-17 06:41:43

idk about the mouse/touchpad because I'm not using a GUI dm, so the cursor doesn't show up

Is the getty cursor blinking?
You can btw. have a mouse cursor on the console, https://wiki.archlinux.org/title/General_purpose_mouse

creemy0cheesekake · 2022-08-17 22:19:01

seth wrote:

You can btw. have a mouse cursor on the console, https://wiki.archlinux.org/title/General_purpose_mouse

Well I can't really do this without booting into the system, right?

seth wrote:

Is the getty cursor blinking?

Yes

creemy0cheesekake · 2022-08-18 04:00:59

cfr wrote:

Do you have a phone or tablet, maybe, which can use `ssh`? I know there are apps for Android.

I tried using some android apps, I tried multiple different ones, but for every single one when it asks for my system password, it just keeps asking over and over again and I can't figure out why

seth · 2022-08-18 06:37:28

Well I can't really do this without booting into the system, right?

You can, offline: https://wiki.archlinux.org/title/Pacman … an_upgrade (ignore the context)

when it asks for my system password, it just keeps asking over and over again

Did you enable the sshd.service on the target system?

Can you boot the fallback initramfs? The rescue target?
https://wiki.archlinux.org/title/Kernel_parameters - "systemd.unit=rescue.target nomodeset"

If neither you could seek to enable autologin, https://wiki.archlinux.org/title/Getty# … al_console as root and in your /root/.bash_profile

sleep 5; journalctl -b | curl -F 'file=@-' 0x0.st

(you'll have to do all of this from a different system, eg. the install iso - if you're not chrooting in, don't forget that the paths would be sth. like /mnt/root/.bash_profile if you mounted the root of the installed system to /mnt)

Ideally, this would automatically log in after the next boot, sleep 5 seconds to maybe settle some stuff and then upload the system journal and print a url where to find it.
We will need *some* data on the system to make any comment beyond blind guessing.

creemy0cheesekake · 2022-08-19 03:06:15

seth wrote:

Did you enable the sshd.service on the target system?

Inside chroot it says

Running in chroot, ignoring command 'start'

when trying to start any service. I did

/usr/sbin/sshd -D &

, but I don't know if that's the problem

seth · 2022-08-19 06:28:05

"enable", not "start" - whatever service you start or process you run inside that chroot won't have any impact on the next boot anyway.

creemy0cheesekake · 2022-08-20 18:45:14

Ok, at this point I'm fairly certain that it's a kernel issue. Even after

# pacman -Syu

the linux-lts version 5.15.58-2 kernel is being used even though that's not the latest version. When I did the full system upgrade, it showed the linux-lts kernel being upgraded to version 5.15.61-2, however it's not being used. I even tried uninstalling linux-lts to use the linux package as the kernel but it's still using linux-lts version 5.15.58-2 kernel which makes no sense because I uninstalled it. How do I fix this?

seth · 2022-08-20 19:35:56

cat /proc/cmdline
lsblk -f
mount

You either forgot to mount the /boot partition (or mount the wrong partition) and installed the kernel onto the root partition or you mounted the /boot partition but are actually booting from the root partition.

creemy0cheesekake · 2022-08-21 00:20:34

Ok I can finally log in now! I'm so happy to be back on Arch again! However my issue isn't solved yet. You were right, the reason I was still on the old kernel was because I didn't mount my /boot partition. I guess that means the kernel was the issue, which is a bit concerning.

However, after doing a system upgrade after mounting it, I ran into the same issue I did the day this all started, which was that it hangs before even reaching the login prompt (I did some things, which I don't exactly remember, which made me have a different issue). I downgraded all my packages and that fixed the issue, but now some things are messed up such as Firefox telling me that I've used a newer version of Firefox in the past and I shouldn't be using this version now, so I still need to get my system back to the latest version. What should I do now?

cfr · 2022-08-21 01:08:59

You probably didn't get a new kernel (linux or linux-lts) when you upgraded, which will have done nothing to change their not getting installed onto the /boot partition.
You can also do

file /boot/vmlinuz-linux

or

file /boot/vmlinuz-linux-lts

to check the versions with your boot partition mounted and compare that with

pacman -Qi linux
pacman -Qi linux-lts

to ensure the versions match. If you booted with older files on /boot, that would mess things up quite considerably.

After mounting the boot partition

pacman -Syu linux linux-lts

would update the system and trigger the scripts to get the right stuff on /boot, even if the kernel packages are already up to date.

creemy0cheesekake · 2022-08-21 02:15:46

cfr wrote:

After mounting the boot partition
pacman -Syu linux linux-lts
would update the system and trigger the scripts to get the right stuff on /boot, even if the kernel packages are already up to date.

Yes, thank you, I figured that out and that works. However the issue I mentioned in the previous reply is still present.

cfr · 2022-08-21 03:49:51

creemy0cheesekake wrote:

Yes, thank you, I figured that out and that works. However the issue I mentioned in the previous reply is still present.

If you mean that when you boot a properly updated system you again can't use the keyboard when you boot, you need to get the data from a boot where this happens using one of the methods seth described above.

creemy0cheesekake · 2022-08-21 04:01:36

cfr wrote:

creemy0cheesekake wrote:
Yes, thank you, I figured that out and that works. However the issue I mentioned in the previous reply is still present.
If you mean that when you boot a properly updated system you again can't use the keyboard when you boot, you need to get the data from a boot where this happens using one of the methods seth described above.

When I "boot" a properly updated system, I can't boot.

creemy0cheesekake wrote:

... which was that it hangs before even reaching the login prompt

seth · 2022-08-21 06:01:31

Which is not the subject of this thread, though.
Can you boot the multi-user.target (2nd link below) w/ the "nomodeset" parameter?
Post a journal from a current (working) boot to get us *some* idea about the system, then update and try to boot the multi-user.target

If not, we'll need a quantification of "it hangs before even reaching the login prompt" - make sure to remove the "quiet" kernel parameter to get a more fine-grained state feedback.

In any event, report your findings in a new thread that subjects the issue at hand and mark this one (I understand the keyboard issue was a result of the botched downgrade?) as solved.

creemy0cheesekake · 2022-08-24 03:29:48

seth wrote:

Which is not the subject of this thread, though.
Can you boot the multi-user.target (2nd link below) w/ the "nomodeset" parameter?
Post a journal from a current (working) boot to get us *some* idea about the system, then update and try to boot the multi-user.target
If not, we'll need a quantification of "it hangs before even reaching the login prompt" - make sure to remove the "quiet" kernel parameter to get a more fine-grained state feedback.
In any event, report your findings in a new thread that subjects the issue at hand and mark this one (I understand the keyboard issue was a result of the botched downgrade?) as solved.

Ok, actually I'm able to boot in, execept I can't start an x server and NetworkManger doesnt detect my wifi card (however iwctl on a live usb does). I still think its the same issue though, because even after upgrading back to latest while booted in the system, the old kernel is still being used. Running df gives this:

$ df
Filesystem     1K-blocks      Used Available Use% Mounted on
dev              8062088         0   8062088   0% /dev
run              8070252      1520   8068732   1% /run
/dev/nvme0n1p9 480209544 218127380 237615428  48% /
tmpfs            8070252     63628   8006624   1% /dev/shm
tmpfs            8070252     12804   8057448   1% /tmp
tmpfs            1614048        16   1614032   1% /run/user/1000

As you can see, it doesn't list the /boot partition being mounted. I think that's the issue. How do I fix that, and if it's not being mounted, how can I boot into the system? I thought the /boot partition was used for that?

seth · 2022-08-24 06:26:20

This doesn't even say whether you *have* a boot partition.
https://bbs.archlinux.org/viewtopic.php … 9#p2052839 to illustrate the state of your system.

creemy0cheesekake · 2022-08-25 00:30:33

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 9#p2052839 to illustrate the state of your system.

$ cat /proc/cmdline                                                                                                                                                                                          I
BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=70cf9436-0c39-4655-8b55-6ce4dcdea958 rw loglevel=3
 $ lsblk -f                                                                                                                                                                                                   I
NAME        FSTYPE FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda
nvme0n1
├─nvme0n1p1 vfat   FAT32 ESP         1E27-31E3
├─nvme0n1p2
├─nvme0n1p3 ntfs         OS          3C3445033444C19E
├─nvme0n1p4 ntfs         WINRETOOLS  34327A9C327A6332
├─nvme0n1p5 ntfs         Image       4ED07AACD07A9A43
├─nvme0n1p6 ntfs         DELLSUPPORT 685C26805C2648E0
├─nvme0n1p7 vfat   FAT32             3FFB-F171
├─nvme0n1p8 swap   1                 eda73507-6f5a-41dd-8785-59c37d543bb8
└─nvme0n1p9 ext4   1.0               70cf9436-0c39-4655-8b55-6ce4dcdea958  225.9G    46% /
 $mount                                                                                                                                                                                                      I
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8062088k,nr_inodes=2015522,mode=755,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p9 on / type ext4 (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14127)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=1048576,inode64)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
none on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1614048k,nr_inodes=403512,mode=700,uid=1000,gid=1000,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

/dev/nvme0n1p7 should be my boot partition

Last edited by creemy0cheesekake (2022-08-25 00:31:21)

seth · 2022-08-25 06:11:05

You're NOT booting from the root partition, so you should have the /boot partition (and nvme0n1p7 is a contender) mounted there at least whenever updating the kernel and/or the bootloader)
What's the output of

ls -R /boot
sudo mount /dev/nvme0n1p7 /boot
ls -R /boot

There's likely a vmlinuz-linux* in either case and you can

file /boot/vmlinuz-linux*

to inspect the version of those kernel files.

Arch Linux

#1 2022-08-14 21:40:38

Keyboard stops working at login prompt, can't log in

#2 2022-08-15 06:32:06

Re: Keyboard stops working at login prompt, can't log in

#3 2022-08-15 22:50:38

Re: Keyboard stops working at login prompt, can't log in

#4 2022-08-16 06:06:41

Re: Keyboard stops working at login prompt, can't log in

#5 2022-08-16 21:12:05

Re: Keyboard stops working at login prompt, can't log in

#6 2022-08-17 04:04:04

Re: Keyboard stops working at login prompt, can't log in

#7 2022-08-17 04:15:12

Re: Keyboard stops working at login prompt, can't log in

#8 2022-08-17 06:41:43

Re: Keyboard stops working at login prompt, can't log in

#9 2022-08-17 22:19:01

Re: Keyboard stops working at login prompt, can't log in

#10 2022-08-18 04:00:59

Re: Keyboard stops working at login prompt, can't log in

#11 2022-08-18 06:37:28

Re: Keyboard stops working at login prompt, can't log in

#12 2022-08-19 03:06:15

Re: Keyboard stops working at login prompt, can't log in

#13 2022-08-19 06:28:05

Re: Keyboard stops working at login prompt, can't log in

#14 2022-08-20 18:45:14

Re: Keyboard stops working at login prompt, can't log in

#15 2022-08-20 19:35:56

Re: Keyboard stops working at login prompt, can't log in

#16 2022-08-21 00:20:34

Re: Keyboard stops working at login prompt, can't log in

#17 2022-08-21 01:08:59

Re: Keyboard stops working at login prompt, can't log in

#18 2022-08-21 02:15:46

Re: Keyboard stops working at login prompt, can't log in

#19 2022-08-21 03:49:51

Re: Keyboard stops working at login prompt, can't log in

#20 2022-08-21 04:01:36

Re: Keyboard stops working at login prompt, can't log in

#21 2022-08-21 06:01:31

Re: Keyboard stops working at login prompt, can't log in

#22 2022-08-24 03:29:48

Re: Keyboard stops working at login prompt, can't log in

#23 2022-08-24 06:26:20

Re: Keyboard stops working at login prompt, can't log in

#24 2022-08-25 00:30:33

Re: Keyboard stops working at login prompt, can't log in

#25 2022-08-25 06:11:05

Re: Keyboard stops working at login prompt, can't log in

Board footer