Comment 15 for bug 357412

Revision history for this message
anjilslaire (anjilslaire) wrote : RE: [Bug 357412] Re: Failure using Aircraft-Manager with Jaunty UNR

Well, manually toggling the commannds

> sudo aircraft-manager-util AC_CHARGING off
> sudo aircraft-manager-util AC_CHARGING on

Seems to have fixed it, but I have since done a reinstall of karmic UNR to the machine. Strangely enough, the LIVE CD works in safe graphics mode, but after a full install th xorg fails and leaves a "snowing" GUI. Weird that X can't autodetect Intel 945 chpset.. BUt that's another issue unrelated to this thread/bug.

Thanks Brandon.

anjilslaire

From: <email address hidden>
To: <email address hidden>
Subject: RE: [Bug 357412] Re: Failure using Aircraft-Manager with Jaunty UNR
Date: Tue, 22 Dec 2009 16:51:06 -0800

Cool, I'll try that, thanks.
Here's a thought:
Since this is making calls to the hardware directly charging won't work even if the system is powered off) I would guess that it's associated to the BIOS or firmware in some way. Obviously resetting the BIOS to default values doesn't work, but what do you think about *flashing* the BIOS? Wouldn't that reset everything to a clean slate, BIOS/firmware/hardware-wise?

Just a thought. I'll try toggling things directly when I get a chance.

Thanks again, Brandon

> Date: Tue, 22 Dec 2009 18:56:35 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 357412] Re: Failure using Aircraft-Manager with Jaunty UNR
>
> Unfortunately, the code in aircraft-manager-util (the script that does
> the real work) looks a bit like magic to me. It uses a raw interface to
> the hardware ports and figuring out whether or not it does the right
> thing requires a lower level understanding of what the hardware is doing
> than I have.
>
> The best that I can suggest is to toggle the AC status. The following
> commands will do it:
>
> sudo aircraft-manager-util AC_CHARGING off
> sudo aircraft-manager-util AC_CHARGING on
>
> If that and the suggestions in the two threads that you referenced don't
> solve the problem, then my best guess would be that it's a problem with
> the battery. Folks on the 'Ubuntu on the Dell Mini' google group might
> have additional suggestions.
>
> --
> Failure using Aircraft-Manager with Jaunty UNR
> https://bugs.launchpad.net/bugs/357412
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Dell Inspiron Mini with Custom Dell UI: Confirmed
> Status in Ubuntu Netbook Remix: Confirmed
>
> Bug description:
> I am not sure if this should be bug or a wishlist. BUT aircraft-manager crashes miserably when I add the package to a Jaunty Ubuntu-Netbook-Remix. I wanted that aircraft manager installed to turn off and on my bluetooth support mostly.
>
> I did dig into the code of aircraft manager and discovered two incompatibilities with the UNR live image for Jaunty. First the kernel is missing a module called hci_usb which may explain why bluetooth notification icon does not appear. I know this cause I ran the command that this app ran directly in a terminal.
>
> Second the d-bus messages for network manager appear to have changed which does explain why it crashes in the first place. I know this cause it spews "dbus.exceptions.DBus Exceptions: org.freedesktop.DBus.Error.UnknownMethod: Method "getWirelessEnabled" with signature "" on interface ("null") doesn't exist. This method is called with getWifiState() on line 300 of aircraft-manager.
>
> As I said I am unsure how this should be handled :/ but I think that aircraft-manager should be usuable in Jaunty even if the entire mini9 package set stays with Hardy. It seems only common sense to keep those brave mini9 users happy.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/dell-mini/+bug/357412/+subscribe

Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now.
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141664/direct/01/