Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently installed openSUSE without any big issue except that I have no network running despite a working hardware. I first got the error during the installation, then no way to fix the problem. Note that the system log confirms a timeout on eth1.
For information I have no network problem on Windows and I previously installed openSUSE 11.0 with the VirtualBox (under WinXP) without facing such problem on the same machine.
Here are some data which maybe could help to find some hints. Any help is greatly appreciated!
Boot Log File
Setting up (localfs) network interfaces:
lo
lo IP address: 127.0.0.1/8
IP address: 127.0.0.2/8
done eth1 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
eth1 Starting DHCP4 client. . . . <notice>checkproc: /usr/bin/kdm 2228
. . . .
eth1 DHCP4 continues in background
waiting
Waiting for mandatory devices: eth1 __NSC__
11 10 8 7 6 4 3 2 0
eth1 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
eth1 DHCP4 client (dhcpcd) is running
eth1 . . . but is still waiting for data
waiting
eth1 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . . .failed
# dmesg
vendor=8086 device=2448
tifm_7xx1 0000:06:06.3: PCI INT A -> GSI 22 (level, low) -> IRQ 22
8139cp 0000:06:07.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp 0000:06:07.0: Try the "8139too" driver instead.
sdhci-pci 0000:06:06.4: SDHCI controller found [104c:8034] (rev 0)
vendor=8086 device=2448
sdhci-pci 0000:06:06.4: PCI INT A -> GSI 22 (level, low) -> IRQ 22
mmc0: SDHCI controller on PCI [0000:06:06.4] using PIO
mmc1: SDHCI controller on PCI [0000:06:06.4] using PIO
mmc2: SDHCI controller on PCI [0000:06:06.4] using PIO
8139too Fast Ethernet driver 0.9.28
vendor=8086 device=2448
8139too 0000:06:07.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
eth1: RealTek RTL8139 at 0xf8a5a400, 00:0a:e4:dd:29:bf, IRQ 20
eth1: Identified 8139 chip type 'RTL-8100B/8139D'
# ifconfig -a
eth1 Link encap:Ethernet HWaddr 00:0A:E4:DD:29:BF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:155 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4990 (4.8 Kb) TX bytes:53010 (51.7 Kb)
Interrupt:20 Base address:0xa400
Under Windows, which eth port is it using, eth0 or eth1? Under linux have you tried making it use eth0 instead of 1?
Does 'lsmod' show the driver loaded?
Don't know if this helps, but I stumbled across a similar problem some time ago with my ISP dhcp implementation:
It seemed that only Windows and some Slackware variants were able to receive an IP address through dhcp. RedHat/Centos variants, Debian/Ubuntu/Knoppix even BSDs all would fail retrieving an IP address.
However, in my case the IP address had a high lease time (possibly forever) so I worked around this issue by using the IP data from a working Windows machine (or Slackware) and setting it up as a fixed IP address. Don't know if this was actually an ISP dhcp implementation issue, but all OSes would work retrieving an IP address from a eg. router so I assumed it to be ISP related.
Also, note that at the time I was also using a Realtek RTL-8139 adapter
If you disconnect the ethernet cable and assign a static IP, does the interface come up? If yes, then you can focus your diagnosis on the DHCP aspect. If no, then it would seem to be a driver issue. There is more than one Realtek driver. The line that says
Code:
8139cp 0000:06:07.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
would suggest that you are using the wrong one.
--- rod.
Well, one thing that seems odd is that the driver is loading as eth1 and not eth0. Also, there seems to be some remnant of the 8139cp driver, as evidenced by:
Code:
Driver Info #1:
Driver Status: 8139cp is not active
Driver Activation Cmd: "modprobe 8139cp"
What are the relevant lines in your modprobe.conf? I'm not sure how Suse does ethernet configuration, but if there is something like ifcfg.eth1 or ifcfg.eth0, what is in those? In network startup scripts that I am familiar with, the numeric subscript is an iterator in setting up the devices. I'm not sure how it copes with a 'missing' device number.
Also, what happens if you try to assign a static IP (ifcfg.eth0/1)? Does the device become active?
--- rod.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.