User avatar
HawaiianPi
Posts: 4734
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: No Wifi connection to Pi Zero W after Raspbian update

Tue Feb 13, 2018 5:35 pm

JacobRask wrote:
Tue Feb 13, 2018 11:19 am
As I announced in my earlier post ('Thu Feb 08, 2018 4:14 pm') I'm suffering from the same issue regarding lack of WiFi-connection to/from my rPi-ZW.
If you don't have wireless at all, even with a fresh image, then it's not the same problem as the OP and you should start your own thread. The OP's Pi0W has WiFi with a newly imaged SD card, but loses it after updating/upgrading the OS.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

hippy
Posts: 6079
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: No Wifi connection to Pi Zero W after Raspbian update

Tue Feb 13, 2018 6:13 pm

The two syslog files differ in their order and content too much for me to figure out anything meaningful so far.

There are things like RF Kill Switch which come before dhcpcd in Nov which works, after in Feb which doesn't, a whole lot more fsck checking in Feb. I don't know enough about Linux or what that even means to tell if important or not. It's going to take someone who does to go through it and see if they can see what's causing the "No valid interfaces" issue.

What about starting with the Nov release, excluding / holding back the firmware updates, updating everything else. That should clear up whether it's a result of the firmware update or something else. I don't believe it is the firmware update itself.

Or just update the firmware, nothing else.

If worse comes to the worse, perhaps update an item or two at a time until it stops working.

Maybe updating some things then updating the rest will cause a re-ordering of behaviour which lets it work.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 6031
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: No Wifi connection to Pi Zero W after Raspbian update

Tue Feb 13, 2018 6:47 pm

If I could reproduce the issue, I would start by installing updates one by one and see what breaks it.

Edit: Also, did restarting dhcpcd after booting kick it into life?

hippy
Posts: 6079
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: No Wifi connection to Pi Zero W after Raspbian update

Tue Feb 13, 2018 7:00 pm

Not sure if this helps any. Perhaps the most obvious thing is that there's no starting or started udev kernel Device Manager in Feb, that comes well afterwards.

What was done in the Nov syslog before dhcpcd starts which wasn't done before dhcpcd starts in the Feb syslog

Code: Select all

Nov systemd[]: Starting udev Kernel Device Manager...
Nov systemd-udevd[]: Network interface NamePolicy= disabled on kernel command line, ignoring.
Nov systemd[]: Started udev Kernel Device Manager.
Nov systemd[]: Started Set the console keyboard layout.
Nov systemd[]: Received SIGRTMIN+20 from PID 149 (plymouthd).
Nov systemd-fsck[]: /dev/mmcblk0p1: 146 files, 42656/83705 clusters
Nov systemd[]: Starting Commit a transient machine-id on disk...
Nov systemd[]: Started Commit a transient machine-id on disk.
Nov systemd[]: apt-daily.timer: Adding 9h 41min 39.545783s random time.
Nov systemd[]: apt-daily-upgrade.timer: Adding 40min 52.889776s random time.
Nov systemd[]: Starting LSB: Resize the root filesystem to fill partition...
Nov systemd[]: Starting Regenerate SSH host keys...
Nov systemd[]: Starting Copy user wpa_supplicant.conf...
Nov dd[]: 1+0 records in
Nov dd[]: 1+0 records out
Nov dd[]: 4096 bytes (4.1 kB, 4.0 KiB) copied, 0.402791 s, 10.2 kB/s
Nov dbus[]: [] Successfully activated service 'org.freedesktop.systemd1'
Nov systemd[]: Started Check for v3d driver.
Nov kernel: [ ] brcmfmac: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
Nov kernel: [ ] 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.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47
Nov kernel: [ ] uart-pl011 20201000.serial: no DMA platform data
Nov systemd[]: Started Copy user wpa_supplicant.conf.
Nov raspi-config[]: Checking if shift key is held down:Error opening '/dev/input/event*': No such file or directory
Nov dphys-swapfile[]: Starting dphys-swapfile swapfile setup ...
Nov raspi-config[]: No. Switching to ondemand scaling governor.
Nov resize2fs_once[]: Starting resize2fs_once:resize2fs 1.43.4 (31-Jan-2017)
Nov systemd[]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
Nov systemd[]: Started Avahi mDNS/DNS-SD Stack.
Nov systemd[]: Started Login Service.
Nov kernel: [ ] EXT4-fs (mmcblk0p2): resizing filesystem from 1189376 to 7803392 blocks
Nov systemd[]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Nov systemd[]: Starting Load/Save RF Kill Switch Status...
Nov systemd[]: Started Load/Save RF Kill Switch Status.
Nov systemd[]: Started Raise network interfaces.
What was done in the Feb syslog before dhcpcd starts which wasn't done before dhcpcd starts in the Nov syslog

Code: Select all

Feb kernel: [ ] Waiting for root device /dev/mmcblk0p2...
Feb kernel: [ ] random: crng init done
Feb kernel: [ ] brcmfmac: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
Feb kernel: [ ] 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
Feb systemd[]: Started File System Check on Root Device.
Feb systemd[]: Starting Remount Root and Kernel File Systems...
Feb systemd[]: Received SIGRTMIN+20 from PID 158 (plymouthd).
Feb systemd-fsck[]: /dev/mmcblk0p1: 144 files, 42655/83705 clusters
Feb systemd[]: apt-daily.timer: Adding 6h 43min 39.610214s random time.
Feb systemd[]: apt-daily-upgrade.timer: Adding 38min 1.544771s random time.

repo
Posts: 6
Joined: Fri Feb 16, 2018 9:02 am

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 9:13 am

carriba wrote:
Thu Feb 08, 2018 2:10 pm
I've done this morning a "sudo apt-get update ; sudo apt-get -y upgrade" on a Raspberry Pi Zero W and from have been able to witness during the update that certain firmware packages have been installed as well.


Question: What have the Raspbian Stretch packages updates done today to my device?
will it be fixed and how without reinstalling whole system?
cant these people read?

pcmanbob
Posts: 7073
Joined: Fri May 31, 2013 9:28 pm
Location: Mansfield UK

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 11:19 am

repo wrote:
Fri Feb 16, 2018 9:13 am
carriba wrote:
Thu Feb 08, 2018 2:10 pm
I've done this morning a "sudo apt-get update ; sudo apt-get -y upgrade" on a Raspberry Pi Zero W and from have been able to witness during the update that certain firmware packages have been installed as well.


Question: What have the Raspbian Stretch packages updates done today to my device?
will it be fixed and how without reinstalling whole system?
cant these people read?
As other people including me have done the updates without any problems It is not a problem with the updates but more likely a problem with something specific to the individual pi having the problem.

As we don't know exactly what's installed or how everything is configured of the pi its unlikely anyone could say how it can be fixed unless they could get their hands on the pi in question for testing, there is a limit on what faulting you can do remotely
We want information… information… information........................no information no help
The use of crystal balls & mind reading are not supported

repo
Posts: 6
Joined: Fri Feb 16, 2018 9:02 am

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 2:48 pm

i do not understand why you replied if have no problem and cant offer help and i do not believe you, forum is moderated so easy to ignore complaints. As op said tried new sd card, new installation and update broke things again so definitely updates to blame. I have Pi Zero W version 1.1 dated 2016 everything worked until decided to update.
Now even ethernet dongle does not work after update unless assigned static IP addrress

pcmanbob
Posts: 7073
Joined: Fri May 31, 2013 9:28 pm
Location: Mansfield UK

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 4:30 pm

repo wrote:
Fri Feb 16, 2018 2:48 pm
i do not understand why you replied if have no problem and cant offer help and i do not believe you, forum is moderated so easy to ignore complaints. As op said tried new sd card, new installation and update broke things again so definitely updates to blame. I have Pi Zero W version 1.1 dated 2016 everything worked until decided to update.
Now even ethernet dongle does not work after update unless assigned static IP addrress
if you look back to the start of the post you will find my attempts to help including working through logs of boots by the original poster carriba eliminating various things , even ShiftPlusOne of the RPF has not been able to reproduce this issue.
ShiftPlusOne wrote:
Tue Feb 13, 2018 6:47 pm
If I could reproduce the issue, I would start by installing updates one by one and see what breaks it.

Edit: Also, did restarting dhcpcd after booting kick it into life?
several suggestions of things to try were posted but as yet carriba has not posted back with the results.
We want information… information… information........................no information no help
The use of crystal balls & mind reading are not supported

User avatar
carriba
Posts: 139
Joined: Tue Nov 18, 2014 5:55 pm
Contact: ICQ

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 4:40 pm

ShiftPlusOne wrote:
Tue Feb 13, 2018 6:47 pm
If I could reproduce the issue, I would start by installing updates one by one and see what breaks it.
I have followed your advice and have reflashed the SD card with the Raspbian Stretch November 2017 image.

This time, I did configure the OS packages repository to prevent any updating of firmware specific packages with the command:

Code: Select all

for i in `dpkg --get-selections | grep install | grep firmware | awk '{ print $1 }'` ; do echo "$i hold" | sudo dpkg --set-selections ; done


I ran the usual "sudo apt-get update ; sudo apt-get -y upgrade" command, and rebooted the Raspberry Pi Zero W device, and it came up without any problems. Access to the Wifi AP granted and I can connect the headless Raspberry Pi Zero W device with Wifi using the known mechanism.

Here the corresponding contents of the "/var/log/syslog" file after rebooting the device:

Code: Select all

Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Booting Linux on physical CPU 0x0
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Linux version 4.9.59+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1047 Sun Oct 29 11:47:10 GMT 2017
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] OF: fdt:Machine model: Raspberry Pi Zero W Rev 1.1
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] cma: Reserved 8 MiB at 0x1b400000
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Memory policy: Data cache writeback
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] On node 0 totalpages: 114688
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] free_area_init_node: node 0, pgdat c0914e10, node_mem_map db010000
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]   Normal zone: 1008 pages used for memmap
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]   Normal zone: 0 pages reserved
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]   Normal zone: 114688 pages, LIFO batch:31
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] pcpu-alloc: [0] 0
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 113680
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:9E:23:52 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet logo.nologo plymouth.ignore-serial-consoles
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Memory: 435944K/458752K available (5950K kernel code, 491K rwdata, 1948K rodata, 396K init, 725K bss, 14616K reserved, 8192K cma-reserved)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Virtual kernel memory layout:
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     vmalloc : 0xdc800000 - 0xff800000   ( 560 MB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xdc000000   ( 448 MB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]       .text : 0xc0008000 - 0xc05d7a48   (5951 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]       .init : 0xc0841000 - 0xc08a4000   ( 396 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]       .data : 0xc08a4000 - 0xc091ef48   ( 492 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]        .bss : 0xc091ef48 - 0xc09d4648   ( 726 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] NR_IRQS:16 nr_irqs:16 16
Feb 16 17:15:16 raspberrypi kernel: [    0.000031] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
Feb 16 17:15:16 raspberrypi kernel: [    0.000062] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
Feb 16 17:15:16 raspberrypi kernel: [    0.000155] bcm2835: system timer (irq = 27)
Feb 16 17:15:16 raspberrypi kernel: [    0.000614] Console: colour dummy device 80x30
Feb 16 17:15:16 raspberrypi kernel: [    0.000638] console [tty1] enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.000664] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
Feb 16 17:15:16 raspberrypi kernel: [    0.060316] pid_max: default: 32768 minimum: 301
Feb 16 17:15:16 raspberrypi kernel: [    0.060746] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.060762] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.062019] Disabling memory control group subsystem
Feb 16 17:15:16 raspberrypi kernel: [    0.062156] CPU: Testing write buffer coherency: ok
Feb 16 17:15:16 raspberrypi kernel: [    0.062214] ftrace: allocating 21715 entries in 64 pages
Feb 16 17:15:16 raspberrypi kernel: [    0.180500] Setting up static identity map for 0x8200 - 0x8238
Feb 16 17:15:16 raspberrypi kernel: [    0.182497] devtmpfs: initialized
Feb 16 17:15:16 raspberrypi kernel: [    0.192305] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
Feb 16 17:15:16 raspberrypi kernel: [    0.192727] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Feb 16 17:15:16 raspberrypi kernel: [    0.192754] futex hash table entries: 256 (order: -1, 3072 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.194033] pinctrl core: initialized pinctrl subsystem
Feb 16 17:15:16 raspberrypi kernel: [    0.195475] NET: Registered protocol family 16
Feb 16 17:15:16 raspberrypi kernel: [    0.197996] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Feb 16 17:15:16 raspberrypi kernel: [    0.207659] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
Feb 16 17:15:16 raspberrypi kernel: [    0.207676] hw-breakpoint: maximum watchpoint size is 4 bytes.
Feb 16 17:15:16 raspberrypi kernel: [    0.207777] Serial: AMBA PL011 UART driver
Feb 16 17:15:16 raspberrypi kernel: [    0.210679] bcm2835-mbox 2000b880.mailbox: mailbox enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.211429] uart-pl011 20201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
Feb 16 17:15:16 raspberrypi kernel: [    0.261253] bcm2835-dma 20007000.dma: DMA legacy API manager at dc80d000, dmachans=0x1
Feb 16 17:15:16 raspberrypi kernel: [    0.263901] SCSI subsystem initialized
Feb 16 17:15:16 raspberrypi kernel: [    0.264162] usbcore: registered new interface driver usbfs
Feb 16 17:15:16 raspberrypi kernel: [    0.264283] usbcore: registered new interface driver hub
Feb 16 17:15:16 raspberrypi kernel: [    0.264480] usbcore: registered new device driver usb
Feb 16 17:15:16 raspberrypi kernel: [    0.270571] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-10-24 17:09
Feb 16 17:15:16 raspberrypi kernel: [    0.272575] clocksource: Switched to clocksource timer
Feb 16 17:15:16 raspberrypi kernel: [    0.326718] VFS: Disk quotas dquot_6.6.0
Feb 16 17:15:16 raspberrypi kernel: [    0.326836] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.327158] FS-Cache: Loaded
Feb 16 17:15:16 raspberrypi kernel: [    0.327514] CacheFiles: Loaded
Feb 16 17:15:16 raspberrypi kernel: [    0.346892] NET: Registered protocol family 2
Feb 16 17:15:16 raspberrypi kernel: [    0.348231] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.348321] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.348416] TCP: Hash tables configured (established 4096 bind 4096)
Feb 16 17:15:16 raspberrypi kernel: [    0.348515] UDP hash table entries: 256 (order: 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.348542] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.348852] NET: Registered protocol family 1
Feb 16 17:15:16 raspberrypi kernel: [    0.349595] RPC: Registered named UNIX socket transport module.
Feb 16 17:15:16 raspberrypi kernel: [    0.349607] RPC: Registered udp transport module.
Feb 16 17:15:16 raspberrypi kernel: [    0.349612] RPC: Registered tcp transport module.
Feb 16 17:15:16 raspberrypi kernel: [    0.349617] RPC: Registered tcp NFSv4.1 backchannel transport module.
Feb 16 17:15:16 raspberrypi kernel: [    0.350850] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
Feb 16 17:15:16 raspberrypi kernel: [    0.353418] workingset: timestamp_bits=14 max_order=17 bucket_order=3
Feb 16 17:15:16 raspberrypi kernel: [    0.374090] FS-Cache: Netfs 'nfs' registered for caching
Feb 16 17:15:16 raspberrypi kernel: [    0.375845] NFS: Registering the id_resolver key type
Feb 16 17:15:16 raspberrypi kernel: [    0.375892] Key type id_resolver registered
Feb 16 17:15:16 raspberrypi kernel: [    0.375899] Key type id_legacy registered
Feb 16 17:15:16 raspberrypi kernel: [    0.380361] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Feb 16 17:15:16 raspberrypi kernel: [    0.380725] io scheduler noop registered
Feb 16 17:15:16 raspberrypi kernel: [    0.380738] io scheduler deadline registered (default)
Feb 16 17:15:16 raspberrypi kernel: [    0.381205] io scheduler cfq registered
Feb 16 17:15:16 raspberrypi kernel: [    0.387203] BCM2708FB: allocated DMA memory 5b500000
Feb 16 17:15:16 raspberrypi kernel: [    0.387262] BCM2708FB: allocated DMA channel 0 @ dc80d000
Feb 16 17:15:16 raspberrypi kernel: [    0.395542] Console: switching to colour frame buffer device 82x26
Feb 16 17:15:16 raspberrypi kernel: [    0.404063] bcm2835-rng 20104000.rng: hwrng registered
Feb 16 17:15:16 raspberrypi kernel: [    0.404230] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
Feb 16 17:15:16 raspberrypi kernel: [    0.405190] vc-sm: Videocore shared memory driver
Feb 16 17:15:16 raspberrypi kernel: [    0.429747] brd: module loaded
Feb 16 17:15:16 raspberrypi kernel: [    0.442201] loop: module loaded
Feb 16 17:15:16 raspberrypi kernel: [    0.442222] Loading iSCSI transport class v2.0-870.
Feb 16 17:15:16 raspberrypi kernel: [    0.443206] usbcore: registered new interface driver smsc95xx
Feb 16 17:15:16 raspberrypi kernel: [    0.443234] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Feb 16 17:15:16 raspberrypi kernel: [    0.671612] Core Release: 2.80a
Feb 16 17:15:16 raspberrypi kernel: [    0.671639] Setting default values for core params
Feb 16 17:15:16 raspberrypi kernel: [    0.671679] Finished setting default values for core params
Feb 16 17:15:16 raspberrypi kernel: [    0.872094] Using Buffer DMA mode
Feb 16 17:15:16 raspberrypi kernel: [    0.872107] Periodic Transfer Interrupt Enhancement - disabled
Feb 16 17:15:16 raspberrypi kernel: [    0.872111] Multiprocessor Interrupt Enhancement - disabled
Feb 16 17:15:16 raspberrypi kernel: [    0.872121] OTG VER PARAM: 0, OTG VER FLAG: 0
Feb 16 17:15:16 raspberrypi kernel: [    0.872214] Dedicated Tx FIFOs mode
Feb 16 17:15:16 raspberrypi kernel: [    0.872897] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xdb514000 dma = 0x5b514000 len=9024
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] FIQ FSM acceleration enabled for :
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] Non-periodic Split Transactions
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] Periodic Split Transactions
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] High-Speed Isochronous Endpoints
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] Interrupt/Control Split Transaction hack enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.872936] dwc_otg: Microframe scheduler enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.873021] WARN::hcd_init_fiq:459: FIQ on core 0 at 0xc0451694
Feb 16 17:15:16 raspberrypi kernel: [    0.873034] WARN::hcd_init_fiq:460: FIQ ASM at 0xc0451970 length 36
Feb 16 17:15:16 raspberrypi kernel: [    0.873059] WARN::hcd_init_fiq:486: MPHI regs_base at 0xdc8a5000
Feb 16 17:15:16 raspberrypi kernel: [    0.873130] dwc_otg 20980000.usb: DWC OTG Controller
Feb 16 17:15:16 raspberrypi kernel: [    0.873190] dwc_otg 20980000.usb: new USB bus registered, assigned bus number 1
Feb 16 17:15:16 raspberrypi kernel: [    0.873309] dwc_otg 20980000.usb: irq 56, io mem 0x00000000
Feb 16 17:15:16 raspberrypi kernel: [    0.873365] Init: Port Power? op_state=1
Feb 16 17:15:16 raspberrypi kernel: [    0.873370] Init: Power Port (0)
Feb 16 17:15:16 raspberrypi kernel: [    0.873743] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 16 17:15:16 raspberrypi kernel: [    0.873759] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 16 17:15:16 raspberrypi kernel: [    0.873770] usb usb1: Product: DWC OTG Controller
Feb 16 17:15:16 raspberrypi kernel: [    0.873780] usb usb1: Manufacturer: Linux 4.9.59+ dwc_otg_hcd
Feb 16 17:15:16 raspberrypi kernel: [    0.873789] usb usb1: SerialNumber: 20980000.usb
Feb 16 17:15:16 raspberrypi kernel: [    0.874968] hub 1-0:1.0: USB hub found
Feb 16 17:15:16 raspberrypi kernel: [    0.875060] hub 1-0:1.0: 1 port detected
Feb 16 17:15:16 raspberrypi kernel: [    0.875951] dwc_otg: FIQ enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.875961] dwc_otg: NAK holdoff enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.875966] dwc_otg: FIQ split-transaction FSM enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.875987] Module dwc_common_port init
Feb 16 17:15:16 raspberrypi kernel: [    0.876474] usbcore: registered new interface driver usb-storage
Feb 16 17:15:16 raspberrypi kernel: [    0.876919] mousedev: PS/2 mouse device common for all mice
Feb 16 17:15:16 raspberrypi kernel: [    0.878551] bcm2835-wdt 20100000.watchdog: Broadcom BCM2835 watchdog timer
Feb 16 17:15:16 raspberrypi kernel: [    0.879058] bcm2835-cpufreq: min=700000 max=1000000
Feb 16 17:15:16 raspberrypi kernel: [    0.879672] sdhci: Secure Digital Host Controller Interface driver
Feb 16 17:15:16 raspberrypi kernel: [    0.879682] sdhci: Copyright(c) Pierre Ossman
Feb 16 17:15:16 raspberrypi kernel: [    0.880151] sdhost-bcm2835 20202000.sdhost: could not get clk, deferring probe
Feb 16 17:15:16 raspberrypi kernel: [    0.882694] mmc-bcm2835 20300000.mmc: could not get clk, deferring probe
Feb 16 17:15:16 raspberrypi kernel: [    0.882882] sdhci-pltfm: SDHCI platform and OF driver helper
Feb 16 17:15:16 raspberrypi kernel: [    0.883399] ledtrig-cpu: registered to indicate activity on CPUs
Feb 16 17:15:16 raspberrypi kernel: [    0.883544] hidraw: raw HID events driver (C) Jiri Kosina
Feb 16 17:15:16 raspberrypi kernel: [    0.883816] usbcore: registered new interface driver usbhid
Feb 16 17:15:16 raspberrypi kernel: [    0.883823] usbhid: USB HID core driver
Feb 16 17:15:16 raspberrypi kernel: [    0.885066] vchiq: vchiq_init_state: slot_zero = 0xdb580000, is_master = 0
Feb 16 17:15:16 raspberrypi kernel: [    0.886948] [vc_sm_connected_init]: start
Feb 16 17:15:16 raspberrypi kernel: [    0.896387] [vc_sm_connected_init]: end - returning 0
Feb 16 17:15:16 raspberrypi kernel: [    0.896881] Initializing XFRM netlink socket
Feb 16 17:15:16 raspberrypi kernel: [    0.896920] NET: Registered protocol family 17
Feb 16 17:15:16 raspberrypi kernel: [    0.897075] Key type dns_resolver registered
Feb 16 17:15:16 raspberrypi kernel: [    0.898929] registered taskstats version 1
Feb 16 17:15:16 raspberrypi kernel: [    0.908056] uart-pl011 20201000.serial: cts_event_workaround enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.908202] 20201000.serial: ttyAMA0 at MMIO 0x20201000 (irq = 81, base_baud = 0) is a PL011 rev2
Feb 16 17:15:16 raspberrypi kernel: [    0.910628] sdhost: log_buf @ db513000 (5b513000)
Feb 16 17:15:16 raspberrypi kernel: [    0.982660] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Feb 16 17:15:16 raspberrypi kernel: [    0.985239] mmc-bcm2835 20300000.mmc: mmc_debug:0 mmc_debug2:0
Feb 16 17:15:16 raspberrypi kernel: [    0.985257] mmc-bcm2835 20300000.mmc: DMA channel allocated
Feb 16 17:15:16 raspberrypi kernel: [    1.015452] random: fast init done
Feb 16 17:15:16 raspberrypi kernel: [    1.060068] mmc0: host does not support reading read-only switch, assuming write-enable
Feb 16 17:15:16 raspberrypi kernel: [    1.062137] mmc0: new high speed SDHC card at address b368
Feb 16 17:15:16 raspberrypi kernel: [    1.062790] of_cfs_init
Feb 16 17:15:16 raspberrypi kernel: [    1.062929] of_cfs_init: OK
Feb 16 17:15:16 raspberrypi kernel: [    1.065555] mmcblk0: mmc0:b368 NCard 14.9 GiB
Feb 16 17:15:16 raspberrypi kernel: [    1.073347]  mmcblk0: p1 p2
Feb 16 17:15:16 raspberrypi kernel: [    1.086279] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    1.088281] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    1.090502] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Feb 16 17:15:16 raspberrypi kernel: [    1.090592] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Feb 16 17:15:16 raspberrypi kernel: [    1.091648] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    1.092134] devtmpfs: mounted
Feb 16 17:15:16 raspberrypi kernel: [    1.093454] Freeing unused kernel memory: 396K
Feb 16 17:15:16 raspberrypi kernel: [    1.093464] This architecture does not have kernel memory protection.
Feb 16 17:15:16 raspberrypi kernel: [    1.096110] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    1.202486] mmc1: new high speed SDIO card at address 0001
Feb 16 17:15:16 raspberrypi kernel: [    1.796039] NET: Registered protocol family 10
Feb 16 17:15:16 raspberrypi kernel: [    1.830604] ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 16 17:15:16 raspberrypi kernel: [    3.451509] i2c /dev entries driver
Feb 16 17:15:16 raspberrypi kernel: [    4.989933] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Feb 16 17:15:16 raspberrypi kernel: [    7.894556] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
Feb 16 17:15:16 raspberrypi kernel: [    9.018106] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Feb 16 17:15:16 raspberrypi kernel: [    9.043294] usbcore: registered new interface driver brcmfmac
Feb 16 17:15:16 raspberrypi kernel: [    9.423162] brcmfmac: Firmware version = wl0: Aug  7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
Feb 16 17:15:16 raspberrypi kernel: [    9.424504] 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.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47
Feb 16 17:15:16 raspberrypi kernel: [   12.921552] uart-pl011 20201000.serial: no DMA platform data
Feb 16 17:15:16 raspberrypi avahi-daemon[223]: Successfully called chroot().
Feb 16 17:15:16 raspberrypi avahi-daemon[223]: Successfully dropped remaining capabilities.
Feb 16 17:15:16 raspberrypi avahi-daemon[223]: No service file found in /etc/avahi/services.
Feb 16 17:15:16 raspberrypi avahi-daemon[223]: Network interface enumeration completed.
Feb 16 17:15:16 raspberrypi avahi-daemon[223]: Server startup complete. Host name is raspberrypi.local. Local service cookie is 2018728155.
Feb 16 17:15:16 raspberrypi systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Feb 16 17:15:16 raspberrypi systemd[1]: Starting Login Service...
Feb 16 17:15:16 raspberrypi systemd[1]: Starting System Logging Service...
Feb 16 17:15:16 raspberrypi systemd[1]: Started triggerhappy global hotkey daemon.
Feb 16 17:15:16 raspberrypi systemd[1]: Started Check for v3d driver.
Feb 16 17:15:16 raspberrypi systemd[1]: Started dhcpcd on all interfaces.
Feb 16 17:15:16 raspberrypi liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="262" x-info="http://www.rsyslog.com"] start
Feb 16 17:15:16 raspberrypi systemd[1]: Started System Logging Service.
Feb 16 17:15:16 raspberrypi dphys-swapfile[240]: Starting dphys-swapfile swapfile setup ...
Feb 16 17:15:16 raspberrypi raspi-config[225]: Checking if shift key is held down:Error opening '/dev/input/event*': No such file or directory
Feb 16 17:15:17 raspberrypi raspi-config[225]:  No. Switching to ondemand scaling governor.
Feb 16 17:15:17 raspberrypi systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
Feb 16 17:15:17 raspberrypi systemd[1]: Started Login Service.
Feb 16 17:15:17 raspberrypi systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Feb 16 17:15:17 raspberrypi systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb 16 17:15:17 raspberrypi dphys-swapfile[240]: want /var/swap=100MByte, checking existing: keeping it
Feb 16 17:15:17 raspberrypi systemd[1]: Started Load/Save RF Kill Switch Status.
Feb 16 17:15:17 raspberrypi systemd[1]: Started Raise network interfaces.
Feb 16 17:15:17 raspberrypi systemd[1]: Reached target Network.
Feb 16 17:15:17 raspberrypi systemd[1]: Starting /etc/rc.local Compatibility...
Feb 16 17:15:17 raspberrypi systemd[1]: Starting OpenBSD Secure Shell server...
Feb 16 17:15:17 raspberrypi systemd[1]: Starting Permit User Sessions...
Feb 16 17:15:17 raspberrypi kernel: [   15.041760] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS
Feb 16 17:15:17 raspberrypi dphys-swapfile[240]: done.
Feb 16 17:15:17 raspberrypi systemd[1]: Started LSB: Autogenerate and use a swap file.
Feb 16 17:15:18 raspberrypi systemd[1]: Started Permit User Sessions.
Feb 16 17:15:18 raspberrypi systemd-udevd[138]: Process '/sbin/crda' failed with exit code 249.
Feb 16 17:15:18 raspberrypi systemd[1]: Starting Light Display Manager...
Feb 16 17:15:18 raspberrypi dhcpcd-run-hooks[336]: wlan0: starting wpa_supplicant
Feb 16 17:15:18 raspberrypi systemd[1]: Started OpenBSD Secure Shell server.
Feb 16 17:15:18 raspberrypi kernel: [   16.123759] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 17:15:18 raspberrypi kernel: [   16.123776] brcmfmac: power management disabled
Feb 16 17:15:19 raspberrypi dhcpcd[255]: wlan0: waiting for carrier
Feb 16 17:15:19 raspberrypi dhcpcd[255]: wlan0: carrier acquired
Feb 16 17:15:19 raspberrypi lightdm[346]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 16 17:15:19 raspberrypi dhcpcd[255]: DUID 00:01:00:01:21:b0:de:83:b8:27:eb:cb:76:07
Feb 16 17:15:19 raspberrypi dhcpcd[255]: wlan0: IAID eb:cb:76:07
Feb 16 17:15:19 raspberrypi dhcpcd[255]: wlan0: adding address fe80::a6d3:3185:7be6:d0c4
Feb 16 17:15:19 raspberrypi dhcpcd[255]: wlan0: carrier lost
Feb 16 17:15:19 raspberrypi dhcpcd[255]: wlan0: deleting address fe80::a6d3:3185:7be6:d0c4
Feb 16 17:15:19 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 144 (plymouthd).
Feb 16 17:15:19 raspberrypi lightdm[346]: Failed to create IPv6 VNC socket: Error binding to address: Address already in use
Feb 16 17:15:19 raspberrypi systemd[1]: Started Light Display Manager.
Feb 16 17:15:20 raspberrypi systemd[1]: Started /etc/rc.local Compatibility.
Feb 16 17:15:20 raspberrypi kernel: [   17.524843] Bluetooth: Core ver 2.22
Feb 16 17:15:20 raspberrypi kernel: [   17.524977] NET: Registered protocol family 31
Feb 16 17:15:20 raspberrypi kernel: [   17.524983] Bluetooth: HCI device and connection manager initialized
Feb 16 17:15:20 raspberrypi kernel: [   17.525004] Bluetooth: HCI socket layer initialized
Feb 16 17:15:20 raspberrypi kernel: [   17.525017] Bluetooth: L2CAP socket layer initialized
Feb 16 17:15:20 raspberrypi kernel: [   17.525056] Bluetooth: SCO socket layer initialized
Feb 16 17:15:20 raspberrypi kernel: [   17.550287] Bluetooth: HCI UART driver ver 2.3
Feb 16 17:15:20 raspberrypi kernel: [   17.550302] Bluetooth: HCI UART protocol H4 registered
Feb 16 17:15:20 raspberrypi kernel: [   17.550307] Bluetooth: HCI UART protocol Three-wire (H5) registered
Feb 16 17:15:20 raspberrypi kernel: [   17.550439] Bluetooth: HCI UART protocol Broadcom registered
Feb 16 17:15:20 raspberrypi systemd[1]: Starting Hold until boot process finishes up...
Feb 16 17:15:20 raspberrypi btuart[224]: bcm43xx_init
Feb 16 17:15:20 raspberrypi btuart[224]: Flash firmware /lib/firmware/BCM43430A1.hcd
Feb 16 17:15:20 raspberrypi btuart[224]: Set BDADDR UART: b8:27:eb:34:89:f8
Feb 16 17:15:20 raspberrypi btuart[224]: Set Controller UART speed to 3000000 bit/s
Feb 16 17:15:20 raspberrypi btuart[224]: Device setup complete
Feb 16 17:15:20 raspberrypi systemd[1]: Starting Terminate Plymouth Boot Screen...
Feb 16 17:15:20 raspberrypi systemd[1]: Started Configure Bluetooth Modems connected by UART.
Feb 16 17:15:20 raspberrypi systemd[1]: Started Hold until boot process finishes up.
Feb 16 17:15:20 raspberrypi systemd[1]: Started Terminate Plymouth Boot Screen.
Feb 16 17:15:20 raspberrypi systemd[1]: Started Getty on tty1.
Feb 16 17:15:20 raspberrypi systemd[1]: Reached target Login Prompts.
Feb 16 17:15:20 raspberrypi systemd[1]: Starting Bluetooth service...
Feb 16 17:15:20 raspberrypi systemd[1]: Reached target Multi-User System.
Feb 16 17:15:20 raspberrypi bluetoothd[394]: Bluetooth daemon 5.43
Feb 16 17:15:20 raspberrypi systemd[1]: Started Bluetooth service.
Feb 16 17:15:20 raspberrypi bluetoothd[394]: Starting SDP server
Feb 16 17:15:20 raspberrypi systemd[1]: Started BluezALSA proxy.
Feb 16 17:15:20 raspberrypi systemd[1]: Reached target Graphical Interface.
Feb 16 17:15:20 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb 16 17:15:20 raspberrypi kernel: [   18.211106] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 16 17:15:20 raspberrypi kernel: [   18.211118] Bluetooth: BNEP filters: protocol multicast
Feb 16 17:15:20 raspberrypi kernel: [   18.211140] Bluetooth: BNEP socket layer initialized
Feb 16 17:15:21 raspberrypi bluetoothd[394]: Bluetooth management interface 1.14 initialized
Feb 16 17:15:21 raspberrypi bluetoothd[394]: Failed to obtain handles for "Service Changed" characteristic
Feb 16 17:15:21 raspberrypi bluetoothd[394]: Sap driver initialization failed.
Feb 16 17:15:21 raspberrypi dbus[245]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 16 17:15:21 raspberrypi bluetoothd[394]: sap-server: Operation not permitted (1)
Feb 16 17:15:21 raspberrypi bluetoothd[394]: Endpoint registered: sender=:1.6 path=/A2DP/SBC/Source/1
Feb 16 17:15:21 raspberrypi bluetoothd[394]: Endpoint registered: sender=:1.6 path=/A2DP/SBC/Sink/1
Feb 16 17:15:21 raspberrypi kernel: [   18.552707] Bluetooth: RFCOMM TTY layer initialized
Feb 16 17:15:21 raspberrypi kernel: [   18.552741] Bluetooth: RFCOMM socket layer initialized
Feb 16 17:15:21 raspberrypi kernel: [   18.552781] Bluetooth: RFCOMM ver 1.11
Feb 16 17:15:21 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
Feb 16 17:15:21 raspberrypi systemd[1]: Starting Hostname Service...
Feb 16 17:15:21 raspberrypi systemd[1]: Reached target Bluetooth.
Feb 16 17:15:21 raspberrypi dbus[245]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 16 17:15:21 raspberrypi systemd[1]: Started Hostname Service.
Feb 16 17:15:21 raspberrypi systemd[1]: Startup finished in 1.513s (kernel) + 17.281s (userspace) = 18.795s.
Feb 16 17:15:21 raspberrypi systemd[1]: Created slice User Slice of pi.
Feb 16 17:15:22 raspberrypi systemd[1]: Started Session c1 of user pi.
Feb 16 17:15:22 raspberrypi systemd[1]: Starting User Manager for UID 1000...
Feb 16 17:15:22 raspberrypi systemd[421]: Starting D-Bus User Message Bus Socket.
Feb 16 17:15:22 raspberrypi systemd[421]: Reached target Timers.
Feb 16 17:15:22 raspberrypi systemd[421]: Listening on GnuPG cryptographic agent (access for web browsers).
Feb 16 17:15:22 raspberrypi systemd[421]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 16 17:15:22 raspberrypi systemd[421]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 16 17:15:22 raspberrypi systemd[421]: Reached target Paths.
Feb 16 17:15:22 raspberrypi systemd[421]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 16 17:15:22 raspberrypi systemd[421]: Listening on D-Bus User Message Bus Socket.
Feb 16 17:15:22 raspberrypi systemd[421]: Reached target Sockets.
Feb 16 17:15:22 raspberrypi systemd[421]: Reached target Basic System.
Feb 16 17:15:22 raspberrypi systemd[421]: Reached target Default.
Feb 16 17:15:22 raspberrypi systemd[421]: Startup finished in 457ms.
Feb 16 17:15:22 raspberrypi systemd[1]: Started User Manager for UID 1000.
Feb 16 17:15:24 raspberrypi lightdm[448]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 16 17:15:24 raspberrypi systemd[1]: Started Session c2 of user pi.
Feb 16 17:15:25 raspberrypi lightdm[346]: Error opening audit socket: Protocol not supported
Feb 16 17:15:25 raspberrypi systemd[421]: Started D-Bus User Message Bus.
Feb 16 17:15:28 raspberrypi dbus-daemon[466]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Feb 16 17:15:28 raspberrypi systemd[421]: Starting Virtual filesystem service...
Feb 16 17:15:28 raspberrypi dbus-daemon[466]: Successfully activated service 'org.gtk.vfs.Daemon'
Feb 16 17:15:28 raspberrypi systemd[421]: Started Virtual filesystem service.
Feb 16 17:15:29 raspberrypi kernel: [   26.341881] fuse init (API version 7.26)
Feb 16 17:15:29 raspberrypi systemd[1]: Mounting FUSE Control File System...
Feb 16 17:15:29 raspberrypi systemd[1]: Mounted FUSE Control File System.
Feb 16 17:15:30 raspberrypi dbus[245]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Feb 16 17:15:30 raspberrypi systemd[1]: Starting Authorization Manager...
Feb 16 17:15:31 raspberrypi polkitd[561]: started daemon version 0.105 using authority implementation `local' version `0.105'
Feb 16 17:15:31 raspberrypi dbus[245]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 16 17:15:31 raspberrypi systemd[1]: Started Authorization Manager.
Feb 16 17:15:41 raspberrypi dbus-daemon[466]: Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service'
Feb 16 17:15:42 raspberrypi systemd[421]: Starting Virtual filesystem service - disk device monitor...
Feb 16 17:15:44 raspberrypi dbus[245]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 16 17:15:44 raspberrypi systemd[1]: Starting Disk Manager...
Feb 16 17:15:44 raspberrypi udisksd[605]: udisks daemon version 2.1.8 starting
Feb 16 17:15:45 raspberrypi dbus[245]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 16 17:15:45 raspberrypi systemd[1]: Started Disk Manager.
Feb 16 17:15:45 raspberrypi udisksd[605]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 16 17:15:45 raspberrypi dbus-daemon[466]: Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Feb 16 17:15:45 raspberrypi systemd[421]: Started Virtual filesystem service - disk device monitor.
Feb 16 17:15:45 raspberrypi dbus-daemon[466]: Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service'
Feb 16 17:15:45 raspberrypi systemd[421]: Starting Virtual filesystem service - digital camera monitor...
Feb 16 17:15:46 raspberrypi dbus-daemon[466]: Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Feb 16 17:15:46 raspberrypi systemd[421]: Started Virtual filesystem service - digital camera monitor.
Feb 16 17:15:46 raspberrypi dbus-daemon[466]: Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service'
Feb 16 17:15:46 raspberrypi systemd[421]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Feb 16 17:15:46 raspberrypi dbus-daemon[466]: Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Feb 16 17:15:46 raspberrypi systemd[421]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Feb 16 17:15:46 raspberrypi dbus-daemon[466]: Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service'
Feb 16 17:15:46 raspberrypi systemd[421]: Starting Virtual filesystem service - Apple File Conduit monitor...
Feb 16 17:15:46 raspberrypi gvfs-afc-volume-monitor[625]: Volume monitor alive
Feb 16 17:15:46 raspberrypi dbus-daemon[466]: Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Feb 16 17:15:46 raspberrypi systemd[421]: Started Virtual filesystem service - Apple File Conduit monitor.
Feb 16 17:15:46 raspberrypi dbus-daemon[466]: Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service'
Feb 16 17:15:46 raspberrypi systemd[421]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Feb 16 17:15:46 raspberrypi dbus-daemon[466]: Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Feb 16 17:15:46 raspberrypi systemd[421]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Feb 16 17:16:01 raspberrypi kernel: [   59.101694] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 16 17:16:02 raspberrypi dhcpcd[255]: wlan0: carrier acquired
Feb 16 17:16:02 raspberrypi dhcpcd[255]: wlan0: IAID eb:cb:76:07
Feb 16 17:16:02 raspberrypi dhcpcd[255]: wlan0: adding address fe80::f09:b82c:7fdd:6f12
Feb 16 17:16:03 raspberrypi dhcpcd[255]: wlan0: rebinding lease of 192.168.0.31
Feb 16 17:16:03 raspberrypi dhcpcd[255]: wlan0: probing address 192.168.0.31/24
Feb 16 17:16:03 raspberrypi dhcpcd[255]: wlan0: soliciting an IPv6 router
Feb 16 17:16:04 raspberrypi avahi-daemon[223]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::f09:b82c:7fdd:6f12.
Feb 16 17:16:04 raspberrypi avahi-daemon[223]: New relevant interface wlan0.IPv6 for mDNS.
Feb 16 17:16:04 raspberrypi avahi-daemon[223]: Registering new address record for fe80::f09:b82c:7fdd:6f12 on wlan0.*.
Feb 16 17:16:08 raspberrypi dhcpcd[255]: wlan0: leased 192.168.0.31 for 864000 seconds
Feb 16 17:16:08 raspberrypi avahi-daemon[223]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.31.
Feb 16 17:16:08 raspberrypi dhcpcd[255]: wlan0: adding route to 192.168.0.0/24
Feb 16 17:16:08 raspberrypi dhcpcd[255]: wlan0: adding default route via 192.168.0.254
Feb 16 17:16:08 raspberrypi avahi-daemon[223]: New relevant interface wlan0.IPv4 for mDNS.
Feb 16 17:16:08 raspberrypi avahi-daemon[223]: Registering new address record for 192.168.0.31 on wlan0.IPv4.
Feb 16 17:16:42 raspberrypi systemd[421]: Time has been changed
Feb 16 17:16:42 raspberrypi systemd-timesyncd[202]: Synchronized to time server 193.104.228.123:123 (0.europe.pool.ntp.org).
Feb 16 17:16:42 raspberrypi systemd[1]: Time has been changed
Feb 16 17:16:43 raspberrypi dhcpcd[255]: wlan0: no IPv6 Routers available
Feb 16 17:17:28 raspberrypi CRON[729]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 16 17:21:10 raspberrypi kernel: [  340.342553] random: crng init done
Feb 16 17:23:21 raspberrypi systemd[1]: Started Session c3 of user pi
And here the corresponding contents of the "/var/log/kern.log" file after rebooting the device:

Code: Select all

Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Booting Linux on physical CPU 0x0
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Linux version 4.9.59+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1047 Sun Oct 29 11:47:10 GMT 2017
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] OF: fdt:Machine model: Raspberry Pi Zero W Rev 1.1
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] cma: Reserved 8 MiB at 0x1b400000
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Memory policy: Data cache writeback
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] On node 0 totalpages: 114688
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] free_area_init_node: node 0, pgdat c0914e10, node_mem_map db010000
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]   Normal zone: 1008 pages used for memmap
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]   Normal zone: 0 pages reserved
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]   Normal zone: 114688 pages, LIFO batch:31
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] pcpu-alloc: [0] 0
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 113680
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:9E:23:52 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet logo.nologo plymouth.ignore-serial-consoles
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Memory: 435944K/458752K available (5950K kernel code, 491K rwdata, 1948K rodata, 396K init, 725K bss, 14616K reserved, 8192K cma-reserved)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] Virtual kernel memory layout:
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     vmalloc : 0xdc800000 - 0xff800000   ( 560 MB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xdc000000   ( 448 MB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]       .text : 0xc0008000 - 0xc05d7a48   (5951 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]       .init : 0xc0841000 - 0xc08a4000   ( 396 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]       .data : 0xc08a4000 - 0xc091ef48   ( 492 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000]        .bss : 0xc091ef48 - 0xc09d4648   ( 726 kB)
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Feb 16 17:15:16 raspberrypi kernel: [    0.000000] NR_IRQS:16 nr_irqs:16 16
Feb 16 17:15:16 raspberrypi kernel: [    0.000031] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
Feb 16 17:15:16 raspberrypi kernel: [    0.000062] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
Feb 16 17:15:16 raspberrypi kernel: [    0.000155] bcm2835: system timer (irq = 27)
Feb 16 17:15:16 raspberrypi kernel: [    0.000614] Console: colour dummy device 80x30
Feb 16 17:15:16 raspberrypi kernel: [    0.000638] console [tty1] enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.000664] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
Feb 16 17:15:16 raspberrypi kernel: [    0.060316] pid_max: default: 32768 minimum: 301
Feb 16 17:15:16 raspberrypi kernel: [    0.060746] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.060762] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.062019] Disabling memory control group subsystem
Feb 16 17:15:16 raspberrypi kernel: [    0.062156] CPU: Testing write buffer coherency: ok
Feb 16 17:15:16 raspberrypi kernel: [    0.062214] ftrace: allocating 21715 entries in 64 pages
Feb 16 17:15:16 raspberrypi kernel: [    0.180500] Setting up static identity map for 0x8200 - 0x8238
Feb 16 17:15:16 raspberrypi kernel: [    0.182497] devtmpfs: initialized
Feb 16 17:15:16 raspberrypi kernel: [    0.192305] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
Feb 16 17:15:16 raspberrypi kernel: [    0.192727] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Feb 16 17:15:16 raspberrypi kernel: [    0.192754] futex hash table entries: 256 (order: -1, 3072 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.194033] pinctrl core: initialized pinctrl subsystem
Feb 16 17:15:16 raspberrypi kernel: [    0.195475] NET: Registered protocol family 16
Feb 16 17:15:16 raspberrypi kernel: [    0.197996] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Feb 16 17:15:16 raspberrypi kernel: [    0.207659] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
Feb 16 17:15:16 raspberrypi kernel: [    0.207676] hw-breakpoint: maximum watchpoint size is 4 bytes.
Feb 16 17:15:16 raspberrypi kernel: [    0.207777] Serial: AMBA PL011 UART driver
Feb 16 17:15:16 raspberrypi kernel: [    0.210679] bcm2835-mbox 2000b880.mailbox: mailbox enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.211429] uart-pl011 20201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
Feb 16 17:15:16 raspberrypi kernel: [    0.261253] bcm2835-dma 20007000.dma: DMA legacy API manager at dc80d000, dmachans=0x1
Feb 16 17:15:16 raspberrypi kernel: [    0.263901] SCSI subsystem initialized
Feb 16 17:15:16 raspberrypi kernel: [    0.264162] usbcore: registered new interface driver usbfs
Feb 16 17:15:16 raspberrypi kernel: [    0.264283] usbcore: registered new interface driver hub
Feb 16 17:15:16 raspberrypi kernel: [    0.264480] usbcore: registered new device driver usb
Feb 16 17:15:16 raspberrypi kernel: [    0.270571] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-10-24 17:09
Feb 16 17:15:16 raspberrypi kernel: [    0.272575] clocksource: Switched to clocksource timer
Feb 16 17:15:16 raspberrypi kernel: [    0.326718] VFS: Disk quotas dquot_6.6.0
Feb 16 17:15:16 raspberrypi kernel: [    0.326836] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.327158] FS-Cache: Loaded
Feb 16 17:15:16 raspberrypi kernel: [    0.327514] CacheFiles: Loaded
Feb 16 17:15:16 raspberrypi kernel: [    0.346892] NET: Registered protocol family 2
Feb 16 17:15:16 raspberrypi kernel: [    0.348231] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.348321] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.348416] TCP: Hash tables configured (established 4096 bind 4096)
Feb 16 17:15:16 raspberrypi kernel: [    0.348515] UDP hash table entries: 256 (order: 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.348542] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    0.348852] NET: Registered protocol family 1
Feb 16 17:15:16 raspberrypi kernel: [    0.349595] RPC: Registered named UNIX socket transport module.
Feb 16 17:15:16 raspberrypi kernel: [    0.349607] RPC: Registered udp transport module.
Feb 16 17:15:16 raspberrypi kernel: [    0.349612] RPC: Registered tcp transport module.
Feb 16 17:15:16 raspberrypi kernel: [    0.349617] RPC: Registered tcp NFSv4.1 backchannel transport module.
Feb 16 17:15:16 raspberrypi kernel: [    0.350850] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
Feb 16 17:15:16 raspberrypi kernel: [    0.353418] workingset: timestamp_bits=14 max_order=17 bucket_order=3
Feb 16 17:15:16 raspberrypi kernel: [    0.374090] FS-Cache: Netfs 'nfs' registered for caching
Feb 16 17:15:16 raspberrypi kernel: [    0.375845] NFS: Registering the id_resolver key type
Feb 16 17:15:16 raspberrypi kernel: [    0.375892] Key type id_resolver registered
Feb 16 17:15:16 raspberrypi kernel: [    0.375899] Key type id_legacy registered
Feb 16 17:15:16 raspberrypi kernel: [    0.380361] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Feb 16 17:15:16 raspberrypi kernel: [    0.380725] io scheduler noop registered
Feb 16 17:15:16 raspberrypi kernel: [    0.380738] io scheduler deadline registered (default)
Feb 16 17:15:16 raspberrypi kernel: [    0.381205] io scheduler cfq registered
Feb 16 17:15:16 raspberrypi kernel: [    0.387203] BCM2708FB: allocated DMA memory 5b500000
Feb 16 17:15:16 raspberrypi kernel: [    0.387262] BCM2708FB: allocated DMA channel 0 @ dc80d000
Feb 16 17:15:16 raspberrypi kernel: [    0.395542] Console: switching to colour frame buffer device 82x26
Feb 16 17:15:16 raspberrypi kernel: [    0.404063] bcm2835-rng 20104000.rng: hwrng registered
Feb 16 17:15:16 raspberrypi kernel: [    0.404230] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
Feb 16 17:15:16 raspberrypi kernel: [    0.405190] vc-sm: Videocore shared memory driver
Feb 16 17:15:16 raspberrypi kernel: [    0.429747] brd: module loaded
Feb 16 17:15:16 raspberrypi kernel: [    0.442201] loop: module loaded
Feb 16 17:15:16 raspberrypi kernel: [    0.442222] Loading iSCSI transport class v2.0-870.
Feb 16 17:15:16 raspberrypi kernel: [    0.443206] usbcore: registered new interface driver smsc95xx
Feb 16 17:15:16 raspberrypi kernel: [    0.443234] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Feb 16 17:15:16 raspberrypi kernel: [    0.671612] Core Release: 2.80a
Feb 16 17:15:16 raspberrypi kernel: [    0.671639] Setting default values for core params
Feb 16 17:15:16 raspberrypi kernel: [    0.671679] Finished setting default values for core params
Feb 16 17:15:16 raspberrypi kernel: [    0.872094] Using Buffer DMA mode
Feb 16 17:15:16 raspberrypi kernel: [    0.872107] Periodic Transfer Interrupt Enhancement - disabled
Feb 16 17:15:16 raspberrypi kernel: [    0.872111] Multiprocessor Interrupt Enhancement - disabled
Feb 16 17:15:16 raspberrypi kernel: [    0.872121] OTG VER PARAM: 0, OTG VER FLAG: 0
Feb 16 17:15:16 raspberrypi kernel: [    0.872214] Dedicated Tx FIFOs mode
Feb 16 17:15:16 raspberrypi kernel: [    0.872897] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xdb514000 dma = 0x5b514000 len=9024
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] FIQ FSM acceleration enabled for :
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] Non-periodic Split Transactions
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] Periodic Split Transactions
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] High-Speed Isochronous Endpoints
Feb 16 17:15:16 raspberrypi kernel: [    0.872925] Interrupt/Control Split Transaction hack enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.872936] dwc_otg: Microframe scheduler enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.873021] WARN::hcd_init_fiq:459: FIQ on core 0 at 0xc0451694
Feb 16 17:15:16 raspberrypi kernel: [    0.873034] WARN::hcd_init_fiq:460: FIQ ASM at 0xc0451970 length 36
Feb 16 17:15:16 raspberrypi kernel: [    0.873059] WARN::hcd_init_fiq:486: MPHI regs_base at 0xdc8a5000
Feb 16 17:15:16 raspberrypi kernel: [    0.873130] dwc_otg 20980000.usb: DWC OTG Controller
Feb 16 17:15:16 raspberrypi kernel: [    0.873190] dwc_otg 20980000.usb: new USB bus registered, assigned bus number 1
Feb 16 17:15:16 raspberrypi kernel: [    0.873309] dwc_otg 20980000.usb: irq 56, io mem 0x00000000
Feb 16 17:15:16 raspberrypi kernel: [    0.873365] Init: Port Power? op_state=1
Feb 16 17:15:16 raspberrypi kernel: [    0.873370] Init: Power Port (0)
Feb 16 17:15:16 raspberrypi kernel: [    0.873743] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 16 17:15:16 raspberrypi kernel: [    0.873759] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 16 17:15:16 raspberrypi kernel: [    0.873770] usb usb1: Product: DWC OTG Controller
Feb 16 17:15:16 raspberrypi kernel: [    0.873780] usb usb1: Manufacturer: Linux 4.9.59+ dwc_otg_hcd
Feb 16 17:15:16 raspberrypi kernel: [    0.873789] usb usb1: SerialNumber: 20980000.usb
Feb 16 17:15:16 raspberrypi kernel: [    0.874968] hub 1-0:1.0: USB hub found
Feb 16 17:15:16 raspberrypi kernel: [    0.875060] hub 1-0:1.0: 1 port detected
Feb 16 17:15:16 raspberrypi kernel: [    0.875951] dwc_otg: FIQ enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.875961] dwc_otg: NAK holdoff enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.875966] dwc_otg: FIQ split-transaction FSM enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.875987] Module dwc_common_port init
Feb 16 17:15:16 raspberrypi kernel: [    0.876474] usbcore: registered new interface driver usb-storage
Feb 16 17:15:16 raspberrypi kernel: [    0.876919] mousedev: PS/2 mouse device common for all mice
Feb 16 17:15:16 raspberrypi kernel: [    0.878551] bcm2835-wdt 20100000.watchdog: Broadcom BCM2835 watchdog timer
Feb 16 17:15:16 raspberrypi kernel: [    0.879058] bcm2835-cpufreq: min=700000 max=1000000
Feb 16 17:15:16 raspberrypi kernel: [    0.879672] sdhci: Secure Digital Host Controller Interface driver
Feb 16 17:15:16 raspberrypi kernel: [    0.879682] sdhci: Copyright(c) Pierre Ossman
Feb 16 17:15:16 raspberrypi kernel: [    0.880151] sdhost-bcm2835 20202000.sdhost: could not get clk, deferring probe
Feb 16 17:15:16 raspberrypi kernel: [    0.882694] mmc-bcm2835 20300000.mmc: could not get clk, deferring probe
Feb 16 17:15:16 raspberrypi kernel: [    0.882882] sdhci-pltfm: SDHCI platform and OF driver helper
Feb 16 17:15:16 raspberrypi kernel: [    0.883399] ledtrig-cpu: registered to indicate activity on CPUs
Feb 16 17:15:16 raspberrypi kernel: [    0.883544] hidraw: raw HID events driver (C) Jiri Kosina
Feb 16 17:15:16 raspberrypi kernel: [    0.883816] usbcore: registered new interface driver usbhid
Feb 16 17:15:16 raspberrypi kernel: [    0.883823] usbhid: USB HID core driver
Feb 16 17:15:16 raspberrypi kernel: [    0.885066] vchiq: vchiq_init_state: slot_zero = 0xdb580000, is_master = 0
Feb 16 17:15:16 raspberrypi kernel: [    0.886948] [vc_sm_connected_init]: start
Feb 16 17:15:16 raspberrypi kernel: [    0.896387] [vc_sm_connected_init]: end - returning 0
Feb 16 17:15:16 raspberrypi kernel: [    0.896881] Initializing XFRM netlink socket
Feb 16 17:15:16 raspberrypi kernel: [    0.896920] NET: Registered protocol family 17
Feb 16 17:15:16 raspberrypi kernel: [    0.897075] Key type dns_resolver registered
Feb 16 17:15:16 raspberrypi kernel: [    0.898929] registered taskstats version 1
Feb 16 17:15:16 raspberrypi kernel: [    0.908056] uart-pl011 20201000.serial: cts_event_workaround enabled
Feb 16 17:15:16 raspberrypi kernel: [    0.908202] 20201000.serial: ttyAMA0 at MMIO 0x20201000 (irq = 81, base_baud = 0) is a PL011 rev2
Feb 16 17:15:16 raspberrypi kernel: [    0.910628] sdhost: log_buf @ db513000 (5b513000)
Feb 16 17:15:16 raspberrypi kernel: [    0.982660] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Feb 16 17:15:16 raspberrypi kernel: [    0.985239] mmc-bcm2835 20300000.mmc: mmc_debug:0 mmc_debug2:0
Feb 16 17:15:16 raspberrypi kernel: [    0.985257] mmc-bcm2835 20300000.mmc: DMA channel allocated
Feb 16 17:15:16 raspberrypi kernel: [    1.015452] random: fast init done
Feb 16 17:15:16 raspberrypi kernel: [    1.060068] mmc0: host does not support reading read-only switch, assuming write-enable
Feb 16 17:15:16 raspberrypi kernel: [    1.062137] mmc0: new high speed SDHC card at address b368
Feb 16 17:15:16 raspberrypi kernel: [    1.062790] of_cfs_init
Feb 16 17:15:16 raspberrypi kernel: [    1.062929] of_cfs_init: OK
Feb 16 17:15:16 raspberrypi kernel: [    1.065555] mmcblk0: mmc0:b368 NCard 14.9 GiB
Feb 16 17:15:16 raspberrypi kernel: [    1.073347]  mmcblk0: p1 p2
Feb 16 17:15:16 raspberrypi kernel: [    1.086279] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    1.088281] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    1.090502] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Feb 16 17:15:16 raspberrypi kernel: [    1.090592] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Feb 16 17:15:16 raspberrypi kernel: [    1.091648] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    1.092134] devtmpfs: mounted
Feb 16 17:15:16 raspberrypi kernel: [    1.093454] Freeing unused kernel memory: 396K
Feb 16 17:15:16 raspberrypi kernel: [    1.093464] This architecture does not have kernel memory protection.
Feb 16 17:15:16 raspberrypi kernel: [    1.096110] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Feb 16 17:15:16 raspberrypi kernel: [    1.202486] mmc1: new high speed SDIO card at address 0001
Feb 16 17:15:16 raspberrypi kernel: [    1.796039] NET: Registered protocol family 10
Feb 16 17:15:16 raspberrypi kernel: [    1.830604] ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 16 17:15:16 raspberrypi kernel: [    3.451509] i2c /dev entries driver
Feb 16 17:15:16 raspberrypi kernel: [    4.989933] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Feb 16 17:15:16 raspberrypi kernel: [    7.894556] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
Feb 16 17:15:16 raspberrypi kernel: [    9.018106] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Feb 16 17:15:16 raspberrypi kernel: [    9.043294] usbcore: registered new interface driver brcmfmac
Feb 16 17:15:16 raspberrypi kernel: [    9.423162] brcmfmac: Firmware version = wl0: Aug  7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
Feb 16 17:15:16 raspberrypi kernel: [    9.424504] 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.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47
Feb 16 17:15:16 raspberrypi kernel: [   12.921552] uart-pl011 20201000.serial: no DMA platform data
Feb 16 17:15:17 raspberrypi kernel: [   15.041760] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS
Feb 16 17:15:18 raspberrypi kernel: [   16.123759] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 17:15:18 raspberrypi kernel: [   16.123776] brcmfmac: power management disabled
Feb 16 17:15:20 raspberrypi kernel: [   17.524843] Bluetooth: Core ver 2.22
Feb 16 17:15:20 raspberrypi kernel: [   17.524977] NET: Registered protocol family 31
Feb 16 17:15:20 raspberrypi kernel: [   17.524983] Bluetooth: HCI device and connection manager initialized
Feb 16 17:15:20 raspberrypi kernel: [   17.525004] Bluetooth: HCI socket layer initialized
Feb 16 17:15:20 raspberrypi kernel: [   17.525017] Bluetooth: L2CAP socket layer initialized
Feb 16 17:15:20 raspberrypi kernel: [   17.525056] Bluetooth: SCO socket layer initialized
Feb 16 17:15:20 raspberrypi kernel: [   17.550287] Bluetooth: HCI UART driver ver 2.3
Feb 16 17:15:20 raspberrypi kernel: [   17.550302] Bluetooth: HCI UART protocol H4 registered
Feb 16 17:15:20 raspberrypi kernel: [   17.550307] Bluetooth: HCI UART protocol Three-wire (H5) registered
Feb 16 17:15:20 raspberrypi kernel: [   17.550439] Bluetooth: HCI UART protocol Broadcom registered
Feb 16 17:15:20 raspberrypi kernel: [   18.211106] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 16 17:15:20 raspberrypi kernel: [   18.211118] Bluetooth: BNEP filters: protocol multicast
Feb 16 17:15:20 raspberrypi kernel: [   18.211140] Bluetooth: BNEP socket layer initialized
Feb 16 17:15:21 raspberrypi kernel: [   18.552707] Bluetooth: RFCOMM TTY layer initialized
Feb 16 17:15:21 raspberrypi kernel: [   18.552741] Bluetooth: RFCOMM socket layer initialized
Feb 16 17:15:21 raspberrypi kernel: [   18.552781] Bluetooth: RFCOMM ver 1.11
Feb 16 17:15:29 raspberrypi kernel: [   26.341881] fuse init (API version 7.26)
Feb 16 17:16:01 raspberrypi kernel: [   59.101694] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 16 17:21:10 raspberrypi kernel: [  340.342553] random: crng init done
Please let me know your observations compared to the log files provided with viewtopic.php?f=63&t=204882&start=25#p1272918...
Last edited by carriba on Fri Feb 16, 2018 5:03 pm, edited 1 time in total.

User avatar
carriba
Posts: 139
Joined: Tue Nov 18, 2014 5:55 pm
Contact: ICQ

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 5:02 pm

OK, looks like holding back the updates for firmware packages did do the job now, and the device is working just fine.

Now, here I need your help, which of the following packages

Code: Select all

firmware-atheros firmware-brcm80211 firmware-libertas firmware-misc-nonfree firmware-realtek
would be in charge of the Wifi chip of the Raspberry Pi Zero W device? I would then go ahead and just update this one (unless there's a dependency to another package) and see how the device is behaving after a firmware package update followed by a reboot...

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 6031
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 5:16 pm

Interesting. It would be the firmware-brcm80211 package.

Maybe leave a comment here:
viewtopic.php?t=203508

User avatar
HawaiianPi
Posts: 4734
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 6:00 pm

repo wrote:
Fri Feb 16, 2018 2:48 pm
i do not understand why you replied if have no problem and cant offer help and i do not believe you, forum is moderated so easy to ignore complaints. As op said tried new sd card, new installation and update broke things again so definitely updates to blame. I have Pi Zero W version 1.1 dated 2016 everything worked until decided to update.
Now even ethernet dongle does not work after update unless assigned static IP addrress
Your lack of belief does not change the fact that many of us do not have this problem, including myself. I have no trouble after updating either Raspbian Stretch Desktop or Lite. WiFi continues to work on my Pi-Zero-W after an update/upgrade or dist-upgrade. This problem is not common, and certainly not encountered by everyone. It seems to happen to a few individuals and no one has been able to figure out why yet, but we post because we want to help.

You can continue to bury your head in the sand and pretend this is all some big conspiracy, but the problem will not be solved that way, so I suggest you adjust your attitude and try to add something constructive to the thread.

One difference I did notice is that my Pi0W is dated 2017, but it's also a V1.1 so I don't know if the date has any significance.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

hippy
Posts: 6079
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 6:16 pm

carriba wrote:
Fri Feb 16, 2018 4:40 pm
Please let me know your observations compared to the log files provided with viewtopic.php?f=63&t=204882&start=25#p1272918...
I took a look but things are so different in the sequencing that it's impossible for me to arrive at any sensible conclusion. I guess it's systemd starting things in parallel which means there's no guarantee what starts before something else.

I'm eagerly waiting to see if upgrading the firmware breaks things or it remains working. I would agree it looks like it's a firmware issue for yourself, but I have no explanation why it works for myself and others.

MrEngman
Posts: 3854
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 16, 2018 7:11 pm

carriba wrote:
Fri Feb 16, 2018 5:02 pm
OK, looks like holding back the updates for firmware packages did do the job now, and the device is working just fine.

Now, here I need your help, which of the following packages

Code: Select all

firmware-atheros firmware-brcm80211 firmware-libertas firmware-misc-nonfree firmware-realtek
would be in charge of the Wifi chip of the Raspberry Pi Zero W device? I would then go ahead and just update this one (unless there's a dependency to another package) and see how the device is behaving after a firmware package update followed by a reboot...
It's firmware-brcm80211.

My Pi 0 W wifi refused to connect after I installed this package and rebooted. The driver was loaded when it booted but it would not connect to my network. I had stuff in the log files about ipv6 similar to what you've shown. I then disabled ipv6 and after rebooting it I was able to get it to connect.

Worked fine when I first set up the SD card with the 2017-11-29-raspbian-stretch-lite image. After doing update/upgrade which installed a load of other packages but without installing the firmware-brcm80211 package and it was still OK. Also did an rpi-update and it continued to work.

Only after installing the wifi firmware update, firmware-brcm80211, the problem occurred.
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

repo
Posts: 6
Joined: Fri Feb 16, 2018 9:02 am

Re: No Wifi connection to Pi Zero W after Raspbian update

Sun Feb 18, 2018 4:07 pm

in my case it was neither blocking ipv6 nor skipping firmware update, only after adding scan_ssid=1 and
key_mgmt=WPA-PSK to network in wpa_supplicant.conf my pi started to work.
thanks for no help, somewhat confused whether maybe complaining on forum helped.

pcmanbob
Posts: 7073
Joined: Fri May 31, 2013 9:28 pm
Location: Mansfield UK

Re: No Wifi connection to Pi Zero W after Raspbian update

Sun Feb 18, 2018 4:50 pm

repo wrote:
Sun Feb 18, 2018 4:07 pm
in my case it was neither blocking ipv6 nor skipping firmware update, only after adding scan_ssid=1 and
key_mgmt=WPA-PSK to network in wpa_supplicant.conf my pi started to work.
thanks for no help, somewhat confused whether maybe complaining on forum helped.
May be if you had started your own thread stating your problem with the relevant details you would have got the help you were expecting, just posting on someone else thread with comments like this " cant these people read?" as your very first post will not encourage people to help you.
We want information… information… information........................no information no help
The use of crystal balls & mind reading are not supported

User avatar
HawaiianPi
Posts: 4734
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: No Wifi connection to Pi Zero W after Raspbian update

Mon Feb 19, 2018 11:27 am

repo wrote:
Sun Feb 18, 2018 4:07 pm
in my case it was neither blocking ipv6 nor skipping firmware update, only after adding scan_ssid=1 and
key_mgmt=WPA-PSK to network in wpa_supplicant.conf my pi started to work.
If your wpa_supplicant.conf file did not have key_mgmt=WPA-PSK, then it was not created properly, and if you required scan_ssid=1 then you have your SSID hidden and caused your own problems by believing that nonsense of hiding your SSID for security, when in reality hiding your SSID actually makes your network LESS secure and creates connection headaches.

You also didn't provide any useful information in your post at all, so I don't know how you expected us to help. We are computer enthusiasts, not psychics. If you want help then you need to provide details about your setup and problems.
...thanks for no help, somewhat confused whether maybe complaining on forum helped.
Posting in someone else's thread just to accuse us of lying is not the way to get help here or anywhere else (neither is being a whiny little *****).
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

User avatar
carriba
Posts: 139
Joined: Tue Nov 18, 2014 5:55 pm
Contact: ICQ

Re: No Wifi connection to Pi Zero W after Raspbian update

Mon Feb 19, 2018 1:17 pm

MrEngman wrote:
Fri Feb 16, 2018 7:11 pm
carriba wrote:
Fri Feb 16, 2018 5:02 pm
OK, looks like holding back the updates for firmware packages did do the job now, and the device is working just fine.
Now, here I need your help, which of the following packages

Code: Select all

firmware-atheros firmware-brcm80211 firmware-libertas firmware-misc-nonfree firmware-realtek
would be in charge of the Wifi chip of the Raspberry Pi Zero W device? I would then go ahead and just update this one (unless there's a dependency to another package) and see how the device is behaving after a firmware package update followed by a reboot...
It's firmware-brcm80211.
My Pi 0 W wifi refused to connect after I installed this package and rebooted. The driver was loaded when it booted but it would not connect to my network. I had stuff in the log files about ipv6 similar to what you've shown. I then disabled ipv6 and after rebooting it I was able to get it to connect.
[...]
Only after installing the wifi firmware update, firmware-brcm80211, the problem occurred.
Thank you for the pointer. I updated now all the firmware packages except “firmware-brcm80211”, and after a reboot everything was running fine. Thus, I can conclude that all other firmware packages seem not cause any problems.

Since I already made the experience that Wifi access to my AP does not work with IPv6 enabled, I disabled IPv6 as described in my post viewtopic.php?f=63&t=204882&start=25#p1271196. I rebooted the Raspberry Pi Zero W device, and everything is working fine despite an error message “Process '/sbin/crda' failed with exit code 249” as outlined with the following entries in the “/var/log/syslog” file:

Code: Select all

Feb 18 16:26:29 raspberrypi systemd[1]: Started dhcpcd on all interfaces.
Feb 18 16:26:29 raspberrypi dhcpcd[268]: no valid interfaces found
Feb 18 16:26:29 raspberrypi dhcpcd[268]: forked to background, child pid 279
[...]
Feb 18 16:26:31 raspberrypi dhcpcd-run-hooks[344]: wlan0: starting wpa_supplicant
Feb 18 16:26:31 raspberrypi systemd-udevd[129]: Process '/sbin/crda' failed with exit code 249.
Feb 18 16:26:31 raspberrypi systemd[1]: Started OpenBSD Secure Shell server.
Feb 18 16:26:31 raspberrypi kernel: [   16.611414] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 18 16:26:31 raspberrypi kernel: [   16.611430] brcmfmac: power management disabled
[...]
Feb 18 16:26:33 raspberrypi systemd[1]: Reached target Multi-User System.
Feb 18 16:26:33 raspberrypi dhcpcd[279]: DUID 00:01:00:01:21:b0:de:83:b8:27:eb:cb:76:07
Feb 18 16:26:33 raspberrypi dhcpcd[279]: wlan0: IAID eb:cb:76:07
Feb 18 16:26:33 raspberrypi dhcpcd[279]: wlan0: adding address fe80::a6d3:3185:7be6:d0c4
Feb 18 16:26:33 raspberrypi dhcpcd[279]: wlan0: carrier lost
[...]
Feb 18 16:26:33 raspberrypi systemd[1]: Starting Hostname Service...
Feb 18 16:26:33 raspberrypi dhcpcd[279]: wlan0: deleting address fe80::a6d3:3185:7be6:d0c4
[...]
Feb 18 16:27:15 raspberrypi kernel: [   60.051964] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 18 16:27:16 raspberrypi dhcpcd[279]: wlan0: carrier acquired
Feb 18 16:27:16 raspberrypi dhcpcd[279]: wlan0: IAID eb:cb:76:07
Feb 18 16:27:16 raspberrypi dhcpcd[279]: wlan0: adding address fe80::f09:b82c:7fdd:6f12
Feb 18 16:27:16 raspberrypi dhcpcd[279]: wlan0: rebinding lease of 192.168.0.31
Feb 18 16:27:16 raspberrypi dhcpcd[279]: wlan0: probing address 192.168.0.31/24
Feb 18 16:27:16 raspberrypi dhcpcd[279]: wlan0: soliciting an IPv6 router
Feb 18 16:27:17 raspberrypi avahi-daemon[261]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::f09:b82c:7fdd:6f12.
Feb 18 16:27:17 raspberrypi avahi-daemon[261]: New relevant interface wlan0.IPv6 for mDNS.
Feb 18 16:27:17 raspberrypi avahi-daemon[261]: Registering new address record for fe80::f09:b82c:7fdd:6f12 on wlan0.*.
Feb 18 16:27:21 raspberrypi dhcpcd[279]: wlan0: leased 192.168.0.31 for 864000 seconds
Feb 18 16:27:21 raspberrypi avahi-daemon[261]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.31.
Feb 18 16:27:21 raspberrypi dhcpcd[279]: wlan0: adding route to 192.168.0.0/24
Feb 18 16:27:21 raspberrypi dhcpcd[279]: wlan0: adding default route via 192.168.0.254
Feb 18 16:27:21 raspberrypi avahi-daemon[261]: New relevant interface wlan0.IPv4 for mDNS.
Feb 18 16:27:21 raspberrypi avahi-daemon[261]: Registering new address record for 192.168.0.31 on wlan0.IPv4.
Feb 18 16:27:51 raspberrypi systemd[417]: Time has been changed
Feb 18 16:27:51 raspberrypi systemd[1]: Time has been changed
Feb 18 16:27:51 raspberrypi systemd-timesyncd[201]: Synchronized to time server 178.79.162.34:123 (0.europe.pool.ntp.org).
Feb 18 16:27:54 raspberrypi dhcpcd[279]: wlan0: no IPv6 Routers available
Feb 18 16:32:37 raspberrypi kernel: [  358.161624] random: crng init done
I then updated the last remaining firmware package “firmware-brcm80211” as depicted with:

Code: Select all

(Reading database ... 124220 files and directories currently installed.)
Preparing to unpack .../firmware-brcm80211_1%3a20161130-3+rpt1_all.deb ...
Unpacking firmware-brcm80211 (1:20161130-3+rpt1) over (1:20161130-3+rpi2) ...
Setting up firmware-brcm80211 (1:20161130-3+rpt1) ...
Instead of a reboot, I simply fired the command “sudo systemctl restart dhcpcd”, which causes to abort my current SSH session (which is normal), however could connect again after a short while.

After a while, I got disconnected from the new SSH session for some unknown reason, however could connect again. The SSH did not last long enough and I got disconnected again (weird!), and this scenario did repeat a couple of times as you can see depicted from the new established user sessions (output of the “who” command):

Code: Select all

pi       tty1         2018-02-18 16:55
pi       tty7         2018-02-18 16:55 (:0)
pi       pts/0        2018-02-18 17:06 (192.168.0.32)
pi       pts/1        2018-02-18 17:13 (192.168.0.32)
pi       pts/2        2018-02-18 17:14 (192.168.0.32)
pi       pts/3        2018-02-18 17:20 (192.168.0.32)
pi       pts/4        2018-02-18 17:22 (192.168.0.32)
pi       pts/5        2018-02-18 17:24 (192.168.0.32)
pi       pts/6        2018-02-18 17:25 (192.168.0.32)
Checking further the “/var/log/syslog” file, I can only find the following entries:

Code: Select all

Feb 18 16:54:54 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...
Feb 18 16:54:54 raspberrypi dhcpcd[256]: dev: loaded udev
Feb 18 16:54:54 raspberrypi dhcpcd[256]: no valid interfaces found
Feb 18 16:54:54 raspberrypi systemd[1]: Started dhcpcd on all interfaces.
Feb 18 16:54:56 raspberrypi dhcpcd-run-hooks[338]: wlan0: starting wpa_supplicant
Feb 18 16:54:58 raspberrypi dhcpcd[266]: wlan0: waiting for carrier
Feb 18 16:54:58 raspberrypi dhcpcd[266]: wlan0: carrier acquired
Feb 18 16:54:58 raspberrypi dhcpcd[266]: wlan0: carrier lost
Feb 18 16:55:40 raspberrypi dhcpcd[266]: wlan0: carrier acquired
Feb 18 16:55:41 raspberrypi dhcpcd[266]: wlan0: rebinding lease of 192.168.0.31
Feb 18 16:55:41 raspberrypi dhcpcd[266]: wlan0: probing address 192.168.0.31/24
Feb 18 16:55:46 raspberrypi dhcpcd[266]: wlan0: leased 192.168.0.31 for 864000 seconds
Feb 18 16:55:46 raspberrypi dhcpcd[266]: wlan0: adding route to 192.168.0.0/24
Feb 18 16:55:46 raspberrypi dhcpcd[266]: wlan0: adding default route via 192.168.0.254
Feb 18 17:11:57 raspberrypi systemd[1]: Stopping dhcpcd on all interfaces...
Feb 18 17:11:57 raspberrypi dhcpcd[859]: sending signal TERM to pid 266
Feb 18 17:11:57 raspberrypi dhcpcd[266]: received SIGTERM, stopping
Feb 18 17:11:57 raspberrypi dhcpcd[266]: wlan0: removing interface
Feb 18 17:11:57 raspberrypi dhcpcd[859]: waiting for pid 266 to exit
Feb 18 17:11:57 raspberrypi dhcpcd[266]: dhcpcd exited
Feb 18 17:11:57 raspberrypi dhcpcd[859]: sending signal TERM to pid 266
Feb 18 17:11:57 raspberrypi dhcpcd[859]: waiting for pid 266 to exit
Feb 18 17:11:58 raspberrypi systemd[1]: Stopped dhcpcd on all interfaces.
Feb 18 17:11:58 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...
Feb 18 17:11:58 raspberrypi dhcpcd[867]: dev: loaded udev
Feb 18 17:11:58 raspberrypi dhcpcd[867]: forked to background, child pid 869
Feb 18 17:11:58 raspberrypi systemd[1]: Started dhcpcd on all interfaces.
Feb 18 17:11:58 raspberrypi dhcpcd-run-hooks[880]: wlan0: starting wpa_supplicant
Feb 18 17:11:59 raspberrypi dhcpcd[869]: wlan0: waiting for carrier
Feb 18 17:13:08 raspberrypi dhcpcd[869]: wlan0: carrier acquired
Feb 18 17:13:09 raspberrypi dhcpcd[869]: wlan0: rebinding lease of 192.168.0.31
Feb 18 17:13:09 raspberrypi dhcpcd[869]: wlan0: leased 192.168.0.31 for 864000 seconds
Feb 18 17:13:09 raspberrypi dhcpcd[869]: wlan0: adding route to 192.168.0.0/24
Feb 18 17:13:09 raspberrypi dhcpcd[869]: wlan0: adding default route via 192.168.0.254
The log entries do not provide sufficient hint on what is really going on there after having restarted the “dhcpcd” daemon.

Thus, every SSH session I’m initiating to the device gets cut after a while, and the times loosing a connection even increase up to the point I can no longer connect to the device anymore forcing me to unplug the PSU from the device.

Plugging in the PSU, no access to the device at all, and same situation as described in previous posts.
Last edited by carriba on Mon Feb 19, 2018 4:47 pm, edited 1 time in total.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23876
Joined: Sat Jul 30, 2011 7:41 pm

Re: No Wifi connection to Pi Zero W after Raspbian update

Mon Feb 19, 2018 3:56 pm

Hmm, this is an odd one.

We've not seen any issues with the new wireless firmware in our testing, and the majority of people seem to be running ok, so it's going to be difficult to track this down.

So far it seems that hidden networks and/or IPv6 may be partly responsible. Anyone have any other clues?
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
“I think it’s wrong that only one company makes the game Monopoly.” – Steven Wright

MrEngman
Posts: 3854
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: No Wifi connection to Pi Zero W after Raspbian update

Mon Feb 19, 2018 4:22 pm

My Pi 0 W worked fine with the 2017-11-29-raspbian-stretch-lite image using the older firmware.

However, after doing an update/upgrade that installed the new firmware amongst other items it refused to connect to my network. It appeared to want to use ipv6 but could not get a connection and ended up with a local ipv6 address.

To check the wifi not working I starting with the 2017-11-29-raspbian-stretch-lite image again and did update/upgrade but did not update the firmware to see why the wifi failed and the Pi 0 W wifi worked OK even with ipv6 enabled. So it appeared the issue was with the new firmware and not anything else that was updated.

After updating the firmware the Pi 0 W wifi refused to work so I blacklisted ipv6 and it is now working. It's been up for about 9 days, mostly idle, but still connected via SSH. I blacklisted ipv6 by adding the line blacklist ipv6 to the beginning of file /etc/modprobe.d/ipv6.conf.

Currently The Pi 0 W is running kernel 4.14.18.
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

kayel
Posts: 109
Joined: Sun May 13, 2012 4:45 am
Location: France

Re: No Wifi connection to Pi Zero W after Raspbian update

Mon Feb 19, 2018 5:47 pm

My wifi dongle stopped working after an update/upgrade I was forced to do to install dnsmasq and hostapd on a pi2.
I got fed up of trying to get it to work and installed ubuntu mate.
Now the wifi works but the names of wlan0 and eth0 have changed to wlxHWaddr and enxHWaddr respectively. On my laptop running Debian Stretch they've changed to enp4s0 and wlp3s0 respectively. On a laptop running Arch linux eth0 has become enlsp0.

I don't know if this has anything to do with carriba's problem, but what's goin' on?

User avatar
carriba
Posts: 139
Joined: Tue Nov 18, 2014 5:55 pm
Contact: ICQ

Re: No Wifi connection to Pi Zero W after Raspbian update

Wed Feb 21, 2018 1:12 pm

jamesh wrote:
Mon Feb 19, 2018 3:56 pm
Hmm, this is an odd one.

We've not seen any issues with the new wireless firmware in our testing, and the majority of people seem to be running ok, so it's going to be difficult to track this down.

So far it seems that hidden networks and/or IPv6 may be partly responsible. Anyone have any other clues?
No further clues from my side that can complement the observations already made in previous posts. It happens to me with and without an IPv6 setup, and am able to reproduce the described with different RPi 0 W devices and different microSD cards.

I'm wondering, what could be the difference between the new "firmware-brcm80211 (1:20161130-3+rpt1)" compared to the previuos installed "firmware-brcm80211 (1:20161130-3+rpi2)".
ShiftPlusOne wrote:
Fri Feb 16, 2018 5:16 pm
Interesting. It would be the firmware-brcm80211 package.
Maybe leave a comment here:
viewtopic.php?t=203508
I will also have a look into the new firmware offering...

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 6031
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: No Wifi connection to Pi Zero W after Raspbian update

Wed Feb 21, 2018 1:18 pm

carriba wrote:
Wed Feb 21, 2018 1:12 pm
I will also have a look into the new firmware offering...
That is the firmware that was added in the +rpt1 version, (since no issues were reported in that thread).

Could you provide some information about your access point? Maybe it's a compatibility issue with that specific hardware or configuration.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23876
Joined: Sat Jul 30, 2011 7:41 pm

Re: No Wifi connection to Pi Zero W after Raspbian update

Wed Feb 21, 2018 2:28 pm

carriba wrote:
Wed Feb 21, 2018 1:12 pm
jamesh wrote:
Mon Feb 19, 2018 3:56 pm
Hmm, this is an odd one.

We've not seen any issues with the new wireless firmware in our testing, and the majority of people seem to be running ok, so it's going to be difficult to track this down.

So far it seems that hidden networks and/or IPv6 may be partly responsible. Anyone have any other clues?
No further clues from my side that can complement the observations already made in previous posts. It happens to me with and without an IPv6 setup, and am able to reproduce the described with different RPi 0 W devices and different microSD cards.

I'm wondering, what could be the difference between the new "firmware-brcm80211 (1:20161130-3+rpt1)" compared to the previuos installed "firmware-brcm80211 (1:20161130-3+rpi2)".
ShiftPlusOne wrote:
Fri Feb 16, 2018 5:16 pm
Interesting. It would be the firmware-brcm80211 package.
Maybe leave a comment here:
viewtopic.php?t=203508
I will also have a look into the new firmware offering...
Just as a FYI, Cypress provide us with the firmware as a binary blob, and because we have moved source tree there from a dedicated Pi one to their master, we are not entirely sure what has changed. The firmware is much more recent that our previous version, and should be much easier to support. It has certainly been beneficial in some areas, but it does appear that others may have suffered. So far the number of people affected does seem small fortunately, but we will continue to look at it.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
“I think it’s wrong that only one company makes the game Monopoly.” – Steven Wright

User avatar
carriba
Posts: 139
Joined: Tue Nov 18, 2014 5:55 pm
Contact: ICQ

Re: No Wifi connection to Pi Zero W after Raspbian update

Fri Feb 23, 2018 11:07 am

Apologises for being persistent here, but apart from observing these annoying symptoms, I see the origin of the problem not being identifed yet and the root cause not being determined either.

I have carried on my troubleshooting activities and have followed the advice of another post to connect straight to the console port of my Raspberry Pi Zero W device.

Thus, I went ahead and flashed a brand new microSD card with the latest Raspbian Stretch with Desktop image file of November 2017 (the "full" OS) using the usual Win32 Disk Imager tool that worked fine and reliable to me many years.

In the top level directory of the SD card, I have created an empty "ssh" file (to allow access to the device via network) and have edited the usual "wpa_supplicant.conf" text file with the following similar contents:

Code: Select all

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=GB

network={
	ssid="MyWifiNetworkSSID"
	psk="password"
	key_mgmt=WPA-PSK
}
Nothing else has changed after flashing the SD card, all other files remained untouched!

Have ejected SD card from the card reader of my PC and gently slided it into the card reader of the RPi 0 W device. Plugged in the PSU, and the Raspberry Pi Zero W device just booted up fine, expanded the disk, rebooted itself, and could connect to the device via WLAN. Wireless access works fine, wether the SSID is being advertised or not (hidden network).

I followed the advice of another post to connect to the device straight using its console port. Thus, I went ahead and fired sudo raspi-config, and have activated serial access via the device's GPIO pins and have enabled console access under the menu options "5 Interfacing Options -> P6 Serial -> Enable" and made sure that the line "enable_uart=1" has been addedd to the /boot/config.txt file.

I hooked up a RS232 to TTL converter board to the RPi 0 W device according to the Serial GPIO Pinout for Raspberry Pi Zero and connected the other end with a DB9 serial connector to my PC.

I have updated the Putty program to its latest release that allows my using the COM1: serial port of my PC and thus connect straight to the console port of the Raspberry Pi Zero W device. And see there, console access works!

Hooked up on the console port, I can log into the Raspebrry Pi 0 W device on its console after powering up and can see that WLAN access is working fine with any of my Wifi APs independented of the SSID being advertised or not (the later representing the case of a "hidden network" setup). I checked WLAN access with the command ifconfig -a to make sure that an IP address has been asigned, and also connected to the device with Putty using SSH to make sure that I can indeed access the device through WLAN.

On the RPi 0 W console, I fired the following commands:

Code: Select all

echo "firmware-brcm80211 hold" | sudo dpkg --set-selections
sudo apt-get update ; sudo apt-get -y upgrade
All OS packages got updated with the exception of the "firmware-brcm80211" package. The "firmware-brcm80211" stayed on its original version as provided with the latest Raspbian Stretch with Desktop image file of November 2017.

I checked again WLAN access with the command ifconfig -a to make sure that an IP address has been asigned, and also connected to the device with Putty using SSH. Thus, no problems to access the RPi 0 W device as long as the "firmware-brcm80211" stayed on its original version and independent of the Wifi AP setup (hidden or no hidden SSID).

I moved further and fired on the console port the following commands:

Code: Select all

echo "firmware-brcm80211 install" | sudo dpkg --set-selections
sudo apt-get -y upgrade
The Wifi AP has been setup to advertise its SSID, and from the console I can fire ifconfig -a showing that RPi 0 W is hooked up on the WLAN:

Code: Select all

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.0.31  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::82b:ae5c:6bcd:c023  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:cb:76:07  txqueuelen 1000  (Ethernet)
        RX packets 169  bytes 27908 (27.2 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 110  bytes 12070 (11.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
And I can connect to the device with Putty using SSH via WLAN.

Thus, after having updated the "firmware-brcm80211 (1:20161130-3+rpi2)" that comes with the original November 2017 image file to the latest "firmware-brcm80211 (1:20161130-3+rpt1)" version as described above, WLAN access to the RPi 0 W works fine with a Wifi AP setup to advertise its SSID.

I shutdown the RPi 0 W device and unplug the PSU.

Then, I change the Wifi AP setup to "hide" the SSID advertisement and have recycled the Wifi AP device. I made sure that I can connect to the "hidden network" with other devices, and this works fine!

I powered up the RPi 0 W device, and on the console port I can observe the usual startup process messages being displayed. I quickly log in to the console port, and fired the command ifconfig -a showing that the RPi 0 W device is not hooked up on the WLAN:

Code: Select all

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:cb:76:07  txqueuelen 1000  (Ethernet)
        RX packets 169  bytes 27908 (27.2 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 110  bytes 12070 (11.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Note above output: IP details are missing for the wlan0 interface!

And within the next 3 to 5 seconds I'm getting the following output on the console port of the RPi 0 W device:

Code: Select all

[  671.636857] ------------[ cut here ]------------
[  671.641578] kernel BUG at mm/vmalloc.c:473!
[  671.645828] Internal error: Oops - BUG: 0 [#1] ARM
[  671.650690] Modules linked in: fuse rfcomm cmac bnep hci_uart btbcm bluetooth brcmfmac brcmutil cfg80211 rfkill bcm2835_gpiomem fixed uio_pdrv_genirq uio i2c_dev ip_tables x_tables ipv6
[  671.667564] CPU: 0 PID: 741 Comm: kworker/u2:2 Not tainted 4.9.59+ #1047
[  671.674366] Hardware name: BCM2835
[  671.678222] Workqueue: brcmf_wq/mmc1:0001:1 brcmf_sdio_dataworker [brcmfmac]
[  671.685391] task: d876df60 task.stack: d9154000
[  671.690015] PC is at alloc_vmap_area+0x360/0x390
[  671.694709] LR is at __insert_vmap_area+0x84/0xd8
[  671.699489] pc : [<c01243f0>]    lr : [<c012403c>]    psr: a8050013
[  671.699489] sp : d9155d00  ip : d9155ce8  fp : d9155d5c
[  671.711140] r10: ffffffff  r9 : ff800000  r8 : c08c2898
[  671.716443] r7 : c09a2cec  r6 : dc800000  r5 : 00000001  r4 : d84f9240
[  671.723068] r3 : 00000000  r2 : dc800000  r1 : d84f9258  r0 : 00000000
[  671.729694] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[  671.736937] Control: 00c5387d  Table: 185dc008  DAC: 00000055
[  671.742771] Process kworker/u2:2 (pid: 741, stack limit = 0xd9154188)
[  671.749309] Stack: (0xd9155d00 to 0xd9156000)
[  671.753740] 5d00: 00000200 00000000 dc800000 d84f9240 00400000 00000001 dc804000 00000000
[  671.762048] 5d20: 00000001 dc800000 c0133d8c c0133de8 00000040 00004000 00000022 024080c2
[  671.770355] 5d40: 00000001 dc800000 d90c80e0 da69fe28 d9155d8c d9155d60 c01244cc c012409c
[  671.778664] 5d60: ffffffff 024080c2 00002220 ffffffff dac02800 ffffffff da69fe28 024080c2
[  671.786972] 5d80: d9155dcc d9155d90 c0125478 c012442c ff800000 ffffffff 024080c2 bf2539f0
[  671.795280] 5da0: c04d5e28 bf2539f0 ffffffff dac02800 bf269c44 da69fe28 0000000c da69fe28
[  671.803588] 5dc0: d9155dfc d9155dd0 c0125668 c012541c 024080c2 0000024f 00000000 ffffffff
[  671.811896] 5de0: bf2539f0 00000000 00000020 da6ef7e0 d9155e14 d9155e00 c0125700 c0125620
[  671.820204] 5e00: ffffffff bf2539f0 d9155ef4 d9155e18 bf2539f0 c01256d0 d9155e44 d9155e28
[  671.828511] 5e20: c004bc68 c00401a0 da46e340 da408da0 da69fd32 00000000 00000032 00000014
[  671.836818] 5e40: da69fc0c c00bf4b4 d876df60 00000032 00000040 da69fc00 d9155e7c d876df60
[  671.845125] 5e60: 00000000 da69fd50 0000009c 00000000 00000000 d9155e80 c05d1910 c0045f4c
[  671.853433] 5e80: d9155ea4 d9155e90 c0038b2c 68050013 00000000 00000000 d9155f2c c0035960
[  671.861740] 5ea0: dac02800 da5d7b00 d9155ed4 d9155eb8 c0035960 c0035868 00000000 da5d7b00
[  671.870047] 5ec0: da5d7b00 c0038500 d9155ef4 da69fe28 cd81cae0 dac02800 00000000 00000000
[  671.878353] 5ee0: da5d7b00 cd81cae0 d9155f2c d9155ef8 c0038b3c bf25196c c08b54c0 00000088
[  671.886661] 5f00: dac02800 dac02800 cd81caf8 dac02814 c08b54c0 00000088 dac02800 cd81cae0
[  671.894968] 5f20: d9155f64 d9155f30 c0038df4 c0038a2c c0038db8 00000000 00000000 00000000
[  671.903275] 5f40: d92ba620 cd81cae0 c0038db8 00000000 00000000 00000000 d9155fac d9155f68
[  671.911582] 5f60: c003e954 c0038dc4 d9154000 00000000 d9155f94 cd81cae0 00000000 d9155f7c
[  671.919890] 5f80: d9155f7c 00000000 d9155f88 d9155f88 d92ba620 c003e85c 00000000 00000000
[  671.928196] 5fa0: 00000000 d9155fb0 c000fec8 c003e868 00000000 00000000 00000000 00000000
[  671.936502] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  671.944808] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 000027ff 00002800
[  671.953137] [<c01243f0>] (alloc_vmap_area) from [<c01244cc>] (__get_vm_area_node+0xac/0x144)
[  671.961722] [<c01244cc>] (__get_vm_area_node) from [<c0125478>] (__vmalloc_node_range+0x68/0x204)
[  671.970743] [<c0125478>] (__vmalloc_node_range) from [<c0125668>] (__vmalloc_node+0x54/0x64)
[  671.979320] [<c0125668>] (__vmalloc_node) from [<c0125700>] (vzalloc+0x3c/0x4c)
[  671.987016] [<c0125700>] (vzalloc) from [<bf2539f0>] (brcmf_sdio_dataworker+0x2090/0x2358 [brcmfmac])
[  671.996656] [<bf2539f0>] (brcmf_sdio_dataworker [brcmfmac]) from [<c0038b3c>] (process_one_work+0x11c/0x398)
[  672.006653] [<c0038b3c>] (process_one_work) from [<c0038df4>] (worker_thread+0x3c/0x508)
[  672.014886] [<c0038df4>] (worker_thread) from [<c003e954>] (kthread+0xf8/0x114)
[  672.022330] [<c003e954>] (kthread) from [<c000fec8>] (ret_from_fork+0x14/0x2c)
[  672.029671] Code: 251b0050 2affffe1 e7f001f2 e7f001f2 (e7f001f2) 
[  672.035864] ---[ end trace d9489205bcc517a5 ]---
I haven't finished copying & pasting above output from the console into a text file on my PC, and just meanwhile saving the text file, the console port gets flooded with more message like the ones above, and suddenly I have a Blue Screen of Death on my PC :-(

I have recycled my PC and with the Putty application connected again to the console port of the RPi 0 W device, however no response or any further output on the console; the device's LED stayed lit green all time, no activity. Even with a Wifi radar application on my PC, I could not locate the RPi 0 W device on teh WLAN, meaning the device is not connected to the WLAN at all.

I removed the PSU from the RPi 0 W device, altered the setup of the Wifi AP device to advertise its SSID, powered up again RPi 0 W device, and after a while, could connect to the RPi 0 W device through its console port and etsbalish a SSH session through WLAN.

Please let me know your observations on the above...

Return to “General discussion”