[SOLVED] Netcfg on boot-up doesn't work since update

mamr · 2008-08-16 09:29:23

Hi,
I have Archlinux running for a while now. I have a wpa2-secured wlan running at home. Yesterday I ran an update and now my box doesn't auto-connect to my wireless network at boot-up anymore. I don't know why, since it worked flawelessly before and works when I run "netcfg2 home" (where home is the name of my profile) manually.

The guys on IRC tried to help me for a while now, but we don't have ideas anymore. Maybe it's a bug I don't know?

So what happens exactly: When I boot my system and the net-profiles daemon gets started I get the following: HOME - UP .... FAIL
After that I log into my KDE, start konsole and as root do "netcfg2 home" which results in connecting without any error. On IRC we weren't able to figure out this strange problem.

Here is my /etc/rc.conf:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="de_DE.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Berlin"
KEYMAP="de-latin1-nodeadkeys"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(forcedeth slhc !ath5k ath_hal ath_pci wlan snd-mixer-oss 
snd-pcm-oss snd-seq-oss snd-seq-device snd-seq-midi-event snd-seq 
snd-hwdep snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-hda-intel 
soundcore snd-usb-audio snd-usb-lib gspca usblp vboxdrv)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="tux"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(!eth0 ath0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(home)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(@syslog-ng @network @netfs @crond @alsa @cups @hal @fam 
net-profiles kdm)

This is my /etc/network.d/home profile:

CONNECTION="wireless"
INTERFACE=ath0
SCAN="yes"
SECURITY="wpa"
ESSID="myssid"
KEY="mykey"
IP="dhcp"
TIMEOUT=30

This is an excerpt from /var/log/pacman.log:

[2008-08-15 18:03] -----------------------------------------------------------
[2008-08-15 18:03] Attention netcfg users: netcfg is no longer included as
[2008-08-15 18:03] part of the initscripts package.
[2008-08-15 18:03] Be aware that rc.conf's NET_PROFILES has changed to
[2008-08-15 18:03] NETWORKS, and that netcfg must be installed separately.
[2008-08-15 18:03] For more info, see the netcfg man page.
[2008-08-15 18:03] -----------------------------------------------------------
[2008-08-15 18:03] upgraded initscripts (2008.05-1 -> 2008.08-1)

What we tried already:
- insert/remove the ath0-device in INTERFACES=(...) in /etc/rc.conf
- move the net-profiles daemon at the end of the DAEMONS line, right next to kdm to make sure, all other daemons are running already
- re-install the netcfg-package, my version is now 2.0.6-1

I would be glad if you can help me out with this problem. Thanks in advance!

Last edited by mamr (2008-08-17 07:53:15)

Army · 2008-08-16 12:41:05

Seems like you are using the [testing] repo? I do as well and it works here

...
AUTO_NETWORKS=(auto-wireless eth1)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(@net-auto @laptop-mode @keytouch @hal @alsa @cpufreq @mpd @mpdscribble)

Does that help you?

mamr · 2008-08-16 12:52:15

No, I'm not using the testing repo. And your solution doesn't work either.

I tried something else, too:
- I blacklisted the 'net-profiles' daemon, so it didn't start on boot
- afterwards I tried to start it manually and git this:

root@tux matthias]# /etc/rc.d/net-profiles start
:: home up  - Network unavailable                                        [FAIL]
[root@tux matthias]# /etc/rc.d/net-profiles start
net-profiles has already been started.  Try '/etc/rc.d/net-profiles restart'
[root@tux matthias]# /etc/rc.d/net-profiles restart
:: home up                                                               [DONE]

Why does it say my network is unavailable once and then works afterwards? I did not change anything and the time between both tries is about 2 seconds.

Army · 2008-08-16 13:33:01

Oh no, I think I got it!!!

DAEMONS=(@syslog-ng @network @netfs @crond @alsa @cups @hal @fam 
net-profiles kdm)

should be

DAEMONS=(@syslog-ng @network @netfs @crond @alsa @cups @hal @fam net-profiles kdm)

RIGHT?!?!

fwojciec · 2008-08-16 13:43:51

Are you using nano to edit config files? If you use nano without a "-w" switch then it tends to wrap long lines automatically, which can lead to problems of this sort.

iphitus · 2008-08-16 13:48:59

Read the wiki page "Network profiles development"

The main change between core and testing is that hardware specific quirks are now "opt-in" as some hardware quirks were causing problems for other hardware...

mamr · 2008-08-16 17:34:25

@ Army & fwojciec: Yes, I was using nano. I fixed the break in the line with vi, but it didn't solve my problem. On boot it says that the network connection failed and bringing up network manually afterwards works.

@ iphitus: I don't have the testing repo turned on in /etc/pacman.conf. So as far as I know, I'm not using an unstable netcfg, am I?

petelewis · 2008-08-16 18:22:57

@mamr I'm getting the same behaviour using the iwl3945 driver - first attempt to associate fails, second (and subsequent ones) succeed.

Any idea? On the first (failed) attempt, it does seem to bring up the device, but doesn't connect to anything.

floke · 2008-08-16 18:35:37

Same here - let's hope for a swift fix!

petelewis · 2008-08-16 19:16:28

BTW, have tried both:

QUIRKS=(preessid)

and

SCAN=no

but neither made any difference.

petelewis · 2008-08-16 19:23:17

Right - I have managed to figure this out now. In the network profile file, changing SCAN="yes" to SCAN="no" made it work first time.

(I'd previously set it in /etc/rc.conf and hadn't realised that it was profile specific - as said on the wiki page.)

Hope this works for others too :-)

floke · 2008-08-16 19:51:48

Well I have no network profile - everything runs through rc.conf - so can't see how this would work for me

(thanks though)

mamr · 2008-08-16 20:30:01

petelewis wrote:

Right - I have managed to figure this out now. In the network profile file, changing SCAN="yes" to SCAN="no" made it work first time.
(I'd previously set it in /etc/rc.conf and hadn't realised that it was profile specific - as said on the wiki page.)
Hope this works for others too :-)

Don't know why, but this fixed my problem, too. Is this a bug?

@floke: Maybe you should give creating a profile a try.

whargoul · 2008-08-16 22:19:07

If the problem is solved you should probably mark the thread with [SOLVED].

petelewis · 2008-08-16 22:22:45

I'm certainly no expert in this, but it looks to me like it might be either some kind of bug in intel driver... or else in the wireless tools?

Not sure...

monstermudder78 · 2008-08-17 01:06:27

I have the same problem also, started after the update yesterday. Up til now I had been running everything through rc.conf, I don't have any profiles in network.d.

EDIT:
Ok, I got it working by creating a profile for netcfg, but I am still confused why a netcfg update screwed up my wireless that was being configured through rc.conf?

EDIT EDIT:
As it turns out I like using netcfg better My connection comes up much faster than it did running through rc.conf.

Last edited by monstermudder78 (2008-08-17 01:40:55)

mamr · 2008-08-17 07:52:08

@petelewis: As I don't have an intel chipset, the bug can't be in the intel driver but must be somewhere else.

I marked the thread as solved.

floke · 2008-08-17 14:08:50

Still no beans for me - I created a profile, installed netcfg etc. but no joy. No connection at boot and need to 'netcfg2 home' one into desktop to connect.

mamr · 2008-08-17 16:28:40

@floke: Try to move net-profiles at the end of the line und rc.conf's daemons array. I moved it right in front of kdm. This makes sure every daemon is loaded already (except you have an @-character in front of some daemons). Maybe this helps. And - as said above - turn scan off in your profile: SCAN="no".

monstermudder78 · 2008-08-17 17:26:08

floke wrote:

Still no beans for me - I created a profile, installed netcfg etc. but no joy. No connection at boot and need to 'netcfg2 home' one into desktop to connect.

If it will connect once you are in the desktop, I don't think it would be a problem with the scan setting. As mamr said, make sure net-profiles is in your daemons list. The other thing that you might check is if you have multiple profiles in network.d, make sure the right one is being used at start-up. I am new to netcfg2 so I am not sure how netcfg2 picks the right profile to use but it might be something to look into.

petelewis · 2008-08-17 17:42:17

In case it helps, I'm using the line:

NETWORKS=(auto-wireless wlan0)

in my rc.conf. I then have a profile set up in /etc/network.d/ which was adapted from one of the files in the "examples" subdirectory.

It might also be worth noting that I got this working using the default ARCH kernel. I also tried using the fbcondecor kernel from the AUR (which appears to be 2.6.25 rather than 2.6.26) and the SCAN="no" fix stopped working. Might be something else to try.... :-)

ghostcat · 2008-08-18 14:04:34

Don't know if this is the same problem. The new /etc/rc.d/network script has a new test to see if the wireless LAN is associated. This fails with the message "Could not associate ath0 - try increasing WIRELESS_TIMEOUT and check network is WEP or has no security".

It turns out that (at least for the madwifi driver) the driver does not associate until it is given a valid IP address. This means that regardless of the timeout value this test will always fail.

vjoe · 2008-08-26 10:42:41

petelewis wrote:

Right - I have managed to figure this out now. In the network profile file, changing SCAN="yes" to SCAN="no" made it work first time.
(I'd previously set it in /etc/rc.conf and hadn't realised that it was profile specific - as said on the wiki page.)
Hope this works for others too :-)

This didn't work for me. Any ideas?

iphitus · 2008-08-26 11:34:39

Ahhhhhhh lots of problems all mixed up. Not sure what to say to who, but here's a pile of suggestions that may work for some.

For those who have to run netcfg TWICE for it to work, give the netcfg in [testing] a go. This was due to some workarounds for some hardware that in turn messed up other hardware.

If you're using netcfg from [testing], you may need to experiment with different QUIRKS=() options. They're a pile of hacks and workarounds that some hardware needs. If you're having problems, the best thing is to use trial and error and find what works. They're not all documented, but you can find them pretty easily in the code here within wireless_up()
http://projects.archlinux.org/?p=netcfg … br;hb=HEAD

The SCAN option can cause problems on some crap hardware, so if the above workarounds havn't worked, try disabling it.

ghostcat: I suggest you file a bug with the madwifi developers, that's absolutely stupid behaviour by the driver. In the meantime, netcfg from [testing] supports a QUIRK=(predown) option that works around that. No workarounds will be merged to rc.d/network for retarded drivers.

Also.... WPA works more reliably than WEP (most QUIRKS are for wep connections). So give that a go if you have access to the AP settings. It's more secure too

Last edited by iphitus (2008-08-26 11:37:59)

vjoe · 2008-08-26 12:19:11

iphitus, basically the profile doesn't load in boot. Actually, there is no message related to netcfg2 or the profile during the boot. I always have to do "netcfg2 profile" after booting which is boring...

Any ideas?

My profile file:

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes" (already tried with no)
SECURITY="wpa"
ESSID="hugenetwork"
KEY="key"
IP="dhcp"
TIMEOUT=20

rc.conf:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_GB.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="UTC"
KEYMAP="pt-latin9"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(r8169 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore fuse)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="hugelaptop"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(hugenetwork)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(@syslog-ng net-profiles @netfs @crond @alsa @fam @hal @laptop-mode slim)

This is strange because one month ago it worked fine. Now that I have the laptop back and reinstalled arch, it doesn't!

Arch Linux

#1 2008-08-16 09:29:23

[SOLVED] Netcfg on boot-up doesn't work since update

#2 2008-08-16 12:41:05

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#3 2008-08-16 12:52:15

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#4 2008-08-16 13:33:01

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#5 2008-08-16 13:43:51

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#6 2008-08-16 13:48:59

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#7 2008-08-16 17:34:25

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#8 2008-08-16 18:22:57

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#9 2008-08-16 18:35:37

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#10 2008-08-16 19:16:28

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#11 2008-08-16 19:23:17

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#12 2008-08-16 19:51:48

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#13 2008-08-16 20:30:01

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#14 2008-08-16 22:19:07

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#15 2008-08-16 22:22:45

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#16 2008-08-17 01:06:27

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#17 2008-08-17 07:52:08

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#18 2008-08-17 14:08:50

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#19 2008-08-17 16:28:40

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#20 2008-08-17 17:26:08

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#21 2008-08-17 17:42:17

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#22 2008-08-18 14:04:34

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#23 2008-08-26 10:42:41

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#24 2008-08-26 11:34:39

Re: [SOLVED] Netcfg on boot-up doesn't work since update

#25 2008-08-26 12:19:11

Re: [SOLVED] Netcfg on boot-up doesn't work since update

Board footer