It's a pretty complicated backport to 6.1. there is a directory rename,
missing quirks that this builds on.
Considering 6.1 OEM will transition to 6.5 OEM eventually it might be
better to only target to 6.5 OEM.
They patches were nominated to 6.6.y already, but 6.5.y is EOL upstream
so it's up to
Boot a bad kernel, reboot the system, boot a good kernel.
>From the good kernel:
journalctl -k -b0 > good_kernel.txt
journalctl -k -b-1 > bad_kernel.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Since the PPA failed would you be able to manually build 6.5.13 to see
if it's fixed there?
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayla
Is this going to happen for noble? It should just be kernel config
changes at this point.
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Noble)
Imp
** Description changed:
- Some OEM platforms swap DP connections on the Rembrandt-R, which causes
- improper eDP behavior. AMD experimented with reproducing at CRB level to
- come out with a solution
+ [Impact]
+ Some OEM platforms swap DP connections on the Rembrandt-R, which causes
improper eDP
** Changed in: linux (Ubuntu)
Status: In Progress => 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/2036737
Title:
Enable dynamic boost control in ccp kernel driver
If it's a SAUCE only patch, I think it should be proposed here:
https://lists.ubuntu.com/mailman/listinfo/kernel-team
--
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/1970069
Title:
Annoyi
AFAICT those kernel commits are now landed in Ubuntu's kernel.
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1990052
I'm not sure where you posted that to, I didn't see it dri-devel. But I
think this is the first use of "splash" from the kernel command line
within the kernel. I think it needs to be documented.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
> This seems to be a bug in the kernel documentation.
Yeah I guess so.
> I'm now waiting until my conversation with Daniel Vetter is concluded
before formulating a plan for how to approach dri-devel.
👍
--
You received this bug notification because you are a member of Kernel
Packages, which is
> Also to prevent Grub from blanking the screen you need to uncomment:
Can you open another bug against GRUB to fix this default for Noble?
> Thanks for testing, so DRM_SIMPLEDRM needs to be built-in for it to
work properly
Yeah it should need to be built in.
> But bug 1970069 still pops up aft
Probably a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042867.
Try turning on proposed and getting 6.5.0-17.17 to see if it helps. It picks
up that fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed
** Changed in: linux-firmware (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Mantic)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
JFYI
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37 [1] is
reported to fix issues that were found in 36 in [2].
[1]
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/5217b76bed90ae86d5f3fe9a5f4e2301868cdd02
[2] https://bugzilla.kernel.org/show_bug.cgi?id=217239
** Bug wat
Have you already looked at everything Fedora is doing in this area?
They already have simpledrm; but from what you described I would have
thought they should still lose the fbcon race.
Is it just that they don't have systemd-fsckd patch? I would think they
still end up showing ERR/WARN kernel mes
> But the feature would still be gated on the "splash" kernel parameter
which is Plymouth-specific and may cause pushback from kernel
developers.
If the patch is the way you go another idea for you is to use the
"quiet" keyword to key off instead for this behavior which is already
used by the kern
> I don't really know if Fedora does that better or they just failed to
notice the bug.
I have Fedora 39 and Ubuntu both set up on a Z13 and Plymouth comes up in
Fedora with simpledrm; never see the console. That's why I was thinking
something might be missing and worth looking at.
* Fedora doe
Something "big" I notice different is that by default Ubuntu doesn't put
plymouth in the initramfs but Fedora does.
Maybe plymouthd really isn't running at the time systemd-fsckd is
running.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Yeah; so try forcing plymouth to the Ubuntu initrd like this:
echo "FRAMEBUFFER=y" | sudo tee /etc/initramfs-tools/conf.d/splash
Then if you rebuild the initrd you'll end up with plymouth in it.
This unfortunately DOUBLES the initramfs size; but it's because it puts all the
drm modules in there
You could detect both parameters to avoid that corner case.
Alternatively this is something I feel simpledrm will help you avoid
hitting too.
Otherwise it sounds good to me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I tested it on Noble with a hand built kernel and it at least does what
you planned (don't see any console messages), but also I'm not seeing
the OEM vendor logo stick all the way through. There's a really long
time of a black screen. Not sure if this is because it was an upstream
kernel and it's
Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black
screen.
Moving that to zero certainly helps. It's a lot better; but still not perfect.
Let me get things back to as close as possible to stock and capture logs and a
videos to compare with Ubuntu and Fedora with this exact sam
With your change Fedora and Ubuntu are now behaving relatively similarly.
* Both have a deficiency where the handoff from BGRT logo to Plymouth is doing
a modeset for some reason.
* Due to something in Fedora's GRUB it's a little clearer when GRUB starts.
Here's various artifacts if you want to
Noble got updated: https://launchpad.net/ubuntu/+source/linux-
firmware/20240202.git36777504-0ubuntu1
Still waiting for others.
** Changed in: linux-firmware (Ubuntu Noble)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
** Bug watch added: Linux Kernel Bug Tracker #216816
https://bugzilla.kernel.org/show_bug.cgi?id=216816
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=216816
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Would it be possible to bump up to 5.15.83 this cycle instead? Wanting
to see
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=249011f4c3b8a636f019c9740d5c4356d11031be
land.
--
You received this bug notification because you are a member of Kernel
Package
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1998106
Title:
Fix AMD-PState driver for Genoa C
> Just to give another data point, I've been running 5.19 from hwe-edge
(instead of hwe) for some time but I realized this suspend issue after
updating hwe-edge from 5.19.0.28.29~22.04.6 to 5.19.0.32.33~22.04.9.
I had a try with the latest 5.19 HWE kernel on a Lenovo Z13 I have on
hand (with a sim
I do think a double check against 6.3-rc4 would be worthwhile with no
parameters set.
The upstream issue is a bit confusing because it has both PSR and S/G
issues conflated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in
Public bug reported:
[ Impact ]
The current GPU firmware in place for DCN 3.1.4 based products fails to resume
from s2idle on newer BIOSes.
The following GPU F/W stack is confirmed to fix the problem and works
both with the older BIOSes and newer BIOSes:
9ee24ce0 amdgpu: Update SDMA 6.0.1 firmw
There are potentially two bugs at play here. One with scatter/gather
and one for PSR. They both manifest really similarly, so let's try with
both disabled.
There is a parameter that is introduced in 6.3 for amdgpu.sg_display.
Can you please explicitly set that to "0" along with the PSR disable
p
** No longer affects: linux (Ubuntu)
** Changed in: linux-firmware (Ubuntu)
Status: Triaged => Fix Released
--
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/1523565
Title:
If it's trending to be caused by PSR (which it sounds like it is), try to
revert this patch:
https://github.com/torvalds/linux/commit/751281c55579f0cb0e56c9797d4663f689909681
> Short, massive flickering while running with parameters
"amdgpu.dcdebugmask=0x10 amdgpu.sg_display=0",
Have a try with
OK, here's the patch being submitted upstream that should help this if
it's S/G caused:
https://patchwork.freedesktop.org/patch/532323/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bu
--
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/1912946
Title:
[ThinkPad E14 Gen2] Closing the lid does not trigger system suspend
Status in linux package in Ubuntu:
Confirmed
Bug desc
Thanks for checking. So good to know it hasn't regressed from stable in
5.10. Can you redo your 5.15 test with the firmware in place so we can
see if we're OK there or not?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In this case the kernel is the "messenger" for the page fault. This is
more likely to be a mesa or application issue than a kernel issue.
Can you please raise a ticket to the upstream mesa bug tracker?
https://gitlab.freedesktop.org/mesa/mesa/
** Also affects: mesa (Ubuntu)
Importance: Undec
AMD internal team has tested this updated firmware package against
Navi31 and Navi33 dGPUs on both OEM-6.1 and OEM-6.5 kernels. No new
problems introduced.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://
Are you up to date on the current version of mesa in 23.10?
23.2.1-1ubuntu2?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
I'd say that's very likely. That mesa upgrade just landed in the archive
a few days ago and the trace you reported looks more like how a mesa bug
manifests.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You r
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed
right after you reported this issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you ar
Ok in this case can you please open an upstream mesa bug?
** Changed in: mesa (Ubuntu)
Status: Fix Released => Triaged
--
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/2037641
Title:
I don't expect it helps your boot issue, but the UBSAN issue will be
fixed by this commit.
https://lore.kernel.org/amd-
gfx/78abc334-44ed-4632-8796-6bbe9c432...@amd.com/T/#me31ff6b88640b03be1a8edfc6fc8878ac78ca6bb
Please redo the test with 5.15.
--
You received this bug notification because you
Can you please upload your journal from the failure?
Also can you please experiment with rolling back to this one version of
this one firmware binary:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/gc_11_0_0_imu.bin?id=e32209f07556427c9b0b841bfb76ca71e8
Thanks, let me check with others on Monday if that's the right action
for your issue.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ub
Instead of reverting the IMU binary can you please upgrade the SMU
binary from the same 5.5 release ?
Navi31:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/smu_13_0_0.bin?id=39d6fcc73100ae4aeeec0194bbf102c672673edd
Navi33:
https://git.kernel.org/pub/scm
I believe the same thing should be done for Navi33 at same time, it
upgraded IMU as well. So these two commits are needed in Jammy and
Lunar:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/smu_13_0_0.bin?id=39d6fcc73100ae4aeeec0194bbf102c672673edd
http
Let's track the regression in
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
** Changed in: linux-firmware (Ubuntu Lunar)
Status: New => Confirmed
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => Critical
** Changed in: linux-firmware (Ubuntu Lunar)
Importance:
@Juerg:
Internal team looked at it, VP with Navi31 XTX boards, VNP with the others.
So the testing with OEM-6.1/OEM-6.5 on other Navi31 from earlier bug is
accurate.
Confirmed that upgrading SMU binary (just dropped into
/lib/firmware/updates/amdgpu) fixes the issue.
Considering the regression
** Tags added: verification-done-lunar
--
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/2038745
Title:
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
driv
Internal team has tested the Jammy update
(20220329.git681281e4-0ubuntu3.21) as well on NV31 XTX card and it looks
good there as well.
** Changed in: linux-firmware (Ubuntu Lunar)
Status: Fix Released => Fix Committed
** Tags added: verification-done-jammy
--
You received this bug notifi
Can you please share your kernel log from a boot that had the failure, and
without that parameter in place share the output of this script?
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py
--
You received this bug notification because you are a member of Kernel
Packages, which
The issue won't occur in Lunar. It's only specifically a problem with gdm when
a kernel has been configured this way.
It's not a problem in Jammy yet, but will be a problem when such a kernel gets
backported as HWE.
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Ne
*** This bug is a duplicate of bug 2038745 ***
https://bugs.launchpad.net/bugs/2038745
** This bug has been marked a duplicate of bug 2038745
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver
installed
--
You received this bug notification because you are a mem
Please share a kernel log of the failure after you've upgraded.
--
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/2038745
Title:
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop wi
Something is really fishy here - the 5.15 test is again missing firmware
for both i915, amdgpu and ath10k:
[2.345119] kernel: i915 :00:02.0: Direct firmware load for
i915/rkl_dmc_ver2_03.bin failed with error -2
[2.345122] kernel: i915 :00:02.0: [drm] Failed to load DMC firmware
This seems like a different bug to me. Can you please open a different
report and attach the relevant logs from the journal to it?
--
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/2036742
T
The problem is specifically when 24.04's kernel backports to 22.04 it
will expose the race condition to GDM. If that kernel will never
backport then it won't be a problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
> Oh, wait. You are just fixing the race condition?
Yeah; I see the confusion. This issue got caught up by making sure the
GDM race condition was fixed at the same as when this feature is
enabled.
Perhaps it's better to split the GDM part of it off to it's own bug
instead then.
> In that case,
I've split up the GDM for Jammy change into
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757
** No longer affects: gdm3 (Ubuntu 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/
> the firmware on mantic is zstd compressed, so mainline builds from the
past can't load the firmware..
As a hack then maybe just clone https://gitlab.com/kernel-
firmware/linux-firmware and put everything (uncompressed) in
/lib/firmware/updates/ to get by that.
Or run the check on Jammy instead.
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
I was just checking a Lenovo X13 for another issue and reproduced the
same thing. This is a duplicate of that other bug.
** This bug has been marked a duplicate of bug 2034619
[amdgpu] gnome-shell gets
This is the upstream fix for this issue:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
6.5.6 has the fix for preemption issue, it should get fixed when stable
updates come in Mantic.
--
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/2039868
Title:
amdgpu reset during usage of
For Framework please upgrade to bios 3.03. There is a very crucial bug
in 3.02 that can lead to stuff like this.
--
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/2039819
Title:
amdgpu cras
To explain some of the differences in the logs:
* UVD is the IP block that fails to init (so no "UVD and UVD ENC initialized
successfully").
* Once an IP block fails, next one isn't even tried (so no "VCE initialized
successfully")
* kfd doesn't initialize because amdgpu_amdkfd_device_init() won
If amdgpu.aspm=0 helps the issue, then can you please test this patch
against Mantic? If it helps I'll submit it.
** Patch added: "Disable ASPM for VI on all Intel systems"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/5711749/+files/0001-drm-amd-Disable-ASPM-for-VI
Great, thanks! Let me know if the patch works too.
--
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/2036742
Title:
amdgpu crash on Mantic
Status in linux package in Ubuntu:
Confirmed
Also reported at #2036742
It's caused by the use of flexible size arrays.
Here's the fixes from linux-next that should help it.
https://cgit.freedesktop.org/drm/drm/commit/drivers/gpu/drm/amd/pm/powerplay/hwmgr?id=0f0e59075b5c22f1e871fbd508d6e4f495048356
https://cgit.freedesktop.org/drm/drm/commi
resume after suspend: screen not detected
+ dGPU suspend fails under memory pressure
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2362
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed
Great! Thanks I've posted it for review.
https://lore.kernel.org/amd-
gfx/20231023134514.144863-1-mario.limoncie...@amd.com/T/#u
Yes the "UBSAN: array-index-out-of-bounds" traces are to be fixed in
6.7. If you want to pull those patches early I can point you at them.
--
You received this bug
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=217947
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2874
https://gitlab.freedesktop.org/drm/amd/-/issues/2874
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2874
Importance: Unknown
Status: Unknown
--
You received this bug notification because
I'd say let's track the out of bounds stuff in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039926
** Summary changed:
- amdgpu crash on Mantic
+ VI dGPU fails to initialize on Intel platforms w/ 5.14+
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You
/+packages
I've also uploaded the mutter package into the proposed queue for SRU
team to look at.
** Changed in: mutter (Ubuntu Mantic)
Status: Fix Committed => In Progress
** Changed in: mutter (Ubuntu Mantic)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
> - I still have an error message in dmesg:
In this issue you actually discovered two independent bugs.
The first was the regression, the second was the UBSAN issue.
* The first fix is what you tested.
* The second fix wasn't picked up yet.
This is the commit that is now landed upstream for the s
That's good news. Just today there was a new patch posted that might
help the remaining PSR issue. Can you please apply this on top of
6.4-rc5?
https://patchwork.freedesktop.org/patch/541535/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
OK let's look for results with that patch when you have time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2009952
Title:
[amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.
FWIW I don't feel this is likely a kernel regression but rather a
platform firmware problem.
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=219101
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Pac
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
--
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/2072612
Title:
Lenovo touchpad intermittently stops working with i2c_des
Perhaps a dumb question - but why even bother to put any of the GPU
binaries in the initramfs? There should be a good enough display from
the pre-boot framebuffer that none of them should be needed with
simpledrm.
Punt i915.ko, xe.ko, amdgpu.ko, nvidia.ko out of the initramfs and let
them get loa
> But building a new kernel and switching to it without deeper
experience and a fallback would be too hard for me.
No need to build a new kernel. There are binaries in the link that was
posted above. You can grab some of those to try. Just note that you
need to turn off secure boot if you have i
This appears to be a different problem even if it leads to same symptom.
Please open a separate issue.
--
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/2064595
Title:
AMD Rembrandt & AMD R
Try adding thunderbolt.host_reset=0 to your kernel command line.
Suspect it's the changes that came in
https://launchpad.net/ubuntu/+source/linux/6.8.0-38.38:
- thunderbolt: Introduce tb_port_reset()
- thunderbolt: Introduce tb_path_deactivate_hop()
- thunderbolt: Make tb_switch_reset(
Thanks for confirming it. You can also try to add thunderbolt to
/etc/initramfs-tools/modules to see if that's enough to fix the issue
instead of the kernel command line workaround.
I suspect it's not though, and that a hook will be needed to add:
* /lib/udev/rules/90-bolt.rules
* bolt.service
*
Thanks for checking. I believe what's going on is that it resets the
topology, but the policy to re-authorize it doesn't happen because bolt
is missing until the rootfs is loaded. So initramfs needs a hook to
include bolt.
--
You received this bug notification because you are a member of Kernel
> That's an unsupported DKMS, not a kernel problem. Is there any reason
why you don't use the kernel's amdgpu driver?
The DKMS driver takes an upstream snapshot of amdgpu for use with older
kernel versions. As I notice that in the above error log the DKMS
driver is from "6.8.5-2009582.24.04" you
This definitely isn't an Ubuntu kernel bug, I will reject it as such.
You can file an issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues if you have problems
stemming from that script.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificati
For some unknown reason this only seems to be reported on some people's
Framework 13 AMD laptops.
FYI - there are two workarounds for those currently encountering this
issue.
* On the kernel command line: amdgpu.sg_display=0
* Change the BIOS settings from Auto to UMA_Game_Optimized.
** Bug wat
I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.
--
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
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445
** This bug has been marked a duplicate of bug 2056445
external monitors flash white with every interrupt
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445
** This bug has been marked a duplicate of bug 2056445
external monitors flash white with every interrupt
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445
** This bug has been marked a duplicate of bug 2056445
external monitors flash white with every interrupt
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
FWIW it's in drm-fixes now.
https://cgit.freedesktop.org/drm/drm/commit/?id=2f14c0c8cae8e9e3b603a3f91909baba66540027
--
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/2057424
Title:
No var
** Also affects: linux-firmware (Ubuntu Noble)
Importance: Undecided
Assignee: Jose Ogando Justo (joseogando)
Status: New
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Mantic)
Importance: Undeci
> Should this fix the flickering issue? I'm happy to test it out.
It will fix a colored flickering; but not the white screen (if that is
what you're observing). It also fixes issues with suspend/resume that
were present in earlier 6.8-rc kernels but fixed by the final version.
> I'm curious abou
> Am I missing something to get the proposed
kernel?
I guess the same reason it's not migrating is the reason you can't
install it? Maybe some kernel team members can comment.
> It sounds like GTT access is what causes this issue, and that using the
bios option won't guarantee that it will never
*** This bug is a duplicate of bug 2046504 ***
https://bugs.launchpad.net/bugs/2046504
** This bug has been marked a duplicate of bug 2046504
AMD GPU display is blank when set lower resolution than native mode on eDP
--
You received this bug notification because you are a member of Kernel
201 - 300 of 624 matches
Mail list logo
