Same issue also appears in Linux Mint 18.1 Mate. In all instances, the
touchpad works in the live USB boot before installation but after
installation, its as though it is not even installed.
@santi Thank you for letting me know. It's definitely frustrating as its
an essential piece of the
Public bug reported:
I recently purchased a Sager NP8152-S / Clevo 650RP6.
See http://www.clevo.com/clevo_prodetail.asp?id=958=en
The trackpad is not detected. xinput does not display a trackpad device
nor is the device listed in
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package:
** Description changed:
- I recently purchased a Sager NP8152-S / Clevo 650RP6.
- See http://www.clevo.com/clevo_prodetail.asp?id=958=en
+ I recently purchased a Sager NP8152-S / Clevo 650RP6.
+ See http://www.clevo.com/clevo_prodetail.asp?id=958=en
The trackpad is not detected. xinput
Output of xinput booting from USB. Touchpad works:
↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer
(2)]
--
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/1651005
This did not work:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1314198/comments/31
--
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/1651005
Title:
Unidentified Trackpad
IGNORE COMMENT #3.
Here is the full output of lshw:
description: Notebook
product: P65xRP (Not Applicable)
vendor: Notebook
version: Not Applicable
serial: Not Applicable
width: 64 bits
capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
configuration: boot=normal
Output from lshw for the unidentified touchpad device:
*-serial UNCLAIMED
description: SMBus
product: Sunrise Point-H SMBus
vendor: Intel Corporation
physical id: 1f.4
bus info: pci@:00:1f.4
version: 31
I had tried upgrading to 16.10 using the automated upgrade to see if I
could fix the problem. This is the version for which I reported the bug.
I've since tried reinstalling with 16.04.1 and attempted the upstream
kernel fix that you recommended.
Sorry for my inconsistencies.
** Tags added:
This issue is occurring after a brand new installation using latest 16.04.1 iso
image on a new computer. When booting into a USB live testing/installation, the
touchpad works and is detected using xinput command. However, after
installation, the touchpad is no longer detected. Not sure if this
Okay. That file exists.
Thanks for the info. Looking forward to seeing these patches arrive in
the next few kernel iterations.
Cheers
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This fix is not showing up in 4.4.0-70.
--
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/1674390
Title:
Kernel 4.4.0-67 Defaults to ACPI-cpufreq rather than P-State - Dell
Precision
Fix not showing up in 4.4.0-70. Not sure if it was intended for this
release.
--
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/1672439
Title:
No C-State Deeper than C3 utilized by Kaby
Fix not showing in 4.4.0-71 either. Just FYI in case it was intended.
--
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/1672439
Title:
No C-State Deeper than C3 utilized by Kaby Lake
Kai-Heng Feng, I also noticed that by default the scaling driver used is
acpi-cpufreq and not p-state. I've read that p-state is favorable for
kernels >= 4.4. Is this something that is up to the user to decide or
should this be considered an incorrect default?
analyzing CPU 0:
driver:
sudo powertop (idel stats)
Package | Core|CPU 0 CPU 4
POLL0.0%| POLL0.0%| POLL0.0%0.0 ms 0.1%
3.1 ms
C1E-SKL 0.5%| C1E-SKL 0.2%| C1E-SKL 0.4%0.6 ms 0.0%
0.1 ms
C3-SKL 0.2%
However, I notcied powertop is now not automatically choosing to adjust
many of the bad parameters to good (not sure if that is related...).
Most of the PCI devices are not set to Bad when previously they were
automatically at Good.
Bad Enable SATA link power management for host0
Autotune with powertop works fine. No interference. Still showing heavy
usage of C10 state when idling :) :)
I think this is a worthy path to incorporate for us 5520 users.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Okay. I'll try it out.
--
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/1672439
Title:
No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
5520
Status in linux package
Should I install all four .deb packages in the link you provided?
--
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/1672439
Title:
No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in
Just an FYI, I do see this warning every time I've tried to build a
kernel on my 5520. Not sure if this is an issue.
: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
--
You received this bug notification because you are a member of Kernel
Packages,
Okay. Right away I notice a difference with the program i7z:
Cpu speed from cpuinfo 2875.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating
via tsc
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2895 MHz
CPU Multiplier 29x
Also trying to run turbostat:
sudo turbostat --debug
WARNING: turbostat not found for kernel 4.4.0-68
You may need to install the following packages for this specific kernel:
linux-tools-4.4.0-68-generic
linux-cloud-tools-4.4.0-68-generic
You may also want to install one of the
Excuse my ignorance, but does that mean I should continue to use your
4.4.0-68 kernel and as Canonical releases kernel updates, I should
naturally phase into the regular update stream again? Or should I revert
to the newest updated (4.4.0-67) and remove your custom kernel?
Thanks!
--
You
Public bug reported:
sudo cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 2.80 GHz
TLP settings:
--- TLP 0.8
+++ Configured Settings: /etc/default/tlp
TLP_ENABLE=1
TLP_DEFAULT_MODE=AC
DISK_IDLE_SECS_ON_AC=0
DISK_IDLE_SECS_ON_BAT=2
MAX_LOST_WORK_SECS_ON_AC=15
MAX_LOST_WORK_SECS_ON_BAT=60
CPU_MIN_PERF_ON_AC=0
CPU_MAX_PERF_ON_AC=100
Kai-Heng,
It has been filed:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674390
--
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/1672439
Title:
No C-State Deeper than C3
Your kernel does not have cpupower but according to tlp -p, the test
kernel is now using pstate. Is there a more appropriate way to confirm
this other than using tlp? Also, according to tlp, the scaling-govenors
swtich appropriately (performace for A/C and powersave for bat).
Lastly, I just
Just another observation, the scaling_max_freq is now at 390 (the
boost max) using pstate vs 2801000 (standard max) when using acpi-
cpufreq driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Kai-Heng Feng, I am not sure if this patch was intended for 4.4.0-67
(which recently was updated via Software Updater) but that kernel
version reverted my CPU behavior back to only using C3 states and
nothing deeper. Just FYI.
--
You received this bug notification because you are a member of
Kai-Feng, you were right about Powertop. I am a big fan of presuming th
worst. For some reason, my trackpad stopped tracking (I could click but
no movement). However upon restart it seems to be fully restored and
operational.
--
You received this bug notification because you are a member of
Sorry to be so persistent but Intel has posted a warning about not using
lower power states. See page 64 of this data sheet:
http://www.intel.com/content/www/us/en/processors/core/6th-gen-core-
family-mobile-u-y-processor-lines-datasheet-vol-1.html
--
You received this bug notification because
@Kai-Heng Feng, the fix is not showing up in 4.4.0-72
carl@carl-5520:~$ uname -a
Linux carl-5520 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
carl@carl-5520:~$ sudo powertop
Package | Core|CPU 0 CPU 4
~$ sudo powertop (Idle Stats tab)
Package | Core|CPU 0 CPU 4
POLL0.0%| POLL0.0%| POLL0.0%0.0 ms 0.0%
0.0 ms
C1 0.8%| C1 0.3%| C1 0.3%0.2 ms 0.4%
0.6 ms
C2
Installed:
intel-microcode_3.20161104.1~deb8u1~bpo7+1_amd6
--
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/1672439
Title:
No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in
~$ dmesg |grep idle
[0.00] clocksource: refined-jiffies: mask: 0x max_cycles:
0x, max_idle_ns: 7645519600211568 ns
[0.00] clocksource: hpet: mask: 0x max_cycles: 0x,
max_idle_ns: 79635855245 ns
[0.044934] process: using mwait in idle threads
[
Let me know what other information I could supply.
--
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/1672439
Title:
No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
Public bug reported:
My processor does not appear to be utilizing and idling states deeper
than C3.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
cat /sys/module/intel_idle/parameters/max_cstate
~$ cat /sys/module/intel_idle/parameters/max_cstate
9
--
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/1672439
Title:
No C-State Deeper
~$ sudo i7z
sudo i7z
i7z DEBUG: i7z version: svn-r93-(27-MAY-2013)
i7z DEBUG: Found Intel Processor
i7z DEBUG:Stepping 9
i7z DEBUG:Model e
i7z DEBUG:Family 6
i7z DEBUG:Processor Type 0
i7z DEBUG:Extended Model 9
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Unknown
~$ sudo turbostat
cpu0: Guessing tjMax 100 C, Please use -T to specify
CPU Avg_MHz Busy% Bzy_MHz TSC_MHz
- 1006.6315002904
0 1097.2715002904
4 805.3315012904
1 1338.8514982904
5 93
@Kai-Heng Feng, What are the odds of this backport patch being included
with the next update from Canonical for 16.04. Since your recommended
kernel is 4.4.0-68 do you think it will arrive as part of the regular
release schedule? I can report if the patch worked when it arrives. As
much as I love
Kernel 4.4.75 appears to have fixed the problem for C states.
Package | Core|CPU 0 CPU 4
POLL0.1%| POLL0.0%| POLL0.0%0.0 ms 0.0%
0.0 ms
C1E-SKL 1.4%| C1E-SKL 2.9%| C1E-SKL 3.5%0.3 ms
@Kai-Feng. The other bug regarding p-state as disappeared (I cannot
access it on Ubuntu bugs). This bug also appears to be fixed as p-state
is now the default scaling driver. However tlp stat is showing unusual
max/min cpufreq settings after kernel installation. Do these settings
seem incorrect
43 matches
Mail list logo
