Gericom Supersonic ACPI hang (smi_cmd)

Hello there again!

I posted some days ago, that I have problems getting ACPI up and running
on my Gericom Laptop. The Kernel just hangs without any error message.
Arndt Schoenewald suggested some Kernel Configurations to me (thanks again!) , but none of them did work. It seems like I have a very rare Version of this laptop model, with a (very) broken BIOS.
So I tried to debug that myself. I'm not a very good C Programmer and have no clue about the ACPI specifications, so I cannot solve this problem myself.
I was able to trace down the hang where acpi_enable gets called and itself calls acpi_hw_set_mode. This goes into the function acpi_os_write_port(acpi_gbl_FADT->smi_cmd, (acpi_integer) acpi_gbl_FADT->acpi_enable, 8), where outb gets called with port acpi_gbl_FADT->smi_cmd and value acpi_gbl_FADT->acpi_enable. I think there is something wrong with the address smi_cmd. I could not find the part in the code where it gets set.
Tell me if I can provide more information about this problem or something.

Ulrich Dobramysl

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Success!
Thanks a lot! Now it works.
I had to tweak some things in the source file arch/i386/kernel/mpparse.c because FIX_APIC_BASE, Dprintk, and apic_read aren't defined when APIC is disabled, but needed by ACPI? I got a lot of compiler errors when trying to build the kernel. I just commented some things out, and made some real bad hacks, but it compiles and works now. I don't think that this is the normal way of doing this? ;-)

S1 just works fine, MUCH better than with APM.
Now I have problems putting the laptop in S4 (swsusp) state. It seems like swsusp goes into an endless loop, with many warnings that he is scheduling in atomic state or something.

Sometimes, when trying to read some state files in /proc/acpi (the battery state and some other things too), the reading process (cat in my case) hangs and I have to kill it with STRG-C.

The Lid fires no event when closed or opened.

I'm using kernel 2.5.40 and acpi patch 20021002, sorry I forgot to write that in my last mail.

Ulrich Dobramysl

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven.
http://thinkgeek.com/sf