You are not logged in.
Pages: 1
I seem to be suffering the old realtek driver issue for my networking only on arch. The attempts to connect via dhcpd time out or are connected and then i suffer large amounts of packet loss. unloading the r8169 module obviously means i get no eth0 device. Chucking a gentoo install disk in and checking the results of lsmod reveals that it is successfully using the same driver - an modinfo shows it is the same version. I only seem to have problems with Arch (which i have used successfully in the past.. I am sure using this same adapter...). Does anybody have any ideas of what I could try - I am at the tearing my hair out stage. I installed off both the standard disks and the archboot disks.
Offline
Must be some kind of regression, at least another user reports having the same problem here [1].
However the solution used could be a bit more refined, as in creating a pkgbuild for the update so all files are tracked.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
I'm using the same module on my laptop right now with no problem. Just an FYI.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
This is still present in the 2.6.38 kernel currently in core. I fluked an update to core.db and then ran the updates locally from packages on a USB stick (very dirty I know, but as I said I am desperate!). I will try the module off the website, although i don't currently have another Arch box to compile it on.
Offline
Same problem here. I can't do a network install because it's too flaky to get a solid connection. Often the network card just completely dies and nothing gets through (eg. endless arp requests). I tried both the 2010.05 official release and the latest 2011.05 builds.
I'm using a IP35-Pro motherboard which I believe has the Realtek 8110sc card (uses the r8169 driver). Years ago Arch used to work on this system but at some point this issue popped up and I haven't used Arch in years because of it. I was just trying the latest version to see if it had resolved, I guess not. Never seen this issue on any other distro, they must maintain patches specifically for these cards or something.
I mean I could probably do a non-network full install and copy all the crap I need for building from another install and then build the latest Realtek driver but come on, that would be a fragile solution and I want to use my system to get stuff done not mess with junk like this.
Last edited by excl (2011-05-21 13:40:40)
I only installed Arch yesterday but so far every boot I have had connectivity. I have a Gigabyte GA-P55A-UD3 board and
it has the Realtek 8111 Ethernet controller
lspci -v
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
Flags: bus master, fast devsel, latency 0, IRQ 46
I/O ports at be00 [size=256]
Memory at fbeff000 (64-bit, prefetchable) [size=4K]
Memory at fbef8000 (64-bit, prefetchable) [size=16K]
[virtual] Expansion ROM at fbe00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169
For many months I have had an intermittant connection problem on Ethernet, about 1 in 20 boots I have no connectivity. Only way
is to power down and unplug for about 3 minutes. Cold boot resets the ethernet connection. Problem happens across various linux
systems and windows, so I think its hardware (in my case).
I have seen other people with same hardware and similar problem one solution was to unload and reload the driver
modprobe -r r8169
modprobe 8169
Only other thing you can try is static adressing. DHCP adds about 3 seconds to my boot time just to get an IP address, static adressing
may speed your boot, not sure if it solve the problem though.
Offline
Pages: 1