32bit Cardbus not working with Ricoh 475 PCI

[Alistair John Strachan]

On Sunday 02 May 2004 19:07, Alistair John Strachan wrote:
>
> I checked the kernel bugzilla and found the following:
> http://bugzilla.kernel.org/show_bug.cgi?id=1840
>
> It seems to approximately describe my problem. I tried the attached patch
> and got (what seems to be) a little further. However, now dmesg reports the
> following:
>
> PCI: cardbus bridge: 0000:01:07.0
> PCI: Failed to allocate resource 7(2000000) for 0000:01:07.0
> PCI: Failed to allocate resource 8(2000000) for 0000:01:07.0
> PCI: Failed to allocate resource 10(1000) for 0000:01:07.0
>
> Before getting to init. prism.ko now loads, however;
>
> Loaded prism54 driver, version 1.1
> eth1: prism54 driver detected card model: 3COM 3CRWE154G72
>
> The card doesn't work, however, as hotplug won't upload the firmware and
> ifconfig eth1 up doesn't do anything. The card still appears dead to the
> world.
>
> Since the cardbus bridge shares an IRQ with my video card, when I start X I
> get:
>
> Assuming someone else called the IRQ
> Assuming someone else called the IRQ
>
> Thousands of times. The message doesn't stop until I unplug the card.

Aand, the dmesg from a fresh boot:

cs: IO port probe 0x9000-0xbfff: clean.
Loaded prism54 driver, version 1.1
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
eth1: prism54 driver detected card model: 3COM 3CRWE154G72
eth1: islpci_open()
eth1: resetting device...
eth1: uploading firmware...
eth1: firmware uploaded done, now triggering reset...
eth1: device soft reset timed out
eth1: timeout waiting for mgmt response 1000, trigging device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 1000, trigging device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 1000, trigging device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 1000, trigging device
eth1: timeout waiting for mgmt response
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
eth1: mgt_commit has failed. Restart the device
eth1: mgmt tx queue is still full
eth1: islpci_close ()
Assuming someone else called the IRQ
Assuming someone else called the IRQ
Assuming someone else called the IRQ
Assuming someone else called the IRQ
eth1: hot unplug detected
eth1: removing device

I don't think the firmware upload does succeed, this all takes place in a far 
shorter time than I'm used to.

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/AI Undergraduate
contact:    7/10 Darroch Court,
            University of Edinburgh.