[solved] stable network card name eth0 eth1

Hello, I'm new to Arch Linux. I have two Ethernet interface adapters, let's distinguish them by their MAC addresses MAC0 and MAC1. Relationship between MAC addresses and 'eth' unit numbers may change after reboot. Sometimes
MAC0~eth0
MAC1~eth1
sometimes
MAC0~eth1
MAC1~eth0
When they swap, I should change 'rc.conf' settings (IP addresses and such) or keep rebooting until they swap back. I want to name devices in 'rc.conf' by their MAC addresses, is it possible?
Last edited by beroal (2009-06-14 01:47:57)

Had this issue recently. The best solution is to create a rule in udev which handles the naming task. See http://wiki.archlinux.org/index.php/Udev. The general solution didn't solve my problem. The udev rule has been effective so far. I renamed to lan0 and lan1. If you do rename remember to change your configs that refer to the network cards.
*edit: just a little late, typing with 1 hand...*
Last edited by stryder (2009-06-07 17:34:59)

Similar Messages

Network card name switching.

Hello. I have a problem with NICs switching names. I followed Wiki and added 10-network.rules in /etc/udev/rules.d but it seems there is no effect.
/etc/udev/rules.d/10-network.rules
SUBSYSTEM=="net", ATTR{address}=="11:11:11:11:11:11", name="eth0"
SUBSYSTEM=="net", ATTR{address}=="00:11:11:11:11:11", name="eth1"
SUBSYSTEM=="net", ATTR{address}=="00:00:11:11:11:11", name="eth2"
MAC addresses have been hidden but the one in my config are correct.
I have 1 NIC onboard (eth0) and one network card with dual port (eth1,eth2).
Also what is the difference beteen ATTR{address} and ATTRS{address}?
Wiki mentions something about:
With a recent version of udev, this problem should be solved automatically thanks to the /usr/lib/udev/write_net_rules program which runs the 75-persistent-net-generator.rules script which produces a 70-persistent-net.rules.
I can't find any of those files.
Last edited by verb0ss (2012-06-14 17:09:16)

alphaniner wrote:
In my 10-network.rules, "name" is in all caps. Maybe that's your problem.
SUBSYSTEM=="net", ATTR{address}=="##:##:##:##:##:##", NAME="eth0"
SUBSYSTEM=="net", ATTR{address}=="##:##:##:##:##:##", NAME="eth1"
SUBSYSTEM=="net", ATTR{address}=="##:##:##:##:##:##", NAME="eth2"
SUBSYSTEM=="net", ATTR{address}=="##:##:##:##:##:##", NAME="eth3"
I haven't noticed such an obvious thing. I have corrected the config now and i will give it a few days to test it. Thx a lot mate.

[SOLVED] Wireless network card

I have got it to work, but it lost the connection all the time and then it have the connection again.
networkmanager and wpa_supplicant I have look into wireless how to arch and edit some files but it did not work 100%
Last edited by amandus (2012-11-24 17:02:11)

I had problem before with disconnecting but that was becouse I had netcfg and network manager enabled.Remowing netcfg worked for me.On my new Arch installation I use netcfg and wpa_supplicant without any problems.First time I didn't read the wiki very carefully and it coused problem .

The name of network card is changing

Hello,
I have network card and wifi card in my notebook. I have updated udev, kernel, firefox etc. Since time the name of network card is changing. Sometimes lan is eth1 and wlan is eth0 and sometimes lan is eth0 and wlan is eth1.
It s problem for me. Becouse I dont use dhcp.
Any sugestions.

I gave this a shot and I'm still haveing the same problems.
This is my /etc/udev/rules.d/netdevices.rules:
KERNEL="eth*", SYSFS{address}="00:0d:56:b3:52:fc", NAME="eth0"
KERNEL="eth*", SYSFS{address}="00:0e:35:40:91:77", NAME="eth1"
Output from ifconfig (just to show names and macs...
eth0 Link encap:Ethernet HWaddr 00:0E:35:40:91:77
eth1 Link encap:Ethernet HWaddr 00:0D:56:B3:52:FC
It seems that udev just ignores the custom rules and its potluck on whether it comes up with the right names or not. I have another custom rule file in there as well which changes various usb cameras and stick drives into more meaning full names other then sd?1, those rules seem to be ignored as well.
[edit]Solved!
The following netdevices.rules works:
KERNEL=="eth*", SYSFS{address}=="00:0d:56:b3:52:fc", NAME="eth0"
KERNEL=="eth*", SYSFS{address}=="00:0e:35:40:91:77", NAME="eth1"
It seems that you have to use "==" in comparison operations. Did this used to be the case? I don't remember having to use them before and most examples I see use a "=" for both comparison and assignment. Did they change the rules syntax for the new version or maybe just correct an error that allowed "=" to work as "=="?
[/edit]
andy

How to swap eth0 - eth1 with testingudev rules[SOLVED

Hi,
I want to use the udev in testing because my ML-1710P works just out of the box. Of course there is one problem ... I have two network cards and they are recognized by kernel as eth0 the one that uses 8139too (a Realtek I belive) and as eth1 the one that uses tulip. I need to swap their names because I use the tulip one for internet (my ISP uses MAC address for validation)
Previously I had in /etc/modprobe.conf
alias eth0 tulip
alias eth1 8139too
I already tried
KERNEL="eth*", SYSFS{address}="xx-xx-xx-xx-xx-xx", NAME="eth1"
KERNEL="eth*", SYSFS{address}="xx-xx-xx-xx-xx-xx", NAME="eth0"
in a file /etc/udev/rules.d/00_my.rules with correct MAC address (and lines order swapped also), but it won't work.
Any ideea how to do this?
PS: I have MOD_AUTOLOAD="yes" in /etc/rc.conf

I would add the modules to the modules section in rc.conf, in the order you need them to be loaded. It does not change the autoload function, but this modules are loaded just before autoloader starts. So here is a good point to touch the system. In the end, it does what your old modprobe.conf entries did.
The first one will allways be eth0 etc.

[SOLVED] Need to manually toggle rc.d/network for network card to work

I installed (or actually re-installed) Arch yesterday and have an unusual problem. After boot, I don't have internet connection and I think that the network card isn't active either because i can't see light in my switch's panel.
I have managed to get the connection to work but the procedure is pretty strange.
There's a line "interface=eth1" in my /etc/rc.conf. I change it to "interface=eth0" and execute "/etc/rc.d/network restart". For some reason it prints "RTNETLINK answers: File exists" at this point.
Now there's no internet connection nor activity in switch's panel. I change "interface=eth1" back to /etc/rc.conf and execute "/etc/rc.d/network restart". Now i can connect to internet and there's a green light in switch's panel.
According to lspci my two network cards are named "NVidia Corporation nForce2 Ethernet Controller (rev a1)"(integrated into motherboard) and "Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)."
I already thought that maybe they are just loading in different orders at boot so I added their modules into rc.conf but it didn't do the trick. Googling about that RTNETLINK thing gave some results, but if understood them correctly, they are doing something similar what I have been doing.
Last edited by mylvari (2011-10-28 08:39:52)

I don't know if this card is Realtek based, but wiki's advice for Realtek cards worked. https://wiki.archlinux.org/index.php/Ne … _WOL_issue

[SOLVED] Lost MAC address on network card

It seems that my wired ethernet card has lost its MAC address. Some information/output:
# lspci|grep Ethernet
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller
The card uses the sky2 kernel module
# dmesg|grep sky2
sky2 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
sky2 0000:02:00.0: setting latency timer to 64
sky2 0000:02:00.0: v1.22 addr 0xf7dfc000 irq 16 Yukon-2 EC Ultra rev 2
sky2 eth0: addr 00:00:00:00:00:00
Adding a line
#ifconfig eth0 hw ether <random-address-here>
to the startup-scripts makes it possible to use the nic, but it seems like a very temporary solution.
I don't know what can have caused this. Maybe the winter cold here in Norway erased some part of the nic's ROM?
- Does anybody have any idea how I can remedy this?
- Do I have to send the laptop in for repair to get it restored?
Last edited by kapelrud (2008-12-05 16:35:54)

iBertus wrote:I suppose a driver bug could have corrupted the ROM on the network card. Do you have a Windows install that you can boot into to see if the card is working correctly with those drivers?
Using "ipconfig /all" on windows showed the same zeroed mac address, so I guess the problem isn't (wasn't) linux-specific.
I left the pc in my locker at school last night and when I started it up again this morning the mac had mysteriously returned! Maybe the university leprechaun was bored yesterday.
So I guess the problem is solved, for now... Thanks anyway!

What API i can see network card driver name

Dear all
in java i/o evirnment what API I can use to call current machine network card driver name?

Well the first step for you is to look through your Windows documentation to see what the library call is to get the information you want. Can you find that and post what you find, and post the full signature of that library call (ie, arguments and return type)?
In other words, here's what you should do: Write a simple C program that gets just the information you are looking for. How that works is outside the scope of JNI, so it's outside the scope of this forum, but once you get that working, post some info about it and I'll explain how to get that linked in with JNI. The good news is, it's easy to do.

[SOLVED] Network interface name keeps changing

My network interface name keeps changing between wlp2s0 and wlan0. This is a real pain, since I never know what name will be generated at boot. Most of the time it's called wlp2s0, so this is what netctl is set up to handle by itself. At boots were wlan0 is generated I have to connect manually.
I've tried making the name static by adding a rule to the /etc/udev/rules.d/10-network.rules. The rule i added was:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="48:5d:60:7e:64:e9", NAME="wlp2s0"
Wlp2s0 is generated at boot alright, but I still have to connect manually with this solution. As if the "new" wlp2s0 is not recognized as the old one (same MAC). What gives?
This is on an Asus Eee 1001PXD, with the Qualcomm Atheros AR9285.
Last edited by madr (2013-05-18 20:09:34)

I've now been able to replicate the issue, and run the command:
journalctl -b
I did find the output:
mai 18 02:30:02 <hostname> systemd-udevd[126]: error changing net interface name wlan0 to wlp2s0: Device or resource busy
I haven't been able to process the whole output yet (I'll continue tomorrow if necessary), but I've found some things that I hope will clearify things. I get similar outputs to the following a lot throughout:
mai 18 02:30:03 <hostname> dhcpcd[237]: wlan0: carrier lost
mai 18 02:30:03 <hostname> dhcpcd[237]: wlan0: waiting for carrier
mai 18 02:30:04 <hostname> systemd[1]: [email protected]: control process exited, code=exited status=1
mai 18 02:30:04 <hostname> systemd[1]: Failed to start Automatic wireless network connection using netctl profiles.
mai 18 02:30:04 <hostname> systemd[1]: Unit [email protected] entered failed state.
mai 18 02:30:04 <hostname> systemd[1]: Starting Network.
mai 18 02:30:04 <hostname> systemd[1]: Reached target Network.
EDIT:
I see now that this is later in time, so that's not so strange after all. I'll look some more.
EDIT2:
The error code that a name change i impossible is the first time the term 'wlan0' occurs in the log. However there's a line much earlier that talks about wlp2s0:
mai 18 02:29:59 <hostname> systemd[1]: Expecting device sys-subsystem-net-devices-wlp2s0.device...
But as I said, if this information doesn't help, I'll have a closer look at the output tomorrow. Getting late here in Norway now.
Last edited by madr (2013-05-18 01:20:50)

Assignment of network cards switches each boot (bizarre).

I'm working from a dell inspiron laptop which has both an ethernet port and a wifi card, which are registered as eth0 and eth1. I have no problems configuring rc.conf and related etcs to get the wireless card to work (no driver problems or anything), but they switch names each boot. Has anyone had this problem/ know why it would happen? I can confirm that all I need to do in order to get network running is switch all references of eth0 to eth1 (or eth1 to eth0) and /etc/rc.d/network restart in order to get online (as I am right now).

This particular link to our wiki might help you: Mixed Up Devices, Sound/Network Cards Changing Order Each Boot
Last edited by Cerebral (2007-06-05 01:17:58)

Two network cards configuration

Hi
I have problem with my network - I have two network cards and it seems they can't live both but I need them both so:
1st card (rtl8139) is connected to cable modem and gets ip by DHCP (eth0="dhcp" in rc.conf)
2nd card (nv forcedeth) is connected to router and gets ip by DHCP too (eth1="dhcp")
When I start them both -> 1st and 2nd card gets good IP by DHCP but when I want to ping google.com for example packet is lost.
What I want ? I want to use my eth0 (1st card) for internet and my 2nd card for local network.
##EDIT##
My resolv.conf is 192.168.1.1 but I need DNS from 1st interface -> how to do this?
Last edited by cpu (2007-02-22 22:46:09)

Messy setup IMO, but anyway....
Your faulty resolv.conf is the reason you can't ping google. Edit it manually as required, and then use the -R flag in /etc/conf.d/dhcpcd to prevent it being overwritten. DHCP on both interfaces will probably cause routing issues as well, in which case you will need the -G flag.

Xennet error, when tried to add new network card

Hi,
I got an error when I tried to create new virtual network thru VM manager,
I have add a new virtual network card thru VM manager in the same Xen bridge "xenbr0" , then i reboot the virtual machine, but when i tried to activate this network I got the below error:
cannot activate network device
xennet device eth1 does not seem to be present, delaying initialization.
ifconfig in the virtual machine:
dev13248 Link encap:Ethernet HWaddr 00:16:3E:0B:DD:E4
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)
eth0 Link encap:Ethernet HWaddr 00:16:3E:5A:3E:6E
inet addr:192.168.2.102 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::216:3eff:fe5a:3e6e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:204 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:47253 (46.1 KiB) TX bytes:5623 (5.4 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1045 errors:0 dropped:0 overruns:0 frame:0
TX packets:1045 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1458998 (1.3 MiB) TX bytes:1458998 (1.3 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
ifconfig in the VM server:
eth0 Link encap:Ethernet HWaddr 00:1C:C4:46:AF:3D
inet addr:192.168.2.101 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13177 (12.8 KiB) TX bytes:17612 (17.1 KiB)
eth1 Link encap:Ethernet HWaddr 00:1C:C4:46:AF:3E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:2052 (2.0 KiB)
eth2 Link encap:Ethernet HWaddr 00:1C:C4:A6:B8:0E
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth3 Link encap:Ethernet HWaddr 00:1C:C4:A6:B8:10
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:127 errors:0 dropped:0 overruns:0 frame:0
TX packets:127 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11984 (11.7 KiB) TX bytes:11984 (11.7 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:127 errors:0 dropped:0 overruns:0 frame:0
TX packets:92 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14405 (14.0 KiB) TX bytes:17422 (17.0 KiB)
Interrupt:21
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST NOARP 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:23
peth2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST NOARP 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
Interrupt:16 Memory:f8000000-f8011100
peth3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST NOARP 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:23 Memory:fa000000-fa011100
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:98 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:17612 (17.1 KiB) TX bytes:13177 (12.8 KiB)
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2052 (2.0 KiB) TX bytes:0 (0.0 b)
vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2236 (2.1 KiB) TX bytes:0 (0.0 b)
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1968 (1.9 KiB) TX bytes:0 (0.0 b)
xenbr2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Don't inject the Windows 7 version of the driver into your WinPE image. Depending on what version of ADK you are using determines what version of the driver you will inject into WinPE. If you are using MDT 2013 with ADK 8.1 you are using WinPE 5.0/5.1
which is basically Windows 8.1. Make a selection profile explicitly for your WinPE drivers to inject. Only include the drivers you want in the WinPE image. And match the architecture of the network and storage drivers (Windows 8.1 versions).
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

OEL6.1 in VM manager does not see network card

I installed OL6.1 as a guest machine in VM manager. I started the install process and when I got to the network configuration it would not let me click on "configure network", it was greyed out. I thought that was a little bit odd but I just thought that I would configure it later. Once I got to the desktop of OL6.1 i checked for the eth0 settings but there was no eth0 at all. The OL6.1 did not even know a network card existed, but I tried to add it manually and still it did not see anything and would not connect to the internet. Has anyone seen this problem before? Thanks.

I will try to answer to the best of my knowledge your questions but I am a bit new at this. I downloaded the OEL 6.1iso media from Oracle site, I then imported it into the resources section in VM manager 2.1.
I then used the create new Virtual Machine and selected the server pool.
I selected the ISO file with OEL 6.1.
I gave it a name, memory size, console password.
Below that I can see the Virtual Network Interface is selected and it shows Bridge xenbr0.
It is showing Fully Virtualized machine not paravirtualized mode. As far as I know I did not install in Xen HVM or with PV drivers.
That is about all I did. Then I started the machine and when through the install process but it did not see the virtual network device.

Network Card Installation problem

Hi All,
I have HCL LX INIFINITY POWERLITE 6010 G1 laptop which Marvel Yukon 88E8053 PCI-E Gigabit Ethernet Controller . I tried lot of time to install the driver of it on Sun Solaris but I am not able to install it. I have done add_drv -i and give device id and vendor id . Still gives error softwares is partially install but not able to connect hardware. This lan driver is installed on Windows and Linux . Can anybody help me to sort out my problem or some pkg to download .
Thanks in advance.

I don't think your network card is Solaris compatible. A good stable choice is 3C905 by 3Com and Intel eepro100.
2) I have got a no name brand network card with
Realtek RTL8029 chip. At the begining of the
installation, the hardware detection software does
detect the card and assign resources to it. Later on
during the installation, the program ask me what IP
address to assign to the system, so I enter an IP
address. AS soon as, I click OK. I got a messange
like the IP address can not be assigned to the network
card. Does this mean my network card is not
compatible?Chetan Bhargava
ASA Computers inc.

Problems with my network card..

I have just installed arch on my new desktop computer, everything seems fine after a base install,
Now, the command $ ifconfig, displays lo and eth0, recognizes the hardware name and all sorts, but for some reason dhcpcd always fails to run (times out) on eth0,.
The device works fine under fedora (temporary solution), but I was wondering how I would go about making my network card work under arch.
lspci
01.03.0Ethernet controller: Marvell Tech ltd. 88E8001 Gigabit Ethernet controller (rev 14)
Any ideas?

I thought I could get by using Gentoo, but no.... so Im here to get this sorted...
#rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_GB.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Pacific"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
MODULES=(sk98lin skge slhc snd-mixer-oss snd-pcm-oss snd-seq-oss snd-seq-device snd-seq-midi-event snd-seq snd-hwdep snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-hda-intel soundcore snd-usb-audio snd-usb-lib)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
HOSTNAME="dreamy"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles
#NET_PROFILES=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng network netfs crond hal alsa gdm)
# End of file
#lscpi
00:00.0 Host bridge: Intel Corporation 82946GZ/PL/GL Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82946GZ/PL/GL PCI Express Root Port (rev 02)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller IDE (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0400 (rev a1)
02:03.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 14)
#dmesg | grep Ethernet
eth0: Marvell Yukon 88E8001 Gigabit Ethernet Controller

[solved] stable network card name eth0 eth1

Similar Messages

Maybe you are looking for