#26 Le 17/08/2022, à 18:35
- Mario2020C
Re : Vérification de l'intégrité de mon installation
J'ai installé selon tes instructions et fait un redémarrage.
Voici mon Boot-Info
boot-info-4ppa200 [20220817_1225]
============================== Boot Info Summary ===============================
=> No boot loader is installed in the MBR of /dev/nvme0n1.
=> No boot loader is installed in the MBR of /dev/sda.
=> No boot loader is installed in the MBR of /dev/sdb.
nvme0n1p1: _____________________________________________________________________
File system: vfat
Boot sector type: Windows 8/10/11/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi /efi/Boot/fbx64.efi
/efi/Boot/mmx64.efi /efi/ubuntu/grubx64.efi
/efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi
/efi/ubuntu/grub.cfg /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
nvme0n1p2: _____________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
nvme0n1p3: _____________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/10/11/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /Windows/System32/winload.exe
nvme0n1p4: _____________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/10/11/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: Unknown
Boot sector info: According to the info in the boot sector, sda1 starts
at sector 0. But according to the info from fdisk,
sda1 starts at sector 40.
Operating System:
Boot files:
sda2: __________________________________________________________________________
File system: exfat
Boot sector type: Unknown
Boot sector info:
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sdb2: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 22.04.1 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
sdb3: __________________________________________________________________________
File system: ntfs
Boot sector type: Unknown
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
================================ 2 OS detected =================================
OS#1: L'OS actuellement utilisé - Ubuntu 22.04.1 LTS CurrentSession on sdb2
OS#2: Windows 7 on nvme0n1p3
================================ Host/Hardware =================================
CPU architecture: 64-bit
Video: GA106M [GeForce RTX 3060 Mobile / Max-Q] TigerLake-H GT1 [UHD Graphics] from NVIDIA Corporation Intel Corporation
BOOT_IMAGE of the installed session in use:
/boot/vmlinuz-5.15.0-46-generic root=UUID=2bba5d16-3e6c-45b2-a367-baca5249744d ro quiet splash vt.handoff=7
df -Th / : /dev/sdb2 ext4 75G 37G 34G 53% /
===================================== UEFI =====================================
BIOS/UEFI firmware: FB03(5.19) from American Megatrends International, LLC.
The firmware is EFI-compatible, and is set in EFI-mode for this installed-session.
SecureBoot enabled but mokutil says: SecureBoot enabled - Veuillez indiquer ce message à boot.repair@gmail.com.
BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0000,0001
Boot0000* ubuntu HD(1,GPT,95646662-9d80-4a07-bf28-fd0bf509070b,0x800,0x32000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0001* Windows Boot Manager HD(1,GPT,95646662-9d80-4a07-bf28-fd0bf509070b,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
sdb : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, no-wind, 2048 sectors * 512 bytes
nvme0n1 : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, has-win, 2048 sectors * 512 bytes
sda : is-GPT, no-BIOSboot, has---ESP, liveusb, not-mmc, no-os, no-wind, 40 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
sdb2 : is-os, 64, apt-get, signed grub-pc grub-efi , grub2, grub-install, grubenv-ok, update-grub, not-far
nvme0n1p3 : is-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
nvme0n1p1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
nvme0n1p4 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sdb3 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sdb1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda2 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
Partitions info (2/3): _________________________________________________________
sdb2 : isnotESP, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme0n1p3 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot
nvme0n1p1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme0n1p4 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
sdb3 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sdb1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
Partitions info (3/3): _________________________________________________________
sdb2 : not--sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sdb
nvme0n1p3 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme0n1p1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme0n1p4 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
sdb3 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sdb
sdb1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sdb
sda2 : maybesepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda
sda1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk identifier: D53225F2-B423-44AE-ABE1-0F4BA75C3B91
Start End Sectors Size Type
nvme0n1p1 2048 206847 204800 100M EFI System
nvme0n1p2 206848 239615 32768 16M Microsoft reserved
nvme0n1p3 239616 999024639 998785024 476.3G Microsoft basic data
nvme0n1p4 999024640 1000214527 1189888 581M Windows recovery environment
Disk sda: 4.55 TiB, 5000981077504 bytes, 9767541167 sectors
Disk identifier: F495C889-E684-48F4-87DF-C44D9E662065
Start End Sectors Size Type
sda1 40 409639 409600 200M EFI System
sda2 411648 9767540735 9767129088 4.5T Microsoft basic data
Disk sdb: 223.57 GiB, 240057409024 bytes, 468862127 sectors
Disk identifier: 1B4433F8-EC3F-45B3-A2A2-0C018CE6B3D3
Start End Sectors Size Type
sdb1 2048 1050623 1048576 512M EFI System
sdb2 1050624 160106495 159055872 75.8G Linux filesystem
sdb3 160106496 468860927 308754432 147.2G Microsoft basic data
parted -lm (filtered): _________________________________________________________
sda:5001GB:scsi:512:4096:gpt:Seagate BUP Portable:;
1:20.5kB:210MB:210MB:fat32:EFI System Partition:boot, esp;
2:211MB:5001GB:5001GB:::msftdata;
sdb:240GB:scsi:512:512:gpt:Generic External:;
1:1049kB:538MB:537MB:fat32:EFI System Partition:boot, esp;
2:538MB:82.0GB:81.4GB:ext4::;
3:82.0GB:240GB:158GB:ntfs::msftdata;
nvme0n1:512GB:nvme:512:512:gpt:ESR512GMFCM-E8GBTNB4:;
1:1049kB:106MB:105MB:fat32:EFI system partition:boot, esp;
2:106MB:123MB:16.8MB::Microsoft reserved partition:msftres;
3:123MB:512GB:511GB:ntfs:Basic data partition:msftdata;
4:512GB:512GB:609MB:ntfs::hidden, diag;
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat 67E3-17ED ffae2dc6-748c-4a41-b125-b15f972357d7 EFI EFI System Partition
└─sda2 exfat 5D71-6D9A 93ec5390-05e9-43d3-b733-3c78222a09a6 Backup Plus
sdb
├─sdb1 vfat 8186-A096 f6b22ef0-a92b-4589-9de0-d5a001cbebc2 EFI System Partition
├─sdb2 ext4 2bba5d16-3e6c-45b2-a367-baca5249744d acf4ec14-2b11-4152-b2b1-3a039c78de29
└─sdb3 ntfs 5D8D721D6E4EC74A a671f97a-570d-4b0d-8c43-2528e731859b DatasLinux
nvme0n1
├─nvme0n1p1 vfat 56F0-74B0 95646662-9d80-4a07-bf28-fd0bf509070b SYSTEM EFI system partition
├─nvme0n1p2 6a146e04-29c0-47ac-8670-0550e1a96388 Microsoft reserved partition
├─nvme0n1p3 ntfs 9A30F14B30F12EBF 1d884a43-aaa0-434c-b86f-6a44c121f885 Windows Basic data partition
└─nvme0n1p4 ntfs 24B4F16FB4F14438 53e02132-6648-47d4-90e6-e9c5991ff7bd Windows RE tools Basic data partition
Mount points (filtered): _______________________________________________________
Avail Use% Mounted on
/dev/nvme0n1p3 85.5G 82% /mnt/boot-sav/nvme0n1p3
/dev/nvme0n1p4 89.2M 85% /mnt/boot-sav/nvme0n1p4
/dev/sda1 196.9M 0% /mnt/boot-sav/sda1
/dev/sda2 1.1T 75% /media/mario1/Backup Plus
/dev/sdb1 511M 0% /mnt/boot-sav/sdb1
/dev/sdb2 33.3G 50% /
/dev/sdb3 113.6G 23% /media/mario1/DatasLinux
Mount options (filtered): ______________________________________________________
/dev/nvme0n1p3 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p4 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/sda2 exfat rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro
/dev/sdb1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/sdb2 ext4 rw,relatime,errors=remount-ro
/dev/sdb3 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
=================== nvme0n1p1/efi/ubuntu/grub.cfg (filtered) ===================
search.fs_uuid 2bba5d16-3e6c-45b2-a367-baca5249744d root hd1,gpt2
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
====================== sdb2/boot/grub/grub.cfg (filtered) ======================
Ubuntu 2bba5d16-3e6c-45b2-a367-baca5249744d
Ubuntu, with Linux 5.15.0-46-generic 2bba5d16-3e6c-45b2-a367-baca5249744d
Ubuntu, with Linux 5.15.0-43-generic 2bba5d16-3e6c-45b2-a367-baca5249744d
Windows Boot Manager (on nvme0n1p1) osprober-efi-56F0-74B0
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###
========================== sdb2/etc/fstab (filtered) ===========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb2 during installation
UUID=2bba5d16-3e6c-45b2-a367-baca5249744d / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=56F0-74B0 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
======================= sdb2/etc/default/grub (filtered) =======================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
==================== sdb2: Location of files loaded by Grub ====================
GiB - GB File Fragment(s)
58,309341431 = 62,609178624 boot/grub/grub.cfg 1
39,527339935 = 42,442158080 boot/vmlinuz 1
4,323802948 = 4,642648064 boot/vmlinuz-5.15.0-43-generic 1
39,527339935 = 42,442158080 boot/vmlinuz-5.15.0-46-generic 1
4,323802948 = 4,642648064 boot/vmlinuz.old 1
32,364635468 = 34,751262720 boot/initrd.img 1
39,012176514 = 41,889005568 boot/initrd.img-5.15.0-43-generic 4
32,364635468 = 34,751262720 boot/initrd.img-5.15.0-46-generic 1
39,012176514 = 41,889005568 boot/initrd.img.old 4
===================== sdb2: ls -l /etc/grub.d/ (filtered) ======================
-rwxr-xr-x 1 root root 18683 Apr 15 17:50 10_linux
-rwxr-xr-x 1 root root 43031 Apr 15 17:50 10_linux_zfs
-rwxr-xr-x 1 root root 14180 Apr 15 17:50 20_linux_xen
-rwxr-xr-x 1 root root 13369 Apr 15 17:50 30_os-prober
-rwxr-xr-x 1 root root 1372 Apr 15 17:50 30_uefi-firmware
-rwxr-xr-x 1 root root 700 Feb 19 08:21 35_fwupd
-rwxr-xr-x 1 root root 214 Apr 15 17:50 40_custom
-rwxr-xr-x 1 root root 215 Apr 15 17:50 41_custom
=========================== sdb2/etc/grub.d/35_fwupd ===========================
#! /bin/sh
# SPDX-License-Identifier: LGPL-2.1+
set -e
[ -d ${pkgdatadir:?} ]
# shellcheck source=/dev/null
. "$pkgdatadir/grub-mkconfig_lib"
if [ -f /var/lib/fwupd/uefi_capsule.conf ] &&
ls /sys/firmware/efi/efivars/fwupd-*-0abba7dc-e516-4167-bbf5-4d9d1c739416 1>/dev/null 2>&1; then
. /var/lib/fwupd/uefi_capsule.conf
if [ "${EFI_PATH}" != "" ] && [ "${ESP}" != "" ]; then
echo "Adding Linux Firmware Updater entry" >&2
cat << EOF
menuentry 'Linux Firmware Updater' \$menuentry_id_option 'fwupd' {
EOF
${grub_probe:?}
prepare_grub_to_access_device '`${grub_probe} --target=device \${ESP}` | sed -e "s/^/\t/"'
cat << EOF
chainloader ${EFI_PATH}
}
EOF
fi
fi
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would reinstall the grub-efi-amd64-signed of
sdb2,
using the following options: sdb1/boot/efi
Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file
Blockers in case of suggested repair: __________________________________________
Please use this software in a live-session (live-CD or live-USB). This will enable this feature.
Final advice in case of suggested repair: ______________________________________
Please do not forget to make your UEFI firmware boot on the L'OS actuellement utilisé - Ubuntu 22.04.1 LTS CurrentSession entry (sdb1/efi/****/shim****.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\****\shim****.efi (**** will be updated in the final message)Je refais donc tes commandes que tu m'as cité n'étant pas certain que tu en aies besoin.
mario1@mario1-AORUS-15P-KD:~$ lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"
00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller])
Kernel driver in use: i915
Kernel modules: i915
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller])
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
mario1@mario1-AORUS-15P-KD:~$ mario1@mario1-AORUS-15P-KD:~$ ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
modalias : pci:v000010DEd00002520sv00001458sd00001533bc03sc00i00
vendor : NVIDIA Corporation
model : GA106M [GeForce RTX 3060 Mobile / Max-Q]
driver : nvidia-driver-515 - distro non-free recommended
driver : nvidia-driver-470 - distro non-free
driver : nvidia-driver-510 - distro non-free
driver : nvidia-driver-510-server - distro non-free
driver : nvidia-driver-470-server - distro non-free
driver : nvidia-driver-515-server - distro non-free
driver : xserver-xorg-video-nouveau - distro free builtin
mario1@mario1-AORUS-15P-KD:~$ mario1@mario1-AORUS-15P-KD:~$ uname -a
Linux mario1-AORUS-15P-KD 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
mario1@mario1-AORUS-15P-KD:~$ mario1@mario1-AORUS-15P-KD:~$ dpkg -l | grep nvidia
ii libnvidia-cfg1-515:amd64 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA binary OpenGL/GLX configuration library
ii libnvidia-common-515 515.65.01-0ubuntu0.22.04.1 all Shared files used by the NVIDIA libraries
ii libnvidia-compute-515:amd64 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA libcompute package
ii libnvidia-compute-515:i386 515.65.01-0ubuntu0.22.04.1 i386 NVIDIA libcompute package
ii libnvidia-decode-515:amd64 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA Video Decoding runtime libraries
ii libnvidia-decode-515:i386 515.65.01-0ubuntu0.22.04.1 i386 NVIDIA Video Decoding runtime libraries
ii libnvidia-egl-wayland1:amd64 1:1.1.9-1.1 amd64 Wayland EGL External Platform library -- shared library
ii libnvidia-encode-515:amd64 515.65.01-0ubuntu0.22.04.1 amd64 NVENC Video Encoding runtime library
ii libnvidia-encode-515:i386 515.65.01-0ubuntu0.22.04.1 i386 NVENC Video Encoding runtime library
ii libnvidia-extra-515:amd64 515.65.01-0ubuntu0.22.04.1 amd64 Extra libraries for the NVIDIA driver
ii libnvidia-fbc1-515:amd64 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-fbc1-515:i386 515.65.01-0ubuntu0.22.04.1 i386 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-gl-515:amd64 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-gl-515:i386 515.65.01-0ubuntu0.22.04.1 i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii linux-modules-nvidia-515-5.15.0-46-generic 5.15.0-46.49 amd64 Linux kernel nvidia modules for version 5.15.0-46
ii linux-modules-nvidia-515-generic-hwe-22.04 5.15.0-46.49 amd64 Extra drivers for nvidia-515 for the generic-hwe-22.04 flavour
ii linux-objects-nvidia-515-5.15.0-46-generic 5.15.0-46.49 amd64 Linux kernel nvidia modules for version 5.15.0-46 (objects)
ii linux-signatures-nvidia-5.15.0-46-generic 5.15.0-46.49 amd64 Linux kernel signatures for nvidia modules for version 5.15.0-46-generic
ii nvidia-compute-utils-515 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA compute utilities
ii nvidia-driver-515 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA driver metapackage
ii nvidia-kernel-common-515 515.65.01-0ubuntu0.22.04.1 amd64 Shared files used with the kernel module
ii nvidia-kernel-source-515 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA kernel source package
ii nvidia-prime 0.8.17.1 all Tools to enable NVIDIA's Prime
ii nvidia-settings 510.47.03-0ubuntu1 amd64 Tool for configuring the NVIDIA graphics driver
ii nvidia-utils-515 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA driver support binaries
ii screen-resolution-extra 0.18.2 all Extension for the nvidia-settings control panel
ii xserver-xorg-video-nvidia-515 515.65.01-0ubuntu0.22.04.1 amd64 NVIDIA binary Xorg driver
mario1@mario1-AORUS-15P-KD:~$ mario1@mario1-AORUS-15P-KD:~$ dpkg -l | grep -v ^ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version Architecture Description
+++-==========================================-==========================================-============-================================================================================
mario1@mario1-AORUS-15P-KD:~$ mario1@mario1-AORUS-15P-KD:~$ echo $XDG_SESSION_TYPE
x11
mario1@mario1-AORUS-15P-KD:~$ Hors ligne
#27 Le 17/08/2022, à 18:38
- Mario2020C
Re : Vérification de l'intégrité de mon installation
Et la dernière commande pour voir les erreurs:
mario1@mario1-AORUS-15P-KD:~$ journalctl --no-pager -b -p err
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG2.WKEN], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG2._DSW], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG2._PR0], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG2._PR3], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG3.WKEN], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG3._DSW], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG3._PR0], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG3._PR3], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PR00.CPOC], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PR00._CPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: integrity: Problem loading X.509 certificate -22
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: integrity: Problem loading X.509 certificate -22
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20210730/psargs-330)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20210730/psargs-330)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20210730/psargs-330)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS03._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20210730/psargs-330)
aoû 17 12:23:09 mario1-AORUS-15P-KD kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS04._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
aoû 17 12:23:13 mario1-AORUS-15P-KD kernel: mtd device must be supplied (device name is empty)
aoû 17 12:23:13 mario1-AORUS-15P-KD kernel:
aoû 17 12:23:18 mario1-AORUS-15P-KD systemd[1325]: Failed to start Service for snap application snapd-desktop-integration.snapd-desktop-integration.
aoû 17 12:23:20 mario1-AORUS-15P-KD gnome-session-binary[1674]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
aoû 17 12:23:20 mario1-AORUS-15P-KD gnome-session-binary[1674]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
aoû 17 12:23:53 mario1-AORUS-15P-KD gdm-password][2017]: gkr-pam: unable to locate daemon control file
aoû 17 12:23:56 mario1-AORUS-15P-KD systemd[2034]: Failed to start Service for snap application snapd-desktop-integration.snapd-desktop-integration.
aoû 17 12:23:57 mario1-AORUS-15P-KD systemd[2034]: Failed to start Application launched by gnome-session-binary.
aoû 17 12:23:57 mario1-AORUS-15P-KD systemd[2034]: Failed to start Application launched by gnome-session-binary.
aoû 17 12:23:57 mario1-AORUS-15P-KD systemd[2034]: Failed to start Application launched by gnome-session-binary.
aoû 17 12:23:57 mario1-AORUS-15P-KD systemd[2034]: Failed to start Application launched by gnome-session-binary.
aoû 17 12:23:58 mario1-AORUS-15P-KD kernel: ntfs3: Unknown parameter 'windows_names'
aoû 17 12:24:00 mario1-AORUS-15P-KD gdm-launch-environment][1320]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
aoû 17 12:24:00 mario1-AORUS-15P-KD kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
mario1@mario1-AORUS-15P-KD:~$ Merci
Hors ligne
#28 Le 17/08/2022, à 18:44
- xubu1957
Re : Vérification de l'intégrité de mon installation
Pour :
[drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownershipJ'ai pas bien compris dans bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1963805
Dernière modification par xubu1957 (Le 17/08/2022, à 18:44)
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#29 Le 17/08/2022, à 19:28
- iznobe
Re : Vérification de l'intégrité de mon installation
Bonjour , si @geole passe par là :
aoû 17 12:23:58 mario1-AORUS-15P-KD kernel: ntfs3: Unknown parameter 'windows_names'
c' etait pas dans une discussion a propos du " nouveau " NTFS3 , ou il etait dit que justement ce " nouveau pilote NTFS " ne reconnaissait pas cette option ?
Du coup ca voudrait dire qu ' il est maintenant implémenté nativement ?
autre remarque , au debut la session etait de type wayland , puis est maintenant passée a X11 .
Dernière modification par iznobe (Le 17/08/2022, à 19:30)
retour utilisable de commande
MSI Z490A-pro , i7 10700 , 32 GB RAM .
Hors ligne
#30 Le 17/08/2022, à 19:32
- xubu1957
Re : Vérification de l'intégrité de mon installation
> wiki.archlinux.org/title/NTFS
De Wikipédia :
NTFS (New Technology File System) est un système de fichiers de journalisation propriétaire développé par Microsoft. À partir de Windows NT 3.1, il s'agit du système de fichiers par défaut de la famille Windows NT.
Depuis Linux 5.15, ntfs3 prend en charge la lecture et l'écriture du système de fichiers. Tous les noyaux officiellement pris en charge avec les versions 5.15 ou plus récentes sont construits avec CONFIG_NTFS3_FS=met donc le prennent en charge.Pour les noyaux < 5.15, la prise en charge de la lecture et de l'écriture NTFS est fournie par le système de fichiers NTFS-3G FUSE. Ou vous pouvez utiliser NTFS3 rétroporté via ntfs3-dkms
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#31 Le 17/08/2022, à 20:27
- geole
Re : Vérification de l'intégrité de mon installation
iznobe a écrit :
Bonjour , si @geole passe par là :
aoû 17 12:23:58 mario1-AORUS-15P-KD kernel: ntfs3: Unknown parameter 'windows_names'
c' etait pas dans une discussion a propos du " nouveau " NTFS3 , ou il etait dit que justement ce " nouveau pilote NTFS " ne reconnaissait pas cette option ?
Du coup ca voudrait dire qu ' il est maintenant implémenté nativement ?
Ce parametre n'est plus reconnu, mais la création de fichiers avec des caractères interdits est refusée avec un message laissant dubitatif (impossible trouver date). je te conseille d'essayer
J'ai oublié de vérifier pour la taille des noms supérieurs à 256 caractères ou de plus de 20 niveaux. hiérarchiques.
Si c'est nativement bien traité, cela sera enfin une bonne chose
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
En ligne