Public bug reported:
5.15.0-105 stops my SD Card from working and no wifi - using Lenovo
T470.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2064018
Title:
No Wifi or SD Card with latest kernel
Status in linux package in Ubuntu:
New
Bug description:
5.15.0-105 stops my SD Card from working and no wifi - using Lenovo
T470.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064018/+subscriptions
воскресенье
[Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp
** Tags added: verification-done-jammy-linux-xilinx-zynqmp
** Tags removed: verification-needed-focal-linux-oracle-5.15 verification-needed-jammy-linux-bluefield verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-mantic-linux-raspi
** Tags added: verification-done-focal-linux-oracle-5.15 verification-done-jammy-linux-bluefield verification-done-jammy-linux-intel-iotg verification-done-jammy-linux-nvidia-tegra-igx verification-done-mantic-linux-raspi
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2054809
Title:
linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from
linux-modules-extra to linux-modules
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
SRU Justification
[Impact]
The erofs.ko module (CONFIG_EROFS) is currently shipped in linux-
modules-extra. This makes it hard to pull in via the linux-virtual
package, it can only come from the linux-generic one that also pulls
in the firmware and everything else needed for baremetal, and that
serves no purpose in a qemu VM. This stops VMs using these kernels
from using the erofs filesystem. Erofs is a modern alternative to
squashfs that supports more features such as ACLs. The following LPC
presentation has more details on erofs and its advantages over
squashfs: https://youtu.be/jt-hp_LtSBc.
A user launching a VM using the linux-virtual kernel image is not able
to mount erofs filesystems due to the lack of this kconfig. We make
extensive use of erofs in systemd's upstream CI, which is running on
Github Actions, which uses Jammy, so it would be great to have this
backported.
[Fix]
Please consider moving this module to linux-modules.
These are already enabled in the 'main' kernel config, and in other
distros. In Debian/Archlinux/Fedora it is a (core) module that is
built by default.
To verify this works, it is sufficient to create an erofs filesystem
with mkfs.erofs and verify that it can be mounted:
$ mkdir sources
$ echo abcde > sources/file
$ mkfs.erofs erofs sources
$ mount erofs mnt --mkdir
$ ls mnt
file
Without this module installed and loaded, the mount will fail. Once
enabled, it will succeed.
[Test]
1. pull built linux-modules packages for architectures with do_extras_package
set to true;
2. extract the deb and check if erofs kernel module file exists:
$ dpkg-deb -R linux-modules-*.deb .
$ find . -name erofs.ko\*
[Regression Potential]
Moving a module from a less-common to a more-common package should not
have any negative side effects. The main effect will be a little more
disk space used by the more common package, whether the module is in
use or not. There will also be more functionality available in the
default installation, which means a slightly increased surface and
possibility of new bugs in case it gets used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions
** Tags added: verification-done-jammy-linux-xilinx-zynqmp
** Tags removed: verification-needed-focal-linux-oracle-5.15 verification-needed-jammy-linux-bluefield verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-mantic-linux-raspi
** Tags added: verification-done-focal-linux-oracle-5.15 verification-done-jammy-linux-bluefield verification-done-jammy-linux-intel-iotg verification-done-jammy-linux-nvidia-tegra-igx verification-done-mantic-linux-raspi
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2054809
Title:
linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from
linux-modules-extra to linux-modules
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
SRU Justification
[Impact]
The erofs.ko module (CONFIG_EROFS) is currently shipped in linux-
modules-extra. This makes it hard to pull in via the linux-virtual
package, it can only come from the linux-generic one that also pulls
in the firmware and everything else needed for baremetal, and that
serves no purpose in a qemu VM. This stops VMs using these kernels
from using the erofs filesystem. Erofs is a modern alternative to
squashfs that supports more features such as ACLs. The following LPC
presentation has more details on erofs and its advantages over
squashfs: https://youtu.be/jt-hp_LtSBc.
A user launching a VM using the linux-virtual kernel image is not able
to mount erofs filesystems due to the lack of this kconfig. We make
extensive use of erofs in systemd's upstream CI, which is running on
Github Actions, which uses Jammy, so it would be great to have this
backported.
[Fix]
Please consider moving this module to linux-modules.
These are already enabled in the 'main' kernel config, and in other
distros. In Debian/Archlinux/Fedora it is a (core) module that is
built by default.
To verify this works, it is sufficient to create an erofs filesystem
with mkfs.erofs and verify that it can be mounted:
$ mkdir sources
$ echo abcde > sources/file
$ mkfs.erofs erofs sources
$ mount erofs mnt --mkdir
$ ls mnt
file
Without this module installed and loaded, the mount will fail. Once
enabled, it will succeed.
[Test]
1. pull built linux-modules packages for architectures with do_extras_package
set to true;
2. extract the deb and check if erofs kernel module file exists:
$ dpkg-deb -R linux-modules-*.deb .
$ find . -name erofs.ko\*
[Regression Potential]
Moving a module from a less-common to a more-common package should not
have any negative side effects. The main effect will be a little more
disk space used by the more common package, whether the module is in
use or not. There will also be more functionality available in the
default installation, which means a slightly increased surface and
possibility of new bugs in case it gets used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions
[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+attachment/5771970/+files/dmesg
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia driver
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-550 package in Ubuntu:
New
Bug description:
[ Impact ]
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.
[ Workaround ]
1. sudo rm /dev/dri/card0
2. Log in again.
[ Test Plan ]
Open Settings and verify the only monitors shown are your real
monitors.
[ Where problems could occur ]
Removing the simpledrm card is only safe when it's not being used. If
somehow a machine wasn't using the installed Nvidia driver then there
could be a risk of deleting the only working display.
[ Other Info ]
ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dan 4631 F.... pipewire
/dev/snd/controlC1: dan 4636 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-01-04 (92 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
MachineType: Intel(R) Client Systems NUC12DCMi7
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
RelatedPackageVersions:
linux-restricted-modules-6.8.0-11-generic N/A
linux-backports-modules-6.8.0-11-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu1
Tags: noble
Uname: Linux 6.8.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 12/20/2021
dmi.bios.release: 5.24
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EDADL579.0046.2021.1220.2351
dmi.board.name: NUC12EDBi7
dmi.board.vendor: Intel Corporation
dmi.board.version: M27908-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.7
dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi70000:
dmi.product.family: DC
dmi.product.name: NUC12DCMi7
dmi.product.sku: RNUC12DCMi70000
dmi.product.version: M30143-302
dmi.sys.vendor: Intel(R) Client Systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+attachment/5771970/+files/dmesg
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia driver
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-550 package in Ubuntu:
New
Bug description:
[ Impact ]
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.
[ Workaround ]
1. sudo rm /dev/dri/card0
2. Log in again.
[ Test Plan ]
Open Settings and verify the only monitors shown are your real
monitors.
[ Where problems could occur ]
Removing the simpledrm card is only safe when it's not being used. If
somehow a machine wasn't using the installed Nvidia driver then there
could be a risk of deleting the only working display.
[ Other Info ]
ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dan 4631 F.... pipewire
/dev/snd/controlC1: dan 4636 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-01-04 (92 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
MachineType: Intel(R) Client Systems NUC12DCMi7
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
RelatedPackageVersions:
linux-restricted-modules-6.8.0-11-generic N/A
linux-backports-modules-6.8.0-11-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu1
Tags: noble
Uname: Linux 6.8.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 12/20/2021
dmi.bios.release: 5.24
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EDADL579.0046.2021.1220.2351
dmi.board.name: NUC12EDBi7
dmi.board.vendor: Intel Corporation
dmi.board.version: M27908-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.7
dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi70000:
dmi.product.family: DC
dmi.product.name: NUC12DCMi7
dmi.product.sku: RNUC12DCMi70000
dmi.product.version: M30143-302
dmi.sys.vendor: Intel(R) Client Systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions
[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
Same problem for me on Ubuntu 24.04 fresh install on X11.
I tried updating my nvidia driver to nvidia-driver-550, but I keep
getting this "phantom" monitor in Gnome settings.
I have two physical monitors :
- Main one : AOC 27" AG271QG with G-Sync
- Other one : Dell 25"
$ find /sys/devices -name "edid"
/sys/devices/platform/simple-framebuffer.0/drm/card0/card0-Unknown-1/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-HDMI-A-1/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-DP-2/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-Unknown-2/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-DP-3/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-DP-1/edid
[ Workaround ]
I type in terminal : sudo rm -f /dev/dri/card0
*After relogin : Phantom monitor has disappeared, but I lost my monitors' configuration (Main becoming second and vice versa, losing refresh rate too for the AOC).
No sign of the phantom screen in Gnome settings.
/dev/dri$ ls -l
total 0
drwxr-xr-x 2 root root 100 avril 28 14:52 by-path
crw-rw----+ 1 root video 226, 1 avril 28 14:52 card1
crw-rw----+ 1 root render 226, 128 avril 28 14:52 renderD128
I set my monitors like before (refresh rate at 144Hz and main monitor
for the AOC), and reboot.
* After rebooting : phantom monitor is there again in Gnome settings. I
kept my monitors' configuration.
/dev/dri$ ls -l
total 0
drwxr-xr-x 2 root root 100 avril 28 15:21 by-path
crw-rw----+ 1 root video 226, 0 avril 28 15:21 card0
crw-rw----+ 1 root video 226, 1 avril 28 15:21 card1
crw-rw----+ 1 root render 226, 128 avril 28 15:21 renderD128
Other informations about my PC :
# Rapport d'informations du système
---
## Détails du compte rendu
- **Date de génération :** 2024-04-28 15:07:02
## Informations liées au matériel :
- **Modèle du matériel :** ASRock X570 Taichi
- **Mémoire :** 32,0 Gio
- **Processeur :** AMD Ryzen™ 7 5800X3D × 16
- **Carte graphique :** NVIDIA GeForce RTX™ 2080
- **Capacité du disque :** 8,5 To
## Informations liées au logiciel :
- **Version du micrologiciel :** P5.01
- **Nom du système d'exploitation :** Ubuntu 24.04 LTS
- **Construction du système d'exploitation :** (null)
- **Type de système d'exploitation :** 64 bits
- **Version de GNOME :** 46
- **Système de fenêtrage :** X11
- **Version du noyau :** Linux 6.8.0-31-generic
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia driver
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-550 package in Ubuntu:
New
Bug description:
[ Impact ]
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.
[ Workaround ]
1. sudo rm /dev/dri/card0
2. Log in again.
[ Test Plan ]
Open Settings and verify the only monitors shown are your real
monitors.
[ Where problems could occur ]
Removing the simpledrm card is only safe when it's not being used. If
somehow a machine wasn't using the installed Nvidia driver then there
could be a risk of deleting the only working display.
[ Other Info ]
ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dan 4631 F.... pipewire
/dev/snd/controlC1: dan 4636 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-01-04 (92 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
MachineType: Intel(R) Client Systems NUC12DCMi7
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
RelatedPackageVersions:
linux-restricted-modules-6.8.0-11-generic N/A
linux-backports-modules-6.8.0-11-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu1
Tags: noble
Uname: Linux 6.8.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 12/20/2021
dmi.bios.release: 5.24
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EDADL579.0046.2021.1220.2351
dmi.board.name: NUC12EDBi7
dmi.board.vendor: Intel Corporation
dmi.board.version: M27908-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.7
dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi70000:
dmi.product.family: DC
dmi.product.name: NUC12DCMi7
dmi.product.sku: RNUC12DCMi70000
dmi.product.version: M30143-302
dmi.sys.vendor: Intel(R) Client Systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions
I tried updating my nvidia driver to nvidia-driver-550, but I keep
getting this "phantom" monitor in Gnome settings.
I have two physical monitors :
- Main one : AOC 27" AG271QG with G-Sync
- Other one : Dell 25"
$ find /sys/devices -name "edid"
/sys/devices/platform/simple-framebuffer.0/drm/card0/card0-Unknown-1/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-HDMI-A-1/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-DP-2/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-Unknown-2/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-DP-3/edid
/sys/devices/pci0000:00/0000:00:03.1/0000:0e:00.0/drm/card1/card1-DP-1/edid
[ Workaround ]
I type in terminal : sudo rm -f /dev/dri/card0
*After relogin : Phantom monitor has disappeared, but I lost my monitors' configuration (Main becoming second and vice versa, losing refresh rate too for the AOC).
No sign of the phantom screen in Gnome settings.
/dev/dri$ ls -l
total 0
drwxr-xr-x 2 root root 100 avril 28 14:52 by-path
crw-rw----+ 1 root video 226, 1 avril 28 14:52 card1
crw-rw----+ 1 root render 226, 128 avril 28 14:52 renderD128
I set my monitors like before (refresh rate at 144Hz and main monitor
for the AOC), and reboot.
* After rebooting : phantom monitor is there again in Gnome settings. I
kept my monitors' configuration.
/dev/dri$ ls -l
total 0
drwxr-xr-x 2 root root 100 avril 28 15:21 by-path
crw-rw----+ 1 root video 226, 0 avril 28 15:21 card0
crw-rw----+ 1 root video 226, 1 avril 28 15:21 card1
crw-rw----+ 1 root render 226, 128 avril 28 15:21 renderD128
Other informations about my PC :
# Rapport d'informations du système
---
## Détails du compte rendu
- **Date de génération :** 2024-04-28 15:07:02
## Informations liées au matériel :
- **Modèle du matériel :** ASRock X570 Taichi
- **Mémoire :** 32,0 Gio
- **Processeur :** AMD Ryzen™ 7 5800X3D × 16
- **Carte graphique :** NVIDIA GeForce RTX™ 2080
- **Capacité du disque :** 8,5 To
## Informations liées au logiciel :
- **Version du micrologiciel :** P5.01
- **Nom du système d'exploitation :** Ubuntu 24.04 LTS
- **Construction du système d'exploitation :** (null)
- **Type de système d'exploitation :** 64 bits
- **Version de GNOME :** 46
- **Système de fenêtrage :** X11
- **Version du noyau :** Linux 6.8.0-31-generic
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia driver
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-550 package in Ubuntu:
New
Bug description:
[ Impact ]
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.
[ Workaround ]
1. sudo rm /dev/dri/card0
2. Log in again.
[ Test Plan ]
Open Settings and verify the only monitors shown are your real
monitors.
[ Where problems could occur ]
Removing the simpledrm card is only safe when it's not being used. If
somehow a machine wasn't using the installed Nvidia driver then there
could be a risk of deleting the only working display.
[ Other Info ]
ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dan 4631 F.... pipewire
/dev/snd/controlC1: dan 4636 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-01-04 (92 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
MachineType: Intel(R) Client Systems NUC12DCMi7
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
RelatedPackageVersions:
linux-restricted-modules-6.8.0-11-generic N/A
linux-backports-modules-6.8.0-11-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu1
Tags: noble
Uname: Linux 6.8.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 12/20/2021
dmi.bios.release: 5.24
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EDADL579.0046.2021.1220.2351
dmi.board.name: NUC12EDBi7
dmi.board.vendor: Intel Corporation
dmi.board.version: M27908-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.7
dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi70000:
dmi.product.family: DC
dmi.product.name: NUC12DCMi7
dmi.product.sku: RNUC12DCMi70000
dmi.product.version: M30143-302
dmi.sys.vendor: Intel(R) Client Systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions
[Bug 2056743] Re: Keyboard stops working after suspend on Dell XPS 13
With the latest kernel update from Ubuntu (5.15.0-106-generic) the
problem has been solved.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2056743
Title:
Keyboard stops working after suspend on Dell XPS 13
Status in linux package in Ubuntu:
Confirmed
Bug description:
The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100.
The issue seems to be identical to the problem reported for 6.7.0
here: https://bbs.archlinux.org/viewtopic.php?id=292203
On the page linked above is says a patch was submitted 2024-01-26 and
the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17.
I'm concerned that this still needs fixing in the 5.xxx kernel branch.
Touchpad does not freeze and mouse-control of windows still works, so
it's different from a bug reported elsewhere.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-102-generic 5.15.0-102.112
ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: axel 2494 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 11 09:54:23 2024
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
InstallationDate: Installed on 2018-08-31 (2018 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-100-generic N/A
linux-backports-modules-5.15.0-100-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.29
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2022
dmi.bios.release: 1.21
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.0
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056743/+subscriptions
problem has been solved.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2056743
Title:
Keyboard stops working after suspend on Dell XPS 13
Status in linux package in Ubuntu:
Confirmed
Bug description:
The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100.
The issue seems to be identical to the problem reported for 6.7.0
here: https://bbs.archlinux.org/viewtopic.php?id=292203
On the page linked above is says a patch was submitted 2024-01-26 and
the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17.
I'm concerned that this still needs fixing in the 5.xxx kernel branch.
Touchpad does not freeze and mouse-control of windows still works, so
it's different from a bug reported elsewhere.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-102-generic 5.15.0-102.112
ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: axel 2494 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 11 09:54:23 2024
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
InstallationDate: Installed on 2018-08-31 (2018 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-100-generic N/A
linux-backports-modules-5.15.0-100-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.29
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2022
dmi.bios.release: 1.21
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.0
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056743/+subscriptions
[Bug 2056743] Re: Keyboard stops working after suspend on Dell XPS 13
Hello
I have the same problem on a Dell XPS 13 running Ubuntu 22.04.4, ever
since 17 April 2024 or so when I believe the kernel was upgraded.
However, my kernel is 5.15.0-105-generic.
Hope it can be fixed - many thanks!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2056743
Title:
Keyboard stops working after suspend on Dell XPS 13
Status in linux package in Ubuntu:
Confirmed
Bug description:
The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100.
The issue seems to be identical to the problem reported for 6.7.0
here: https://bbs.archlinux.org/viewtopic.php?id=292203
On the page linked above is says a patch was submitted 2024-01-26 and
the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17.
I'm concerned that this still needs fixing in the 5.xxx kernel branch.
Touchpad does not freeze and mouse-control of windows still works, so
it's different from a bug reported elsewhere.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-102-generic 5.15.0-102.112
ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: axel 2494 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 11 09:54:23 2024
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
InstallationDate: Installed on 2018-08-31 (2018 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-100-generic N/A
linux-backports-modules-5.15.0-100-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.29
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2022
dmi.bios.release: 1.21
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.0
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056743/+subscriptions
I have the same problem on a Dell XPS 13 running Ubuntu 22.04.4, ever
since 17 April 2024 or so when I believe the kernel was upgraded.
However, my kernel is 5.15.0-105-generic.
Hope it can be fixed - many thanks!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2056743
Title:
Keyboard stops working after suspend on Dell XPS 13
Status in linux package in Ubuntu:
Confirmed
Bug description:
The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100.
The issue seems to be identical to the problem reported for 6.7.0
here: https://bbs.archlinux.org/viewtopic.php?id=292203
On the page linked above is says a patch was submitted 2024-01-26 and
the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17.
I'm concerned that this still needs fixing in the 5.xxx kernel branch.
Touchpad does not freeze and mouse-control of windows still works, so
it's different from a bug reported elsewhere.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-102-generic 5.15.0-102.112
ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: axel 2494 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 11 09:54:23 2024
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
InstallationDate: Installed on 2018-08-31 (2018 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-100-generic N/A
linux-backports-modules-5.15.0-100-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.29
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2022
dmi.bios.release: 1.21
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.0
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056743/+subscriptions
[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
I forgot to mention in my summary that I could not duplicate any of the
issues I was having when I swapped out the Radeon 6800XT for a GeForce
1070 in my Desktop and repeated the process of doing a full wipe and
reinstall of 24.04. I plan to repeat these steps with my current
configuration (Ryzen CPU and 6800XT GPU) after swapping out the SSD so I
can collect logs as requested of me in #ubuntu on Libera.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
Confirmed
Bug description:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions
issues I was having when I swapped out the Radeon 6800XT for a GeForce
1070 in my Desktop and repeated the process of doing a full wipe and
reinstall of 24.04. I plan to repeat these steps with my current
configuration (Ryzen CPU and 6800XT GPU) after swapping out the SSD so I
can collect logs as requested of me in #ubuntu on Libera.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
Confirmed
Bug description:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions
[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
I had the same issue while trying to upgrade to Kubuntu 24.04 or install
Kubuntu 24.04 from scratch. I get a black screen at startup.
My graphic card is also an AMD GPU : Radeon RX 7800 XT.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
Confirmed
Bug description:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions
Kubuntu 24.04 from scratch. I get a black screen at startup.
My graphic card is also an AMD GPU : Radeon RX 7800 XT.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
Confirmed
Bug description:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions
[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
Confirmed
Bug description:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
Confirmed
Bug description:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions
суббота
[Bug 1621367] Re: 4.4.0-36: keyboard dead at boot & full disk encryption prompt for password
** Changed in: linux (Ubuntu)
Assignee: Marcelo Cerri (mhcerri) => Mirko Flade (mirkoflade1)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1621367
Title:
4.4.0-36: keyboard dead at boot & full disk encryption prompt for
password
Status in linux package in Ubuntu:
Confirmed
Bug description:
After updating to kernel 4.4.0-36.55, I cannot enter the password for the full disk encrypted drive, that contains the ubuntu installation.
Keyboard is totally dead. Nothing else than hardware reset is possible.
This bug affects normal, upstart and recovery boot.
I don't know whether that is a kernel panik (no led is blinking) or
the driver for keyboard is failing. boot.log looks normal to me.
Last and working kernel version before the update, was "Ubuntu
4.4.0-34.53-generic 4.4.15".
I cannot report "ubuntu-bug linux", because I cannot enter the system.
I am willing to investigate, but please give me hints.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621367/+subscriptions
Assignee: Marcelo Cerri (mhcerri) => Mirko Flade (mirkoflade1)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1621367
Title:
4.4.0-36: keyboard dead at boot & full disk encryption prompt for
password
Status in linux package in Ubuntu:
Confirmed
Bug description:
After updating to kernel 4.4.0-36.55, I cannot enter the password for the full disk encrypted drive, that contains the ubuntu installation.
Keyboard is totally dead. Nothing else than hardware reset is possible.
This bug affects normal, upstart and recovery boot.
I don't know whether that is a kernel panik (no led is blinking) or
the driver for keyboard is failing. boot.log looks normal to me.
Last and working kernel version before the update, was "Ubuntu
4.4.0-34.53-generic 4.4.15".
I cannot report "ubuntu-bug linux", because I cannot enter the system.
I am willing to investigate, but please give me hints.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621367/+subscriptions
[Bug 2063529] Re: Add support for Quectel RM520N-GL modem
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: Invalid => In Progress
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063529
Title:
Add support for Quectel RM520N-GL modem
Status in HWE Next:
In Progress
Status in OEM Priority Project:
Confirmed
Status in linux package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
In Progress
Bug description:
[Impact]
* Add support for Quectel RM520N-GL modem, so the device could be
properly probed.
[Test Plan]
* Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
use` is mht-pci-generic.
[Where problems could occur]
* These commits only introduces a PID, it won't impact devices which
are supported originally.
[Other Info]
* Upstream commits:
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
* Lenovo with this device will be enabled by linux-oem-6.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063529/+subscriptions
Status: New => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: Invalid => In Progress
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063529
Title:
Add support for Quectel RM520N-GL modem
Status in HWE Next:
In Progress
Status in OEM Priority Project:
Confirmed
Status in linux package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
In Progress
Bug description:
[Impact]
* Add support for Quectel RM520N-GL modem, so the device could be
properly probed.
[Test Plan]
* Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
use` is mht-pci-generic.
[Where problems could occur]
* These commits only introduces a PID, it won't impact devices which
are supported originally.
[Other Info]
* Upstream commits:
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
* Lenovo with this device will be enabled by linux-oem-6.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063529/+subscriptions
[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
New
Bug description:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Status in linux package in Ubuntu:
New
Bug description:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a
week ago, I took a kernel update via apt and rebooted. The result was
that the system would hard freeze to a black screen after the initial
kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
switching terminals (ctrl-alt-f#) did nothing, had to hard power off
to regain control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but
then any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most
recent installer iso to my thumbdrive, copied my home folder to my
RAID and did a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control
or what I did differently when doing a wipe and reinstall, I would
always reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power
offs required to be able to use my system again, no suspend issues.
Was not necessary for me to do anything else to maintain a consistent
successful reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions
[Bug 2063983] [NEW] 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
You have been subscribed to a public bug:
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a week
ago, I took a kernel update via apt and rebooted. The result was that
the system would hard freeze to a black screen after the initial kernel
messages cleared from the screen. Ctrl-Alt-Del did nothing, switching
terminals (ctrl-alt-f#) did nothing, had to hard power off to regain
control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but then
any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most recent
installer iso to my thumbdrive, copied my home folder to my RAID and did
a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control or
what I did differently when doing a wipe and reinstall, I would always
reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power offs
required to be able to use my system again, no suspend issues. Was not
necessary for me to do anything else to maintain a consistent successful
reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
https://bugs.launchpad.net/bugs/2063983
You received this bug notification because you are subscribed to linux in Ubuntu.
Config: Ryzen 5 5600X with Radeon 6800 XT GPU, a Navi21 card.
Using xUbuntu.
I had been daily driving the 24.04 nightly iso since March. About a week
ago, I took a kernel update via apt and rebooted. The result was that
the system would hard freeze to a black screen after the initial kernel
messages cleared from the screen. Ctrl-Alt-Del did nothing, switching
terminals (ctrl-alt-f#) did nothing, had to hard power off to regain
control of the system.
I tried various fixes, none of which permanently stuck. This includes
nomodeset in grub, rebooting into safe mode, checking for proprietary
drivers. Safe mode allowed me to reboot once more into desktop, but then
any subsequent reboots would result in a black screen lockup.
Suspending while able to use the desktop before reboot would cause a
black screen lockup did not seem to cause any issues.
3 days before 24.04 was officially released, I reflashed the most recent
installer iso to my thumbdrive, copied my home folder to my RAID and did
a full wipe and fresh install.
First reboot after installation always went to the desktop. Subsequent
reboots always resulted in a black screen lockup.
Memtest cleared without errors.
Again tried various fixes, nomodeset, safe mode, drivers. The only
consistency was that regardless of what I could do to regain control or
what I did differently when doing a wipe and reinstall, I would always
reboot to a black screen.
Once 24.04 was officially released, I again did a full wipe and
reinstall and encountered all of the above same issues as before.
After mentioning this in #ubuntu on libera, someone suggested a kernel
downgrade.
24.04 as installed was using 6.8.0-31.31
Using Mainline, I downgraded to the next minor version below 6.8 that
was considered stable. 6.7.10
Problem went away. No more black screen on boot, no more hard power offs
required to be able to use my system again, no suspend issues. Was not
necessary for me to do anything else to maintain a consistent successful
reboot to desktop.
Did yet another full wipe and fresh install of 24.04, only installing
Mainline upon first reboot to install 6.7.10, using Grub Customizer to
edit the default grub option to boot the 6.7.10 kernel instead.
No issues.
I apologise that I did not collect logs during this process.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
https://bugs.launchpad.net/bugs/2063983
You received this bug notification because you are subscribed to linux in Ubuntu.
Подписаться на:
Сообщения (Atom)