[Solved]Wireless LAN can not start on boot

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

[Solved]Wireless LAN can not start on boot

Postby permitivity » Sat Oct 05, 2013 2:19 am

Hi,
I have a Series 4 Pogoplug. I stole the rootfs from one of my E02's and it's working on the Series 4.

Except I'm having issues with a wireless USB adapter. I'll try to explain as best I can to make it easier to help me.

lsusb:
$this->bbcode_second_pass_quote('', '
')Bus 002 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter


I know this usb adapter works on an E02.

If I run "wifi-menu", it scans the network, and I can connect to the wireless AP. The LED on the adapter turn on, and I can disconnect the hardwire and connect to the Series4 Pogoplug via wireless. Once I reboot however, no go. Have to connect via wired lan. Even though I ran "systemctl enable netctl-auto@wlan0.service".


dmesg: There is an odd message where it renames my "wlan0" to "wlp0s1u2". Why is it doing that? In "/etc/netctl/", it added a profile "wlp0s1u2". Actually, there's also a "wlp0s1u1", probably from a previous reboot. I've tried doing a "systemctl enable netctl-auto@wlp0s1u1.service" and a "systemctl enable netctl-auto@wlp0s1u2.service", but it didn't make wireless lan come up on boot.

$this->bbcode_second_pass_code('', '
[ 13.221562] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
[ 13.222278] xhci_hcd 0000:00:01.0: irq 9, io mem 0xe0000000
[ 13.222305] xhci_hcd 0000:00:01.0: Failed to enable MSI-X
[ 13.227687] xhci_hcd 0000:00:01.0: failed to allocate MSI entry
[ 13.234211] xHCI xhci_add_endpoint called for root hub
[ 13.234226] xHCI xhci_check_bandwidth called for root hub
[ 13.234430] hub 2-0:1.0: USB hub found
[ 13.234462] hub 2-0:1.0: 2 ports detected
[ 13.234963] xhci_hcd 0000:00:01.0: xHCI Host Controller
[ 13.235006] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 3
[ 13.235615] xHCI xhci_add_endpoint called for root hub
[ 13.235630] xHCI xhci_check_bandwidth called for root hub
[ 13.235847] hub 3-0:1.0: USB hub found
[ 13.235879] hub 3-0:1.0: 2 ports detected
[ 13.236460] Initializing USB Mass Storage driver...
[ 13.236643] usbcore: registered new interface driver usb-storage
[ 13.236656] USB Mass Storage support registered.
[ 13.236830] usbcore: registered new interface driver libusual
[ 13.237306] mousedev: PS/2 mouse device common for all mice
[ 13.459906] ata1: SATA link down (SStatus 0 SControl F300)
[ 13.539902] usb 1-1: new high speed USB device number 2 using orion-ehci
[ 13.691857] scsi1 : usb-storage 1-1:1.0
[ 13.809902] usb 2-2: new high speed USB device number 2 using xhci_hcd
[ 13.831825] xhci_hcd 0000:00:01.0: WARN: short transfer on control ep
[ 13.834464] xhci_hcd 0000:00:01.0: WARN: short transfer on control ep
[ 13.836429] xhci_hcd 0000:00:01.0: WARN: short transfer on control ep
[ 13.837529] xhci_hcd 0000:00:01.0: WARN: short transfer on control ep
[ 13.839086] xhci_hcd 0000:00:01.0: WARN: short transfer on control ep
[ 13.841823] xhci_hcd 0000:00:01.0: WARN: short transfer on control ep
[ 14.239905] rtc-mv rtc-mv: internal RTC not ticking
[ 14.245005] sdhci: Secure Digital Host Controller Interface driver
[ 14.245019] sdhci: Copyright(c) Pierre Ossman
[ 14.245325] mmc0: mvsdio driver initialized, using GPIO 27 for card detection
[ 14.245389] sdhci-pltfm: SDHCI platform and OF driver helper
[ 14.245580] Registered led device: status:green:health
[ 14.245712] Registered led device: status:red:fault
[ 14.246041] usbcore: registered new interface driver r8712u
[ 14.247377] GRE over IPv4 demultiplexor driver
[ 14.247578] TCP cubic registered
[ 14.247594] NET: Registered protocol family 17
[ 14.247714] lib80211: common routines for IEEE802.11 drivers
[ 14.247730] lib80211_crypt: registered algorithm 'NULL'
[ 14.247743] Registering the dns_resolver key type
[ 14.247789] Gating clock of unused units
[ 14.247802] before: 0x00c7c1dd
[ 14.247813] after: 0x00c741dd
[ 14.248555] registered taskstats version 1
[ 14.249676] console [netcon0] enabled
[ 14.249688] netconsole: network logging started
[ 14.250259] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 14.250652] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 14.257530] Waiting for root device /dev/sda1...
[ 14.690894] scsi 1:0:0:0: Direct-Access SanDisk Cruzer Fit 1.26 PQ: 0 ANSI: 5
[ 14.691924] sd 1:0:0:0: Attached scsi generic sg0 type 0
[ 14.693178] sd 1:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[ 14.694662] sd 1:0:0:0: [sda] Write Protect is off
[ 14.694682] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 14.695414] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 14.700775] sda: sda1
[ 14.703914] sd 1:0:0:0: [sda] Attached SCSI removable disk
[ 14.801183] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[ 15.058083] EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
[ 15.060537] EXT4-fs (sda1): recovery complete
[ 15.062314] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 15.062378] VFS: Mounted root (ext3 filesystem) on device 8:1.
[ 15.068225] devtmpfs: mounted
[ 15.069088] Freeing init memory: 172K
[ 15.570105] systemd[1]: systemd 204 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[ 15.640265] systemd[1]: Inserted module 'autofs4'
[ 15.705345] NET: Registered protocol family 10
[ 15.710697] systemd[1]: Inserted module 'ipv6'
[ 15.713412] systemd[1]: Set hostname to <alarm>.
[ 15.995854] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
[ 15.997253] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 15.997779] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 15.997930] systemd[1]: Expecting device dev-ttyS0.device...
[ 16.020086] systemd[1]: Expecting device sys-subsystem-net-devices-wlan0.device...
[ 16.040033] systemd[1]: Starting Remote File Systems.
[ 16.060004] systemd[1]: Reached target Remote File Systems.
[ 16.060126] systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
[ 16.080028] systemd[1]: Starting Delayed Shutdown Socket.
[ 16.100011] systemd[1]: Listening on Delayed Shutdown Socket.
[ 16.100130] systemd[1]: Starting LVM2 metadata daemon socket.
[ 16.120007] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 16.120127] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 16.140001] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 16.140118] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 16.160002] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 16.160148] systemd[1]: Starting Journal Socket.
[ 16.180006] systemd[1]: Listening on Journal Socket.
[ 16.180259] systemd[1]: Mounting POSIX Message Queue File System...
[ 16.241404] systemd[1]: Starting Journal Service...
[ 16.320183] systemd[1]: Started Journal Service.
[ 16.320579] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 16.321145] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 16.321324] systemd[1]: Starting Paths.
[ 16.340155] systemd[1]: Reached target Paths.
[ 16.340794] systemd[1]: Starting Create static device nodes in /dev...
[ 16.400996] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 16.420137] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 16.420711] systemd[1]: Starting udev Kernel Socket.
[ 16.440241] systemd[1]: Listening on udev Kernel Socket.
[ 16.440852] systemd[1]: Starting udev Control Socket.
[ 16.460256] systemd[1]: Listening on udev Control Socket.
[ 16.460839] systemd[1]: Starting udev Coldplug all Devices...
[ 16.520716] systemd[1]: Starting Setup Virtual Console...
[ 16.590666] systemd[1]: Started Set Up Additional Binary Formats.
[ 16.590861] systemd[1]: Mounting Debug File System...
[ 16.663923] systemd[1]: Started Load Kernel Modules.
[ 16.664150] systemd[1]: Mounted Configuration File System.
[ 16.664258] systemd[1]: Starting Encrypted Volumes.
[ 16.680161] systemd[1]: Reached target Encrypted Volumes.
[ 16.693073] systemd[1]: Starting Apply Kernel Variables...
[ 16.750798] systemd[1]: Mounted FUSE Control File System.
[ 16.750978] systemd[1]: Mounted Huge Pages File System.
[ 16.751134] systemd[1]: Starting Swap.
[ 16.770150] systemd[1]: Reached target Swap.
[ 16.770380] systemd[1]: Started File System Check on Root Device.
[ 16.770487] systemd[1]: Mounting Temporary Directory...
[ 16.840386] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 16.940145] systemd[1]: Mounted POSIX Message Queue File System.
[ 17.000041] systemd[1]: Started Create static device nodes in /dev.
[ 17.100200] systemd[1]: Started Setup Virtual Console.
[ 17.120246] systemd[1]: Mounted Debug File System.
[ 17.180033] systemd[1]: Started Apply Kernel Variables.
[ 17.200105] systemd[1]: Mounted Temporary Directory.
[ 17.260032] systemd[1]: Started Remount Root and Kernel File Systems.
[ 17.320031] systemd[1]: Started udev Coldplug all Devices.
[ 17.320281] systemd[1]: Starting Load Random Seed...
[ 17.381074] systemd[1]: Starting udev Kernel Device Manager...
[ 17.458392] systemd-udevd[69]: starting version 204
[ 17.490145] systemd[1]: Started Load Random Seed.
[ 17.580255] systemd[1]: Started udev Kernel Device Manager.
[ 17.580568] systemd[1]: Starting Local File Systems (Pre).
[ 17.600234] systemd[1]: Reached target Local File Systems (Pre).
[ 17.600425] systemd[1]: Starting Local File Systems.
[ 17.620222] systemd[1]: Reached target Local File Systems.
[ 17.620665] systemd[1]: Starting Recreate Volatile Files and Directories...
[ 17.680990] systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
[ 17.820283] systemd[1]: Started Recreate Volatile Files and Directories.
[ 17.820599] systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
[ 17.900170] systemd[1]: Found device /dev/ttyS0.
[ 18.050123] systemd[1]: Found device /sys/subsystem/net/devices/eth0.
[ 18.200160] systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
[ 18.260208] systemd[1]: Started Update UTMP about System Reboot/Shutdown.
[ 18.260570] systemd[1]: Starting System Initialization.
[ 18.280182] systemd[1]: Reached target System Initialization.
[ 18.280430] systemd[1]: Starting D-Bus System Message Bus Socket.
[ 18.300206] systemd[1]: Listening on D-Bus System Message Bus Socket.
[ 18.300415] systemd[1]: Starting Sockets.
[ 18.320119] systemd[1]: Reached target Sockets.
[ 18.320326] systemd[1]: Starting Daily Cleanup of Temporary Directories.
[ 18.320534] systemd[1]: Started Daily Cleanup of Temporary Directories.
[ 18.320661] systemd[1]: Starting Timers.
[ 18.340114] systemd[1]: Reached target Timers.
[ 18.340381] systemd[1]: Started Manage Sound Card State (restore and store).
[ 18.340668] systemd[1]: Starting Restore Sound Card State...
[ 18.391047] systemd[1]: Starting Basic System.
[ 18.410199] systemd[1]: Reached target Basic System.
[ 18.410530] systemd[1]: Starting Automatic wired network connection using netctl profiles...
[ 18.437966] systemd-journald[49]: File /var/log/journal/e4b5dad211aa4a41920893d218a05e68/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 18.470031] cfg80211: Calling CRDA to update world regulatory domain
[ 18.500242] systemd[1]: Started Automatic wired network connection using netctl profiles.
[ 18.925713] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.952443] systemd[1]: Started SSH Key Generation.
[ 18.952797] systemd[1]: Starting OpenSSH Daemon...
[ 19.030159] systemd[1]: Started OpenSSH Daemon.
[ 19.030466] systemd[1]: Starting devmon Service...
[ 19.100960] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 19.105863] ieee80211 phy0: hwaddr 00:08:54:9f:fa:59, RTL8187BvE V0 + rtl8225z2, rfkill mask 2
[ 19.125337] rtl8187: Customer ID is 0x00
[ 19.128817] Registered led device: rtl8187-phy0::radio
[ 19.131922] Registered led device: rtl8187-phy0::tx
[ 19.133506] Registered led device: rtl8187-phy0::rx
[ 19.134934] rtl8187: wireless switch is on
[ 19.136332] usbcore: registered new interface driver rtl8187
[ 19.622587] systemd-udevd[73]: renamed network interface wlan0 to wlp0s1u2
[ 19.860175] systemd[1]: Started devmon Service.
[ 19.860460] systemd[1]: Starting Entropy Harvesting Daemon...
[ 19.920574] systemd[1]: Starting D-Bus System Message Bus...
[ 20.000178] systemd[1]: Started D-Bus System Message Bus.
[ 20.001442] systemd[1]: Starting Login Service...
[ 20.060904] systemd[1]: Starting Permit User Sessions...
[ 20.180175] systemd[1]: Started Restore Sound Card State.
[ 20.383195] systemd[1]: Started Permit User Sessions.
[ 20.383539] systemd[1]: Starting Getty on tty1...
[ 20.490172] systemd[1]: Started Getty on tty1.
[ 20.490511] systemd[1]: Starting Serial Getty on ttyS0...
[ 20.570199] systemd[1]: Started Serial Getty on ttyS0.
[ 20.570558] systemd[1]: Starting Login Prompts.
[ 20.590037] systemd[1]: Reached target Login Prompts.
[ 20.610107] systemd[1]: Started Login Service.
[ 122.568890] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full duplex, flow control disabled
[ 122.569046] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 132.819876] eth0: no IPv6 routers present
')
Last edited by permitivity on Mon Oct 14, 2013 5:23 am, edited 2 times in total.
permitivity
 
Posts: 141
Joined: Mon Feb 18, 2013 3:08 am

Re: Wireless LAN can not start on boot

Postby permitivity » Mon Oct 07, 2013 2:37 pm

Has anyone else gotten Series 4 Pogoplugs to boot with wireless lan working? Just wanted to give this a bump. Worked on it this weekend on a fresh install but still couldn't get it to start wireless on reboot. Tried three different wireless USB adapters.
permitivity
 
Posts: 141
Joined: Mon Feb 18, 2013 3:08 am

Re: Wireless LAN can not start on boot

Postby WarheadsSE » Mon Oct 07, 2013 2:45 pm

Looks like persistent net naming rules are biting you.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Wireless LAN can not start on boot

Postby permitivity » Tue Oct 08, 2013 4:58 am

$this->bbcode_second_pass_quote('WarheadsSE', 'L')ooks like persistent net naming rules are biting you.


Thanks for giving me the hint on what to look for. That's the first I've heard of persistent net naming. I'm not sure why it's effecting the Series 4 Pogoplug and not the E02. I made the two rootfs flash drives the same. Maybe I accidentally enabled persistent net naming somehow.

I googled and disabled it using this:

$this->bbcode_second_pass_code('', 'ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules')

Reference: https://wiki.archlinux.org/index.php/Ne ... figuration

That fixed the problem.
permitivity
 
Posts: 141
Joined: Mon Feb 18, 2013 3:08 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 5 guests