[pkg-fso-maint] Kernel and wifi

Christian Adams morlac at morlac.de
Mon Mar 2 19:10:17 UTC 2009

Hash: SHA1


Am 01.03.2009 um 18:41 schrieb Luca Capello:
> Hi there!
> On Sat, 28 Feb 2009 20:46:13 +0100, gregor herrmann wrote:
>> On Sat, 28 Feb 2009 16:42:43 +0100, Christian Adams wrote:
>>>>> * I can start wicd and wicd-client.py later, without getting an  
>>>>> oops;
>>>>>   but (as before) I have no eth0 device?!
>>> eth0 gets enabled via frameworkd (there is also another way via  
>>> sysfs
>>> i currently don't remember)
> wlan should be present in /proc/net/dev as soon as you insert the
> module.  I guess with "enabled" you meant "brought up".

this - i think - should be discussed @om-kernel ..

>> Ah, I didn't know that, thanks.
> I do not remember how frameworkd works in this specific case, but I
> guess it disables every service (GSM, GPS, WiFi, Bluetooth) when it
> starts because this is the only way to deal with a consistent state at
> frameworkd boot.

right - if i understand it correctly

>>>> - should not this be ath0 or (which I would prefer) wlan0?
>> With 2.6.24 it's eth0, and I didn't find any hints for another name.
> Read below :-)
>>>> - can you check if udev has assigned a persistend ifname to the
>>>> device,
>>>>   please?  Look at
>>>>     /etc/udev/rules.d/70-persistent-net.rules
>> Yes:
>> # cat /etc/udev/rules.d/70-persistent-net.rules
>> [..]
>> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address} 
>> =="00:12:cf:8f:08:56", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
> I do not know if we need to blame the kernel, the ar6000 driver or  
> udev
> for not picking a "better" name.  I was under the impression that any
> WiFi interface should have the wlan* name, but I stopped being  
> surprised
> by the various ath*, ra* and so on.
>>> test a)
> [...]
>>> 	no probs found
>> Same here, except that I have wicd installed but not started.
>> But I could produce an oops later by combining manual "ifconfig eth0
>> down", activating wicd-client, and turning wifi on/off with o-p-p.
>> (Don't ask me how exactly ...)
> I know, I am sometime a bit boring, but I think the command order  
> would
> be a good start to understand what cause the oops.

IMHO the oops is caused by in background starting wicd trying to  
configure wifi and then starting
fso-frameworkd turning wifi off (eth0 disappears) and wmiconfig tries  
to access a not longer existing interface

> BTW, I have never asked it before, but does the oops happen with plain
> (i.e. not encrypted) WiFi networks as well?

i think (but not tested yet as is don't have (nor want) any not  
encrypted networks)
there is no differnce at all


> The only explanation I have is that frameworkd loads the module for  
> you,
> but I do not have the latest frameworkd sources here ATM to check.


> So it seems to me that the problem relies in the ar6000 module only,
> but I am not an expert, sorry.

same thoughts here

> I will prepare a new Debian kernel package based on a more recent Git
> snapshot (not sure if it will already 2.6.29), maybe the FSO-MS5  
> kernel
> is missing some patches.

and i will test it as soon it is available / i have the time to do so

> Thx, bye,
> Gismo / Luca

	christian (morlac) adams
- --
   eMail:	morlac at morlac.de
   Jabber:	morlac at skavaer.homelinux.org
- ------END CONTACT BLOCK------

Version: 3.1
- ------END GEEK CODE BLOCK------

Version: GnuPG v1.4.7 (Darwin)


More information about the pkg-fso-maint mailing list