Hi there! With this mail I cc:ed for the last time the pkg-fso-maint@ mailing list: that list should be used only for Debian packaging issues and not for "general" discussion. I set R-T and M-F-T to continue on the smartphones-kernel@ mailing list.
Michael, please correct me if you think I am wrong. On Mon, 02 Mar 2009 20:10:17 +0100, Christian Adams wrote: > 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 .. According to [1] (one of the first links Google returned for /proc/net/dev): Interface statistics The /proc/net/dev file contains information about the configured network interfaces. [1] http://www.linuxdevcenter.com/pub/a/linux/2000/11/16/LinuxAdmin.html Thus, if I read it correctly, I was wrong. However, there is still something I do not understand... - without frameworkd eth0 (i.e. the WiFi interfaced) is *always* present in /proc/net/dev, starting from the simple fact of loading the module. The same happens for iwconfig: simply loading the module causes iwconfig to show eth0 as well. For eth0 to be shown by ifconfig, I need to bring it up with `ifconfig eth0 up` at least. Some notes: * AFAIK Debian does not enable by default any network interfaces if it is not listed in /etc/network/interfaces, which in my case contains only commented lines for eth0 * I also tried booting with the ar6000 modules disabled (adding "install ar6000 /bin/true" in a file in /etc/modprobe.d/) and nothing changed, i.e. as soon as I load the ar6000 module eth0 shows up in /proc/net/dev - with frameworkd eth0 is not present in /proc/net/dev at boot, but iwconfig shows it. However, since it is now managed by frameworkd, `ifconfig eth0 up` gives me the "No such device" error. First question: I cannot find how to enable it via frameworkd, is this documented somewhere? If I enable it through openmoko-panel-plugin, then eth0 shows up in /proc/net/dev and `ifconfig eth0 up` now works. If I then disable it, again through openmoko-panel-plugin, eth0 disappears from /proc/net/dev. Second question: the behavior WRT /proc/net/dev seems to be completely different than how the iwl3945 works on my IBM/Lenovo ThinkPad X60. On this laptop, even when the hardware switch is off (which AFAIK should manage by the rfkill module), wlan0 is still present in /proc/net/dev, but `ifconfig wlan0 up` gives the "No such device" error. Thus, here the question: what is the difference in the two cases, i.e. ar6000 and iwl3945? Should not they behave similarly WRT /proc/net/dev? I think it is enough for today about this issue :-D Thx, bye, Gismo / Luca
pgpW7Qx6non5I.pgp
Description: PGP signature
_______________________________________________ pkg-fso-maint mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint
