More from acer_acpi land; thanks to a nudge in the right direction, I’ve been poking around Launch Manager using ’strings’, looking for any and all of interest that might come up. As some may have noticed, acer_acpi isn’t intelligent about detecting hardware (i.e. we don’t) - hence on my system, I get a /proc/acpi/acer/bluetooth, even though my laptop (Aspire 5021) doesn’t have it (Of course, we can’t decide based on the model number - the BIOS only tells us the series, 5020 in this case, and there are other laptops in that series that do have bluetooth).

So how does Launch Manager do it? Some hidden, special, undocumented feature? Nope - it just has a list of PCI ID’s. Not really a lot of use, since in the case of wireless, you could change the mini PCI card, and then what - acer_acpi won’t turn on the wireless because it “isn’t supported”? (Of course, I have no idea if Acer’s BIOS limits which wireless cards can and can’t be connected - we’ll have to assume, unless otherwise disproven, that there is no limit). Can’t go by poking at a PCI slot, since acer_acpi runs on lots of different hardware. So wireless detection is out. (We could potentially get a false positive, but I’ve yet to see any system that uses acer_acpi that lacks wireless).

Bluetooth? Bluetooth is just an internal USB dongle - so we _could_ go by the manufacturer and device ID… unless you happen to have an external USB device that matches - false positive, we show a bluetooth option when we shouldn’t.

Post A Comment

You must be logged in to post a comment.