hello salvatore .
some information you may want to ask me .
first of all, a kernel where everything is fine under sid :
alain@sid:~$ uname -a
Linux sid 6.12.9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.9-1
(2025-01-10) x86_64 GNU/Linux
alain@sid:~$ sudo insmod
/usr/lib/modules/6.12.10-amd64/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko.xz
insmod: ERROR: could not insert module
/usr/lib/modules/6.12.10-amd64/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko.xz:
File exists
alain@sid:~$ sudo dmesg | grep drm
[sudo] Mot de passe de alain :
[ 1.852194] ACPI: bus type drm_connector registered
[ 3.820847] [drm] amdgpu kernel modesetting enabled.
[ 3.821089] [drm] initializing kernel modesetting (IP DISCOVERY
0x1002:0x744C 0x1DA2:0x471E 0xC8).
[ 3.821099] [drm] register mmio base: 0xFCC00000
[ 3.821100] [drm] register mmio size: 1048576
[ 3.826253] [drm] add ip block number 0 <soc21_common>
[ 3.826255] [drm] add ip block number 1 <gmc_v11_0>
[ 3.826256] [drm] add ip block number 2 <ih_v6_0>
[ 3.826257] [drm] add ip block number 3 <psp>
[ 3.826258] [drm] add ip block number 4 <smu>
[ 3.826259] [drm] add ip block number 5 <dm>
[ 3.826260] [drm] add ip block number 6 <gfx_v11_0>
[ 3.826261] [drm] add ip block number 7 <sdma_v6_0>
[ 3.826263] [drm] add ip block number 8 <vcn_v4_0>
[ 3.826264] [drm] add ip block number 9 <jpeg_v4_0>
[ 3.826265] [drm] add ip block number 10 <mes_v11_0>
[ 3.834967] [drm] vm size is 262144 GB, 4 levels, block size is
9-bit, fragment size is 9-bit
[ 3.834982] [drm] Detected VRAM RAM=24560M, BAR=256M
[ 3.834983] [drm] RAM width 384bits GDDR6
[ 3.835059] [drm] amdgpu: 24560M of VRAM memory ready
[ 3.835061] [drm] amdgpu: 16001M of GTT memory ready.
[ 3.835072] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 3.835143] [drm] PCIE GART of 512M enabled (table at
0x0000008002000000).
[ 3.836043] [drm] Loading DMUB firmware via PSP: version=0x07002A00
[ 3.836214] [drm] Found VCN firmware Version ENC: 1.22 DEC: 9 VEP: 0
Revision: 12
[ 4.240562] [drm] Display Core v3.2.301 initialized on DCN 3.2
[ 4.240564] [drm] DP-HDMI FRL PCON supported
[ 4.242428] [drm] DMUB hardware initialized: version=0x07002A00
[ 4.749326] [drm] ring gfx_32768.1.1 was added
[ 4.749633] [drm] ring compute_32768.2.2 was added
[ 4.749889] [drm] ring sdma_32768.3.3 was added
[ 4.749952] [drm] ring gfx_32768.1.1 ib test pass
[ 4.750009] [drm] ring compute_32768.2.2 ib test pass
[ 4.750036] [drm] ring sdma_32768.3.3 ib test pass
[ 4.751713] [drm] Initialized amdgpu 3.59.0 for 0000:0b:00.0 on minor 0
[ 4.759679] fbcon: amdgpudrmfb (fb0) is primary device
[ 4.759886] [drm] pre_validate_dsc:1589 MST_DSC dsc precompute is not
needed
[ 5.042456] amdgpu 0000:0b:00.0: [drm] fb0: amdgpudrmfb frame buffer
device
[ 6.102970] systemd[1]: Starting modprobe@drm.service - Load Kernel
Module drm...
[ 6.112430] systemd[1]: modprobe@drm.service: Deactivated successfully.
[ 6.112551] systemd[1]: Finished modprobe@drm.service - Load Kernel
Module drm.
alain@sid:~$ xrandr
Screen 0: minimum 320 x 200, current 7680 x 2160, maximum 16384 x 16384
DisplayPort-0 connected primary 3840x2160+0+0 (normal left inverted
right x axis y axis) 708mm x 399mm
3840x2160 143.99*+ 60.00 + 120.00 100.00 60.00 50.00
59.94 30.00 25.00 24.00 29.97 23.98
3840x1600 144.00
1920x2160 59.94
2560x1440 144.00 120.00
1920x1200 143.99
1920x1080 120.00 119.88 60.00 60.00 50.00 59.94
1600x1200 143.99
1680x1050 59.95
1280x1024 75.02 60.02
1440x900 59.89
1280x960 60.00
1280x800 143.99
1152x864 75.00
1280x720 120.00 119.88 60.00 50.00 59.94
1440x576 50.00
1024x768 75.03 70.07 60.00
1440x480 60.00 59.94
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08
DisplayPort-1 connected 3840x2160+3840+0 (normal left inverted right x
axis y axis) 697mm x 392mm
3840x2160 60.00*+ 30.00 29.97
2560x1440 59.95
1920x1200 60.00
1920x1080 60.00 59.94
1600x1200 60.00
1680x1050 59.95
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.89
1280x800 59.81
1152x864 75.00
1280x720 60.00 59.94
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-1 disconnected (normal left inverted right x axis y axis)
alain@sid:~$ inxi -C
CPU:
Info: 12-core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP cache:
L2: 6 MiB
Speed (MHz): avg: 1727 min/max: 550/4951 cores: 1: 1727 2: 1727 3: 1727
4: 1727 5: 1727 6: 1727 7: 1727 8: 1727 9: 1727 10: 1727 11: 1727
12: 1727
13: 1727 14: 1727 15: 1727 16: 1727 17: 1727 18: 1727 19: 1727 20: 1727
21: 1727 22: 1727 23: 1727 24: 1727
alain@sid:~$ inxi -G
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900
XT/7900
XTX/7900 GRE/7900M] driver: amdgpu v: kernel
Device-2: HP HP Webcam HD 4310
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.4 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
gpu: amdgpu resolution: 1: 3840x2160~144Hz 2: 3840x2160~60Hz
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4-3
renderer: AMD
Radeon RX 7900 XTX (radeonsi navi31 LLVM 19.1.7 DRM 3.59 6.12.9-amd64)
API: Vulkan v: 1.4.304 drivers: N/A surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: xfce4-display-settings gpu: radeontop x11: xdriinfo, xdpyinfo,
xprop,
xrandr
alain@sid:~$ sudo journalctl -b -r -p err -n 50
févr. 06 18:56:55 sid systemd[2176]: Failed to start fluidsynth.service
- FluidSynth Daemon.
févr. 06 18:56:55 sid systemd[2176]: Failed to start
app-gnome-at\x2dspi\x2ddbus\x2dbus-2436.scope - Applicati>
févr. 06 18:56:55 sid systemd[2176]: Failed to start
app-gnome-gnome\x2dkeyring\x2dssh-2420.scope - Applicatio>
févr. 06 18:56:55 sid systemd[2176]: Failed to start
app-gnome-gnome\x2dkeyring\x2dsecrets-2424.scope - Applic>
févr. 06 18:56:55 sid systemd[2176]: Failed to start
app-gnome-gnome\x2dkeyring\x2dpkcs11-2418.scope - Applica>
févr. 06 18:56:54 sid lightdm[1712]:
pam_systemd(lightdm-greeter:session): Failed to release session: Transpor>
févr. 06 18:56:54 sid lightdm[2161]: gkr-pam: unable to locate daemon
control file
févr. 06 18:56:46 sid systemd[1718]: Failed to start fluidsynth.service
- FluidSynth Daemon.
févr. 06 18:56:43 sid libvirtd[1367]: Impossible d'ouvrir /dev/kvm:
Aucun fichier ou dossier de ce nom
févr. 06 18:56:43 sid systemd[1]: Failed to start fancontrol.service -
fan speed regulator.
alain@sid:~$ ls -l /dev/dri/
total 0
drwxr-xr-x 2 root root 80 6 févr. 2025 by-path
crw-rw----+ 1 root video 226, 0 6 févr. 2025 card0
crw-rw----+ 1 root render 226, 128 6 févr. 2025 renderD128
alain@sid:~$ sudo journalctl -b -n 50
févr. 06 18:17:15 sid sudo[18711]: alain : PWD=/home/alain ;
USER=root ; COMMAND=/usr/sbin/smartctl -a
/dev/disk/by-id/usb-ST2000DL_003-9VT166_152D00539000-0:2
févr. 06 18:17:15 sid sudo[18711]: pam_unix(sudo:session): session
opened for user root(uid=0) by alain(uid=1000)
févr. 06 18:17:15 sid sudo[18670]: pam_unix(sudo:session): session
closed for user root
févr. 06 18:17:15 sid sudo[18691]: pam_unix(sudo:session): session
closed for user root
févr. 06 18:17:15 sid sudo[18711]: pam_unix(sudo:session): session
closed for user root
févr. 06 18:17:16 sid systemd[1514]: onedrive.service: Scheduled restart
job, restart counter is at 64.
févr. 06 18:17:16 sid systemd[1514]: Starting onedrive.service -
OneDrive Client for Linux...
févr. 06 18:17:16 sid sudo[18585]: pam_unix(sudo:session): session
closed for user root
févr. 06 18:17:16 sid onedrive[4410]: Attempting to contact Microsoft
OneDrive Login Service
févr. 06 18:17:16 sid onedrive[4410]: Successfully reached Microsoft
OneDrive Login Service
févr. 06 18:17:16 sid onedrive[4410]: Starting a sync with Microsoft
OneDrive
févr. 06 18:17:17 sid onedrive[4410]: Syncing changes from Microsoft
OneDrive ...
févr. 06 18:17:18 sid onedrive[4410]: Sync with Microsoft OneDrive is
complete
févr. 06 18:17:26 sid gnome-shell[2437]: meta_window_stick: assertion
'!window->override_redirect' failed
févr. 06 18:17:31 sid systemd[1514]: Started onedrive.service - OneDrive
Client for Linux.
févr. 06 18:17:31 sid dbus-daemon[1614]: [session uid=117 pid=1614
pidfd=5] Activating service name='org.freedesktop.Notifications'
requested by ':1.75' (uid=117 pid=18823 comm="/usr/bin/onedrive --monitor")
févr. 06 18:17:31 sid mate-notificati[18830]: cannot open display:
févr. 06 18:17:31 sid dbus-daemon[1614]: [session uid=117 pid=1614
pidfd=5] Activated service 'org.freedesktop.Notifications' failed:
Process org.freedesktop.Notifications exited with status 1
févr. 06 18:17:31 sid onedrive[18823]: WARNING: D-Bus message bus daemon
is not available; GUI notifications are disabled
févr. 06 18:17:31 sid onedrive[18823]: Using IPv4 and IPv6 (if
configured) for all network operations
févr. 06 18:17:31 sid onedrive[18823]: Attempting to contact Microsoft
OneDrive Login Service
févr. 06 18:17:31 sid onedrive[18823]: Successfully reached Microsoft
OneDrive Login Service
févr. 06 18:17:31 sid onedrive[18823]: Configuring Global Azure AD Endpoints
févr. 06 18:17:31 sid onedrive[18823]: Authorise this application by
visiting:
févr. 06 18:17:31 sid onedrive[18823]:
https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=d50ca740-c83f-4d1b-b616-12c519384f0c&scope=Files.ReadWrite%20Files.ReadWrite.All%20Sites.ReadWrite.All%20offline_access&response_type=code&prompt=login&redirect_uri=https://login.microsoftonline.com/common/oauth2/nativeclient
févr. 06 18:17:31 sid onedrive[18823]: Enter the response uri from your
browser: An empty or invalid response uri was entered
févr. 06 18:17:31 sid onedrive[18823]: The OneDrive API could not be
initialised
févr. 06 18:17:32 sid systemd[1514]: onedrive.service: Main process
exited, code=exited, status=1/FAILURE
févr. 06 18:17:32 sid systemd[1514]: onedrive.service: Failed with
result 'exit-code'.
févr. 06 18:17:35 sid systemd[1514]: onedrive.service: Scheduled restart
job, restart counter is at 65.
févr. 06 18:17:35 sid systemd[1514]: Starting onedrive.service -
OneDrive Client for Linux...
févr. 06 18:17:50 sid systemd[1514]: Started onedrive.service - OneDrive
Client for Linux.
févr. 06 18:17:50 sid dbus-daemon[1614]: [session uid=117 pid=1614
pidfd=5] Activating service name='org.freedesktop.Notifications'
requested by ':1.76' (uid=117 pid=18962 comm="/usr/bin/onedrive --monitor")
févr. 06 18:17:50 sid mate-notificati[18969]: cannot open display:
févr. 06 18:17:50 sid dbus-daemon[1614]: [session uid=117 pid=1614
pidfd=5] Activated service 'org.freedesktop.Notifications' failed:
Process org.freedesktop.Notifications exited with status 1
févr. 06 18:17:50 sid onedrive[18962]: WARNING: D-Bus message bus daemon
is not available; GUI notifications are disabled
févr. 06 18:17:50 sid onedrive[18962]: Using IPv4 and IPv6 (if
configured) for all network operations
févr. 06 18:17:50 sid onedrive[18962]: Attempting to contact Microsoft
OneDrive Login Service
févr. 06 18:17:50 sid onedrive[18962]: Successfully reached Microsoft
OneDrive Login Service
févr. 06 18:17:50 sid onedrive[18962]: Configuring Global Azure AD Endpoints
févr. 06 18:17:50 sid onedrive[18962]: Authorise this application by
visiting:
févr. 06 18:17:50 sid onedrive[18962]:
https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=d50ca740-c83f-4d1b-b616-12c519384f0c&scope=Files.ReadWrite%20Files.ReadWrite.All%20Sites.ReadWrite.All%20offline_access&response_type=code&prompt=login&redirect_uri=https://login.microsoftonline.com/common/oauth2/nativeclient
févr. 06 18:17:50 sid onedrive[18962]: Enter the response uri from your
browser: An empty or invalid response uri was entered
févr. 06 18:17:50 sid onedrive[18962]: The OneDrive API could not be
initialised
févr. 06 18:17:51 sid systemd[1514]: onedrive.service: Main process
exited, code=exited, status=1/FAILURE
févr. 06 18:17:51 sid systemd[1514]: onedrive.service: Failed with
result 'exit-code'.
févr. 06 18:17:54 sid systemd[1514]: onedrive.service: Scheduled restart
job, restart counter is at 66.
févr. 06 18:17:54 sid systemd[1514]: Starting onedrive.service -
OneDrive Client for Linux...
févr. 06 18:18:06 sid sudo[19109]: alain : TTY=pts/0 ;
PWD=/home/alain ; USER=root ; COMMAND=/usr/bin/journalctl -b -n 50
févr. 06 18:18:06 sid sudo[19109]: pam_unix(sudo:session): session
opened for user root(uid=0) by alain(uid=1000)
alain@sid:~$ sudo insmod
/usr/lib/modules/6.12.10-amd64/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko.xz
insmod: ERROR: could not insert module
/usr/lib/modules/6.12.10-amd64/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko.xz:
File exists
On Thu, 6 Feb 2025 09:30:55 +0100 alain <compte.perso.de-al...@bbox.fr>
wrote:
> hello salvatore .
> excuse me for replying so late .
> I've just seen your signature.
>
> all kernels after 6.12.9 are broken .
> there's no graphic support left .
> in any case, not for amd (my case).
> i've tried the following official kernels :
> 6.12.10
> 6.12.11
> 6.12.12
> 6.13-rc7
> the graphic support is broken.
> even amdgpu-dkms no longer exists in the repositories ,
> so you can't even recreate the amdgpu module.
> module and support by hand.
> /dev/dri/ no longer exists.
> I've changed processor, but that's done almost nothing.
> graphics support is broken.
> as far as I've learned, on both amd and nvidia.
>
> I don't understand debian's behavior.
>
> respectfully and amicably .
> alain .
>
>
> Translated with DeepL.com (free version)
>
>
> On Fri, 31 Jan 2025 06:42:50 +0100 Salvatore Bonaccorso
> <car...@debian.org> wrote:
>
> > Control: tags -1 + moreinfo
> >
> > On Thu, Jan 30, 2025 at 10:08:42PM +0100, alain wrote:
> > > Package: src:linux
> > > Version: 6.12.10-1
> > > Severity: important
> > > Tags: upstream
> > > X-Debbugs-Cc: compte.perso.de-al...@bbox.fr
> > >
> > > Dear Maintainer,
> > >
> > > *** Reporter, please consider answering these questions, where
> appropriate ***
> > >
> > > * What led up to the situation?
> > > an update made linux unusuable
> > > * What exactly did you do (or not do) that was effective (or
> > > ineffective)?
> > > sudo apt update && sudo apt upgrade
> > > * What was the outcome of this action?
> > > amdgpu support was broken also , i think , gnome
> > > * What outcome did you expect instead?
> > > i wanted to maintain up-to-date my distribution
> >
> > From the report it's not enitrely clear "what is unusable", do you get
> > errors on the UI, what is the behaviour?
> >
