pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

wlan0 disappears after Stretch 2017-09-07

Sat Nov 25, 2017 11:28 am

Hi mates,

Of what I am trying to accomplish is to setup my Pi3 as a router by following this wonderful tutorial: https://blog.adafruit.com/2016/09/13/up ... pberry_pi/

In fact, 6 months ago I did set one up with Jessie and it worked beautifully. Unfortunately my Samsung Evo SD card recently experienced some difficulty every single time I tried to run apt-get update && apt-get upgrade -y. It crashed every single time and left the system unable to get any update. Fsck -vf reported it is okay but at the end of the day, evidently speaking, it is a useless piece of junk. Nothing can be installed on it.

I decided to upgrade my headless pi to Stretch from the image of 2017-09-07 and run on a usb stick. Things worked out fine especially with eth0. Yesterday, I tried to get the wlan0 up and set it to static so that I can get on with the tutorial. Very unexpectedly, for more than a day nothing can be achieved. I have goolged and tried out different guides like these and many more:

1- viewtopic.php?t=191061
2- https://raspberrypi.stackexchange.com/q ... ress#37921

In the end, nothing seems to work at this moment. Here is how things look currently. Some other settings would cause the pi not to boot at all. Being on headless it was a pain in the rear end every single time it hangs.

Below is my ifconfig -a:
Image

Below is my /etc/network/interfaces:
Image

Below is my /etc/dhcpcd.conf:
Image

Below is my /etc/wpa_supplicant/wpa_supplicant.conf:
Image

What in the world is going with Stretch. Could anyone beam me a light of hope to this ridiculous update. Thank you very much in advance.

DirkS
Posts: 8822
Joined: Tue Jun 19, 2012 9:46 pm
Location: Essex, UK

Re: wlan0 disappears after Stretch 2017-09-07

Sat Nov 25, 2017 12:27 pm

Below is my /etc/network/interfaces:
Remove the stuff you added to this file and reboot

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sat Nov 25, 2017 12:52 pm

Originally it was empty with no wlan0 when run ifconfig.

User avatar
ksharindam
Posts: 70
Joined: Sat Jan 09, 2016 4:16 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 3:57 am

Is the wifi driver/firmware installed?
show me the output of lsusb command after inserting wifi dongle.
And also show the output of the command ....

Code: Select all

dpkg -l | grep firmware

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 5:24 am

Thank ksharindam for your suggestion. I use mostly windows so have no clue of how to get the driver or stuffs like that out of linux. Everyday is a learning day for me here.

Anyway, here is the outputs that you requested:

Image

BTW, I intended to use the built-in Wifi that comes with the Pi3. I do have the TP-Link722 usb dongle but that is for later because I am still struggling with the basic stuffs here. Do I need to do anything special if I decided to use the usb dongle instead of the built-in Wifi?

I am not sure but it appears like the drivers are installed based on the outputs. If it is not installed how do you install it? Just curious if later on I run into a situation like this again.

Thank you very much for your help.

User avatar
ksharindam
Posts: 70
Joined: Sat Jan 09, 2016 4:16 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 9:11 am

I use TP-Link 725N and it works fine. required firmware is firmware-realtek which is already installed in your system.
your wpa-suppliccant.conf file is also error free. So wifi should work in your Pi.

But the wifi dongle is not shown in the output of lsusb command.
Have you inserted the wifi dongle before running lsusb command?
lsusb command should list all the devices connected via usb.

If your Pi is Pi3, then wlan0 should be always up (unless you have disabled in /boot/config.txt)

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 9:31 am

I am running Stretch of my usb which is SanDisk on the list. This is the only usb device plugged into my pi3.

I am not using any usb wifi. I am only looking for solution to make the pi's internal wifi work ( the built-in wifi). Are you sure that the internal wifi's driver is the firmware-realtek?

For some reasons, the internal wlan0 is not showing up at all.

It is very frustrating. Thanks anyway.

User avatar
ksharindam
Posts: 70
Joined: Sat Jan 09, 2016 4:16 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 1:18 pm

The firmware for internal wifi is firmware-brcm80211 which is also installed.
Its very weird that wifi is not working. I want do a final try... paste the contents of /boot/config.txt

If there is no problem in config.txt then you have to reinstall the image. wifi works in a fresh installation.

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 3:43 pm

You are right this is kinda weird. I just put the same Stretch image onto a corrupted SD card and it was able to boot up with the wlan0 flawlessly out of the box from the same Pi3.

I even attempted to set dhcpcd.conf with these:

interface eth0
static ip_address=192.168.1.190/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1 8.8.8.8

interface wlan0
static ip_address=192.168.1.191/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1 8.8.8.8

and it still working fine with wlan0 having the correct ip address as above.

Too bad, I don't have much time so I am re-flashing the usb stick as of this moment writing this to you. Sorry for not being able to get you the /boot/config.txt. I did check it earlier and it looks normal. I read somewhere that if you put this stupid thing "dtoverlay=pi3-disable-wifi" in the /boot/config.txt it would disable your internal wifi. It was not in there when I checked.

There gotta be some crazy thing going wrong. Unfortunately I am not good enough to check to find out of what it is. Someone suggested reading the output of dmesg but that thing is like a bible to me. No idea what to look for.

At any rate, I will try to finish the new installation and let you know what will happen this time. Thanks for your time and concern. Cheer.

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 5:03 pm

Finally, it is a success. Don't know what happened. This is what I see:

Image

My headless pi3 boots up and connected into my Wireless network with no hiccup.

Even though I got the wlan0 up and running, still the original question remains unanswered. Still have no clue what causing that crazy phenomenon.

Thanks.

User avatar
ksharindam
Posts: 70
Joined: Sat Jan 09, 2016 4:16 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 5:10 pm

I also have no clue what happened.

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 5:51 pm

Just when I thought I am off the hook. I am literally back to square one after running apt-get update and upgrade. Here is how it looks right after the upgrade process finished and rebooted.

Image

Just finished a clean installation and run the upgrade. Nothing else has done to the system. Don't know what to say now.

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 5:54 pm

Just one more thing. If you notice the audio and Bluetooth icon. It appears to me that upgrade has done something not only to the wifi but also the bluetooth and audio too. Only God knows what has happened. Cheers.

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

Re: wlan0 disappears after Stretch 2017-09-07

Sun Nov 26, 2017 8:25 pm

If you could pastebin the output of 'sudo journalctl' that could give some information to go on.

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Mon Nov 27, 2017 3:48 am

Here is my journalctl. Thanks ShiftPlusOne.

-- Logs begin at Fri 2016-11-04 00:16:42 +07, end at Mon 2017-11-27 10:23:25 +07. --
Nov 04 00:16:42 raspberrypi kernel: Booting Linux on physical CPU 0x0
Nov 04 00:16:42 raspberrypi kernel: Linux version 4.9.41-v7+ ([email protected]) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1023 SMP Tue Aug 8 16:00:15 BST 2017
Nov 04 00:16:42 raspberrypi kernel: CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Nov 04 00:16:42 raspberrypi kernel: CPU: div instructions available: patching division code
Nov 04 00:16:42 raspberrypi kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Nov 04 00:16:42 raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2
Nov 04 00:16:42 raspberrypi kernel: cma: Reserved 8 MiB at 0x3ac00000
Nov 04 00:16:42 raspberrypi kernel: Memory policy: Data cache writealloc
Nov 04 00:16:42 raspberrypi kernel: On node 0 totalpages: 242688
Nov 04 00:16:42 raspberrypi kernel: free_area_init_node: node 0, pgdat 80c6eec0, node_mem_map ba3a1000
Nov 04 00:16:42 raspberrypi kernel: Normal zone: 2133 pages used for memmap
Nov 04 00:16:42 raspberrypi kernel: Normal zone: 0 pages reserved
Nov 04 00:16:42 raspberrypi kernel: Normal zone: 242688 pages, LIFO batch:31
Nov 04 00:16:42 raspberrypi kernel: percpu: Embedded 14 pages/cpu @ba35b000 s25600 r8192 d23552 u57344
Nov 04 00:16:42 raspberrypi kernel: pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096
Nov 04 00:16:42 raspberrypi kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Nov 04 00:16:42 raspberrypi kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 240555
Nov 04 00:16:42 raspberrypi kernel: Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=720 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=020c3677-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
Nov 04 00:16:42 raspberrypi kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
Nov 04 00:16:42 raspberrypi kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Nov 04 00:16:42 raspberrypi kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Nov 04 00:16:42 raspberrypi kernel: Memory: 940356K/970752K available (7168K kernel code, 484K rwdata, 2012K rodata, 1024K init, 778K bss, 22204K reserved, 8192K cma-reserved)
Nov 04 00:16:42 raspberrypi kernel: Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xbb800000 - 0xff800000 (1088 MB)
lowmem : 0x80000000 - 0xbb400000 ( 948 MB)
modules : 0x7f000000 - 0x80000000 ( 16 MB)
.text : 0x80008000 - 0x80800000 (8160 kB)
.init : 0x80b00000 - 0x80c00000 (1024 kB)
.data : 0x80c00000 - 0x80c79094 ( 485 kB)
.bss : 0x80c7b000 - 0x80d3da64 ( 779 kB)
Nov 04 00:16:42 raspberrypi kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Nov 04 00:16:42 raspberrypi kernel: Hierarchical RCU implementation.
Nov 04 00:16:42 raspberrypi kernel: Build-time adjustment of leaf fanout to 32.
Nov 04 00:16:42 raspberrypi kernel: NR_IRQS:16 nr_irqs:16 16
Nov 04 00:16:42 raspberrypi kernel: arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys).
Nov 04 00:16:42 raspberrypi kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Nov 04 00:16:42 raspberrypi kernel: sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Nov 04 00:16:42 raspberrypi kernel: Switching to timer-based delay loop, resolution 52ns
Nov 04 00:16:42 raspberrypi kernel: Console: colour dummy device 80x30
Nov 04 00:16:42 raspberrypi kernel: console [tty1] enabled
Nov 04 00:16:42 raspberrypi kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Nov 04 00:16:42 raspberrypi kernel: pid_max: default: 32768 minimum: 301
Nov 04 00:16:42 raspberrypi kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Nov 04 00:16:42 raspberrypi kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
Nov 04 00:16:42 raspberrypi kernel: Disabling cpuset control group subsystem
Nov 04 00:16:42 raspberrypi kernel: CPU: Testing write buffer coherency: ok
Nov 04 00:16:42 raspberrypi kernel: ftrace: allocating 22396 entries in 66 pages
Nov 04 00:16:42 raspberrypi kernel: CPU0: update cpu_capacity 1024
Nov 04 00:16:42 raspberrypi kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Nov 04 00:16:42 raspberrypi kernel: Setting up static identity map for 0x100000 - 0x100034
Nov 04 00:16:42 raspberrypi kernel: CPU1: update cpu_capacity 1024
Nov 04 00:16:42 raspberrypi kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Nov 04 00:16:42 raspberrypi kernel: CPU2: update cpu_capacity 1024
Nov 04 00:16:42 raspberrypi kernel: CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Nov 04 00:16:42 raspberrypi kernel: CPU3: update cpu_capacity 1024
Nov 04 00:16:42 raspberrypi kernel: CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Nov 04 00:16:42 raspberrypi kernel: Brought up 4 CPUs
Nov 04 00:16:42 raspberrypi kernel: SMP: Total of 4 processors activated (153.60 BogoMIPS).
Nov 04 00:16:42 raspberrypi kernel: CPU: All CPU(s) started in HYP mode.
Nov 04 00:16:42 raspberrypi kernel: CPU: Virtualization extensions available.
Nov 04 00:16:42 raspberrypi kernel: devtmpfs: initialized
Nov 04 00:16:42 raspberrypi kernel: VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
Nov 04 00:16:42 raspberrypi kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Nov 04 00:16:42 raspberrypi kernel: futex hash table entries: 1024 (order: 4, 65536 bytes)
Nov 04 00:16:42 raspberrypi kernel: pinctrl core: initialized pinctrl subsystem
Nov 04 00:16:42 raspberrypi kernel: NET: Registered protocol family 16
Nov 04 00:16:42 raspberrypi kernel: DMA: preallocated 1024 KiB pool for atomic coherent allocations
Nov 04 00:16:42 raspberrypi kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Nov 04 00:16:42 raspberrypi kernel: hw-breakpoint: maximum watchpoint size is 8 bytes.
Nov 04 00:16:42 raspberrypi kernel: Serial: AMBA PL011 UART driver
Nov 04 00:16:42 raspberrypi kernel: bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Nov 04 00:16:42 raspberrypi kernel: uart-pl011 3f201000.serial: could not find pctldev for node /soc/[email protected]/uart0_pins, deferring probe
Nov 04 00:16:42 raspberrypi kernel: bcm2835-dma 3f007000.dma: DMA legacy API manager at bb80f000, dmachans=0x1
Nov 04 00:16:42 raspberrypi kernel: SCSI subsystem initialized
Nov 04 00:16:42 raspberrypi kernel: usbcore: registered new interface driver usbfs
Nov 04 00:16:42 raspberrypi kernel: usbcore: registered new interface driver hub
Nov 04 00:16:42 raspberrypi kernel: usbcore: registered new device driver usb
Nov 04 00:16:42 raspberrypi kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2017-08-08 12:01
Nov 04 00:16:42 raspberrypi kernel: clocksource: Switched to clocksource arch_sys_counter
Nov 04 00:16:42 raspberrypi kernel: VFS: Disk quotas dquot_6.6.0
Nov 04 00:16:42 raspberrypi kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Nov 04 00:16:42 raspberrypi kernel: FS-Cache: Loaded
Nov 04 00:16:42 raspberrypi kernel: CacheFiles: Loaded
Nov 04 00:16:42 raspberrypi kernel: NET: Registered protocol family 2
Nov 04 00:16:42 raspberrypi kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Nov 04 00:16:42 raspberrypi kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Nov 04 00:16:42 raspberrypi kernel: TCP: Hash tables configured (established 8192 bind 8192)
Nov 04 00:16:42 raspberrypi kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
Nov 04 00:16:42 raspberrypi kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Nov 04 00:16:42 raspberrypi kernel: NET: Registered protocol family 1
Nov 04 00:16:42 raspberrypi kernel: RPC: Registered named UNIX socket transport module.
Nov 04 00:16:42 raspberrypi kernel: RPC: Registered udp transport module.
Nov 04 00:16:42 raspberrypi kernel: RPC: Registered tcp transport module.
Nov 04 00:16:42 raspberrypi kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Nov 04 00:16:42 raspberrypi kernel: hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
Nov 04 00:16:42 raspberrypi kernel: workingset: timestamp_bits=14 max_order=18 bucket_order=4
Nov 04 00:16:42 raspberrypi kernel: FS-Cache: Netfs 'nfs' registered for caching
Nov 04 00:16:42 raspberrypi kernel: NFS: Registering the id_resolver key type
Nov 04 00:16:42 raspberrypi kernel: Key type id_resolver registered
Nov 04 00:16:42 raspberrypi kernel: Key type id_legacy registered
Nov 04 00:16:42 raspberrypi kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Nov 04 00:16:42 raspberrypi kernel: io scheduler noop registered
Nov 04 00:16:42 raspberrypi kernel: io scheduler deadline registered (default)
Nov 04 00:16:42 raspberrypi kernel: io scheduler cfq registered
Nov 04 00:16:42 raspberrypi kernel: BCM2708FB: allocated DMA memory fad10000
Nov 04 00:16:42 raspberrypi kernel: BCM2708FB: allocated DMA channel 0 @ bb80f000
Nov 04 00:16:42 raspberrypi kernel: Console: switching to colour frame buffer device 160x45
Nov 04 00:16:42 raspberrypi kernel: bcm2835-rng 3f104000.rng: hwrng registered
Nov 04 00:16:42 raspberrypi kernel: vc-cma: Videocore CMA driver
Nov 04 00:16:42 raspberrypi kernel: vc-cma: vc_cma_base = 0x00000000
Nov 04 00:16:42 raspberrypi kernel: vc-cma: vc_cma_size = 0x00000000 (0 MiB)
Nov 04 00:16:42 raspberrypi kernel: vc-cma: vc_cma_initial = 0x00000000 (0 MiB)
Nov 04 00:16:42 raspberrypi kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Nov 04 00:16:42 raspberrypi kernel: brd: module loaded
Nov 04 00:16:42 raspberrypi kernel: loop: module loaded
Nov 04 00:16:42 raspberrypi kernel: Loading iSCSI transport class v2.0-870.
Nov 04 00:16:42 raspberrypi kernel: usbcore: registered new interface driver smsc95xx
Nov 04 00:16:42 raspberrypi kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Nov 04 00:16:42 raspberrypi kernel: Core Release: 2.80a
Nov 04 00:16:42 raspberrypi kernel: Setting default values for core params
Nov 04 00:16:42 raspberrypi kernel: Finished setting default values for core params
Nov 04 00:16:42 raspberrypi kernel: Using Buffer DMA mode
Nov 04 00:16:42 raspberrypi kernel: Periodic Transfer Interrupt Enhancement - disabled
Nov 04 00:16:42 raspberrypi kernel: Multiprocessor Interrupt Enhancement - disabled
Nov 04 00:16:42 raspberrypi kernel: OTG VER PARAM: 0, OTG VER FLAG: 0
Nov 04 00:16:42 raspberrypi kernel: Dedicated Tx FIFOs mode
Nov 04 00:16:42 raspberrypi kernel: WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xbad04000 dma = 0xfad04000 len=9024
Nov 04 00:16:42 raspberrypi kernel: FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
Nov 04 00:16:42 raspberrypi kernel: dwc_otg: Microframe scheduler enabled
Nov 04 00:16:42 raspberrypi kernel: WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8058f7fc
Nov 04 00:16:42 raspberrypi kernel: WARN::hcd_init_fiq:460: FIQ ASM at 0x8058fb6c length 36
Nov 04 00:16:42 raspberrypi kernel: WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87a000
Nov 04 00:16:42 raspberrypi kernel: dwc_otg 3f980000.usb: DWC OTG Controller
Nov 04 00:16:42 raspberrypi kernel: dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Nov 04 00:16:42 raspberrypi kernel: dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
Nov 04 00:16:42 raspberrypi kernel: Init: Port Power? op_state=1
Nov 04 00:16:42 raspberrypi kernel: Init: Power Port (0)
Nov 04 00:16:42 raspberrypi kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 04 00:16:42 raspberrypi kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 04 00:16:42 raspberrypi kernel: usb usb1: Product: DWC OTG Controller
Nov 04 00:16:42 raspberrypi kernel: usb usb1: Manufacturer: Linux 4.9.41-v7+ dwc_otg_hcd
Nov 04 00:16:42 raspberrypi kernel: usb usb1: SerialNumber: 3f980000.usb
Nov 04 00:16:42 raspberrypi kernel: hub 1-0:1.0: USB hub found
Nov 04 00:16:42 raspberrypi kernel: hub 1-0:1.0: 1 port detected
Nov 04 00:16:42 raspberrypi kernel: dwc_otg: FIQ enabled
Nov 04 00:16:42 raspberrypi kernel: dwc_otg: NAK holdoff enabled
Nov 04 00:16:42 raspberrypi kernel: dwc_otg: FIQ split-transaction FSM enabled
Nov 04 00:16:42 raspberrypi kernel: Module dwc_common_port init
Nov 04 00:16:42 raspberrypi kernel: usbcore: registered new interface driver usb-storage
Nov 04 00:16:42 raspberrypi kernel: mousedev: PS/2 mouse device common for all mice
Nov 04 00:16:42 raspberrypi kernel: bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
Nov 04 00:16:42 raspberrypi kernel: bcm2835-cpufreq: min=600000 max=1200000
Nov 04 00:16:42 raspberrypi kernel: sdhci: Secure Digital Host Controller Interface driver
Nov 04 00:16:42 raspberrypi kernel: sdhci: Copyright(c) Pierre Ossman
Nov 04 00:16:42 raspberrypi kernel: sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
Nov 04 00:16:42 raspberrypi kernel: mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
Nov 04 00:16:42 raspberrypi kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Nov 04 00:16:42 raspberrypi kernel: ledtrig-cpu: registered to indicate activity on CPUs
Nov 04 00:16:42 raspberrypi kernel: hidraw: raw HID events driver (C) Jiri Kosina
Nov 04 00:16:42 raspberrypi kernel: usbcore: registered new interface driver usbhid
Nov 04 00:16:42 raspberrypi kernel: usbhid: USB HID core driver
Nov 04 00:16:42 raspberrypi kernel: vchiq: vchiq_init_state: slot_zero = 0xbad80000, is_master = 0
Nov 04 00:16:42 raspberrypi kernel: Initializing XFRM netlink socket
Nov 04 00:16:42 raspberrypi kernel: NET: Registered protocol family 17
Nov 04 00:16:42 raspberrypi kernel: Key type dns_resolver registered
Nov 04 00:16:42 raspberrypi kernel: Registering SWP/SWPB emulation handler
Nov 04 00:16:42 raspberrypi kernel: registered taskstats version 1
Nov 04 00:16:42 raspberrypi kernel: vc-sm: Videocore shared memory driver
Nov 04 00:16:42 raspberrypi kernel: [vc_sm_connected_init]: start
Nov 04 00:16:42 raspberrypi kernel: [vc_sm_connected_init]: end - returning 0
Nov 04 00:16:42 raspberrypi kernel: 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
Nov 04 00:16:42 raspberrypi kernel: sdhost: log_buf @ bad07000 (fad07000)
Nov 04 00:16:42 raspberrypi kernel: mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Nov 04 00:16:42 raspberrypi kernel: mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
Nov 04 00:16:42 raspberrypi kernel: mmc-bcm2835 3f300000.mmc: DMA channel allocated
Nov 04 00:16:42 raspberrypi kernel: mmc0: host does not support reading read-only switch, assuming write-enable
Nov 04 00:16:42 raspberrypi kernel: mmc0: new high speed SD card at address b368
Nov 04 00:16:42 raspberrypi kernel: mmcblk0: mmc0:b368 SMISD 1.86 GiB
Nov 04 00:16:42 raspberrypi kernel: mmcblk0: p1
Nov 04 00:16:42 raspberrypi kernel: of_cfs_init
Nov 04 00:16:42 raspberrypi kernel: of_cfs_init: OK
Nov 04 00:16:42 raspberrypi kernel: Waiting for root device PARTUUID=020c3677-02...
Nov 04 00:16:42 raspberrypi kernel: mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Nov 04 00:16:42 raspberrypi kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Nov 04 00:16:42 raspberrypi kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Nov 04 00:16:42 raspberrypi kernel: mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Nov 04 00:16:42 raspberrypi kernel: Indeed it is in host mode hprt0 = 00021501
Nov 04 00:16:42 raspberrypi kernel: random: fast init done
Nov 04 00:16:42 raspberrypi kernel: mmc1: new high speed SDIO card at address 0001
Nov 04 00:16:42 raspberrypi kernel: usb 1-1: new high-speed USB device number 2 using dwc_otg
Nov 04 00:16:42 raspberrypi kernel: Indeed it is in host mode hprt0 = 00001101
Nov 04 00:16:42 raspberrypi kernel: usb 1-1: New USB device found, idVendor=0424, idProduct=9514
Nov 04 00:16:42 raspberrypi kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 04 00:16:42 raspberrypi kernel: hub 1-1:1.0: USB hub found
Nov 04 00:16:42 raspberrypi kernel: hub 1-1:1.0: 5 ports detected
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 04 00:16:42 raspberrypi kernel: smsc95xx v1.0.5
Nov 04 00:16:42 raspberrypi kernel: smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a5:e2:71
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.3: new high-speed USB device number 4 using dwc_otg
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.3: New USB device found, idVendor=0781, idProduct=5530
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.3: Product: Cruzer
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.3: Manufacturer: SanDisk
Nov 04 00:16:42 raspberrypi kernel: usb 1-1.3: SerialNumber: 200535506311D321DF21
Nov 04 00:16:42 raspberrypi kernel: usb-storage 1-1.3:1.0: USB Mass Storage device detected
Nov 04 00:16:42 raspberrypi kernel: scsi host0: usb-storage 1-1.3:1.0
Nov 04 00:16:42 raspberrypi kernel: scsi 0:0:0:0: Direct-Access SanDisk Cruzer 1.00 PQ: 0 ANSI: 2
Nov 04 00:16:42 raspberrypi kernel: sd 0:0:0:0: [sda] 31250432 512-byte logical blocks: (16.0 GB/14.9 GiB)
Nov 04 00:16:42 raspberrypi kernel: sd 0:0:0:0: [sda] Write Protect is off
Nov 27 10:21:57 raspberrypi kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
Nov 27 10:21:57 raspberrypi kernel: sd 0:0:0:0: [sda] No Caching mode page found
Nov 27 10:21:57 raspberrypi kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Nov 27 10:21:57 raspberrypi kernel: sda: sda1 sda2
Nov 27 10:21:57 raspberrypi kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Nov 27 10:21:57 raspberrypi kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Nov 27 10:21:57 raspberrypi kernel: VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
Nov 27 10:21:57 raspberrypi kernel: devtmpfs: mounted
Nov 27 10:21:57 raspberrypi kernel: Freeing unused kernel memory: 1024K (80b00000 - 80c00000)
Nov 27 10:21:57 raspberrypi systemd[1]: System time before build time, advancing clock.
Nov 27 10:21:57 raspberrypi systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Nov 27 10:21:57 raspberrypi systemd[1]: Detected architecture arm.
Nov 27 10:21:57 raspberrypi systemd[1]: Set hostname to <raspberrypi>.
Nov 27 10:21:57 raspberrypi systemd[1]: Listening on Journal Socket.
Nov 27 10:21:57 raspberrypi systemd[1]: Listening on udev Control Socket.
Nov 27 10:21:57 raspberrypi systemd[1]: Listening on fsck to fsckd communication Socket.
Nov 27 10:21:57 raspberrypi systemd[1]: Created slice User and Session Slice.
Nov 27 10:21:57 raspberrypi systemd[1]: Created slice System Slice.
Nov 27 10:21:57 raspberrypi systemd[1]: Created slice system-autologin.slice.
Nov 27 10:21:57 raspberrypi systemd[1]: Starting Restore / save the current clock...
Nov 27 10:21:57 raspberrypi systemd-journald[124]: Journal started
Nov 27 10:21:57 raspberrypi systemd-journald[124]: Runtime journal (/run/log/journal/28a3f56e669e4806afc628802a4f753f) is 11.5M, max 46.3M, 34.7M free.
Nov 27 10:21:57 raspberrypi systemd-modules-load[117]: could not open moddep file '/lib/modules/4.9.41-v7+/modules.dep.bin'
Nov 27 10:21:57 raspberrypi systemd-modules-load[117]: Failed to lookup alias 'i2c-dev': Function not implemented
Nov 27 10:21:57 raspberrypi fake-hwclock[114]: Mon 27 Nov 03:21:57 UTC 2017
Nov 27 10:21:57 raspberrypi systemd-fsck[115]: e2fsck 1.43.4 (31-Jan-2017)
Nov 27 10:21:57 raspberrypi systemd[1]: Started Create Static Device Nodes in /dev.
Nov 27 10:21:57 raspberrypi systemd[1]: Starting udev Kernel Device Manager...
Nov 27 10:21:57 raspberrypi systemd-fsck[115]: /dev/sda2: clean, 136151/955808 files, 1198854/3894528 blocks
Nov 27 10:21:57 raspberrypi systemd[1]: Started File System Check on Root Device.
Nov 27 10:21:57 raspberrypi systemd[1]: Starting Remount Root and Kernel File Systems...
Nov 27 10:21:57 raspberrypi systemd[1]: Started udev Kernel Device Manager.
Nov 27 10:21:57 raspberrypi kernel: EXT4-fs (sda2): re-mounted. Opts: (null)
Nov 27 10:21:57 raspberrypi systemd[1]: Started Remount Root and Kernel File Systems.
Nov 27 10:21:57 raspberrypi systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 27 10:21:57 raspberrypi systemd[1]: Starting Load/Save Random Seed...
Nov 27 10:21:57 raspberrypi systemd[1]: Starting udev Coldplug all Devices...
Nov 27 10:21:57 raspberrypi systemd[1]: Started Load/Save Random Seed.
Nov 27 10:21:57 raspberrypi systemd-journald[124]: Runtime journal (/run/log/journal/28a3f56e669e4806afc628802a4f753f) is 11.5M, max 46.3M, 34.7M free.
Nov 27 10:21:57 raspberrypi systemd[1]: Started Flush Journal to Persistent Storage.
Nov 27 10:21:57 raspberrypi systemd[1]: Started Set the console keyboard layout.
Nov 27 10:21:57 raspberrypi systemd[1]: Reached target Local File Systems (Pre).
Nov 27 10:21:57 raspberrypi systemd[1]: Started udev Coldplug all Devices.
Nov 27 10:21:57 raspberrypi systemd[1]: Starting Show Plymouth Boot Screen...
Nov 27 10:21:57 raspberrypi systemd[1]: Started Show Plymouth Boot Screen.
Nov 27 10:21:57 raspberrypi systemd[1]: Reached target Encrypted Volumes.
Nov 27 10:21:57 raspberrypi systemd[1]: Reached target Paths.
Nov 27 10:21:57 raspberrypi systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Nov 27 10:21:57 raspberrypi systemd[1]: Found device /dev/serial1.
Nov 27 10:21:58 raspberrypi mtp-probe[247]: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1"
Nov 27 10:21:58 raspberrypi mtp-probe[254]: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Nov 27 10:21:58 raspberrypi mtp-probe[254]: bus: 1, device: 4 was not an MTP device
Nov 27 10:21:58 raspberrypi mtp-probe[247]: bus: 1, device: 3 was not an MTP device
Nov 27 10:21:58 raspberrypi systemd-udevd[196]: could not open moddep file '/lib/modules/4.9.41-v7+/modules.dep.bin'
Nov 27 10:21:58 raspberrypi systemd[1]: Found device Cruzer boot.
Nov 27 10:21:58 raspberrypi systemd[1]: Starting File System Check on /dev/disk/by-partuuid/020c3677-01...
Nov 27 10:21:58 raspberrypi systemd-fsck[268]: fsck.fat 4.1 (2017-01-24)
Nov 27 10:21:58 raspberrypi systemd-fsck[268]: /dev/sda1: 145 files, 42657/84273 clusters
Nov 27 10:21:58 raspberrypi systemd[1]: Started File System Check on /dev/disk/by-partuuid/020c3677-01.
Nov 27 10:21:58 raspberrypi systemd[1]: Mounting /boot...
Nov 27 10:21:58 raspberrypi systemd[1]: Mounted /boot.
Nov 27 10:21:58 raspberrypi systemd[1]: Reached target Local File Systems.
Nov 27 10:21:58 raspberrypi systemd[1]: Starting Preprocess NFS configuration...
Nov 27 10:21:58 raspberrypi systemd[1]: Starting Set console font and keymap...
Nov 27 10:21:58 raspberrypi systemd[1]: Starting Create Volatile Files and Directories...
Nov 27 10:21:58 raspberrypi systemd[1]: Starting Raise network interfaces...
Nov 27 10:21:58 raspberrypi kernel: random: crng init done
Nov 27 10:21:58 raspberrypi systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Nov 27 10:21:58 raspberrypi systemd[1]: Started Preprocess NFS configuration.
Nov 27 10:21:58 raspberrypi systemd[1]: Started Set console font and keymap.
Nov 27 10:21:58 raspberrypi systemd[1]: Reached target NFS client services.
Nov 27 10:21:58 raspberrypi systemd[1]: Reached target Remote File Systems (Pre).
Nov 27 10:21:58 raspberrypi systemd[1]: Reached target Remote File Systems.
Nov 27 10:21:58 raspberrypi systemd[1]: Started Create Volatile Files and Directories.
Nov 27 10:21:58 raspberrypi systemd[1]: Starting Network Time Synchronization...
Nov 27 10:21:58 raspberrypi systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Nov 27 10:21:58 raspberrypi systemd[1]: Started Update UTMP about System Boot/Shutdown.
Nov 27 10:21:59 raspberrypi systemd[1]: Started Network Time Synchronization.
Nov 27 10:21:59 raspberrypi systemd[1]: Reached target System Time Synchronized.
Nov 27 10:21:59 raspberrypi systemd[1]: Received SIGRTMIN+20 from PID 217 (plymouthd).
Nov 27 10:22:00 raspberrypi systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Nov 27 10:22:00 raspberrypi systemd[1]: Reached target System Initialization.
Nov 27 10:22:00 raspberrypi systemd[1]: Listening on D-Bus System Message Bus Socket.
Nov 27 10:22:00 raspberrypi systemd[1]: apt-daily.timer: Adding 2h 4min 3.116548s random time.
Nov 27 10:22:00 raspberrypi systemd[1]: Started Daily apt download activities.
Nov 27 10:22:00 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 44min 24.395839s random time.
Nov 27 10:22:00 raspberrypi systemd[1]: Started Daily apt upgrade and clean activities.
Nov 27 10:22:00 raspberrypi systemd[1]: Started Daily Cleanup of Temporary Directories.
Nov 27 10:22:00 raspberrypi systemd[1]: Reached target Timers.
Nov 27 10:22:00 raspberrypi systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Nov 27 10:22:00 raspberrypi systemd[1]: Listening on triggerhappy.socket.
Nov 27 10:22:00 raspberrypi systemd[1]: Reached target Sockets.
Nov 27 10:22:00 raspberrypi systemd[1]: Reached target Basic System.
Nov 27 10:22:00 raspberrypi systemd[1]: Starting LSB: Autogenerate and use a swap file...
Nov 27 10:22:00 raspberrypi systemd[1]: Started Regular background program processing daemon.
Nov 27 10:22:00 raspberrypi systemd[1]: Starting Login Service...
Nov 27 10:22:00 raspberrypi cron[331]: (CRON) INFO (pidfile fd = 3)
Nov 27 10:22:00 raspberrypi systemd[1]: Starting System Logging Service...
Nov 27 10:22:00 raspberrypi systemd[1]: Starting Check for v3d driver...
Nov 27 10:22:00 raspberrypi systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Nov 27 10:22:00 raspberrypi systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Nov 27 10:22:00 raspberrypi systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)...
Nov 27 10:22:00 raspberrypi systemd[1]: Started D-Bus System Message Bus.
Nov 27 10:22:00 raspberrypi cron[331]: (CRON) INFO (Running @reboot jobs)
Nov 27 10:22:00 raspberrypi kernel: uart-pl011 3f201000.serial: no DMA platform data
Nov 27 10:22:00 raspberrypi liblogging-stdlog[334]: [origin software="rsyslogd" swVersion="8.24.0" x-pid="334" x-info="http://www.rsyslog.com"] start
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: Found user 'avahi' (UID 108) and group 'avahi' (GID 112).
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: Successfully dropped root privileges.
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: avahi-daemon 0.6.32 starting up.
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: Successfully called chroot().
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: Successfully dropped remaining capabilities.
Nov 27 10:22:00 raspberrypi systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Nov 27 10:22:00 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: No service file found in /etc/avahi/services.
Nov 27 10:22:00 raspberrypi systemd[1]: Starting triggerhappy global hotkey daemon...
Nov 27 10:22:00 raspberrypi systemd[1]: Started System Logging Service.
Nov 27 10:22:00 raspberrypi systemd[1]: Started Check for v3d driver.
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: socket() failed: Address family not supported by protocol
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: Failed to create IPv6 socket, proceeding in IPv4 only mode
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: socket() failed: Address family not supported by protocol
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: Network interface enumeration completed.
Nov 27 10:22:00 raspberrypi avahi-daemon[336]: Server startup complete. Host name is raspberrypi.local. Local service cookie is 3117520522.
Nov 27 10:22:00 raspberrypi thd[376]: Found socket passed from systemd
Nov 27 10:22:00 raspberrypi dhcpcd[375]: dev: loaded udev
Nov 27 10:22:00 raspberrypi systemd[1]: Started triggerhappy global hotkey daemon.
Nov 27 10:22:00 raspberrypi dhcpcd[375]: all: IPv6 kernel autoconf disabled
Nov 27 10:22:00 raspberrypi dhcpcd[375]: forked to background, child pid 382
Nov 27 10:22:00 raspberrypi systemd[1]: Started dhcpcd on all interfaces.
Nov 27 10:22:00 raspberrypi systemd[1]: Started Login Service.
Nov 27 10:22:00 raspberrypi systemd-logind[333]: New seat seat0.
Nov 27 10:22:00 raspberrypi dphys-swapfile[329]: Starting dphys-swapfile swapfile setup ...
Nov 27 10:22:00 raspberrypi raspi-config[340]: Checking if shift key is held down:Error opening '/dev/input/event*': No such file or directory
Nov 27 10:22:00 raspberrypi systemd[1]: Started Raise network interfaces.
Nov 27 10:22:00 raspberrypi systemd[1]: Reached target Network.
Nov 27 10:22:00 raspberrypi systemd[1]: Starting Permit User Sessions...
Nov 27 10:22:00 raspberrypi raspi-config[340]: No. Switching to ondemand scaling governor.
Nov 27 10:22:00 raspberrypi systemd[1]: Started VNC Server in Service Mode daemon.
Nov 27 10:22:00 raspberrypi systemd[1]: Starting /etc/rc.local Compatibility...
Nov 27 10:22:00 raspberrypi systemd[1]: Starting OpenBSD Secure Shell server...
Nov 27 10:22:00 raspberrypi systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
Nov 27 10:22:00 raspberrypi systemd[1]: Started Permit User Sessions.
Nov 27 10:22:00 raspberrypi systemd[1]: Starting Light Display Manager...
Nov 27 10:22:00 raspberrypi dhcpcd[382]: eth0: waiting for carrier
Nov 27 10:22:00 raspberrypi dhcpcd[382]: eth0: carrier acquired
Nov 27 10:22:00 raspberrypi dhcpcd[382]: all: IPv6 kernel autoconf disabled
Nov 27 10:22:00 raspberrypi kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov 27 10:22:00 raspberrypi systemd[1]: Started /etc/rc.local Compatibility.
Nov 27 10:22:00 raspberrypi systemd[1]: Starting Hold until boot process finishes up...
Nov 27 10:22:00 raspberrypi dhcpcd[382]: DUID 00:01:00:01:21:44:2c:51:b8:27:eb:f0:b7:24
Nov 27 10:22:00 raspberrypi systemd[1]: Starting Terminate Plymouth Boot Screen...
Nov 27 10:22:00 raspberrypi dhcpcd[382]: eth0: IAID eb:a5:e2:71
Nov 27 10:22:00 raspberrypi dhcpcd[382]: eth0: adding address fe80::45da:cb7:cc42:b8bc
Nov 27 10:22:00 raspberrypi dhcpcd[382]: if_addaddress6: Operation not supported
Nov 27 10:22:00 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 217 (plymouthd).
Nov 27 10:22:00 raspberrypi systemd[1]: Started Hold until boot process finishes up.
Nov 27 10:22:00 raspberrypi systemd[1]: Started Terminate Plymouth Boot Screen.
Nov 27 10:22:00 raspberrypi systemd[1]: Started Getty on tty1.
Nov 27 10:22:00 raspberrypi systemd[1]: Reached target Login Prompts.
Nov 27 10:22:00 raspberrypi dphys-swapfile[329]: want /var/swap=100MByte, checking existing: keeping it
Nov 27 10:22:00 raspberrypi dphys-swapfile[329]: done.
Nov 27 10:22:00 raspberrypi kernel: Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k FS
Nov 27 10:22:00 raspberrypi systemd[1]: Started LSB: Autogenerate and use a swap file.
Nov 27 10:22:01 raspberrypi sshd[414]: Server listening on 0.0.0.0 port 22.
Nov 27 10:22:01 raspberrypi systemd[1]: Started OpenBSD Secure Shell server.
Nov 27 10:22:01 raspberrypi vncserver-x11[434]: ServerManager: Server started
Nov 27 10:22:01 raspberrypi lightdm[422]: 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
Nov 27 10:22:01 raspberrypi dhcpcd[382]: eth0: rebinding lease of 192.168.1.190
Nov 27 10:22:01 raspberrypi systemd[1]: Started Light Display Manager.
Nov 27 10:22:01 raspberrypi vncserver-x11[434]: ConsoleDisplay: Cannot find a running X server on vt1
Nov 27 10:22:01 raspberrypi vncserver-x11[434]: AgentInitCheck: agent comms failure
Nov 27 10:22:01 raspberrypi vncserver-x11[434]: ConsoleDisplay: Found running X server (pid=447)
Nov 27 10:22:02 raspberrypi kernel: smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Nov 27 10:22:04 raspberrypi btuart[339]: Can't set line discipline: Invalid argument
Nov 27 10:22:04 raspberrypi btuart[339]: Can't initialize device: Invalid argument
Nov 27 10:22:04 raspberrypi btuart[339]: bcm43xx_init
Nov 27 10:22:04 raspberrypi btuart[339]: Flash firmware /lib/firmware/BCM43430A1.hcd
Nov 27 10:22:04 raspberrypi btuart[339]: Set BDADDR UART: b8:27:eb:0f:48:db
Nov 27 10:22:04 raspberrypi btuart[339]: Set Controller UART speed to 921600 bit/s
Nov 27 10:22:04 raspberrypi systemd[1]: hciuart.service: Control process exited, code=exited status=1
Nov 27 10:22:04 raspberrypi systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
Nov 27 10:22:04 raspberrypi systemd[1]: hciuart.service: Unit entered failed state.
Nov 27 10:22:04 raspberrypi systemd[1]: hciuart.service: Failed with result 'exit-code'.
Nov 27 10:22:04 raspberrypi systemd[1]: Reached target Multi-User System.
Nov 27 10:22:04 raspberrypi systemd[1]: Started BluezALSA proxy.
Nov 27 10:22:04 raspberrypi systemd[1]: Reached target Graphical Interface.
Nov 27 10:22:04 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Nov 27 10:22:04 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
Nov 27 10:22:04 raspberrypi systemd[1]: Startup finished in 3.705s (kernel) + 8.749s (userspace) = 12.455s.
Nov 27 10:22:04 raspberrypi bluealsa[465]: /usr/bin/bluealsa: No HCI device available
Nov 27 10:22:04 raspberrypi systemd[1]: bluealsa.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 10:22:04 raspberrypi systemd[1]: bluealsa.service: Unit entered failed state.
Nov 27 10:22:04 raspberrypi systemd[1]: bluealsa.service: Failed with result 'exit-code'.
Nov 27 10:22:05 raspberrypi login[432]: pam_unix(login:session): session opened for user pi by LOGIN(uid=0)
Nov 27 10:22:05 raspberrypi systemd[1]: Created slice User Slice of pi.
Nov 27 10:22:05 raspberrypi systemd[1]: Starting User Manager for UID 1000...
Nov 27 10:22:05 raspberrypi systemd-logind[333]: New session c1 of user pi.
Nov 27 10:22:05 raspberrypi systemd[1]: Started Session c1 of user pi.
Nov 27 10:22:05 raspberrypi systemd[491]: pam_unix(systemd-user:session): session opened for user pi by (uid=0)
Nov 27 10:22:05 raspberrypi systemd[491]: Listening on GnuPG cryptographic agent and passphrase cache.
Nov 27 10:22:05 raspberrypi systemd[491]: Reached target Timers.
Nov 27 10:22:05 raspberrypi systemd[491]: Starting D-Bus User Message Bus Socket.
Nov 27 10:22:05 raspberrypi systemd[491]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Nov 27 10:22:05 raspberrypi systemd[491]: Reached target Paths.
Nov 27 10:22:05 raspberrypi systemd[491]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Nov 27 10:22:05 raspberrypi systemd[491]: Listening on GnuPG cryptographic agent (access for web browsers).
Nov 27 10:22:05 raspberrypi systemd[491]: Listening on D-Bus User Message Bus Socket.
Nov 27 10:22:05 raspberrypi systemd[491]: Reached target Sockets.
Nov 27 10:22:05 raspberrypi systemd[491]: Reached target Basic System.
Nov 27 10:22:05 raspberrypi systemd[491]: Reached target Default.
Nov 27 10:22:05 raspberrypi systemd[491]: Startup finished in 198ms.
Nov 27 10:22:05 raspberrypi systemd[1]: Started User Manager for UID 1000.
Nov 27 10:22:05 raspberrypi lightdm[518]: 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
Nov 27 10:22:05 raspberrypi lightdm[518]: pam_unix(lightdm-autologin:session): session opened for user pi by (uid=0)
Nov 27 10:22:05 raspberrypi systemd[1]: Started Session c2 of user pi.
Nov 27 10:22:05 raspberrypi systemd-logind[333]: New session c2 of user pi.
Nov 27 10:22:05 raspberrypi lightdm[422]: Error opening audit socket: Protocol not supported
Nov 27 10:22:06 raspberrypi systemd[491]: Started D-Bus User Message Bus.
Nov 27 10:22:06 raspberrypi dbus-daemon[543]: Successfully activated service 'org.freedesktop.systemd1'
Nov 27 10:22:06 raspberrypi dhcpcd[382]: eth0: probing address 192.168.1.190/24
Nov 27 10:22:07 raspberrypi dbus-daemon[543]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Nov 27 10:22:07 raspberrypi systemd[491]: Starting Virtual filesystem service...
Nov 27 10:22:07 raspberrypi dbus-daemon[543]: Successfully activated service 'org.gtk.vfs.Daemon'
Nov 27 10:22:07 raspberrypi systemd[491]: Started Virtual filesystem service.
Nov 27 10:22:07 raspberrypi gvfsd[588]: fuse: device not found, try 'modprobe fuse' first
Nov 27 10:22:08 raspberrypi dbus[341]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Nov 27 10:22:08 raspberrypi systemd[1]: Starting Authorization Manager...
Nov 27 10:22:08 raspberrypi polkitd[619]: started daemon version 0.105 using authority implementation `local' version `0.105'
Nov 27 10:22:08 raspberrypi dbus[341]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Nov 27 10:22:08 raspberrypi systemd[1]: Started Authorization Manager.
Nov 27 10:22:08 raspberrypi polkitd(authority=local)[619]: Registered Authentication Agent for unix-session:c2 (system bus name :1.9 [lxpolkit], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service'
Nov 27 10:22:09 raspberrypi systemd[491]: Starting Virtual filesystem service - disk device monitor...
Nov 27 10:22:09 raspberrypi dbus[341]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Nov 27 10:22:09 raspberrypi systemd[1]: Starting Disk Manager...
Nov 27 10:22:09 raspberrypi udisksd[656]: udisks daemon version 2.1.8 starting
Nov 27 10:22:09 raspberrypi dbus[341]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Nov 27 10:22:09 raspberrypi udisksd[656]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Nov 27 10:22:09 raspberrypi systemd[1]: Started Disk Manager.
Nov 27 10:22:09 raspberrypi udisksd[656]: Cleaning up mount point /media/pi/BOOT (device 179:1 is not mounted)
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Nov 27 10:22:09 raspberrypi systemd[491]: Started Virtual filesystem service - disk device monitor.
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service'
Nov 27 10:22:09 raspberrypi systemd[491]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Nov 27 10:22:09 raspberrypi systemd[491]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service'
Nov 27 10:22:09 raspberrypi systemd[491]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Nov 27 10:22:09 raspberrypi systemd[491]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service'
Nov 27 10:22:09 raspberrypi systemd[491]: Starting Virtual filesystem service - digital camera monitor...
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Nov 27 10:22:09 raspberrypi systemd[491]: Started Virtual filesystem service - digital camera monitor.
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service'
Nov 27 10:22:09 raspberrypi systemd[491]: Starting Virtual filesystem service - Apple File Conduit monitor...
Nov 27 10:22:09 raspberrypi gvfs-afc-volume-monitor[680]: Volume monitor alive
Nov 27 10:22:09 raspberrypi dbus-daemon[543]: Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Nov 27 10:22:09 raspberrypi systemd[491]: Started Virtual filesystem service - Apple File Conduit monitor.
Nov 27 10:22:10 raspberrypi kernel: FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Nov 27 10:22:10 raspberrypi udisksd[656]: Mounted /dev/mmcblk0p1 at /media/pi/BOOT on behalf of uid 1000
Nov 27 10:22:11 raspberrypi dhcpcd[382]: eth0: leased 192.168.1.190 for infinity
Nov 27 10:22:11 raspberrypi dhcpcd[382]: eth0: adding route to 192.168.1.0/24
Nov 27 10:22:11 raspberrypi dhcpcd[382]: eth0: adding default route via 192.168.1.1
Nov 27 10:22:11 raspberrypi avahi-daemon[336]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.190.
Nov 27 10:22:11 raspberrypi avahi-daemon[336]: New relevant interface eth0.IPv4 for mDNS.
Nov 27 10:22:11 raspberrypi avahi-daemon[336]: Registering new address record for 192.168.1.190 on eth0.IPv4.
Nov 27 10:22:22 raspberrypi vncserver-x11[434]: Connections: connected: 192.168.1.102::50186
Nov 27 10:22:23 raspberrypi vncserver-x11[434]: session started: user pi permissions f
Nov 27 10:22:23 raspberrypi vncserver-x11[434]: Connections: authenticated: 192.168.1.102::50186, as pi (f permissions)
Nov 27 10:22:23 raspberrypi vncserver-x11[434]: SPrintConnMgr: Failed to add printer: server-error-service-unavailable
Nov 27 10:22:42 raspberrypi systemd[491]: Time has been changed
Nov 27 10:22:42 raspberrypi systemd-timesyncd[299]: Synchronized to time server 210.245.100.39:123 (2.debian.pool.ntp.org).
Nov 27 10:22:42 raspberrypi systemd[1]: Time has been changed
Nov 27 10:22:42 raspberrypi systemd[1]: apt-daily.timer: Adding 11h 50min 42.880878s random time.
Nov 27 10:22:42 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 8min 29.990988s random time.
Nov 27 10:23:25 raspberrypi sudo[786]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl
Nov 27 10:23:25 raspberrypi sudo[786]: pam_unix(sudo:session): session opened for user root by (uid=0)

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

Re: wlan0 disappears after Stretch 2017-09-07

Mon Nov 27, 2017 9:16 am

Are you doing anything strange with /boot or /etc/fstab?

This looks a bit strange:

Code: Select all

systemd-modules-load[117]: could not open moddep file '/lib/modules/4.9.41-v7+/modules.dep.bin'
Which may suggest that your kernel doesn't match your modules.

The latest kernel in apt is 4.9.59-v7+, but you're running 4.9.41-v7+ somehow.

This seems a bit unusual:

Code: Select all

Mounted /dev/mmcblk0p1 at /media/pi/BOOT on behalf of uid 1000

User avatar
ksharindam
Posts: 70
Joined: Sat Jan 09, 2016 4:16 pm

Re: wlan0 disappears after Stretch 2017-09-07

Mon Nov 27, 2017 3:05 pm

few days ago i updated dhcpcd5 package, after that my wifi dongle does not works at first attempt. I have to plug and unplug two or more times to make it work. There may be a bug in latest dhcpcd5 package.

DirkS
Posts: 8822
Joined: Tue Jun 19, 2012 9:46 pm
Location: Essex, UK

Re: wlan0 disappears after Stretch 2017-09-07

Mon Nov 27, 2017 3:09 pm

ksharindam wrote:
Mon Nov 27, 2017 3:05 pm
few days ago i updated dhcpcd5 package, after that my wifi dongle does not works at first attempt. I have to plug and unplug two or more times to make it work. There may be a bug in latest dhcpcd5 package.
Seems to be irrelevant to this topic. Please start a new topic with details of your setup

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Mon Nov 27, 2017 4:04 pm

To ShiftPlusOne,

I think you are very good. You might have found the reason which I also suspected this morning but I am no way near your skill to know what to investigate.

Here is what happened. I used to run Raspbian on a SD card in headless mode. After a while I could no longer successfully complete apt-get update and upgrade (might be the SD card corrupted? I am still learning how to overcome this). A gentleman goes by RonR in this forum show me how to run Raspbian on a USB stick instead of SD card. Please read this post and you will get the whole story: viewtopic.php?f=66&t=180716&p=1221043#p1221043

I did what he showed me, use Etcher to flash the image on both USB and SC card. Run the little program named set-boot (this might be the one causing the current problem) on the SD card (alter /etc/fstab ? I don't know). Point cmdline.txt to the PARTUUID of the USB and boot from it. It actually works for a while until now. So far, the only thing I flashed is the USB not the SD card (its content with set-boot remained).

The USB boots up fine. Problem only occurs if I performed an update/upgrade.

What do I need to to from here? Thank you very much.

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

Re: wlan0 disappears after Stretch 2017-09-07

Mon Nov 27, 2017 6:18 pm

Modify /etc/fstab so that /boot is the first partition on the sd card, not the USB stick.
Reboot and run 'sudo apt-get install raspberrypi-kernel raspberrypi-bootloader --reinstall', then reboot again.

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Tue Nov 28, 2017 1:20 am

To ShiftPlusOne,

After follow your instruction it looks very promising. Wlan0, audio, and bluetooth are all back for business immediately. Please allow me a few more hours to test drive it. Will be back with conclusion. Thank you very much for the privilege of your time.

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Tue Nov 28, 2017 2:57 am

Hi ShiftPlusOne,

After following your instruction there are many new things start to change.

This time I decided to start the whole thing from scratch (re-flash the fresh Stretch image again) to study the nature of how this process work so that I don’t have to run around asking for questions like I am doing now. Unfortunately, these are the new trouble makers:

1- I am no longer being able to headlessly connectted to my wifi network from the beginning (by putting ssh + wpa_supplicant.conf into the little boot partition on the USB). I even tried to put those 2 files inside the SD card’s boot partition, it is still behaved in the same fashion. It used to work fine yesterday. Obviously eth0 is fully functional.

2- Stretch this time, immediately from the first boot up, goes straight to the state where NO wlan0, audio, and bluethooth whereas before it takes apt-get update and upgrade to inflict that.

3- Journalctl now has 3 different date entries instead of 2.

Could you help me beam some light to how this process work especially the interaction of the different kernels, modules, /etc/fstab, etc…
I insisted on using the USB stick because my Samsung 16GB SD card is acting up. It would run but no update/upgrade nor installing anything to it. I am not at the convenience of getting another SD card now. I am still googling around to find the way to fix this SD card but has no clue of what to look for.

Currently, I copied the entire content of the 16GB SD card onto another functional 2GB SD card and run this 2 GB SD card with the USB stick that has the new Stretch on it.

As far as I understand, when we turn on the power the pi goes for the SD card first then from cmdline.txt it redirected the process to the 2nd partition of the USB with root (/) on it. From there on the SD card steps aside giving way to the USB to run the show. How all of these get tangled up causing all kind of weird things happened is what I am keenly going after.

After the errorous boot up, running your instruction would magically put Stretch back to the way it should be with 4.9.41-v7+ #1023. I am running the update/upgrade now to see if it survived the final test and I expected it does. Will keep you posted after the update.

Thank ShiftPlusOne for your dedicative help/lecture.

pixxx
Posts: 25
Joined: Sun Oct 08, 2017 4:12 pm

Re: wlan0 disappears after Stretch 2017-09-07

Tue Nov 28, 2017 3:56 am

To ShiftPlusOne,

I conclude that your instruction works beautifully. You are the man.

I have finished the update/upgrade -> reboot -> some installation -> reboot and all of the Wlan0 + Bluetooth + Audio are still there to stay.

Even though the problem is fixed I am still baffled with the method/concept that you provided to guide me to the finish line. I spent 6 hrs last night googling around to find pieces of the puzzle about how the kernel/module got messed up in my case but still arrived empty-handed due to my lack of knowledge of how linux works.

If you do have time please beam me some light so that I can pick up some momentum to continue on with this journey. I prefer to find the way to fix this problem and have a clean installation instead of running through your script every single time I perform a fresh installation of Raspbian.

As always, thank you very much for your unconditional help. Take care.

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

Re: wlan0 disappears after Stretch 2017-09-07

Tue Nov 28, 2017 9:42 am

Here's how a pi normally boots when you have the boot files on an sd card:
The 'firmware' (bootcode.bin and start.elf) load the linux kernel and pass it the content or cmdline.txt. The root= parameter tells the Linux kernel what the 'root' file system is. The linux kernel initialises the rest of the hardware and loads up the init system (in this case, systemd) from the root filesystem. /etc/fstab tells the system where the storage devices should be mounted.

With the above info, here's why things went wrong:
cmdline.txt says root is on USB - that's fine
fstab says /boot is on USB - that's not fine because, in your case, the firmware loads the boot files off the sd card.
The firmware and linux now disagree where files are.
You upgrade the system, which upgrades the kernel and firmware on USB, which never gets used. Everything within linux gets set up to use the new kernel, but when you reboot, you're still running the old kernel off the SD card.
Linux has drivers which can be loaded when they're needed rather than compiled into the kernel - these are called 'modules' and live on the root filesystem. The modules for the old kernel were deleted and new ones installed, so the old kernel you're running isn't able to initialise all of the hardware.

Hope that makes sense.

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

Re: wlan0 disappears after Stretch 2017-09-07

Tue Nov 28, 2017 9:45 am

A few alternative modes to try:
The pi 3 can boot off some USB devices directly. I haven't read the other thread, but I assume you've tried that and it didn't work for your device.
If you just have a fat32 partition on an SD card with bootcode.bin, then more devices are supported. I think there are various ways to adjust the timeout to allow hard drives time to spin up, but I haven't used that personally.

Return to “Raspbian”

Who is online

Users browsing this forum: Google [Bot], k-pi, lgalex and 25 guests