Linux 2.6.x / EnE CB1410 cardbus - No Interrupts

Jeff Noxon jeff at
Sun Mar 21 12:54:37 GMT 2004

Thanks guys,

I have a lot of egg on my face right now...  I had two 2.6.4 kernels
installed, and I was booting the unpatched one.  I need to get some
more sleep!

With the two patches applied, I get this:

Linux Kernel Card Services
  options:  [pci] [cardbus] [pm]
PCI: Enabling device 0000:00:08.0 (0000 -> 0002)
Yenta: CardBus bridge found at 0000:00:08.0 [0000:0000]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:08.0, mfunc 0x00000000, devctl 0x46
Yenta TI: socket 0000:00:08.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:08.0 falling back to parallel PCI interrupts
Yenta TI: socket 0000:00:08.0 parallel PCI interrupts ok
Yenta: ISA IRQ mask 0x0000, PCI irq 20
Socket status: 30000020
Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Enabling device 0000:04:00.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:04:00.0 to 64
tulip0:  EEPROM default media type Autosense.
tulip0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
tulip0:  MII transceiver #0 config 3000 status 7809 advertising 01e1.
eth2: Digital DS21143 Tulip rev 65 at 0x4000, 00:E0:98:06:B1:A2, IRQ 20.

           CPU0       CPU1       
 20:       1173       2598   IO-APIC-level  yenta, eth2

The card is on its own IRQ, and it is working just fine!

I'll do a few more tests to see whether it was the TI_1250 patch or
the TI irq patches that actually made the difference.  Before I asked
on the list, I was calling it a TI_12XX, not a 1250.

I am very encouraged.  It still remains to be seen whether the card
does anything in my target machine, where previously it didn't even
recognize card insertions.



On Sat, Mar 20, 2004 at 01:45:02PM -0500, Pavel Roskin wrote:
> On Sat, 20 Mar 2004, Jeff Noxon wrote:
> > Russell & Pavel,
> >
> > I have tried these two patches with no success.  The system behaves
> > exactly the same as I described before.
> The patch for fixing the PCI interrupts prints to the kernel log what it's
> doing to fix them.  The dmesg command shows the kernel log.  Lines
> beginning with "Yenta" are most interesting.

More information about the linux-pcmcia mailing list