Comment 31 for bug 335297

Revision history for this message
Grizzly (sven-witterstein) wrote :

I dist-upgraded to 2.6.28.9 and now I can only login with failsafe gnome session.
Normal login gives

> /etc/X11/Xsession.d/60x11-localhost: 4: Syntax error: Bad fd number

from this bug #340697... and moved the ampersand to the end of the line...

I found this in my dmesg as related to imps/psmouse reload

[ 33.610209] psmouse.c: Touchpad at isa0060/serio1/input0 lost sync at byte 4
[ 34.294951] psmouse.c: Touchpad at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
[ 34.803045] psmouse.c: resync failed, issuing reconnect request
[ 35.489893] psmouse.c: Touchpad at isa0060/serio1/input0 lost sync at byte 4
[ 35.622326] psmouse.c: Touchpad at isa0060/serio1/input0 lost sync at byte 4
[ 35.638041] psmouse.c: Touchpad at isa0060/serio1/input0 lost sync at byte 4
[ 35.678491] psmouse.c: Touchpad at isa0060/serio1/input0 lost sync at byte 4
[ 35.689965] psmouse.c: Touchpad at isa0060/serio1/input0 lost sync at byte 4
[ 35.689968] psmouse.c: issuing reconnect request
[ 45.708144] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 45.708150] Bluetooth: BNEP filters: protocol multicast

so - still the system thinks it sees a touchpad - and again it wants to do something with bluetooth which the board does not have :-(

I put the rmmod lsmod sequence in /etc/rc.local - now the ps/2 mouse works even at the login screen

Any comments whether it is a hal bug or a kernel or a startup script bug? (VirtualBox-Jaunty runs fine single-cored - real system doesnt (dual cora = race?)