Mouspad not fully supported in karmic, i8042.reset i8042.nomux don't enable scrolling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I own a Fujitsu-Siemens Lifebook S-6120 which runs Ubuntu Linux since a couple of years. It has a touchpad which supports scrolling, when you drag your finger on the right edge of the pad. It has also a seesaw button so that you can scroll up and down easily.
In previous versions of ubuntu i had to enter
# defoptions=quiet splash i8042.reset i8042.nomux
into the /boot/grub/menu.lst and run
$ sudo update-grub
so that the options "i8042.reset i8042.nomux" make it into the kernel options to enable those features. Without these option the mouse moved erratically for a short time after the Xserver started and the scrolling on the edge as well as the seesaw button didn't work.
Right now i'm trying Ubuntu Karmic with all the latest updates. The behavior without the options "i8042.reset i8042.nomux" is still the same. No scrolling on the edge of the pad and only the down-button of the seesaw works as a middle click. When I add "i8042.reset i8042.nomux" to the /boot/grub/
menuentry "Ubuntu, Linux 2.6.31-12-generic" {
save_env recordfail
set quiet=1
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 026a79a8-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
i notice a regression. Tapping on the touchpad doesn't act as a left click anymore. I have to click on the phsyical mouse button. Also scrolling via dragging a finger on the right side of the pad as well as the seesaw button still doesn't work.
ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'SigmaTel STAC9766,67'
Components : 'AC97a:83847666'
Controls : 31
Simple ctrls : 21
Date: Wed Oct 7 13:07:53 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: FUJITSU SIEMENS LIFEBOOK S6120
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Uname: Linux 2.6.31-12-generic i686
dmi.bios.date: 05/10/2004
dmi.bios.vendor: Phoenix/FUJITSU
dmi.bios.version: Version 1.26
dmi.board.name: FJNB16C
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.
dmi.modalias: dmi:bvnPhoenix/
dmi.product.name: LIFEBOOK S6120
dmi.sys.vendor: FUJITSU SIEMENS
Hi Christoph,
This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux 445360
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]