You are not logged in.
Hi, I tried getting a fix in the pacman upgrade forum without success, I'm hoping somebody can help me salvage my Arch installation on our server...
After a pacman upgrade a few weeks ago we don't have any internet access on our machine. This isn't wireless but through ethernet using a realtek 8111E Ethernet controller.
Doing a lspci -v I find that I have the realtek RTL8111/8168B module.
with dmesg | grep r8169 I get:
r8169 Gigabit Ethernet drive 2.3LK-NAPI loaded
r8169 ...
r8169 ...
r8169 ...
r8169 ...
r8169....
r8169 0000:03:00.0: eth0 link down
r8169 0000:03:00.0: eth0 link down
I then try sudo ifconfig eth0 link up
"link: Host name lookup failure"
When I run ifconfig I get
eth0 Link encap:Ethernet HWaddr " "
UP Broadcast Multicast MTU....
Rx Packets:0 ...0 ...0 ...0
Tx Packets:0 ...0 ...0 ...0
Collisions: 0 , ....0
Interrupt:54 Base add...:0x4000
lo Link encap: Local Loopback
On bootup it notifies me that it failed to load the network daemon.
Would anybody have an idea what the problem could be?
Thanks in advance.
Last edited by leberyo (2011-05-20 17:08:20)
Offline
Try resetting bios. So many people have problems with 8168/8169
Offline
It works with Windows. I have a dual boot setup....
Offline
Post your /etc/rc.conf
Better yet, use the following in your network section:
eth0="eth0 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255"
gateway="default gw 192.168.0.1"
INTERFACES=(eth0)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Post your /etc/rc.conf
Better yet, use the following in your network section:
eth0="eth0 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255" gateway="default gw 192.168.0.1" INTERFACES=(eth0)
Hi, I entered your info into my rc.conf except with my routers info 192.168.1.10 255.255.255.0 192.168.1.255
gw 192.168.1.1
I don't get a fail on bootup for the network daemon anymore but still no internet...
When I "ping 192.168.1.1" I get: "PING 192.168.1.1 56(84) bytes of data" on the first line and then "destination host unreachable" afterwards.
Last edited by leberyo (2011-05-12 00:18:55)
Offline
Hmm... perhaps your /etc/resolv.conf isn't correct?
Make your /etc/resolv.conf.head read:
nameserver 4.2.2.2
nameserver 4.2.2.1
Then restart the network and try to ping google.com.
EDIT: Ah, you can't even ping your router... dunno what to tell ya.
Last edited by graysky (2011-05-12 00:23:50)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
If it were me I’d be seeing if the kernel or some other network package got changed when you changed Pacman, and try reverting to the version before the change.
Offline
If it were me I’d be seeing if the kernel or some other network package got changed when you changed Pacman, and try reverting to the version before the change.
I've downloaded two new kernels and headers through another machine and did a pacman -U install. They didn't help.
Anybody else have an idea what the the problem is?
Checking my errors.log, the last line says:
localhost kernel : [ 27.524270] ioremap error for 0xdf7d1000-0xdf7d2000, requested 0x10, got 0x0
Last edited by leberyo (2011-05-12 17:36:32)
Offline
doing a "dmesg | grep r8169" I get:
[ 6.208961] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 6.208985] r8169 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 6.209081] r8169 0000:03:00.0: setting latency timer to 64
[ 6.209086] r8169 0000:03:00.0: (unregistered net_device): unknown MAC, using family default
[ 6.209132] r8169 0000:03:00.0: irq 46 for MSI/MSI-X
[ 6.209307] r8169 0000:03:00.0: eth0: RTL8168b/8111b at 0xffffc90000656000, 1c:6f:65:3e:81:ae, XID 0c200000 IRQ 46
[ 20.904076] r8169 0000:03:00.0: eth0: link down
[ 20.904082] r8169 0000:03:00.0: eth0: link down
Offline
Hi, I had very bad experience with realtek 8169 (can not remember exact version/name)
It stopped working with one kernel upgrade, probably 2.6.33, I had to keep previous version of kernel for some half of year, and when even another version of kernel (third in line) it did not worked, I just bought new card.
And similarly to your situation 'nothing was wrong', no errors in logs, device (eth0) was created
What used to work with this card was to disconnect box from power (backward switch on box would be enough) and pressing front power button - diods flashed - some remaining electricity discharged and next time network card worked.
Offline
I then try sudo ifconfig eth0 link up
"link: Host name lookup failure"
The command is "sudo ifconfig eth0 up"
Offline
leberyo wrote:I then try sudo ifconfig eth0 link up
"link: Host name lookup failure"The command is "sudo ifconfig eth0 up"
Tried that too...
Offline
I'd still appreciate any kind of help. Still haven't found a fix.
I've gone back to using:
eth="dhcp"
interfaces=(eth0)
on my rc.conf.
When the daemons boot up, network gives "Failed".
When I type sudo dhcpd eth0
it says
dhcpd: command not found.
I have dhcpd installed already though I think and it was working before.
Offline
dhcpcd
Offline
Ahh, ok was misspelling I type sudo dhcpcd eth0 and get:
dhcpcd[3815]: version 5.2.12 starting
dhcpcd[3815]: eth0: waiting for carrier
timed out
I've read elsewhere that the Realtek r8169 module might be the problem. I've blacklisted it in my rc.conf by !r8169. Still no go.
Last edited by leberyo (2011-05-19 23:56:18)
Offline
rc.conf should say:
eth0="dhcp"
interfaces=(eth0)
Offline
rc.conf should say:
eth0="dhcp" interfaces=(eth0)
It does.
Offline
then try using dhclient instead.
usage is the same:
# dhclient eth0
you need to install it, though. (pacman -S dhclient)
Offline
Hi Leberyo
I've downloaded two new kernels and headers through another machine and did a pacman -U install. They didn't help.
Sounds like you tried upgrading the kernel; I was suggesting to try downgrading. Your original complaint was “After an upgrade, things broke”, so my reaction would be to undo that upgrade.
Perhaps you can look through /var/log/pacman.log (starting at the end) for changes to the kernel26 or related package. For example on my computer it has
[2011-05-10 01:32] upgraded kernel26 (2.6.37.2-1 -> 2.6.38.5-1)
I’m currently running kernel26 2.6.38.5-1. What I was suggesting was trying your equivalent of
sudo pacman -U /var/cache/pacman/pkg/kernel26-2.6.37.2-1-x86_64.pkg.tar.xz
In fact in that cache directory hopefully you have a few older kernels you can test.
When I "ping 192.168.1.1" I get: "PING 192.168.1.1 56(84) bytes of data" on the first line and then "destination host unreachable" afterwards.
Assuming your IP address settings were correct for your router to respond, I really suspect the problem is in the hardware, or low level kernel driver. I doubt a different DHCP client will help, but maybe it’s worth a try anyway
Offline
I know you had said that it works with Windows. I'm going to ignore that and suggest something that has solved this sort of problem more times than I count in binary on two hands.
<Ignore Windows>Please don't be insulted, but have you checked the cable? Are the link lights on both at your NIC and at the router? </Ignore Windows> Does it still work under Windows?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I have same/similar ethernet controller(module r8169). Sometimes link speed auto negotiation doesn't work and I'll have to turn autoneg off with ethtool and set link speed manually. Maybe same problem with your nic.
Offline
ewaller all the lights are green on my router and the ethernet cable connected to my computer.
I've been googling the realtek 8169 module and it seems like I should be using the r8168 module for my Lan chipset which is a realtek 8111E. I'm not exactly sure about this and wanted to confirm with others. I really have no idea how to install a different kernel module though.
Offline
I really have no idea how to install a different kernel module though.
By hand, use rmmod and modprobe
Once you get things sorted out, you will modify the MODULES arrat in /etc/rc.conf. Blacklist a module my pre-pending a '!' to the "bad" module name to prevent it being loaded, and include the "good" module name in the line to force it to be loaded.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I've blacklisted r8169 by putting in !r8169
On Aur there is a r8168 package can't I just install that using yaourt?
Error.log says, now that I've blacklisted r8169 and installed r8168 with makepkg -s:
localhost dhcpcd[3511]: etho: interface not found or invalid.
Last edited by leberyo (2011-05-20 16:39:52)
Offline
On Aur there is a r8168 package can't I just install that using yaourt?
Well, I cannot speak to yaourt. Never tried it But yes, install it from the AUR using your method of choice
Error.log says, now that I've blacklisted r8169 and installed r8168 with makepkg -s:
localhost dhcpcd[3511]: etho: interface not found or invalid.
If you have only run makepkg, then you have built the package, but it is not yet installed. You will need to do a pacman -U path-to-package-you-built-with-makepkg
Once the module is installed and loaded into the running kernel, do a ifconfig -a and ensure the interface is listed
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline