Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

message d'erreur arret/reboot

Wed Oct 16, 2019 10:48 am

Bonjour a tous , je suis bloqué sur mon raspberry qui refuse de s'arreter ou rebooter proprement .

j'ai essayé de nettoyer les fichiers tmp , et vider les logs , rien n'y fait .

quelqu'un aurait t'"il une solution ou une piste ?


voici le message :

Image

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Wed Oct 16, 2019 10:49 am

je lui ai fait un apt update pour qu'il soit a jour de la date et heure .

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Wed Oct 16, 2019 10:58 am

j'ai essayé ça , mais ça ne donne rien


https://www.linuxuprising.com/2019/10/h ... -logs.html

totoharibo
Posts: 4256
Joined: Thu Jan 24, 2013 8:43 am

Re: message d'erreur arret/reboot

Wed Oct 16, 2019 3:11 pm

que t'écrit :
systemctl status systemd-journald

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Wed Oct 16, 2019 3:45 pm

systemd-journald.service - Journal Service
Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor
Active: active (running) since Wed 2019-10-16 14:13:19 CEST; 1min 1s ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 91 (systemd-journal)
Status: "Processing requests..."
CGroup: /system.slice/systemd-journald.service
└─91 /lib/systemd/systemd-journald

oct. 16 14:13:19 VTLD systemd-journald[91]: Journal started
oct. 16 14:13:19 VTLD systemd-journald[91]: Runtime journal (/run/log/journal/ac
oct. 16 14:13:19 VTLD systemd-journald[91]: Runtime journal (/run/log/journal/ac
Warning: Journal has been rotated since unit was started.

totoharibo
Posts: 4256
Joined: Thu Jan 24, 2013 8:43 am

Re: message d'erreur arret/reboot

Wed Oct 16, 2019 4:54 pm

que donne
tail /var/syslog
et aussi
systemctl status plymouth-poweroff

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Wed Oct 16, 2019 5:08 pm

tail /var/syslog

tail: impossible d'ouvrir '/var/syslog' en lecture: Aucun fichier ou dossier de ce type



systemctl status plymouth-poweroff:

plymouth-poweroff.service - Show Plymouth Power Off Screen
Loaded: loaded (/lib/systemd/system/plymouth-poweroff.service; static; vendor preset : enabled )
Active: inactive (dead)

totoharibo
Posts: 4256
Joined: Thu Jan 24, 2013 8:43 am

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 12:49 pm

mes excuses c'est /var/log/syslog

regarde aussi journalctl

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 7:31 pm

bash: /var/log/syslog: Permission non accordée

Logs begin at Thu 2016-11-03 18:16:42 CET, end at Wed 2
nov. 03 18:16:42 VTLD kernel: Booting Linux on physical CP
nov. 03 18:16:42 VTLD kernel: Linux version 4.14.98-v7+ (d
nov. 03 18:16:42 VTLD kernel: CPU: ARMv7 Processor [410fd0
nov. 03 18:16:42 VTLD kernel: CPU: div instructions availa
nov. 03 18:16:42 VTLD kernel: CPU: PIPT / VIPT nonaliasing
nov. 03 18:16:42 VTLD kernel: OF: fdt: Machine model: Rasp
nov. 03 18:16:42 VTLD kernel: Memory policy: Data cache wr
nov. 03 18:16:42 VTLD kernel: cma: Reserved 8 MiB at 0x2f8
nov. 03 18:16:42 VTLD kernel: On node 0 totalpages: 196608
nov. 03 18:16:42 VTLD kernel: free_area_init_node: node 0,
nov. 03 18:16:42 VTLD kernel: Normal zone: 1728 pages us
nov. 03 18:16:42 VTLD kernel: Normal zone: 0 pages reser
nov. 03 18:16:42 VTLD kernel: Normal zone: 196608 pages,
nov. 03 18:16:42 VTLD kernel: percpu: Embedded 17 pages/cp
nov. 03 18:16:42 VTLD kernel: pcpu-alloc: s38720 r8192 d22
nov. 03 18:16:42 VTLD kernel: pcpu-alloc: [0] 0 [0] 1 [0]
nov. 03 18:16:42 VTLD kernel: Built 1 zonelists, mobility
nov. 03 18:16:42 VTLD kernel: Kernel command line: 8250.nr
nov. 03 18:16:42 VTLD kernel: PID hash table entries: 4096
nov. 03 18:16:42 VTLD kernel: Dentry cache hash table entr
nov. 03 18:16:42 VTLD kernel: Inode-cache hash table entri
nov. 03 18:16:42 VTLD kernel: Memory: 757532K/786432K avai
nov. 03 18:16:42 VTLD kernel: Virtual kernel memory layout
vector : 0xffff0000 - 0
fixmap : 0xffc00000 - 0
vmalloc : 0xb0800000 - 0
lowmem : 0x80000000 - 0
modules : 0x7f000000 - 0
.text : 0x80008000 - 0
.init : 0x80b00000 - 0
.data : 0x80c00000 - 0
.bss : 0x80c97ef8 - 0
nov. 03 18:16:42 VTLD kernel: SLUB: HWalign=64, Order=0-3,
nov. 03 18:16:42 VTLD kernel: ftrace: allocating 25298 ent
nov. 03 18:16:42 VTLD kernel: Hierarchical RCU implementat
nov. 03 18:16:42 VTLD kernel: NR_IRQS: 16, nr_irqs: 16, pr
lines 1-37

epoch1970
Posts: 3901
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 8:40 pm

"sudo tail -500 /var/log/syslog" -> Les 500 dernières lignes du fichier de traces système
"sudo head -500 /var/log/syslog" -> les 500 premières lignes du fichier
"sudo less /var/log/syslog" -> affichage paginé du fichier depuis le debut. Diverses touches clavier pour manipuler le fichier. Return pour avancer d'une ligne, barre d'espace de tout un écran, etc. "man less" pour les détails.
"sudo cat /var/log/syslog" -> tout le fichier imprimé d'un coup. Peut être long s'il y a beaucoup de lignes.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 8:43 pm

oulaaaaa vous me causez en chinois je suis pas un spécialiste ^^

je suis un utilisateur lambda ultra débutant :D

je dois faire quoi Epoch1970 ?

epoch1970
Posts: 3901
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 8:55 pm

  • ouvrir un terminal
  • taper la commande: sudo tail -500 /var/log/syslog
    (la machine va demander le mot de passe utilisateur, lui donner)
  • lire le bazar qui s'est affiché, le copier-coller dans cette discussion si ce qui est imprimé semble avoir un rapport avec le schmilblick.
  • Si le messages sont sans intérêt évident, effacer la fenêtre de terminal (ou en ouvrir une nouvelle) pour faire place nette, et envoyer la sauce complète: sudo cat /var/log/syslog
Il n'y a pas de grand secrets dans le fichier de log, pas de soucis à le poster (à part la taille du message...)

EDIT: Utiliser de préférence le bouton "</>" lors du post sur le forum. Permet de coller le texte au sein d'un bloc [ code ][ /code ], qui est

Code: Select all

bien plus lisible
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 8:59 pm

Wow , euh ok ya du contenu :shock: :shock:

Code: Select all

Oct 16 21:19:39 VTLD kernel: [    0.172465] FS-Cache: Netfs 'nfs' registered for                      caching
Oct 16 21:19:39 VTLD kernel: [    0.173076] NFS: Registering the id_resolver key                      type
Oct 16 21:19:39 VTLD kernel: [    0.173102] Key type id_resolver registered
Oct 16 21:19:39 VTLD systemd[1]: Reached target Remote File Systems.
Oct 16 21:19:39 VTLD kernel: [    0.173107] Key type id_legacy registered
Oct 16 21:19:39 VTLD kernel: [    0.173123] nfs4filelayout_init: NFSv4 File Layo                     ut Driver Registering...
Oct 16 21:19:39 VTLD kernel: [    0.175063] Block layer SCSI generic (bsg) drive                     r version 0.4 loaded (major 251)
Oct 16 21:19:39 VTLD kernel: [    0.175194] io scheduler noop registered
Oct 16 21:19:39 VTLD systemd[1]: Started Tell Plymouth To Write Out Runtime Data                     .
Oct 16 21:19:39 VTLD kernel: [    0.175202] io scheduler deadline registered (de                     fault)
Oct 16 21:19:39 VTLD kernel: [    0.175374] io scheduler cfq registered
Oct 16 21:19:39 VTLD kernel: [    0.175381] io scheduler mq-deadline registered
Oct 16 21:19:39 VTLD kernel: [    0.175387] io scheduler kyber registered
Oct 16 21:19:39 VTLD systemd[1]: Started Set console font and keymap.
Oct 16 21:19:39 VTLD kernel: [    0.178146] BCM2708FB: allocated DMA memory ef91                     0000
Oct 16 21:19:39 VTLD kernel: [    0.178172] BCM2708FB: allocated DMA channel 0 @                      b0813000
Oct 16 21:19:39 VTLD kernel: [    0.194080] Console: switching to colour frame b                     uffer device 60x40
Oct 16 21:19:39 VTLD systemd[1]: Started Create Volatile Files and Directories.
Oct 16 21:19:39 VTLD kernel: [    0.202665] bcm2835-rng 3f104000.rng: hwrng regi                     stered
Oct 16 21:19:39 VTLD systemd[1]: Reached target System Time Synchronized.
Oct 16 21:19:39 VTLD systemd[1]: Starting Update UTMP about System Boot/Shutdown                     ...
Oct 16 21:19:39 VTLD systemd[1]: Started Show Plymouth Boot Screen.
Oct 16 21:19:39 VTLD systemd[1]: Reached target Encrypted Volumes.
Oct 16 21:19:39 VTLD systemd[1]: Reached target Paths.
Oct 16 21:19:39 VTLD systemd[1]: Started Forward Password Requests to Plymouth D                     irectory Watch.
Oct 16 21:19:39 VTLD systemd[1]: Started Update UTMP about System Boot/Shutdown.
Oct 16 21:19:39 VTLD systemd[1]: Reached target System Initialization.
Oct 16 21:19:39 VTLD systemd[1]: Listening on D-Bus System Message Bus Socket.
Oct 16 21:19:39 VTLD systemd[1]: avahi-daemon.socket: Socket service avahi-daemo                     n.service not loaded, refusing.
Oct 16 21:19:39 VTLD systemd[1]: Failed to listen on Avahi mDNS/DNS-SD Stack Act                     ivation Socket.
Oct 16 21:19:39 VTLD systemd[1]: Started Daily Cleanup of Temporary Directories.
Oct 16 21:19:39 VTLD systemd[1]: apt-daily.timer: Adding 8h 41min 25.383919s ran                     dom time.
Oct 16 21:19:39 VTLD systemd[1]: Started Daily apt download activities.
Oct 16 21:19:39 VTLD systemd[1]: apt-daily-upgrade.timer: Adding 8min 16.708814s                      random time.
Oct 16 21:19:39 VTLD systemd[1]: Started Daily apt upgrade and clean activities.
Oct 16 21:19:39 VTLD systemd[1]: Reached target Timers.
Oct 16 21:19:39 VTLD systemd[1]: Listening on triggerhappy.socket.
Oct 16 21:19:39 VTLD systemd[1]: Reached target Sockets.
Oct 16 21:19:39 VTLD systemd[1]: Reached target Basic System.
Oct 16 21:19:39 VTLD systemd[1]: Starting triggerhappy global hotkey daemon...
Oct 16 21:19:39 VTLD systemd[1]: Starting LSB: Switch to ondemand cpu governor (                     unless shift key is pressed)...
Oct 16 21:19:39 VTLD kernel: [    0.202796] vc-mem: phys_addr:0x00000000 mem_bas                     e=0x3ec00000 mem_size:0x40000000(1024 MiB)
Oct 16 21:19:39 VTLD systemd[1]: Starting dhcpcd on all interfaces...
Oct 16 21:19:39 VTLD kernel: [    0.203255] vc-sm: Videocore shared memory drive                     r
Oct 16 21:19:39 VTLD kernel: [    0.203530] gpiomem-bcm2835 3f200000.gpiomem: In                     itialised: Registers at 0x3f200000
Oct 16 21:19:39 VTLD kernel: [    0.213271] brd: module loaded
Oct 16 21:19:39 VTLD kernel: [    0.222103] loop: module loaded
Oct 16 21:19:39 VTLD systemd[1]: Starting LSB: Autogenerate and use a swap file.                     ..
Oct 16 21:19:39 VTLD kernel: [    0.222115] Loading iSCSI transport class v2.0-8                     70.
Oct 16 21:19:39 VTLD kernel: [    0.222755] libphy: Fixed MDIO Bus: probed
Oct 16 21:19:39 VTLD kernel: [    0.222851] usbcore: registered new interface dr                     iver lan78xx
Oct 16 21:19:39 VTLD systemd[1]: Started Regular background program processing d                     aemon.
Oct 16 21:19:39 VTLD kernel: [    0.222904] usbcore: registered new interface dr                     iver smsc95xx
Oct 16 21:19:39 VTLD kernel: [    0.222920] dwc_otg: version 3.00a 10-AUG-2012 (                     platform bus)
Oct 16 21:19:39 VTLD kernel: [    0.250798] dwc_otg 3f980000.usb: base=0xf098000                     0
Oct 16 21:19:39 VTLD kernel: [    0.451001] Core Release: 2.80a
Oct 16 21:19:39 VTLD systemd[1]: Started D-Bus System Message Bus.
Oct 16 21:19:39 VTLD kernel: [    0.451010] Setting default values for core para                     ms
Oct 16 21:19:39 VTLD kernel: [    0.451040] Finished setting default values for                      core params
Oct 16 21:19:39 VTLD kernel: [    0.651280] Using Buffer DMA mode
Oct 16 21:19:39 VTLD kernel: [    0.651286] Periodic Transfer Interrupt Enhancem                     ent - disabled
Oct 16 21:19:39 VTLD cron[194]: (CRON) INFO (pidfile fd = 3)
Oct 16 21:19:39 VTLD kernel: [    0.651291] Multiprocessor Interrupt Enhancement                      - disabled
Oct 16 21:19:39 VTLD kernel: [    0.651298] OTG VER PARAM: 0, OTG VER FLAG: 0
Oct 16 21:19:39 VTLD kernel: [    0.651314] Dedicated Tx FIFOs mode
Oct 16 21:19:39 VTLD kernel: [    0.651747] WARN::dwc_otg_hcd_init:1046: FIQ DMA                      bounce buffers: virt = 0xaf904000 dma = 0xef904000 len=9024
Oct 16 21:19:39 VTLD systemd-udevd[204]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD kernel: [    0.651771] FIQ FSM acceleration enabled for :
Oct 16 21:19:39 VTLD kernel: [    0.651771] Non-periodic Split Transactions
Oct 16 21:19:39 VTLD kernel: [    0.651771] Periodic Split Transactions
Oct 16 21:19:39 VTLD kernel: [    0.651771] High-Speed Isochronous Endpoints
Oct 16 21:19:39 VTLD systemd-udevd[203]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD kernel: [    0.651771] Interrupt/Control Split Transaction                      hack enabled
Oct 16 21:19:39 VTLD kernel: [    0.651778] dwc_otg: Microframe scheduler enable                     d
Oct 16 21:19:39 VTLD kernel: [    0.651824] WARN::hcd_init_fiq:459: FIQ on core                      1 at 0x805ed94c
Oct 16 21:19:39 VTLD kernel: [    0.651835] WARN::hcd_init_fiq:460: FIQ ASM at 0                     x805edcb4 length 36
Oct 16 21:19:39 VTLD thd[189]: Found socket passed from systemd
Oct 16 21:19:39 VTLD kernel: [    0.651847] WARN::hcd_init_fiq:486: MPHI regs_ba                     se at 0xf0006000
Oct 16 21:19:39 VTLD kernel: [    0.651898] dwc_otg 3f980000.usb: DWC OTG Contro                     ller
Oct 16 21:19:39 VTLD kernel: [    0.651929] dwc_otg 3f980000.usb: new USB bus re                     gistered, assigned bus number 1
Oct 16 21:19:39 VTLD kernel: [    0.651959] dwc_otg 3f980000.usb: irq 62, io mem                      0x00000000
Oct 16 21:19:39 VTLD cron[194]: (CRON) INFO (Running @reboot jobs)
Oct 16 21:19:39 VTLD kernel: [    0.652006] Init: Port Power? op_state=1
Oct 16 21:19:39 VTLD kernel: [    0.652011] Init: Power Port (0)
Oct 16 21:19:39 VTLD kernel: [    0.652212] usb usb1: New USB device found, idVe                     ndor=1d6b, idProduct=0002
Oct 16 21:19:39 VTLD dhcpcd[192]: dev: loaded udev
Oct 16 21:19:39 VTLD kernel: [    0.652222] usb usb1: New USB device strings: Mf                     r=3, Product=2, SerialNumber=1
Oct 16 21:19:39 VTLD kernel: [    0.652231] usb usb1: Product: DWC OTG Controlle                     r
Oct 16 21:19:39 VTLD kernel: [    0.652239] usb usb1: Manufacturer: Linux 4.14.9                     8-v7+ dwc_otg_hcd
Oct 16 21:19:39 VTLD dhcpcd[192]: no valid interfaces found
Oct 16 21:19:39 VTLD dhcpcd[192]: forked to background, child pid 223
Oct 16 21:19:39 VTLD kernel: [    0.652247] usb usb1: SerialNumber: 3f980000.usb
Oct 16 21:19:39 VTLD kernel: [    0.652829] hub 1-0:1.0: USB hub found
Oct 16 21:19:39 VTLD kernel: [    0.652868] hub 1-0:1.0: 1 port detected
Oct 16 21:19:39 VTLD kernel: [    0.653365] dwc_otg: FIQ enabled
Oct 16 21:19:39 VTLD systemd-udevd[229]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD kernel: [    0.653370] dwc_otg: NAK holdoff enabled
Oct 16 21:19:39 VTLD kernel: [    0.653375] dwc_otg: FIQ split-transaction FSM e                     nabled
Oct 16 21:19:39 VTLD kernel: [    0.653385] Module dwc_common_port init
Oct 16 21:19:39 VTLD systemd-udevd[231]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD kernel: [    0.653624] usbcore: registered new interface dr                     iver usb-storage
Oct 16 21:19:39 VTLD systemd-udevd[234]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD kernel: [    0.653778] mousedev: PS/2 mouse device common f                     or all mice
Oct 16 21:19:39 VTLD kernel: [    0.653846] IR NEC protocol handler initialized
Oct 16 21:19:39 VTLD kernel: [    0.653851] IR RC5(x/sz) protocol handler initia                     lized
Oct 16 21:19:39 VTLD systemd[1]: Starting Login Service...
Oct 16 21:19:39 VTLD kernel: [    0.653856] IR RC6 protocol handler initialized
Oct 16 21:19:39 VTLD kernel: [    0.653862] IR JVC protocol handler initialized
Oct 16 21:19:39 VTLD kernel: [    0.653867] IR Sony protocol handler initialized
Oct 16 21:19:39 VTLD kernel: [    0.653872] IR SANYO protocol handler initialize                     d
Oct 16 21:19:39 VTLD systemd-udevd[235]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD kernel: [    0.653877] IR Sharp protocol handler initialize                     d
Oct 16 21:19:39 VTLD kernel: [    0.653882] IR MCE Keyboard/mouse protocol handl                     er initialized
Oct 16 21:19:39 VTLD kernel: [    0.653887] IR XMP protocol handler initialized
Oct 16 21:19:39 VTLD kernel: [    0.654546] bcm2835-wdt 3f100000.watchdog: Broad                     com BCM2835 watchdog timer
Oct 16 21:19:39 VTLD systemd[1]: Starting Disable WiFi if country not set...
Oct 16 21:19:39 VTLD kernel: [    0.654802] bcm2835-cpufreq: min=600000 max=1200                     000
Oct 16 21:19:39 VTLD kernel: [    0.655152] sdhci: Secure Digital Host Controlle                     r Interface driver
Oct 16 21:19:39 VTLD systemd[1]: Starting Check for v3d driver...
Oct 16 21:19:39 VTLD kernel: [    0.655156] sdhci: Copyright(c) Pierre Ossman
Oct 16 21:19:39 VTLD kernel: [    0.655493] mmc-bcm2835 3f300000.mmc: could not                      get clk, deferring probe
Oct 16 21:19:39 VTLD kernel: [    0.655804] sdhost-bcm2835 3f202000.mmc: could n                     ot get clk, deferring probe
Oct 16 21:19:39 VTLD kernel: [    0.655897] sdhci-pltfm: SDHCI platform and OF d                     river helper
Oct 16 21:19:39 VTLD systemd[1]: Starting System Logging Service...
Oct 16 21:19:39 VTLD kernel: [    0.657273] ledtrig-cpu: registered to indicate                      activity on CPUs
Oct 16 21:19:39 VTLD kernel: [    0.657442] hidraw: raw HID events driver (C) Ji                     ri Kosina
Oct 16 21:19:39 VTLD kernel: [    0.657582] usbcore: registered new interface dr                     iver usbhid
Oct 16 21:19:39 VTLD kernel: [    0.657587] usbhid: USB HID core driver
Oct 16 21:19:39 VTLD systemd-udevd[238]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD kernel: [    0.658292] vchiq: vchiq_init_state: slot_zero =                      af980000, is_master = 0
Oct 16 21:19:39 VTLD kernel: [    0.659704] [vc_sm_connected_init]: start
Oct 16 21:19:39 VTLD kernel: [    0.668316] [vc_sm_connected_init]: end - return                     ing 0
Oct 16 21:19:39 VTLD kernel: [    0.668964] Initializing XFRM netlink socket
Oct 16 21:19:39 VTLD kernel: [    0.668989] NET: Registered protocol family 17
Oct 16 21:19:39 VTLD systemd[1]: Started triggerhappy global hotkey daemon.
Oct 16 21:19:39 VTLD kernel: [    0.669108] Key type dns_resolver registered
Oct 16 21:19:39 VTLD kernel: [    0.669665] Registering SWP/SWPB emulation handl                     er
Oct 16 21:19:39 VTLD kernel: [    0.670259] registered taskstats version 1
Oct 16 21:19:39 VTLD systemd[1]: Started dhcpcd on all interfaces.
Oct 16 21:19:39 VTLD kernel: [    0.676029] uart-pl011 3f201000.serial: cts_even                     t_workaround enabled
Oct 16 21:19:39 VTLD kernel: [    0.676100] 3f201000.serial: ttyAMA0 at MMIO 0x3                     f201000 (irq = 87, base_baud = 0) is a PL011 rev2
Oct 16 21:19:39 VTLD kernel: [    0.677800] mmc-bcm2835 3f300000.mmc: mmc_debug:                     0 mmc_debug2:0
Oct 16 21:19:39 VTLD systemd[1]: Started Disable WiFi if country not set.
Oct 16 21:19:39 VTLD kernel: [    0.677810] mmc-bcm2835 3f300000.mmc: DMA channe                     l allocated
Oct 16 21:19:39 VTLD kernel: [    0.732213] sdhost: log_buf @ af907000 (ef907000                     )
Oct 16 21:19:39 VTLD kernel: [    0.769731] mmc1: queuing unknown CIS tuple 0x80                      (2 bytes)
Oct 16 21:19:39 VTLD systemd[1]: Found device /dev/serial1.
Oct 16 21:19:39 VTLD kernel: [    0.771302] mmc1: queuing unknown CIS tuple 0x80                      (3 bytes)
Oct 16 21:19:39 VTLD kernel: [    0.772860] mmc1: queuing unknown CIS tuple 0x80                      (3 bytes)
Oct 16 21:19:39 VTLD kernel: [    0.775640] mmc1: queuing unknown CIS tuple 0x80                      (7 bytes)
Oct 16 21:19:39 VTLD kernel: [    0.811548] mmc0: sdhost-bcm2835 loaded - DMA en                     abled (>1)
Oct 16 21:19:39 VTLD kernel: [    0.812558] of_cfs_init
Oct 16 21:19:39 VTLD kernel: [    0.812695] of_cfs_init: OK
Oct 16 21:19:39 VTLD kernel: [    0.813197] Waiting for root device PARTUUID=2e6                     f101b-02...
Oct 16 21:19:39 VTLD kernel: [    0.851911] random: fast init done
Oct 16 21:19:39 VTLD kernel: [    0.871692] Indeed it is in host mode hprt0 = 00                     021501
Oct 16 21:19:39 VTLD kernel: [    0.938677] mmc0: host does not support reading                      read-only switch, assuming write-enable
Oct 16 21:19:39 VTLD kernel: [    0.941341] mmc0: new high speed SDHC card at ad                     dress 1234
Oct 16 21:19:39 VTLD kernel: [    0.941838] mmcblk0: mmc0:1234 SA16G 14.4 GiB
Oct 16 21:19:39 VTLD kernel: [    0.943201]  mmcblk0: p1 p2
Oct 16 21:19:39 VTLD kernel: [    0.954531] mmc1: new high speed SDIO card at ad                     dress 0001
Oct 16 21:19:39 VTLD kernel: [    0.966377] EXT4-fs (mmcblk0p2): INFO: recovery                      required on readonly filesystem
Oct 16 21:19:39 VTLD kernel: [    0.966384] EXT4-fs (mmcblk0p2): write access wi                     ll be enabled during recovery
Oct 16 21:19:39 VTLD kernel: [    1.081585] usb 1-1: new high-speed USB device n                     umber 2 using dwc_otg
Oct 16 21:19:39 VTLD kernel: [    1.081727] Indeed it is in host mode hprt0 = 00                     001101
Oct 16 21:19:39 VTLD kernel: [    1.321816] usb 1-1: New USB device found, idVen                     dor=0424, idProduct=9514
Oct 16 21:19:39 VTLD kernel: [    1.321828] usb 1-1: New USB device strings: Mfr                     =0, Product=0, SerialNumber=0
Oct 16 21:19:39 VTLD kernel: [    1.322458] hub 1-1:1.0: USB hub found
Oct 16 21:19:39 VTLD kernel: [    1.322540] hub 1-1:1.0: 5 ports detected
Oct 16 21:19:39 VTLD kernel: [    1.641559] usb 1-1.1: new high-speed USB device                      number 3 using dwc_otg
Oct 16 21:19:39 VTLD kernel: [    1.771791] usb 1-1.1: New USB device found, idV                     endor=0424, idProduct=ec00
Oct 16 21:19:39 VTLD kernel: [    1.771802] usb 1-1.1: New USB device strings: M                     fr=0, Product=0, SerialNumber=0
Oct 16 21:19:39 VTLD kernel: [    1.774315] smsc95xx v1.0.6
Oct 16 21:19:39 VTLD kernel: [    1.864841] smsc95xx 1-1.1:1.0 eth0: register 's                     msc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:f5:d4:d6
Oct 16 21:19:39 VTLD kernel: [    1.961560] usb 1-1.5: new low-speed USB device                      number 4 using dwc_otg
Oct 16 21:19:39 VTLD kernel: [    2.102538] usb 1-1.5: New USB device found, idV                     endor=0eef, idProduct=0001
Oct 16 21:19:39 VTLD kernel: [    2.102549] usb 1-1.5: New USB device strings: M                     fr=1, Product=2, SerialNumber=0
Oct 16 21:19:39 VTLD kernel: [    2.102558] usb 1-1.5: Product: Touch
Oct 16 21:19:39 VTLD kernel: [    2.102566] usb 1-1.5: Manufacturer: eGalax Inc.
Oct 16 21:19:39 VTLD kernel: [    2.128655] input: eGalax Inc. Touch as /devices                     /platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:0EEF:0001.0001/input/in                     put0
Oct 16 21:19:39 VTLD kernel: [    2.128989] input: eGalax Inc. Touch as /devices                     /platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:0EEF:0001.0001/input/in                     put1
Oct 16 21:19:39 VTLD kernel: [    2.129248] hid-generic 0003:0EEF:0001.0001: inp                     ut,hidraw0: USB HID v1.12 Pointer [eGalax Inc. Touch] on usb-3f980000.usb-1.5/in                     put0
Oct 16 21:19:39 VTLD kernel: [   11.291053] EXT4-fs (mmcblk0p2): recovery comple                     te
Oct 16 21:19:39 VTLD kernel: [   11.295542] EXT4-fs (mmcblk0p2): mounted filesys                     tem with ordered data mode. Opts: (null)
Oct 16 21:19:39 VTLD kernel: [   11.295594] VFS: Mounted root (ext4 filesystem)                      readonly on device 179:2.
Oct 16 21:19:39 VTLD kernel: [   11.304049] devtmpfs: mounted
Oct 16 21:19:39 VTLD kernel: [   11.307279] Freeing unused kernel memory: 1024K
Oct 16 21:19:39 VTLD kernel: [   11.817478] NET: Registered protocol family 10
Oct 16 21:19:39 VTLD kernel: [   11.818652] Segment Routing with IPv6
Oct 16 21:19:39 VTLD kernel: [   11.828598] ip_tables: (C) 2000-2006 Netfilter C                     ore Team
Oct 16 21:19:39 VTLD systemd-udevd[270]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD dphys-swapfile[193]: Starting dphys-swapfile swapfile setup                      ...
Oct 16 21:19:39 VTLD systemd-udevd[271]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD raspi-config[191]: Checking if shift key is held down:Error                      opening '/dev/input/event*': No such file or directory
Oct 16 21:19:39 VTLD systemd-udevd[281]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD raspi-config[191]:  No. Switching to ondemand scaling gover                     nor.
Oct 16 21:19:39 VTLD systemd[1]: Started LSB: Switch to ondemand cpu governor (u                     nless shift key is pressed).
Oct 16 21:19:39 VTLD systemd[1]: Starting Configure Bluetooth Modems connected b                     y UART...
Oct 16 21:19:39 VTLD kernel: [   11.860558] random: systemd: uninitialized urand                     om read (16 bytes read)
Oct 16 21:19:39 VTLD kernel: [   11.896369] random: systemd: uninitialized urand                     om read (16 bytes read)
Oct 16 21:19:39 VTLD kernel: [   11.926024] random: systemd-cryptse: uninitializ                     ed urandom read (16 bytes read)
Oct 16 21:19:39 VTLD systemd[1]: Started Login Service.
Oct 16 21:19:39 VTLD kernel: [   12.443439] i2c /dev entries driver
Oct 16 21:19:39 VTLD kernel: [   12.751835] EXT4-fs (mmcblk0p2): re-mounted. Opt                     s: (null)
Oct 16 21:19:39 VTLD kernel: [   14.092108] brcmfmac: F1 signature read @0x18000                     000=0x1541a9a6
Oct 16 21:19:39 VTLD systemd[1]: Started Check for v3d driver.
Oct 16 21:19:39 VTLD kernel: [   14.099463] brcmfmac: brcmf_fw_map_chip_to_name:                      using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
Oct 16 21:19:39 VTLD kernel: [   14.099788] usbcore: registered new interface dr                     iver brcmfmac
Oct 16 21:19:39 VTLD systemd[1]: Started Raise network interfaces.
Oct 16 21:19:39 VTLD kernel: [   14.155629] uart-pl011 3f201000.serial: no DMA p                     latform data
Oct 16 21:19:39 VTLD kernel: [   14.187734] usbcore: registered new interface dr                     iver usbtouchscreen
Oct 16 21:19:39 VTLD systemd[1]: Reached target Network.
Oct 16 21:19:39 VTLD systemd[1]: Starting Permit User Sessions...
Oct 16 21:19:39 VTLD systemd[1]: Reached target Network is Online.
Oct 16 21:19:39 VTLD systemd[1]: Starting /etc/rc.local Compatibility...
Oct 16 21:19:39 VTLD systemd[1]: Starting LSB: Start NTP daemon...
Oct 16 21:19:39 VTLD mtp-probe: checking bus 1, device 4: "/sys/devices/platform                     /soc/3f980000.usb/usb1/1-1/1-1.5"
Oct 16 21:19:39 VTLD systemd[1]: Started VNC Server in Service Mode daemon.
Oct 16 21:19:39 VTLD mtp-probe: bus: 1, device: 4 was not an MTP device
Oct 16 21:19:39 VTLD systemd[326]: vncserver-x11-serviced.service: Failed at ste                     p EXEC spawning /usr/bin/vncserver-x11-serviced: No such file or directory
Oct 16 21:19:39 VTLD mtp-probe: checking bus 1, device 3: "/sys/devices/platform                     /soc/3f980000.usb/usb1/1-1/1-1.1"
Oct 16 21:19:39 VTLD systemd[1]: Starting OpenBSD Secure Shell server...
Oct 16 21:19:39 VTLD systemd[1]: Starting TeamViewer remote control daemon...
Oct 16 21:19:39 VTLD systemd[1]: Started Permit User Sessions.
Oct 16 21:19:39 VTLD systemd-udevd[343]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd[1]: Started /etc/rc.local Compatibility.
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Main process ex                     ited, code=exited, status=203/EXEC
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Unit entered fa                     iled state.
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Failed with res                     ult 'exit-code'.
Oct 16 21:19:39 VTLD systemd-udevd[344]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD mtp-probe: bus: 1, device: 3 was not an MTP device
Oct 16 21:19:39 VTLD systemd-udevd[345]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD dphys-swapfile[193]: want /var/swap=100MByte, checking exis                     ting: keeping it
Oct 16 21:19:39 VTLD systemd[1]: Listening on Load/Save RF Kill Switch Status /d                     ev/rfkill Watch.
Oct 16 21:19:39 VTLD systemd[1]: Starting Hold until boot process finishes up...
Oct 16 21:19:39 VTLD systemd[1]: Starting Light Display Manager...
Oct 16 21:19:39 VTLD systemd[1]: Starting Terminate Plymouth Boot Screen...
Oct 16 21:19:39 VTLD liblogging-stdlog:  [origin software="rsyslogd" swVersion="                     8.24.0" x-pid="241" x-info="http://www.rsyslog.com"] start
Oct 16 21:19:39 VTLD systemd[1]: Started System Logging Service.
Oct 16 21:19:39 VTLD systemd[1]: Received SIGRTMIN+21 from PID 169 (plymouthd).
Oct 16 21:19:39 VTLD systemd-udevd[362]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd[1]: Started Hold until boot process finishes up.
Oct 16 21:19:39 VTLD systemd-udevd[363]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd-udevd[364]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd[1]: Started Terminate Plymouth Boot Screen.
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Service hold-of                     f time over, scheduling restart.
Oct 16 21:19:39 VTLD systemd[1]: Stopped VNC Server in Service Mode daemon.
Oct 16 21:19:39 VTLD systemd[369]: vncserver-x11-serviced.service: Failed at ste                     p EXEC spawning /usr/bin/vncserver-x11-serviced: No such file or directory
Oct 16 21:19:39 VTLD systemd[1]: Started VNC Server in Service Mode daemon.
Oct 16 21:19:39 VTLD systemd[1]: Started Getty on tty1.
Oct 16 21:19:39 VTLD systemd[1]: Reached target Login Prompts.
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Main process ex                     ited, code=exited, status=203/EXEC
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Unit entered fa                     iled state.
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Failed with res                     ult 'exit-code'.
Oct 16 21:19:39 VTLD kernel: [   14.272072] Adding 102396k swap on /var/swap.  P                     riority:-2 extents:1 across:102396k SSFS
Oct 16 21:19:39 VTLD systemd-udevd[377]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD dphys-swapfile[193]: done.
Oct 16 21:19:39 VTLD systemd[1]: Started LSB: Autogenerate and use a swap file.
Oct 16 21:19:39 VTLD systemd-udevd[385]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd-udevd[386]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd-udevd[387]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD kernel: [   14.377201] random: crng init done
Oct 16 21:19:39 VTLD kernel: [   14.377211] random: 7 urandom warning(s) missed                      due to ratelimiting
Oct 16 21:19:39 VTLD kernel: [   14.387143] brcmfmac: brcmf_c_preinit_dcmds: Fir                     mware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 0                     1-e58d219f
Oct 16 21:19:39 VTLD kernel: [   14.387789] brcmfmac: brcmf_c_preinit_dcmds: CLM                      version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation:                      2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3                      Creation: 2017-10-23 03:47:14
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Service hold-of                     f time over, scheduling restart.
Oct 16 21:19:39 VTLD systemd[1]: Stopped VNC Server in Service Mode daemon.
Oct 16 21:19:39 VTLD systemd-udevd[388]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd[1]: Started VNC Server in Service Mode daemon.
Oct 16 21:19:39 VTLD systemd[389]: vncserver-x11-serviced.service: Failed at ste                     p EXEC spawning /usr/bin/vncserver-x11-serviced: No such file or directory
Oct 16 21:19:39 VTLD systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Main process ex                     ited, code=exited, status=203/EXEC
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Unit entered fa                     iled state.
Oct 16 21:19:39 VTLD systemd[1]: vncserver-x11-serviced.service: Failed with res                     ult 'exit-code'.
Oct 16 21:19:39 VTLD systemd-udevd[394]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd-udevd[397]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:39 VTLD systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 16 21:19:39 VTLD systemd-udevd[173]: Process '/usr/sbin/th-cmd --socket /var                     /run/thd.socket --passfd --udev' failed with exit code 1.
Oct 16 21:19:39 VTLD systemd-udevd[170]: Process '/usr/sbin/th-cmd --socket /var                     /run/thd.socket --passfd --udev' failed with exit code 1.
Oct 16 21:19:39 VTLD systemd-udevd[403]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:40 VTLD systemd-udevd[404]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:40 VTLD systemd-udevd[176]: Process '/usr/sbin/th-cmd --socket /var                     /run/thd.socket --passfd --udev' failed with exit code 1.
Oct 16 21:19:40 VTLD ntpd[383]: ntpd [email protected] Sat Mar 10 18:03:33 UTC 2                     018 (1): Starting
Oct 16 21:19:40 VTLD ntpd[383]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pi                     d -g -u 111:115
Oct 16 21:19:40 VTLD ntp[325]: Starting NTP server: ntpd.
Oct 16 21:19:40 VTLD systemd[1]: Started LSB: Start NTP daemon.
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Service hold-of                     f time over, scheduling restart.
Oct 16 21:19:40 VTLD systemd[1]: Stopped VNC Server in Service Mode daemon.
Oct 16 21:19:40 VTLD systemd[1]: Started VNC Server in Service Mode daemon.
Oct 16 21:19:40 VTLD systemd[407]: vncserver-x11-serviced.service: Failed at ste                     p EXEC spawning /usr/bin/vncserver-x11-serviced: No such file or directory
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Main process ex                     ited, code=exited, status=203/EXEC
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Unit entered fa                     iled state.
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Failed with res                     ult 'exit-code'.
Oct 16 21:19:40 VTLD dhcpcd[223]: eth0: waiting for carrier
Oct 16 21:19:40 VTLD kernel: [   14.783654] smsc95xx 1-1.1:1.0 eth0: hardware is                     n't capable of remote wakeup
Oct 16 21:19:40 VTLD ntpd[406]: proto: precision = 0.729 usec (-20)
Oct 16 21:19:40 VTLD ntpd[406]: Listen and drop on 0 v6wildcard [::]:123
Oct 16 21:19:40 VTLD ntpd[406]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Oct 16 21:19:40 VTLD ntpd[406]: Listen normally on 2 lo 127.0.0.1:123
Oct 16 21:19:40 VTLD ntpd[406]: Listen normally on 3 lo [::1]:123
Oct 16 21:19:40 VTLD ntpd[406]: Listening on routing socket on fd #20 for interf                     ace updates
Oct 16 21:19:40 VTLD systemd-udevd[422]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:40 VTLD systemd-udevd[423]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:40 VTLD dhcpcd-run-hooks[421]: wlan0: starting wpa_supplicant
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Service hold-of                     f time over, scheduling restart.
Oct 16 21:19:40 VTLD systemd[1]: Stopped VNC Server in Service Mode daemon.
Oct 16 21:19:40 VTLD systemd[1]: Started VNC Server in Service Mode daemon.
Oct 16 21:19:40 VTLD systemd[425]: vncserver-x11-serviced.service: Failed at ste                     p EXEC spawning /usr/bin/vncserver-x11-serviced: No such file or directory
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Main process ex                     ited, code=exited, status=203/EXEC
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Unit entered fa                     iled state.
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Failed with res                     ult 'exit-code'.
Oct 16 21:19:40 VTLD systemd-udevd[140]: Process '/usr/sbin/th-cmd --socket /var                     /run/thd.socket --passfd --udev' failed with exit code 1.
Oct 16 21:19:40 VTLD systemd-udevd[141]: Process '/usr/sbin/th-cmd --socket /var                     /run/thd.socket --passfd --udev' failed with exit code 1.
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Service hold-of                     f time over, scheduling restart.
Oct 16 21:19:40 VTLD systemd[1]: Stopped VNC Server in Service Mode daemon.
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Start request r                     epeated too quickly.
Oct 16 21:19:40 VTLD systemd[1]: Failed to start VNC Server in Service Mode daem                     on.
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Unit entered fa                     iled state.
Oct 16 21:19:40 VTLD systemd[1]: vncserver-x11-serviced.service: Failed with res                     ult 'exit-code'.
Oct 16 21:19:40 VTLD systemd[1]: Started OpenBSD Secure Shell server.
Oct 16 21:19:40 VTLD systemd-udevd[439]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:40 VTLD systemd[1]: Started TeamViewer remote control daemon.
Oct 16 21:19:41 VTLD dhcpcd[223]: wlan0: if_up: Operation not possible due to RF                     -kill
Oct 16 21:19:41 VTLD dhcpcd[223]: wlan0: waiting for carrier
Oct 16 21:19:41 VTLD dhcpcd[223]: eth0: carrier acquired
Oct 16 21:19:41 VTLD dhcpcd[223]: DUID 00:01:00:01:23:7d:9b:35:b8:27:eb:7e:45:7b
Oct 16 21:19:41 VTLD dhcpcd[223]: eth0: IAID eb:f5:d4:d6
Oct 16 21:19:41 VTLD dhcpcd[223]: eth0: adding address fe80::6e34:511e:1de7:8b24
Oct 16 21:19:41 VTLD dhcpcd[223]: eth0: probing address 192.168.1.11/24
Oct 16 21:19:41 VTLD lightdm[376]: Error getting user list from org.freedesktop.                     Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fr                     eedesktop.Accounts was not provided by any .service files
Oct 16 21:19:41 VTLD systemd[1]: Started Light Display Manager.
Oct 16 21:19:41 VTLD dhcpcd[223]: eth0: soliciting an IPv6 router
Oct 16 21:19:41 VTLD systemd-udevd[475]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:41 VTLD dhcpcd[223]: eth0: carrier lost
Oct 16 21:19:41 VTLD dhcpcd[223]: eth0: deleting address fe80::6e34:511e:1de7:8b                     24
Oct 16 21:19:41 VTLD dhcpcd[223]: eth0: carrier acquired
Oct 16 21:19:41 VTLD kernel: [   16.562694] smsc95xx 1-1.1:1.0 eth0: link up, 10                     0Mbps, full-duplex, lpa 0x4DE1
Oct 16 21:19:42 VTLD dhcpcd[223]: eth0: IAID eb:f5:d4:d6
Oct 16 21:19:42 VTLD dhcpcd[223]: eth0: adding address fe80::6e34:511e:1de7:8b24
Oct 16 21:19:42 VTLD dhcpcd[223]: eth0: probing address 192.168.1.11/24
Oct 16 21:19:42 VTLD ntpd[406]: error resolving pool 0.debian.pool.ntp.org: Temp                     orary failure in name resolution (-3)
Oct 16 21:19:42 VTLD ntpd[406]: error resolving pool 1.debian.pool.ntp.org: Temp                     orary failure in name resolution (-3)
Oct 16 21:19:42 VTLD dhcpcd[223]: eth0: soliciting an IPv6 router
Oct 16 21:19:43 VTLD ntpd[406]: bind(23) AF_INET6 fe80::6e34:511e:1de7:8b24%2#12                     3 flags 0x11 failed: Cannot assign requested address
Oct 16 21:19:43 VTLD ntpd[406]: unable to create socket on eth0 (4) for fe80::6e                     34:511e:1de7:8b24%2#123
Oct 16 21:19:43 VTLD ntpd[406]: failed to init interface for address fe80::6e34:                     511e:1de7:8b24%2
Oct 16 21:19:43 VTLD dhcpcd[223]: eth0: Router Advertisement from fe80::a63e:51f                     f:fe67:2f56
Oct 16 21:19:43 VTLD dhcpcd[223]: eth0: adding address 2a01:cb05:844b:2000:3e80:                     996e:cc64:e4fa/64
Oct 16 21:19:43 VTLD dhcpcd[223]: eth0: adding route to 2a01:cb05:844b:2000::/64
Oct 16 21:19:43 VTLD dhcpcd[223]: eth0: adding default route via fe80::a63e:51ff                     :fe67:2f56
Oct 16 21:19:43 VTLD dhcpcd[223]: eth0: requesting DHCPv6 information
Oct 16 21:19:43 VTLD lightdm[513]: Error getting user list from org.freedesktop.                     Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fr                     eedesktop.Accounts was not provided by any .service files
Oct 16 21:19:43 VTLD systemd[1]: Created slice User Slice of pi.
Oct 16 21:19:43 VTLD systemd[1]: Starting User Manager for UID 1000...
Oct 16 21:19:43 VTLD systemd[1]: Started Session c1 of user pi.
Oct 16 21:19:44 VTLD systemd[548]: Listening on GnuPG cryptographic agent and pa                     ssphrase cache (restricted).
Oct 16 21:19:44 VTLD systemd[548]: Listening on GnuPG cryptographic agent and pa                     ssphrase cache.
Oct 16 21:19:44 VTLD systemd[548]: Reached target Paths.
Oct 16 21:19:44 VTLD systemd[548]: Listening on GnuPG cryptographic agent (acces                     s for web browsers).
Oct 16 21:19:44 VTLD systemd[548]: Starting D-Bus User Message Bus Socket.
Oct 16 21:19:44 VTLD systemd[548]: Listening on GnuPG cryptographic agent (ssh-a                     gent emulation).
Oct 16 21:19:44 VTLD systemd[548]: Reached target Timers.
Oct 16 21:19:44 VTLD systemd[548]: Listening on D-Bus User Message Bus Socket.
Oct 16 21:19:44 VTLD systemd[548]: Reached target Sockets.
Oct 16 21:19:44 VTLD systemd[548]: Reached target Basic System.
Oct 16 21:19:44 VTLD systemd[548]: Reached target Default.
Oct 16 21:19:44 VTLD systemd[548]: Startup finished in 322ms.
Oct 16 21:19:44 VTLD systemd[1]: Started User Manager for UID 1000.
Oct 16 21:19:44 VTLD lightdm[376]: Error opening audit socket: Protocol not supp                     orted
Oct 16 21:19:44 VTLD kernel: [   19.256390] Bluetooth: Core ver 2.22
Oct 16 21:19:44 VTLD kernel: [   19.256559] NET: Registered protocol family 31
Oct 16 21:19:44 VTLD kernel: [   19.256575] Bluetooth: HCI device and connection                      manager initialized
Oct 16 21:19:44 VTLD kernel: [   19.258303] Bluetooth: HCI socket layer initiali                     zed
Oct 16 21:19:44 VTLD kernel: [   19.258332] Bluetooth: L2CAP socket layer initia                     lized
Oct 16 21:19:44 VTLD kernel: [   19.258398] Bluetooth: SCO socket layer initiali                     zed
Oct 16 21:19:44 VTLD kernel: [   19.282382] Bluetooth: HCI UART driver ver 2.3
Oct 16 21:19:44 VTLD kernel: [   19.282419] Bluetooth: HCI UART protocol H4 regi                     stered
Oct 16 21:19:44 VTLD kernel: [   19.282426] Bluetooth: HCI UART protocol Three-w                     ire (H5) registered
Oct 16 21:19:44 VTLD kernel: [   19.282795] Bluetooth: HCI UART protocol Broadco                     m registered
Oct 16 21:19:44 VTLD btuart[292]: bcm43xx_init
Oct 16 21:19:44 VTLD btuart[292]: Flash firmware /lib/firmware/brcm/BCM43430A1.h                     cd
Oct 16 21:19:44 VTLD btuart[292]: Set BDADDR UART: b8:27:eb:5f:7e:7c
Oct 16 21:19:44 VTLD btuart[292]: Set Controller UART speed to 921600 bit/s
Oct 16 21:19:44 VTLD btuart[292]: Device setup complete
Oct 16 21:19:44 VTLD systemd[1]: Started Configure Bluetooth Modems connected by                      UART.
Oct 16 21:19:44 VTLD systemd[1]: Reached target Multi-User System.
Oct 16 21:19:44 VTLD systemd[1]: Reached target Graphical Interface.
Oct 16 21:19:44 VTLD systemd[1]: Starting Update UTMP about System Runlevel Chan                     ges...
Oct 16 21:19:44 VTLD systemd[548]: Started D-Bus User Message Bus.
Oct 16 21:19:45 VTLD systemd[1]: Created slice system-bthelper.slice.
Oct 16 21:19:45 VTLD systemd[1]: Starting Bluetooth service...
Oct 16 21:19:45 VTLD dbus-daemon[653]: Successfully activated service 'org.freed                     esktop.systemd1'
Oct 16 21:19:45 VTLD systemd[1]: Started Update UTMP about System Runlevel Chang                     es.
Oct 16 21:19:45 VTLD bluetoothd[654]: Bluetooth daemon 5.43
Oct 16 21:19:45 VTLD systemd[1]: Started Bluetooth service.
Oct 16 21:19:45 VTLD systemd[1]: Reached target Bluetooth.
Oct 16 21:19:45 VTLD systemd[1]: Started Raspberry Pi bluetooth helper.
Oct 16 21:19:45 VTLD systemd[1]: Started BluezALSA proxy.
Oct 16 21:19:45 VTLD systemd[1]: Startup finished in 11.668s (kernel) + 8.061s (                     userspace) = 19.729s.
Oct 16 21:19:45 VTLD bluetoothd[654]: Starting SDP server
Oct 16 21:19:45 VTLD bthelper[662]: Can't init device hci0: Operation not possib                     le due to RF-kill (132)
Oct 16 21:19:45 VTLD systemd[1]: [email protected]: Main process exited, cod                     e=exited, status=1/FAILURE
Oct 16 21:19:45 VTLD systemd[1]: [email protected]: Unit entered failed stat                     e.
Oct 16 21:19:45 VTLD systemd[1]: [email protected]: Failed with result 'exit                     -code'.
Oct 16 21:19:45 VTLD dbus[195]: [system] Activating via systemd: service name='o                     rg.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Oct 16 21:19:45 VTLD kernel: [   19.812570] Bluetooth: BNEP (Ethernet Emulation)                      ver 1.3
Oct 16 21:19:45 VTLD kernel: [   19.812579] Bluetooth: BNEP filters: protocol mu                     lticast
Oct 16 21:19:45 VTLD kernel: [   19.812594] Bluetooth: BNEP socket layer initial                     ized
Oct 16 21:19:45 VTLD bluetoothd[654]: Bluetooth management interface 1.14 initia                     lized
Oct 16 21:19:45 VTLD bluetoothd[654]: Failed to obtain handles for "Service Chan                     ged" characteristic
Oct 16 21:19:45 VTLD systemd[1]: Starting Hostname Service...
Oct 16 21:19:45 VTLD bluetoothd[654]: Sap driver initialization failed.
Oct 16 21:19:45 VTLD bluetoothd[654]: sap-server: Operation not permitted (1)
Oct 16 21:19:45 VTLD bluetoothd[654]: Endpoint registered: sender=:1.11 path=/A2                     DP/SBC/Source/1
Oct 16 21:19:45 VTLD bluetoothd[654]: Failed to set mode: Blocked through rfkill                      (0x12)
Oct 16 21:19:45 VTLD systemd[1]: Started Session c2 of user pi.
Oct 16 21:19:45 VTLD kernel: [   19.870264] Bluetooth: RFCOMM TTY layer initiali                     zed
Oct 16 21:19:45 VTLD kernel: [   19.870294] Bluetooth: RFCOMM socket layer initi                     alized
Oct 16 21:19:45 VTLD kernel: [   19.870316] Bluetooth: RFCOMM ver 1.11
Oct 16 21:19:45 VTLD ntpd[406]: Soliciting pool server 2a00:1080:80d:201::d:1
Oct 16 21:19:45 VTLD ntpd[406]: Soliciting pool server 82.64.45.50
Oct 16 21:19:45 VTLD dbus[195]: [system] Successfully activated service 'org.fre                     edesktop.hostname1'
Oct 16 21:19:45 VTLD systemd[1]: Started Hostname Service.
Oct 16 21:19:46 VTLD ntpd[406]: Listen normally on 5 eth0 [2a01:cb05:844b:2000:3                     e80:996e:cc64:e4fa]:123
Oct 16 21:19:46 VTLD ntpd[406]: Listen normally on 6 eth0 [fe80::6e34:511e:1de7:                     8b24%2]:123
Oct 16 21:19:47 VTLD dhcpcd[223]: eth0: using static address 192.168.1.11/24
Oct 16 21:19:47 VTLD dhcpcd[223]: eth0: adding route to 192.168.1.0/24
Oct 16 21:19:47 VTLD dhcpcd[223]: eth0: adding default route via 192.168.1.1
Oct 16 21:19:49 VTLD ntpd[406]: Listen normally on 7 eth0 192.168.1.11:123
Oct 16 21:19:55 VTLD dbus-daemon[653]: Activating via systemd: service name='org                     .gtk.vfs.Daemon' unit='gvfs-daemon.service'
Oct 16 21:19:55 VTLD systemd[548]: Starting Virtual filesystem service...
Oct 16 21:19:55 VTLD dbus-daemon[653]: Successfully activated service 'org.gtk.v                     fs.Daemon'
Oct 16 21:19:55 VTLD systemd[548]: Started Virtual filesystem service.
Oct 16 21:19:56 VTLD kernel: [   30.589265] fuse init (API version 7.26)
Oct 16 21:19:56 VTLD systemd-udevd[820]: open /dev/null failed: No such file or                      directory
Oct 16 21:19:56 VTLD systemd[1]: Mounting FUSE Control File System...
Oct 16 21:19:56 VTLD systemd[1]: Mounted FUSE Control File System.
Oct 16 21:19:56 VTLD dbus[195]: [system] Activating via systemd: service name='o                     rg.freedesktop.PolicyKit1' unit='polkit.service'
Oct 16 21:19:56 VTLD systemd[1]: Starting Authorization Manager...
Oct 16 21:19:56 VTLD polkitd[855]: started daemon version 0.105 using authority                      implementation `local' version `0.105'
Oct 16 21:19:56 VTLD dbus[195]: [system] Successfully activated service 'org.fre                     edesktop.PolicyKit1'
Oct 16 21:19:56 VTLD systemd[1]: Started Authorization Manager.
Oct 16 21:19:57 VTLD dbus-daemon[653]: Activating via systemd: service name='org                     .gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service'
Oct 16 21:19:57 VTLD systemd[548]: Starting Virtual filesystem service - disk de                     vice monitor...
Oct 16 21:19:57 VTLD dbus[195]: [system] Activating via systemd: service name='o                     rg.freedesktop.UDisks2' unit='udisks2.service'
Oct 16 21:19:57 VTLD systemd[1]: Starting Disk Manager...
Oct 16 21:19:59 VTLD udisksd[887]: udisks daemon version 2.1.8 starting
Oct 16 21:19:59 VTLD dbus[195]: [system] Successfully activated service 'org.fre                     edesktop.UDisks2'
Oct 16 21:19:59 VTLD udisksd[887]: Acquired the name org.freedesktop.UDisks2 on                      the system message bus
Oct 16 21:19:59 VTLD systemd[1]: Started Disk Manager.
Oct 16 21:19:59 VTLD dbus-daemon[653]: Successfully activated service 'org.gtk.v                     fs.UDisks2VolumeMonitor'
Oct 16 21:19:59 VTLD systemd[548]: Started Virtual filesystem service - disk dev                     ice monitor.
Oct 16 21:19:59 VTLD dbus-daemon[653]: Activating via systemd: service name='org                     .gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service'
Oct 16 21:19:59 VTLD systemd[548]: Starting Virtual filesystem service - Apple F                     ile Conduit monitor...
Oct 16 21:19:59 VTLD gvfs-afc-volume-monitor[894]: Volume monitor alive
Oct 16 21:19:59 VTLD dbus-daemon[653]: Successfully activated service 'org.gtk.v                     fs.AfcVolumeMonitor'
Oct 16 21:19:59 VTLD systemd[548]: Started Virtual filesystem service - Apple Fi                     le Conduit monitor.
Oct 16 21:19:59 VTLD dbus-daemon[653]: Activating via systemd: service name='org                     .gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service'
Oct 16 21:19:59 VTLD systemd[548]: Starting Virtual filesystem service - Media T                     ransfer Protocol monitor...
Oct 16 21:19:59 VTLD dbus-daemon[653]: Successfully activated service 'org.gtk.v                     fs.MTPVolumeMonitor'
Oct 16 21:19:59 VTLD systemd[548]: Started Virtual filesystem service - Media Tr                     ansfer Protocol monitor.
Oct 16 21:19:59 VTLD dbus-daemon[653]: Activating via systemd: service name='org                     .gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service'
Oct 16 21:19:59 VTLD systemd[548]: Starting Virtual filesystem service - digital                      camera monitor...
Oct 16 21:19:59 VTLD dbus-daemon[653]: Successfully activated service 'org.gtk.v                     fs.GPhoto2VolumeMonitor'
Oct 16 21:19:59 VTLD systemd[548]: Started Virtual filesystem service - digital                      camera monitor.
Oct 16 21:19:59 VTLD dbus-daemon[653]: Activating via systemd: service name='org                     .gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service'
Oct 16 21:19:59 VTLD systemd[548]: Starting Virtual filesystem service - GNOME O                     nline Accounts monitor...
Oct 16 21:19:59 VTLD dbus-daemon[653]: Successfully activated service 'org.gtk.v                     fs.GoaVolumeMonitor'
Oct 16 21:19:59 VTLD systemd[548]: Started Virtual filesystem service - GNOME On                     line Accounts monitor.
Oct 16 21:20:01 VTLD dbus-daemon[653]: Activating service name='com.teamviewer.T                     eamViewer.Desktop'
Oct 16 21:20:02 VTLD dbus-daemon[653]: Successfully activated service 'com.teamv                     iewer.TeamViewer.Desktop'
Oct 16 21:20:47 VTLD ntpd[406]: Soliciting pool server 151.80.211.8
Oct 16 21:20:47 VTLD ntpd[406]: Soliciting pool server 194.57.169.1
Oct 16 21:20:48 VTLD ntpd[406]: Soliciting pool server 51.75.17.219
Oct 16 21:20:49 VTLD ntpd[406]: Soliciting pool server 2001:41d0:2:b7a2:0:162:b:                     123
Oct 16 21:20:49 VTLD ntpd[406]: Soliciting pool server 80.74.64.1
Oct 16 21:20:50 VTLD ntpd[406]: Soliciting pool server 91.121.154.174
Oct 16 21:20:51 VTLD ntpd[406]: Soliciting pool server 149.202.2.105
Oct 16 21:20:52 VTLD ntpd[406]: Soliciting pool server 37.187.5.167
Oct 16 21:20:53 VTLD ntpd[406]: Soliciting pool server 91.121.88.161
Oct 16 21:20:54 VTLD ntpd[406]: Soliciting pool server 82.64.45.50
Oct 17 21:28:17 VTLD systemd[548]: Time has been changed
Oct 17 21:28:17 VTLD systemd[1]: Time has been changed
Oct 17 21:28:17 VTLD systemd[1]: apt-daily-upgrade.timer: Adding 23min 52.102400                     s random time.
Oct 17 21:28:17 VTLD systemd[1]: apt-daily.timer: Adding 11h 2min 48.813384s ran                     dom time.
Oct 17 21:28:17 VTLD systemd[1]: Starting Daily apt download activities...
Oct 17 21:28:20 VTLD systemd[1]: Started Daily apt download activities.
Oct 17 21:28:20 VTLD systemd[1]: apt-daily.timer: Adding 1h 7min 35.695676s rand                     om time.
Oct 17 21:28:20 VTLD systemd[1]: apt-daily.timer: Adding 9h 47min 32.181630s ran                     dom time.
Oct 17 21:28:20 VTLD systemd[1]: Starting Daily apt upgrade and clean activities                     ...
Oct 17 21:28:22 VTLD systemd[1]: Started Daily apt upgrade and clean activities.
Oct 17 21:28:22 VTLD systemd[1]: apt-daily-upgrade.timer: Adding 52min 7.548045s                      random time.
Oct 17 21:28:22 VTLD systemd[1]: apt-daily-upgrade.timer: Adding 55min 52.493997                     s random time.
Oct 17 21:37:27 VTLD ntpd[406]: 149.202.2.105 local addr 192.168.1.11 -> <null>
Oct 17 21:40:06 VTLD ntpd[406]: 194.57.169.1 local addr 192.168.1.11 -> <null>
Oct 17 21:42:27 VTLD systemd[1]: Starting Cleanup of Temporary Directories...
Oct 17 21:42:27 VTLD systemd[1]: Started Cleanup of Temporary Directories.
Oct 17 22:17:01 VTLD CRON[2691]: (root) CMD (   cd / && run-parts --report /etc/                     cron.hourly)
Last edited by Cougar133 on Thu Oct 17, 2019 9:06 pm, edited 1 time in total.

epoch1970
Posts: 3901
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 9:04 pm

Si tu pouvais éditer ton message mettre ça entre balises "code" comme j'ai rajouté à mon propre message, ça serait plus sympa à lire.

Je suis chagriné par ceci: "open /dev/null failed"
Quel est l'OS qui est installé ?
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 9:09 pm

Raspbian GNU/Linux 9.8 (stretch)

epoch1970
Posts: 3901
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 9:17 pm

Ok. J'utilise très peu l'environnement graphique linux et quasi jamais sur Pi.
Je sais que systemd a sa manière de faire au démarrage, mais voir des messages où '/dev/null' (le périphérique 'trou noir', rien de ce qu'on y envoie n'en ressort, ultra basique et primitif dans l'OS) n'est pas disponible, je trouve ça inquiétant.

Est-ce que le système de fichiers est en bon état ? Des mises à jour difficiles ou évènements du même style ?
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 9:23 pm

Alors j'explique un peu l'utilisation de mon pi et de son écran ,

c'est censé devenir un écran tactile avec un programme pour un simulateur de vol .

j'ai galéré ( mais vraiment beaucoup ) a installer les drivers pour que le tactile fonctionne , du coup je n'ai plus fait aucune MAJ ni upgrade de peur de perdre le tacile et sa calibration

ce system d[1] freeze execution etc est apparu du jour au lendemain , la carte SD est neuve , j'ai eu beau cloner sur une autre , même problème .

sinon , a part ça , une fois lancé , il tourne nickel , et j'ai installé teamviewer dessus pour pouvoir y accéder plus facilement

epoch1970
Posts: 3901
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 9:39 pm

Bon. D'après el goog, systemd dit "freeze execution" quand it perd les pédales et se plante.
Si le message arrive uniquement à l'arrêt du système, ça n'est peut être pas si grave...

Je voudrais pas dire de bêtises et je n'ai pas de Raspbian sous la main. Mais j'aurais bien envie d'essayer de soigner ce /dev/null.
Dans le terminal, que dit "which MAKEDEV"?
S'il existe, lire "man MAKEDEV", et envisager de passer à l'action:

Code: Select all

cd /dev
sudo MAKEDEV -v null
Sinon à la dure avec "mknod": https://unix.stackexchange.com/question ... e-dev-null

Tout ça est assez étrange et je me sens loin de ma base. Je recommande un backup complet avant de passer à l'action.
Je préfèrerais qu'un autre contributeur intervienne...
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 9:42 pm

which MAKEDEV
donne :

/sbin/MAKEDEV

et le man MAKEDEV donne ça

Code: Select all

MAKEDEV(8)                              Make Linux Devices                              MAKEDEV(8)

NAME
       MAKEDEV - create devices

SYNOPSIS
       cd /dev; ./MAKEDEV [ -n ] [ -v ] [ update ]
       cd /dev; ./MAKEDEV [ -n ] [ -v ] [ generic ] [ local ] [ group-keyword ... device ... ]
       cd /dev; ./MAKEDEV [ -n ] [ -v ] [ -d ] device ...

DESCRIPTION
       MAKEDEV  is a script that will create the devices in /dev used to interface with drivers in
       the kernel.

       Note that programs giving the error ``ENOENT: No such file or  directory''  normally  means
       that the device file is missing, whereas ``ENODEV: No such device'' normally means the ker‐
       nel does not have the driver configured or loaded.

OPTIONS
       -n     Do not actually update the devices, just print the actions that would be performed.

       -d     Delete the devices.  The main use for this flag is by MAKEDEV itself.

       -v     Be verbose.  Print out the actions as they are performed.  This is the  same  output
              as produced by -n.

CUSTOMISATION
       Since  there  is  currently  no standardisation in what names are used for system users and
       groups, it is possible that you may need to modify MAKEDEV to reflect your site's settings.
       Near the top of the file is a mapping from device type to user, group and permissions (e.g.
       all CD-ROM devices are set from the $cdrom variable).  If you wish to change the  defaults,
       this is the section to edit.

GENERAL OPTIONS
       update This  only  works  on kernels which have /proc/interrupts (introduced during 1.1.x).
              This file is scanned to see what devices are currently configured into  the  kernel,
              and  this  is compared with the previous settings stored in the file called DEVICES.
              Devices which are new since then or have a different major number are  created,  and
              those which are no longer configured are deleted.
j'ai une sauvegarde sur une autre micro SD ;)

epoch1970
Posts: 3901
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 10:06 pm

La page de manuel c'était pour toi... J'ai les miennes ;)

Bon si tu aimes l'aventure :

Code: Select all

cd /dev
sudo MAKEDEV -v std
Après ça, rebouter et voir si la machine s'arrête plus proprement désormais.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Thu Oct 17, 2019 10:26 pm

impossible : il me dit


/run/udev or .udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation.

Cougar133
Posts: 14
Joined: Sat Feb 16, 2019 1:04 am

Re: message d'erreur arret/reboot

Mon Oct 21, 2019 10:37 am

d'autres pistes ?

iznobe
Posts: 289
Joined: Sun Feb 05, 2017 4:14 pm
Location: Avignon , FRANCE

Re: message d'erreur arret/reboot

Thu Oct 31, 2019 10:50 am

Salut , ca ne va pas forcement vous plaire , mais je vois une seule solution " propre " :

reprendre depuis le debut , installer raspbian stretch proprement , faire la config de base raspi-config en commencant par expand file system , mise a jour complete , puis re-installer les pilotes de votre ecran .

verifier que tout va bien dans les cas les plus divers , et finir par une sauvegarde de l ' image .

Souvent quand on a du mal a faire un truc , on a tendance a faire des " mauvaises manip " a cause du stress ou de la fatigue ou par megarde .

quand ca se produit , il n ' y a pas 50 solutions , car il est quasi impossible de savoir quelle erreur ou commande a mal ete faite .

Dans la pratique , vu que la partie qui pose probleme est l ' installation du pilote de l' ecran , je vous conseille de faire tout bien comme il faut au sein des etapes de base de l' installation a proprement parler du systeme d' exploitation et avant de passer a l ' instal des drivers de l ' ecran faite une image de sauvegarde de votre carte afin de ne pas vous retapez tout depuis le depart ;)
Donnez des noms explicite a vos sauvegardes , groupees dans un meme repertoire : sauvegarde/raspberry/image.stretch.pi.mise.a.jour.img par exemple puis quand le pilote est correctement installé creer une nouvelle image avec un nom du style image.stretch.mise.a.jour.pilote.ecran.installe.img

en cas de probleme futur ca aide et fait gagner du temps .

Return to “Français”