[Prism54-users] Re: init_module: No such device

[Wolfgang Miller-Reichling]

On Sat, Nov 15, 2003 at 09:05:16AM +0100, Herbert Valerio Riedel wrote:
> On Sat, 2003-11-15 at 08:36, Wolfgang Miller-Reichling wrote:
> > Wolfgang Miller-Reichling <wolle-tmp20030401@gmx.de> wrote:
> >  
> > > I'm trying to use today's cvs version with a Netgear WG511 on a Thinkpad
> > > 760E. Building the driver (gcc 3.3.2) works fine but insmod fails with
> > > the following message: 
> > > 
> > > root@thinkpad:~ # modprobe prism54
> > > /lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism54.o:
> > > init_module: No such device Hint: insmod errors can be caused by
> > >     incorrect module parameters, including invalid IO or IRQ parameters.
> > > You may find more information in syslog or the output from dmesg
> > > /lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism54.o:
> > > insmod
> > > /lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism54.o
> > > failed
> > > /lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism54.o:
> > > insmod prism54 failed
> > > 
> > > root@thinkpad:~ # dmesg | tail -4
> > > Loaded prism54 driver, version 1.0.2.2
> > > PCI: No IRQ known for interrupt pin A of device .
> > > eth1: could not install IRQ handler
> > > prism54: No devices found, driver not installed.
> > > 
> > > Any hints?
> > 
> > Hmm, no hints? Maybe I can give a few more: 
> > The card works (very unstable though) with the old ISL3890-0.1.0
> > release. It takes IRQ 5. So this is not (only?) a PCMCIA-PCI assignment
> > problem. 
> 
> what does lspci -vv show for the device in question?

To get any output at all I have to use lspci -H1, this is the output
with the ISL3890-0.1.0 release:
01:00.0 Network controller: Harris Semiconductor: Unknown device 3890 (rev 01)
        Subsystem: Netgear: Unknown device 4800
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
                 ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
                >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (2500ns min, 7000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 9
        Region 0: Memory at a0004000 (32-bit, non-prefetchable)
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
                       PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

This is the output with the newest kernel patch:
01:00.0 Network controller: Harris Semiconductor: Unknown device 3890 (rev 01)
        Subsystem: Netgear: Unknown device 4800
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
                 ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
                >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 0
        Region 0: Memory at 60000000 (32-bit, non-prefetchable)
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
                       PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

I have to admit IRQ0 looks suspicious.
BTW, if I use kernel PCMCIA instead of pcmcia-cs lspci doesn't need the
"-H1" switch.

Wolfgang