I have a link called net.wlan0 to the net.eth0 script of baselayout-1.11.5. At boot time, this script does not properly set up wireless parameters, as defined in /etc/conf.d/wireless. The ESSID, the ESSID WEP Key and other set up is not respected at boot time. Reproducible: Always Steps to Reproduce: 1. /etc/init.d/net.wlan0 (at boot time) 2. rmmod ndiswrapper 3. /etc/init.d/net.wlan0 restart Actual Results: At boot time (step 1) the output to console is: * Bringing up wlan0 * Configuration not set for wlan0 - assuming dhcp * wlan0 dhcp * Running dhcpcd ... <timeout> [!!] iwconfig shows that neither ESSID nor WEP key is set. Expected Results: On manual restart of the service, everything is okay: * Starting wlan0 * Configuring wireless network for wlan0 * wlan0 connected to "<ESSID>" at 00:30:AB:21:1A:CA * in managed mode on channel 1 (WEP enabled - restricted) * Bringing up wlan0 * Configuration not set for wlan0 - assuming dhcp * wlan0 dhcp * Running dhcpcd ... * wlan0 received address 192.168.25.4 [ ok ] Portage 2.0.51-r2 (default-x86-2004.2, gcc-3.4.2, glibc-2.3.4.20041021-r0, 2.6.9 -gentoo-r2 i686) ================================================================= System uname: 2.6.9-gentoo-r2 i686 Intel(R) Pentium(R) M processor 1600MHz Gentoo Base System version 1.6.5 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O2 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/s hare/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dv ipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config / /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox userpriv" GENTOO_MIRRORS="ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://mirror s.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/ gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi acpi4linux aim alsa antlr apache2 apm audiofile avi berkdb bitmap-fo nts bluetooth bonobo cddb cdr chroot crypt cups devfs26 doc dvd encode esd ether eal evo f77 fam foomaticdb gda gdbm gif gimp gimpprint glade gnome gpm gtk gtk2 gtkhtml guile ieee1394 imagemagick imlib irda java jpeg ldap libg++ libwww mad m box mikmod mmx motif mozilla mpeg mpeg4 msn ncurses nls nptl odbc oggvorbis open gl pam pcmcia pda pdflib perl png postgres ppds python quicktime readline samba scanner sdl slang sox spell sse ssl svga tcltk tcpd tetex truetype usb vanilla x 86 xinerama xml2 xmms xv zlib"
I have the same result
Could you post the FULL output of the boot message please? I would like to see the bit before * Bringing up wlan0 BTW, if the wireless configuration failed - for whatever reason - all wireless configuration info is stripped
Well, there's not much more to include, the full context of the boot messages is: ... * Setting user font ... * Starting lo * Bringing up lo ... * Starting wlan0 loadndisdriver: loadndisdriver: main(479): version 0.11 started * Bringing up wlan0 * Configuration not set for wlan0 - assuming dhcp * wlan0 dhcp * Running dhcpcd ... * Starting S.M.A.R.T. monitoring daemon ... ... As I said, calling the same script from a shell after boot time, does configure everything well, regardless of the ndiswrapper module beeing loaded or rmmod'ed previously by me.
It looks like that ndiswrapper is too slow in enabling wireless extensions the first time it's loaded. How are you starting ndiswrapper?
I don't start it at all, the module is bound via alias wlan0 ndiswrapper to the ndiswrapper. I added "post-install ndiswrapper sleep 10" to modules.conf and this doesn't change anything. However, the behaviour of the init-script is slightly different from the ones I describes originally, it does not (re-)start after boot time as well, when ndiswrapper was rmmod'ed or not yet loaded.
For the time being, add ndiswrapper to /etc/modules.autoload.d/kernel-version and remove the entry in /etc/modules.d (or wherever you added it) This should be fixed baselayout-1.11.6
Damn, that was the situation before, my intention was to trim the list of autoloaded modules, since I do not always use WLAN. But for now, I am turning back to old state. How will baselayout 1.11.6 deal with this problem?
If the interface does not exist when we start then we modprobe ${iface} In your case, ndiswrapper would get loaded.
But, as shown in comment #3, ndiswrapper _is_ loaded, when accessing wlan0 device, because it's "aliased" to wlan0 ...
It's not loading at the correct point though .....
Fixed in baselayout-1.11.6 Reopen bug if it's not
It is.
