Please reboot, try to connect them again, and after it fails run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
Please also specify how long ago and in which Ubuntu release it was
working.
** Summary changed:
- I cant connect my bluetooth keyboard, mouse and jbl head
** Summary changed:
- Horizonral line artifact/ghosting when scaling windows to a certain width
+ [Intel N95] Horizonral line artifact/ghosting when scaling windows to a
certain width
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
** Package changed: mesa (Ubuntu) => linux (Ubuntu)
** Pack
There's probably nothing to do in the kernel task here.
--
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) shown in Settings after installing t
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761623/+files/RfKill.txt
--
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
Public bug reported:
no bluetooth detected
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: a
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761624/+files/UdevDb.txt
--
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
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761626/+files/acpidump.txt
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Phantom 46" monitor after installing
Public bug reported:
After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.
It looks like the phantom monitor is /dev/dri/card0 which is still controlled
by simpledrm, while Nvidia uses /dev/dri/card1.
---
ProblemType: B
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761621/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761615/+files/Lspci-vt.txt
--
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/20
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761613/+files/IwConfig.txt
--
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/20
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761612/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761616/+files/Lsusb.txt
--
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
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761625/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761614/+files/Lspci.txt
--
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
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761617/+files/Lsusb-t.txt
--
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/2060
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761622/+files/ProcModules.txt
--
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
It looks like i915 avoids this by deleting /dev/dri/card0 (simpledrm)
after /dev/dri/card1 (i915) exists. Although I don't really know exactly
where that's implemented.
** Summary changed:
- Phantom 46" monitor (simpledrm) after installing the Nvidia driver
+ Phantom 46" monitor (simpledrm) show
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761620/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761611/+files/AlsaInfo.txt
--
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/20
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761619/+files/ProcCpuinfo.txt
--
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
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761618/+files/Lsusb-v.txt
--
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/2060
Sorry, but I don't believe that for a second. The fix is not difficult
or time-consuming, and they already had a patched version.
"Eventually 6.5+ based jammy kernels will not have it in lrm either. And we
will only keep it against older kernels in bionic..jammy (ga only)"
Unless they reverse ^th
** Summary changed:
- Bluetooth earbuds not being 'set up' on new machine
+ T60 Bluetooth earbuds not being 'set up' on new machine
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Everyone is very busy with the 24.04 release as well as other
responsibilities. So don't take silence to imply anything :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad
@vanvugt: I appreciate you opening the Jammy task, but I'm not holding my
breath for this to get fixed after reading
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189/comments/1
Basically, they knew this bug was coming when they removed the 390 package, but
they
It seems a few different manufacturers have products called 'T60' so
please mention the brand in the bug title.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu
I don't think the "simpledrm" reason listed in 2035189 holds up. Unless
you're in a virtual machine, SimpleDRM is only used for the few seconds
of initrd, or for the duration of the disk unlock prompt. Even if old
Nvidia drivers can't support SimpleDRM, they can support legacy
framebuffers which we
It's not bug 2049927 because that's amdgpu and this is i915.
** This bug is no longer a duplicate of bug 2049927
[amdgpu] since Linux kernel 6.5.0-14 external monitors are no longer detected
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Summary changed:
- since Linux kernel 6.5.0-14 external monitors are no longer detected
+ [amdgpu] since Linux kernel 6.5.0-14 external monitors are no longer detected
** Tags added: amdgpu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
In case anyone is wondering, you won't start to see an improvement until
you have at least:
linux >= 6.8.0-20.20 and
plymouth >= 24.004.60-1ubuntu6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
@Dmitry: Ubuntu devs made a conscious decision to drop the 390 driver and some
other branches:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189
So if they haven't fixed the Jammy version by now, it's probably not going to
happen.
Good news though: I patched the
Public bug reported:
System hung indefinitely during a Software Update prompt. The update
related to audio. I had to hard restart the system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Unam
** Tags removed: kinetic
** Tags added: mantic
** Tags added: fixed-in-linux-v6.9-rc1 fixed-upstream
** No longer affects: kwin (Ubuntu)
** No longer affects: mutter (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed
*** This bug is a duplicate of bug 2003031 ***
https://bugs.launchpad.net/bugs/2003031
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2003031, so it is being marked as such. Please look
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Summary changed:
- Kernel 6.8 - S
Public bug reported:
I am trying to update ubuntu to 23.10 from 21.04 but it appears I have
both versions installed at the same partation at the same time...
Found Ubuntu 21.04 (21.04) on /dev/sda2
Adding boot menu entry for UEFI Firmware Settings ...
sudo do-release-upgrade
Checking for a new
** 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/1970069
Title:
Annoying boot messages interfering with splash sc
Please also follow these steps in case there is a separate userspace
crash:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
It appears the recurring problem here is:
simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem)
WARNING: CPU: 19 PID: 4751 at drivers/gpu/drm/drm_gem_shmem_helper.c:319
drm_gem_shmem_vmap+0x1a5/0x1e0
** Summary changed:
- Xorg crash
+ Crash
** Package changed: xorg (Ubuntu) =
** Package changed: ubuntu => nvidia-graphics-drivers-535 (Ubuntu)
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Incomplete => New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: nvidia
--
You received this bug notification becaus
That commit is not meant to reflect the outcome of discussions that
happened after it (comment #93). It's just an intermediate "UNRELEASED"
commit reflecting intermediate development.
My intent with shared repos like this is to show what is being worked on
before anything is released to the archiv
I would not give up on NVIDIA just yet. No one else with NVIDIA hardware
is reporting an issue like this so it's just as likely a problem with
some other kernel driver or system component.
That said, unless you want to experiment with swapping components (like
the NVIDIA card or RAM) then changing
That's because I ran out of ideas, sorry.
** Summary changed:
- Random Freezing
+ Random whole system lockups
** Summary changed:
- Random whole system lockups
+ Random whole system lockups on Lenovo ThinkStation P350 Tiny
--
You received this bug notification because you are a member of Kern
Thanks. I've reflected those changes in git:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest/
--
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:
Anno
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bu
If you are suggesting moving the logic from plymouth into initramfs-
tools then please start by duplicating the code you'd like moved into
initramfs-tools. That would be efficient since you have commit access to
initramfs-tools, and would mean I only have to deal with plymouth here.
--
You receiv
That change is in plymouth, but hooks/framebuffer is in initramfs-tools.
If you're suggesting moving the code from plymouth into initramfs-tools
then I kind of understand, but it's not directly related to fixing this
bug.
--
You received this bug notification because you are a member of Kernel
Pa
event this bug 1970069.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
In proposed: https://launchpad.net/ubuntu/+source/linux/6.8.0-19.19
** Changed in: linux (Ubuntu)
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/2
Here's a fix for plymouth/noble.
The source is in:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest
We skipped ubuntu5 because that technically existed in bug 2054769 for
10 days already.
Also note this will cause some temporary initrd bloat while the
initramfs-tools cha
Thanks. It seems I asked for too much of the wrong information there.
Please:
1. Remove drm.debug=0xff but keep loglevel=8
2. Reinstall the Nvidia driver using the 'Additional Drivers' app.
3. Reboot
--
You received this bug notification because you are a member of Kernel
Packages, which is su
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 receive
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/462482
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a me
** Description changed:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many machines,
when the user should be seeing only the BIOS logo and/or Plymouth splash
screens.
[ Workaround ]
On most machines you can hide the problem by using these kernel parameter
Seems it's fairly easy to make a working solution in initramfs-tools
alone, but there's a compromise. If I only include tiny/simple
framebuffer drivers in initrd then i915 starts so late that Plymouth
doesn't use it, and bug 2054769 can occur on some machines. If I include
all the current drm drive
Plymouth would still need patching in order to optimize the drm modules
in debian/local/plymouth.hook
** Changed in: plymouth (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I think the delay I'm seeing is a feature of Plymouth, not a bug:
"ignoring since we only handle SimpleDRM devices after timeout"
As much as I dislike it perpetuating bug 1869655, this feature does
prevent bug 2054769 from reoccurring.
But this raises the question: is it worth putting i915, am
1. Edit /etc/default/grub and add them to GRUB_CMDLINE_LINUX_DEFAULT=...
2. Run: sudo update-grub
3. Reboot.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Fedora 39:
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
Ubuntu 24.04:
# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not set
In the kernel source, DRM_SIMPLEDRM recommends SYSFB_SIMPLEFB if you
want it to work on UEFI and VESA. And we do enable SYSFB_SIMPLEFB whose
help text says:
> you should still keep
Perhaps we're approaching it wrong. Try going back to the Ubuntu kernel
(6.5) and enabling debug messages with these kernel parameters:
drm.debug=0xff loglevel=8
then collect another prevboot.txt after the freeze occurs.
--
You received this bug notification because you are a member of Kernel
Maybe try an even older kernel next, and/or disabling the Nvidia GPU in
the BIOS if there's an option to do so.
--
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/2054121
Title:
Random Freez
That might explain the strange behaviour I'm seeing where simpledrm
doesn't seem to be usable until a few seconds into the boot (maybe not
till i915drmfb is mentioned in the log?).
/boot/config-6.8.0-11-generic:# CONFIG_FB_EFI is not set
It was removed as part of bug 1965303. But I was hoping sim
Hopefully I'm wrong about the need for all the 'tiny' drivers and
simpledrm is in a class of its own. But I'd like to better understand
what the backend of simpledrm is and how much we can assume that it will
just work(tm).
--
You received this bug notification because you are a member of Kernel
Also hooks/plymouth is equally to blame and needs modifying, as
mentioned in comment #49 which I forgot.
Looking at my older 6.6 kernel however I'm reminded that some kernels
may have the drivers we need in the form of tiny drm (which is the
backend for simpledrm??):
/lib/modules/6.6.0-14-gener
> * hooks/framebuffer can be totally removed.
By chance I was testing on a desktop that has the Nvidia driver
installed (though no Nvidia card today, Intel only). Disabling
hooks/framebuffer had relatively little impact. In the end it was
hooks/framebuffer-nvidia that also needed disabling to remo
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
--
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 interfering with splash scr
Please try an older v5.x kernel
--
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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups
Since my kernel patch for bug 1970069 is being blocked upstream at the
moment, reducing the loglevel to 3 is becoming more of a priority.
Otherwise I don't see us making sufficient progress on bug 1970069.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Thanks for the bug report. This is a common problem and is almost always
due to a bad connection or low quality cable. Please try unplugging and
replugging the cable at both ends. If that doesn't solve it then please
try a different cable. For better performance and reliability on a
Lenovo G50-70,
** Description changed:
I need the snd-aloop module (and its dependencies: snd, snd-timer, snd-
pcm) on an AWS server.
- The linux-modules-extra-aws package (or the one this drags in) used to
provide that module (as a fix for
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/197058
This problem persists in Kernel 6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2054598
Title:
AWS kernels lacking sound support (even snd-aloop missing)
Status in linux-aws pack
It seems there was an update to 'linux-hwe-6.5' a couple of days ago so
we were likely already tracking the correct component.
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
Also warning: In order to test such unsigned kernels I think you need to
disable Secure Boot in the BIOS.
--
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/2054121
Title:
Random Freezing
S
Please try the newest one first:
https://kernel.ubuntu.com/mainline/v6.8-rc7/amd64/
And if the freezes still happen in kernel 6.8 then try some older
versions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
I'm running out of ideas. If it was my machine I would try booting a
different kernel:
https://kernel.ubuntu.com/mainline/?C=M;O=D
And if that didn't work then I would even try changing the RAM in the
machine.
--
You received this bug notification because you are a member of Kernel
Packages,
Please check the headphone is in pairing mode, and try pairing something
else like a mouse if you can.
I can see only one other bug with the same Bluetooth chip having similar
issues: bug 1887968
** Summary changed:
- i could not able to connect my bluetooth headphone or for context any
headpho
Thanks. Please also check that ssh did work before the freeze :)
** Changed in: nvidia-graphics-drivers-545 (Ubuntu)
Status: Incomplete => Invalid
** No longer affects: nvidia-graphics-drivers-545 (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received th
https://salsa.debian.org/gnome-
team/mutter/-/commit/7f3b3fa18bca658cbc6c7fa98295b169c8f38793
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
** Changed in: initramfs-tools (Ubuntu)
Status: Opinion => 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/bugs/1970069
Title:
Annoying boot messages interfering with splash screen
Indeed this doesn't seem to have happened since 2020.
** No longer affects: mutter (Ubuntu)
** No longer affects: plasma-desktop (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You receive
You will actually get Wayland by default if the Nvidia driver is
uninstalled. So try that as well as Xorg (selectable on the login
screen).
--
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/20
Thanks. Next I would resort to drastic measures: Uninstall the Nvidia
driver completely. Then wait and see if that's eliminated the freezes.
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: nvidia
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
St
Maybe initramfs-tools does still need changing. plymouth-start.service
seems to run twice, and I get the feeling only the second instance is
actually succeeding in splashing on screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
You can test if the above suggestion will work for you by adding these
kernel parameters:
loglevel=3 fsck.mode=skip
--
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:
Annoy
I've analysed a couple of Noble systems today and don't think initramfs-
tools needs improving (although it might not hurt). On both systems,
plymouth-start was within 1 second of simpledrm starting (same
timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences the
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
** This bug has been marked a duplicate of bug 2028165
nvidia-dkms-* FTBS with linux 6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-
Seeing some strange "Device or resource busy" errors on the
/usr/bin/nvidia-debugdump file, seemingly due to Nvidia lossage. Closing
as likely unrelated to the packaging.
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Invalid
--
You received this bug notification becau
Public bug reported:
This concerns nvidia-utils-535 (535.161.07-0ubuntu3) in Ubuntu noble.
I had already installed nvidia-cuda-toolkit, and then...
# apt-get install nvidia-utils-535
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packag
You can add new parameters to /etc/default/grub as part of the
GRUB_CMDLINE_LINUX_DEFAULT.
Then run this command to install the changes:
sudo update-grub
and reboot.
** Summary changed:
- My screen radomly starts flickering
+ [amdgpu] My screen radomly starts flickering
** Summary changed:
It changes the backlight behaviour in the kernel.
--
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/2055153
Title:
[Lenovo Legion Pro 7 16IRX8H] Boots slowly or not at all when NVID
I was wrong. Kernel 6.8 is now exhibiting the same bug.
** Changed in: linux (Ubuntu)
Status: Fix Released => 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/2040977
Title:
Kernel 6.8 has fixed it for all machines tested so far.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Noble is now shipping with SimpleDRM enabled in kernel 6.8, so the next
step is comment #49 (which would also resolve bug 1869655).
--
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
T
Also focal (20.04.6) does have the bug now, per comment #23.
** Tags added: focal
--
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 interfering with s
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.
https://bugs.launchp
For the slow boots, try experimenting with kernel parameters like
acpi_backlight=vendor and for more detailed info see
https://wiki.ubuntu.com/Kernel/Debugging/Backlight
For the failed boots I would also recommend trying the kernel parameter:
nvidia-drm.modeset=0
For both issues try the new exper
** 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
The only explanations I can see for the failed boots is:
Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]:
(WW) NVIDIA(G0): Failed to set the display configuration
Feb 28 21:20:49 alvin-Legion-Pro-7-16IRX8H /usr/libexec/gdm-x-session[1356]:
(WW) NVIDIA(G0): - Setting
201 - 300 of 6487 matches
Mail list logo
