netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: smolny@o2.pl
Cc: foner+x-forcedeth@media.mit.edu,
	Manfred Spraul <manfred@colorfullife.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew de Quincey <adq@lidskialf.net>,
	Netdev <netdev@oss.sgi.com>
Subject: Re: Forcedeth and vesa
Date: Fri, 04 Jun 2004 16:25:02 +0200	[thread overview]
Message-ID: <40C0863E.9070508@gmx.net> (raw)
In-Reply-To: <20040604135640.C218BD0B60@rekin6.o2.pl>

Hi,

[foner: I included you in the CC because your problem seems similar.]

smolny@o2.pl wrote:
> Hi,
> Sorry if you get this post by mistake. I found your address googling
> for "forcedeth vesa".

Well, you reached the right person.

> When i use forcedeth module, both with 2.4.26 and 2.6.6 kernels, i
> can't access vesa with mplayer. Just loading the module doesn't
> cause the problem, only after i configure the net with ifconfig i
> can't use vesa.

This is interesting. Does the problem persist if you ifdown the interface?

> If i use nvnet NVidia driver with 2.4.26, everything goes fine (no
> nvnet for 2.6.x kernels). 

That is even more interesting. So the bug affects forcedeth, but not
nvnet. Hmmm. We'll have to review the code again.

> It's an EPOX 8RDA+ motherboard.

Foner: Do you see similarities between your problem and this one?

Janusz, Foner: Are you willing to test forcedeth with a few dozen
iterations of
patch, recompile, install, power down, power up and test again?

I would send you patches to binary search the offending code.

Regards,
Carl-Daniel

       reply	other threads:[~2004-06-04 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040604135640.C218BD0B60@rekin6.o2.pl>
2004-06-04 14:25 ` Carl-Daniel Hailfinger [this message]
2004-06-04 14:41   ` Forcedeth and vesa Andrew de Quincey
2004-06-12  2:47   ` Lenny Foner

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=40C0863E.9070508@gmx.net \
    --to=c-d.hailfinger.kernel.2004@gmx.net \
    --cc=adq@lidskialf.net \
    --cc=foner+x-forcedeth@media.mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=netdev@oss.sgi.com \
    --cc=smolny@o2.pl \
    /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;
as well as URLs for NNTP newsgroup(s).