> I clearly dont have time to play with (1) and rebuilding/maintaining a
kernel in the hope of a non reproduction ; especially since I dont have
clear STR so it means making this my daily driver.
I'm not suggesting you to keep using/maintaining such a kernel, it's a
debugging data point to prove w
>From the trace this is triggered from a userspace IOCTL to remove a
framebuffer. This causes drm core to process atomic_remove_fb() as
work, and this will use the drm driver to do atomic modesets.
One of the things that happens for this is going to be recalculating MST
DSC configs (if appropriat
Can you tell me how many times you unplugged and plugged power adapter
during that log?
I see that hardware left s0i3 state 4 times over the one suspend cycle:
> 2024-11-19 21:47:42,898 INFO: ○ Hardware sleep cycle count: 4
I'm wondering if it's 1:1 mapping that it woke up and went back to
hardw
> sorry, I don't understand question. How do I change power adapter
state over the suspend sequence?
I'm meaning do either of these scenarios (specifically) trigger it:
1) You start your suspend sequence with it unplugged and then plug in and then
resume and the issue happens.
2) You start your
Did you happen to change the power adapter state over the suspend
sequence when this reproduced? There may be a problem with the firmware
handling of that event.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Your bad log seems to be showing the following problems.
Nov 10 22:38:42 Silencio kernel: [drm:drm_atomic_helper_wait_for_flip_done
[drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Nov 10 22:41:17 Silencio kernel: [drm:drm_crtc_commit_wait [drm]] *ERROR*
flip_done timed out
Nov 10
I suggest starting out with a mainline kernel build for 6.12-rc7.
* If you can reproduce the issue still there then you should check if
it's on the AMD bug tracker
(https://gitlab.freedesktop.org/drm/amd/-/issues). If it's not you
should raise an issue there.
* If you can't reproduce it on 6.12-
** No longer affects: amd
** Project changed: xf86-video-amd => linux
** Also affects: linux (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.launchpad.net
> Now the problem is I can't reproduce this so far. gnome-shell/xwayland
randomly exits at some point without any explanation (you can see it
just starts broken pipe at 12:31:54, no crash before, I need to find the
cause for that and report another bug :(
Maybe this:
https://gitlab.gnome.org/GNOM
> Attaching the Journal, the initial crash can be seen at 12:31:54, lots
going on there, but nothing root-causing this.
[ 3300.659129] WARNING: CPU: 1 PID: 65823 at
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
This is the assertion yo
Did you rebuild your initramfs after blacklist? Or maybe it's
"dell_laptop"?
--
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/2084971
Title:
Unable to change power modes from balanced
Sta
It still appears loaded. Or something else is providing the platform
profile.
--
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/2084971
Title:
Unable to change power modes from balanced
St
Oh this is a Dell system? I thought it was a Thinkpad sorry.
Can you please try to blacklist dell-laptop and restart your system?
Does it still reproduce?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
This appears to be a kernel driver or platform firmware bug. If it's new
to this kernel upgrade then it's more likely a kernel bug.
You should report it against the Thinkpad ACPI driver upstream.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: power-pro
(From the log you can see that you switched modes but then the kernel
changed it right back)
--
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/2084971
Title:
Unable to change power modes fr
Here is the fixed firmware binary upstream.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/ath12k/WCN7850/hw2.0?id=34d181d737527d903ebb363de6b2e3b1dcd42683
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Are you sure it's kernel? Or that's just a first guess? This could
easily be the systemd bugs.
https://github.com/systemd/systemd/issues/33626
https://github.com/systemd/systemd/issues/33462
You could try SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false to see if it
helps.
** Bug watch added: github.c
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
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/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 /
> but the GPU restarts are failing and the driver apparently deadlocks
or something (quite a bunch of mutex backtraces).
Yes; poor clean up/recovery should be tracked as a separate bug report
at https://gitlab.freedesktop.org/drm/amd/-/issues
--
You received this bug notification because you are
Possibly the same issue as fixed in mesa 24.1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
Please uprev mesa in the snap and see if it helps.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11138
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
--
You receiv
Can you check that? Was this maybe when the snap refreshed silently in
background? Or try a version without snap so you could use the host
mesa?
--
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
This is most likely a mesa issue. Have you upgraded mesa recently to
match when it showed up?
** 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.
htt
Actually the second is in 6.11 already.
> git describe --contains bf5641eccf71bcd13a849930e190563c3a19815d
v6.11-rc2~2^2~4
This is just an ask for 6.8.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
I see the same message on 0x60. Please pull in the this commit too.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bf5641eccf71bcd13a849930e190563c3a19815d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
> I don't know why i use dkms
When you installed the packaged version of ROCm you can use arguments to
decide whether or not to build the DKMS package. I don't expect you
really need it with this kernel version.
--
You received this bug notification because you are a member of Kernel
Packages,
I am tending to agree with Juerg, this is not Ubuntu's bug. They picked
up a stable update that fixed a problem, but it just so happens this
DKMS doesn't compile anymore.
I think the DKMS package will need to be re-spun due to this change.
I suggest reporting it here: https://gitlab.freedesktop.o
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
> 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
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
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
*
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(
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
> 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
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
** 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
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-oem-6.8 (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
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 Rembrandt-R: Suspe
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
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/2059215
Title:
HDMI Display Not detected: AMD Ryzen 5 7530U/L
For the plymouth part I think the suggestion above "plymouth.use-
simpledrm" makes sense.
--
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/2063143
Title:
Frequent boot to black display
St
** Description changed:
- Products with DCN 3.5 need linux-firmware to be added for noble.
- Matching kernel support is already in kernel 6.8.
+ [Impact]
+ Products with DCN 3.5 need linux-firmware to be added for noble. Matching
kernel support is already in kernel 6.8.
+ Without this firmwar
Public bug reported:
Products with DCN 3.5 need linux-firmware to be added for noble.
Matching kernel support is already in kernel 6.8.
6bfdacdd amdgpu: add DMCUB 3.5 firmware
cb59bf73 amdgpu: add VPE 6.1.0 firmware
3ca35ef5 amdgpu: add VCN 4.0.5 firmware
9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware
There is a second commit with a similar problem and really the one I
should have linked; this one is much more severe.
Here is that fix:
https://github.com/torvalds/linux/commit/37bee1855d0e3b6dbeb8de71895f6f68cad137be
It also came into 6.8.3.
3e52444ed190 ("ASoC: amd: yc: Revert "add new YC pl
The problem is that the "Pink Sardine" (Phoenix) laptops were being
applied to the "Yellow Carp" (Rembrandt) driver. This is improper
behavior and will cause other problems even if it fixed the immediate
microphone issue.
The Phoenix Lenovo laptops are supposed to have something in the ACPI
table
This is the upstream solution:
https://github.com/torvalds/linux/commit/861b3415e4dee06cc00cd1754808a7827b9105bf
Here is the commit from 6.8.3:
b44a34f581b0 ("ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo
21J2"")
--
You received this bug notification because you are a member of Kerne
Variable sized arrays have fallen out of fashion.
There are various patches like that which fix this issue every time it
crops up.
If you can still reproduce on the latest 6.9-rc kernels you should
report a bug upstream to get the remaining cases fixed. Or if you feel
comfortable you can write a
https://patchwork.freedesktop.org/patch/588305/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
(drivers/gpu/drm/amd
It was confirmed by many people this is fixed in the upgraded Framework
BIOS 3.05.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
*** 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
I have a suspicion the root cause of the white screen could be fixed in
BIOS 3.05.
https://community.frame.work/t/framework-
laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle-beta/48276
Can you still reproduce it with no workarounds, 6.8.0-20 and the BIOS
upgrade?
--
You received this bu
Probably nvidia.ko is missing a call to
drm_aperture_remove_conflicting_pci_framebuffers()
--
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/2060268
Title:
Phantom 46" monitor (simpledrm) s
This is because amd-pstate is in active mode but nothing is tuning EPP
most likely.
Try to upgrade to this version of power profiles daemon:
https://launchpad.net/~superm1/+archive/ubuntu/ppd
Then you can change the power setting using the Gnome or kde GUI for it
or by using powerprofilesctl.
-
> I'll also report back once I am able to test the new kernel.
I had a try and I was able to install it today on Noble by pulling the
deb packages for linux-image-unsigned-6.8.0-20-generic, linux-
modules-6.8.0-20-generic, linux-modules-extra-6.8.0-20-generic from
Launchpad manually.
--
You rece
> this system has a single DIMM which was provided by framework:
DDR5-5600 - 32GB (1 x 32GB)
My system is 8GB, single stick, same speed 5600 MT/s, same company
(A-DATA).
> Restarting firefox temporarily resolves the issue. This behavior
started to happen after I switched to X11.
You're the first
*** 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
> 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
> 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
** 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
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
*** 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
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
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
Can you double check the framebuffer FB related conf options in your
kconfig against those in Fedora?
--
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:
Annoying boot messages
The backend is a framebuffer driver. For example efifb which uses the
framebuffer set up by GOP in pre-boot.
If there are framebuffer drivers in tinydrm then maybe they matter for
those architectures.
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
V2 addressed comments and was reviewed.
--
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 variable refresh rate (VRR) on the Framework 16
Status in HWE Next:
New
Status
*** This bug is a duplicate of bug 2039926 ***
https://bugs.launchpad.net/bugs/2039926
** This bug has been marked a duplicate of bug 2039926
Error UBSAN: array-index-out-of-bounds amdgpu
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)
--
You received this bug notificatio
Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
AFAICT; these initramfs-tools package changes would cover it:
* hooks/framebuffer can be totally removed.
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it
--
You received this bug notification because you are a member of Kernel
Packages,
Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.
So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.
--
You
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049758
Title:
DP connection swap to break eDP behavior on AMD 7735U
Status in linux packag
#33, was your issue a one boot problem? Or it happens every time? Is
it tied to specifically that kernel + firmware, or is it also with older
kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.
I tested with a Framework 16 with a 14c3:0616 WLAN. With
20220329.git681281e4-0ubuntu3.28 it's completely unusable with my AP
unless I turn off power save with iwconfig (Unifi).
With to 20220329.git681281e4-0ubuntu3.29 it works as expected.
** Tags removed: verification-failed-jammy
** Tags adde
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Triaged => Won't Fix
--
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 d
Internal team at AMD has tested an OEM RMB that doesn't need the DP swap
change to check for any potential regression. They tested using OEM
6.5-1014 kernel. This testing well.
Anson will confirm results on the system needing DP swap after he's back
from holiday.
--
You received this bug notif
Internal team at AMD has tested across a number of different OEM PHX
systems using OEM 6.5-1014 kernel. This is testing well.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu
The two missing commits are specified in comment #4.
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1180974eb33ac67903269b71f35a489a2b77e5e9
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/6b91b2ef6f4173099c1434e5d7c552e51814e26e
** Tags added: verification-failed-jammy
--
I examined the packages and I notice the MT7921 firmware (Which
confusingly goes by MT7961) is updated but "not" the MT7922 firmware.
Based on the above comments and below finding it seems that the MT7921
hardware is fixed with the update but not the MT7922 (which also
confusingly uses the mt7921e
Did you put any other files in /lib/firmware? Maybe the output of
$tree /lib/firmware
Would explain what is going on.
--
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/2049220
Titl
Do you perhaps have the older version in /lib/firmware/updates?
--
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/2049220
Title:
Update firmware for MT7921 in order to fix Framewor
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,
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
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
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
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.
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
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
> 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
> 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
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
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
** 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
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
> 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
> 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
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
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
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
** 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
** 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
1 - 100 of 614 matches
Mail list logo
