[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive
Thanks for following up - we can close this bug, I no longer have this issue. I have attached info just for the record. I upgraded my system BIOS and the problems went away. $ sudo nvme id-ctrl /dev/nvme0 [sudo] password for ian: NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S2FZNYAG801690 mn : PM951 NVMe SAMSUNG 1024GB fr : BXV76D0Q rab : 2 ieee: 002538 cmic: 0 mdts: 5 cntlid : 1 ver : 0 rtd3r : 0 rtd3e : 0 oaes: 0 ctratt : 0 oacs: 0x17 acl : 7 aerl: 3 frmw: 0x6 lpa : 0 elpe: 63 npss: 4 avscc : 0x1 apsta : 0x1 wctemp : 0 cctemp : 0 mtfa: 0 hmpre : 0 hmmin : 0 tnvmcap : 0 unvmcap : 0 rpmbs : 0 edstt : 35 dsto: 0 fwug: 0 kas : 0 hctma : 0 mntmt : 0 mxtmt : 0 sanicap : 0 hmminds : 0 hmmaxd : 0 sqes: 0x66 cqes: 0x44 maxcmd : 0 nn : 1 oncs: 0x1f fuses : 0 fna : 0 vwc : 0x1 awun: 255 awupf : 0 nvscc : 1 acwu: 0 sgls: 0 subnqn : ioccsz : 0 iorcsz : 0 icdoff : 0 ctrattr : 0 msdbd : 0 ps0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps2 : mp:3.10W operational enlat:100 exlat:100 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- $ uname -a Linux ian-XPS-15-9550 4.19.8-041908-generic #201812080831 SMP Sat Dec 8 13:34:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux System BIOS was upgraded to 1.9.0 - I believe this is the thing that fixed the NVMe issues. Thanks for following up, please feel free to close the bug if you have the details you need (and hopefully these will help someone else). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805816 Title: APST quirk needed for PM951 Samsung 1TB NVMe Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Hello Yingfag - can I check please - was it a 1TB Samsung SSD? Which model of SSD (950? 960? 970? something else?). When you changed the SSD - did you keep the same model? What was your final solution? Regards, Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive
Oops - I can mark this issue as "New" but not "Complete" (which in turn was me mis-reading the instruction from the bot in #4). Sorry for the noise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805816 Title: APST quirk needed for PM951 Samsung 1TB NVMe Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive
Sorry - I've hit a hiccup. `apport` wants me to file extra information (as uploaded above, twice) but upon running at the command line it notes: ` It appears you are currently running a mainline kernel. It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the upstream kernel developers are aware of the issue. If you'd still like to file a bug against the Ubuntu kernel, please boot with an official Ubuntu kernel and re-file. ` I believe I installed 4.19.0 from: http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.19/ which I presume is the official Ubuntu kernel source - should I be installing from elsewhere? My first step is to mark this as Complete in case someone can give me sensible guidance and I've _also_ posted it to the Kernel.org Bugzilla (which might be the best place for this bug?): https://bugzilla.kernel.org/show_bug.cgi?id=201811 Any and all guidance very happily received, thanks for your help, Ian. ** Bug watch added: Linux Kernel Bug Tracker #201811 https://bugzilla.kernel.org/show_bug.cgi?id=201811 ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805816 Title: APST quirk needed for PM951 Samsung 1TB NVMe Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive
apport information
** Description changed:
This is a fresh posted connected to a very similar now-solved bug ("APST
quirk needed for Samsung 512GB NVMe drive"):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
My NVMe is the less-common 1TB version. It exhibits similar (possibly
identical) behaviour but has not yet been quirked.
I've followed up as Comment #101 but maybe I need to open this as a new
issue?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/101
Specifically - using Kernel 4.19.0 on Mint 19.0 the default APST
settings caused read-only errors within minutes-1 hour, this is fatal.
Disabling APST solves the problem, I have this disabled in GRUB now.
Reducing the APST settings but not disabling them does not stop the
problem.
An example of the read-only result (copied from #101) that occurs if APST is
left in its default state:
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem
with ordered data mode. Opts: (null)
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts:
errors=remount-ro
Oct 31 11:33:05 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted
filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem
with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts:
errors=remount-ro
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted
filesystem with ordered data mode. Opts: (null)
I had tried `nvme_core.default_ps_max_latency_us=250` but the read-only
bug persists, it just takes longer to occur. Disabling APST with
`nvme_core.default_ps_max_latency_us=0` has solved the issue.
I've been using my laptop successfully (no read-only errors) for over a
week having disabled APST including many suspend/awaken cycles. Prior to
this every boot would crash and burn with read-only errors within an
hour or so.
This is the drive and kernel (copied from #101):
$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
- --
/dev/nvme0n1 S2FZNYAG801690 PM951 NVMe SAMSUNG 1024GB 1 314.10 GB / 1.02 TB
512 B + 0 B BXV76D0Q
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic #201810221809 SMP Mon Oct 22
22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description: Linux Mint 19 Tara
Release: 19
I am of course happy to upload more info - let me know what's needed?
Could this be added as a quirk to the kernel please?
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
InstallationDate: Installed on 2018-10-27 (32 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
Package: linux (not installed)
Tags: tara
Uname: Linux 4.19.0-041900-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19
+ InstallationDate: Installed on 2018-10-27 (32 days ago)
+ InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
+ Package: linux (not installed)
+ Tags: tara
+ Uname: Linux 4.19.0-041900-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1805816/+attachment/5217333/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805816
Title:
APST quirk needed for PM951 Samsung 1TB NVMe Drive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805816] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1805816/+attachment/5217334/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805816 Title: APST quirk needed for PM951 Samsung 1TB NVMe Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+attachment/5217297/+files/lspci-vnvn.log
** Tags added: apport-collected tara
** Description changed:
This is a fresh posted connected to a very similar now-solved bug ("APST
quirk needed for Samsung 512GB NVMe drive"):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
My NVMe is the less-common 1TB version. It exhibits similar (possibly
identical) behaviour but has not yet been quirked.
I've followed up as Comment #101 but maybe I need to open this as a new
issue?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/101
Specifically - using Kernel 4.19.0 on Mint 19.0 the default APST
settings caused read-only errors within minutes-1 hour, this is fatal.
Disabling APST solves the problem, I have this disabled in GRUB now.
Reducing the APST settings but not disabling them does not stop the
problem.
An example of the read-only result (copied from #101) that occurs if APST is
left in its default state:
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem
with ordered data mode. Opts: (null)
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts:
errors=remount-ro
Oct 31 11:33:05 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted
filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem
with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts:
errors=remount-ro
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted
filesystem with ordered data mode. Opts: (null)
I had tried `nvme_core.default_ps_max_latency_us=250` but the read-only
bug persists, it just takes longer to occur. Disabling APST with
`nvme_core.default_ps_max_latency_us=0` has solved the issue.
I've been using my laptop successfully (no read-only errors) for over a
week having disabled APST including many suspend/awaken cycles. Prior to
this every boot would crash and burn with read-only errors within an
hour or so.
This is the drive and kernel (copied from #101):
$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
- --
/dev/nvme0n1 S2FZNYAG801690 PM951 NVMe SAMSUNG 1024GB 1 314.10 GB / 1.02 TB
512 B + 0 B BXV76D0Q
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic #201810221809 SMP Mon Oct 22
22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description: Linux Mint 19 Tara
Release: 19
I am of course happy to upload more info - let me know what's needed?
Could this be added as a quirk to the kernel please?
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19
+ InstallationDate: Installed on 2018-10-27 (32 days ago)
+ InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
+ Package: linux (not installed)
+ Tags: tara
+ Uname: Linux 4.19.0-041900-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805816
Title:
APST quirk needed for PM951 Samsung 1TB NVMe Drive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805816] [NEW] APST quirk needed for PM951 Samsung 1TB NVMe Drive
Public bug reported:
This is a fresh posted connected to a very similar now-solved bug ("APST
quirk needed for Samsung 512GB NVMe drive"):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
My NVMe is the less-common 1TB version. It exhibits similar (possibly
identical) behaviour but has not yet been quirked.
I've followed up as Comment #101 but maybe I need to open this as a new
issue?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/101
Specifically - using Kernel 4.19.0 on Mint 19.0 the default APST
settings caused read-only errors within minutes-1 hour, this is fatal.
Disabling APST solves the problem, I have this disabled in GRUB now.
Reducing the APST settings but not disabling them does not stop the
problem.
An example of the read-only result (copied from #101) that occurs if APST is
left in its default state:
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with
ordered data mode. Opts: (null)
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts:
errors=remount-ro
Oct 31 11:33:05 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem
with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with
ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts:
errors=remount-ro
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem
with ordered data mode. Opts: (null)
I had tried `nvme_core.default_ps_max_latency_us=250` but the read-only
bug persists, it just takes longer to occur. Disabling APST with
`nvme_core.default_ps_max_latency_us=0` has solved the issue.
I've been using my laptop successfully (no read-only errors) for over a
week having disabled APST including many suspend/awaken cycles. Prior to
this every boot would crash and burn with read-only errors within an
hour or so.
This is the drive and kernel (copied from #101):
$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
- --
/dev/nvme0n1 S2FZNYAG801690 PM951 NVMe SAMSUNG 1024GB 1 314.10 GB / 1.02 TB 512
B + 0 B BXV76D0Q
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic #201810221809 SMP Mon Oct 22
22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description:Linux Mint 19 Tara
Release:19
I am of course happy to upload more info - let me know what's needed?
Could this be added as a quirk to the kernel please?
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
InstallationDate: Installed on 2018-10-27 (32 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
Package: linux (not installed)
Tags: tara
Uname: Linux 4.19.0-041900-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: apport-collected tara
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805816
Title:
APST quirk needed for PM951 Samsung 1TB NVMe Drive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805816] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1805816/+attachment/5217298/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805816 Title: APST quirk needed for PM951 Samsung 1TB NVMe Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805816] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1805816/+attachment/5217299/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805816 Title: APST quirk needed for PM951 Samsung 1TB NVMe Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
I have posted my 1TB (PM951) issue as a new bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Hi Kai-Heng, thanks! Overnight I've used `nvme_core.default_ps_max_latency_us=0` in GRUB with no read-only crashes (everything has been smooth). I left the machine awake all night, I've since suspended & awoken it twice, all seems to be ok. As expected all APSTE is disabled: ` $ sudo nvme get-feature -f 0x0c -H /dev/nvme0 get-feature:0xc (Autonomous Power State Transition), Current value: Autonomous Power State Transition Enable (APSTE): Disabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 1] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . ... ` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
To follow-up. Earlier today I fresh-booted and didn't use the APST disable command - my machine crashed out with read-only errors after minutes. I then updated grub to use `nvme_core.default_ps_max_latency_us=250` as suggested - it was stable for 6 hours, through 2 suspends. A little while ago it crashed with read-only errors. I'm now going to try `nvme_core.default_ps_max_latency_us=0` in GRUB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
I'd like to follow-up on this bug - it affects me using kernel 4.19.0 on a Dell XPS 9550 with a 1TB Samsung drive. Details below. Do I need to open a new bug as I've got a 1TB drive and this bug report was opened for a 512GB drive? $ uname -a Linux ian-XPS-15-9550 4.19.0-041900-generic #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.19.0-041900-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 S2FZNYAG801690 PM951 NVMe SAMSUNG 1024GB 1 314.10 GB / 1.02 TB512 B + 0 B BXV76D0Q A few weeks back I reformatted my machine due to Dropbox's requirement to drop encrypted home folders (I went for full-disk encryption). I'm using Linux Mint 19.0. I used to run kernel 4.9.91, I had to stick to that in my previous machine's Mint installation as >4.9.91 had boot issues (e.g. missing firmware for my wifi) and going 4.10+ caused other issues including, from memory, strange disk issues that I didn't track down along with occasional GPU+second screen issues. I was keen to upgrade to 4.10+ but sticking to 4.9.91 gave me a stable machine. I'm keen to push on now that I'm running on a fresh installation. Having installed Mint 19.0 and upgraded to 4.19.0 I was happy that everything worked...until left idle for a while when I got similar errors to the ones noted here: Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro Oct 31 11:33:05 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null) Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null) After this state the machine would be unusable due to a read-only filesystem. So far I've only exprerimented with disabling APSTE (using: `sudo nvme set-feature -f 0x0c -v=0 /dev/nvme0`) - if I do this after every awaken from suspend then I'm able to use the laptop for over a week without issues with many suspended sessions. If I forget to disable APSTE after awakening from suspend then I lose the hard-drive to a read-only state in 1-2 hours depending on usage. I'm going to start experimenting with adding the grub boot parameter to try different values starting with `nvme_core.default_ps_max_latency_us=250`. I figured opening up this report and taking guidance on what you'd need and whether I needed a new bug report would get the ball rolling. Much obliged! Ian. Note that the following command was run after I disabled APSTE, I'm not sure if the results vary before/after settting APSTE, I can re-run it if that's useful after a fresh boot: $ sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S2FZNYAG801690 mn : PM951 NVMe SAMSUNG 1024GB fr : BXV76D0Q rab : 2 ieee: 002538 cmic: 0 mdts: 5 cntlid : 1 ver : 0 rtd3r : 0 rtd3e : 0 oaes: 0 ctratt : 0 oacs: 0x17 acl : 7 aerl: 3 frmw: 0x6 lpa : 0 elpe: 63 npss: 4 avscc : 0x1 apsta : 0x1 wctemp : 0 cctemp : 0 mtfa: 0 hmpre : 0 hmmin : 0 tnvmcap : 0 unvmcap : 0 rpmbs : 0 edstt : 35 dsto: 0 fwug: 0 kas : 0 hctma : 0 mntmt : 0 mxtmt : 0 sanicap : 0 hmminds : 0 hmmaxd : 0 sqes: 0x66 cqes: 0x44 maxcmd : 0 nn : 1 oncs: 0x1f fuses : 0 fna : 0 vwc : 0x1 awun: 255 awupf : 0 nvscc : 1 acwu: 0 sgls: 0 subnqn : ioccsz : 0 iorcsz : 0 icdoff : 0 ctrattr : 0 msdbd : 0 ps0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps2 : mp:3.10W operational enlat:100 exlat:100 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung
[Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]
Further note - when I made comment #4 I was using the NVIDIA driver 331.113 and kernel 3.13.0-24. I've just updated from Mint 17.1 to Mint 17.2 (with a new nvidia driver and kernel), I'll try suspend hibernate over the coming days and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297049 Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]
Further notes - the A19 bios was from approx June 2013, there is an A21 bios released in 2014 but the few fixes don't seem relevant. I would *very much* like to have a way of getting some sort of kernel log dump after a failure on the next boot, so I can even diagnose if it is failing the same way each time. Can anyone please direct me to how I should do this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297049 Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]
** This bug is no longer a duplicate of bug 1275621 [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297049 Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]
Note I removed the duplicate link (to #1275621) as the other link doesn't mention NVIDIA and it isn't a Dell machine, I suspect that the NVIDIA chipset is the problem. For the 4 years I've owned my E6420 I've failed to get reliable suspend/hibernate behaviour, I always turn the laptop off when I want to change location. Sometimes it'll suspend once or twice, sometimes it fails the first time. A failure can mean that it tries to suspend and then wakes up (sometimes having completely shut down - power light off, no activity...then a few seconds later it wakes up) or it'll start to suspend and then freeze on the console screen (having shut down Cinnamon). After a suspend it is hit or miss whether wifi is working. On occasion the Suspend does work correctly but I can't narrow down the conditions that make it work, it can fail (either re-awakening or freezing) if I try to Suspend just from a fresh boot. A year back I changed the behaviour so it'll only Suspend if I hit the power button and click Suspend (if I close the lid it'll just keep running), that way I can't accidentally close it thinking it might suspend correctly. Since it only Suspends if I click a button I'm confident that there's no odd hardware interactions (e.g. a laptop- closed sensor that's dodgy), as after I click Suspend I wait to see what happens without trying to close the lid. I'm using E6420 Bios A19 (from late 2013). This bug affects me right now (I tried Suspend again last week - same problems occurred). I'm running Linux Mint 17.1 (I've been using Mint for 2.5 years). I started with the official Ubuntu 10.10 Dell installation from 2011 when I bought the machine, that never successfully Hibernated or Suspended either. I've never used apport or other crash report tools, I'd be happy to do so if this might help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297049 Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311257] Re: Wifi cannot connect or unstable after suspend 14.04
In reference to Milton's comments (and thanks for the follow-ups) - my problems (listed in #11) are *not* related to a post-suspend loss of wifi. My problems happen consistently on a fresh boot. Frankly my E6420 can be 'wobbly' after suspend (it has been since 10.10) so I rarely suspend (it can fail to restart wifi, sometimes it refuses to wake at all, sometimes it works fine but won't shutdown - I've no idea what causes this instability). For the time being I'm using a 2nd wifi device (a EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]) whilst in the office to avoid the loss of wifi problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311257 Title: Wifi cannot connect or unstable after suspend 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/1311257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303079] Re: refresh rate value is not saved
I'm seeing this on 14.04 (Linux mint 17), 64 bit. I can't help but remember that I've seen this bug over the years. Two scenarios: 1) Edit|Preferences, Resources tab, Update interval is shown as 0.00, you can adjust it, Close, then if you go back it'll be marked as 0.00 (although the update speed in the charts has probably changed) 2) Make a change to Update interval, switch to another tab, the change is made and the graphs change speed, switch back to Resources tab and the interval is shown as 0.00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303079 Title: refresh rate value is not saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1303079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311257] Re: Wifi cannot connect or unstable after suspend 14.04
I'll mirror the above reports, I'm using a Intel Corporation Centrino Advanced-N 6205 on Linux Mint 17 (Ubuntu 14.04 Trusty), I recently upgraded from 12.04 Linux Mint 16 (Ubuntu 13.04 Saucy) using a complete clean reinstall and now the problem manifests. On Mint 16 (13.04) I had *no* wifi problems in my office (I've been here for 6 months). Since reinstalling 11 days ago with Mint 17 (14.04) in the office (with a BTHub) I'm kicked off of wifi every 5-15 minutes, at home (on a Virgin Wifi device) I have no connection problems. I believe the problem is a combination of 14.04 and the BTHubs here in the office (we have two, different SSIDs, I could use them both before, now both exhibit the same kick-me-off behaviour). Currently I solve the problem using sudo pkill wpa_supplicant as discovered in this thread. This takes me back online, it feels very much like the same behaviour shown in this thread with 14.04 and for #1294044. Before discovering this bug report I was using the widget in the notification bar to disable and then enable the wireless device. Re. it tooks me ages to find this page as others have noted - I've been hunting around with log messages for 11 days before I found this bug report, nothing else I found got me even close to a useful diagnosis. $ uname -a Linux ian-Latitude-E6420 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lspci ... 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34) I have the latest firmware for the 6205 (verifying against Intel's site: http://www.intel.com/support/wireless/wlan/sb/CS-034398.htm) $ sudo lshw -C network *-network description: Ethernet interface product: 82579LM Gigabit Network Connection vendor: Intel Corporation physical id: 19 bus info: pci@:00:19.0 logical name: eth0 version: 04 serial: 5c:26:0a:61:e2:24 capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k firmware=0.13-3 latency=0 link=no multicast=yes port=twisted pair resources: irq:43 memory:e670-e671 memory:e678-e6780fff ioport:5040(size=32) *-network description: Wireless interface product: Centrino Advanced-N 6205 [Taylor Peak] vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 logical name: wlan0 version: 34 serial: a0:88:b4:65:ed:7c width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=3.13.0-24-generic firmware=18.168.6.1 ip=192.168.1.65 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:45 memory:e660-e6601fff A typical dmesg (from when the problem first starts to the wifi being offline): [22291.312726] wlan0: deauthenticated from 00:81:d8:64:33:4a (Reason: 6) [22291.35] cfg80211: Calling CRDA to update world regulatory domain [22291.351954] cfg80211: World regulatory domain updated: [22291.351963] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [22291.351998] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [22291.352004] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [22291.352009] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [22291.352013] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [22291.352017] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [22306.450438] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready The same for syslog: Nov 18 15:35:17 ian-Latitude-E6420 NetworkManager[1067]: warn Activation (wlan0/wireless): association took too long, failing activation. Nov 18 15:35:17 ian-Latitude-E6420 NetworkManager[1067]: info (wlan0): device state change: config - failed (reason 'SSID not found') [50 120 53] Nov 18 15:35:17 ian-Latitude-E6420 NetworkManager[1067]: info NetworkManager state is now DISCONNECTED Nov 18 15:35:17 ian-Latitude-E6420 NetworkManager[1067]: info Marking connection 'Auto BTHub3-35MZ' invalid. Nov 18 15:35:17 ian-Latitude-E6420 NetworkManager[1067]: warn Activation (wlan0) failed for connection 'Auto BTHub3-35MZ' Nov 18 15:35:17 ian-Latitude-E6420 NetworkManager[1067]: info (wlan0): device state change: failed - disconnected (reason 'none') [120 30 0] Nov 18 15:35:17 ian-Latitude-E6420 NetworkManager[1067]: info (wlan0): deactivating device (reason 'none') [0] Nov 18 15:35:17 ian-Latitude-E6420 NetworkManager[1067]: info (wlan0): supplicant interface state: scanning - disconnected Nov 18 15:35:17 ian-Latitude-E6420
[Bug 893597] Re: Phantom batteries are reported on Dell E6420
It looks like this bug is a duplicate and it is now fixed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852406 along with the fix message at #44 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852406/comments/44 which requires kernel 3.0.0-14.23 (I'm on 3.0.0-12-generic so will have to wait for an update). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893597 Title: Phantom batteries are reported on Dell E6420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/893597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893597] Re: Phantom batteries are reported on Dell E6420
Additionally - after un-suspending and seeing 2 or 3 batteries, if I run Power Statistics (this is a Mint package that reports batter/AC statistics) it shows the 2 or 3 batteries. After 20 seconds if I close and re-open Power Statistics it will only show 1 battery. If I then restart Gnome (using: Alt-F2, 'r') it will correctly show just the 1 battery. I have also physically checked the battery compartment - the battery is safely stowed and the plastic locks hold it securely in place. The laptop is only 4 months old, the battery lasts for 2-3 hours from a full charge with a fairly bright screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893597 Title: Phantom batteries are reported on Dell E6420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/893597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893597] Re: Phantom batteries are reported on Dell E6420
I'll report a similar problem. I'm using Linux Mint 12 (based on Ubuntu 11.10) with the default Gnome 3 interface. On approximately every 3rd to 5th wake-up from suspend (using the default pm-suspend) the system reports not 1 battery but 2 or 3 with the extra 1 or 2 having 0 charge. This used to cause the machine to throw up a Critical battery alert and it would hibernate, it would normally not come back from hibernate (I'm not using tuxonice, I have the default power manager), it would partially un-hibernate and then lock on a black screen. To avoid this problem I changed the system setting 'critical battery action' from 'hibernate' to 'nothing' so it doesn't go into hibernate on a critical battery warning. For Linux Mint 12 this is found using the dconf Editor under org/gnome/settings-daemon/plugins/power”. I have an E6420 with NVIDIA NVS 4200M, 64bit Ubuntu. I've produced the following bug notes manually, I tried running apport but it reports an error (The problem cannot be reported: This is not a genuine LinuxMint package) no matter how I try to call it. ProblemType: Bug DistroRelease: Ubuntu 11.10 (Linux Mint 12) Package: acpi (not installed) ProcVersionSignature: (don't know how to find this) Uname: Linux ian-Latitude-E6420 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux NonfreeKernelModules: nvidia (290.10 via ubuntu-x-swat/x-updates) Architecture: x86_64 Date: Tue Dec 27 14:11:57 GMT 2011 InstallationMedia: Linux Mint 12 Lisa DVD 64 bit SourcePackage: acpi UpgradeStatus: No upgrade log (fresh install) I'm a long-time Linux user (back to Slackware and Diamond Stealth video cards), I'm happy to dig/report if someone gives me some guidance. This E6420 is my only laptop and I'd love for it to work reliably. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893597 Title: Phantom batteries are reported on Dell E6420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/893597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760142] Re: Several Ubuntu-certified Dell laptops: ImPS/2 ALPS GlidePoint configure as PS/2 mouse instead of proper touchpad
*** This bug is a duplicate of bug 606238 *** https://bugs.launchpad.net/bugs/606238 Agreeing with #83 - on my Dell E6420 with 11.10 (Linux Mint 12 with NVS4200M) I just downloaded and installed the .deb from #81, rebooted and then I saw the Touchpad tab in Mouse and Settings - two finger scrolling and disable-pad-whilst-typing are now enabled. Yay! Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760142 Title: Several Ubuntu-certified Dell laptops: ImPS/2 ALPS GlidePoint configure as PS/2 mouse instead of proper touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/760142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others
Echoing #88 - on that thread comment #81 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/760142/comments/81 links back to #78, I downloaded and installed the .deb via #81, rebooted and now I have the Touchpad settings in Ubuntu 11.10 (Linux Mint 12) on my Dell E6420. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 and others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510
*** This bug is a duplicate of bug 550625 *** https://bugs.launchpad.net/bugs/550625 In reply to Philip Aston's comment #41 I have a slightly tweaked KeyboardDetector.py script which catches two OSError exceptions (numbers 4 and 24) which cause the script to die quickly on my E6420. The fixes are linked here: https://github.com/ianozsvald/Dell_E6420_Touchpad_AutoDisabler and related E6420 notes are here: http://ianozsvald.com/2011/08/02/dell-e6420-with-ubuntu-10-10-maverick-meerkat-32-bit/ I have an E6420, Ubuntu 10.10, with NVIDIA NVS 4200M, SSD, 8GB RAM, built in camera, Broadcom 5800 based wifi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606238 Title: synaptic touchpad not recognized on dell latitude e6510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
