From: Kasper Sandberg <lkml@metanurb.dk>
To: Jacques de Krahe <dekrahe@tiscali.be>
Cc: c-d hailfinger <linux-kernel@vger.kernel.org>,
hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Subject: Re: forcedeth
Date: Fri, 02 Dec 2005 21:54:52 +0100 [thread overview]
Message-ID: <1133556892.16820.13.camel@localhost> (raw)
In-Reply-To: <1133554191.4786.8.camel@localhost.localdomain>
On Fri, 2005-12-02 at 21:09 +0100, Jacques de Krahe wrote:
> Running FC4 on a PC equipped with NForce2 chipset and AMD k7 (Athlon XP
> 2200)
> The eth interface can't be normally configured at boot and fails.
> The problem comes from forcedeth. The system asks me to have a look into
> dmesg, where I find a line that reads a follows: forcedeth : Unknown
> parameter "irq"
are you trying to load forcedeth with a parameter called "irq" ? if so,
try without
> The next line in /var/log/dmesg shows the version number.
> Is it possible to correct the code and what are the necessary steps to
> get a functional module?
> If you answer my question, please be as complete as possible, I am a new
> user of FC4.
> Thank in advance
> Regards
> Jacques de Krahe
>
> -
> 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/
>
next prev parent reply other threads:[~2005-12-02 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 20:09 forcedeth Jacques de Krahe
2005-12-02 20:54 ` Kasper Sandberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-01 18:16 forcedeth James Drabb
2004-08-01 19:14 ` forcedeth Manfred Spraul
2004-08-01 22:01 ` forcedeth James Drabb
2004-08-02 19:38 ` forcedeth Manfred Spraul
2003-11-13 13:07 forcedeth Richard
2003-11-10 1:45 forcedeth Gustavo De Nardin
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=1133556892.16820.13.camel@localhost \
--to=lkml@metanurb.dk \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=dekrahe@tiscali.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.