[WANDBOARD QUAD] no network

This forum is for supported devices using an ARMv7 Freescale SoC.

[WANDBOARD QUAD] no network

Postby mkey2000 » Sun Jun 22, 2014 9:27 am

Hi@all,

I'm trying to install ARCH on my wandboard quad. First of all, I have the WB connected to a 2.5A Power Supply, my HDMI Monitor, Keyboard and Network cable. But unfortunately I can't get the network to run. And I can't figure out if this is a hardware bug or not. I'm running 3.10.17-2-ARCH. The Installation is rather fresh, no changes so far.

journalctl shows:
$this->bbcode_second_pass_code('', '-- Logs begin at Wed 1969-12-31 17:00:03 MST, end at Wed 1969-12-31 18:42:49 MST. --
Dec 31 17:00:03 alarm systemd-journal[163]: Runtime journal is using 8.0M (max allowed 87.5M, trying to leave 131.2M free of 867.3M available → current limit 87.5M).
Dec 31 17:00:03 alarm systemd-journal[163]: Runtime journal is using 8.0M (max allowed 87.5M, trying to leave 131.2M free of 867.3M available → current limit 87.5M).
Dec 31 17:00:03 alarm kernel: Booting Linux on physical CPU 0x0
Dec 31 17:00:03 alarm kernel: Initializing cgroup subsys cpuset
Dec 31 17:00:03 alarm kernel: Initializing cgroup subsys cpu
Dec 31 17:00:03 alarm kernel: Initializing cgroup subsys cpuacct
Dec 31 17:00:03 alarm kernel: Linux version 3.10.17-2-ARCH (nobody@root-chroot-copy) (gcc version 4.8.2 20131219 (prerelease) (GCC) ) #1 SMP Mon May 12 22:08:43 MDT 2014
Dec 31 17:00:03 alarm kernel: CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
Dec 31 17:00:03 alarm kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Dec 31 17:00:03 alarm kernel: Machine: Freescale i.MX6 Quad/DualLite (Device Tree), model: Wandboard Quad based on Freescale i.MX6 Quad
Dec 31 17:00:03 alarm kernel: Truncating RAM at 10000000-8fffffff to -7f7fffff (vmalloc region overlap).
Dec 31 17:00:03 alarm kernel: cma: CMA: reserved 256 MiB at 6e000000
Dec 31 17:00:03 alarm kernel: Memory policy: ECC disabled, Data cache writealloc
Dec 31 17:00:03 alarm kernel: On node 0 totalpages: 456704
Dec 31 17:00:03 alarm kernel: free_area_init_node: node 0, pgdat 80d71880, node_mem_map 80deb000
Dec 31 17:00:03 alarm kernel: DMA zone: 3568 pages used for memmap
Dec 31 17:00:03 alarm kernel: DMA zone: 0 pages reserved
Dec 31 17:00:03 alarm kernel: DMA zone: 456704 pages, LIFO batch:31
Dec 31 17:00:03 alarm kernel: PERCPU: Embedded 8 pages/cpu @81c02000 s9344 r8192 d15232 u32768
Dec 31 17:00:03 alarm kernel: pcpu-alloc: s9344 r8192 d15232 u32768 alloc=8*4096
Dec 31 17:00:03 alarm kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Dec 31 17:00:03 alarm kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 453136
Dec 31 17:00:03 alarm kernel: Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p1 rw rootwait video=
Dec 31 17:00:03 alarm kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
Dec 31 17:00:03 alarm kernel: Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
Dec 31 17:00:03 alarm kernel: Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
Dec 31 17:00:03 alarm kernel: allocated 3653632 bytes of page_cgroup
Dec 31 17:00:03 alarm kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Dec 31 17:00:03 alarm kernel: Memory: 1784MB = 1784MB total
Dec 31 17:00:03 alarm kernel: Memory: 1530168k/1530168k available, 296648k reserved, 0K highmem
Dec 31 17:00:03 alarm kernel: Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
lowmem : 0x80000000 - 0xef800000 (1784 MB)
modules : 0x7f000000 - 0x80000000 ( 16 MB)
.text : 0x80008000 - 0x80cbf5ac (13022 kB)
.init : 0x80cc0000 - 0x80d10480 ( 322 kB)
.data : 0x80d12000 - 0x80d729a0 ( 387 kB)
.bss : 0x80d729a0 - 0x80dea0d0 ( 478 kB)
Dec 31 17:00:03 alarm kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Dec 31 17:00:03 alarm kernel: Hierarchical RCU implementation.
Dec 31 17:00:03 alarm kernel: NR_IRQS:16 nr_irqs:16 16
Dec 31 17:00:03 alarm kernel: L310 cache controller enabled
Dec 31 17:00:03 alarm kernel: l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x32070000, Cache size: 1048576 B
Dec 31 17:00:03 alarm kernel: sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
Dec 31 17:00:03 alarm kernel: CPU identified as i.MX6Q, silicon rev 1.2
Dec 31 17:00:03 alarm kernel: Console: colour dummy device 80x30
Dec 31 17:00:03 alarm kernel: Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
Dec 31 17:00:03 alarm kernel: pid_max: default: 32768 minimum: 301
Dec 31 17:00:03 alarm kernel: Mount-cache hash table entries: 512
Dec 31 17:00:03 alarm kernel: Initializing cgroup subsys memory
Dec 31 17:00:03 alarm kernel: Initializing cgroup subsys devices
Dec 31 17:00:03 alarm kernel: Initializing cgroup subsys freezer
Dec 31 17:00:03 alarm kernel: Initializing cgroup subsys blkio
Dec 31 17:00:03 alarm kernel: Initializing cgroup subsys perf_event
Dec 31 17:00:03 alarm kernel: CPU: Testing write buffer coherency: ok
Dec 31 17:00:03 alarm kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Dec 31 17:00:03 alarm kernel: Setting up static identity map for 0x806b4b10 - 0x806b4b68
Dec 31 17:00:03 alarm kernel: CPU1: Booted secondary processor
Dec 31 17:00:03 alarm kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Dec 31 17:00:03 alarm kernel: CPU2: Booted secondary processor
Dec 31 17:00:03 alarm kernel: CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Dec 31 17:00:03 alarm kernel: CPU3: Booted secondary processor
Dec 31 17:00:03 alarm kernel: CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Dec 31 17:00:03 alarm kernel: Brought up 4 CPUs
Dec 31 17:00:03 alarm kernel: SMP: Total of 4 processors activated (6324.22 BogoMIPS).
Dec 31 17:00:03 alarm kernel: CPU: All CPU(s) started in SVC mode.
Dec 31 17:00:03 alarm kernel: devtmpfs: initialized
Dec 31 17:00:03 alarm kernel: xor: measuring software checksum speed
Dec 31 17:00:03 alarm kernel: arm4regs : 1102.000 MB/sec
Dec 31 17:00:03 alarm kernel: 8regs : 857.200 MB/sec
Dec 31 17:00:03 alarm kernel: 32regs : 902.000 MB/sec
Dec 31 17:00:03 alarm kernel: xor: using function: arm4regs (1102.000 MB/sec)
Dec 31 17:00:03 alarm kernel: pinctrl core: initialized pinctrl subsystem
Dec 31 17:00:03 alarm kernel: regulator-dummy: no parameters
Dec 31 17:00:03 alarm kernel: NET: Registered protocol family 16
Dec 31 17:00:03 alarm kernel: DMA: preallocated 256 KiB pool for atomic coherent allocations
Dec 31 17:00:03 alarm kernel: Use WDOG1 as reset source
Dec 31 17:00:03 alarm kernel: syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered
Dec 31 17:00:03 alarm kernel: vdd1p1: 800 <--> 1375 mV at 1125 mV
Dec 31 17:00:03 alarm kernel: vdd3p0: 2800 <--> 3150 mV at 3000 mV
Dec 31 17:00:03 alarm kernel: vdd2p5: 2000 <--> 2750 mV at 2425 mV
Dec 31 17:00:03 alarm kernel: cpu: 725 <--> 1450 mV at 1150 mV
Dec 31 17:00:03 alarm kernel: vddpu: 725 <--> 1450 mV at 1150 mV
Dec 31 17:00:03 alarm kernel: vddsoc: 725 <--> 1450 mV at 1175 mV
Dec 31 17:00:03 alarm kernel: syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered
Dec 31 17:00:03 alarm kernel: syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered
Dec 31 17:00:03 alarm kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
Dec 31 17:00:03 alarm kernel: hw-breakpoint: maximum watchpoint size is 4 bytes.
Dec 31 17:00:03 alarm kernel: imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
Dec 31 17:00:03 alarm kernel: bio: create slab <bio-0> at 0
Dec 31 17:00:03 alarm kernel: raid6: int32x1 91 MB/s
Dec 31 17:00:03 alarm kernel: raid6: int32x2 128 MB/s
Dec 31 17:00:03 alarm kernel: raid6: int32x4 128 MB/s
Dec 31 17:00:03 alarm kernel: raid6: int32x8 145 MB/s
Dec 31 17:00:03 alarm kernel: raid6: using algorithm int32x8 (145 MB/s)
Dec 31 17:00:03 alarm kernel: raid6: using intx1 recovery algorithm
Dec 31 17:00:03 alarm kernel: mxs-dma 110000.dma-apbh: initialized
Dec 31 17:00:03 alarm kernel: 1P8V: 1800 mV
Dec 31 17:00:03 alarm kernel: 2P5V: 2500 mV
Dec 31 17:00:03 alarm kernel: 3P3V: 3300 mV
Dec 31 17:00:03 alarm kernel: usb_otg_vbus: 5000 mV
Dec 31 17:00:03 alarm kernel: vgaarb: loaded
Dec 31 17:00:03 alarm kernel: i2c-core: driver [max17135] using legacy suspend method
Dec 31 17:00:03 alarm kernel: i2c-core: driver [max17135] using legacy resume method
Dec 31 17:00:03 alarm kernel: SCSI subsystem initialized
Dec 31 17:00:03 alarm kernel: libata version 3.00 loaded.
Dec 31 17:00:03 alarm kernel: usbcore: registered new interface driver usbfs
Dec 31 17:00:03 alarm kernel: usbcore: registered new interface driver hub
Dec 31 17:00:03 alarm kernel: usbcore: registered new device driver usb
Dec 31 17:00:03 alarm kernel: i2c i2c-0: IMX I2C adapter registered
Dec 31 17:00:03 alarm kernel: i2c i2c-1: IMX I2C adapter registered
Dec 31 17:00:03 alarm kernel: i2c i2c-2: IMX I2C adapter registered
Dec 31 17:00:03 alarm kernel: media: Linux media interface: v0.10
Dec 31 17:00:03 alarm kernel: Linux video capture interface: v2.00
Dec 31 17:00:03 alarm kernel: pps_core: LinuxPPS API ver. 1 registered
Dec 31 17:00:03 alarm kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Dec 31 17:00:03 alarm kernel: PTP clock support registered
Dec 31 17:00:03 alarm kernel: imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Dec 31 17:00:03 alarm kernel: imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Dec 31 17:00:03 alarm kernel: mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 driver probed
Dec 31 17:00:03 alarm kernel: mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 dphy version is 0x3130302a
Dec 31 17:00:03 alarm kernel: MIPI CSI2 driver module loaded
Dec 31 17:00:03 alarm kernel: Advanced Linux Sound Architecture Driver Initialized.
Dec 31 17:00:03 alarm kernel: cfg80211: Calling CRDA to update world regulatory domain
Dec 31 17:00:03 alarm kernel: Switching to clocksource mxc_timer1
Dec 31 17:00:03 alarm kernel: imx6q-pcie 1ffc000.pcie: phy link never came up
Dec 31 17:00:03 alarm kernel: PCI host bridge to bus 0000:00
Dec 31 17:00:03 alarm kernel: pci_bus 0000:00: root bus resource [io 0x1000-0x10000]
Dec 31 17:00:03 alarm kernel: pci_bus 0000:00: root bus resource [mem 0x01000000-0x01efffff]
Dec 31 17:00:03 alarm kernel: pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
Dec 31 17:00:03 alarm kernel: pci 0000:00:00.0: [16c3:abcd] type 01 class 0x060400
Dec 31 17:00:03 alarm kernel: pci 0000:00:00.0: reg 10: [mem 0x00000000-0x000fffff]
Dec 31 17:00:03 alarm kernel: pci 0000:00:00.0: reg 38: [mem 0x00000000-0x0000ffff pref]
Dec 31 17:00:03 alarm kernel: pci 0000:00:00.0: supports D1
Dec 31 17:00:03 alarm kernel: pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
Dec 31 17:00:03 alarm kernel: PCI: bus0: Fast back to back transfers disabled
Dec 31 17:00:03 alarm kernel: PCI: bus1: Fast back to back transfers enabled
Dec 31 17:00:03 alarm kernel: pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
Dec 31 17:00:03 alarm kernel: pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 01
Dec 31 17:00:03 alarm kernel: pci 0000:00:00.0: BAR 0: assigned [mem 0x01000000-0x010fffff]
Dec 31 17:00:03 alarm kernel: pci 0000:00:00.0: BAR 6: assigned [mem 0x01100000-0x0110ffff pref]
Dec 31 17:00:03 alarm kernel: pci 0000:00:00.0: PCI bridge to [bus 01]
Dec 31 17:00:03 alarm kernel: pci_bus 0000:00: resource 4 [io 0x1000-0x10000]
Dec 31 17:00:03 alarm kernel: pci_bus 0000:00: resource 5 [mem 0x01000000-0x01efffff]
Dec 31 17:00:03 alarm kernel: NET: Registered protocol family 2
Dec 31 17:00:03 alarm kernel: TCP established hash table entries: 16384 (order: 5, 131072 bytes)
Dec 31 17:00:03 alarm kernel: TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
Dec 31 17:00:03 alarm kernel: TCP: Hash tables configured (established 16384 bind 16384)
Dec 31 17:00:03 alarm kernel: TCP: reno registered
Dec 31 17:00:03 alarm kernel: UDP hash table entries: 1024 (order: 3, 32768 bytes)
Dec 31 17:00:03 alarm kernel: UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
Dec 31 17:00:03 alarm kernel: NET: Registered protocol family 1
Dec 31 17:00:03 alarm kernel: RPC: Registered named UNIX socket transport module.
Dec 31 17:00:03 alarm kernel: RPC: Registered udp transport module.
Dec 31 17:00:03 alarm kernel: RPC: Registered tcp transport module.
Dec 31 17:00:03 alarm kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Dec 31 17:00:03 alarm kernel: PCI: CLS 64 bytes, default 64
Dec 31 17:00:03 alarm kernel: hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
Dec 31 17:00:03 alarm kernel: pureg-dummy: no parameters
Dec 31 17:00:03 alarm kernel: imx6_busfreq busfreq.15: DDR medium rate not supported.
Dec 31 17:00:03 alarm kernel: Bus freq driver module loaded
Dec 31 17:00:03 alarm kernel: wandboard-rfkill rfkill.25: Wandboard rfkill initialization
Dec 31 17:00:03 alarm kernel: wandboard-rfkill rfkill.25: initialize wifi chip
Dec 31 17:00:03 alarm kernel: wandboard-rfkill rfkill.25: wifi-rfkill registered.
Dec 31 17:00:03 alarm kernel: wandboard-rfkill rfkill.25: initialize bluetooth chip
Dec 31 17:00:03 alarm kernel: wandboard-rfkill rfkill.25: bluetooth-rfkill registered.
Dec 31 17:00:03 alarm kernel: VFS: Disk quotas dquot_6.5.2
Dec 31 17:00:03 alarm kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Dec 31 17:00:03 alarm kernel: NFS: Registering the id_resolver key type
Dec 31 17:00:03 alarm kernel: Key type id_resolver registered
Dec 31 17:00:03 alarm kernel: Key type id_legacy registered
Dec 31 17:00:03 alarm kernel: jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
Dec 31 17:00:03 alarm kernel: fuse init (API version 7.22)
Dec 31 17:00:03 alarm kernel: bio: create slab <bio-1> at 1
Dec 31 17:00:03 alarm kernel: Btrfs loaded
Dec 31 17:00:03 alarm kernel: msgmni has been set to 3500
Dec 31 17:00:03 alarm kernel: async_tx: api initialized (async)
Dec 31 17:00:03 alarm kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
Dec 31 17:00:03 alarm kernel: io scheduler noop registered
Dec 31 17:00:03 alarm kernel: io scheduler deadline registered
Dec 31 17:00:03 alarm kernel: io scheduler cfq registered (default)
Dec 31 17:00:03 alarm kernel: imx-weim 21b8000.weim: WEIM driver registered.
Dec 31 17:00:03 alarm kernel: MIPI DSI driver module loaded
Dec 31 17:00:03 alarm kernel: mxc_sdc_fb fb.26: register mxc display driver hdmi
Dec 31 17:00:03 alarm kernel: mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1
Dec 31 17:00:03 alarm kernel: fbcvt: 1920x1080@60: CVT Name - 2.073M9
Dec 31 17:00:03 alarm kernel: mxc_sdc_fb fb.26: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
Dec 31 17:00:03 alarm kernel: imx-ipuv3 2400000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
Dec 31 17:00:03 alarm kernel: mxc_sdc_fb fb.26: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
Dec 31 17:00:03 alarm kernel: Console: switching to colour frame buffer device 240x67
Dec 31 17:00:03 alarm kernel: imx-sdma 20ec000.sdma: no iram assigned, using external mem
Dec 31 17:00:03 alarm kernel: imx-sdma 20ec000.sdma: loaded firmware 1.1
Dec 31 17:00:03 alarm kernel: imx-sdma 20ec000.sdma: initialized
Dec 31 17:00:03 alarm kernel: Serial: IMX driver
Dec 31 17:00:03 alarm kernel: 2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
Dec 31 17:00:03 alarm kernel: console [ttymxc0] enabled
Dec 31 17:00:03 alarm kernel: 21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX
Dec 31 17:00:03 alarm kernel: serial: Freescale lpuart driver
Dec 31 17:00:03 alarm kernel: [drm] Initialized drm 1.1.0 20060810
Dec 31 17:00:03 alarm kernel: [drm] Initialized vivante 1.0.0 20120216 on minor 0
Dec 31 17:00:03 alarm kernel: brd: module loaded
Dec 31 17:00:03 alarm kernel: loop: module loaded
Dec 31 17:00:03 alarm kernel: Wait for CR ACK error!
Dec 31 17:00:03 alarm kernel: sata phy RX_PLL is stable!
Dec 31 17:00:03 alarm kernel: ahci: SSS flag set, parallel bus scan disabled
Dec 31 17:00:03 alarm kernel: ahci ahci: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
Dec 31 17:00:03 alarm kernel: ahci ahci: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst
Dec 31 17:00:03 alarm kernel: mxc_hdmi 20e0000.hdmi_video: Read EDID again
Dec 31 17:00:03 alarm kernel: mxc_hdmi 20e0000.hdmi_video: No modes read from edid
Dec 31 17:00:03 alarm kernel: mxc_hdmi 20e0000.hdmi_video: create default modelist
Dec 31 17:00:03 alarm kernel: scsi0 : ahci_platform
Dec 31 17:00:03 alarm kernel: ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71
Dec 31 17:00:03 alarm kernel: libphy: fec_enet_mii_bus: probed
Dec 31 17:00:03 alarm kernel: fec 2188000.ethernet eth0: registered PHC device 0
Dec 31 17:00:03 alarm kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Dec 31 17:00:03 alarm kernel: ehci-pci: EHCI PCI platform driver
Dec 31 17:00:03 alarm kernel: usbcore: registered new interface driver usb-storage
Dec 31 17:00:03 alarm kernel: mxc_sdc_fb fb.26: 640x480 h_sync,r,l: 96,16,48 v_sync,l,u: 2,10,33 pixclock=25175000 Hz
Dec 31 17:00:03 alarm kernel: ci_hdrc ci_hdrc.1: doesn't support gadget
Dec 31 17:00:03 alarm kernel: ci_hdrc ci_hdrc.1: EHCI Host Controller
Dec 31 17:00:03 alarm kernel: ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
Dec 31 17:00:03 alarm kernel: ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
Dec 31 17:00:03 alarm kernel: hub 1-0:1.0: USB hub found
Dec 31 17:00:03 alarm kernel: hub 1-0:1.0: 1 port detected
Dec 31 17:00:03 alarm kernel: mousedev: PS/2 mouse device common for all mice
Dec 31 17:00:03 alarm kernel: i2c-core: driver [isl29023] using legacy suspend method
Dec 31 17:00:03 alarm kernel: i2c-core: driver [isl29023] using legacy resume method
Dec 31 17:00:03 alarm kernel: snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0
Dec 31 17:00:03 alarm kernel: i2c /dev entries driver
Dec 31 17:00:03 alarm kernel: mxc_v4l2_output v4l2_out.28: V4L2 device registered as video16
Dec 31 17:00:03 alarm kernel: mxc_v4l2_output v4l2_out.28: V4L2 device registered as video17
Dec 31 17:00:03 alarm kernel: i2c-core: driver [mag3110] using legacy suspend method
Dec 31 17:00:03 alarm kernel: i2c-core: driver [mag3110] using legacy resume method
Dec 31 17:00:03 alarm kernel: imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
Dec 31 17:00:03 alarm kernel: md: raid1 personality registered for level 1
Dec 31 17:00:03 alarm kernel: md: raid10 personality registered for level 10
Dec 31 17:00:03 alarm kernel: md: raid6 personality registered for level 6
Dec 31 17:00:03 alarm kernel: md: raid5 personality registered for level 5
Dec 31 17:00:03 alarm kernel: md: raid4 personality registered for level 4
Dec 31 17:00:03 alarm kernel: cpuidle: using governor ladder
Dec 31 17:00:03 alarm kernel: cpuidle: using governor menu
Dec 31 17:00:03 alarm kernel: sdhci: Secure Digital Host Controller Interface driver
Dec 31 17:00:03 alarm kernel: sdhci: Copyright(c) Pierre Ossman
Dec 31 17:00:03 alarm kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Dec 31 17:00:03 alarm kernel: sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed state, work on normal mode
Dec 31 17:00:03 alarm kernel: mmc0: no vqmmc regulator found
Dec 31 17:00:03 alarm kernel: mmc0: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
Dec 31 17:00:03 alarm kernel: sdhci-esdhc-imx 2194000.usdhc: could not get ultra high speed state, work on normal mode
Dec 31 17:00:03 alarm kernel: mmc1: no vqmmc regulator found
Dec 31 17:00:03 alarm kernel: mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
Dec 31 17:00:03 alarm kernel: sdhci-esdhc-imx 2190000.usdhc: could not get ultra high speed state, work on normal mode
Dec 31 17:00:03 alarm kernel: mmc2: no vqmmc regulator found
Dec 31 17:00:03 alarm kernel: mmc0: host does not support reading read-only switch. assuming write-enable.
Dec 31 17:00:03 alarm kernel: mmc0: new high speed SDHC card at address aaaa
Dec 31 17:00:03 alarm kernel: mmcblk0: mmc0:aaaa SL08G 7.40 GiB
Dec 31 17:00:03 alarm kernel: mmcblk0: p1
Dec 31 17:00:03 alarm kernel: mmc2: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA
Dec 31 17:00:03 alarm kernel: usb 1-1: new full-speed USB device number 2 using ci_hdrc
Dec 31 17:00:03 alarm kernel: ata1: SATA link down (SStatus 0 SControl 300)
Dec 31 17:00:03 alarm kernel: mxc_sdc_fb fb.26: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
Dec 31 17:00:03 alarm kernel: mmc1: queuing unknown CIS tuple 0x80 (50 bytes)
Dec 31 17:00:03 alarm kernel: mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Dec 31 17:00:03 alarm kernel: mmc1: queuing unknown CIS tuple 0x80 (4 bytes)
Dec 31 17:00:03 alarm kernel: mmc1: queuing unknown CIS tuple 0x02 (1 bytes)
Dec 31 17:00:03 alarm kernel: mmc1: new SDIO card at address 0001
Dec 31 17:00:03 alarm kernel: Galcore version 4.6.9.9754
Dec 31 17:00:03 alarm kernel: mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
Dec 31 17:00:03 alarm kernel: mxc_asrc 2034000.asrc: mxc_asrc registered
Dec 31 17:00:03 alarm kernel: mxc_vpu 2040000.vpu: VPU initialized
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: device ID = 0x0a16010000000000 (Era -524)
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: job rings = 2, qi = 0
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-md5-cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-md5-cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha1-cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha1-cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha224-cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha224-cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha256-cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha256-cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-md5-cbc-des3_ede-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-md5-cbc-des3_ede-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha1-cbc-des3_ede-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha1-cbc-des3_ede-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha224-cbc-des3_ede-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha224-cbc-des3_ede-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha256-cbc-des3_ede-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha256-cbc-des3_ede-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-md5-cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-md5-cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha1-cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha1-cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha224-cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha224-cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authenc-hmac-sha256-cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: authencesn-hmac-sha256-cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: ecb-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: ecb-arc4-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: ecb-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: ctr-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: cbc-aes-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: ecb-des3-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: cbc-3des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: cbc-des-caam
Dec 31 17:00:03 alarm kernel: caam 2100000.caam: fsl,sec-v4.0 algorithms registered in /proc/crypto
Dec 31 17:00:03 alarm kernel: platform 2101000.jr0: registering rng-caam
Dec 31 17:00:03 alarm kernel: platform caam_sm: caam_sm_test: 8-byte key test match OK
Dec 31 17:00:03 alarm kernel: platform caam_sm: caam_sm_test: 16-byte key test match OK
Dec 31 17:00:03 alarm kernel: platform caam_sm: caam_sm_test: 32-byte key test match OK
Dec 31 17:00:03 alarm kernel: platform caam_secvio.29: security violation service handlers armed
Dec 31 17:00:03 alarm kernel: hidraw: raw HID events driver (C) Jiri Kosina
Dec 31 17:00:03 alarm kernel: input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/soc0/soc.1/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1:1.0/input/input0
Dec 31 17:00:03 alarm kernel: hid-generic 0003:045E:0800.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v2.0] on usb-ci_hdrc.1-1/input0
Dec 31 17:00:03 alarm kernel: input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/soc0/soc.1/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1:1.1/input/input1
Dec 31 17:00:03 alarm kernel: hid-generic 0003:045E:0800.0002: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v2.0] on usb-ci_hdrc.1-1/input1
Dec 31 17:00:03 alarm kernel: input: Microsoft Microsoft® Nano Transceiver v2.0 as /devices/soc0/soc.1/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1:1.2/input/input2
Dec 31 17:00:03 alarm kernel: hid-generic 0003:045E:0800.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v2.0] on usb-ci_hdrc.1-1/input2
Dec 31 17:00:03 alarm kernel: usbcore: registered new interface driver usbhid
Dec 31 17:00:03 alarm kernel: usbhid: USB HID core driver
Dec 31 17:00:03 alarm kernel: i2c-core: driver [cs42888] using legacy suspend method
Dec 31 17:00:03 alarm kernel: i2c-core: driver [cs42888] using legacy resume method
Dec 31 17:00:03 alarm kernel: sgtl5000 1-000a: sgtl5000 revision 0x11
Dec 31 17:00:03 alarm kernel: sgtl5000 1-000a: Failed to get supply 'VDDD': -19
Dec 31 17:00:03 alarm kernel: 1-000a: 1200 mV normal
Dec 31 17:00:03 alarm kernel: sgtl5000 1-000a: Using internal LDO instead of VDDD
Dec 31 17:00:03 alarm kernel: imx-sgtl5000 sound.22: sgtl5000 <-> 2028000.ssi mapping ok
Dec 31 17:00:03 alarm kernel: imx-spdif sound-spdif.23: dit-hifi <-> 2004000.spdif mapping ok
Dec 31 17:00:03 alarm kernel: imx-audio-hdmi sound-hdmi.24: hdmi-hifi <-> hdmi_audio.16 mapping ok
Dec 31 17:00:03 alarm kernel: TCP: cubic registered
Dec 31 17:00:03 alarm kernel: NET: Registered protocol family 10
Dec 31 17:00:03 alarm kernel: mip6: Mobile IPv6
Dec 31 17:00:03 alarm kernel: NET: Registered protocol family 17
Dec 31 17:00:03 alarm kernel: Key type dns_resolver registered
Dec 31 17:00:03 alarm kernel: VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Dec 31 17:00:03 alarm kernel: Registering SWP/SWPB emulation handler
Dec 31 17:00:03 alarm kernel: registered taskstats version 1
Dec 31 17:00:03 alarm kernel: console [netcon0] enabled
Dec 31 17:00:03 alarm kernel: netconsole: network logging started
Dec 31 17:00:03 alarm kernel: snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:01 UTC (1)
Dec 31 17:00:03 alarm kernel: ALSA device list:
Dec 31 17:00:03 alarm kernel: #0: imx6-wandboard-sgtl5000
Dec 31 17:00:03 alarm kernel: #1: imx-spdif
Dec 31 17:00:03 alarm kernel: #2: imx-hdmi-soc
Dec 31 17:00:03 alarm kernel: md: Waiting for all devices to be available before autodetect
Dec 31 17:00:03 alarm kernel: md: If you don't use raid, use raid=noautodetect
Dec 31 17:00:03 alarm kernel: md: Autodetecting RAID arrays.
Dec 31 17:00:03 alarm kernel: md: Scanned 0 and added 0 devices.
Dec 31 17:00:03 alarm kernel: md: autorun ...
Dec 31 17:00:03 alarm kernel: md: ... autorun DONE.
Dec 31 17:00:03 alarm kernel: EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature incompatibilities
Dec 31 17:00:03 alarm kernel: EXT4-fs (mmcblk0p1): couldn't mount as ext2 due to feature incompatibilities
Dec 31 17:00:03 alarm kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
Dec 31 17:00:03 alarm kernel: VFS: Mounted root (ext4 filesystem) on device 179:1.
Dec 31 17:00:03 alarm kernel: devtmpfs: mounted
Dec 31 17:00:03 alarm kernel: Freeing unused kernel memory: 320K (80cc0000 - 80d10000)
Dec 31 17:00:03 alarm systemd[1]: systemd 212 running in system mode. (+PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR)
Dec 31 17:00:03 alarm systemd[1]: Detected architecture 'arm'.
Dec 31 17:00:03 alarm systemd[1]: Set hostname to <alarm>.
Dec 31 17:00:03 alarm systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Dec 31 17:00:03 alarm systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
Dec 31 17:00:03 alarm systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Dec 31 17:00:03 alarm systemd[1]: Expecting device dev-ttymxc0.device...
Dec 31 17:00:03 alarm systemd[1]: Starting Remote File Systems.
Dec 31 17:00:03 alarm systemd[1]: Reached target Remote File Systems.
Dec 31 17:00:03 alarm systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
Dec 31 17:00:03 alarm systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
Dec 31 17:00:03 alarm systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Dec 31 17:00:03 alarm systemd[1]: Starting Paths.
Dec 31 17:00:03 alarm systemd[1]: Reached target Paths.
Dec 31 17:00:03 alarm systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
Dec 31 17:00:03 alarm systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Dec 31 17:00:03 alarm systemd[1]: Starting Encrypted Volumes.
Dec 31 17:00:03 alarm systemd[1]: Reached target Encrypted Volumes.
Dec 31 17:00:03 alarm systemd[1]: Starting Swap.
Dec 31 17:00:03 alarm systemd[1]: Reached target Swap.
Dec 31 17:00:03 alarm systemd[1]: Starting Root Slice.
Dec 31 17:00:03 alarm systemd[1]: Created slice Root Slice.
Dec 31 17:00:03 alarm systemd[1]: Starting Delayed Shutdown Socket.
Dec 31 17:00:03 alarm systemd[1]: Listening on Delayed Shutdown Socket.
Dec 31 17:00:03 alarm systemd[1]: Starting Device-mapper event daemon FIFOs.
Dec 31 17:00:03 alarm systemd[1]: Listening on Device-mapper event daemon FIFOs.
Dec 31 17:00:03 alarm systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
Dec 31 17:00:03 alarm systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
Dec 31 17:00:03 alarm systemd[1]: Starting udev Control Socket.
Dec 31 17:00:03 alarm systemd[1]: Listening on udev Control Socket.
Dec 31 17:00:03 alarm systemd[1]: Starting udev Kernel Socket.
Dec 31 17:00:03 alarm systemd[1]: Listening on udev Kernel Socket.
Dec 31 17:00:03 alarm systemd[1]: Starting LVM2 metadata daemon socket.
Dec 31 17:00:03 alarm systemd[1]: Listening on LVM2 metadata daemon socket.
Dec 31 17:00:03 alarm systemd[1]: Starting User and Session Slice.
Dec 31 17:00:03 alarm systemd[1]: Created slice User and Session Slice.
Dec 31 17:00:03 alarm systemd[1]: Starting Journal Socket.
Dec 31 17:00:03 alarm systemd[1]: Listening on Journal Socket.
Dec 31 17:00:03 alarm systemd[1]: Starting System Slice.
Dec 31 17:00:03 alarm systemd[1]: Created slice System Slice.
Dec 31 17:00:03 alarm systemd[1]: Starting Create list of required static device nodes for the current kernel...
Dec 31 17:00:03 alarm systemd[1]: Starting Apply Kernel Variables...
Dec 31 17:00:03 alarm systemd[1]: Starting udev Coldplug all Devices...
Dec 31 17:00:03 alarm systemd[1]: Mounting Debug File System...
Dec 31 17:00:03 alarm systemd[1]: Mounted Huge Pages File System.
Dec 31 17:00:03 alarm systemd[1]: Starting Setup Virtual Console...
Dec 31 17:00:03 alarm systemd[1]: Mounting POSIX Message Queue File System...
Dec 31 17:00:03 alarm systemd[1]: Started Set Up Additional Binary Formats.
Dec 31 17:00:03 alarm systemd[1]: Starting system-netctl\x2difplugd.slice.
Dec 31 17:00:03 alarm systemd[1]: Created slice system-netctl\x2difplugd.slice.
Dec 31 17:00:03 alarm systemd[1]: Starting system-getty.slice.
Dec 31 17:00:03 alarm systemd[1]: Created slice system-getty.slice.
Dec 31 17:00:03 alarm systemd[1]: Starting system-serial\x2dgetty.slice.
Dec 31 17:00:03 alarm systemd[1]: Created slice system-serial\x2dgetty.slice.
Dec 31 17:00:03 alarm systemd[1]: Started Load Kernel Modules.
Dec 31 17:00:03 alarm systemd[1]: Mounting FUSE Control File System...
Dec 31 17:00:03 alarm systemd[1]: Mounted Configuration File System.
Dec 31 17:00:03 alarm systemd[1]: Starting Journal Service...
Dec 31 17:00:03 alarm systemd[1]: Started Journal Service.
Dec 31 17:00:03 alarm systemd-journal[163]: Journal started
Dec 31 17:00:03 alarm systemd[1]: Starting Slices.
Dec 31 17:00:03 alarm systemd[1]: Reached target Slices.
Dec 31 17:00:03 alarm systemd[1]: Mounting Temporary Directory...
Dec 31 17:00:03 alarm systemd[1]: Starting Remount Root and Kernel File Systems...
Dec 31 17:00:03 alarm systemd[1]: Mounted POSIX Message Queue File System.
Dec 31 17:00:03 alarm systemd[1]: Mounted Debug File System.
Dec 31 17:00:03 alarm systemd[1]: Mounted FUSE Control File System.
Dec 31 17:00:03 alarm systemd[1]: Mounted Temporary Directory.
Dec 31 17:00:03 alarm systemd[1]: Started Create list of required static device nodes for the current kernel.
Dec 31 17:00:03 alarm systemd[1]: Started Apply Kernel Variables.
Dec 31 17:00:03 alarm systemd[1]: Started Setup Virtual Console.
Dec 31 17:00:03 alarm systemd[1]: Started Remount Root and Kernel File Systems.
Dec 31 17:00:03 alarm systemd[1]: Starting Load/Save Random Seed...
Dec 31 17:00:03 alarm systemd[1]: Starting Create Static Device Nodes in /dev...
Dec 31 17:00:03 alarm systemd[1]: Started udev Coldplug all Devices.
Dec 31 17:00:03 alarm systemd[1]: Started Load/Save Random Seed.
Dec 31 17:00:03 alarm systemd[1]: Started Create Static Device Nodes in /dev.
Dec 31 17:00:03 alarm systemd[1]: Starting udev Kernel Device Manager...
Dec 31 17:00:03 alarm systemd[1]: Starting Local File Systems (Pre).
Dec 31 17:00:03 alarm systemd[1]: Reached target Local File Systems (Pre).
Dec 31 17:00:03 alarm systemd[1]: Starting Local File Systems.
Dec 31 17:00:03 alarm systemd-udevd[174]: starting version 212
Dec 31 17:00:03 alarm systemd[1]: Reached target Local File Systems.
Dec 31 17:00:03 alarm systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Dec 31 17:00:03 alarm systemd[1]: Starting Create Volatile Files and Directories...
Dec 31 17:00:03 alarm systemd[1]: Started udev Kernel Device Manager.
Dec 31 17:00:03 alarm systemd[1]: Started Create Volatile Files and Directories.
Dec 31 17:00:04 alarm systemd-journal[163]: Permanent journal is using 8.0M (max allowed 732.8M, trying to leave 1.0G free of 6.3G available → current limit 732.8M).
Dec 31 17:00:04 alarm systemd-journal[163]: Time spent on flushing to /var is 74.869ms for 435 entries.
Dec 31 17:00:04 alarm kernel: ov5640_read_reg:write reg error:reg=300a
Dec 31 17:00:04 alarm kernel: camera ov5640_mipi is not found
Dec 31 17:00:04 alarm kernel: evbug: Connected device: input0 (Microsoft Microsoft® Nano Transceiver v2.0 at usb-ci_hdrc.1-1/input0)
Dec 31 17:00:04 alarm kernel: evbug: Connected device: input1 (Microsoft Microsoft® Nano Transceiver v2.0 at usb-ci_hdrc.1-1/input1)
Dec 31 17:00:04 alarm kernel: evbug: Connected device: input2 (Microsoft Microsoft® Nano Transceiver v2.0 at usb-ci_hdrc.1-1/input2)
Dec 31 17:00:04 alarm kernel: brcmfmac: F1 signature read @0x18000000=0x9934329
Dec 31 17:00:04 alarm kernel: brcmfmac: brcmf_sdio_chip_drivestrengthinit: No SDIO Drive strength init done for chip 4329 rev 3 pmurev 6
Dec 31 17:00:04 alarm kernel: ERROR: v4l2 capture: slave not found!
Dec 31 17:00:04 alarm kernel: unable to find transceiver of type USB3 PHY
Dec 31 17:00:04 alarm kernel: dwc3 dwc3.0.auto: no usb3 phy configured
Dec 31 17:00:04 alarm kernel: platform dwc3.0.auto: Driver dwc3 requests probe deferral
Dec 31 17:00:03 alarm systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Dec 31 17:00:03 alarm systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Dec 31 17:00:04 alarm systemd[1]: Found device /dev/ttymxc0.
Dec 31 17:00:04 alarm systemd[1]: Started Update UTMP about System Boot/Shutdown.
Dec 31 17:00:04 alarm systemd[1]: Starting system-systemd\x2drfkill.slice.
Dec 31 17:00:04 alarm systemd[1]: Created slice system-systemd\x2drfkill.slice.
Dec 31 17:00:04 alarm systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill1...
Dec 31 17:00:04 alarm systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill0...
Dec 31 17:00:04 alarm systemd[1]: Started Load/Save RF Kill Switch Status of rfkill1.
Dec 31 17:00:04 alarm systemd[1]: Started Load/Save RF Kill Switch Status of rfkill0.
Dec 31 17:00:04 alarm systemd[1]: Found device /sys/subsystem/net/devices/eth0.
Dec 31 17:00:04 alarm systemd[1]: Reached target Sockets.
Dec 31 17:00:04 alarm systemd[1]: Starting Daily rotation of log files.
Dec 31 17:00:04 alarm systemd[1]: Started Daily rotation of log files.
Dec 31 17:00:04 alarm systemd[1]: Starting Daily Cleanup of Temporary Directories.
Dec 31 17:00:04 alarm systemd[1]: Started Daily Cleanup of Temporary Directories.
Dec 31 17:00:04 alarm systemd[1]: Starting Daily verification of password and group files.
Dec 31 17:00:04 alarm systemd[1]: Started Daily verification of password and group files.
Dec 31 17:00:04 alarm systemd[1]: Starting Timers.
Dec 31 17:00:04 alarm kernel: brcmfmac: brcmf_sdbrcm_download_code_file: Fail to request firmware -2
Dec 31 17:00:04 alarm kernel: brcmfmac: _brcmf_sdbrcm_download_firmware: dongle image file download failed
Dec 31 17:00:04 alarm kernel: brcmfmac: brcmf_bus_start: brcmf_sdbrcm_bus_init failed -1
Dec 31 17:00:04 alarm kernel: brcmfmac: brcmf_sdbrcm_probe: dongle is not responding
Dec 31 17:00:04 alarm kernel: brcmfmac: brcmf_sdio_probe: device attach failed
Dec 31 17:00:04 alarm kernel: brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...
Dec 31 17:00:04 alarm kernel: usbcore: registered new interface driver brcmfmac
Dec 31 17:00:04 alarm systemd[1]: Reached target Timers.
Dec 31 17:00:04 alarm systemd[1]: Starting Basic System.
Dec 31 17:00:04 alarm systemd[1]: Reached target Basic System.
Dec 31 17:00:04 alarm systemd[1]: Starting Entropy Harvesting Daemon...
Dec 31 17:00:04 alarm systemd[1]: Starting Automatic wired network connection using netctl profiles...
Dec 31 17:00:04 alarm ifplugd[215]: ifplugd 0.28 initializing.
Dec 31 17:00:04 alarm kernel: unable to find transceiver of type USB3 PHY
Dec 31 17:00:04 alarm kernel: dwc3 dwc3.0.auto: no usb3 phy configured
Dec 31 17:00:04 alarm kernel: platform dwc3.0.auto: Driver dwc3 requests probe deferral
Dec 31 17:00:04 alarm haveged[214]: haveged starting up
Dec 31 17:00:04 alarm kernel: fec 2188000.ethernet eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=2188000.ethernet:01, irq=-1)
Dec 31 17:00:04 alarm kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 31 17:00:04 alarm systemd[1]: Started Automatic wired network connection using netctl profiles.
Dec 31 17:00:04 alarm systemd[1]: Starting SSH Key Generation...
Dec 31 17:00:04 alarm ifplugd[215]: Using interface eth0/00:1F:7B:B4:03:2E with driver <fec> (version: Revision: 1.0)
Dec 31 17:00:04 alarm ifplugd[215]: Using detection mode: SIOCETHTOOL
Dec 31 17:00:04 alarm ifplugd[215]: Initialization complete, link beat not detected.
Dec 31 17:00:04 alarm systemd[1]: Starting Permit User Sessions...
Dec 31 17:00:04 alarm systemd[1]: Starting Login Service...
Dec 31 17:00:05 alarm systemd[1]: Starting D-Bus System Message Bus...
Dec 31 17:00:05 alarm systemd[1]: Started D-Bus System Message Bus.
Dec 31 17:00:05 alarm systemd[1]: Starting Sound Card.
Dec 31 17:00:05 alarm systemd[1]: Reached target Sound Card.
Dec 31 17:00:05 alarm systemd[1]: Started Entropy Harvesting Daemon.
Dec 31 17:00:05 alarm systemd[1]: Started Permit User Sessions.
Dec 31 17:00:05 alarm systemd[1]: Starting Getty on tty1...
Dec 31 17:00:05 alarm systemd-logind[220]: New seat seat0.
Dec 31 17:00:05 alarm systemd[1]: Started Getty on tty1.
Dec 31 17:00:05 alarm systemd[1]: Starting Serial Getty on ttymxc0...
Dec 31 17:00:05 alarm systemd[1]: Started Serial Getty on ttymxc0.
Dec 31 17:00:05 alarm systemd[1]: Starting Login Prompts.
Dec 31 17:00:05 alarm systemd[1]: Reached target Login Prompts.
Dec 31 17:00:05 alarm systemd[1]: Started Login Service.
Dec 31 17:00:06 alarm haveged[216]: haveged: ver: 1.9.1; arch: generic; vend: ; build: (gcc 4.8.2 CTV); collect: 128K
Dec 31 17:00:06 alarm haveged[216]: haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 8/40; sz: 15180/73928
Dec 31 17:00:06 alarm haveged[216]: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 8.00369
Dec 31 17:00:06 alarm haveged[216]: haveged: fills: 0, generated: 0
Dec 31 17:00:07 alarm kernel: libphy: 2188000.ethernet:01 - Link is Up - 100/Full
Dec 31 17:00:07 alarm kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec 31 17:00:07 alarm ifplugd[215]: Link beat detected.
Dec 31 17:00:08 alarm ifplugd[215]: Executing '/etc/ifplugd/netctl.action eth0 up'.
Dec 31 17:00:09 alarm ifplugd[215]: client: up
Dec 31 17:00:09 alarm ifplugd[215]: client: Reading profile 'eth0'
Dec 31 17:00:09 alarm ifplugd[215]: client: Starting network profile 'eth0'...
Dec 31 17:00:09 alarm dhcpcd[238]: version 6.3.2 starting
Dec 31 17:00:09 alarm dhcpcd[238]: DUID 00:01:00:01:c7:92:bc:89:00:1f:7b:b4:03:2e
Dec 31 17:00:09 alarm dhcpcd[238]: eth0: IAID 7b:b4:03:2e
Dec 31 17:00:09 alarm dhcpcd[238]: eth0: soliciting a DHCP lease
Dec 31 17:00:09 alarm dhcpcd[238]: eth0: offered 192.168.1.171 from 192.168.1.1
Dec 31 17:00:09 alarm kernel: fec 2188000.ethernet eth0: rcv is not +last
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458773
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 19, Value: 1
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458773
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 19, Value: 0
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458770
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 24, Value: 1
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458770
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 24, Value: 0
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458770
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 24, Value: 1
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458770
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 24, Value: 0
Dec 31 17:00:16 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458775
D')
Is this a driver issue?
Any help would be appreciated.

P.s.: I used the Instructions on http://archlinuxarm.org/platforms/armv7 ... /wandboard to set up my SD Card
mkey2000
 
Posts: 9
Joined: Sun Jun 22, 2014 9:10 am

Re: [WANDBOARD QUAD] no network

Postby Yenal » Sun Jun 22, 2014 5:22 pm

what is the output of:
$ ip link
do you use LAN or WLAN?

LAN: should work without problems..maybe you need to use dhclient instead of dhcpcd
WLAN: afaik there is no wpa_supplicant in the basic image and the wlan firmware isnt correct.. in /usr/lib/firmware/brcm/ there should be brcmfmac-sdio.bin (which is a copy of brcmfmac4329-sdio.bin) and brcmfmac-sdio.txt (which you can get from https://raw.github.com/Freescale/meta-f ... /nvram.txt or wandboard-sdk-20140519.tar.xz)
after reboot "ip link" should list the wlan module, then you can use wpa_passphrase and wpa_supplicant to connect to your wifi network

PS: you can also use my PKGBUILD to manage the firmware stuff (https://raw.githubusercontent.com/Yenal ... e/PKGBUILD)

edit: oh and what I found out: trying to connect wlan at boot (using netctl or a rc.local-service executing wpa_supplicant) fails with some strange errors... so I can only manage to connect manually after logging in
edit2: seems that auto wlan is working now - I tried it with netctl
for Rev. B in /usr/lib/firmware/brcm/ : brcmfmac4329-sdio.txt & brcmfmac4329-sdio.bin are not necessary, you can rename brcmfmac4329-sdio.bin to brcmfmac-sdio.bin or delete and take the file from wandboard-sdk-20140519.tar.xz
Last edited by Yenal on Thu Jun 26, 2014 12:56 pm, edited 2 times in total.
Yenal
 
Posts: 18
Joined: Wed Jan 29, 2014 6:31 pm

Re: [WANDBOARD QUAD] no network

Postby pepedog » Sun Jun 22, 2014 5:31 pm

Yenal, wireless, what is wrong with package firmware-brcm43xx? Crux/Crawx worked on it to work on wandboard as it does on cubox-i4pro
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: [WANDBOARD QUAD] no network

Postby mkey2000 » Sun Jun 22, 2014 6:24 pm

ip link shows lo and eth0, I can set IP address manually but doesn't work, and dhcpcd shows an OFFER but no ACKNOWLEDGEMENT. WLan doesn't appear at all.
mkey2000
 
Posts: 9
Joined: Sun Jun 22, 2014 9:10 am

Re: [WANDBOARD QUAD] no network

Postby mkey2000 » Sun Jun 22, 2014 9:51 pm

PS: what about the "evbug: Event. Dev: input0, Type" lines in journalctl? aren't they related to dhcpcd and/or eth0?
mkey2000
 
Posts: 9
Joined: Sun Jun 22, 2014 9:10 am

Re: [WANDBOARD QUAD] no network

Postby Yenal » Mon Jun 23, 2014 4:17 pm

uhm I didnt see that firmware-brcm43xx package until now and didnt try it, but I guess this works also...

wlan0 must be listed in "ip link" ..eth0 is LAN
try firmware-brcm43xx, manual insertation of nvram.txt or my package to get wlan working

if LAN/WLAN cant solicit ip this could be related to your router.. then you should first try dhclient instead of dhcpcd


have no idea for the evbug, maybe you dont need to bother about it - as long as it doesnt hinder you doing your stuff. there are some more bugs you will notice soon (e.g. kernel panic after "shutdown now"...)
Yenal
 
Posts: 18
Joined: Wed Jan 29, 2014 6:31 pm

Re: [WANDBOARD QUAD] no network

Postby mkey2000 » Mon Jun 23, 2014 6:28 pm

1. wlan is not listed in ip link!
2. tried dhclient-4.3.0-1-armv7h.pkg.tar but only sends DHCPDISCOVER on eth0 doesn't receive any offer
3. tried firmware-brcm43xx-1.1-1-armv7h.pkg.tar.xz, wlan0 still not listed
mkey2000
 
Posts: 9
Joined: Sun Jun 22, 2014 9:10 am

Re: [WANDBOARD QUAD] no network

Postby Yenal » Tue Jun 24, 2014 12:00 pm

Are there any error logs in your router?

if firmware-brcm43xx is not working... pls try that and tell me if wlan comes up:
$this->bbcode_second_pass_code('', '
wget https://raw.githubusercontent.com/Freescale/meta-fsl-arm-extra/master/recipes-bsp/broadcom-nvram-config/files/wandboard/nvram.txt && \
wget https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/brcmfmac4329-sdio.bin && \
mv nvram.txt brcmfmac4329-sdio.txt && \
cp brcmfmac4329-sdio.txt brcmfmac-sdio.txt && \
cp brcmfmac4329-sdio.bin brcmfmac-sdio.bin

..then copy all 4 files to the sdcard @ /usr/lib/firmware/brcm/')

if you got wlan, please try wpa_supplicant and dhclient (pkgs can be downloaded e.g. from here
EDIT: http://mirror.archlinuxarm.org/ *):
$this->bbcode_second_pass_code('', '
wpa_passphrase SSID passphrase > /etc/wpa_supplicant/wpa_supplicant.conf
wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -B
dhclient wlan0
')

maybe something went wrong with alarm, you could also try to reinstall


btw: having also "evbug: Event. Dev: input0, Type" which are not influencing my network
$this->bbcode_second_pass_code('', 'Jun 17 20:25:25 alarm kernel: mxc_sdc_fb fb.26: 1920x1080 h_sync,r,l: 44,88,148 v_sync,l,u: 5,4,36 pixclock=148500000 Hz
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458792
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 28, Value: 1
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458792
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 28, Value: 0
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458792
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 28, Value: 1
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458792
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 28, Value: 0
Jun 17 20:25:26 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458773
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 19, Value: 1
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458760
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 18, Value: 1
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458773
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 19, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458760
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 18, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458757
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 48, Value: 1
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458757
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 48, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458770
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 24, Value: 1
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458770
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 24, Value: 0
Jun 17 20:25:27 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458770
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 24, Value: 1
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458770
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 24, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458775
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 20, Value: 1
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458775
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 20, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458792
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 28, Value: 1
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 4, Code: 4, Value: 458792
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 1, Code: 28, Value: 0
Jun 17 20:25:28 alarm kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0')

*mirror.us.leaseweb.net/archlinux/ was wrong
Last edited by Yenal on Wed Jun 25, 2014 6:39 am, edited 1 time in total.
Yenal
 
Posts: 18
Joined: Wed Jan 29, 2014 6:31 pm

Re: [WANDBOARD QUAD] no network

Postby WarheadsSE » Tue Jun 24, 2014 1:18 pm

That mirror location WILL NOT WORK
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: [WANDBOARD QUAD] no network

Postby PLyttle » Tue Jun 24, 2014 3:17 pm

I am guessing that, because wandboard rev.C1 uses a 4330 chip instead of a 4329 there need to be changes in the device tree. The schematics show differences in processor connections.:

$this->bbcode_second_pass_quote('', 'W')L_WAKE was: WL_AWAKE, now: BT_WAKE
WL_HOST_WAKE was: WL_GPIO0, now: SDIO_HOST_WAKE
BT_RST_N was: EIM_DA13, now: GPIO5_21
BT_HOST_WAKE was: n/a now: GPIO5_20
EIM_DA14 was BT_GPIO1, now n/a.
EIM_DA15 was: BT_GPIO0 now, n/a.

and probably a few more

LP
PLyttle
 
Posts: 120
Joined: Mon Jun 10, 2013 6:52 am

Next

Return to Freescale

Who is online

Users browsing this forum: No registered users and 2 guests