public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
To: Johan <jo_ni@telia.com>, linux-kernel@vger.kernel.org
Cc: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Subject: Re: Still having problems with eepro100
Date: Tue, 30 Oct 2001 17:07:36 -0000	[thread overview]
Message-ID: <38130000.1004461656@shed> (raw)
In-Reply-To: <20011030123927.74e26501.jo_ni@telia.com>
In-Reply-To: <20011030123927.74e26501.jo_ni@telia.com>

Johan,

If you mean occasional lockups, which go away if you do ifdown / ifup,
then try the patch I posted Sunday - it forces one of the bug workarounds
on, which was dependent on eeprom by default. Also has a debug line
which writes out what it thinks the chip ID is, which activates
(or not) the other bug workaround. Alan put some or all of this
patch into the latest -ac; from his docs I couldn't tell whether
he put in the 'always use bug override' bit, and I expect not.
if you want to do it yourself, find where rx_bug is set, and just
set it to 1 the line afterwards, and try that.

Alternatively, try the intel drivers.

Alex

--On Tuesday, October 30, 2001 12:39:27 +0100 Johan <jo_ni@telia.com> wrote:

>
> Hello,
> Does anyone except me still having problems with the eepro100 drivers ?
>
> The network connection stalls and I'll get this message:
>
> eepro100: wait_for_cmd_done timeout!
>
> I am using the eepro100 drivers with my 100/10 card running in
> 10mbit and it works in windows.
>
> I have been trying all new kernels + the ac patches but nothing
> seems to work. The fun thing is that I only gets this problem
> when I am running XFree, is this just a weird coincidence?
>
> /Johan Nilsson
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>



--
Alex Bligh

  parent reply	other threads:[~2001-10-30 17:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30 11:39 Still having problems with eepro100 Johan
2001-10-30 11:57 ` Thomas Langås
2001-10-30 12:05   ` Johan
2001-10-30 12:58     ` Kirill Ratkin
2001-10-30 20:19   ` Kurt Roeckx
2001-10-30 12:09 ` Alan Cox
2001-10-30 12:20   ` Rafael Martinez
2001-10-30 16:23 ` Lee Packham
2001-10-30 16:51   ` Kirill Ratkin
2001-10-30 17:07 ` Alex Bligh - linux-kernel [this message]
2001-10-31 14:40   ` Alex Bligh - linux-kernel
2001-11-01 11:15 ` Andrey Savochkin
2001-11-01 11:33   ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2001-12-01  0:08 Joe Rice
2001-12-01  0:37 ` Mike Fedyk
2001-12-01  0:49   ` Joe Rice
2001-12-01  1:07     ` Mike Fedyk

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=38130000.1004461656@shed \
    --to=linux-kernel@alex.org.uk \
    --cc=jo_ni@telia.com \
    --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