Similar behavior on HWE kernel in 22.04 on Thinkpad E16.
Linux ernie 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu
Nov 16 10:53:04 UTC 2 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
Tried some recent mainline kernels again. No luck with 5.13.19, but
5.14.13 is using both displays just fine. (Earlier I had tried 5.14.3
with no luck.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Still happens on 21.10's 5.13.16-051316-generic with a fairly new HP
Pavilion 15. The workaround from Arch doesn't quite help -- internal
monitor did work after that but external display is not detected.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Although I had planned to leave my laptop on LTS, eventually bluetooth
issues convinced me to move to 18.10. It works much better with the
newer kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yes, it continues.
--
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/1726061
Title:
Inspiron 5565 suspend issues after 17.10 upgrade
Status in linux package in Ubuntu:
Confirmed
Bug
I first had to resume from suspending this morning. I ran journalctl -b
before and after attempting to suspend again with the lid open. The
attachment includes the lines added in between.
** Attachment added: "journalctl_output"
Perhaps this is no longer a kernel issue or at least no longer a
regression. I am getting the same behavior with 4.14 and 4.13.11 and
even the kernel from 17.04 . Normally when I am suspending at the end of
the day I first close the laptop lid, then choose suspend from the menu
on the external
Upon initially booting either 4.13.11 or 4.14.0 I see 1 in active_count for
ACAD, and zeros elsewhere. When 4.14.0 has immediately resumed from suspend and
shows additional events from the lid and the power button, I have not touched
either of those in the course of attempting to suspend.
** Attachment added: "wakeup_sources_4.14.0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726061/+attachment/5008223/+files/wakeup_sources_4.14.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
But that bisection may be leading toward a dead end or at least a moot
point. The behavior which I am calling "bad" there is different from
what I am currently seeing in later RCs and in 4.14.0.
In, for example, my last "bad" commit 126f760ca94, upon suspend the
machine does actually suspend but
Still a few rounds of bisect remaining but this is where I am now:
# bad: [126f760ca94dae77425695f9f9238b731de86e32] rds: Fix incorrect statistics
counting
git bisect bad 126f760ca94dae77425695f9f9238b731de86e32
# good: [98e93e968e4947cd71c2eb69e323682daa453ee7] mac80211: Complete ampdu
work
To summarize my earlier comments: All the below relates to
suspend/resume of 17.10.
Suspend/resume works fine if I boot with the 4.10-based Ubuntu kernel
from 17.04, or any 4.13 mainline kernel starting from 4.13.5 .
The mainline kernels from 4.13 through 4.13.4, upon which the Ubuntu
kernel is
Tested with newest mainline kernels. 4.3.11 still works fine. 4.14.rc7
still fails to come out of suspend.
--
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/1726061
Title:
Inspiron 5565
sorry, meant to say 4.13.11, not 4.3.11
--
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/1726061
Title:
Inspiron 5565 suspend issues after 17.10 upgrade
Status in linux package in
Tested a couple more kernels and it seems that the issue I have with
4.13.4 is not present in mainline 4.13.5, nor in 4.13.9. Resume worked
fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
4.14-rc6 is even worse -- I can't wake the machine after suspend at all,
except by rebooting with long-press of the power button.
I tested other mainline kernels too. All 4.13-based mainline kernels I
tested behave similar to the shipped Ubuntu kernel, from 4.13.4 down
back to 4.13rc1.
** Summary changed:
- Inspiron 5536 suspend issues after 17.10 upgrade
+ Inspiron 5565 suspend issues after 17.10 upgrade
** Description changed:
- On my Inspiron 5536, 17.10 seems to work fairly well, unless I try to
+ On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to
Public bug reported:
On my Inspiron 5536, 17.10 seems to work fairly well, unless I try to
suspend. Suspend shuts off the display but doesn't seem to actually shut
off the CPU -- fans still run. When I move the mouse the display comes
back on but upon entering my password sometimes the session
Unfortunately not everyone has access to a new version of the client.
Would be nice if kernel compatibility with previous versions could be
restored.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looks good.
$ uname -a
Linux cookie 4.4.0-40-generic #60-Ubuntu SMP Fri Sep 23 16:45:45 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Tim Gardner, thanks for building that. Downloaded your build, installed
it, and rebooted. Both monitors work fine. Anything else I should check?
$ uname -a
Linux cookie 4.4.0-38-generic #57 SMP Tue Sep 6 12:47:10 UTC 2016 x86_64 x86_64
x86_64 GNU/Linux
[Sorry I didn't notice until now --
What would it take to apply this single commit to the stable kernel for
xenial?
--
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/1600092
Title:
radeon: monitor connected to onboard VGA
Public bug reported:
[In comments on 1579481 I mentioned that I had found and cherry-picked a
fix from upstream. I was asked to file another bug so that my hardware
information could be compared. apport will show kernel version 4.4.0-24
but the issue is reproducible on 4.4.0-28 as well-- just
As I mentioned on 1579481: The commit below (also from upstream) fixes
this for me. Hadn't noticed the one mentioned above... I only cherry-
picked this one on top of current xenial git source. Would be nice to
see this commit find its way into official Xenial kernels.
Confirmed: typing this on my second screen, connected via VGA, after
cherry-picking the commit I linked to in #28. Without that commit the
second screen was recognized but remained dark while connected to the
VGA port of my Kaveri-based desktop. Same monitor had been fine when
connected via DVI.
If we identify which commit from upstream fixed the issue, would it make
sense to release an update for Xenial?
Suspect it is this one but haven't tried to build yet:
https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690
--
You received this bug notification because
Public bug reported:
I built 3.19.0-18 from master-next (commit ccb645c) and my Dell 1545
boots, but X doesn't run. I was able to SSH to the machine and find this
in dmesg output:
[ 18.128077] [ cut here ]
[ 18.128117] kernel BUG at
With the recent kernel update this started working for me. Looks like it
is using the packaged firmware, not the updated one, which might mean
the updated one is not needed for this device.
$ uname -a
Linux kermit 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013
x86_64 x86_64 x86_64
+tgrundle does that patch from #9 work for you? It's not working for me.
I built per your instructions-- thanks for spelling it out like that.
Now I see in dmesg that it is loading the new firmware, but then it
repeatedly gets either authenticating with ... timed out or, when it
does manage to
29 matches
Mail list logo
