Re: PS2 Keyboard not working after latest update
- To: debian-user@lists.debian.org
- Subject: Re: PS2 Keyboard not working after latest update
- From: Roger Leigh <rleigh@codelibre.net>
- Date: Mon, 2 Jul 2012 14:20:25 +0100
- Message-id: <[🔎] 20120702132025.GC4080@codelibre.net>
- In-reply-to: <CAD3_CNPnyHPezqBOjt_nfF7wx4tcn6RT1DnU2WQPjW6dZGLK7g@mail.gmail.com>
- References: <4FEC7883.5020901@googlemail.com> <20120629031842.GT4141@tal> <CAD3_CNPnyHPezqBOjt_nfF7wx4tcn6RT1DnU2WQPjW6dZGLK7g@mail.gmail.com>
On Fri, Jun 29, 2012 at 09:43:56AM +0100, James Allsopp wrote:
> Tried both of those but nothing. I have a theory that it might be a Udev
> problem, but can't be certain. Does anyone have any ideas why a problem
> like that might arise?
Yes, if something removes the udev state in /dev/.udev (or /run/udev
on wheezy or sid) then the input device autodetection won't work
when X starts up.
If you have a USB (NOT PS/2) keyboard/mouse, try unplugging and then
plug back in--hotplugging should result in autodetection of the new
input devices.
If you're running wheezy/unstable, and /run is a symlink to /var/run,
your system is broken (/run should not be a symlink), and you should
try the packages at
http://people.debian.org/~rleigh/sysvinit/
which fix the problem (they'll be uploaded soon).
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
Reply to: