Baselayout 1.12.4-r7 breaks wireless connectivity on my rt61 chip based wireless pci card (Edimax EW-7128g). I traced the problem to /lib/rcscripts/net/iwconfig.sh where the definition of iwconfig_set_mode (on line 118 onwards) is as follows: iwconfig_set_mode() { local iface="$1" mode="$2" [[ ${mode} == $(iwconfig_get_mode "${iface}") ]] && return 0 # Devicescape stack requires the interface to be down interface_down "${iface}" if ! iwconfig "${iface}" mode "${mode}" ; then eerror "${iface} does not support setting the mode to \"${mode}\"" return 1 fi interface_up "${iface}" } The problem with this is that the driver for the card requires the interface to be up, otherwise it'll claim there are no wireless extensions on the device when queried by iwconfig. As a result the init script will fail. The driver I'm using does not have a Gentoo ebuild since none of rt2x00, rt2400 rt2500 drivers in portage work for my card. Instead I downloaded the driver from the manufacturer's website. It identifies itself as RT61 Linux STA Driver version 1.0.4.0, available here: http://www.ralinktech.com/drivers/Linux/RT61_Linux_STA_Drv1.0.4.0.tar.gz If I change line 123 in iwconfig.sh to ensure the interface is up everything works just fine. Similarly manual configuration of the card using iwconfig as normal works as well. Here are the relevant bits from emerge --info Portage 2.1-r2 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.16-gentoo-r7 i686) ================================================================= System uname: 2.6.16-gentoo-r7 i686 Pentium III (Katmai) Gentoo Base System version 1.12.4 app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.3.5-r2, 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu"
How would you resolve this as all wireless drivers in portage and kernel work with the interface down, and some require the interface to be down? rt2x00 should work with your card - and will eventually, so I'm loath to do something driver specific.
We can assume rt2x00 and more specifically the dscape stack does the right thing. But I might be wrong, but is this really a gentoo/baselayout bug? As you stated, you downloaded the rt61 driver from the Ralink website, that package is not in portage. The rt61 package from the rt2x00.serialmonkey.com project is. If that is the case, a lot of fixes from rt2400 and rt2500 have been ported to rt61 as well, among some fixes about pre-up configuration. Even when that has not been done it would be a small fix, since this issue is only with essid and bssid I believe. At least that issue was also present in rt2400 and rt2500 and had been fixed. Basicly it comes down to the fact that the drivers from the Ralink website are doing the bad thing on most occasions. And I would not recommend making changes to baselayout specifically for those drivers.
Ivo is the rt2x00 project lead, and knows the rt* drivers inside and out. Take his advice and try out the drivers from the serial monkey web site instead. Either way, this is an upstream issue.
$ eix rt61 * net-wireless/rt61 Available versions: 1.1.0_beta1 Homepage: http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page Description: Driver for the RaLink RT61 wireless chipsets It is actually in portage :)
(In reply to comment #4) > It is actually in portage :) Bleh for the reporter not looking in portage. Double bleh for me not doing that either :/
