Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12108 - Network fails after last kernel update [Realtek RTL8101E]

Attached to Project: Arch Linux
Opened by Luís Moreira (knap) - Wednesday, 12 November 2008, 19:39 GMT
Last edited by Aaron Griffin (phrakture) - Sunday, 23 November 2008, 03:07 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hello.

After last kernel update

kernel26-2.6.27.4-1 -> kernel26-2.6.27.5-1

network stopped working (can't get an ip lease) with an Intel D945GCLF board (RTL8101E ethernet network chipset).

I downgraded the kernel to version 2.6.27.4-1 and the network started working again so this is definitely a kernel issue.

Using X86_64 with all the updates.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Sunday, 23 November 2008, 03:07 GMT
Reason for closing:  Fixed
Comment by Jakob Gruber (schuay) - Thursday, 13 November 2008, 08:15 GMT
working ok for me.. i'm using the rtl8101 package from aur instead of the r8169 module (had some problems with 100% dropped packets on that)

$ lspci | grep RTL
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

$ uname -a
Linux one 2.6.27-ARCH #1 SMP PREEMPT Sat Nov 8 10:11:43 UTC 2008 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux

$ pacman -Q kernel26
kernel26 2.6.27.5-1

$ lsmod | grep r8
r8101 31376 0

$ pacman -Qs 8101
local/rtl8101 1.009.00-1
rtl8101 realter lan drivers, working with msi wind

Comment by Jakob Gruber (schuay) - Thursday, 13 November 2008, 08:22 GMT
Just noticed that your report concerns x86_64 so my previous comment might not be relevant..
Comment by Luís Moreira (knap) - Thursday, 13 November 2008, 10:32 GMT
My report concerns X86_64 because this is what I'm using in this box, don't know if it also happens with i686.

I'm not using the drive from AUR, using the stock driver (r8169 probably?)

Thanks for the comments.
Comment by Luís Moreira (knap) - Saturday, 22 November 2008, 19:03 GMT
Hello.

The bug seems fixed after the latest kernel update to kernel26-2.6.27.6-1.

The bug report can be closed.

Loading...