[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <46569CF4.2030108@tugraz.at>
Date: Fri, 25 May 2007 10:23:16 +0200
From: Clemens Brunner <clemens.brunner@...raz.at>
To: Francois Romieu <romieu@...zoreil.com>
CC: netdev@...r.kernel.org
Subject: Re: Link always down
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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists