Debian-facile

Bienvenue sur Debian-Facile, site d'aide pour les nouveaux utilisateurs de Debian.

Vous n'êtes pas identifié(e).

#1 10-06-2019 09:54:06

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

[Buster] - Messages d'erreurs au lancement

Hello,

Je cherche à résoudre les différents messages d'erreur qui apparaissent au lancement de Buster…
Si un expert sur le sujet pouvait jeter un coup d'œil dessus, et m'indiquer quoi faire ce serait cool!
Mais je ne lâche pas l'affaire de mon coté !
Merci d'avance.

Voici le journal que j'ai récupéré au lancement :


juin 09 17:05:58 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:58 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:58 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 systemd[1]: Failed to start keep memory of all UPnP devices that announced themselves.
juin 09 17:03:24 minissdpd[876]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
juin 09 17:03:21 wpa_supplicant[507]: bgscan simple: Failed to enable signal strength monitoring
juin 09 17:03:16 NetworkManager[517]: ((src/settings/nm-settings.c:899)): assertion '<dropped>' failed
juin 09 17:03:16 systemd[1]: Failed to start Raise network interfaces.
juin 09 17:03:16 dhclient[623]: exiting.
juin 09 17:03:16 dhclient[623]:
juin 09 17:03:16 dhclient[623]: process and the information we find helpful for debugging.
juin 09 17:03:16 dhclient[623]: before submitting a bug.  These pages explain the proper
juin 09 17:03:16 dhclient[623]: bugs on either our web page at www.isc.org or in the README file
juin 09 17:03:16 dhclient[623]: than a configuration issue please read the section on submitting
juin 09 17:03:16 dhclient[623]: If you think you have received this message due to a bug rather
juin 09 17:03:16 dhclient[623]:
juin 09 17:03:16 dhclient[623]: Failed to get interface index: No such device
juin 09 17:03:15 bluetoothd[508]: sap-server: Operation not permitted (1)
juin 09 17:03:15 bluetoothd[508]: Sap driver initialization failed.
juin 09 17:03:15 avahi-daemon[630]: chroot.c: open() failed: No such file or directory
juin 09 17:03:09 kernel: uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
juin 09 17:03:09 kernel: uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
juin 09 17:03:08 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 8 on unit 1: -32 (exp. 1).
juin 09 17:03:07 kernel: kvm: disabled by bios
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:04 systemd[1]: network.target: Job networking-routes.service/start deleted to break ordering cycle starting with network.target
juin 09 17:03:04 kernel: do_IRQ: 3.55 No irq handler for vector
juin 09 17:03:04 kernel: do_IRQ: 2.55 No irq handler for vector
juin 09 17:03:04 kernel: do_IRQ: 1.55 No irq handler for vector

 




1 - Les informations de la distribution installée

Debian 10.0
4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux



2 - Les informations du matériel

dmidecode -q



Résultat:


BIOS Information
  Vendor: Insyde
  Version: F.1F
  Release Date: 12/01/2015
  Address: 0xE0000
  Runtime Size: 128 kB
  ROM Size: 4096 kB
  Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
    Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
    5.25"/360 kB floppy services are supported (int 13h)
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    8042 keyboard services are supported (int 9h)
    CGA/mono video services are supported (int 10h)
    ACPI is supported
    USB legacy is supported
    Targeted content distribution is supported
    UEFI is supported
  BIOS Revision: 15.31
  Firmware Revision: 99.45

System Information
  Manufacturer: Hewlett-Packard
  Product Name: HP Notebook
  Version: Type1ProductConfigId
  Serial Number: CND5267PGC
  UUID: 6d9383a4-f51a-e511-a26a-5820b167894f
  Wake-up Type: Power Switch
  SKU Number: N0L65EA#ABF
  Family: 103C_5335KV G=N L=CON B=HP

Base Board Information
  Manufacturer: Hewlett-Packard
  Product Name: 8137
  Version: 99.45
  Serial Number: PFHTKD2WV8VRQM
  Asset Tag: Base Board Asset Tag
  Features:
    Board is a hosting board
    Board is replaceable
  Location In Chassis: Base Board Chassis Location
  Type: Motherboard

Chassis Information
  Manufacturer: Hewlett-Packard
  Type: Notebook
  Lock: Not Present
  Version: Chassis Version
  Serial Number: Chassis Serial Number
  Asset Tag: Chassis Asset Tag
  Boot-up State: Safe
  Power Supply State: Safe
  Thermal State: Safe
  Security Status: None
  OEM Information: 0x0000010E
  Height: Unspecified
  Number Of Power Cords: 1
  Contained Elements: 0
  SKU Number: Not Specified

System Slot Information
  Designation: J3606
  Type: x2 PCI Express 2 x2
  Current Usage: Available
  Length: Short
  ID: 1
  Characteristics:
    3.3 V is provided
    PME signal is supported
    Hot-plug devices are supported
  Bus Address: 0000:00:02.0

System Slot Information
  Designation: J3703
  Type: x1 PCI Express x1
  Current Usage: Available
  Length: Short
  ID: 2
  Characteristics:
    3.3 V is provided
    PME signal is supported
    Hot-plug devices are supported
  Bus Address: 0000:00:04.0

System Slot Information
  Designation: J3700
  Type: x1 PCI Express x1
  Current Usage: Available
  Length: Short
  ID: 3
  Characteristics:
    3.3 V is provided
    PME signal is supported
    Hot-plug devices are supported
  Bus Address: 0000:00:05.0

System Slot Information
  Designation: J3701
  Type: x1 PCI Express x1
  Current Usage: Available
  Length: Short
  ID: 4
  Characteristics:
    3.3 V is provided
    PME signal is supported
    Hot-plug devices are supported
  Bus Address: 0000:00:06.0

System Slot Information
  Designation: J2500
  Type: x1 PCI Express x1
  Current Usage: Available
  Length: Short
  ID: 4
  Characteristics:
    3.3 V is provided
    PME signal is supported
    Hot-plug devices are supported
  Bus Address: 0000:00:07.0

System Slot Information
  Designation: J615
  Type: 32-bit PC-98/Card
  Current Usage: Available
  Length: Long
  Characteristics:
    5.0 V is provided
    3.3 V is provided
    Cardbus is supported
    Modem ring resume is supported
    PME signal is supported
    SMBus signal is supported
  Bus Address: 0000:00:14.7

OEM Strings
  String 1: $HP$
  String 2: LOC#ABA
  String 3: ABS 70/71 78 79 7A 7B
  String 4: String4 for Original Equipment Manufacturer
  String 5: HP_Mute_LED_0_A
  String 6: String6 for Original Equipment Manufacturer
  String 7: String7 for Original Equipment Manufacturer
  String 8: String8 for Original Equipment Manufacturer
  String 9: FBYTE#3Q6b7K7P7W7jaBapaqasauawbPbSbhbpbzcbce.nF;
  String 10: BUILDID#15WW2THA602#SABF#DABF;
  String 11: String11 for Original Equipment Manufacturer

BIOS Language Information
  Language Description Format: Long
  Installable Languages: 5
    en|US|iso8859-1
    fr|CA|iso8859-1
    es|ES|iso8859-1
    zh|TW|unicode
    zh|CN|unicode
  Currently Installed Language: fr|CA|iso8859-1

System Boot Information
  Status: No errors detected

Portable Battery
  Location: Primary
  Manufacturer: 13-42....
  Manufacture Date: 8/7/2018
  Serial Number: 04369 8/7/2018
  Name: HS04041
  Chemistry: Lithium Ion
  Design Capacity: 38480 mWh
  Design Voltage: 14800 mV
  SBDS Version: 1
  Maximum Error: 11%
  OEM-specific Information: 0x000C090E

Onboard Device
  Reference Designation:  
  Type: Other
  Status: Enabled
  Type Instance: 1
  Bus Address: 0000:02:00.0

Physical Memory Array
  Location: System Board Or Motherboard
  Use: System Memory
  Error Correction Type: None
  Maximum Capacity: 4 GB
  Number Of Devices: 2

Memory Device
  Total Width: Unknown
  Data Width: Unknown
  Size: No Module Installed
  Form Factor: SODIMM
  Set: None
  Locator: Bottom
  Bank Locator: CHANNEL A
  Type: Unknown
  Type Detail: Unknown
  Speed: Unknown
  Manufacturer: Empty
  Serial Number: Empty
  Asset Tag: Asset Tag:
  Part Number: Empty
  Rank: Unknown
  Configured Memory Speed: Unknown
  Minimum Voltage: Unknown
  Maximum Voltage: Unknown
  Configured Voltage: Unknown

Memory Device
  Total Width: 64 bits
  Data Width: 64 bits
  Size: 4096 MB
  Form Factor: SODIMM
  Set: None
  Locator: Top
  Bank Locator: CHANNEL A
  Type: DDR3
  Type Detail: Synchronous Unbuffered (Unregistered)
  Speed: 1600 MT/s
  Manufacturer: Samsung
  Serial Number: 123CD8E8
  Asset Tag: Asset Tag:
  Part Number: M471B5173QH0-YK0  
  Rank: 1
  Configured Memory Speed: 800 MT/s
  Minimum Voltage: Unknown
  Maximum Voltage: Unknown
  Configured Voltage: Unknown

Memory Device Mapped Address
  Starting Address: 0x00000000000
  Ending Address: 0x000FFFFFFFF
  Range Size: 4 GB
  Partition Row Position: 1

Memory Array Mapped Address
  Starting Address: 0x00000000000
  Ending Address: 0x000FFFFFFFF
  Range Size: 4 GB
  Partition Width: 255

Processor Information
  Socket Designation: Socket FT1
  Type: Central Processor
  Family: A-Series
  Manufacturer: AMD processor
  ID: 01 0F 70 00 FF FB 8B 17
  Signature: Family 22, Model 0, Stepping 1
  Flags:
    FPU (Floating-point unit on-chip)
    VME (Virtual mode extension)
    DE (Debugging extension)
    PSE (Page size extension)
    TSC (Time stamp counter)
    MSR (Model specific registers)
    PAE (Physical address extension)
    MCE (Machine check exception)
    CX8 (CMPXCHG8 instruction supported)
    APIC (On-chip APIC hardware supported)
    SEP (Fast system call)
    MTRR (Memory type range registers)
    PGE (Page global enable)
    MCA (Machine check architecture)
    CMOV (Conditional move instruction supported)
    PAT (Page attribute table)
    PSE-36 (36-bit page size extension)
    CLFSH (CLFLUSH instruction supported)
    MMX (MMX technology supported)
    FXSR (FXSAVE and FXSTOR instructions supported)
    SSE (Streaming SIMD extensions)
    SSE2 (Streaming SIMD extensions 2)
    HTT (Multi-threading)
  Version: AMD A6-5200 APU with Radeon(TM) HD Graphics    
  Voltage: 1.3 V
  External Clock: 100 MHz
  Max Speed: 2000 MHz
  Current Speed: 2000 MHz
  Status: Populated, Enabled
  Upgrade: None
  Serial Number: NotSupport
  Asset Tag: FFFF
  Part Number: FFFF
  Core Count: 4
  Core Enabled: 4
  Thread Count: 4
  Characteristics:
    64-bit capable

Cache Information
  Socket Designation: L1 Cache
  Configuration: Enabled, Not Socketed, Level 1
  Operational Mode: Write Back
  Location: Internal
  Installed Size: 256 kB
  Maximum Size: 256 kB
  Supported SRAM Types:
    Pipeline Burst
  Installed SRAM Type: Pipeline Burst
  Speed: 1 ns
  Error Correction Type: Multi-bit ECC
  System Type: Unified
  Associativity: 2-way Set-associative

Cache Information
  Socket Designation: L2 Cache
  Configuration: Enabled, Not Socketed, Level 2
  Operational Mode: Write Back
  Location: Internal
  Installed Size: 2048 kB
  Maximum Size: 2048 kB
  Supported SRAM Types:
    Pipeline Burst
  Installed SRAM Type: Pipeline Burst
  Speed: 1 ns
  Error Correction Type: Multi-bit ECC
  System Type: Unified
  Associativity: 16-way Set-associative


 



3 - D'autres informations du matériel

dmidecode -t bios



Résultat:


# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
  Vendor: Insyde
  Version: F.1F
  Release Date: 12/01/2015
  Address: 0xE0000
  Runtime Size: 128 kB
  ROM Size: 4096 kB
  Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
    Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
    5.25"/360 kB floppy services are supported (int 13h)
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    8042 keyboard services are supported (int 9h)
    CGA/mono video services are supported (int 10h)
    ACPI is supported
    USB legacy is supported
    Targeted content distribution is supported
    UEFI is supported
  BIOS Revision: 15.31
  Firmware Revision: 99.45

Handle 0x000B, DMI type 13, 22 bytes
BIOS Language Information
  Language Description Format: Long
  Installable Languages: 5
    en|US|iso8859-1
    fr|CA|iso8859-1
    es|ES|iso8859-1
    zh|TW|unicode
    zh|CN|unicode
  Currently Installed Language: fr|CA|iso8859-1
 



4 - Et pour finir sur le hardware

lspci



Résultat:


00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Root Complex
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series]
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 0
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:02.5 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 01)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 39)
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 39)
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 39)
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 39)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 3a)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 02)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
00:14.7 SD Host controller: Advanced Micro Devices, Inc. [AMD] FCH SD Flash Controller (rev 01)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 5
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 07)
 

Hors ligne

#2 10-06-2019 10:04:34

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

tu as mis beaucoup de renseignements , c'est bien , tu as  fait un effort .

mais peux tu nous donner le nom de ton notebook ?

on sait que c'est un HP , un notebook , mais on sait pas son nom ou alors j'ai mal lu .

tu as beaucoup de problèmes de kernel , c'est pas  très bon signe ....

amicalement ,

alain.

smile

1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#3 10-06-2019 10:10:57

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

Voici le nom :

PC Portable HP Notebook 15-af008nf 15.6"

Hors ligne

#4 10-06-2019 10:24:56

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

je sais que je vais faire hurler mais , tu as essaye ubuntu  ?

1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#5 10-06-2019 10:42:28

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

Pas sur cet ordinateur… Il y avait Debian 9 précédemment.

Hors ligne

#6 10-06-2019 10:45:16

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

arf ! , j'ai rien dit alors .

1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#7 12-06-2019 20:19:37

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

Pour le message suivant :

kernel: pstore: crypto_comp_decompress failed


j'ai reçu une réponse par ailleurs qui m'a réglé ce premier point. 


cd /sys/fs/pstore
 


puis


ls
 


retour

dmesg-efi-153087460601001.enc.z dmesg-efi-153087460606001.enc.z dmesg-efi-153087460611001.enc.z
dmesg-efi-153087460602001.enc.z dmesg-efi-153087460607001.enc.z dmesg-efi-153087460612001.enc.z
dmesg-efi-153087460603001.enc.z dmesg-efi-153087460608001.enc.z dmesg-efi-153087460613001.enc.z
dmesg-efi-153087460604001.enc.z dmesg-efi-153087460609001.enc.z dmesg-efi-153087460614001.enc.z
dmesg-efi-153087460605001.enc.z dmesg-efi-153087460610001.enc.z


puis


3- rm dmesg-efi*
 

Hors ligne

#8 12-06-2019 20:42:24

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

que donne :

dmesg | tail -n 100


???

Dernière modification par Debian Alain (12-06-2019 20:44:03)


1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#9 12-06-2019 20:48:42

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement


[   12.365660] ACPI: AC Adapter [ACAD] (on-line)
[   12.401497] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[   12.401650] sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
[   12.401825] sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
[   12.439396] input: PC Speaker as /devices/platform/pcspkr/input/input8
[   12.460744] EFI Variables Facility v0.08 2004-May-17
[   12.682674] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   12.682754] sr 1:0:0:0: Attached scsi generic sg1 type 5
[   12.689486] pstore: Registered efi as persistent store backend
[   12.939031] battery: ACPI: Battery Slot [BAT1] (battery present)
[   13.242290] hp_wmi: query 0xd returned error 0x5
[   13.242472] input: HP WMI hotkeys as /devices/virtual/input/input9
[   13.295138] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   13.439938] rtl8188ee: rtl8188ee: FW Power Save off (module option)
[   13.440070] rtl8188ee: Using firmware rtlwifi/rtl8188efw.bin
[   13.474176] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[   13.474608] rtlwifi: rtlwifi: wireless switch is on
[   13.488551] Bluetooth: Core ver 2.22
[   13.488579] NET: Registered protocol family 31
[   13.488580] Bluetooth: HCI device and connection manager initialized
[   13.488587] Bluetooth: HCI socket layer initialized
[   13.488591] Bluetooth: L2CAP socket layer initialized
[   13.488602] Bluetooth: SCO socket layer initialized
[   13.508924] kvm: disabled by bios
[   13.529296] rtl8188ee 0000:02:00.0 wlp2s0: renamed from wlan0
[   13.537865] rtl8188ee 0000:02:00.0: firmware: direct-loading firmware rtlwifi/rtl8188efw.bin
[   13.568400] MCE: In-kernel MCE decoding enabled.
[   13.599242] EDAC amd64: Node 0: DRAM ECC disabled.
[   13.599246] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
[   13.622351] usbcore: registered new interface driver btusb
[   13.859453] snd_hda_intel 0000:00:01.1: Force to non-snoop mode
[   13.880390] media: Linux media interface: v0.10
[   13.928724] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card0/input10
[   14.087441] videodev: Linux video capture interface: v2.00
[   14.109830] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   14.109836] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   14.109839] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   14.109841] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
[   14.109843] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[   14.109847] snd_hda_codec_realtek hdaudioC1D0:      Mic=0x19
[   14.109850] snd_hda_codec_realtek hdaudioC1D0:      Internal Mic=0x12
[   14.124416] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/sound/card1/input11
[   14.125537] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input12
[   14.125648] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input13
[   14.251460] Adding 3620860k swap on /dev/sda3.  Priority:-2 extents:1 across:3620860k FS
[   14.463024] uvcvideo: Found UVC 1.00 device HP Webcam (04f2:b52d)
[   14.464861] uvcvideo: Failed to query (GET_INFO) UVC control 8 on unit 1: -32 (exp. 1).
[   14.474388] uvcvideo 4-1:1.0: Entity type for entity Extension 4 was not initialized!
[   14.474394] uvcvideo 4-1:1.0: Entity type for entity Extension 7 was not initialized!
[   14.474396] uvcvideo 4-1:1.0: Entity type for entity Processing 2 was not initialized!
[   14.474399] uvcvideo 4-1:1.0: Entity type for entity Camera 1 was not initialized!
[   14.474532] input: HP Webcam: HP Webcam as /devices/pci0000:00/0000:00:13.2/usb4/4-1/4-1:1.0/input/input14
[   14.474677] usbcore: registered new interface driver uvcvideo
[   14.474679] USB Video Class driver (1.1.1)
[   15.564606] uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
[   15.565064] uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
[   17.090320] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
[   17.706320] audit: type=1400 audit(1560362000.548:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=493 comm="apparmor_parser"
[   17.706378] audit: type=1400 audit(1560362000.548:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=492 comm="apparmor_parser"
[   17.777816] audit: type=1400 audit(1560362000.620:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=495 comm="apparmor_parser"
[   17.777828] audit: type=1400 audit(1560362000.620:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=495 comm="apparmor_parser"
[   17.799449] audit: type=1400 audit(1560362000.640:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=496 comm="apparmor_parser"
[   17.824284] audit: type=1400 audit(1560362000.664:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=497 comm="apparmor_parser"
[   17.824294] audit: type=1400 audit(1560362000.664:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=497 comm="apparmor_parser"
[   17.824298] audit: type=1400 audit(1560362000.664:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=497 comm="apparmor_parser"
[   17.844296] audit: type=1400 audit(1560362000.684:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=498 comm="apparmor_parser"
[   17.844310] audit: type=1400 audit(1560362000.684:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=498 comm="apparmor_parser"
[   21.817872] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   21.817877] Bluetooth: BNEP filters: protocol multicast
[   21.817887] Bluetooth: BNEP socket layer initialized
[   23.696599] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[   23.748661] r8169 0000:03:00.0: firmware: direct-loading firmware rtl_nic/rtl8106e-1.fw
[   23.750319] Generic PHY r8169-300:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[   24.014239] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[   24.024314] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   24.436048] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   24.857487] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   25.246458] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   27.093409] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   28.109063] wlp2s0: authenticate with ac:84:c9:ca:4d:a0
[   28.119615] wlp2s0: send auth to ac:84:c9:ca:4d:a0 (try 1/3)
[   28.124890] wlp2s0: authenticated
[   28.126338] wlp2s0: associate with ac:84:c9:ca:4d:a0 (try 1/3)
[   28.130477] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control off
[   28.130496] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[   28.130780] wlp2s0: RX AssocResp from ac:84:c9:ca:4d:a0 (capab=0x411 status=0 aid=1)
[   28.131316] wlp2s0: associated
[   28.265057] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[   33.583625] fuse init (API version 7.27)
[   97.672402] Bluetooth: RFCOMM TTY layer initialized
[   97.672413] Bluetooth: RFCOMM socket layer initialized
[   97.672426] Bluetooth: RFCOMM ver 1.11
[  126.899819] hidraw: raw HID events driver (C) Jiri Kosina
[  126.923780] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[  126.923793] Bluetooth: HIDP socket layer initialized
[  126.943382] hid-generic 0005:0A5C:4503.0001: unknown main item tag 0x0
[  126.943507] input: TeckNet BM308 as /devices/pci0000:00/0000:00:10.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:70/0005:0A5C:4503.0001/input/input15
[  126.943776] hid-generic 0005:0A5C:4503.0001: input,hidraw0: BLUETOOTH HID v1.29 Mouse [TeckNet BM308] on 00:1a:7d:da:71:13
 

Hors ligne

#10 12-06-2019 20:55:28

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

Voici aussi le dernier retour de la commande suivante pour remonter les erreurs:

sudo journalctl -p err


kernel: do_IRQ: 1.55 No irq handler for vector
kernel: do_IRQ: 2.55 No irq handler for vector
kernel: do_IRQ: 3.55 No irq handler for vector
systemd[1]: network.target: Job networking-routes.service/start deleted to break ordering cycle starting with network.target
kernel: kvm: disabled by bios
kernel: uvcvideo: Failed to query (GET_INFO) UVC control 8 on unit 1: -32 (exp. 1).
kernel: uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
kernel: uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
dhclient[620]: Failed to get interface index: No such device
dhclient[620]:
dhclient[620]: If you think you have received this message due to a bug rather
dhclient[620]: than a configuration issue please read the section on submitting
dhclient[620]: bugs on either our web page at www.isc.org or in the README file
dhclient[620]: before submitting a bug.  These pages explain the proper
dhclient[620]: process and the information we find helpful for debugging.
dhclient[620]:
dhclient[620]: exiting.
systemd[1]: Failed to start Raise network interfaces.
avahi-daemon[674]: chroot.c: open() failed: No such file or directory
bluetoothd[514]: Sap driver initialization failed.
bluetoothd[514]: sap-server: Operation not permitted (1)
NetworkManager[517]: ((src/settings/nm-settings.c:899)): assertion '<dropped>' failed
wpa_supplicant[524]: bgscan simple: Failed to enable signal strength monitoring
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
 

Dernière modification par RobGall (12-06-2019 20:55:55)

Hors ligne

#11 12-06-2019 20:59:02

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

peut être :

journalctl | tail -n 100


ainsi que :

lspci -nnk | grep -ie network

Dernière modification par Debian Alain (12-06-2019 21:01:14)


1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#12 12-06-2019 21:11:46

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

robgall@robgall:~$ sudo journalctl | tail -n 100
juin 12 19:55:34 robgall systemd[1]: Starting PackageKit Daemon...
juin 12 19:55:34 robgall PackageKit[1952]: daemon start
juin 12 19:55:35 robgall dbus-daemon[516]: [system] Successfully activated service 'org.freedesktop.PackageKit'
juin 12 19:55:35 robgall systemd[1]: Started PackageKit Daemon.
juin 12 19:55:37 robgall sudo[1566]: pam_unix(sudo:session): session closed for user root
juin 12 19:55:58 robgall sudo[1960]:  robgall : TTY=pts/0 ; PWD=/home/robgall ; USER=root ; COMMAND=/usr/bin/apt-get upgrade
juin 12 19:55:58 robgall sudo[1960]: pam_unix(sudo:session): session opened for user root by (uid=0)
juin 12 19:56:42 robgall sudo[1960]: pam_unix(sudo:session): session closed for user root
juin 12 19:57:17 robgall gnome-keyring-daemon[1095]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
juin 12 19:57:18 robgall gnome-keyring-daemon[1095]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
juin 12 19:57:19 robgall gnome-keyring-daemon[1095]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
juin 12 19:57:26 robgall gnome-keyring-daemon[1095]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
juin 12 20:01:50 robgall PackageKit[1952]: daemon quit
juin 12 20:01:50 robgall systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM
juin 12 20:01:50 robgall systemd[1]: packagekit.service: Succeeded.
juin 12 20:08:38 robgall systemd[1]: Starting Cleanup of Temporary Directories...
juin 12 20:08:38 robgall systemd-tmpfiles[3075]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
juin 12 20:08:38 robgall systemd-tmpfiles[3075]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly.
juin 12 20:08:38 robgall systemd-tmpfiles[3075]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
juin 12 20:08:38 robgall systemd-tmpfiles[3075]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
juin 12 20:08:38 robgall systemd-tmpfiles[3075]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly.
juin 12 20:08:38 robgall systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
juin 12 20:08:38 robgall systemd[1]: Started Cleanup of Temporary Directories.
juin 12 20:17:01 robgall CRON[3141]: pam_unix(cron:session): session opened for user root by (uid=0)
juin 12 20:17:01 robgall CRON[3142]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
juin 12 20:17:01 robgall CRON[3141]: pam_unix(cron:session): session closed for user root
juin 12 20:22:01 robgall sudo[3301]:  robgall : TTY=pts/0 ; PWD=/home/robgall ; USER=root ; COMMAND=/bin/journalctl -p err
juin 12 20:22:01 robgall sudo[3301]: pam_unix(sudo:session): session opened for user root by (uid=0)
juin 12 20:23:01 robgall sudo[3301]: pam_unix(sudo:session): session closed for user root
juin 12 20:23:12 robgall sudo[3321]:  robgall : TTY=pts/0 ; PWD=/home/robgall ; USER=root ; COMMAND=/bin/journalctl -p err
juin 12 20:23:12 robgall sudo[3321]: pam_unix(sudo:session): session opened for user root by (uid=0)
juin 12 20:24:20 robgall sudo[3321]: pam_unix(sudo:session): session closed for user root
juin 12 20:24:20 robgall gnome-terminal-[1556]: gtk_widget_get_realized: assertion 'GTK_IS_WIDGET (widget)' failed
juin 12 20:24:20 robgall gnome-terminal-[1556]: gtk_widget_get_realized: assertion 'GTK_IS_WIDGET (widget)' failed
juin 12 20:24:20 robgall gnome-terminal-[1556]: gtk_widget_get_realized: assertion 'GTK_IS_WIDGET (widget)' failed
juin 12 20:24:20 robgall systemd[1081]: gnome-terminal-server.service: Succeeded.
juin 12 20:28:30 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Activating service name='org.gnome.gedit' requested by ':1.74' (uid=1000 pid=3366 comm="nemo ")
juin 12 20:28:31 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Successfully activated service 'org.gnome.gedit'
juin 12 20:28:49 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Activating service name='org.gnome.gedit' requested by ':1.74' (uid=1000 pid=3366 comm="nemo ")
juin 12 20:28:49 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Successfully activated service 'org.gnome.gedit'
juin 12 20:29:41 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.77' (uid=1000 pid=3421 comm="gnome-terminal ")
juin 12 20:29:41 robgall systemd[1081]: Starting GNOME Terminal Server...
juin 12 20:29:41 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Successfully activated service 'org.gnome.Terminal'
juin 12 20:29:41 robgall systemd[1081]: Started GNOME Terminal Server.
juin 12 20:29:53 robgall sudo[3436]:  robgall : TTY=pts/0 ; PWD=/home/robgall ; USER=root ; COMMAND=/bin/journalctl -p err
juin 12 20:29:53 robgall sudo[3436]: pam_unix(sudo:session): session opened for user root by (uid=0)
juin 12 20:30:01 robgall CRON[3439]: pam_unix(cron:session): session opened for user root by (uid=0)
juin 12 20:30:01 robgall CRON[3440]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
juin 12 20:30:01 robgall CRON[3439]: pam_unix(cron:session): session closed for user root
juin 12 20:33:36 robgall systemd[1]: Started Run anacron jobs.
juin 12 20:33:36 robgall anacron[3471]: Anacron 2.3 started on 2019-06-12
juin 12 20:33:36 robgall anacron[3471]: Normal exit (0 jobs run)
juin 12 20:33:36 robgall systemd[1]: anacron.service: Succeeded.
juin 12 20:34:50 robgall sudo[3436]: pam_unix(sudo:session): session closed for user root
juin 12 20:35:27 robgall sudo[3486]:  robgall : TTY=pts/0 ; PWD=/home/robgall ; USER=root ; COMMAND=/bin/journalctl -p err
juin 12 20:35:27 robgall sudo[3486]: pam_unix(sudo:session): session opened for user root by (uid=0)
juin 12 20:36:23 robgall dbus-daemon[516]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.134' (uid=1000 pid=3408 comm="/usr/bin/gedit --gapplication-service ")
juin 12 20:36:23 robgall systemd[1]: Starting Hostname Service...
juin 12 20:36:23 robgall dbus-daemon[516]: [system] Successfully activated service 'org.freedesktop.hostname1'
juin 12 20:36:23 robgall systemd[1]: Started Hostname Service.
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:24 robgall gvfsd[1166]: mkdir failed on directory /var/run/samba: Permission non accordée
juin 12 20:36:32 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.58' (uid=1000 pid=1428 comm="/usr/lib/tracker/tracker-miner-fs ")
juin 12 20:36:32 robgall systemd[1081]: Starting Tracker metadata extractor...
juin 12 20:36:33 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
juin 12 20:36:33 robgall systemd[1081]: Started Tracker metadata extractor.
juin 12 20:36:44 robgall systemd[1081]: tracker-extract.service: Succeeded.
juin 12 20:36:53 robgall systemd[1]: systemd-hostnamed.service: Succeeded.
juin 12 20:40:35 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.58' (uid=1000 pid=1428 comm="/usr/lib/tracker/tracker-miner-fs ")
juin 12 20:40:35 robgall systemd[1081]: Starting Tracker metadata extractor...
juin 12 20:40:36 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
juin 12 20:40:36 robgall systemd[1081]: Started Tracker metadata extractor.
juin 12 20:40:46 robgall systemd[1081]: tracker-extract.service: Succeeded.
juin 12 20:42:55 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.58' (uid=1000 pid=1428 comm="/usr/lib/tracker/tracker-miner-fs ")
juin 12 20:42:55 robgall systemd[1081]: Starting Tracker metadata extractor...
juin 12 20:42:55 robgall dbus-daemon[1106]: [session uid=1000 pid=1106] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
juin 12 20:42:55 robgall systemd[1081]: Started Tracker metadata extractor.
juin 12 20:43:06 robgall systemd[1081]: tracker-extract.service: Succeeded.
juin 12 20:43:59 robgall sudo[3486]: pam_unix(sudo:session): session closed for user root
juin 12 20:47:19 robgall sudo[3730]:  robgall : TTY=pts/0 ; PWD=/home/robgall ; USER=root ; COMMAND=/bin/dmesg
juin 12 20:47:19 robgall sudo[3730]: pam_unix(sudo:session): session opened for user root by (uid=0)
juin 12 20:47:19 robgall sudo[3730]: pam_unix(sudo:session): session closed for user root
juin 12 21:01:54 robgall kernel: perf: interrupt took too long (2504 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
juin 12 21:05:27 robgall sudo[4071]:  robgall : TTY=pts/0 ; PWD=/home/robgall ; USER=root ; COMMAND=/bin/journalctl
juin 12 21:05:27 robgall sudo[4071]: pam_unix(sudo:session): session opened for user root by (uid=0)
 



robgall@robgall:~$ lspci -nnk | grep -ie network
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter [10ec:8179] (rev 01)
  Subsystem: Hewlett-Packard Company RTL8188EE Wireless Network Adapter [103c:804b]
 

Hors ligne

#13 12-06-2019 21:26:42

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

google me renvoie le rapport suivant :

https://bugs.launchpad.net/ubuntu/+sour … ug/1758653

que donne

ls /var/cache/samba/


poste ici la réponse : normalement , un message d'erreur

Dernière modification par Debian Alain (12-06-2019 22:28:06)


1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#14 12-06-2019 21:56:33

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

ls /var/cache/samba/


retour

gencache.tdb

Hors ligne

#15 12-06-2019 21:59:27

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

je ne sais pas .

je sèche .

1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#16 12-06-2019 22:19:24

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

le lien du rapport google ne fonctionne pas!?

Hors ligne

#17 12-06-2019 22:29:05

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

oui , faute de frappe . rectifié . tu peux recommencer .

1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#18 30-06-2019 09:20:57

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

Aux lignes suivantes dans le journal :

Failed to start Raise network interface
See 'systemctl status networking.service' for detais.
 



Voici le résultat pour le statut:


sudo service networking status
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-06-30 07:59:43 CEST; 1h 3min ago
     Docs: man:interfaces(5)
  Process: 520 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
 Main PID: 520 (code=exited, status=1/FAILURE)

juin 30 07:59:43 robgall dhclient[621]: than a configuration issue please read the section on submitting
juin 30 07:59:43 robgall dhclient[621]: bugs on either our web page at www.isc.org or in the README file
juin 30 07:59:43 robgall dhclient[621]: before submitting a bug.  These pages explain the proper
juin 30 07:59:43 robgall dhclient[621]: process and the information we find helpful for debugging.
juin 30 07:59:43 robgall dhclient[621]:
juin 30 07:59:43 robgall dhclient[621]: exiting.
juin 30 07:59:43 robgall ifup[520]: ifup: failed to bring up eth0
juin 30 07:59:43 robgall systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
juin 30 07:59:43 robgall systemd[1]: networking.service: Failed with result 'exit-code'.
juin 30 07:59:43 robgall systemd[1]: Failed to start Raise network interfaces.
 



Une idée pour corriger ce point là?

Hors ligne

#19 30-06-2019 09:30:34

Debian Alain
Adhérent(e)
Lieu : zone 51
Distrib. : W$10 / stable / ubuntu / F29 / testing
Noyau : Linux 4.19.0-5 amd 64 debian
(G)UI : Gnome wayland / Gdm3
Inscription : 11-03-2017

Re : [Buster] - Messages d'erreurs au lancement

est ce que tu as internet  ?

de mémoire , je crois que c'est un problème de timing tout bête entre le systeme qui met en place les pilotes  réseau  et le matériel qui réagit parfois en retard .

je crois  que c'est un souci mineur .

1498812139.jpg Cats, funniest creatures in animal kingdom - Funny cat compilation
RYZEN7 1700X - PRIME X370 PRO - 16 Go DDR4 - RADEON PULSE RX 550 4GB DDR5 OC UEFI - CORSAIR RM750X - SSD crucial MX500 500GB

Hors ligne

#20 30-06-2019 09:53:33

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

Oui j'ai bien internet. Ok c'est noté.
Merci pour ce prompt retour!

Hors ligne

#21 30-06-2019 10:34:25

raleur
Membre
Inscription : 03-10-2014

Re : [Buster] - Messages d'erreurs au lancement

Apparemment une interface ethernet "eth0" est définie dans /etc/network/interfaces. Est-ce qu'une interface existe bien avec ce nom, et pas quelque chose comme "enpXsY" ?

Hors ligne

#22 30-06-2019 11:06:03

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

Voici ce qu'il y a dans /etc/network/interfaces


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback
 



…et dans /etc/network/interfaces.d/setup


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
 

Hors ligne

#23 30-06-2019 11:35:14

raleur
Membre
Inscription : 03-10-2014

Re : [Buster] - Messages d'erreurs au lancement

Je sais déjà qu'il y avait ces lignes avec eth0. La question est : y a-t-il vraiment une interface réseau avec ce nom ?

ip link

Hors ligne

#24 30-06-2019 12:48:26

RobGall
Membre
Lieu : Orsay
Distrib. : Debian 10.0
Noyau : Linux 4.19.0-5-amd64
(G)UI : Cinnamon
Inscription : 26-05-2019

Re : [Buster] - Messages d'erreurs au lancement

voici le retour de


ip link
 


1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 58:20:b1:67:89:4f brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether d8:5d:e2:4d:d2:6f brd ff:ff:ff:ff:ff:ff
 

Hors ligne

#25 30-06-2019 14:57:36

raleur
Membre
Inscription : 03-10-2014

Re : [Buster] - Messages d'erreurs au lancement

Donc il n'y a pas d'interface eth0, pas étonnant que le service networking ne soit pas content si tu lui dis de configurer une interface qui n'existe pas. Supprime ce fichier /etc/network/interfaces.d/setup ou commente toutes ses lignes avec #.

Hors ligne

Pied de page des forums