Public bug reported:
When the power button is pressed for resume from standby, screen remain
black. I'm unable to do anything, and I have to power off the laptop
using power button.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature
First post was incomplete, more informations:
Precitations
This issue is present shutting the lid of my laptop, which is set to suspend on
close and also clicking the word Suspend in the GUI.
Shutting the lid of my laptop + power button to resume: black screen.
Standby clicking the word Suspend i
** Attachment added: "wakeup-none.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791720/+files/wakeup-none.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
** Attachment added: "dmesg-devices.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791710/+files/dmesg-devices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
** Attachment added: "dmesg-freezer.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791709/+files/dmesg-freezer.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
--
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/1649945
Title:
HP 470g3 - not resume from standby
Status in linux package in Ubuntu:
Confirmed
Bug description:
When the power button
** Attachment added: "dmesg-none.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791714/+files/dmesg-none.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "dmesg-processors.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791712/+files/dmesg-processors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Attachment added: "dmesg-platform.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791711/+files/dmesg-platform.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
** Attachment added: "wakeup.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791708/+files/wakeup.txt
--
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/16499
** Attachment added: "dmesg-core.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791713/+files/dmesg-core.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "dmesg-core.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791718/+files/dmesg-core.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "dmesg-processors.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791717/+files/dmesg-processors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Attachment added: "dmesg-none.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791719/+files/dmesg-none.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment removed: "dmesg-none.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791714/+files/dmesg-none.txt
** Attachment removed: "dmesg-core.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791713/+files/dmesg-core.txt
**
No, this is a new computer and this is a fresh install. I'm really sorry but at
this time I'm unable to try the latest upstream kernel.
But I confirm that this issue is also present in these kernels (they are the
latest kernels present in the official Mint Update Manager):
4.8.0-30
4.8.0-32
4.8.0
Ok, now I test the upstream kernel from here http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.10-rc5/
kernel tested is:
4.10.0-041000rc5-generic
Now with this kernel, going to standby using suspend button in the GUI,
and resuming from standby using the power button, the bug is still NOT
present,
Hi to all,
I've the same problem whit Ubuntu 14.10
from lspci:
02:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
from modinfo iwlwifi
federico@nessuno:~$ modinfo iwlwifi
filename:
/lib/modules/3.16.0-28-generic/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko
li
** Changed in: linux-firmware (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1888647
Title:
Realtek wifi dont work after update
It worked! I added a few parameters to grub before but the did not
worked.
For future reference to others:
- Access the grub configuration file by typing in a terminal: sudo nano
/etc/default/grub
- Find the line "GRUB_CMDLINE_LINUX_DEFAULT" and append i8042.nopnp=1 pci=nocrs
- Save the file and
It worked! I added a few parameters to grub before but the did not
worked.
For future reference to others:
- Access the grub configuration file by typing in a terminal: sudo nano
/etc/default/grub
- Find the line "GRUB_CMDLINE_LINUX_DEFAULT" and append i8042.nopnp=1 pci=nocrs
- Save the file and
You-Cheng, i also tried removing pci=nocrs and rebooting and it did not
work either.
I would like to try
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1881322, should I
delete all the grub parameters that i added?
To add further information:
- With the parameters I currently have, and with M
Public bug reported:
Hello!
The touchpad of my "Bangho G05 Zero" laptop is recognized by "xinput
list" as a "ImPS/2 Generic Wheel Mouse".
I been try everything these days, but I do anything about it :(. I had
come to the conclusion that probably is a kernel bug, it shouldn't
recognize it at leas
Public bug reported:
Hello!
The webcam of my dell xps isn't been recognized by Linux. I search a lot
on the internet and found that many people is experiencing this. For
example, in the ubuntu page they say regarding the camera:
"Intel Icelake integrated the IPU 4th Generation Gen IPU with on-di
I have the same machine (Dell XPS 13 9300), came preloaded with Ubuntu
18, then upgraded to 20.04. Running Kernel 5.4.0-48-generic #52.
I have the same problem, only that nothing really helps apart from
restarting until it randomly works ...
--
You received this bug notification because you are
lem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7
Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal
Machine: Type: Laptop System: TOSHIBA product: Satellite-L845 v:
PSKF6
up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7
Distro: Linux Mint 20 Ulyana base: Ubu
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
without
staying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits:
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
without
staying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits:
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
nsion.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
nsion.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
nsion.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
nsion.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7
Distro: Linux Mint 20 Ulyana base:
staying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compile
Same here, UX433FN.
Linux asus-ux433fn 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22
03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/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/18
It's not restricted to Xubuntu, but this bug affects all *buntu I've
tested in the last week. Now I'm testing Ubuntu Budgie on a notebook HP
2910us and kernel 4.10.0-19-generic.
** Tags added: zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Tags added: kernel-bug-exists-mainline-4.11rc7 kernel-bug-exists-
upstream
--
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/1637347
Title:
Xubuntu 16.10: drm errors causing slow boot
S
Filipe,
as far as I can see you're having issue with usbhid module, not with i8042. But
since you get a very similar issue could be very related to my issue. Good luck!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
I have the same problemi with dell XPS 13 9360.
Here the wifi info
(https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info)
results, hope they are useful: http://paste.ubuntu.com/24848753/
--
You received this bug notification because you are a member of Kernel
Packages, which i
Happened after upgrade to 16.04.1, works with kernel 4.4.0-21-generic
works with kernel 4.9.0-040900-generic
--
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/1654374
Title:
Touchpad and to
Tested (even with broken wifi drivers)
4.11.0-041100rc1-generic #201703051731 SMP Sun Mar 5 22:34:02 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Issue still present.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-mainline-4.11rc1
--
You recei
Yes, the touchpad works just fine (see videos on OP).
--
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/1599306
Title:
[HP Pavilion dv2910us Entertainment Notebook PC] i8042 need to start
i8042.kbdreset=1, i8042.reset and i8042.nomux=1 with no luck.
I don't remember if I've tested atkbd, but I can give a new spin of boot
options tomorrow just to be sure.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Public bug reported:
While running the snapd suite using the amd64 kernel snap from the beta
channel (rev 59) we got this error running [1]:
2017-03-30 09:36:41 Error preparing
linode:ubuntu-core-16-64:tests/main/snap-auto-mount :
-
[ ... ]
Create a ramdisk with the testrootorg-store.accoun
The oroblem happens on an amd64 ubuntu-core system, no apport-collect in
there, please let me know how can I get the required logs on that
system.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Package
Yes, the same test is currently passing on rev 55 (edge) [1], the
/dev/ramX files are there after booting [2], and starting with rev 59
that files are missing and the tests fail [3].
[1] https://travis-ci.org/snapcore/spread-cron/builds/216734158
[2] http://paste.ubuntu.com/24306876/
[3] https://t
Finally I got the time to test (with a second SSD just to be sure) this
notebook with some quirks.
So far, the quirks I've found and tested are:
i8042.kbdreset
i8042.reset
i8042.nomux
i8042.dumbkbd
i8042.direct
i8042.noaux (irrelevant but tested anyway)
i8042.nokbd (completely kill the keyboard)
** Tags removed: kernel-bug-exists-mainline-4.11rc1
** Tags added: kernel-bug-exists-mainline-4.12.3
--
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/1599306
Title:
[HP Pavilion dv2910us E
I've created a script for lightDM to check the state of the keyboard with
xinput: it starts when X is loaded (tested with display-setup-script and
greeter-setup-script options) and check the state of the internal keyboard then
create a txt in my home.
The keyboard is correctly identified from t
Christopher, sorry for the delay but I completely missed your last
messages.
My bios is the latest version:
F.2D 08/26/2008
And the issue is still present with any *buntu I've tried.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Tags removed: bios-outdated-f.2d
** Tags a
I ran in a similar bug while running inotifywait on kernel:
3.19.0-30-generic #34-Ubuntu SMP Fri Oct 2 22:08:41 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
--
[3975766.571492] BUG: unable to handle kernel paging request at 812363a7
[3975766.571500] IP: [<812363a7>] 0x812363a7
[3
Public bug reported:
I ran in a bug similar to #922906 while running inotifywait on kernel:
3.19.0-30-generic #34-Ubuntu SMP Fri Oct 2 22:08:41 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
--
[3975766.571492] BUG: unable to handle kernel paging request at 812363a7
[3975766.571500] IP:
reaches 50 ° C the fans start to run and when that
temperature drops stop.
Perform testing to reinstall the acpi package and the problem appears again, to
uninstall everything starts working again.
Hope this helps.
Best regards,
Federico
--
You received this bug notification because you are a
Yesterday everything seemed to work properly, but today again the fans began to
malfunction.
I followed the steps in this post
http://www.webupd8.org/2014/04/prevent-your-laptop-from-overheating.html to
activate the drivers instead of intel_pstate acpi_cpufreq, and now everything
seems to work
]
Capabilities:
Kernel driver in use: 8139too
-
federico@P8H61:~$ sudo ethtool -i eth0
driver: 8139too
version: 0.9.28
firmware-version:
bus-info: :05:02.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
Ok. As soon as I can I'll push the bug to acpi_intel list and his
mantainer.
** Tags removed: kernel-bug-exists-upstream-3.14-rc2
** Tags added: kernel-bug-exists-upstream-3.14-rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Description changed:
- When I press the appropriate keys on keyboard (which ones specifically?)
- the slider appears on the upper right corner of the screen but the
- brightness doesn't change.
+ When I press the appropriate keys on keyboard (Fn+up/Fn+down) the slider
+ appears on the upper rig
Done.
http://marc.info/?l=linux-acpi&m=139290477319769&w=2
** Summary changed:
- 8086:2a02 [Dell Vostro 1310] no brightness control on (x)ubuntu 13.10
+ 8086:2a02 [Dell Vostro 1310] no brightness control on (x)ubuntu 13.10 / 14.04
--
You received this bug notification because you are a member
Today I've updated my 14.04 install and the osd no longer works.
Anyway the issue is present on the latest rc4 too.
Acpi_listen is reporting the keypressed code and the backlight files are
correctly updated but nothing changes.
** Tags removed: kernel-bug-exists-upstream-3.14-rc3
** Tags added: k
I found on dmesg those lines:
[ 16.487465] ACPI Warning: 0x1028-0x102f SystemIO
conflicts with Region \PMIO 1 (20131115/utaddress-251)
[ 16.487476] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[ 16.487481] ACPI
Christopher,
I reinstalled my Windows Vista from my restoration DVD just to check if
brightness works and I had many difficult installing it.
I was able to install an old XP and I discovered multiple errors about ACPI and
the brightness control has issues on this OS too: I can see the brightness
A customer of mine gave me his old notebook because he bought a new one.
The laptop is running an p to date Xubuntu 13.10 64bit. Now I'm
suffering similar issue with brightness control: when I press the
appropriate keys on keyboard the slide appears on the upper right corner
of the screen but even
Christopher,
thanks for your reply. I'll open the new bug ASAP.
--
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/1261853
Title:
8086:0166 [Dell Inspiron 15R 5521] Impossible to adjust the
Public bug reported:
A customer of mine gave me his old notebook because he bought a new one.
I trow in a new HDD and now the laptop is running an up to date Xubuntu
13.10 64bit. Everithing is working fine exept for the brightness
control: when I press the appropriate keys on keyboard the slider
a
Christoper,
I've tested the latest available Ubuntu 14.04 64bit iso from
http://cdimage.ubuntu.com/daily-live/current/ .
Same issues with both stock 3.13.0-8-generic and 3.14.0-031400rc2-generic (rc3
has not 64bit packages to test) from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D .
Hi,
I've also a Asus N550JK with a
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 0c)
With standard installation of Ubuntu 14.04.1 the ethernet card is NOT working.
Nevertheless I did try 3.16.7-031607-generic and 3.18
I performed a few preliminary test with both kernels and the wireless seems
working with only G networks.
I had to disable the N part on the routers.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
has someone found a workaround while we wait for the 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/1385137
Title:
[ASUS N550JK] Touchpad recognized wrongly as PS/2 mouse
Sta
1 - 100 of 167 matches
Mail list logo
