Turns out we didn't even need to modify the kernel for this. By choosing
simplefb and the 'tiny' DRM drivers for initrd, we get simpledrm.ko as
it existed in our older kernels...
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/462482
--
You
This bug was fixed in the package linux - 6.8.0-11.11
---
linux (6.8.0-11.11) noble; urgency=medium
* noble/linux: 6.8.0-11.11 -proposed tracker (LP: #2053094)
* Miscellaneous Ubuntu changes
- [Packaging] riscv64: disable building unnecessary binary debs
-- Paolo Pisati
I'm told this is in 6.8, and see 6.8 is in proposed.
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
** Tags added: flickerfreeboot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1965303
Title:
Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
False alarm. The screen blanking that GRUB_TERMINAL=console "fixes" was
actually caused by me using GRUB_TIMEOUT=3. Changing it back to the
default GRUB_TIMEOUT=0 also prevents the blanking mentioned in comment
#30.
--
You received this bug notification because you are a member of Kernel
> 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
Thanks for testing, so DRM_SIMPLEDRM needs to be built-in for it to work
properly? I guess that's fine then..
--
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/1965303
Title:
Migrate from
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Timo Aaltonen (tjaalton)
Status: Confirmed
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
--
You received this bug notification because you are
Also to prevent Grub from blanking the screen you need to uncomment:
GRUB_TERMINAL=console
Then you get a smooth transition from BIOS to kernel graphics
(simpledrm). But bug 1970069 still pops up after that.
--
You received this bug notification because you are a member of Kernel
Packages,
OK I've got simpledrm working now. It needed:
FB_EFI=n
FB_VESA=n
CONFIG_SYSFB_SIMPLEFB=y
CONFIG_DRM_SIMPLEDRM=y
So now I have working graphics very early:
[0.588237] [drm] Initialized simpledrm 1.0.0 20200625 for
simple-framebuffer.0 on minor 0
...
[7.153876] [drm] Initialized
> This requires Kernel config changes:
>
> FB_EFI=n
> FB_VESA=n
I'm testing this and it's a step backwards. The screen just turns black
for the first 6 seconds or so while Plymouth waits for i915drmfb to
start instead (might be Plymouth's fault for being too picky?). FB_EFI
was better because it
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.
** No longer affects: gdm3 (Ubuntu)
** No longer affects: gdm3 (Ubuntu Lunar)
** No longer affects: gdm3 (Ubuntu Mantic)
** Description changed:
[ Impact ]
The fbdev subsystem has been deprecated for a long time. We should drop it in
favour of using simpledrm with fbdev emulation layer.
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.
The GDM issue sounds like something we do want fixed, but not here. It
should get its own bug.
This bug should involve no SRUs.
--
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/1965303
> 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,
Oh, wait. You are just fixing the race condition?
Please the SRU documentation then. Right now I read "We should drop it
in favour of using simpledrm with fbdev emulation layer" which is very
misleading as to what you're actually proposing to do.
--
You received this bug notification because
> it will expose the race condition to GDM
What race condition, please? If this is the justification for the
proposed SRU, then I'd expect to see that explained, but I don't see any
explanation.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Oh, this?
> When this stack is enabled, it changes boot timing such that some
drivers may take a longer time to boot and GDM may hang in a black
screen.
In that case, why can you not revert the kernel config change in the HWE
backport to Jammy?
--
You received this bug notification because you
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.
I don't quite follow why we're calling this an issue. It's an
enhancement that should target 24.04 only.
--
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/1965303
Title:
Migrate from fbdev
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:
This has been marked as fixed in mantic, but this bug does not say what
the plan is for lunar, which is still the supported upgrade path from
jammy.
** Changed in: gdm3 (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of
can't target NN yet, so it'll stay open for mantic for now
--
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/1965303
Title:
Migrate from fbdev drivers to simpledrm and DRM fbdev emulation
Right, I don't think we'll get this in mantic yet, I'll send it for
linux-unstable first (and then it'll get enabled by mainline builds).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yes I was referring to the linux task.
--
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/1965303
Title:
Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Status in
The kernel part yes. The bug fix in GDM to prepare for whenever the
kernel part happens I would think not.
--
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/1965303
Title:
Migrate from
This seems like a significant enhancement that will affect the graphics
backends chosen by Plymouth and some desktop sessions, particularly
virtual machines. Surely this needs a feature freeze exception?
--
You received this bug notification because you are a member of Kernel
Packages, which is
I've uploaded the jammy backport of this patch into the queue, so
assigning it to myself. As I have readily seen this problem on my own
test kernels I'll validate it with a local kernel with the matching
kconfig options when it's accepted. This can then be done in advance of
waiting for matching
** Changed in: gdm
Status: Unknown => 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/1965303
Title:
Migrate from fbdev drivers to simpledrm and DRM fbdev emulation
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=2022385.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Description changed:
- The fbdev subsystem has been deprecated for a long time. We should drop
- it in favour of using simpledrm with fbdev emulation layer.
+ [ Impact ]
+ The fbdev subsystem has been deprecated for a long time. We should drop it in
favour of using simpledrm with fbdev
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is
still open.
** Changed in: gdm3 (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
The fbdev subsystem has been deprecated for a long time. We should drop
it in favour of using simpledrm with fbdev emulation layer.
This requires config changes:
- DRM=y
- DRM_FBDEV_EMULATION=y
-
FB_EFI=n
- FB_VESA=n (? check this)
-
- SYSFB_SIMPLEFB=y
+
** Package changed: gdm (Ubuntu Jammy) => 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/bugs/1965303
Title:
Migrate from fbdev drivers to simpledrm and DRM fbdev
** Also affects: gdm (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu
all current nvidia releases support simpledrm since last March, except
390 which has been EOL for some time now
--
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/1965303
Title:
Migrate
thanks for the heads-up, yeah that'd need to be fixed in jammy as well
(for gdm) when a hwe kernel supports simpledrm
I'm thinking if mantic 6.5 would be the first candidate
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: New => Fix Released
--
You received this bug
I'm adding a task for gdm to this bug. The reason is that if simpledrm
is used, we've found race conditions that occur where the transition
from simpledrm to the proper KMS driver may race with gdm starting up
the login screen.
When gdm loses the race you end up with a black screen. So please
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
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/1965303
Title:
Migrate from fbdev drivers to
40 matches
Mail list logo
