2008/12/6 Darren Salt <[EMAIL PROTECTED]>: > I demand that Santi Béjar may or may not have written... > >> 2008/12/3 Darren Salt <[EMAIL PROTECTED]>: >>> Prefer to use rfkill where available for toggling wireless & bluetooth. > >> Why do you need support for rfkill in /etc/acpi/actions/wireless.sh? > > The interface needs to be properly brought down when the device is disabled > (it disappears) and up again when the device is re-enabled. > >> I'm running 2.6.28-rc5 without /e/a/a/wireless.sh and the wireless toggle >> works just fine. What I think should be done is to exit when >> /e/a/a/wireless.sh detects that the rfkill is in use. > > No. I'm using /etc/network/interfaces: re-enabling the device would leave the > interface unconfigured but with ifupdown thinking that it's configured, so > I'd have to run "ifdown ra0; ifup ra0" as root.
With an old laptop I had an external wireless card (pccard) and everything worked fine without all this. Maybe it was the hotplug subsystem that did all this, but then why it doesn't happen now? > > Also, writing to the sysfs file may be superfluous but it's also harmless, so > there's no point in avoiding the write. > >> (I don't have bluetooth) > > It's required for the bluetooth toggle to work at all. Thanks, I didn't know it. Santi _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
