7.04 CardBus bridge ToPIC97 (rev 20) won't recognice cardbus cards

Please attach, via the web interface (do not paste into comments) the output of the following commands, one attachment for each output:

dmesg
lspci -vv
lspci -vvn

Do this with the PC card inserted.

OK, for this test I have done a fresh installation of Kubuntu 7.04 herd 5.

I ejected and inserted various kinds of cards for the dmesg.

[ 1014.644648] cs: pcmcia_socket1: cardbus cards are not supported.

This is saying that the socket you are inserting this card into does not support CardBus (physically). From reading the driver code, there's not much that can be done there.

Have you been able to use CardBus cards in these sockets in other operating systems (Some other Linux, or Windows)?

Well I've been able to use that card in the same computer, same slot with Ubuntu 6.06 I think. Strangely enought it also doesn't seem to work with Puppy Linux.

Hmm, but look at the following lines of dmesg:

[ 19.537481] PCI: No IRQ known for interrupt pin A of device 0000:00:13.0. Please try using pci=biosirq.
[ 400.303308] Yenta: no PCI IRQ, CardBus support disabled for this socket.

When I use pci=biosirq the "19.5 seconds" line still appears, but without saying "please try using pci=biosirq."

Please try some of these config options, especially the pci=noacpi

        pci=option[,option...] [PCI] various PCI subsystem options:
                bios [IA-32] force use of PCI BIOS, don't access
                                the hardware directly. Use this if your machine
                                has a non-standard PCI host bridge.
                nobios [IA-32] disallow use of PCI BIOS, only direct
                                hardware access methods are allowed. Use this
                                if you experience crashes upon bootup and you
                                suspect they are caused by the BIOS.
                conf1 [IA-32] Force use of PCI Configuration
                                Mechanism 1.
                conf2 [IA-32] Force use of PCI Configuration
                                Mechanism 2.
                mmconf [IA-32,X86_64] Enable use of MMCONFIG for PCI
                                Configuration
                nommconf [IA-32,X86_64] Disable use of MMCONFIG for PCI
                                Configuration
                nomsi [MSI] If the PCI_MSI kernel config parameter is
                                enabled, this kernel boot option can be used to
                                disable the use of MSI interrupts system-wide.
                biosirq [IA-32] Use PCI BIOS calls to get the interrupt
                                routing table. These calls are known to be buggy
                                on several machines and they hang the machine
                                when used, but on other computers it's the only
                                way to get the interrupt routing table. Try
                                this option if the kernel is unable to allocate
                                IRQs or discover secondary PCI buses on your
                                motherboard.
                assign-busses [IA-32] Always assign all PCI bus
                                numbers ourselves, overriding
                                whatever the firmware may have done.
                noacpi [IA-32] Do not use ACPI for IRQ routing
                                or for PCI scanning.
                routeirq Do IRQ routing for all PCI devices.
                                This is normally done in pci_enable_device(),
                                so this option is a temporary workaround
                                for broken drivers that don't call it.

It works with pci=mmconf
It does not work with:
pci=bios
pci=nobios
pci=conf1
pci=conf2 (lspci just produces no output)
pci=noacpi

If I shall try more options, just tell me. I'm sorry it took so long.

Sorry, I have tried with a PCMCIA card. so
pci=mmconf does _NOT_ work. Sorry.

It does not seem to work at all with Kubuntu 7.04.
I now installed Xubuntu 6.06 and it works. Shall I send you the output of dmesg and lspci?

I experience exactly the same issue with a ToPI97 (rev 02) on a Tecra 750CDT that was working perfectly with hoary. I have try many kernel opts without much success. I am downloading Dapper...

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!