|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Network/Internet Questions about internet applications, network configuration, usage (SAMBA, network printing, NFS) |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
My system can't connect to the network by the only on-board UTP connection available, getting the error:
SIOCSIFFLAGS: Cannot assign requested address I have already tried many things found at Google but I still disconnected! I am using a: - i 7 Intel 4 core 8 tread processor - 6GB Memory - GIBABYTE motherboard EX58-UD4P - On-board Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet - OpenSuse 11.1 I have tried to install the Realtek drivers r8168-8.014.00.tar.bz2 following the instructions: Realtek Code:
# make clean modules # make install # depmod -a # rmmod r8169 # modprobe r8168 Code:
# insmod ./src/r8168.ko speed=100 duplex=1 autoneg=0 # ethtool -s ethX speed 100 duplex full autoneg off ...perhaps I have tried all the tips I found about that at web... such as: Script to Fix R8168 and R8111 in Debian/Ubuntu GNU/Linux Now I get back, with the standard SUSE 11.1 installation with the following details: Code:
# ifconfig eth0 up
SIOCSIFFLAGS: Cannot assign requested address
# ifconfig eth0 192.168.0.2
SIOCSIFFLAGS: Cannot assign requested address
# lsmod | grep r8169
r8169 31388 0
mii 6024 1 r8169
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:247 Base address:0xa000
...
# ifstatus eth0
eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI ExpressGigabit Ethernet controller (rev 03)
DHCP4 client NOT running
eth0 is down
# dmesg | grep eth0
eth0: RTL8169 at 0xffffc20000c4a000, 00:00:00:00:00:00, XID 281000c0 IRQ 4343
# lspci | grep Ethernet
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
# dhclient
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
Listening on LPF/eth0/00:00:00:00:00:00
Sending on LPF/eth0/00:00:00:00:00:00
Sending on Socket/fallback
receive_packet failed on eth0: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
# cat /var/log/messages | grep eth0
Sep 1 22:05:03 linux ifdown: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Sep 1 22:05:04 linux ifup: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Sep 1 22:05:09 linux ifup-dhcp: eth0 Starting DHCP4 client
Sep 1 22:05:09 linux dhcpcd[6182]: eth0: dhcpcd 3.2.3 starting
Sep 1 22:05:09 linux dhcpcd[6182]: eth0: ioctl SIOCSIFFLAGS: Cannot assign requested address
Sep 1 22:05:09 linux dhcpcd[6182]: eth0: exiting
Sep 1 22:05:10 linux ifup-dhcp: eth0 DHCP4 client NOT running
Sep 1 22:05:10 linux ifup-route: interface eth0 is not up
Sep 1 22:06:05 linux ifdown: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Sep 1 22:06:06 linux-v38s ifup: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Sep 1 22:06:11 linux-v38s ifup-dhcp: eth0 Starting DHCP4 client
Sep 1 22:06:11 linux-v38s dhcpcd[9571]: eth0: dhcpcd 3.2.3 starting
Sep 1 22:06:11 linux-v38s dhcpcd[9571]: eth0: ioctl SIOCSIFFLAGS: Cannot assign requested address
Sep 1 22:06:11 linux-v38s dhcpcd[9571]: eth0: exiting
Sep 1 22:06:12 linux-v38s ifup-dhcp: eth0 DHCP4 client NOT running
Sep 1 22:06:12 linux-v38s ifup-route: interface eth0 is not up
Sep 1 22:09:45 linux-v38s dhclient: Listening on LPF/eth0/00:00:00:00:00:00
Sep 1 22:09:45 linux-v38s dhclient: Sending on LPF/eth0/00:00:00:00:00:00
Sep 1 22:09:45 linux-v38s dhclient: receive_packet failed on eth0: Network is down
Sep 1 22:09:47 linux-v38s dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Sep 1 22:09:52 linux-v38s dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Sep 1 22:10:01 linux-v38s dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Sep 1 22:10:11 linux-v38s dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
...
Thanks |
|
|||
|
Quote:
|
|
|||
|
Additional info:
This is the modules running now, the standard for OpenSUSE 11.1 installation: Code:
# modinfo r8169 filename: /lib/modules/2.6.27.7-9-default/kernel/drivers/net/r8169.ko version: 2.3LK-NAPI license: GPL description: RealTek RTL-8169 Gigabit Ethernet driver author: Realtek and the Linux r8169 crew <netdev@vger.kernel.org> srcversion: 27A97C1328715A534A39D92 alias: pci:v00000001d00008168sv*sd00002410bc*sc*i* alias: pci:v00001737d00001032sv*sd00000024bc*sc*i* alias: pci:v000016ECd00000116sv*sd*bc*sc*i* alias: pci:v00001259d0000C107sv*sd*bc*sc*i* alias: pci:v00001186d00004300sv*sd*bc*sc*i* alias: pci:v000010ECd00008169sv*sd*bc*sc*i* alias: pci:v000010ECd00008168sv*sd*bc*sc*i* alias: pci:v000010ECd00008167sv*sd*bc*sc*i* alias: pci:v000010ECd00008136sv*sd*bc*sc*i* alias: pci:v000010ECd00008129sv*sd*bc*sc*i* depends: mii supported: yes vermagic: 2.6.27.7-9-default SMP mod_unload modversions parm: rx_copybreak:Copy breakpoint for copy-only-tiny-frames (int) parm: use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int) parm: debug:Debug verbosity level (0=none, ..., 16=all) (int) # modinfo mii filename: /lib/modules/2.6.27.7-9-default/kernel/drivers/net/mii.ko license: GPL description: MII hardware support library author: Jeff Garzik <jgarzik@pobox.com> srcversion: 16DCEDEE4B5629C222C352D depends: supported: yes vermagic: 2.6.27.7-9-default SMP mod_unload modversions Code:
r8101-1.013.00.tar.bz2 r8168_scripts.tar.bz2 r1000_v1.07.tgz r8168-8.014.00.tar.bz2 |
|
|||
|
Add "or broken" (either physically or "by design") to that list.
The last time I had this problem (same chipset IIRC) in a help thread (in some german linux forum) the reason was "dying hardware".
__________________
“Never attribute to malice that which can be adequately explained by stupidity.” (R.J. Hanlon) |
|
|||
|
New findings...
Well, now I am writing this message from the system with problems... Now this is a standard OpenSUSE 11.1 installation with the driver r8169, detected by the setup process. I got it working just changing by YAST the IPV6 and IPV4 support for just IPV4. Well we have now 3 scenarios: 1. Some times the system start and get the IP by DHCP and them connect to the network and Internet without any problem. Success! 2. Some times the system start and do not detect the network card. 3. Some times the system start get the IP by DHCP and DNS server, ping the eth0 and lo, but do not ping the router or Internet or any other IP/NAME... For scenery 1 (the happy one): Code:
eth0 Link encap:Ethernet HWaddr 00:24:1D:18:0C:DA
inet addr:192.168.0.185 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::224:1dff:fe18:cda/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:68999 errors:0 dropped:1794276295 overruns:0 frame:0
TX packets:41957 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:102337741 (97.5 Mb) TX bytes:3202091 (3.0 Mb)
Interrupt:247 Base address:0xa000
...
# lsmod | grep r8169
r8169 31388 0
mii 6024 1 r8169
# ethtool -i eth0
driver: r8169
version: 2.3LK-NAPI
firmware-version:
bus-info: 0000:08:00.0
For scenery 2 (bad): Nothing!!! The network card does not exist for the system... For scenery 3 (bad): Code:
# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.185: icmp_seq=2 Destination Host Unreachable
From 192.168.0.185 icmp_seq=2 Destination Host Unreachable
From 192.168.0.185 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.0.1 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5038ms
, pipe 2
# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.021 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.014 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.010 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.013 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.011 ms
^C64 bytes from 127.0.0.1: icmp_seq=6 ttl=64 time=0.012 ms
64 bytes from 127.0.0.1: icmp_seq=7 ttl=64 time=0.011 ms
64 bytes from 127.0.0.1: icmp_seq=8 ttl=64 time=0.013 ms
^C
--- 127.0.0.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7001ms
rtt min/avg/max/mdev = 0.010/0.013/0.021/0.003 ms
# ping 192.168.0.185
PING 192.168.0.185 (192.168.0.185) 56(84) bytes of data.
64 bytes from 192.168.0.185: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from 192.168.0.185: icmp_seq=2 ttl=64 time=0.012 ms
64 bytes from 192.168.0.185: icmp_seq=3 ttl=64 time=0.019 ms
64 bytes from 192.168.0.185: icmp_seq=4 ttl=64 time=0.017 ms
^C
--- 192.168.0.185 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 0.012/0.018/0.024/0.004 ms
eth0 Link encap:Ethernet HWaddr 00:24:1D:18:0C:DA
inet addr:192.168.0.185 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:2550136680 overruns:0 frame:0
TX packets:0 errors:0 dropped:46 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:247 Base address:0xc000
...
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
# lsmod | grep r8169
r8169 31388 0
mii 6024 1 r8169
# ethtool eth0
Settings for eth0:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: pumbg
Current message level: 0x00000033 (51)
Link detected: yes
# ethtool -i eth0
driver: r8169
version: 2.3LK-NAPI
firmware-version:
bus-info: 0000:08:00.0
For this 3 scenarios I am just using resources available at the standard installation without other drivers, modules, compilations or kernel adjustments... Well... any direction?? :-) |
|
|||
|
Broken/dying Hardware is the most likely one, what better match for this hypothesis than your described "sometimes works, sometimes not" behaviour, especially in combination with the other scenario "hell, where's my MAC address now?" a few posts earlier.
__________________
“Never attribute to malice that which can be adequately explained by stupidity.” (R.J. Hanlon) |
![]() |
| Bookmarks |
| Tags |
| gigabyte motherboard, internet not connected, network configuration, realtek |
| Thread Tools | |
| Display Modes | |
|
|