How to boot to emergency.target and have a functional USB keyboard?

graysky · 2012-10-25 00:40:59

I appending systemd.unit=emergency.target to my kernel line in GRUB while booting so I could manually do an e2fsck. I was unable to enter my password; my USB keyboard was not activate. Seems like systemd didn't load a module or something. Thoughts?

ataraxia · 2012-10-25 00:49:06

Do you have the usbinput hook in mkinitcpio.conf? That will make the initrd load the needed modules, such that it'll be done before systemd even starts. This was already needed to prevent a similar problem if you are dropped to the ramfs shell.

graysky · 2012-10-25 00:54:13

@ataraxia

% sed '/#/d' /etc/mkinitcpio.conf
MODULES="i915 ahci sd_mod ext4"
BINARIES="fsck fsck.ext4"
FILES=""
HOOKS="base consolefont usbinput"
COMPRESSION="lzop"

epinephrine · 2012-10-25 13:34:34

This could be related to the problem I discussed here. You're lucky, my system simply ignores systemd.unit=rescue.target, haven't tried out emergency.target yet though.
EDIT:woops, fixed it. I have /boot on a different partition, which wasn't mounted while upgrading kmod and linux. chrooting into the system and reinstalling the packages WHILE /boot is mounted fixed it... Poker face

Last edited by epinephrine (2012-10-25 15:13:00)

ataraxia · 2012-10-25 15:31:43

graysky wrote:

@ataraxia

% sed '/#/d' /etc/mkinitcpio.conf
MODULES="i915 ahci sd_mod ext4"
BINARIES="fsck fsck.ext4"
FILES=""
HOOKS="base consolefont usbinput"
COMPRESSION="lzop"

You don't have the udev hook, so none of the modules included by usbinput are actually getting loaded. Figure out the module your keyboard needs (probably just hid-generic) and add it to MODULES.

graysky · 2012-10-25 18:47:50

ataraxia wrote:

You don't have the udev hook, so none of the modules included by usbinput are actually getting loaded. Figure out the module your keyboard needs (probably just hid-generic) and add it to MODULES.

Good observation.

% lsmod | grep usb
usbhid                 36996  0 
hid                    85641  3 hid_generic,hid_microsoft,usbhid
usbcore               149715  3 ehci_hcd,usbhid,xhci_hcd
usb_common               954  1 usbcore

I will add these 4 and see if it works.

EDIT: Nope

% grep MODULES= /etc/mkinitcpio.conf
MODULES="i915 ahci sd_mod ext4 usbhid usbcore usb_common hid"

Last edited by graysky (2012-10-25 18:52:47)

ataraxia · 2012-10-25 18:52:56

graysky wrote:

ataraxia wrote:
You don't have the udev hook, so none of the modules included by usbinput are actually getting loaded. Figure out the module your keyboard needs (probably just hid-generic) and add it to MODULES.
Good observation.
% lsmod | grep usb
usbhid                 36996  0 
hid                    85641  3 hid_generic,hid_microsoft,usbhid
usbcore               149715  3 ehci_hcd,usbhid,xhci_hcd
usb_common               954  1 usbcore
I will add these 4 and see if it works.

Add hid-generic as well - that's the top-level module for this functionality.

Potomac · 2012-10-26 12:50:03

graysky wrote:

I appending systemd.unit=emergency.target to my kernel line in GRUB while booting so I could manually do an e2fsck. I was unable to enter my password; my USB keyboard was not activate. Seems like systemd didn't load a module or something. Thoughts?

check if the option "Legacy USB Support " in your bios is set to "enabled"

graysky · 2012-10-26 18:59:07

@ata - Still no go.

MODULES="i915 ahci sd_mod ext4 hid-generic hid_microsoft usbhid usbcore usb_common hid"

F*ck it. I'll just add the damn udev hook (which DOES work).

@Potomac - It is, thanks for the suggestion.

Last edited by graysky (2012-10-26 18:59:27)

rutgerr · 2012-10-26 22:36:42

graysky wrote:

@ata - Still no go.
MODULES="i915 ahci sd_mod ext4 hid-generic hid_microsoft usbhid usbcore usb_common hid"
F*ck it. I'll just add the damn udev hook (which DOES work).
@Potomac - It is, thanks for the suggestion.

this:

HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck timestamp"

works fine for me all my keyboards are usb / wireless

WonderWoofy · 2012-10-27 04:30:24

graysky, I wonder if you might be able to diff the output of lsinitcpio of your old initramfs and your new one with the udev hook. I am curious as to what it actually added in terms of keyboard input. I believe my system uses evdev and psmouse, as I have a thinkpad, so it would ceratinly be different. But I am just curious.

ZekeSulastin · 2012-10-27 06:40:47

graysky wrote:

MODULES="i915 ahci sd_mod ext4 hid-generic hid_microsoft usbhid usbcore usb_common hid"
                                  ^

Out of curiosity's sake, was that typo originally in your mkinitcpio.conf or was it introduced in the copy? That might be why it didn't work

graysky · 2012-10-27 09:47:01

ZekeSulastin wrote:

graysky wrote:
MODULES="i915 ahci sd_mod ext4 hid-generic hid_microsoft usbhid usbcore usb_common hid"
                                  ^
Out of curiosity's sake, was that typo originally in your mkinitcpio.conf or was it introduced in the copy? That might be why it didn't work

I do not understand what you are claiming is a typo?

1: MODULES="i915 ahci sd_mod ext4"
2: MODULES="i915 ahci sd_mod ext4 hid-generic hid_microsoft usbhid usbcore usb_common hid"

illusionist · 2012-10-27 10:11:34

@graysky
try

ata_piix

Strike0 · 2012-10-27 13:56:10

graysky wrote:

I do not understand what you are claiming is a typo?

1: MODULES="i915 ahci sd_mod ext4"
2: MODULES="i915 ahci sd_mod ext4 hid-generic hid_microsoft usbhid usbcore usb_common hid"

ZekeSulastin was referring to your spelling of "hid_generic".

graysky · 2012-10-27 14:32:09

@Strike0 - I get it... hyphen instead of underscore. I modded it, rebooted and still no keyboard. Thanks tough.

% grep MODULES= /etc/mkinitcpio.conf
MODULES="i915 ahci sd_mod ext4 hid_generic hid_microsoft usbhid usbcore usb_common hid"

falconindy · 2012-10-27 15:27:17

dashes and underscores are interchangeable. kmod tools ignore the difference, and I've extended that to mkinitcpio as well. It makes no difference whether your modules array contains ata-piix or ata_piix. If it did, mkinitcpio would have thrown an error.

This also should have nothing to do with the initramfs. If you want a functional keyboard, use rescue.target instead, and udev will run in userspace before dropping you into the shell. emergency.target interrupts bootup sooner.

Last edited by falconindy (2012-10-27 15:33:00)

Arch Linux

#1 2012-10-25 00:40:59

How to boot to emergency.target and have a functional USB keyboard?

#2 2012-10-25 00:49:06

Re: How to boot to emergency.target and have a functional USB keyboard?

#3 2012-10-25 00:54:13

Re: How to boot to emergency.target and have a functional USB keyboard?

#4 2012-10-25 13:34:34

Re: How to boot to emergency.target and have a functional USB keyboard?

#5 2012-10-25 15:31:43

Re: How to boot to emergency.target and have a functional USB keyboard?

#6 2012-10-25 18:47:50

Re: How to boot to emergency.target and have a functional USB keyboard?

#7 2012-10-25 18:52:56

Re: How to boot to emergency.target and have a functional USB keyboard?

#8 2012-10-26 12:50:03

Re: How to boot to emergency.target and have a functional USB keyboard?

#9 2012-10-26 18:59:07

Re: How to boot to emergency.target and have a functional USB keyboard?

#10 2012-10-26 22:36:42

Re: How to boot to emergency.target and have a functional USB keyboard?

#11 2012-10-27 04:30:24

Re: How to boot to emergency.target and have a functional USB keyboard?

#12 2012-10-27 06:40:47

Re: How to boot to emergency.target and have a functional USB keyboard?

#13 2012-10-27 09:47:01

Re: How to boot to emergency.target and have a functional USB keyboard?

#14 2012-10-27 10:11:34

Re: How to boot to emergency.target and have a functional USB keyboard?

#15 2012-10-27 13:56:10

Re: How to boot to emergency.target and have a functional USB keyboard?

#16 2012-10-27 14:32:09

Re: How to boot to emergency.target and have a functional USB keyboard?

#17 2012-10-27 15:27:17

Re: How to boot to emergency.target and have a functional USB keyboard?

Board footer