the new networking module thing tries to configure my wireless interfaces out of the blue ignoring my nicely hand-crafted config in /etc/pcmcia/wireless.opts I don't feel like reinventing the wheel, so I just deleted this strange new module. However, I'd prefer an option for /etc/conf.d/wireless to disable this new "feature" alltogether happens with baselayout 1.11.3 Reproducible: Always Steps to Reproduce: 1. 2. 3.
so dont configure / add that net init script
hello? you've modified the /etc/pcmcia/network script to invoke the /etc/init.d/net.whatever scripts - this is the only chance to get the ip address set. since pcmcia-cs was modified to use the gentoo init.d scripts, somebody should take care they don't conflict. since the last baselayout update, they do conflict
not a baselayout problem then, we dont deal with pcmcia
Hmmm... and we have influence on baselayout, it seems.
I've got this request fixed in my net-scripts code as we'll be needing it for supplicant support anyway Hopefully I can get it synced with agriffis soon so we can close this one :)
well, if "baselayout" thinks the best solution is not to use their scripts, i'd opt for not using them at all... it's already quite annoying to configure /etc/init.d/net.eth0 to be able to cope with different settings based on the pcmcia scheme... why not drop this and use the "normal" pcmcia cs scripts?
Because not all wireless cards are pcmcia and the wireless module can do much much more than the pcmcia wireless.opts can. Personally, I don't use pcmcia-cs - my lappy with a pcmcia wireless card does not need it. pcmcia-cs is only really needed for 16-bit cards anyway.
i can't do schemes. I need something quick to reconfigure my whole network. like cardctl scheme <whatever> anyway, obviously the pcmcia scripts are broken then.. what to do about it?
Some options 1) Wait for this to be fixed 2) Remove the wireless module from /lib/rcscripts/net.modules.d (be warned that future upgrades to baselayout will put it back) 3) Go back to baselayout-1.9.x
uberlord, i don't mean to attack you there. I already fixed my system before reporting the bug along with the other half of a dozend bugs introduced by the new baselayout. Thanks for your suggestions anyway :) I'm just baffled about the lack of communication between the developers and/or to close to not-existing testing done... i don't see any other explanation, how something this bad (like baselayout) can go into portage
baselayout-1.11.3 is masked for a reason...
i'm using 1.11.4, and it's not masked but ~x86 i mean a tad more QA would be nice... anyway, i took a look at the "new" scripts and converted my config. works for me now[tm], so feel free to close the bug
~ARCH is a mask as well.
had a little discussion with vapier, and I came to the following conclussion: the pcmcia_cs package should inform the user that it's better to use the baselayout network scripts. Maybe it shouldn't even invoke net.$iface start, because hotplug already does that. Maybe it's best to disable them completly.
This should be fixed in baselayout-1.11.5 You can put the following into /etc/conf.d/net to disable wireless configuration module=( "!wireless" )
that's nice, however, this bug is about disabling the pcmcia_cs scripts, not the gentoo scripts
You can disable the wireless network scripts simply by not adding any configuration parameteres there - or, if you're using linux-2.6.13-rc1 or newer, you can use the brand new sys-apps/pcmciautils. Closing as WONTFIX.
