Bug 785603

This is similar to bug #775669

As can be seen from the mkinitrd output, the -desktop flavor gets (among others)

ohci-hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid

whereas the -xen flavor out of these only gets xhci-hcd. Why this is (or how to get mkinitrd to produce sufficiently verbose output to determine the reason) needs to be looked at (suggested by) a mkinitrd person.

(In reply to comment #1)
> This is similar to bug #775669

I'm not sure - there the ?hci-hcd modules all appear to be present.

(In reply to comment #2)
> As can be seen from the mkinitrd output, the -desktop flavor gets (among
> others)
> 
> ohci-hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid
> 
> whereas the -xen flavor out of these only gets xhci-hcd. Why this is (or how to
> get mkinitrd to produce sufficiently verbose output to determine the reason)
> needs to be looked at (suggested by) a mkinitrd person.

Michal Marek owns the mkinitrd package.
Perhaps he can answer this question.

Long time no response.So closed. Feel free to reopen it.Thanks:)

Since the bug is still present and breaks Xen on OpenSUSE with encrypted LVM, I am reopening this bug.

The -xen flavor *does* have ohci-hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid. Scroll your window to the left when viewing http://bugzillafiles.novell.org/attachment.cgi?id=509955

The missing module is hid-generic, which is listed in the /lib/mkinitrd/scripts/boot-usb.sh script but which can't be found and is not included.

Weird mkinitrd behavior #1, probably not related: modprobe gives the error "Module hid_generic not found" for *both* the -desktop and -xen flavors, but the USB keyboard only fails to be active when booting the Xen kernel. I can unlock the encrypted LVM just fine when booting the -desktop kernel.

Weird mkinitrd behavior #2, probably not related: The /lib/mkinitrd/scripts/boot-usb.sh script lists ohci_hcd and ehci_hcd (names with underscores), mkinitrd shows ohci-hcd and ehci-hcd as successfully included modules (names with dashes). They're included in both the -desktop and -xen flavors, so it appears to work, but seems odd that the names don't match.

Possibly relevant clue: When booting -desktop, I get a graphical screen with a prompt for the passphrase to unlock the LVM. When booting -xen, I get textmode (no graphics) and when I get the text prompt to unlock the LVM, my keyboard does nothing.



(In reply to comment #2)
> As can be seen from the mkinitrd output, the -desktop flavor gets (among
> others)
> 
> ohci-hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid
> 
> whereas the -xen flavor out of these only gets xhci-hcd. Why this is (or how to
> get mkinitrd to produce sufficiently verbose output to determine the reason)
> needs to be looked at (suggested by) a mkinitrd person.
> 
> (In reply to comment #1)
> > This is similar to bug #775669
> 
> I'm not sure - there the ?hci-hcd modules all appear to be present.

(In reply to comment #6)
> The -xen flavor *does* have ohci-hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid.
> Scroll your window to the left when viewing
> http://bugzillafiles.novell.org/attachment.cgi?id=509955

Yeah, sorry, it's the -desktop flavor that only gets xhci-hcd ([uoe]hci-hcd are all built in there).

> The missing module is hid-generic, which is listed in the
> /lib/mkinitrd/scripts/boot-usb.sh script but which can't be found and is not
> included.

As mentioned elsewhere (perhaps in the referenced bug): 3.4 simply doesn't have such a module, it got introduced in 3.5 only.

> Possibly relevant clue: When booting -desktop, I get a graphical screen with a
> prompt for the passphrase to unlock the LVM. When booting -xen, I get textmode
> (no graphics) and when I get the text prompt to unlock the LVM, my keyboard
> does nothing.

So why don't you make Xen match (by passing "vga=mode-<number>" to the hypervisor, with <number> matching the value passed via "vga=" to the native kernel)?

In my testing the keyboard appears to be dead when plymouth asks for password.
However, shortly before it starts I can press space and see the cursor move. So overall the usbkbd works in initrd. For some reason kernel-xen does not display the 'ask for passphrase' screen as splash screen, instead it is displayed in textmode (not vga mode!), while kernel-desktop shows the splashscreen.
I will dig into it further.

booting with 'rd.plymouth=0' solves the "dead keyboard".

Issue #1: the plymouth textmode is broken.
Issue #2: plymouth does not display splash with kernel-xen in dom0, even with a working console DRM driver (radeondrmfb).

Therefor I reassing it to the plymouth maintainer, not a Xen issue.

Olaf, 

Can you provide me with the following :

output of the lsinitrd command for the initrd used by the kernel-xen

Created attachment 514440 [details]
bug785603-lsinitrd-l-initrd-xen.txt

lsinitrd -l initrd-xen, its identical to initrd-desktop

Note that rd.plymouth=0 will disable splash in initrd with kernel-desktop, but once booting proceeds in real root, the splash screen is shown. This does not happen with kernel-xen, no splash screen shown.
Somehow plymouth can not deal with kernel-xen.

Olaf: I can confirm that the work-around of adding "rd.plymouth=0" to the Xen module line in /boot/grub2/grub.cfg allowed me to type in the password for my LVM and boot with the Xen kernel. The boot sequence is in text mode, not graphical.

Jan: the video mode is set to "video=1680x1050" for all of the boot options in my grub.cfg file and has been since I started this thread. I was using the OpenSUSE setup for Grub without making any manual changes. The first manual change I made was adding "rd.plymouth=0".

Don't know what "video=" option you're talking about - I outlined above how the correct mode setting options would look like.

Is this still a valid bug ?

Closing