All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Ligot <spyroux@freegates.be>
To: Mike Dresser <mdresser_l@windsormachine.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: xircom card bus with 2.4.20 link trouble
Date: 20 Jun 2003 16:28:27 +0200	[thread overview]
Message-ID: <1056119306.6727.27.camel@portable> (raw)
In-Reply-To: <Pine.LNX.4.33.0306201007470.15589-100000@router.windsormachine.com>

Le ven 20/06/2003 à 16:11, Mike Dresser a écrit :
>> bla bla bla...
> 
> Mine doesn't work either, I have a RBEM56G-100.
> 
> Bought this off ebay for quite cheap to replace my REM56G-100.
> 
> It detects it, etc etc, but never actually works.
> 
> I put the REM56G-100 back in, insmod'd the driver, and back in business.
> 
I have a CEM56-100

> I haven't tried a 2.5.x kernel, nor a 2.4.21(it's on my list of things to
> do)
the card works with 2.4.20 nice and works if you set an ip address with
the 2.4.21

> I was using the xircom_cb driver though.  The xircom_tulip_cb didn't work
> either.
I use the xirc2ps_cs module. I haven't force cardmgr to use so I think
it's the good module for the card

-- 
Arnaud Ligot <spyroux@freegates.be>


  reply	other threads:[~2003-06-20 14:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20  9:26 xircom card bus with 2.4.20 link trouble Arnaud Ligot
2003-06-20  9:31 ` xircom card bus with 2.4.21 link trouble (was: xircom card bus with 2.4.20 link trouble) Arnaud Ligot
2003-06-20  9:54   ` Arnaud Ligot
2003-06-20 14:11 ` xircom card bus with 2.4.20 link trouble Mike Dresser
2003-06-20 14:28   ` Arnaud Ligot [this message]
2003-06-20 14:35     ` Mike Dresser
2003-06-20 16:47       ` Arnaud Ligot
2003-06-20 15:49     ` Mike Dresser
2003-06-21 11:36       ` Alan Cox
2003-06-22 19:47         ` Mike Dresser
2003-06-23 20:04           ` Mike Dresser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1056119306.6727.27.camel@portable \
    --to=spyroux@freegates.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdresser_l@windsormachine.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.