I'm using a Dell Inspiron XPS Gen II laptop, which implements the 2915 chipset. I have a recent (less than a week old) Gentoo 2005.1 built from stage1, using the gentoo-sources 2.6.12-gentoo-r10 kernel. I had no problem emerging the ipw2200 ebuild. When I reboot the system, the ipw2200 module loads correctly, and I can verify it via lsmod. But, iwconfig eth0 says "no wireless extensions", and ifconfig eth0 reports "Device not found". Now, the workaround is simple. If I do: rmmod ipw2200 && modprobe ipw2200 The problem is solved. Not only does the card become available, all my info, IP, netmask, broadcast, etc, set in /etc/conf.d/net is set correctly, even though I don't re-run any startup scripts. So, I'm stumped. The module loads on boot, but doesn't work. Unloading and reloading solves the problem. I suppose I can hack one of the /etc/init.d scripts to explicitly do the rmmod/modprobe, but that's not a nice solution, and it's certainly not "the Gentoo way...". Help! Thanks, -Mark Reproducible: Always Steps to Reproduce: 1. reboot system, wireless module is loaded, card does not work. 2.rmmod/modprobe solves the problem. Actual Results: After reboot wireless connection does not work. Expected Results: I should work. mjb@mars ~ $ emerge info Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r1, 2.6.12-gentoo-r10-mjb-custom i686) ================================================================= System uname: 2.6.12-gentoo-r10-mjb-custom i686 Intel(R) Pentium(R) M processor 2.13GHz Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -mcpu=pentium4 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=pentium4 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://gentoo.chem.wisc.edu/gentoo/ http://gentoo.mirrors.tds.net/gentoo http://gentoo.seren.com/gentoo http://adelie.polymtl.ca/" MAKEOPTS="-j6" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts avi berkdb bitmap-fonts cdr crypt css cups curl dvd dvdr dvdread eds emboss encode esd fam foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib jpeg libg++ libwww mad mikmod motif mozilla mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl spell ssl tcpd tiff truetype truetype-fonts type1-fonts vorbis xine xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
What does a plain call to `iwlist` and `ifconfig -a` yield upon boot-up (before your manual fix)?
'iwlist' gives a usage error: mars mjb # iwlist Usage: iwlist [interface] scanning [interface] frequency [interface] channel [interface] bitrate [interface] rate [interface] encryption [interface] key [interface] power [interface] txpower [interface] retry [interface] ap [interface] accesspoints [interface] peers [interface] event I'm not sure which of the iwlist options you want me to demonstrate.... Here's iwconfig output: mars mjb # iwconfig eth0 eth0 unassociated ESSID:off/any Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00 Bit Rate=0 kb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 So, clearly, it's not associating with the AP. But why does unloading and reloading fix it? Here's ifconfig -a output: mars mjb # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:13:CE:1A:82:66 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:17 Base address:0xe000 Memory:dcfef000-dcfeffff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:60 errors:0 dropped:0 overruns:0 frame:0 Finally, here's the same output after a simple rmmod ipw2200 && modprobe ipw2200: mars mjb # iwconfig eth0 eth0 IEEE 802.11b ESSID:"linksys" Nickname:"linksys" Mode:Managed Frequency:2.437 GHz Access Point: 00:06:25:5A:DC:85 Bit Rate=11 Mb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=86/100 Signal level=-43 dBm Noise level=-86 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 mars mjb # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:13:CE:1A:82:66 inet addr:216.144.205.109 Bcast:216.144.205.111 Mask:255.255.255.248 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:699 errors:0 dropped:0 overruns:0 frame:0 TX packets:459 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:465278 (454.3 Kb) TX bytes:64404 (62.8 Kb) Interrupt:17 Base address:0x2000 Memory:dcfef000-dcfeffff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:60 errors:0 dropped:0 overruns:0 frame:0 TX packets:60 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3000 (2.9 Kb) TX bytes:3000 (2.9 Kb) Please let me know what other info I can provide.... Thanks!
Please see if you can reproduce this using net-wireless/ipw2200-1.0.7-r1.