** Tags added: jammy
--
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/2062951
Title:
Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu
24.04)
Status in Linux:
New
Sta
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1479136
Title:
[ubuntu 14.04.2] Artefacts in radeon driver on ke
*** This bug is a duplicate of bug 1678184 ***
https://bugs.launchpad.net/bugs/1678184
Followed the instructions from here and from duplicate, but
nvme_core.default_ps_max_latency_us=6000
did not work for me.
I'm now 0 and will try if this helps.
17.04 4.12 from mainline, Bios from May, De
Followed the instructions from here, but
nvme_core.default_ps_max_latency_us=6000
did not work for me.
I'm now on nvme_core.default_ps_max_latency_us= 0 and will try if this
helps.
17.04 4.12 from mainline, Bios from May, Dell Precision 5510 (from
12/2015), Samsung 512 GB
--
You received thi
*** This bug is a duplicate of bug 1678184 ***
https://bugs.launchpad.net/bugs/1678184
Dell Precision 5510
since ugrade from 16.04 to 17.04 this bug happens to me.
Currently I'm on the latest kernel from the standard release:
4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017
Tri
@Ivan: There is a slight possibility that the patch could work for you
(I don't know because I don't have that hardware). You could test by
installing kernel 4.7 from mainline.
The probable cause of the flickering is PLL-resonance which only seems
to affect LVDS and only on older GPU-chips. It is
Update:
Patch is part of the ubuntu mainline kernel 4.7
I'm running this kernel on ubuntu 16.04 and everything works as perfectly as
expected.
If anyone of you wants to try:
Read this:
https://wiki.ubuntu.com/Kernel/MainlineBuilds
here is kernel 4.7:
http://kernel.ubuntu.com/~kernel-ppa/mainli
Before I forget:
What can I do to get the patch incorporated in the current LTS release ?
(Xenial 16.04)
According to Christian König the patch is backwards compatible with the 4.x
series kernels.
I've tested it (compiled against 4.4.0.26) and it works without problem.
Who do I have to contact
Public bug reported:
just happened...no idea why
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
ProcVersionSignature: Ubuntu 3.13.0-89.136-generic 3.13.11-ckt39
Uname: Linux 3.13.0-89-generic i686
NonfreeKernelModules: wl
ApportVersion:
UPDATE:
Patch submitted by Christian König
Patch applied by Alex Deucher
https://lists.freedesktop.org/archives/dri-devel/2016-June/110724.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
@Tim,
Sorry to hear about that, so close to the finish.
Thank you anyway for all the help.
--
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/1479136
Title:
[ubuntu 14.04.2] Artefacts in
@Marius, Yes, thanks, that is exactly what I needed.
That one line plus your card model. Excellent.
I need it from as much people (i.e. affected hardware) as possible .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Tim, Mrerexx and anyone who is hit by this bug:
I am testing a lot at the moment and I need your help.
please boot that problematic kernel with bootoption: drm.debug=4
Then, in a terminal type this:
grep -i "\[drm:" /var/log/kern.log | grep div | tail
post the results here, I'm going to need it
OK, about the bisect:
c2fb3094669a3205f16a32f4119d0afe40b1a1fd is the first bad commit
Date: Sun Apr 20 13:24:32 2014 +0200
drm/radeon: improve PLL limit handling in post div calculation
This improves the PLL parameters when we work at
the limits of the allowed ranges.
I rever
Maybebut it is not supposed to cause such weird side effects
I ended up doing a git bisect myself on this issue:
https://bugs.freedesktop.org/show_bug.cgi?id=87682
(because it's an upstream bug)
Anyone any tips how to continue ?
** Bug watch added: freedesktop.org Bugzilla #87682
https:/
Mrerexx, could you perhaps test if your VGA output on that laptop is unaffected
?
My VGA-output seems to work without problems and only LVDS seems affected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Mrerexx, I can confirm this... I have the EXACT same laptop model (I rarely use
nowadays) and just checked it.
Indeed this model still has the same problems with the newer kernels.
Since this is an upstream bug, please follow this link [
https://bugzilla.kernel.org/show_bug.cgi?id=83461 ] and me
According to bugzilla:
(https://bugzilla.kernel.org/show_bug.cgi?id=83461)
32167016076f714f0e35e287fbead7de0f1fb179 seems to be the first bad
commit
bug seems to affect only the RS880 series and older
Christian König proposed a patch to limit the reference divider to fix
this and it seems to wo
Cool thanks. Hoping we can make some headway as I like the laptop and would
like to keep it.
On May 7, 2015 4:00 PM, "Gabriel Lemieux"
wrote:
> Don't loose your time, I tried. Noting is corrected for us. Also, I
> called the support. They will do what they can to get an answer. I also
> ask them
Thanks. I gave them a call, but then I noticed a new BIOS was posted.
Unfortunately it looks like I'll have to reinstall Windows in order to
flash it. I did not see anything directly related to this in the release
notes, but I'll give it a try.
I think I must get some sleep :P. I don't remember if
@Gabriel: Have you heard anything back from HP Support yet? I just got a
Spectre x360 and (obviously) have the same lack of audio. I have started
a case with HP, but just wanted to check if there was any progress or if
there was anything specifically I should tell them. I'm new to bug
tracking.
--
onsider this an real bug, especially because the
> postgres error is misleading and incomplete.
SHMALL is measured in pages, whereas SHMMAX is measured in bytes. They
shouldn't be set to the same values as one another.
Regards
Thom
--
You received this bug notification because you
Tried to run apport-collect from within a chroot (after booting off of
the liveUSB again) and it segfaulted.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
Public bug reported:
A fresh install of the nightly build of Saucy on my Eee PC 1215B
successfully starts up grub, but grub hangs on a blank console screen
with "GRUB" in the top left corner, with a flashing cursor after.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
This still doesn't work for me. After installing grub starts after a
restart, but freezes on a blank console screen with "GRUB" in the upper
left corner, with a flashing cursor after it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
The newest saucy daily build crashes on the step "grub-installer:
Running chroot /target grub-install --force" for me. Is there a way I
can recover the installation from this point?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
26 matches
Mail list logo
