[Prism54-users] isl3890 driver not detecting pci card
Luis R. Rodriguez
mcgrof@ruslug.rutgers.edu
Tue, 13 Jan 2004 00:49:57 -0500 (EST)
Can you tell us why you are using islpci instead of prism54?
http://prism54.org/pub/linux/snapshot/tars/prism54-cvs-latest.tar.bz2
It seems you have an ixp platform. We can help prism54 working on it.
Luis
On Tue, 13 Jan 2004, Tan Choon Siang wrote:
> Hello,
> By execute the command lsmod, message shown:
>
> Module Size Used by Tainted: P
> islpci 22628 1
> ixp425_eth 10344 1
> csr 922476 0 [ixp425_eth]
>
> Therefore I'm quite sure that the module has been loaded.
>
> By execute command, lspci:
>
> # lspci -vvx
> 00:00.0 Co-processor: Intel Corp.: Unknown device 8500
> 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: 0
> Interrupt: pin A routed to IRQ 0
> Region 0: Memory at <unassigned> (32-bit, prefetchable)
> [size=16M]
> Region 1: Memory at 01000000 (32-bit, prefetchable) [size=16M]
> Region 2: Memory at 02000000 (32-bit, prefetchable) [size=16M]
> Region 3: Memory at 03000000 (32-bit, prefetchable) [size=16M]
> Region 4: Memory at ff000000 (32-bit, prefetchable) [size=16M]
> Region 5: I/O ports at ffffff00 [disabled] [size=256]
> 00: 86 80 00 85 46 03 a0 22 00 00 40 0b 00 00 00 00
> 10: 08 00 00 00 08 00 00 01 08 00 00 02 08 00 00 03
> 20: 08 00 00 ff 01 ff ff ff 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00
>
> 00:0e.0 Network controller: Harris Semiconductor: Unknown device 3890
> (rev 01)
> Subsystem: Unknown device 17cf:0014
> 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: 128 (2500ns min, 7000ns max)
> Interrupt: pin A routed to IRQ 0
> Region 0: Memory at 4bffe000 (32-bit, non-prefetchable)
> [size=8K]
> 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-
> 00: 60 12 90 38 46 03 90 02 01 00 80 02 00 80 00 00
> 10: 00 e0 ff 4b 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 01 08 00 00 cf 17 14 00
> 30: 00 00 00 00 dc 00 00 00 00 00 00 00 00 01 0a 1c
>
>
> Is the driver not appropriate for the device?
> By execute command iwconfig and ifconfig:
>
> # iwconfig
> lo no wireless extensions.
>
> ixp0 no wireless extensions.
>
> ixp1 no wireless extensions.
>
> eth0 no wireless extensions.
>
> # ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 iB) TX bytes:0 (0.0 iB)
> Base address:0xe000 Memory:c3970000-c3972000
>
> As shown in HWaddr 00:00:00:00:00:00, no wlan card is detected.
> What could be wrong?
>
>
>
>
>
> Regards
> Tan Choon Siang
>
>
>
>
> -----Original Message-----
> From: prism54-users-admin@prism54.org
> [mailto:prism54-users-admin@prism54.org] On Behalf Of kaleda
> Sent: Monday, January 12, 2004 9:38 PM
> To: prism54-users@prism54.org
> Subject: Re: [Prism54-users] isl3890 driver not detecting pci card
>
> > Is anybody know whether the prism isl3890 driver, version
> ISL3890-0.1.0
> > statically bind the pci/mini-pci as eth1?
> No.
> It lets linux kernel to assign interface name.
> Almost always it's ethX interface (X - any number).
> E.g. if you already have eth0 - prism54 will register its device, as
> eth1
>
> if you have eth0, eth1 & eth2 already - prism54 will registre eth3
> device, and so on.
>
> > I've built and load the
> > package successfully, but seem like the driver not able to detect the
> > card.
> Why do you think thar you loaded package successfully ?
> Are you able to see its interfase with iwconfig ?
> If yes, than you should bee able to see it with ifconfig -a
> and configure it as normal network device (with some additional wireless
> extention functions using iwconfig).
> If no - try to find why it's not working:
> dmesg
> lsmod
> less /var/log/syslog
> lspci
> these are your friends.
> I think in dmesg output you'll find why module wasn't loaded.
>
> > My system only detect eth0, MAC address of the card is not
> > detected even I've loaded the driver.
> is eth0 your ordinary ethernet device ?
> or you have wireless device is the only network device in your system ?
>
>
> Kaleda
> _______________________________________________
> Prism54-users mailing list
> Prism54-users@prism54.org
> http://prism54.org/mailman/listinfo/prism54-users
>
>
> _______________________________________________
> Prism54-users mailing list
> Prism54-users@prism54.org
> http://prism54.org/mailman/listinfo/prism54-users
>