[Prism54-users] Bought a SMC2802W - did I get a .V2?

Jouni Kujala jouni.kujala at flexibilis.com
Sat Feb 12 13:56:56 UTC 2005 

I too have a card with part number 99-012084-294 and the problem is the same
as the original writer (Oliver) has. I have tried all the firmware versions,
both 2.4 and 2.6 kernels, many different kernel configurations, many
versions of the prism54 drivers, nothing works. I am not sure if this is V2,
but is certainly a newer version of the SMC card because in this version
there is no big metal cover over the whole card as in older version of the
card. (Picture of the older version:
http://www.bdog.fi/netstore/tuotekuvat/09450.jpg).

--Jouni


-----Original Message-----
From: prism54-users-bounces at prism54.org
[mailto:prism54-users-bounces at prism54.org]On Behalf Of sebastien
Sent: 10. helmikuuta 2005 21:29
To: prism54-users at prism54.org
Subject: Re: [Prism54-users] Bought a SMC2802W - did I get a .V2?


Sorry but, AFAIK, if this is not 99-012084-178 or 99-012084-179,
this is not a V1.
Anyone to confirm ?
Seb.


Oliver Aruväli wrote:

> Hello,
> This is my first post here so, I will try to keep it as detailed as
> possible:
>
> I bough a SMC2802W for my linux router (old pentium 200 running debian
> testing with 2.6.8) so that I could connect my laptop to the network.
>
> After recompileing the kernel with required flags from
> http://prism54.org/phpwiki?pagename=Prism54%20Debian%20HowTo and
> installing the needed packages everything seemed to be in order. The
> first time I booted up, I got the missing firmware error so I placed the
> .arm file into the needed location and renamed it. Inserted the
> configuration to /etc/network/interfaces and rebooted again. Dmesg shows
> the following:
>
> eth2: islpci_open()
> eth2: resetting device...
> eth2: uploading firmware...
> eth2: firmware uploaded done, now triggering reset...
> eth2: device soft reset timed out
> eth2: timeout waiting for mgmt response 1000, triggering device
> eth2: timeout waiting for mgmt response
> eth2: timeout waiting for mgmt response 1000, triggering device
> eth2: timeout waiting for mgmt response
> eth2: timeout waiting for mgmt response 1000, triggering device
> eth2: timeout waiting for mgmt response
> eth2: timeout waiting for mgmt response 1000, triggering device
> eth2: timeout waiting for mgmt response
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgt_commit has failed. Restart the device
> eth2 (WE) : Buffer for request SIOCGIWPRIV too small (16<100)
> eth2 (WE) : Buffer for request SIOCGIWPRIV too small (32<100)
> eth2 (WE) : Buffer for request SIOCGIWPRIV too small (64<100)
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgmt tx queue is still full
> eth2: mgt_commit has failed. Restart the device
> eth2 (WE) : Buffer for request SIOCGIWPRIV too small (16<100)
> eth2 (WE) : Buffer for request SIOCGIWPRIV too small (32<100)
> eth2 (WE) : Buffer for request SIOCGIWPRIV too small (64<100)
>
> my ifconfig output is:
>
> serenity:/home/chaser# ifconfig eth2
> eth2      Link encap:Ethernet  HWaddr 00:30:B4:00:00:00          inet
> addr:10.10.11.1  Bcast:10.255.255.255  Mask:255.255.255.0
>          inet6 addr: fe80::230:b4ff:fe00:0/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:0 (0.0 b)  TX bytes:378 (378.0 b)
>          Interrupt:10
>
> serenity:/home/chaser#
>
> note the eth2 MAC/Hardware address ... it should be 00:04:E2:D5:B3:BC
>
> and iwconfig shows the following:
>
> serenity:/home/chaser# iwconfig
> lo        no wireless extensions.
>
> eth0      no wireless extensions.
>
> eth1      no wireless extensions.
>
> eth2      no wireless extensions.
>
> sit0      no wireless extensions.
>
> serenity:/home/chaser#
>
> and here is the info from the card:
>
> Part no. 99-012084-294
> SUB-ASSY NO 91-012084-294
> MADE IN CHINA
>
> output of lspci -vv:
>
> 0000:00:0b.0 Network controller: Intersil Corporation Intersil ISL3890
> [Prism GT/Prism Duette] (rev 01)
>        Subsystem: Accton Technology Corporation: Unknown device ee03
>        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: 80 (2500ns min, 7000ns max), Cache Line Size: 0x08 (32
> bytes)
>        Interrupt: pin A routed to IRQ 10
>        Region 0: Memory at e6000000 (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-
>
> As I see, v2 is nowhere mentioned.
> I just need to now if I might be missing something else here or did I
> truly get a V2 card. I was thinking of going to have a little chat with
> the sales person who sold it to me as I was assured that this card is V1
> not V2.
>
> lsmod shows that all relevant modules are indeed loaded:
> .....
> prism54                47488  0
> firmware_class      7296    1 prism54
> pci_hotplug           26556  0
> ......
>
> Thank You all in advance,
> Oliver
>
> _______________________________________________
> Prism54-users mailing list
> Prism54-users at prism54.org
> http://prism54.org/mailman/listinfo/prism54-users
>
>

_______________________________________________
Prism54-users mailing list
Prism54-users at prism54.org
http://prism54.org/mailman/listinfo/prism54-users

More information about the Prism54-users mailing list