From: Clemens Brunner <clemens.brunner@tugraz.at>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: Link always down
Date: Fri, 25 May 2007 10:23:16 +0200 [thread overview]
Message-ID: <46569CF4.2030108@tugraz.at> (raw)
In-Reply-To: <20070524120644.GA7224@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> It's known and it hits several P5B users. The 8168 works fine on a different
> motherboard though. It would be helpful if you could investigate the effect
> of the 8168 related options in your bios/and or in Windows (WOL, network
> boot, whatever) combined with the use of
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.22-rc2 on top of 2.6.22-rc2.
I've compiled and installed the latest kernel 2.6.22-rc2, but I wasn't able to
apply your patch (using bzip2 -dc /usr/src/r8169-20070522.tar.bz2 | patch p1
--dry-run yielded the message "Reversed (or previously applied) patch
detected!", so I guess this patch was already included in the latest kernel
source). Anyway, I started my system with the latest kernel, but I still got
the same kernel message "r8169: eth0: link down".
In my BIOS, the only option related to the NIC is "LAN Option ROM" - this was
disabled by default, so I enabled it, booted Linux, but the driver is still
not working.
I don't know what else to try as there are no more BIOS options available. In
Windows, the NIC is working with the Realtek driver from the company's
website. I've tried the driver by Realtek, but I wasn't able to install the
r1000 module, because modprobe r1000 said "FATAL: Error inserting r1000
(/lib/modules/2.6.22-rc2-default/kernel/drivers/net/r1000.ko): Unknown symbol
in module, or unknown parameter (see dmesg)". The unknown symbol was "r1000:
Unknown symbol pci_module_init".
Clemens
next parent reply other threads:[~2007-05-25 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46557430.5060501@tugraz.at>
[not found] ` <20070524120644.GA7224@electric-eye.fr.zoreil.com>
2007-05-25 8:23 ` Clemens Brunner [this message]
2007-05-27 22:20 ` Link always down Francois Romieu
2007-05-27 22:35 ` r8169: link " Francois Romieu
2007-05-29 8:46 ` r8169: Link " Clemens Brunner
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=46569CF4.2030108@tugraz.at \
--to=clemens.brunner@tugraz.at \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).