From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Kenneth Krekula <kenneth.krekula@kiruna.se>
Cc: netdev@oss.sgi.com
Subject: Re: A small forcedeth driver issue
Date: Tue, 10 Feb 2004 01:04:22 +0100 [thread overview]
Message-ID: <40282006.2090508@gmx.net> (raw)
In-Reply-To: <200402092252.22540.kenneth.krekula@kiruna.se>
Kenneth Krekula wrote:
> Hi.
>
> I have a NForce1 motherboard and have tested the forcedeth driver with
> the Mandrake 10 betas. The driver works very well (thanks for the great
> work!!) and I only have a small issue:
>
> If I have been using the driver in Mandrake 10 beta 2, and reboot into
> Win XP or Mandrake Linux 9.2 (with the NVIdia NForce drivers) the
> network just fails.
I assume it works fine if you reboot into Linux with forcedeth again, right?
> However, if I shut off the power switch and wait for some seconds, I
> can power on and boot into Win XP, Mandrake 9.2.
>
> I don't know if this is a known issue or not.
Yes, it's a known issue. Basically, forcedeth does not shutdown the
hardware completely, but this should not matter if it is reinitialized
correctly during the next boot. forcedeth can reinitialize hardware even
if it wasn't shutdown completely. The windows driver, however, lacks this
feature and therefore fails.
There are two ways to deal with the issue:
- get a better windows driver (more recent versions from Nvidia *should* work)
- wait a few weeks until I get access to some nforce hardware and can fix
this.
I do not want to change the shutdown procedure without testing it on real
hardware. The last time I did that, I got a complete lockup.
HTH,
Carl-Daniel
--
http://www.hailfinger.org/
prev parent reply other threads:[~2004-02-10 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 21:52 A small forcedeth driver issue Kenneth Krekula
2004-02-10 0:04 ` Carl-Daniel Hailfinger [this message]
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=40282006.2090508@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=kenneth.krekula@kiruna.se \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).