[SOLVED] Raspberry Pi Wireless Fails to Connect at Boot

This forum is for topics specific to the Raspberry Pi and Arch Linux ARM

[SOLVED] Raspberry Pi Wireless Fails to Connect at Boot

Postby donniezazen » Fri Mar 29, 2013 10:07 pm

Hello,

I have been trying to get wireless to auto-connect at boot but seems to have no success.

$this->bbcode_second_pass_code('', 'systemctl status netcfg@TyrionLannister.service
netcfg@TyrionLannister.service - Netcfg networking service for profile TyrionLannister
Loaded: loaded (/usr/lib/systemd/system/netcfg@.service; enabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 01:00:08 BST; 20min ago
Process: 111 ExecStart=/usr/bin/netcfg check-iface %i (code=exited, status=1/FAILURE)')

$this->bbcode_second_pass_code('', 'cat TyrionLannister
CONNECTION='wireless'
DESCRIPTION='A simple WPA encrypted wireless connection'
INTERFACE='wlan0'
SECURITY='wpa'

ESSID='TyrionLannister'
## Uncomment if the supplied ESSID is hexadecimal
#ESSID_TYPE='hex'
KEY='*************'

IP='static'
ADDR='192.168.0.86'
GATEWAY='192.168.0.1'
DNS=('8.8.8.8')

#IP='dhcp'

# Uncomment this if your ssid is hidden
#HIDDEN=yes')

$this->bbcode_second_pass_code('', 'cat /etc/conf.d/netcfg
# Enable these netcfg profiles at boot time.
# - prefix an entry with a '@' to background its startup
# - set to 'last' to restore the profiles running at the last shutdown
# - set to 'menu' to present a menu (requires the dialog package)
# Network profiles are found in /etc/network.d
NETWORKS=(wlan0)

# Specify the name of your wired interface for net-auto-wired
WIRED_INTERFACE="eth0"

# Specify the name of your wireless interface for net-auto-wireless
WIRELESS_INTERFACE="wlan0"

# Array of profiles that may be started by net-auto-wireless.
# When not specified, all wireless profiles are considered.
#AUTO_PROFILES=("profile1" "profile2")

DHCP_TIMEOUT=30')

I will only connect to one network and I would like it to have auto reconnect as wireless may go down from time to time and Pi might not have access to monitor or keyboard to manually reconnect.

Thanks for working on this.
Donnie.
Last edited by donniezazen on Sun Mar 31, 2013 12:27 am, edited 3 times in total.
donniezazen
 
Posts: 3
Joined: Fri Mar 29, 2013 9:52 pm

Re: Raspberry Pi Wireless Fails to Connect at Boot

Postby WarheadsSE » Fri Mar 29, 2013 11:15 pm

net-auto-wireless
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Raspberry Pi Wireless Fails to Connect at Boot

Postby donniezazen » Sat Mar 30, 2013 7:58 pm

Thanks. net-auto-wireless did the trick. I have also disabled netcfg@TyrionLannister.service to get rid of systemd error.
donniezazen
 
Posts: 3
Joined: Fri Mar 29, 2013 9:52 pm

Re: Raspberry Pi Wireless Fails to Connect at Boot

Postby donniezazen » Sun Mar 31, 2013 12:02 am

I just install cups and avahi packages to get it to be used as a print server. Now net-auto-wireless fails to start.

$this->bbcode_second_pass_code('', 'Process:111 ExecStart=/usr/bin/netcfg-wpa_actiond $WIRELESS_INTERFACE (code:Exited status:1/Failed) ')

It only fails at boot but I am able to manually start it once system is on.

$this->bbcode_second_pass_code('', 'systemctl list-unit-files | grep enabled
cups.path enabled
avahi-daemon.service enabled
avahi-dnsconfd.service enabled
cronie.service enabled
cups-browsed.service enabled
cups.service enabled
dbus-org.freedesktop.Avahi.service enabled
getty@.service enabled
net-auto-wireless.service enabled
openntpd.service enabled
rngd.service enabled
sshd.service enabled
sshdgenkeys.service enabled
syslog-ng.service enabled
syslog.service enabled
avahi-daemon.socket enabled
cups.socket enabled
remote-fs.target enabled')

UPDATE:- It seems systemd is trying to start net-auto-wireless before interface is on. Solution to this problems is found in this thread.
donniezazen
 
Posts: 3
Joined: Fri Mar 29, 2013 9:52 pm


Return to Raspberry Pi

Who is online

Users browsing this forum: No registered users and 73 guests