After upgrading to gentoo-sources-2.6.33, my wireless network fails to come up. The init script is trying to get an IP address via DHCP, but it times out because the wireless setup hasn't happened. I have to run: iwconfig wlan0 essid "Blah" key "0123456789ABCDEF" ap "any" and then restart the net.wlan0 service to successfully bring up the wireless network connection. I think this might be a udev (HAL?) issue, since I can boot with 2.6.22-gentoo-r6 and everything is good. The new kernel must be giving different information to the system, but I can't figure out how to track down what has changed. My wireless card uses the p54pci module, and here is my /etc/conf.d/net script: preferred_aps=("Blah") associate_order_wlan0="forcepreferred" key_Blah="0123456789ABCDEF" Reproducible: Always Steps to Reproduce: 1. boot with 2.6.33-gentoo 2. 3. Actual Results: wireless autoconfiguration fails Expected Results: wireless autoconfiguration should succeed as with 2.6.22-gentoo-r6 Portage 2.1.7.17 (default/linux/x86/10.0/desktop, gcc-4.3.4, glibc-2.10.1-r1, 2.6.33-gentoo i686) ================================================================= System uname: Linux-2.6.33-gentoo-i686-Intel-R-_Pentium-R-_III_Mobile_CPU_1000MHz-with-gentoo-1.12.13 Timestamp of tree: Wed, 03 Mar 2010 07:00:01 +0000 app-shells/bash: 4.0_p35 dev-java/java-config: 2.1.10 dev-lang/python: 2.6.4-r1 dev-util/cmake: 2.6.4-r3 sys-apps/baselayout: 1.12.13 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.9.6-r2, 1.10.3, 1.11.1 sys-devel/binutils: 2.18-r3 sys-devel/gcc: 4.3.4 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6b virtual/os-headers: 2.6.30-r1 ACCEPT_KEYWORDS="x86" ACCEPT_LICENSE="*" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -pipe -march=pentium3 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-O2 -pipe -march=pentium3 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests buildpkg distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync" GENTOO_MIRRORS="http://mirrors.xservers.ro/gentoo/ http://mirror.its.uidaho.edu/pub/gentoo/" LANG="en_CA.UTF-8" LDFLAGS="-Wl,-O1" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/layman/x11 /home/james/software/overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="a52 aac acl acpi alsa amr artworkextra bash-completion branding bzip2 cairo cdda cdr cjk cli consolekit contrast cracklib crypt cups curl custom-cflags cxx dbus dga dirac djvu dri dts dv dvd dvdr dvi emboss encode epiphany evo exif expat fam ffmpeg firefox flac font-server fortran fpx gd gdbm gedit gif gnome gnome-keyring gnutls gphoto2 gpm graphviz gs gsm gstreamer gtk gtkhtml guile hal hbci hdri iconv imagemagick imlib ipv6 java java5 java6 jbig jce jpeg jpeg2k kerberos lame lcms libnotify lua mad md5sum mikmod mmap mmx mng modules mozilla moznocompose moznoirc moznomail mozsvg mp3 mp4 mpeg mudflap nas nautilus ncurses netbeans network nls nptl nptlonly nsplugin nvidia offensive ofx ogg openal openexr opengl openmp pam pcre pdf perl pic png posix ppds pppd python qt3support quicktime raw readline reflection schroedinger sdl session speex spell spl sse ssl startup-notification svg sysfs t1lib tcpd theora threads thunar tiff timezone truetype unicode usb v4l v4l2 vcd vhook videos vidix vorbis wmf x264 x86 xcomposite xinetd xml xmp xorg xprint xscreensaver xulrunner xv xvid xvmc zlib" ALSA_CARDS="intel8x0 intel8x0m usb-audio" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="fbdev nouveau nv nvidia vesa" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Hi, I think you'll get answer more quickly if you try at gentoo forums (http://forums.gentoo.org), "Kernel & Hardware" maybe the best place. Be sure to provide things like: 1. lspci (maybe only line showing what wireless dev you have) 2. relevant parts of system logs, thay may hold an answer already. Also prior to that, make sure that you've followed all steps covered in: http://www.gentoo.org/doc/en/kernel-upgrade.xml and re-emerged all packages that depend on /usr/src/linux. Best regards, Kacper Kowalik
This is probably a problem with wireless-tools. Try upgrading or using net-wireless/wpa_supplicant (or net-wireless/iw) instead.
Please provide the mentioned info on this bug, too. I'm reassigning this to the mobile herd. It doesn't appear to be a kernel issue as you are able to establish a connection manually which suggests HAL/wpa_supplicant broke. And can you please try the *latest stable* kernel (2.6.31-r10) and report back, so we can narrow the problem down? for "relevant system logs" use "dmesg | egrep 'p54|phy0|wlan0'" And could you please post the versions of HAL and wpa_supplicant installed?
(In reply to comment #3) > Please provide the mentioned info on this bug, too. I'm reassigning this to the > mobile herd. It doesn't appear to be a kernel issue as you are able to > establish a connection manually which suggests HAL/wpa_supplicant broke. > > And can you please try the *latest stable* kernel (2.6.31-r10) and report back, > so we can narrow the problem down? Okay, I tried the latest stable kernel as of this morning (2.6.32-r7), and that one works properly. To narrow it down, I also tried some other versions. 2.6.32-r11 works, and anything 3.6.33 and up exhibits the bug as described, so something has changed with the introduction of the 33 series. > > for "relevant system logs" use "dmesg | egrep 'p54|phy0|wlan0'" Here is the dmesg output using 2.6.32-r11: p54pci 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5 p54pci 0000:02:03.0: firmware: requesting isl3886pci phy0: p54 detected a LM86 firmware p54: rx_mtu reduced from 3240 to 2376 phy0: FW rev 2.13.12.0 - Softmac protocol 5.9 phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES phy0: hwaddr 00:60:b3:13:22:0c, MAC:isl3890 RF:Duette3 phy0: Selected rate control algorithm 'minstrel' Registered led device: p54-phy0::assoc Registered led device: p54-phy0::tx Registered led device: p54-phy0::rx Registered led device: p54-phy0::radio p54pci 0000:02:03.0: is registered as 'phy0' wlan0: direct probe to AP 00:24:a5:6f:28:a2 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:24:a5:6f:28:a2 (try 1) wlan0: deauthenticating from 00:24:a5:6f:28:a2 by local choice (reason=3) wlan0: direct probe to AP 00:24:a5:6f:28:a2 (try 1) wlan0: deauthenticating from 00:24:a5:6f:28:a2 by local choice (reason=3) wlan0: direct probe to AP 00:24:a5:6f:28:a2 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:24:a5:6f:28:a2 (try 1) wlan0: authenticated wlan0: associate with AP 00:24:a5:6f:28:a2 (try 1) wlan0: RX AssocResp from 00:24:a5:6f:28:a2 (capab=0x431 status=0 aid=4) wlan0: associated wlan0: no IPv6 routers present I will reboot to 33 and post output in a couple of minutes. > > And could you please post the versions of HAL and wpa_supplicant installed? > sys-apps/hal-0.5.13-r2 I'm not using wpa-supplicant; I use iwconfig: net-wireless/wireless-tools-29
Alright, here is the dmesg output under a 33 kernel. After it failed to automatically configure the wireless settings, I manually configured them, then restarted net.wlan0. This is the aggregate result (almost the same as the 32-r11 case): p54pci 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5 p54pci 0000:02:03.0: firmware: requesting isl3886pci phy0: p54 detected a LM86 firmware p54: rx_mtu reduced from 3240 to 2376 phy0: FW rev 2.13.12.0 - Softmac protocol 5.9 phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES phy0: hwaddr 00:60:b3:13:22:0c, MAC:isl3890 RF:Duette3 phy0: Selected rate control algorithm 'minstrel' Registered led device: p54-phy0::assoc Registered led device: p54-phy0::tx Registered led device: p54-phy0::rx Registered led device: p54-phy0::radio p54pci 0000:02:03.0: is registered as 'phy0' ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: direct probe to AP 00:24:a5:6f:28:a2 (try 1) wlan0: direct probe to AP 00:24:a5:6f:28:a2 (try 2) wlan0: direct probe responded wlan0: authenticate with AP 00:24:a5:6f:28:a2 (try 1) wlan0: authenticated wlan0: associate with AP 00:24:a5:6f:28:a2 (try 1) wlan0: RX AssocResp from 00:24:a5:6f:28:a2 (capab=0x431 status=0 aid=4) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: no IPv6 routers present
> It doesn't appear to be a kernel issue as you are able to > establish a connection manually which suggests HAL/wpa_supplicant broke. I don't think it has anything to do with HAL. The whole autoconfigure thing is being triggered by the p54pci module being loaded. wlan0 appears on the "device initiated services" boot line. Just to be sure, I removed hald from all my runlevels, and the autoconfiguration still happened. I guess it's a udev thing. Since the only thing that has changed between the successful case and the failing case is the kernel version, it seems reasonable to suspect that a change in the kernel is causing the failure. For some reason, the net script doesn't call the wireless setup script before calling the interface setup script, with >=33 kernels. If I had to guess (and I do have to guess, I guess), I'd say that the way the kernel is describing the hardware has changed from between 32 and 33, and the net script no longer recognizes wlan0 as a wireless NIC, the way it does with 32 kernels. I tried parsing the net script in /etc/init.d, but it's pretty opaque to me. Maybe someone could give me some tips on where in the script there is a test for wirelessness, and where the calls are that parse all the wireless settings in /etc/conf.d/net. I'm not having much luck finding it on my own. TIA.
This should likely be a duplicate of http://bugs.gentoo.org/show_bug.cgi?id=321663 but this one was first. For both wireless is changing and iwconfig is outdated according to the wireless mailing-list ----------snip---------------- > Encryption key:off > Power Management:off > Link Quality=70/70 Signal level=-1 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > doesn't care? since we use wpa? on the enc off? The encryption is being handled by mac80211, wpa_supplicant, and the device. The "encryption key:off" should be ignored. The wireless extension tools such as iwconfig are being phased out and do not always have the best information. -----------/snip--------------- in reply to a question on the kernel list. For me using openrc and baselayout-2 wlan0 just starts from wpa_supplicant from /etc/rc.conf and no need for an init script udev finds and loads modules and firmware fine using (current gentoo-sources 2.6.35-r4) no hald. using iw, crda, wpa_supplicant http://wireless.kernel.org/en/users/Documentation
Still valid on a fully updated system?
(In reply to comment #8) > Still valid on a fully updated system? I can't test it because I replaced the card.
*** This bug has been marked as a duplicate of bug 307191 ***
