public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kirill Ratkin <kratkin@egartech.com>
To: Lee Packham <linux@mswinxp.net>
Cc: jo_ni@telia.com, linux-kernel@vger.kernel.org
Subject: Re: Still having problems with eepro100
Date: Tue, 30 Oct 2001 19:51:04 +0300	[thread overview]
Message-ID: <3BDEDA78.5F2A7D19@egartech.com> (raw)
In-Reply-To: <20011030123927.74e26501.jo_ni@telia.com> <14297.193.132.197.81.1004459024.squirrel@mail.mswinxp.net>


I've seen this problem when I compiled 2.4.10 kernel with gcc version
3.0.1. I think there is some problem with broadcast and multicast 
packets because I managed to make direct connection but I can't use
dhcpd or xdmcp.


Lee Packham wrote:
> 
> This problem is inherent in FreeBSD, OpenBSD, NetBSD as well as Linux. I
> spent a few months hacking my Sony Vaio with number of OS's (it has this
> network card built onto it).
> 
> The problem is fatal unfortunately and the only solution I found was
> Intel's e100 driver.
> 
> 'nuff said
> 
> Lee Packham
> 
> >
> > 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/
> 
> -
> 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/

  reply	other threads:[~2001-10-30 16:48 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 [this message]
2001-10-30 17:07 ` Alex Bligh - linux-kernel
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=3BDEDA78.5F2A7D19@egartech.com \
    --to=kratkin@egartech.com \
    --cc=jo_ni@telia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@mswinxp.net \
    /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