You are not logged in.

#1 2009-01-28 21:47:44

mm23
Member
Registered: 2008-11-30
Posts: 9

networking daemons fail on boot, but not after

This is a bizarre issue I can't seem to figure out myself.

Whenever my system boots up, it hangs for 30+ seconds trying to connect to the internet and eventually times out and fails. My rc.conf and all that is fine and worked fine prior to the kernel update to 2.6.28.

It's strange because if I manually do an /etc/rc.d/network restart it works fine. It just doesn't on boot.

I have the module (iwl3945) set to load during boot

MODULES=(acpi-cpufreq cpufreq_ondemand cpufreq_powersave e100 mii iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)

And I have my networking daemons starting up in this order:

DAEMONS=(syslog-ng crond acpid hal laptop-mode lapsusd cpufreq alsa network net-profiles netfs openntpd gdm)

It's seriously bizarre and I've rearranged the order about 9 times but it's not doing any good. If I set the network/net-profiles daemons to start in rc.local AFTER everything else it works fine. But anytime before that? No good.

Is it something with my modules? Is it trying to start the daemon before the module is loaded or something? I don't get it. I don't need to do any modprobing to make it work after I am booted and logged in... it just works after I restart the daemons.

And yes, I have the iwlwifi ucode and have reinstalled it about 300 times to no effect.

Last edited by mm23 (2009-01-28 21:48:57)

Offline

#2 2009-01-28 21:51:30

ndlarsen
Member
From: Denmark
Registered: 2005-11-02
Posts: 157

Re: networking daemons fail on boot, but not after

Try setting iwl3945 as the last module loaded. Might help.


I made it long
as I lacked the time to make it short...

Offline

#3 2009-01-29 04:15:27

u_no_hu
Member
Registered: 2008-06-15
Posts: 453

Re: networking daemons fail on boot, but not after

Do you use network or net-profiles? you dont need both..


Don't be a HELP VAMPIRE. Please search before you ask.

Subscribe to The Arch Daily News.

Offline

#4 2009-01-31 21:24:55

mm23
Member
Registered: 2008-11-30
Posts: 9

Re: networking daemons fail on boot, but not after

Seems it's an issue with my card or computer or God hates me or something.

I've tried about every possible thing I could but no matter what happens iwl3945 will ALWAYS fail on it's first start, no matter what. I think it is a netcfg problem but I am not sure.

The only solution is to let it fail (which makes me wait for 30 seconds at boot and makes starting ssh/ntp/other stuff impossible except manually) and have it restart itself in rc.local. I cannot find any solutions through google or searching the forums, and downgrading to 2.6.27 fixes the issue but is otherwise impractical.

This is why I hate Linux wireless.

Offline

#5 2009-01-31 21:32:11

Diaz
Member
From: Portugal
Registered: 2008-04-16
Posts: 366

Re: networking daemons fail on boot, but not after

you don't need both network and net-profiles to load, maybe that's why you're having the issue. You load network daemon if you configure your network in rc.conf, or you load net-profiles to confifure your network with netcfg.

try to see dmesg, or any other logs for error or other strange messages wink

Offline

#6 2009-02-02 16:25:53

zenlord
Member
From: Belgium
Registered: 2006-05-24
Posts: 1,221
Website

Re: networking daemons fail on boot, but not after

Second u_no_hu and Diaz here: network and net-profiles *could* conflict.

Besides: iwl3945 is a kernel-module, so you don't have to specify it in MODULES=(). Keep it as simple as possible!

Zl.

Offline

#7 2009-02-04 11:56:54

dobedo
Member
From: Belgium
Registered: 2008-10-04
Posts: 113

Re: networking daemons fail on boot, but not after

I have also an IWL3945 and I had exactly the same problem.
I've never been able to configure netcfg to make it work at startup...then I switched to WICD and it works perfectly now.

Offline

Board footer

Powered by FluxBB