wheezy network install on laptop no keyboard or mouse

[lambcutlet]

hi,
i am new to debian, although i have been using fedora for a numbers of years, just fancied trying something different.
anyway the reason for my post
i downloaded a network install of wheezy
partitioned and loaded wheezy on to a dell latitude d600

now after installation the keyboard and mouse ( touchpad or nipple ) do not function
since this inconvenience i have been plugging in a usb keyboard and mouse at the graphical login then using them to work the laptop
After a reboot the usb peripherals do need to be uplugged and reconnected otherwise they also do not function

i am obviously missing something vital here but i am not sure where to start, kernel 2.6.38.2-686
i have loaded the non-free repos added the various firmware files etc. to get wireless and bluetooth to function
but the keyboard and mouse has me stumped
i have searched the forum and google but haven't come across anyone with the same issue.
Some forum suggestions have been to reconfigure xorg.conf but this does not exist on this install
evdev - the event driver is there
udev - the kernel device manager is also there

What could it be?

[emariz]

No keyboard? It could be a kernel issue, but it would be odd. Did you check the installation image?
Since the installation is new and you used the network installer, you could use the Stable businesscard image and reinstall Debian. Stable images are well tested and the bussinesscard one asks you what branch to install (Stable, Testing or Unstable).
Keep in mind that Testing installers might fail any other day.

[gabrielsaldana]

I'm having the same problem. I have a Dell XPS M1530, working fine on squeeze, but decided to do a fresh install of wheezy. Now I have no laptop keyboard or touchpad and usb items have to be re-plugged back in after booting. CD image was tested and everything was fine. I used April 19 kde amd64 testing image.

I also tested on a virtual machine using Virtualbox on a Macbook pro, and same thing, no onboard keyboard or touchpad, only USB.

[emariz]

I searched for udev bugs and it seems that these bug reports describe your problem:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621036
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622309

I then noticed that Sid users of this forum had discussed it a couple of days ago:
http://forums.debian.net/viewtopic.php?f=20&t=62545

Try this solution http://bugs.debian.org/cgi-bin/bugrepor ... =621036#77 or upgrade your system and check if the new packages solve the problem.

I guess that the Testing images that you downloaded include the problematic combination of udev and base-files. I run a daily updated Testing and this issue never affected it.

[Roel63]

Same here when installing with the testing business card. So I reinstalled with the Squeeze business card and dist-upgraded immediately after installing the base system.

And if I remember correctly, the first boot after installing with the testing business card gave a udev error.

[emariz]

So I reinstalled with the Squeeze business card and dist-upgraded immediately after installing the base system.

Why did you upgrade after the installation? One can install Stable, Testing or Sid with the businesscard image.
Their problem was to install the base system contained in a failed Testing image.

[Roel63]

Why did you upgrade after the installation? One can install Stable, Testing or Sid with the businesscard image.
Their problem was to install the base system contained in a failed Testing image.

OK but I figured that I would get the same result when doing it that way, hence my Squeeze install first.

Thinking back, I think you are right.

[lambcutlet]

thankyou to emariz
trawling through the links you suggested i found this command

Code: Select all

rm -rf /run

run as root
i then rebooted the laptop and the keyboard and mouse are now working, fantastic

thanks again

[zem]

thankyou to emariz
trawling through the links you suggested i found this command

Code: Select all

rm -rf /run

run as root
i then rebooted the laptop and the keyboard and mouse are now working, fantastic

thanks again

this worked for me too

[azorius]

thankyou to emariz
trawling through the links you suggested i found this command

Code: Select all

rm -rf /run

run as root
i then rebooted the laptop and the keyboard and mouse are now working, fantastic

thanks again

this worked for me too

worked for me as well!

[jommoner]

This worked for me also

[bkpsusmitaa]

It works for me too. How come such an innocuous code line can solve this grave problem? Will someone with a superior intellect and knowhow have a little patience to explain?
Regards

[networker_]

thankyou to emariz
trawling through the links you suggested i found this command

Code: Select all

rm -rf /run

run as root
i then rebooted the laptop and the keyboard and mouse are now working, fantastic

thanks again

this worked for me too

worked for me as well!

worked for me too, on a dell L502X

[kevmitch]

There is currently a major change under way in how udev (and many other parts of the system) operate with regards to their run status information particularly early on in the boot.

http://www.h-online.com/open/news/item/ ... 19006.html

The /run directory is the new place where all of this information is supposed to go. Before it was all over the bloody place in in /var/run, /var/lock/ /dev/.udev/, and even the particularly disdainful /etc/network/interfaces/run/.

/run is supposed to be a tmpfs (i.e., not actually on the disk) mounted early in the boot so that it is available for full read-write access to things like udev to use. It is used so early, that if this tmpfs is not mounted, and things try to write to it, they will fail because the root filesystem is still read only. I think having the mountpoint non-empty can cause problems getting the tmpfs mounted and furthermore that getting a nonempty /run on the root filesystem isn't to hard if you have just upgraded and stuff starts using it willy nilly before you reboot. The upgrade path is obviously something that's going to get a lot of work before the next stable release.