Getting Wireless working on Pogoplug E02

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

Re: Getting Wireless working on Pogoplug E02

Postby moonman » Sun Mar 10, 2013 8:17 am

I like this joke about "press any key" and the person looking for the "any" key on the keyboard :-) sorry, I couldn't resist :-)

myconnection is just an example and you were supposed to substitute wlan0 in its place
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Getting Wireless working on Pogoplug E02

Postby makuab » Sun Mar 10, 2013 8:40 am

$this->bbcode_second_pass_quote('moonman', 'I') like this joke about "press any key" and the person looking for the "any" key on the keyboard :-) sorry, I couldn't resist :-)

myconnection is just an example and you were supposed to substitute wlan0 in its place



Yes I know. I just didn't want to put in my connection name. Is that the right format though? Thanks for all of your help.


EDIT getting the same error as above with the two services.

Process: 129 ExecStart=/usr/bin/netcfg check-iface %i (code=exited, status=1/FAILURE)

Why is this so damn hard to figure out? IT works fine when I just start it manually with netcfg mynetworkname, why is it so hard to get it to start at boot?

EDIT: Restarted and got the same error for both services, what is going on?

the services are netcfg@wlan0 and netcfg@mynetworkname wlan0 is the one that's failing, and my connection isn't starting at boot.
makuab
 
Posts: 60
Joined: Fri Mar 01, 2013 11:49 pm

Re: Getting Wireless working on Pogoplug E02

Postby jabulmer12 » Sun Mar 10, 2013 9:40 am

I think you need to enable is as a service to boot on startup, systemctl enable netcfg@myprofile <-- edit accordingly

With reference to the question of why netcfg and not wicd or another program, its personal choice. Choose the service that you find most comfortable, for me that's netcfg as it gives you allot of control on your connection

I'm looking into your other errors now and will reply with any results
jabulmer12
 
Posts: 3
Joined: Sat Mar 09, 2013 7:23 am

Re: Getting Wireless working on Pogoplug E02

Postby moonman » Sun Mar 10, 2013 9:47 am

Geez.. talking about jokes... my fault, sorry. Don't know what I was thinking. You are right, it's supposed to be the connection that you set up, not the interface name. "iface" in your error log threw me off. Just remove the one with wlan0.

execute this: $this->bbcode_second_pass_code('', 'echo "ath9k_htc" > /etc/modules-load.d/ath9k_htc.conf') so that the driver for your wireless dongle is loaded before netcfg tries to connect using this dongle. This seems to be the only problem that prevents it from connecting at bootup.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Getting Wireless working on Pogoplug E02

Postby pepedog » Sun Mar 10, 2013 11:35 am

$this->bbcode_second_pass_quote('makuab', '
')with dongle
.
.
.
without dongle
Looks the same to me, what should I do?

I did say
$this->bbcode_second_pass_quote('', 'R')eboot without dongle and lsmod
plug in dongle and lsmod

Just check in /usr/lib/firmware that the firmware is there
http://linuxwireless.org/en/users/Drivers/ath9k_htc#Firmware
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK
Top

Re: Getting Wireless working on Pogoplug E02

Postby makuab » Sun Mar 10, 2013 5:26 pm

$this->bbcode_second_pass_quote('pepedog', '')$this->bbcode_second_pass_quote('makuab', '
')with dongle
.
.
.
without dongle
Looks the same to me, what should I do?

I did say
$this->bbcode_second_pass_quote('', 'R')eboot without dongle and lsmod
plug in dongle and lsmod

Just check in /usr/lib/firmware that the firmware is there
http://linuxwireless.org/en/users/Drivers/ath9k_htc#Firmware


Firmware is there, ath9k_htc is in modules to load, removed the netcfg@wlan0 service, still getting the error $this->bbcode_second_pass_code('', ' Process: 115 ExecStart=/usr/bin/netcfg check-iface %i (code=exited, status=1/FAILURE)')

I rebooted without the dongle, did an lsmod, and then plugged it in and did an lsmod. The outputs were the same.

It's strange because netcfg mynetworkname works fine, but I can't get it to start at boot.
Last edited by makuab on Sun Mar 10, 2013 9:04 pm, edited 1 time in total.
makuab
 
Posts: 60
Joined: Fri Mar 01, 2013 11:49 pm
Top

Re: Getting Wireless working on Pogoplug E02

Postby moonman » Sun Mar 10, 2013 9:03 pm

what does dmesg say?
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Getting Wireless working on Pogoplug E02

Postby makuab » Sun Mar 10, 2013 9:19 pm

$this->bbcode_second_pass_quote('moonman', 'w')hat does dmesg say?

$this->bbcode_second_pass_code('', '
[ 13.712601] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 13.719242] orion-ehci orion-ehci.0: Marvell Orion EHCI
[ 13.724590] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 13.753124] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 13.773117] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 13.779673] hub 1-0:1.0: USB hub found
[ 13.783480] hub 1-0:1.0: 1 port detected
[ 13.787918] Initializing USB Mass Storage driver...
[ 13.792901] usbcore: registered new interface driver usb-storage
[ 13.798962] USB Mass Storage support registered.
[ 13.803698] usbcore: registered new interface driver libusual
[ 13.809779] mousedev: PS/2 mouse device common for all mice
[ 14.103121] usb 1-1: new high speed USB device number 2 using orion-ehci
[ 14.255062] hub 1-1:1.0: USB hub found
[ 14.259188] hub 1-1:1.0: 4 ports detected
[ 14.543446] usb 1-1.1: new high speed USB device number 3 using orion-ehci
[ 14.658931] usb-storage 1-1.1:1.0: Quirks match for vid 05e3 pid 0723: 8000
[ 14.666005] scsi0 : usb-storage 1-1.1:1.0
[ 14.823111] rtc-mv rtc-mv: internal RTC not ticking
[ 14.828170] sdhci: Secure Digital Host Controller Interface driver
[ 14.834395] sdhci: Copyright(c) Pierre Ossman
[ 14.838974] mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
[ 14.847073] sdhci-pltfm: SDHCI platform and OF driver helper
[ 14.852893] Registered led device: plug:red:misc
[ 14.857725] Registered led device: status:green:health
[ 14.862982] Registered led device: status:blue:health
[ 14.868278] usbcore: registered new interface driver r8712u
[ 14.877852] GRE over IPv4 demultiplexor driver
[ 14.882272] TCP cubic registered
[ 14.885741] NET: Registered protocol family 17
[ 14.890282] lib80211: common routines for IEEE802.11 drivers
[ 14.895991] lib80211_crypt: registered algorithm 'NULL'
[ 14.901246] Registering the dns_resolver key type
[ 14.906057] Gating clock of unused units
[ 14.910012] before: 0x00dfc3fd
[ 14.913125] after: 0x00c701d9
[ 14.916733] registered taskstats version 1
[ 14.921500] netconsole: local port 6665
[ 14.925383] netconsole: local IP 10.10.10.3
[ 14.929588] netconsole: interface 'eth0'
[ 14.933561] netconsole: remote port 6666
[ 14.937497] netconsole: remote IP 10.10.10.4
[ 14.941787] netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
[ 14.947928] netconsole: device eth0 not up yet, forcing it
[ 15.664783] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 9451 PQ: 0 ANSI: 0
[ 15.673791] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 15.944344] sd 0:0:0:0: [sda] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB)
[ 15.952958] sd 0:0:0:0: [sda] Write Protect is off
[ 15.957820] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 15.964011] sd 0:0:0:0: [sda] No Caching mode page present
[ 15.969519] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 15.979959] sd 0:0:0:0: [sda] No Caching mode page present
[ 15.985638] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 15.993027] sda: sda1
[ 15.998834] sd 0:0:0:0: [sda] No Caching mode page present
[ 16.004522] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 16.010645] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 17.297722] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 17.314197] console [netcon0] enabled
[ 17.317889] netconsole: network logging started
[ 17.322532] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 17.329200] Waiting 10sec before mounting root device...
[ 27.344728] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[ 27.376761] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 27.384532] VFS: Mounted root (ext3 filesystem) on device 8:1.
[ 27.395392] devtmpfs: mounted
[ 27.399044] Freeing init memory: 172K
[ 27.983265] systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -A UDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[ 28.072477] systemd[1]: Inserted module 'autofs4'
[ 28.078970] systemd[1]: Set hostname to <Arch>.
[ 28.314149] 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.
[ 28.336517] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 28.344591] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 28.352314] systemd[1]: Expecting device dev-ttyS0.device...
[ 28.373233] systemd[1]: Starting Syslog Socket.
[ 28.393205] systemd[1]: Listening on Syslog Socket.
[ 28.398210] systemd[1]: Starting Remote File Systems.
[ 28.423196] systemd[1]: Reached target Remote File Systems.
[ 28.428900] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 28.453198] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 28.459855] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 28.483197] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 28.490288] systemd[1]: Starting LVM2 metadata daemon socket.
[ 28.513201] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 28.519423] systemd[1]: Starting Delayed Shutdown Socket.
[ 28.543198] systemd[1]: Listening on Delayed Shutdown Socket.
[ 28.549102] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 28.557424] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 28.565828] systemd[1]: Starting udev Kernel Socket.
[ 28.593205] systemd[1]: Listening on udev Kernel Socket.
[ 28.598917] systemd[1]: Starting udev Control Socket.
[ 28.623205] systemd[1]: Listening on udev Control Socket.
[ 28.628857] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 28.663210] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 28.672758] systemd[1]: Starting Encrypted Volumes.
[ 28.693197] systemd[1]: Reached target Encrypted Volumes.
[ 28.698714] systemd[1]: Starting Swap.
[ 28.723193] systemd[1]: Reached target Swap.
[ 28.727593] systemd[1]: Starting Journal Socket.
[ 28.753198] systemd[1]: Listening on Journal Socket.
[ 28.758310] systemd[1]: Mounting Temporary Directory...
[ 28.834494] systemd[1]: Mounting Debug File System...
[ 29.066449] systemd[1]: Started Set Up Additional Binary Formats.
[ 29.072727] systemd[1]: Starting Setup Virtual Console...
[ 29.329719] systemd[1]: Starting Load Kernel Modules...
[ 29.394130] systemd[1]: Starting udev Kernel Device Manager...
[ 29.464105] systemd[1]: Starting udev Coldplug all Devices...
[ 29.509896] cfg80211: Calling CRDA to update world regulatory domain
[ 29.533909] systemd[1]: Mounted Huge Pages File System.
[ 29.539314] systemd[1]: Mounting POSIX Message Queue File System...
[ 29.553802] systemd-udevd[55]: starting version 197
[ 29.779250] usbcore: registered new interface driver ath9k_htc
[ 29.885888] systemd[1]: Starting Apply Kernel Variables...
[ 29.934090] systemd[1]: Starting Journal Service...
[ 30.013350] systemd[1]: Started Journal Service.
[ 30.023780] systemd[1]: Starting Syslog.
[ 30.053307] systemd[1]: Reached target Syslog.
[ 30.060770] systemd[1]: Started File System Check on Root Device.
[ 30.067347] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 30.163452] systemd[1]: Started udev Kernel Device Manager.
[ 30.193374] systemd[1]: Mounted Temporary Directory.
[ 30.204909] systemd[1]: Mounted Debug File System.
[ 30.263325] systemd[1]: Started Load Kernel Modules.
[ 30.363317] systemd[1]: Started Setup Virtual Console.
[ 30.393299] systemd[1]: Mounted POSIX Message Queue File System.
[ 30.453317] systemd[1]: Started Apply Kernel Variables.
[ 30.513352] systemd[1]: Started Remount Root and Kernel File Systems.
[ 30.603370] systemd[1]: Started udev Coldplug all Devices.
[ 30.609104] systemd[1]: Starting Local File Systems (Pre).
[ 30.643293] systemd[1]: Reached target Local File Systems (Pre).
[ 30.653299] systemd[1]: Starting Load Random Seed...
[ 30.753950] systemd[1]: Mounted FUSE Control File System.
[ 30.759560] systemd[1]: Mounted Configuration File System.
[ 30.775385] systemd[1]: Starting Local File Systems.
[ 30.803346] systemd[1]: Reached target Local File Systems.
[ 30.819510] systemd[1]: Starting Recreate Volatile Files and Directories...
[ 30.883975] systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
[ 31.033384] systemd[1]: Started Load Random Seed.
[ 31.083297] systemd[1]: Started Recreate Volatile Files and Directories.
[ 31.090301] systemd[1]: Starting System Initialization.
[ 31.133323] systemd[1]: Reached target System Initialization.
[ 31.139276] systemd[1]: Starting D-Bus System Message Bus Socket.
[ 31.183302] systemd[1]: Listening on D-Bus System Message Bus Socket.
[ 31.189924] systemd[1]: Starting Sockets.
[ 31.223296] systemd[1]: Reached target Sockets.
[ 31.228008] systemd[1]: Starting Daily Cleanup of Temporary Directories.
[ 31.243318] systemd[1]: Started Daily Cleanup of Temporary Directories.
[ 31.250109] systemd[1]: Starting Basic System.
[ 31.283294] systemd[1]: Reached target Basic System.
[ 31.288453] systemd[1]: Starting Periodic Command Scheduler...
[ 31.383324] systemd[1]: Started Periodic Command Scheduler.
[ 31.395461] systemd[1]: Starting Netcfg networking service for profile omitted...
[ 31.473784] systemd[1]: Starting Netcfg multi-profile daemon...
[ 31.614798] systemd[1]: Started SSH Key Generation.
[ 31.619969] systemd[1]: Starting OpenSSH Daemon...
[ 31.713298] systemd[1]: Started OpenSSH Daemon.
[ 31.723358] systemd[1]: Starting Login Service...
[ 31.793758] systemd[1]: Starting D-Bus System Message Bus...
[ 31.883280] systemd[1]: Started D-Bus System Message Bus.
[ 31.897848] systemd[1]: Starting System Logger Daemon...
[ 31.983295] systemd[1]: Started System Logger Daemon.
[ 32.023320] systemd[1]: Found device /dev/ttyS0.
[ 32.195420] systemd-journald[82]: Received SIGUSR1
[ 32.243270] systemd[1]: Started Login Service.
[ 32.504741] systemd-journald[82]: File /var/log/journal/5c49cb5bf08724338eb09a6900092bb0/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 32.643297] systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
[ 32.651237] systemd[1]: Starting Permit User Sessions...
[ 32.686286] NET: Registered protocol family 10
[ 43.693104] eth0: no IPv6 routers present
[ 301.995091] usb 1-1.2: new high speed USB device number 4 using orion-ehci
[ 302.420946] usb 1-1.2: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[ 302.656190] ath9k_htc 1-1.2:1.0: ath9k_htc: HTC initialized with 33 credits
[ 302.854080] ath9k_htc 1-1.2:1.0: ath9k_htc: FW Version: 1.3
[ 302.860313] ath: EEPROM regdomain: 0x809c
[ 302.864367] ath: EEPROM indicates we should expect a country code
[ 302.871202] ath: doing EEPROM country->regdmn map search
[ 302.876995] ath: country maps to regdmn code: 0x52
[ 302.881832] ath: Country alpha2 being used: CN
[ 302.886956] ath: Regpair used: 0x52
[ 302.894005] ieee80211 phy0: Atheros AR9271 Rev:1
[ 302.900908] Registered led device: ath9k_htc-phy0
[ 302.906183] usb 1-1.2: ath9k_htc: USB layer initialized
')
makuab
 
Posts: 60
Joined: Fri Mar 01, 2013 11:49 pm
Top

Re: Getting Wireless working on Pogoplug E02

Postby moonman » Sun Mar 10, 2013 9:36 pm

Well, the module does not get loaded in time still. Try this:

$this->bbcode_second_pass_code('', 'echo "ath9k_htc.ko" > /etc/modules-load.d/ath9k_htc.conf') This will erase the old one. The difference is inclusion of .ko in module name
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Getting Wireless working on Pogoplug E02

Postby makuab » Sun Mar 10, 2013 9:53 pm

$this->bbcode_second_pass_quote('moonman', 'W')ell, the module does not get loaded in time still. Try this:

$this->bbcode_second_pass_code('', 'echo "ath9k_htc.ko" > /etc/modules-load.d/ath9k_htc.conf') This will erase the old one. The difference is inclusion of .ko in module name


what does the .ko do?

EDIT: tried the .ko and did sync /sbin/reboot, now it's not booting or isn't establishing a connection.
Last edited by makuab on Sun Mar 10, 2013 10:02 pm, edited 1 time in total.
makuab
 
Posts: 60
Joined: Fri Mar 01, 2013 11:49 pm
Top

PreviousNext

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 12 guests