From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: "Tom Sightler" <ttsig@tuxyturvy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac9
Date: Wed, 6 Jun 2001 14:54:14 -0700 [thread overview]
Message-ID: <200106062154.f56LsE115507@moisil.badula.org> (raw)
In-Reply-To: <002e01c0eead$03c6d890$26040a0a@zeusinc.com>
On Wed, 6 Jun 2001 13:20:41 -0400, Tom Sightler <ttsig@tuxyturvy.com> wrote:
>> 2.4.5-ac9
>
>> o Fix xircom_cb problems with some cisco kit (Ion Badulescu)
>
> I'm not sure what this is supposed to fix, but it makes my Xircom
> RBEM56G-100 almost useless on my network at the office. Actually, I can't
> quite blame just this patch, it only makes the problem worse, the driver
> from 2.4.5-ac3 worked, but with 1 second ping times, the new driver barely
> works at all, it seems to think the link is not there, at least not enough
> to pull an IP address.
The patch does only one thing: it instructs the card not to negotiate
full-duplex modes, because (for undocumented and yet unexplained reasons)
full-duplex modes don't work well on this card.
If you had problems before, then their cause is most likely elsewhere.
1-second ping time is definitely wrong.
> The last driver that worked moderately well for me was the one from
> 2.4.4-ac11, it still had a few issues, mostly when resuming, but everything
> worked at home on my 10Mb hub, and at the office on my 10/100Mb FD Cisco
> 6509. I must admist that I haven't tested every version in between.
The thing is, I don't really see any significant differences between the
2.4.4-ac11 driver and the 2.4.5-ac9 driver. I see lots of clean-ups, some
power management stuff, and the half-duplex stuff. None of them should
affect the core functionality directly..
Please do me a favor: comment out the call to set_half_duplex() (in
xircom_up), recompile and see if it makes a difference.
> One other note, the version in 2.4.4-ac11 is listed as 1.33 while the
> version in 2.4.5-ac9 is 1.11, why did we go backwards? Were there
> significant problems with the newer version? The 1.33 sure seems to work
> better for me.
The CVS version is almost irrelevant, I guess Arjan simply rebuild his
repository.
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
next prev parent reply other threads:[~2001-06-06 21:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 22:49 Alan Cox
2001-06-06 2:03 ` Keith Owens
2001-06-06 4:32 ` David Ford
2001-06-06 4:39 ` Jeff Garzik
2001-06-06 4:55 ` David Ford
2001-06-06 5:25 ` Keith Owens
2001-06-06 6:08 ` SCSI is as SCSI don't Alan Olsen
2001-06-06 5:39 ` Greg KH
2001-06-06 8:04 ` Alan Olsen
2001-06-06 6:20 ` Alan Olsen
2001-06-06 7:49 ` Alan Cox
2001-06-07 0:00 ` Alan Olsen
2001-06-06 9:15 ` Linux 2.4.5-ac9 Thomas Sailer
2001-06-06 21:43 ` Alan Cox
2001-06-06 10:51 ` Christoph Hellwig
2001-06-06 11:41 ` Thomas Sailer
2001-06-06 13:40 ` Christoph Hellwig
2001-06-06 14:49 ` Chris Liebman
2001-06-06 17:20 ` Tom Sightler
2001-06-06 21:54 ` Ion Badulescu [this message]
2001-06-07 3:30 ` xircom_cb problems Tom Sightler
2001-06-07 8:31 ` Ion Badulescu
2001-06-07 18:40 ` Tom Sightler
2001-06-07 20:29 ` Ion Badulescu
2001-06-08 14:11 ` Tom Sightler
2001-06-08 20:34 ` Ion Badulescu
2001-06-09 1:36 ` Tom Sightler
2001-06-06 22:44 ` Linux 2.4.5-ac9 arjan
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=200106062154.f56LsE115507@moisil.badula.org \
--to=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=ttsig@tuxyturvy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®