From: James Drabb <JDrabb@tampabay.rr.com>
To: netdev@oss.sgi.com
Cc: c-d.hailfinger.kernel.2004@gmx.net, manfred@colorfullife.com
Subject: forcedeth
Date: Sun, 01 Aug 2004 14:16:23 -0400 [thread overview]
Message-ID: <410D3377.3030505@tampabay.rr.com> (raw)
I am having some issues with the forcedeth driver.
jim@keelie $ modinfo forcedeth
parm: max_interrupt_work:forcedeth maximum events handled per
interrupt
author: Manfred Spraul <manfred@colorfullife.com>
description: Reverse Engineered nForce ethernet driver
license: GPL
vermagic: 2.6.7-1 686 REGPARM gcc-3.3
depends:
alias: pci:v000010DEd000001C3sv*sd*bc*sc*i*
alias: pci:v000010DEd00000066sv*sd*bc*sc*i*
alias: pci:v000010DEd000000D6sv*sd*bc*sc*i*
jim@keelie $ uname -a
Linux keelie 2.6.7-1 #1 Thu Jul 22 11:42:58 CEST 2004 i686 athlon i386
GNU/Linux
My system is an Athlon XP 2800+, on an MSI K7N2 Delta Mobo based on the
NForce 2 chipset. I have a dual boot with WinXP and Fedora Core 2 and
spend 99% of my time in FC2. Once in a while I shut the system down.
When I boot from a cold boot right into FC2, the forcedeth driver
appears not to work. I am not able to get to the net over my cable
mode. Bringing eth0 up and down, unplugging the network cable does
nothing. However, if I reboot into WinXP, and then reboot right away
back into FC2, the forcedeth driver works like a champ.
Is there anything I can do to look into what might be causing this
issue? Any more information I may be able to send to help?
Thanks for any help,
--
James Drabb
Senior Programmer
Davenport, FL USA
next reply other threads:[~2004-08-01 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 18:16 James Drabb [this message]
2004-08-01 19:14 ` forcedeth Manfred Spraul
2004-08-01 22:01 ` forcedeth James Drabb
2004-08-02 19:38 ` forcedeth Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2003-11-13 13:07 forcedeth Richard
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=410D3377.3030505@tampabay.rr.com \
--to=jdrabb@tampabay.rr.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=manfred@colorfullife.com \
--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).