[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
I posted this on the NVIDIA forums, but thought it might be helpful to cross-post here. --- I just tried the 460 server driver solution. This did not work for me and I still have the display port bug. I have an AMD 3800X, 64 gb ram, rtx 2080 super, fresh install of Ubuntu 20.04 kernel 5.8.0-55, with 3 identical 4K monitors, (1 on HDMI, 2 on DP). The opensource driver continues to work just fine, but we need CUDA for our science to continue. Here are the outputs from nvidia-smi, uname -r, and xrandr. Note that all monitors should have 4K options. ''' (base) x@x:~$ nvidia-smi Wed Jun 9 17:18:16 2021 +-+ | NVIDIA-SMI 460.73.01Driver Version: 460.73.01CUDA Version: 11.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce RTX 208... Off | :0E:00.0 On | N/A | | 0% 45CP517W / 250W |702MiB / 7981MiB | 1% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 918 G /usr/lib/xorg/Xorg198MiB | |0 N/A N/A 1466 G /usr/lib/xorg/Xorg349MiB | |0 N/A N/A 1603 G /usr/bin/gnome-shell 137MiB | |0 N/A N/A 2014 G gnome-control-center2MiB | +-+ (base) x@x:~$ uname -r 5.8.0-55-generic (base) x@x:~$ (base) x@x:~$ xrandr Screen 0: minimum 8 x 8, current 7680 x 2160, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 1110mm x 620mm 1920x1080 60.00 + 59.9429.97* 23.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 3840x2160 30.00*+ 59.9429.9723.9823.98 4096x2160 59.9429.9724.0023.98 1920x1080 60.0059.9429.9723.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 connected 1920x1080+5760+0 (normal left inverted right x axis y axis) 800mm x 450mm 1920x1080 60.00*+ 59.9429.9723.98 1680x1050 59.95 1440x900 59.89 1360x768 60.02 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x720 60.0059.9429.9723.98 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.32 720x480 59.94 640x480 75.0072.8159.9459.93 USB-C-0 disconnected (normal left inverted right x axis y axis) ''' I tried the nvidia-driver-460-server solution. Sadly it did not work for me. The display port connected monitor resolutions are not correct with the 460.73.01 driver version showing 1080p when they should be 4K. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
I'm also experiencing the same issue with the ASM1142 controller on the Core X Chroma and can reproduce consistently. I'm running kernel 5.0.9. Guilherme, thanks for your work diagnosing this. This device is sold by Razer. I will try and reach out but they do not claim Linux support on any of their devices so I worry this may go unfixed. Barring a firmware fix, is there any hope of this being fixed with a quirk, as the other controller was? I realize this LP is not the ideal place for such a fix to take place, but I am happy to participate in finding a solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
That fixed it, I now see both drives: % sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 256B INTEL SSDPEKKF256G8L 1 256.06 GB / 256.06 GB512 B + 0 B L08P /dev/nvme1n1 256B INTEL SSDPEKKF256G8L 1 256.06 GB / 256.06 GB512 B + 0 B L08P -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are identical, then only one drive can be seen. NQN is supposed to be unique but some Intel drives do not follow that. [Fix] The device-supplied subnqn is ignored and one will be generated as if the field is empty. The upstream patch conflicts with a value in 'enum nvme_quirks' that we added in a SAUCE patch, changed that from (1<<8) to (1<<15). [Test] With this fix, both drives can be seen. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. - I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one 256G and the other 512G with the intention of keeping the windows on the 256G disk and using the 512G for linux. When dealing with the installer, it only ever saw one of the SSDs. I did manged to get bionic installed on the 512, but on boot, sometimes it doesn't find the 512G disk and I just get a blank screen. After a hard power-off, and reboot, it drops into the grub selector, and choosing linux, it failed again, but this time dropped into a VT. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2003 F pulseaudio /dev/snd/controlC0: tim2003 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 18:53:34 2019 InstallationDate: Installed on 2019-01-14 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109) MachineType: LENOVO 20MFCTO1WW ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
I still have this issue with booting, though it seems to be less
frequent. However, I can see in the kernel logs when I boot into linux
successfully that my other drive is being thrown out because of the
duplicate subnqn:
nvme nvme1: ignoring ctrl due to duplicate subnqn
(nqn.2017-12.org.nvmexpress:uuid:----).
I'm having some trouble testing this on my own since I'm not experienced with
kernel dev, but I wonder if this duplicate entry in the device table in
drivers/nvme/host/pci.c is the issue:
{ PCI_VDEVICE(INTEL, 0xf1a6),
.driver_data = NVME_QUIRK_NO_DISABLE, },
{ PCI_VDEVICE(INTEL, 0xf1a6), /* Intel 760p/Pro 7600p */
.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN, },
I believe it should be just
{ PCI_VDEVICE(INTEL, 0xf1a6), /* Intel 760p/Pro 7600p */
.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
NVME_QUIRK_NO_DISABLE, },
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811755
Title:
X1 Extreme: only one of the two SSDs is loaded
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
[Impact]
On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are
identical, then only one drive can be seen. NQN is supposed to be unique
but some Intel drives do not follow that.
[Fix]
The device-supplied subnqn is ignored and one will be generated as if
the field is empty.
The upstream patch conflicts with a value in 'enum nvme_quirks' that we
added in a SAUCE patch, changed that from (1<<8) to (1<<15).
[Test]
With this fix, both drives can be seen.
[Regression Potential]
The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been
verified by the bug reporter.
-
I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
256G and the other 512G with the intention of keeping the windows on
the 256G disk and using the 512G for linux.
When dealing with the installer, it only ever saw one of the SSDs. I
did manged to get bionic installed on the 512, but on boot, sometimes
it doesn't find the 512G disk and I just get a blank screen. After a
hard power-off, and reboot, it drops into the grub selector, and
choosing linux, it failed again, but this time dropped into a VT.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tim2003 F pulseaudio
/dev/snd/controlC0: tim2003 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 15 18:53:34 2019
InstallationDate: Installed on 2019-01-14 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
MachineType: LENOVO 20MFCTO1WW
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-43-generic N/A
linux-backports-modules-4.15.0-43-generic N/A
linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET35W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
dmi.product.version: ThinkPad X1 Extreme
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.
I posted a question on superuser about my problem here: http://superuser.com/questions/802797/elantech-touchpad-driver-issues- and-input-lag-in-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1166442 Title: Elantech clickpad/touchpad lacks multitouch features. Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “linux” package in Arch Linux: New Bug description: Newer versions of the Elantech multitouch trackpad are not fully supported in Linux. These appear in many of the newer Samsung laptops, for example. elantech.c in the kernel needs to be updated to support these models (up to v7 perhaps?) This bug is confirmed to affect a range of samsung laptops running Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current (3.9) upstream kernel. A dkms package was produced in 2011 (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/681904/comments/64) which may fix certain older laptops affected by this issue, but doesn't fix newer models. == Original Report == Hello, So far I've been having a problem with my Elantech multitouch trackpad in Linux. Basically all i get is right click, left click, and tap to click, along with basic movement. The problem seems to be rooted in improper detection of the trackpad, likely b/c its a new revision or whatnot. Of note is that working elantech trackpads of the past in forums i scouted through show up as ETPS/2 Elantech Touchpad. Mine just shows up in xinput as PS/2 Elantech Touchpad. I think this might be a simple fix in the end, just improper detection, I hope. For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on Ubuntu 13.04 thus far, with all combinations of psmouse. -- What's expected: touchpad multitouch support What happened: basic touchpad support Laptop mode: Samsung Series 7 NP780 series Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04 Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and psmouse-alps-dst. No improvements so removed. synclient -l reports Couldn't find synaptics properties. No synaptics driver loaded? -- See attached for more info. Ask anything you need! --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gscoppino 2272 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d InstallationDate: Installed on 2013-04-06 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.104 StagingDrivers: rts5139 Tags: raring staging Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03ABU.139.130226.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP780Z5E-S01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03ABU.139.130226.SK:bd02/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E/870Z5E/880Z5E:pvrP03ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP780Z5E-S01UB:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 770Z5E/780Z5E/870Z5E/880Z5E dmi.product.version: P03ABU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.
The fix in comment #137 also fixed my touchpad being detected on my Lenovo U530, and now two-finger scrolling works! Only problem is that now there seems to be a slight (but noticeable) input lag. Does anybody else have this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1166442 Title: Elantech clickpad/touchpad lacks multitouch features. Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “linux” package in Arch Linux: New Bug description: Newer versions of the Elantech multitouch trackpad are not fully supported in Linux. These appear in many of the newer Samsung laptops, for example. elantech.c in the kernel needs to be updated to support these models (up to v7 perhaps?) This bug is confirmed to affect a range of samsung laptops running Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current (3.9) upstream kernel. A dkms package was produced in 2011 (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/681904/comments/64) which may fix certain older laptops affected by this issue, but doesn't fix newer models. == Original Report == Hello, So far I've been having a problem with my Elantech multitouch trackpad in Linux. Basically all i get is right click, left click, and tap to click, along with basic movement. The problem seems to be rooted in improper detection of the trackpad, likely b/c its a new revision or whatnot. Of note is that working elantech trackpads of the past in forums i scouted through show up as ETPS/2 Elantech Touchpad. Mine just shows up in xinput as PS/2 Elantech Touchpad. I think this might be a simple fix in the end, just improper detection, I hope. For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on Ubuntu 13.04 thus far, with all combinations of psmouse. -- What's expected: touchpad multitouch support What happened: basic touchpad support Laptop mode: Samsung Series 7 NP780 series Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04 Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and psmouse-alps-dst. No improvements so removed. synclient -l reports Couldn't find synaptics properties. No synaptics driver loaded? -- See attached for more info. Ask anything you need! --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gscoppino 2272 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d InstallationDate: Installed on 2013-04-06 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.104 StagingDrivers: rts5139 Tags: raring staging Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03ABU.139.130226.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP780Z5E-S01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03ABU.139.130226.SK:bd02/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E/870Z5E/880Z5E:pvrP03ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP780Z5E-S01UB:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 770Z5E/780Z5E/870Z5E/880Z5E dmi.product.version: P03ABU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
