PCMCIA ne2000 compatible Ethernet card driver

[Javier Steinaker]

Hi,

First of all, sorry for my english. I'm from
Argentina, and a newbie in NetBSD (Linux user).
I'm having a problem with the EXP ThinLAN 100 card I
own: NetBSD doesn't recognize it. Under Linux, it
works perfect.
You can see the card here:
http://www.expnet.com/product.nsf/price+for+calculation/ThinLan-100
As you can see, the card is an NE-2000 compatible. In
fact, under Linux works with the ne2000 driver. But
NetBSD doesn't load the driver. dmesg shows the kernel
knows there's an Ethernet card in pcmcia0, but
apparently doesn't know which card it is. The line is
the next:
pcmcia0 function 0: <PCMCIA LAN, Ethernet, A,
004743118001> (manufacturer 0xffffffff, product
0xffffffff)
 not configured

As I understand, there are two possibilites:
* The kernel knows what card it is, but doesn't know
which driver load. In that case, I've heard that would
be relatively easy to tell the kernel "the truth",
modifying a table in the source code. I've looked the
source, but I cannot understand it very well.
* The kernel doesn't recognize the card at all. In
that case, I don't know what I should do (but I hope
you know).

Can you tell me about what case we 're talking? And
provide me a solution?

Many thanks,
Javier


      Yahoo! Encuentros.

Ahora encontrar pareja es mucho más fácil, probá el nuevo Yahoo! Encuentros http://yahoo.cupidovirtual.com/servlet/NewRegistration

[Ari Constancio-3]

Hi Javier,

Probably the card's entry is commented in
/usr/src/sys/arch/<ARCH>/conf/GENERIC (I haven't checked, though).

See http://netbsd.org/docs/kernel/index.html#how_to_build_a_kernel and
http://netbsd.org/docs/kernel/index.html#new_pcmcia_device .

Cheers,
Ari Constancio

On Fri, Mar 7, 2008 at 2:34 PM, Javier Steinaker
<jsteinaker@...> wrote:

> Hi,
>
>  First of all, sorry for my english. I'm from
>  Argentina, and a newbie in NetBSD (Linux user).
>  I'm having a problem with the EXP ThinLAN 100 card I
>  own: NetBSD doesn't recognize it. Under Linux, it
>  works perfect.
>  You can see the card here:
>  http://www.expnet.com/product.nsf/price+for+calculation/ThinLan-100
>  As you can see, the card is an NE-2000 compatible. In
>  fact, under Linux works with the ne2000 driver. But
>  NetBSD doesn't load the driver. dmesg shows the kernel
>  knows there's an Ethernet card in pcmcia0, but
>  apparently doesn't know which card it is. The line is
>  the next:
>  pcmcia0 function 0: <PCMCIA LAN, Ethernet, A,
>  004743118001> (manufacturer 0xffffffff, product
>  0xffffffff)
>   not configured
>
>  As I understand, there are two possibilites:
>  * The kernel knows what card it is, but doesn't know
>  which driver load. In that case, I've heard that would
>  be relatively easy to tell the kernel "the truth",
>  modifying a table in the source code. I've looked the
>  source, but I cannot understand it very well.
>  * The kernel doesn't recognize the card at all. In
>  that case, I don't know what I should do (but I hope
>  you know).
>
>  Can you tell me about what case we 're talking? And
>  provide me a solution?
>
>  Many thanks,
>  Javier
>
>
>       Yahoo! Encuentros.
>
>  Ahora encontrar pareja es mucho más fácil, probá el nuevo Yahoo! Encuentros http://yahoo.cupidovirtual.com/servlet/NewRegistration
>

[Manuel Bouyer]

On Fri, Mar 07, 2008 at 11:34:59AM -0300, Javier Steinaker wrote:

> Hi,
>
> First of all, sorry for my english. I'm from
> Argentina, and a newbie in NetBSD (Linux user).
> I'm having a problem with the EXP ThinLAN 100 card I
> own: NetBSD doesn't recognize it. Under Linux, it
> works perfect.
> You can see the card here:
> http://www.expnet.com/product.nsf/price+for+calculation/ThinLan-100
> As you can see, the card is an NE-2000 compatible. In
> fact, under Linux works with the ne2000 driver. But
> NetBSD doesn't load the driver. dmesg shows the kernel
> knows there's an Ethernet card in pcmcia0, but
> apparently doesn't know which card it is. The line is
> the next:
> pcmcia0 function 0: <PCMCIA LAN, Ethernet, A,
> 004743118001> (manufacturer 0xffffffff, product
> 0xffffffff)
>  not configured
>
> As I understand, there are two possibilites:
> * The kernel knows what card it is, but doesn't know
> which driver load. In that case, I've heard that would
> be relatively easy to tell the kernel "the truth",
> modifying a table in the source code. I've looked the
> source, but I cannot understand it very well.
> * The kernel doesn't recognize the card at all. In
> that case, I don't know what I should do (but I hope
> you know).
>
> Can you tell me about what case we 're talking? And
> provide me a solution?

The first, most probably. Adding it to the table should be easy.
Can you send me the linux dmesg when it probes this card ?

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--

[Manuel Bouyer]

On Fri, Mar 07, 2008 at 09:19:17PM +0100, Manuel Bouyer wrote:
> The first, most probably. Adding it to the table should be easy.
> Can you send me the linux dmesg when it probes this card ?

I'll also need the first 3 bytes of the ethernet address (the vendor
part of the address).

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--

[Javier Steinaker]

Hi again,

Under Puppy Linux, I ejected the card and inserted it
again. The results in dmesg:

-------------------------------------------------
pccard: card ejected from slot 0
pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr
00:C0:0C:03:78:F1
-------------------------------------------------

As you can see, the hardware address is in the last
line.
One more thing: the driver, in Linux, is called
pcnet-cs.

Greetings,
Javier


      Yahoo! Encuentros.

Ahora encontrar pareja es mucho más fácil, probá el nuevo Yahoo! Encuentros http://yahoo.cupidovirtual.com/servlet/NewRegistration

[Manuel Bouyer]

On Sun, Mar 09, 2008 at 09:09:19PM -0300, Javier Steinaker wrote:

> Hi again,
>
> Under Puppy Linux, I ejected the card and inserted it
> again. The results in dmesg:
>
> -------------------------------------------------
> pccard: card ejected from slot 0
> pccard: PCMCIA card inserted into slot 0
> pcmcia: registering new device pcmcia0.0
> eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr
> 00:C0:0C:03:78:F1
> -------------------------------------------------
>
> As you can see, the hardware address is in the last
> line.
> One more thing: the driver, in Linux, is called
> pcnet-cs.

OK, could you try the attached patch ?

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--

Index: if_ne_pcmcia.c
===================================================================
RCS file: /cvsroot/src/sys/dev/pcmcia/if_ne_pcmcia.c,v
retrieving revision 1.150
diff -u -p -u -r1.150 if_ne_pcmcia.c
--- if_ne_pcmcia.c 19 Oct 2007 12:01:04 -0000 1.150
+++ if_ne_pcmcia.c 11 Mar 2008 21:22:18 -0000
@@ -111,6 +111,10 @@ static const struct ne2000dev {
       0, -1, { 0x00, 0x90, 0xcc }, NE2000DVF_AX88190 },
 
     { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
+      PCMCIA_CIS_EXP_THINLAN100,
+      0, -1, { 0x00, 0xc0, 0x0c }, 0 },
+
+    { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
       PCMCIA_CIS_SYNERGY21_S21810,
       0, -1, { 0x00, 0x48, 0x54 }, 0 },
 
Index: pcmciadevs
===================================================================
RCS file: /cvsroot/src/sys/dev/pcmcia/pcmciadevs,v
retrieving revision 1.223
diff -u -p -u -r1.223 pcmciadevs
--- pcmciadevs 22 Sep 2007 19:59:55 -0000 1.223
+++ pcmciadevs 11 Mar 2008 21:22:18 -0000
@@ -499,6 +499,7 @@ product DYNALINK L10C { "DYNALINK", "L1
 product EIGERLABS EPX_AA2000 { "Eiger&splabs,Inc.", "EPX-AA2000&spPC&spSound&spCard", NULL, NULL } EPX-AA2000 PC Sound Card
 product EPSON EEN10B { "Seiko&spEpson&spCorp.", "Ethernet", "P/N:&spEEN10B&spRev.&sp00", NULL } Epson EEN10B
 product EXP EXPMULTIMEDIA { "EXP&sp&sp&sp", "PnPIDE", "F1", NULL } EXP IDE/ATAPI DVD Card
+product EXP THINLAN100 { "PCMCIA&spLAN", "Ethernet", "A", NULL } EXP Thinlan-100 ethernet adapter
 product FUJITSU FMV_J181 { "PCMCIA&spMBH10302", "01", NULL, NULL } FUJITSU FMV-J181 PCMCIA Card
 product FUJITSU FMV_J182 { "FUJITSU", "LAN&spCard(FMV-J182)", "Ver.01", NULL } FUJITSU FMV-J182 PCMCIA Card
 product FUJITSU FMV_J182A { "FUJITSU", "LAN&spCard(FMV-J182)", "Ver.02", NULL } FUJITSU FMV-J182A PCMCIA Card
Index: pcmciadevs.h
===================================================================
RCS file: /cvsroot/src/sys/dev/pcmcia/pcmciadevs.h,v
retrieving revision 1.226
diff -u -p -u -r1.226 pcmciadevs.h
--- pcmciadevs.h 22 Sep 2007 20:01:21 -0000 1.226
+++ pcmciadevs.h 11 Mar 2008 21:22:18 -0000
@@ -1,4 +1,4 @@
-/* $NetBSD: pcmciadevs.h,v 1.226 2007/09/22 20:01:21 kiyohara Exp $ */
+/* $NetBSD$ */
 
 /*
  * THIS FILE AUTOMATICALLY GENERATED.  DO NOT EDIT.
@@ -708,6 +708,8 @@
 #define PCMCIA_PRODUCT_EPSON_EEN10B -1
 #define PCMCIA_CIS_EXP_EXPMULTIMEDIA { "EXP   ", "PnPIDE", "F1", NULL }
 #define PCMCIA_PRODUCT_EXP_EXPMULTIMEDIA -1
+#define PCMCIA_CIS_EXP_THINLAN100 { "PCMCIA LAN", "Ethernet", "A", NULL }
+#define PCMCIA_PRODUCT_EXP_THINLAN100 -1
 #define PCMCIA_CIS_FUJITSU_FMV_J181 { "PCMCIA MBH10302", "01", NULL, NULL }
 #define PCMCIA_PRODUCT_FUJITSU_FMV_J181 -1
 #define PCMCIA_CIS_FUJITSU_FMV_J182 { "FUJITSU", "LAN Card(FMV-J182)", "Ver.01", NULL }
Index: pcmciadevs_data.h
===================================================================
RCS file: /cvsroot/src/sys/dev/pcmcia/pcmciadevs_data.h,v
retrieving revision 1.226
diff -u -p -u -r1.226 pcmciadevs_data.h
--- pcmciadevs_data.h 22 Sep 2007 20:01:21 -0000 1.226
+++ pcmciadevs_data.h 11 Mar 2008 21:22:18 -0000
@@ -1,4 +1,4 @@
-/* $NetBSD: pcmciadevs_data.h,v 1.226 2007/09/22 20:01:21 kiyohara Exp $ */
+/* $NetBSD$ */
 
 /*
  * THIS FILE AUTOMATICALLY GENERATED.  DO NOT EDIT.
@@ -1478,6 +1478,13 @@ struct pcmcia_knowndev pcmcia_knowndevs[
     "EXP IDE/ATAPI DVD Card", }
  ,
  {
+    PCMCIA_VENDOR_UNKNOWN, PCMCIA_PRODUCT_EXP_THINLAN100,
+    PCMCIA_CIS_EXP_THINLAN100,
+    0,
+    "EXP Computer Inc",
+    "EXP Thinlan-100 ethernet adapter", }
+ ,
+ {
     PCMCIA_VENDOR_UNKNOWN, PCMCIA_PRODUCT_FUJITSU_FMV_J181,
     PCMCIA_CIS_FUJITSU_FMV_J181,
     0,

[Javier Steinaker]

--- Manuel Bouyer <bouyer@...> escribió:
> OK, could you try the attached patch ?

Tried. The good news? The kernel now recognizes the
card! In fact, the lines in dmesg are:
----------------------------------------------------
ne0 at pcmcia0 function 0: <PCMCIA LAN, Ethernet, A,
004743118001>
ne0: where did the card go?
----------------------------------------------------
The bad news? The second line. As the ne(4) man page
says about the line: "The driver found the card, but
was unable to make the card respond to complete the
configuration sequence."
So, the card isn't working at the time. Any ideas?

Greetings,
Javier

PS: thank you for your GREAT job. Really.


      Yahoo! Encuentros.

Ahora encontrar pareja es mucho más fácil, probá el nuevo Yahoo! Encuentros http://yahoo.cupidovirtual.com/servlet/NewRegistration

[Christos Zoulas-2]

In article <20080311212248.GA8753@...>,
Manuel Bouyer  <bouyer@...> wrote:

>-=-=-=-=-=-
>
>On Sun, Mar 09, 2008 at 09:09:19PM -0300, Javier Steinaker wrote:
>> Hi again,
>>
>> Under Puppy Linux, I ejected the card and inserted it
>> again. The results in dmesg:
>>
>> -------------------------------------------------
>> pccard: card ejected from slot 0
>> pccard: PCMCIA card inserted into slot 0
>> pcmcia: registering new device pcmcia0.0
>> eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr
>> 00:C0:0C:03:78:F1
>> -------------------------------------------------
>>
>
>     { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
>+      PCMCIA_CIS_EXP_THINLAN100,
>+      0, -1, { 0x00, 0xc0, 0x0c }, 0 },

I think the above line should be:

        0, 0x0ff0, { 0x00, 0xa0, 0x0c }, 0 },
>+
>+    { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
>       PCMCIA_CIS_SYNERGY21_S21810,
>       0, -1, { 0x00, 0x48, 0x54 }, 0 },
>

christos

[Manuel Bouyer]

On Wed, Mar 12, 2008 at 06:44:58PM +0000, Christos Zoulas wrote:

> In article <20080311212248.GA8753@...>,
> Manuel Bouyer  <bouyer@...> wrote:
> >-=-=-=-=-=-
> >
> >On Sun, Mar 09, 2008 at 09:09:19PM -0300, Javier Steinaker wrote:
> >> Hi again,
> >>
> >> Under Puppy Linux, I ejected the card and inserted it
> >> again. The results in dmesg:
> >>
> >> -------------------------------------------------
> >> pccard: card ejected from slot 0
> >> pccard: PCMCIA card inserted into slot 0
> >> pcmcia: registering new device pcmcia0.0
> >> eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr
> >> 00:C0:0C:03:78:F1
> >> -------------------------------------------------
> >>
> >
> >     { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
> >+      PCMCIA_CIS_EXP_THINLAN100,
> >+      0, -1, { 0x00, 0xc0, 0x0c }, 0 },
>
> I think the above line should be:
>
> 0, 0x0ff0, { 0x00, 0xa0, 0x0c }, 0 },

Linux reports 00:c0:0c as mac address ...
And I guess if this was the issue, he wouldn't get "were did the card go"
error, it would fail before that ...

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--

[Manuel Bouyer]

On Wed, Mar 12, 2008 at 12:41:22PM -0300, Javier Steinaker wrote:

> --- Manuel Bouyer <bouyer@...> escribió:
> > OK, could you try the attached patch ?
>
> Tried. The good news? The kernel now recognizes the
> card! In fact, the lines in dmesg are:
> ----------------------------------------------------
> ne0 at pcmcia0 function 0: <PCMCIA LAN, Ethernet, A,
> 004743118001>
> ne0: where did the card go?
> ----------------------------------------------------
> The bad news? The second line. As the ne(4) man page
> says about the line: "The driver found the card, but
> was unable to make the card respond to complete the
> configuration sequence."
> So, the card isn't working at the time. Any ideas?

We'll need more details about the chip used by this adapter.
Is there any way to get a more verbose message from linux ?

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--

[Christos Zoulas]

On Mar 12, 10:33pm, bouyer@... (Manuel Bouyer) wrote:
-- Subject: Re: PCMCIA ne2000 compatible Ethernet card driver

| On Wed, Mar 12, 2008 at 06:44:58PM +0000, Christos Zoulas wrote:
| > In article <20080311212248.GA8753@...>,
| > Manuel Bouyer  <bouyer@...> wrote:
| > >-=-=-=-=-=-
| > >
| > >On Sun, Mar 09, 2008 at 09:09:19PM -0300, Javier Steinaker wrote:
| > >> Hi again,
| > >>
| > >> Under Puppy Linux, I ejected the card and inserted it
| > >> again. The results in dmesg:
| > >>
| > >> -------------------------------------------------
| > >> pccard: card ejected from slot 0
| > >> pccard: PCMCIA card inserted into slot 0
| > >> pcmcia: registering new device pcmcia0.0
| > >> eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr
| > >> 00:C0:0C:03:78:F1
| > >> -------------------------------------------------
| > >>
| > >
| > >     { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
| > >+      PCMCIA_CIS_EXP_THINLAN100,
| > >+      0, -1, { 0x00, 0xc0, 0x0c }, 0 },
| >
| > I think the above line should be:
| >
| > 0, 0x0ff0, { 0x00, 0xa0, 0x0c }, 0 },
|
| Linux reports 00:c0:0c as mac address ...
| And I guess if this was the issue, he wouldn't get "were did the card go"
| error, it would fail before that ...

I looked in the linux pc_net driver code for NE 2000 compatible...

christos

[Manuel Bouyer]

On Wed, Mar 12, 2008 at 05:48:02PM -0400, Christos Zoulas wrote:

> On Mar 12, 10:33pm, bouyer@... (Manuel Bouyer) wrote:
> -- Subject: Re: PCMCIA ne2000 compatible Ethernet card driver
>
> | On Wed, Mar 12, 2008 at 06:44:58PM +0000, Christos Zoulas wrote:
> | > In article <20080311212248.GA8753@...>,
> | > Manuel Bouyer  <bouyer@...> wrote:
> | > >-=-=-=-=-=-
> | > >
> | > >On Sun, Mar 09, 2008 at 09:09:19PM -0300, Javier Steinaker wrote:
> | > >> Hi again,
> | > >>
> | > >> Under Puppy Linux, I ejected the card and inserted it
> | > >> again. The results in dmesg:
> | > >>
> | > >> -------------------------------------------------
> | > >> pccard: card ejected from slot 0
> | > >> pccard: PCMCIA card inserted into slot 0
> | > >> pcmcia: registering new device pcmcia0.0
> | > >> eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr
> | > >> 00:C0:0C:03:78:F1
> | > >> -------------------------------------------------
> | > >>
> | > >
> | > >     { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
> | > >+      PCMCIA_CIS_EXP_THINLAN100,
> | > >+      0, -1, { 0x00, 0xc0, 0x0c }, 0 },
> | >
> | > I think the above line should be:
> | >
> | > 0, 0x0ff0, { 0x00, 0xa0, 0x0c }, 0 },
> |
> | Linux reports 00:c0:0c as mac address ...
> | And I guess if this was the issue, he wouldn't get "were did the card go"
> | error, it would fail before that ...
>
> I looked in the linux pc_net driver code for NE 2000 compatible...

So did I. 0x00, 0xa0, 0x0c doens't match the ethernet address reported
by Javier.

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--

[Javier Steinaker]

Some news.
I tried the solution provided by Christos. Same
problem ("Where did the card go?"). I verified, in
many sites, that the MAC address start with 00:c0:0c.
That address belongs to Relia Technologies, as
http://www.coffer.com/mac_find/?string=00%3Ac0%3A0c
says. In fact, when Puppy Linux is booting, displays a
message about the Relia 2408T, which seems to be
compatible with my card (or my card is, internally, a
Relia), and this time I'm sure!
OpenBSD knows this card, or that shows the pcmciadevs
file in the CVS tree
(http://www.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/dev/pcmcia/pcmciadevs?rev=1.131&content-type=text/plain).
The messages showed here are identical to the messages
my card shows (PCMCIA LAN, Ethernet, etc).
Linux seems to knows Relia, too.

One more thing. "cardctl ident" shows:
PRODID_1="PCMCIA LAN"
PRODID_2="Ethernet"
PRODID_3="A"
PRODID_4="004743118001"
MANFID=0000,0000
FUNCID=6

Again... any ideas?
Thank you very much for your help, guys.

Greetings,
Javier


      Tarjeta de crédito Yahoo! de Banco Supervielle.
Solicitá tu nueva Tarjeta de crédito. De tu PC directo a tu casa. www.tuprimeratarjeta.com.ar

[Manuel Bouyer]

On Thu, Mar 13, 2008 at 01:25:58PM -0300, Javier Steinaker wrote:

> Some news.
> I tried the solution provided by Christos. Same
> problem ("Where did the card go?"). I verified, in
> many sites, that the MAC address start with 00:c0:0c.
> That address belongs to Relia Technologies, as
> http://www.coffer.com/mac_find/?string=00%3Ac0%3A0c
> says. In fact, when Puppy Linux is booting, displays a
> message about the Relia 2408T, which seems to be
> compatible with my card (or my card is, internally, a
> Relia), and this time I'm sure!
> OpenBSD knows this card, or that shows the pcmciadevs
> file in the CVS tree
> (http://www.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/dev/pcmcia/pcmciadevs?rev=1.131&content-type=text/plain).
> The messages showed here are identical to the messages
> my card shows (PCMCIA LAN, Ethernet, etc).
> Linux seems to knows Relia, too.

This is a good point, I should have checked it :)
I suspect it's really a DL10019 chip then. can you check if it works
with the new patch I attached ?

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--

Index: if_ne_pcmcia.c
===================================================================
RCS file: /cvsroot/src/sys/dev/pcmcia/if_ne_pcmcia.c,v
retrieving revision 1.150
diff -u -p -u -r1.150 if_ne_pcmcia.c
--- if_ne_pcmcia.c 19 Oct 2007 12:01:04 -0000 1.150
+++ if_ne_pcmcia.c 13 Mar 2008 20:20:08 -0000
@@ -111,6 +111,10 @@ static const struct ne2000dev {
       0, -1, { 0x00, 0x90, 0xcc }, NE2000DVF_AX88190 },
 
     { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
+      PCMCIA_CIS_RELIA_RE2408T,
+      0, -1, { 0x00, 0xc0, 0x0c }, NE2000DVF_DL10019 },
+
+    { PCMCIA_VENDOR_INVALID, PCMCIA_PRODUCT_INVALID,
       PCMCIA_CIS_SYNERGY21_S21810,
       0, -1, { 0x00, 0x48, 0x54 }, 0 },
 
Index: pcmciadevs
===================================================================
RCS file: /cvsroot/src/sys/dev/pcmcia/pcmciadevs,v
retrieving revision 1.223
diff -u -p -u -r1.223 pcmciadevs
--- pcmciadevs 22 Sep 2007 19:59:55 -0000 1.223
+++ pcmciadevs 13 Mar 2008 20:20:08 -0000
@@ -455,6 +455,7 @@ vendor NDC -1 NDC
 vendor PLANET -1 Planet
 vendor PLANEX -1 Planex Communications Inc
 vendor PREMAX -1 Premax
+vendor RELIA -1 Relia Technologies
 vendor RPTI -1 RPTI
 vendor SVEC -1 SVEC/Hawking Technology
 vendor SYNERGY21 -1 Synergy 21
@@ -499,6 +500,7 @@ product DYNALINK L10C { "DYNALINK", "L1
 product EIGERLABS EPX_AA2000 { "Eiger&splabs,Inc.", "EPX-AA2000&spPC&spSound&spCard", NULL, NULL } EPX-AA2000 PC Sound Card
 product EPSON EEN10B { "Seiko&spEpson&spCorp.", "Ethernet", "P/N:&spEEN10B&spRev.&sp00", NULL } Epson EEN10B
 product EXP EXPMULTIMEDIA { "EXP&sp&sp&sp", "PnPIDE", "F1", NULL } EXP IDE/ATAPI DVD Card
+product RELIA RE2408T { "PCMCIA&spLAN", "Ethernet", "A", NULL } Relia RE2408T ethernet adapter
 product FUJITSU FMV_J181 { "PCMCIA&spMBH10302", "01", NULL, NULL } FUJITSU FMV-J181 PCMCIA Card
 product FUJITSU FMV_J182 { "FUJITSU", "LAN&spCard(FMV-J182)", "Ver.01", NULL } FUJITSU FMV-J182 PCMCIA Card
 product FUJITSU FMV_J182A { "FUJITSU", "LAN&spCard(FMV-J182)", "Ver.02", NULL } FUJITSU FMV-J182A PCMCIA Card
Index: pcmciadevs.h
===================================================================
RCS file: /cvsroot/src/sys/dev/pcmcia/pcmciadevs.h,v
retrieving revision 1.226
diff -u -p -u -r1.226 pcmciadevs.h
--- pcmciadevs.h 22 Sep 2007 20:01:21 -0000 1.226
+++ pcmciadevs.h 13 Mar 2008 20:20:08 -0000
@@ -1,4 +1,4 @@
-/* $NetBSD: pcmciadevs.h,v 1.226 2007/09/22 20:01:21 kiyohara Exp $ */
+/* $NetBSD$ */
 
 /*
  * THIS FILE AUTOMATICALLY GENERATED.  DO NOT EDIT.
@@ -633,6 +633,7 @@
 #define PCMCIA_VENDOR_PLANET -1 /* Planet */
 #define PCMCIA_VENDOR_PLANEX -1 /* Planex Communications Inc */
 #define PCMCIA_VENDOR_PREMAX -1 /* Premax */
+#define PCMCIA_VENDOR_RELIA -1 /* Relia Technologies */
 #define PCMCIA_VENDOR_RPTI -1 /* RPTI */
 #define PCMCIA_VENDOR_SVEC -1 /* SVEC/Hawking Technology */
 #define PCMCIA_VENDOR_SYNERGY21 -1 /* Synergy 21 */
@@ -708,6 +709,8 @@
 #define PCMCIA_PRODUCT_EPSON_EEN10B -1
 #define PCMCIA_CIS_EXP_EXPMULTIMEDIA { "EXP   ", "PnPIDE", "F1", NULL }
 #define PCMCIA_PRODUCT_EXP_EXPMULTIMEDIA -1
+#define PCMCIA_CIS_RELIA_RE2408T { "PCMCIA LAN", "Ethernet", "A", NULL }
+#define PCMCIA_PRODUCT_RELIA_RE2408T -1
 #define PCMCIA_CIS_FUJITSU_FMV_J181 { "PCMCIA MBH10302", "01", NULL, NULL }
 #define PCMCIA_PRODUCT_FUJITSU_FMV_J181 -1
 #define PCMCIA_CIS_FUJITSU_FMV_J182 { "FUJITSU", "LAN Card(FMV-J182)", "Ver.01", NULL }
Index: pcmciadevs_data.h
===================================================================
RCS file: /cvsroot/src/sys/dev/pcmcia/pcmciadevs_data.h,v
retrieving revision 1.226
diff -u -p -u -r1.226 pcmciadevs_data.h
--- pcmciadevs_data.h 22 Sep 2007 20:01:21 -0000 1.226
+++ pcmciadevs_data.h 13 Mar 2008 20:20:08 -0000
@@ -1,4 +1,4 @@
-/* $NetBSD: pcmciadevs_data.h,v 1.226 2007/09/22 20:01:21 kiyohara Exp $ */
+/* $NetBSD$ */
 
 /*
  * THIS FILE AUTOMATICALLY GENERATED.  DO NOT EDIT.
@@ -1478,6 +1478,13 @@ struct pcmcia_knowndev pcmcia_knowndevs[
     "EXP IDE/ATAPI DVD Card", }
  ,
  {
+    PCMCIA_VENDOR_UNKNOWN, PCMCIA_PRODUCT_RELIA_RE2408T,
+    PCMCIA_CIS_RELIA_RE2408T,
+    0,
+    "Relia Technologies",
+    "Relia RE2408T ethernet adapter", }
+ ,
+ {
     PCMCIA_VENDOR_UNKNOWN, PCMCIA_PRODUCT_FUJITSU_FMV_J181,
     PCMCIA_CIS_FUJITSU_FMV_J181,
     0,
@@ -2549,6 +2556,14 @@ struct pcmcia_knowndev pcmcia_knowndevs[
     NULL,
  },
  {
+    PCMCIA_VENDOR_RELIA,
+    PCMCIA_KNOWNDEV_NOPROD,
+    PCMCIA_CIS_INVALID,
+    0,
+    "Relia Technologies",
+    NULL,
+ },
+ {
     PCMCIA_VENDOR_RPTI,
     PCMCIA_KNOWNDEV_NOPROD,
     PCMCIA_CIS_INVALID,

[Javier Steinaker]

Hi again, and sorry for the delay.
We (well, you, really) are more close to the solution.
The card isn't working, but the kernel now shows:
ne0 at pcmcia0 function 0: <PCMCIA LAN, Ethernet, A,
004743118001>
ne0: can't match ethernet vendor code

I also tried to modify the line
+product RELIA RE2408T { "PCMCIA&spLAN", Ethernet",
"A", NULL } Relia RE2408T ethernet adapter
by
+product RELIA RE2408T { "PCMCIA&spLAN", Ethernet",
"A", "004743118001" } Relia RE2408T ethernet adapter
... but the result is the same.

I think the solution is close to us, but... I cannot
find it. Ideas?

Greetings,
Javier


      Tarjeta de crédito Yahoo! de Banco Supervielle.
Solicitá tu nueva Tarjeta de crédito. De tu PC directo a tu casa. www.tuprimeratarjeta.com.ar

[Manuel Bouyer]

On Tue, Mar 18, 2008 at 10:42:39AM -0300, Javier Steinaker wrote:

> Hi again, and sorry for the delay.
> We (well, you, really) are more close to the solution.
> The card isn't working, but the kernel now shows:
> ne0 at pcmcia0 function 0: <PCMCIA LAN, Ethernet, A,
> 004743118001>
> ne0: can't match ethernet vendor code
>
> I also tried to modify the line
> +product RELIA RE2408T { "PCMCIA&spLAN", Ethernet",
> "A", NULL } Relia RE2408T ethernet adapter
> by
> +product RELIA RE2408T { "PCMCIA&spLAN", Ethernet",
> "A", "004743118001" } Relia RE2408T ethernet adapter
> ... but the result is the same.
>
> I think the solution is close to us, but... I cannot
> find it. Ideas?

I'm not sure it's closer than before. It couldn't find the ethernet address
while before it didn't even check it (if I read the code properly).

Can you add some printf() to ne_pcmcia_attach() to see what's going on ?
The interesting part if between again: and the last 'goto again'.
it should enter the (ne_dev->flags & NE2000DVF_DL10019) if, and
call ne_pcmcia_dl10019_get_enaddr(). Either ne_pcmcia_dl10019_get_enaddr()
didn't work, or it didn't return the mac address we expect.

You could also try changing {0x00, 0xc0, 0x0c} with {0xff,0xff,0xff} in
the PCMCIA_CIS_RELIA_RE2408T entry.

--
Manuel Bouyer <bouyer@...>
     NetBSD: 26 ans d'experience feront toujours la difference
--