Bug#633343: Bug#633441: Lost keyboard - workaround found -- calling udevadm trigger

2011-08-02 Thread Helge Kreutzmann
tag 633441 + unreproducible tag 633343 + unreproducible thanks Hello, I finally managed to boot into an early shell as described in the documentation for udev (see below for how to achive this with grub2) just to see - nothing. I then commented out the udevadm trigger command, and the keyboard

Bug#633441: Lost keyboard - workaround found -- calling udevadm trigger

2011-07-18 Thread Marco d'Itri
On Jul 16, Helge Kreutzmann deb...@helgefjell.de wrote: No. I don't see any error message and as told my attempt to convince grub2 to boot single user was unsucessful (maybe I read the grub2 documentation wrong, I had to stich it together myself). Then you need to ask for help on your

Bug#633441: Lost keyboard - workaround found -- calling udevadm trigger

2011-07-16 Thread Helge Kreutzmann
Hello Marco, On Fri, Jul 15, 2011 at 11:54:12PM +0200, Marco d'Itri wrote: On Jul 12, Marco d'Itri m...@linux.it wrote: I did. I could not find anything specific. I tried booting into single user mode as described but given that I use lvm, this is non trivial (I ended up in a kernel

Bug#633441: Lost keyboard - workaround found -- calling udevadm trigger

2011-07-15 Thread Marco d'Itri
On Jul 12, Marco d'Itri m...@linux.it wrote: I did. I could not find anything specific. I tried booting into single user mode as described but given that I use lvm, this is non trivial (I ended up in a kernel panic because no further partition could be found). If you boot with

Bug#633343: Bug#633441: Lost keyboard - workaround found -- calling udevadm trigger

2011-07-12 Thread Helge Kreutzmann
Hello, On Sun, Jul 10, 2011 at 03:01:04PM +0200, Marco d'Itri wrote: On Jul 10, Helge Kreutzmann deb...@helgefjell.de wrote: Could that be because I have EFI (AFAIK) and not a traditional BIOS? No. This probably happens because the udev init script failed. Again, you need to find out why.

Bug#633343: Bug#633441: Lost keyboard - workaround found -- calling udevadm trigger

2011-07-12 Thread Marco d'Itri
On Jul 12, Helge Kreutzmann deb...@helgefjell.de wrote: I did. I could not find anything specific. I tried booting into single user mode as described but given that I use lvm, this is non trivial (I ended up in a kernel panic because no further partition could be found). If you boot with

Bug#633343: Bug#633441: Lost keyboard - workaround found -- calling udevadm trigger

2011-07-10 Thread Marco d'Itri
On Jul 10, Helge Kreutzmann deb...@helgefjell.de wrote: Could that be because I have EFI (AFAIK) and not a traditional BIOS? No. This probably happens because the udev init script failed. Again, you need to find out why. Watch closely the boot process. Also, read README.Debian. -- ciao, Marco