Re: [SOLUTION?] Re: No input devices in wheezy

2011-06-14 Thread Ralf Mardorf
On Mon, 2011-06-13 at 11:10 +0100, AG wrote: > On 12/06/11 19:34, AG wrote: > > My keyboard works fine at the GRUB screen, enabling me to select the > > kernel to boot. However, at gdm3 (and kdm as well now as the > > default), neither mouse nor keyboard works. > > > > Doing a hard reboot, I can

Re: No input devices in wheezy

2011-06-13 Thread AG
On 14/06/11 01:02, Wolodja Wentland wrote: On Sun, Jun 12, 2011 at 19:34 +0100, AG wrote: My keyboard works fine at the GRUB screen, enabling me to select the kernel to boot. However, at gdm3 (and kdm as well now as the default), neither mouse nor keyboard works. Hi Wolodja Quite likely due

Re: No input devices in wheezy

2011-06-13 Thread Wolodja Wentland
On Sun, Jun 12, 2011 at 19:34 +0100, AG wrote: > My keyboard works fine at the GRUB screen, enabling me to select the > kernel to boot. However, at gdm3 (and kdm as well now as the > default), neither mouse nor keyboard works. Quite likely due to the /run + udev + initscripts transition that is s

Re: [SOLUTION?] Re: No input devices in wheezy

2011-06-13 Thread Brian
On Mon 13 Jun 2011 at 11:59:46 +0100, AG wrote: > Just to be clear then, this will hold back the two udev* packages from > being updated? Yes. > At some point, I'm assuming the udev maintainer will fix the problems in > the udev_170-1 so how will I reverse this hold so that I can later > u

Re: [SOLUTION?] Re: No input devices in wheezy

2011-06-13 Thread AG
On 13/06/11 11:41, Brian wrote: On Mon 13 Jun 2011 at 11:10:51 +0100, AG wrote: The problem is now resolved. However, the Update Manager wants to upgrade these two files to 170-1. Is there anyway to stop this from happening, or do I manually deselect these when it is time to update? echo "

Re: [SOLUTION?] Re: No input devices in wheezy

2011-06-13 Thread Brian
On Mon 13 Jun 2011 at 11:10:51 +0100, AG wrote: > The problem is now resolved. However, the Update Manager wants to > upgrade these two files to 170-1. Is there anyway to stop this from > happening, or do I manually deselect these when it is time to update? echo " hold" | dpkg --set-selecti

[SOLUTION?] Re: No input devices in wheezy

2011-06-13 Thread AG
On 12/06/11 19:34, AG wrote: My keyboard works fine at the GRUB screen, enabling me to select the kernel to boot. However, at gdm3 (and kdm as well now as the default), neither mouse nor keyboard works. Doing a hard reboot, I can boot into recovery mode and from there startx and as root, key

Re: No input devices in wheezy +additional info #2

2011-06-13 Thread AG
On 12/06/11 20:37, AG wrote: On 12/06/11 19:34, AG wrote: My keyboard works fine at the GRUB screen, enabling me to select the kernel to boot. However, at gdm3 (and kdm as well now as the default), neither mouse nor keyboard works. Doing a hard reboot, I can boot into recovery mode and from

Re: No input devices in wheezy +additional info

2011-06-12 Thread AG
On 12/06/11 19:34, AG wrote: My keyboard works fine at the GRUB screen, enabling me to select the kernel to boot. However, at gdm3 (and kdm as well now as the default), neither mouse nor keyboard works. Doing a hard reboot, I can boot into recovery mode and from there startx and as root, key

No input devices in wheezy

2011-06-12 Thread AG
My keyboard works fine at the GRUB screen, enabling me to select the kernel to boot. However, at gdm3 (and kdm as well now as the default), neither mouse nor keyboard works. Doing a hard reboot, I can boot into recovery mode and from there startx and as root, keyboard and mouse work fine. Bu