Re: [ACPI] ACPI vs. PCMCIA on Compaq Evo N800c

[Daniele B. <bo...@di...>]

Mike,
I have got a Evo N800v which should not be much different from N800c. I would
say my acpi is fully functional (besides a small problem with CPU performance
status: it works fine, changing its status when on AC or battery, but is not
reported correctly in /proc/acpi).
I don't see your problem. Actually, I've never tried to use PCMCIA since
I don't need it, but here is the output of cardctl and lspci.

Regards,

Daniele

$ cardctl status
Socket 0:
  no card


$ lspci
00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:04.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)
02:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02)
02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42)
02:0e.0 USB Controller: NEC Corporation USB (rev 41)
02:0e.1 USB Controller: NEC Corporation USB (rev 41)
02:0e.2 USB Controller: NEC Corporation USB 2.0 (rev 02)

> I'm trying to get ACPI working on my Compaq Evo N800c.  Actually, I 
> should say that I have it working, or at least it's loading and I'm 
> seeing entries in /proc/acpi, but whenever I boot with a kernel with 
> ACPI enabled, it breaks PCMCIA.  The drivers attempt to load, but can't 
> find the cardbus controller, which doesn't even show up in lspci.  Is 
> this a common problem?  I've tried about 3 different kernel versions 
> with both the stock ACPI and the patches from sourceforge, and they all 
> behave the same way.  Any tips on where I should look to find a fix?
> 
> Thanks
> Mike