rPi 2 B / rPi 1 B - No input possible after startx

[mame82]

There seems to be an issue with the kernel 3.18, which prevents recognition of usb input-devices for X-Server.

I'm using a kali image for rPi 1 B, with kernel 3.12 which works well.
After buying the rPi 2, I rebuilt the Kali image, following these instructions https://cyberkryption.wordpress.com/201 ... erry-pi-2/, which works well. The only problem was that none of my input-devices got's recognized.

Xorg.log shows the following:

Code: Select all

[    73.666] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[    73.666] (II) No input driver specified, ignoring this device.
[    73.666] (II) This device may have been added with another device file.

Under normal circumstances, there are some entries from 'evdev' which are missing here.
Here are the entries from a working Kernel in xorg.log

Code: Select all

[    76.645] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[    76.646] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.

So I went back to the rPi 1 B. I've patched the old working kali image, with the new kernel.img (migrating from 3.12 to 3.18) and the same error arises on the old rPi B - input isn't working anymore.
Overwriting the kernerl.img with the old one makes it work again.

So I grabbed /porc/config.gz on both setups and compared with meld. But there seems to be no differences
hinting to an error with 'evdev' or any mess with the drivers.

I have no idea what to do next. By the way, raspian is working fine with 3.18.

So is there any hint from u folks, about how to go on????
Oh, one more thing: the X-Server of KALI is compiled against Kernel 3.16, armv7l

Code: Select all

[    68.852] Build Operating System: Linux 3.16-0.bpo.2-armmp-lpae armv7l Debian

[mame82]

Problem is solved:
evdev kernel module is needed for input devices to work under x.

One have to install the right modules for the 3.18 under /lib/modules. These could be taken from a fresh raspian image for example.

It's all working fine now, with more wifi adapters supported and a large speedboost. Nice

[NerdProgrammeJadoo]

Boot your pi, login, after that type startx, you get an error saying processgave up runming something like that and could not acquire lock cuz its ready only similar to it, is yes then do the following, type sudo fsck and hit enter, when ever it ask u ti whether fix or not just type y(yes) and it will fix at, at the end it will ask for reboot. After reboot do sudo apt-get clean, after thet sudo apt-get autoclean and you are done.

[elvenstof]

I have the same problem but I can't find the /lib/modules folder on my raspbian install.
When I start the pi it will launch the login screen by it self so I can't update rpi from the launch terminal.

Does any of you know how it can get this to work?