Re: Link always down

Re: Link always down

[Clemens Brunner]

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

Re: Link always down

[Francois Romieu]

Clemens Brunner <clemens.brunner@tugraz.at> :
[...]
> 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).

The patch is not included in the latest kernel source.

Actually, you are not supposed to use the patch-kit this way. If you do
a 'tar jxvf r8169-20070522.tar.bz2', you should notice that the archive
file is extracted into a nice directory which contains a serie of patches.
You should follow the numbering of the patches and apply them to a clean
2.6.22-rc2 tree (i.e. apply 0001-foo, 0002-bar, 0003-frob, usw).

As an option you can retrieve the url below which contains all the patches
above in a single patch-file:
http://www.fr.zoreil.com/people/francois/misc/20070522-2.6.22-rc2-r8169.patch

The patch-kit allows to peel the onion more easily when somthing goes
wrong.

Btw, I have just updated everything for 2.6.22-rc3, you should try any of
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.22-rc3
http://www.fr.zoreil.com/people/francois/misc/20070527-2.6.22-rc3-r8169.patch

If you use 'make oldconfig' to update your config, you will be prompted
for 'EEPROM 93CX6 support' as the relevant bits have been extracted from
the wireless-dev git tree to access the EEPROM connected to the 816x.
Don't disable it.

-- 
Ueimor

Re: r8169: link always down

[Francois Romieu]

Francois Romieu <romieu@fr.zoreil.com> :
[...]

Btw, please include something like 'r8169' (or '8168') in the subject
of r8169 bug messages. It helps me sorting things out.

-- 
Ueimor

Re: r8169: Link always down

[Clemens Brunner]

Francois Romieu wrote:
> [...]
 > As an option you can retrieve the url below which contains all the patches
> above in a single patch-file:
> http://www.fr.zoreil.com/people/francois/misc/20070522-2.6.22-rc2-r8169.patch

Thanks for providing the single patch file. I was able to compile the patched 
kernel (version 2.6.22-rc3) with the EEPROM option enabled. However, the NIC 
still does not work (r8169: eth0: link down). Please let me know what else I 
could do to help you.

Clemens