nasa

Hi,

I was wondering... How are people using thier DC-DC power supplies to put linux asleep or shutdown? I looked for an acpi event corresponding to something from my opus -- but didn't see a thing. I am sure I am lost and googling doesn't result in much. So any hints would be appreciated.

Nasa

MP3Car.com

 

dupa2

acpid handles everything, once it receives the signal from PS, it shuts down the system, you don't even need any special configuration for it.

__________________
EPIA TC 1G 256MB 60GB Linux,WindowMaker, Roadnav, Xine, XMMS, iGuidance3
Lilliput 8", Pharos i360, WUSB11v2.6 WiFi

nasa

hmmm...,

When I try it, all that happens is linux sits there (all dumb and happy) for about 90 seconds and then the PS kills all power. I don't see it going through the shutdown steps at all... I know I *%@$ something up...

Nasa

dupa2

do you have "power button" actually connected to your PS? , try to install a switch and see if it'll work, your PS not necessarily sends the pulse for shutdown, the switch would easily show where the problem is. Make sure acpi daemon loads and keeps running too.

__________________
EPIA TC 1G 256MB 60GB Linux,WindowMaker, Roadnav, Xine, XMMS, iGuidance3
Lilliput 8", Pharos i360, WUSB11v2.6 WiFi

nasa

Ok,

I did some more testing...

doing "cat /proc/acpi/event" doesn't show anything when I kill the power to ACC line. Nor do I see anything on the acpi line in /proc/interrupts. What could keep the signal from getting to ACPI?

BTW: the computer will shutdown after the allotted time, so the DC-DC power supply is getting the message.

nasa

dupa2:

I just noticed your suggestion of running a switch.... Exactly what are you suggesting? Right now I am testing the system on my bench. I have the a switch on the ACC line so I can simulate what happens in the car. That's how I noticed the problem....

Nasa

nasa

Bump....

nasa

So,

no other linux users are having problems with ACPI? I know I can be cursed, but usually someone else is cursed with me....

Nasa

MP3Car.com

 

dupa2

do you have acpi support in kernel? you need it (with "button" property enabled)

eventually you have to load acpi module with parameters to get it to work, and test it with power switch as you have it connected.

__________________
EPIA TC 1G 256MB 60GB Linux,WindowMaker, Roadnav, Xine, XMMS, iGuidance3
Lilliput 8", Pharos i360, WUSB11v2.6 WiFi

kev000

also make sure that you have the acpid package installed.

__________________
LinuxICE - because my car already has enough windows (and because I like speed).
LinuxICE2 beta2 is released!!! get it now!
Follow OpenICE development

nasa

"dpkg -l | grep acpi" results
ii acpi 0.09-1 displays information on ACPI devices
ii acpi-support 0.90-2 scripts for handling many ACPI events
ii acpid 1.0.4-5 Utilities for using ACPI power management

dmesg | grep acpi
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Time: acpi_pm clocksource has been installed.


From /var/log/messages

messages.0:Feb 17 18:18:34 localhost kernel: ACPI: PCI Interrupt 0000:00:14.0[A] -> GSI 17 (level, low) -> IRQ 169
messages.0:Feb 17 18:18:34 localhost kernel: ACPI: Power Button (FF) [PWRF]
messages.0:Feb 17 18:18:34 localhost kernel: ACPI: Power Button (CM) [PWRB]
messages.0:Feb 17 18:18:34 localhost kernel: ACPI: Sleep Button (CM) [SLPB]
messages.0:Feb 17 18:25:55 localhost kernel: BIOS-e820: 000000003bff0000 - 000000003bff3000 (ACPI NVS)
messages.0:Feb 17 18:25:55 localhost kernel: BIOS-e820: 000000003bff3000 - 000000003c000000 (ACPI data)
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PM-Timer IO Port: 0x408
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
messages.0:Feb 17 18:25:55 localhost kernel: Using ACPI (MADT) for SMP configuration information
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: Core revision 20060707
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: bus type pci registered
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: Interpreter enabled
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: Using IOAPIC for interrupt routing
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 11 12) *5
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 *11 12)
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 *10 11 12)
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12) *0, disabled.
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled.
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled.
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 10 11 12) *0, disabled.
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 10 11 12) *0, disabled.
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [ALKA] (IRQs *20)
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [ALKB] (IRQs *21)
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [ALKC] (IRQs *22), disabled.
messages.0:Feb 17 18:25:55 localhost kernel: ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled.
messages.0:Feb 17 18:25:55 localhost kernel: pnp: PnP ACPI init


Thanks for looking.... And hope this helps figure out what's wrong..


Nasa

dupa2

hmmm, last thing that comes to my mind; did you connect to right header on MB? try to pause boot process (break/pause button) and hit the button, it should turn it off, anyway, how do you turn it on? with same button, I assume.

what's your kernel version? is it dist shipped or custom compiled (I would give it a try if everything else fails)?

__________________
EPIA TC 1G 256MB 60GB Linux,WindowMaker, Roadnav, Xine, XMMS, iGuidance3
Lilliput 8", Pharos i360, WUSB11v2.6 WiFi

nasa

dup2,

Yes I am sure I have it attached to the correct header (it won't boot otherwise).

I have tried multiple kernels (none built by me -- yet). I used distro's from elive (debian based) and the linux distro headed by folks like kev000.

I have failed to note the motherboard this is concerning...

it's this one:

http://store.mp3car.com/VIA_EPIA_EN1..._p/mtb-014.htm

if anyone has used this board and had ACPI work for them, plz let me know. Thanks

Nasa

ElNotto

Just to clarify dupa2's post above (#4) regarding the switch: he's suggesting you hook up a switch/button connected to the header on the motherboard where the power button for a case would connect. This way you could press the power button/switch to test whether ACPI is not recognizing the button press or if the PS isn't sending the button press.

Hope this helps!

nasa

ElNotto:

Using a spare harness (bought from opus) I have a switch placed in-line on the ac wire(also known as the ignition wire). It is placed between the molex connector and the power connector (the one that connects to the DC-DC power supply).

Flipping the said switch off, prevents my system from booting (as expected). When in the on position it boots up after the prescribed 10 seconds. So I am confident that the DC-DC adapter is plugged correctly into the motherboard (it fails to boot when it's not).

Thus, this leaves me where I am today.... My carputer not in my car

I appreciate you looking at my story, hopefully you or other helpful souls will let me know what I am messing up.

Nasa

MP3Car.com