From: Arnaud Ligot <spyroux@freegates.be>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: xircom card bus with 2.4.21 link trouble (was: xircom card bus with 2.4.20 link trouble)
Date: 20 Jun 2003 11:54:45 +0200 [thread overview]
Message-ID: <1056102885.6727.21.camel@portable> (raw)
In-Reply-To: <1056101484.6724.18.camel@portable>
against me ;-)
with a lot of tries... there are is a """solution"""
- put the card
- the led link blink
- you MUST define an IP with ifconfig
- the led link stop blinking !!!
is that a bug ?
thanks
Arnaud
Le ven 20/06/2003 à 11:31, Arnaud Ligot a écrit :
> /me auto slaps
>
> with the 2.4.20, it work but it don't work with 2.4.21.
> Sorry
>
> Le ven 20/06/2003 à 11:26, Arnaud Ligot a écrit :
> > Hello,
> >
> > Since I run the 2.4.21 kernel (+bootsplash patch), (I didn't try without
> > this patch but I think it is not the problem), my Xircom Cardbus don't
> > work any more! In fact, I put the card into the pcmcia slot, the pc
> > detect it, load the correct module (xirc2ps_cb), start eth1 but the led
> > link (both side) blinks.
> > I have try with a hub 10, a ethernet card 10 and an ethernet card
> > 10/100. I have so try 2 cables... but same problem.
> > I have try to impose the ethernet type of link mii-tool -A10BaseT-HD and
> > -F10BaseT-HD.
> >
> > Thanks
> >
> > Arnaud
> >
> > extract of /var/messages (10mbps):
> > ------
> > Jun 20 08:34:49 portable kernel: cs: memory probe 0xa0000000-0xa0ffffff:
> > clean.
> > Jun 20 08:34:49 portable kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55
> > (dd9jn+kvh)
> > Jun 20 08:34:53 portable kernel: eth1: autonegotiation failed; using
> > 10mbs
> > Jun 20 08:34:53 portable kernel: eth1: MII selected
> > Jun 20 08:34:53 portable kernel: eth1: media 10BaseT, silicon revision 0
> > Jun 20 08:34:53 portable kernel: eth1: Xircom: port 0x300, irq 3, hwaddr
> > 00:80:C7:CC:1F:A
> > 2
> > Jun 20 08:34:54 portable kernel: eth1: autonegotiation failed; using
> > 10mbs
> > Jun 20 08:34:54 portable kernel: eth1: MII selected
> > Jun 20 08:34:54 portable kernel: eth1: media 10BaseT, silicon revision 0
> > Jun 20 08:34:59 portable kernel: eth1: autonegotiation failed; using
> > 10mbs
> > Jun 20 08:34:59 portable kernel: eth1: MII selected
> > ....
> > -----
> >
> > short extract of /var/messages (100mbps):
> > -----
> > Jun 20 10:14:52 portable kernel: eth1: MII link partner: 05e1
> > Jun 20 10:14:52 portable kernel: eth1: MII selected
> > Jun 20 10:14:52 portable kernel: eth1: media 100BaseT, silicon revision
> > 5
> > -----
> >
> > ----
--
Arnaud Ligot <spyroux@freegates.be>
next prev parent reply other threads:[~2003-06-20 9:41 UTC|newest]
Thread overview: 13+ 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 [this message]
2003-06-20 14:11 ` xircom card bus with 2.4.20 link trouble Mike Dresser
2003-06-20 14:28 ` Arnaud Ligot
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
-- strict thread matches above, loose matches on Subject: below --
2003-06-20 10:22 xircom card bus with 2.4.21 link trouble (was: xircom card bus with 2.4.20 link trouble) John Bradford
2003-06-20 12:21 ` Arnaud Ligot
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=1056102885.6727.21.camel@portable \
--to=spyroux@freegates.be \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox