im usiing a custom kernel, but ive also tried the 2.6.29-2-amd64 from debian repos and i get the same results. i also have tried single user mode with the same result . i also tried debian-live 64bit rescue image (on usb) which boots to console, and i have no keyboard their either. however with a debian-live with which boots X keyboard works fine. i can change to console with cntrl-alt-f1 and keyboard does work.
i just instaled a new kernel, linux-image-2.6.32-trunk-amd64 from sid, to see what happens with initramfs on the new kernel. on install i get the following errors. the "invalid line in /etc/cryptab -" has always appeared but not caused any harm. the grub-probe error may be related to the chroot, however should be noted that ls /dev shows that its full of devices. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-amd64 W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169 cryptsetup: WARNING: invalid line in /etc/crypttab - cryptsetup: WARNING: invalid line in /etc/crypttab - Running update-grub. /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). On Tue, Jan 26, 2010 at 11:27 PM, Ian B. MacDonald <i...@ianbmacdonald.com> wrote: > Hmm. On detection seems even stranger > About that point udev is doing its work; have you made and changes wrt > udev rules or installed any packages that might introduce new rules i updated my system, but it powered down, battery ran out of juice. it was an aptitude safe-upgrade but im not sure what all packets got updated. have not touched udev rules. the next time i booted is when i could no longer login. > The delay change (passphrase vs detection) on the hang makes me think that > device detection is involved > More details on kernel and package versions might be helpful initramfs-tools=0.93.4 grub=0.97-59 udev=150-2 > Running memtest to ensure you are not up aainst some dying hardware might > not be a bad idea > In any event it seems strange; > Is it safe to say this happens in single user mode too? yes > Hard to debug at that stage; I may be out of ideas. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
