Re: ACPI (was: 2.6.5 Upgrade Notes)

[Bill Moseley <moseley@hank.org>]

On Tue, Apr 20, 2004 at 06:53:59PM -0400, Roberto Sanchez wrote:
> Bill Moseley wrote:
>  > One other show stopper was ACPI caused the startup of PCMCIA 
> (loading of the yenta
> >CardBus driver) to hang the machine.  So I disabled ACPI and use APM
> >instead.
> 
> Having CONFIG_PCMCIA=y and CONFIG_YENTA=y solved this particular
> problem for me, as I liked ACPI too much to give it up.


Well, seems like ACPI is still a show stopper.  I rebuilt the kernel
without APM and with ACPI.  Building PCMCIA and YENTA static did solve
the problem of it hanging when starting pcmcia, but still have other
problems.

At boot I see:

    PCI: Enabling device 0000:00:0b.0 (0000 -> 0002)
    ACPI: No IRQ known for interrupt pin A of device 0000:00:0b.0 - using IRQ 255
    Yenta: CardBus bridge found at 0000:00:0b.0 [1179:0001]
    Yenta: ISA IRQ mask 0x0cb8, PCI irq 0

I'm just guessing, but it looks like CardBus isn't going to be able to
generate interrupts.

Then when my pcmcia card tries to install I get:

Apr 20 22:45:43 localhost cardmgr[345]: socket 1: Intersil PRISM2 11 Mbps Wireless Adapter
Apr 20 22:45:43 localhost cardmgr[345]: executing: 'modprobe orinoco_cs'
Apr 20 22:45:43 localhost kernel: orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
Apr 20 22:45:43 localhost kernel: orinoco_cs.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
Apr 20 22:45:43 localhost kernel: orinoco_cs: RequestIRQ: Resource in use
Apr 20 22:45:44 localhost cardmgr[345]: get dev info on socket 1 failed: Resource temporarily unavailable

And then removing the PCMCIA card the system hangs hard.

And I was looking forward to all the access ACPI was going to give me to
the laptop.  Any other ideas?


moseley@laptop:~$ egrep '(PCMCIA|YENTA)' /boot/config-2.6.5-xfs-toshiba 
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
# PCMCIA/CardBus support
CONFIG_PCMCIA=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_YENTA=y
# CONFIG_PARPORT_PC_PCMCIA is not set
# CONFIG_PCMCIA_WAVELAN is not set
# CONFIG_PCMCIA_NETWAVE is not set
# CONFIG_PCMCIA_RAYCS is not set
CONFIG_PCMCIA_HERMES=m
# CONFIG_PCMCIA_WL3501 is not set
# PCMCIA network device support
# CONFIG_NET_PCMCIA is not set
# PCMCIA character devices
# PCMCIA devices



-- 
Bill Moseley
moseley@hank.org