[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gNewSense-users] Lemote: network interfaces down at startup

From: Sam Geeraerts
Subject: Re: [gNewSense-users] Lemote: network interfaces down at startup
Date: Wed, 05 May 2010 23:04:50 +0200
User-agent: Thunderbird (X11/20100402)

Federico Bruni schreef:
Hi all,

I have the following problem:

when I start the system network interfaces are all down (except for lo).
I'm not using any network manager.

I used rcconf to disable /etc/init.d/networking, in order to avoid waste
of time at startup (because interfaces are down so DHCP makes several
tries in vain).

I had a quick look at this. The wifi chip is switched on by /etc/init.d/yeeloong-base. The boot sequence starts with runlevel S (including networking), followed by runlevel 2 (including yeeloong-base). So it tries to bring up the network while it is still unavailable.

This is my unconfirmed suspicion. If this is true then you should be able to get it working by linking /etc/init.d/yeeloong-base in /etc/rcS.d/ before networking.


And wireless works fine.
I just wonder what this message really means:

Error for wireless request "Set Frequency" (8B04) :
    SET failed on device wlan0 ; Operation not supported.

What does it mean? I cannot set the wireless channel?

A quick search on the Web showed me that this also seems to happen for some other wifi drivers. If your wifi connection works I wouldn't worry about it much.

Two weird things:
* if /etc/init.d/networking is enabled at startup the above procedure
does not work, so I can't get wireless connection working

See suggestion above.

* if /etc/init.d/networking is disabled I get an error message at
startup: "Starting NFS common utilities: statd failed!"

Sounds like the NFS init script could use some more checks. Because NFS is only useful with a network connection this is also nothing to worry about.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]