I'm running CentOS 5.2 on an ASUS M2NPV-VM motherboard. This motherboard includes an NVIDIA nForce 430 built-in Gigabit MAC (network interface). I've also installed a second PCI network interface card (NC100 Network Everywhere Fast Ethernet 10/100). The PCI-based card was configured as eth0, while the built-in NIC was configured as eth1. The machine is used as my firewall/router, so eth0 is my internal interface, while eth1 is my external interface. I've had some intermittent problems with the built-in (eth1) NIC. When booting the machine and it attempts to bring up the interface, I get the following message: forcedeth device eth1 does not seem to be present, delaying initialization From that time forward, there is no eth1, and so no external network, etc. If I try running /etc/sysconfig/network-scripts/ifup eth1 (from that directory), it results in the same error.
Originally, I was getting this error when installing the operating system on the machine. At that time, I was using a 75' ethernet cable (as I was working on the machine in my office, and the external ethernet jack was in another part of the house). As soon as I moved the machine to its permanent location (which is within 2 feet of the ethernet jack), the problem went away. However, I just updated the kernel (via yum) from 2.6.18-92.1.22.el5 to 2.6.18-128.1.6.el5, and now it fails 9 out of 10 times. I'm not even sure what I can do to debug this. I'm assuming there is some kind of timing problem with the initialization. Is there a configuration parameter I can set to allow more time for the initialization to do what it needs to do, to prevent this error?
I have added a new network card on my Cent OS machine. This is a RTL-8139/8139C/8139C+ card. When the machine boots or I start the network it displays "eth1 does not seem to be present,delaying initialization."I have gone through different posts on the forum with similar problems and have posted output of some of the commandsOutput of lspci is
I have swapped out four known working, different bran network cards. Each one I get the same error as in the subject. If I boot to a Live CD such as CentOs 5.3 LiveCD both Nics are given an IP. This seems to only be happening with my CentOs 5.3 server install.I noticed the CentOS Live CD the Nics were reversed from eth0 to eth1 and eth1 to eth0.
At the moment as of the output of the commands, I am running two identical Nics, since the first one has always worked. I have previously used an rtl8139, 3com c3905-TX, onboard Rhine III based (now disabled) Here are steps I have done to try and figure this out:
Quote:
[root@centos ~]# lspci | grep -i eth 00:0a.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) 00:0e.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86)
Quote:
[root@centos ~]# cat /var/log/dmesg | grep -i eth eth0: VIA Rhine III at 0xee800000, 00:1b:11:bb:17:7d, IRQ 177. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
[code]....
I went through the system-config-network-tui. I copied /etc/sysconfig/network-scripts/ifcfg-eth1 to the ifcfg-eth0 and edited for sanity. and as stated earlier, have swapped out four different nics for eth0, and booted to two different LiveCD's. Both LiveCD's work fine.
i have problem related nici am using a dell inspiron 1545 laptop outputs are following---(1) [root@localhost ~]#lspci |grep -i ethernet 09:00.0 Ethernet Controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
(2) [root@localhost ~]#cat /etc/modprobe.conf alias scsi_hostadapter ahci alias scsi_hostadapter1 usb-storage
I am struggling to install RHEL 5 in one Hp Compaq dc7900 machine. My network is not coming up with a message e1000e device eth0 does not seem to be present. lspci givens following message
I could see /etc/modprobe.conf has a line "alias etho e1000e" present. In fact another machine dc7900, installed with Fedora Core 10, detects the card with e1000e as the module.
I run many 5.2 virtual machines inside of VMWare ESX3.5 I've updated a couple of test VMs from 5.2 to 5.3. The thing that stands out is that during boot time, the sequence gets to this stage:
device-mapper: dm-raid45: intialized v0.2429 Waiting for driver initialization.
Here it takes about 3 times longer than the previous Centos 5.2 (about 9 seconds instead of 3). Whereas inside a physical box the wait in 5.3 is the same as it was in 5.2
Installed Centos 5 on IBM T60P laptop. Intel 82573L Gigabit ethernet controller. Keep getting this erro message, "e1000 device eth0 does not seem to be present, delaying initialization."
64bit Slack doesn't recognize my ethernet device. ifconfig -a show no eth0. It's an onboard nvidia MCP55 ethernet nic. Never had this problem using 32 bit Slack.
When I try to modprobe forcedeth I get the following error:
repeats those two statements 3 times
I just recompiled my kernel with every possible 10/100 ethernet device included in the modules. Still no go.
I recently upgraded mu Fedora 13 to Fedora 14, I decided to add another NIC that I assumed it'll be eth1, when I boot the PC and typed #ifconfig eth0, eth1, lo appears. But when I typed #setup eth1 is not present. Why is that? I remembered doing this in Centos 5.5 but it automatically appears after I added a NIC and boot the pc? what should I do?
I recently setup a new SUSE box for the purposes of acting as an ftp/sftp server. It's currently setup to run ProFTPD 1.3.3.rc3 and mod_sftp/0.9.7. The server has two internal network interfaces eth0 and eth1. eth0 is purely for internal use to accept ftp and ssh. eth1 is outward facing and receives connections from the WAN via SFTP over port 22. The problem I am facing is that after half hour to an hour eth1 stops accepting connections whenever there is no SSH connection present on eth0. I can't figure out why this is happening.
ProFTPD is setup as follows: SocketBindTight directive is on, default server and port are commented out.
[code]...
When the external interface is unreachable the proftpd and proftpd-sftp logs show no record of any connection attempt. I have noticed however if I leave eth0 down eth1 stays contactable without problem. Can anyone give me some pointers on what I can check to find out why this may be happening.
I need to setup two ethernets in my Centos box. OK no problem both ethernet and 1 virtual works perfect. eth0, eth1 and eth1:0. I'm trying to set up diferent routes for eth0 and eth1/eth1:0 I need eth0 has a 192.168.1.1 gateway and eth1/eth1:0 192.168.1.100 gateway.I think I've tried almost every thing but always get one gateway for all the eth.These are my config..
/sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:XX:XX:XX:XX:XX inet addr:192.168.1.168 Bcast:192.168.1.255 Mask:255.255.255.0[code]......
I've decided to toy around with LVM and mdadm this weekend. I can get everything working, and all is well, until I restart. After that, I no longer have any /dev/md0 device, which during the auto mount process, causes an error. I've looked through several HOWTOs, as well as the LVM/mdadm man pages, and I believe I've tracked it down to mdadm's "assemble" that is needed (so that LVM can see the md0 device).
Not exactly sure how to go about having this occur during the boot process to ensure that the LVM mapped drive is available for when fstab is read. In case it helps this is a base install of 10.10 server 64. I have four drives, the first is used for the OS and is not in the RAID array (nor LVM). The second and third are RAID1 (/dev/md0) and there is a volume group associated with /dev/md0. The last is a LVM, but not RAID, and it has its own volume group.
I can't use my line-in/microphone jack. In system-management-sound input tab there is no input device listed, and the input controls are grayed-out. sudo lshw -C sound produced:
description: Audio device product: N10/ICH 7 Family High Definition Audio Controller vendor: Intel Corporation physical id: 1b
I have installed Open SUSE in my DELL server which has 2 broadcom NIC cards, it showing both the NIC cards in Network configuration in YAST ,but it showing as not configured and not connected . Kernel device eth0,wlan0 are not present. In device manager also 2 Broadcom nic cards are detected.
I have installed Linux SuSE 10.3 on a PC (Lenovo Thinkstation A58). However, when I start the computer I get the following error message:
"No valid Host_ID or host-name found."
I then use YaST to set up the network. I get the following error message:
"Unable to configure the network card because the kernel device is not present."
The computer has Windows 7 installed and everything seems to work fine. The LED on the Ethernetplug is blinking when using Windows, but not when using Linux. I guess this means that there is no driver for the Ethernet card (Marvell Yukon 88E8057). I have not found any driver for the card and am considering buying a new one. Which PCI card works with SuSE Linux 10.3?
I just attempted to install to a USB drive, and somehow in the process, GRUB overwrote my Windows 7 bootloader on the internal disk. My work laptop is now booting into a grub recovery whenever my USB key isn't present (with error: no such device and the uuid) - and hangs on a blinking cursor whenever the key is plugged in.I'm not familiar with what my options are for grub rescue, but ls shows (hd0) (hd0,msdos2) (hd0,msdos1) (fd0)
My laptop is encrypted, so I don't have much chance of recovery unless I can get back to the windows bootloader.
I want to install CentOS from netinstall CD, but it doesn't work for wireless connection, because it just looks up for eth0 connection. Well, I connected server to wired USB connection and it's named eth1. I want to use netinstall CD but using eth1 connection. Is there any way for doing it?
So I installed the Unison synch software with sudo apt-get install unison-gtk. When I set up the two directories for synchronization it looks like this: $ unison ssh:\SERVER\pathpath /var/www/path/path/path
I am getting this error in terminal Uncaught exception Gtk.Error("GtkMain.init: initialization failed ml_gtk_init: initialization failed") Fatal error: exception Util.Fatal("Error in getLogch: /home/path/.unison/unison.log: No such file or directory"
I'm working on a kickstart install to automate a lot of monotony doing installs. When i use the kickstart install i get an error on boot saying "File based locking initialization failed" "no volume groups found". Then it proceeds to boot up with no issues and appears to work just fine. Below is the section of my ks.cfg for creating the partitions: %include /tmp/partition.cfg is included where the partition info usually occurs. The user is prompted in the pre script for how large they would like the partitions to be and then the script below creates the included file with partition info
Installed a TP-Link TG-3269 Gigabit card in a machine running OS 11.3 32 bit, when I go into Yast, Network Devices, Network to try configuring the card I get this errormsg: Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details. Couldn't find any mention of the card in dmesg's output, (though the 8139 onboard card is in there) there is some stuff about pci host bridge but I don't know whether they would be relevant or not
The chip on the card says it's rtl8169sc but lspci lists it as being 00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8369 (rev 10) Done some googling and there don't seem be any drivers for a Realtek 8639 and it returns no matches from a search on realtek's site, but there is a driver there for rtl8169sc chips, which I downloaded and installed, no errors when installing it Even after a reboot I still get the same error in Yast's Network Settings screen, lspci still lists it as 8369 and the device isn't listed at all if I run ifconfig
I'm connecting to my CentOS with remote desktop. While trying 'setxkbmap' the following error is occurring:XKB extension not present on :17.0It doen't happen on the console, i.e.when DISPLAY=:0.0
My motherboard uses nVidia's nForce 570 SLI chipset. It has 2 ethernet ports. I've installed RedHat EL4 update 7 (kernel 2.6.9-78.0.13) and used "up2date" to get the latest package updates. With only 8GB RAM, the ethernet ports function properly. If I add another 8GB RAM, total of 16GB, the ethernet ports no longer function properly. They won't initialize.
i have installed centos 5.1 but it won't recognize 2nd nic card (eth1). i was unable to install the driver supplied by the cd. i am using intellinet gigabite pci network card. the network card recognize by centos 5.3 but i need to use centos 5.1. i also tried another intel gigabite adopter but it also won't recognize by centos 5.1.
Looking at my logs note that the eth1 interface falls and rises many times.
..... Jul 30 04:29:42 localhost kernel: e1000e: eth1 NIC Link is Down Jul 30 04:29:44 localhost kernel: e1000e: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
I have configured IPv6 in my main server and I can ping IPv6 address (eg. google). but I want to do the same on my VPS.What do I have to do to add an additional IPv6 IP to my already present VPS (IPv4 configured)?I tried the web, but no complete info of doing so anywhere.
I'm having a problem and despite I have googled a lot cant find the root cause. I have a server with two embedded NICs and centos 5.5 loaded. I need to have one NIC with a fix internal IP address to communicate with the intranet and a second NIC with a fix address from my telephone provider. I know I cant have two different gateways on the net so I configured only the gateway for the second NIC leaving the field empty for the first.
I found that the first NIC is handling all the traffic for both interfaces (eth0 and eth1) and the second NIC is in standby (or doing nothing). This is causing the traffic intended for the second NIC never reach their destination. After a couple days working with the BIOS and other configuration files I tried another way of solve the issue. I put a fix address for the first NIC and another fix address for the second NIC (both in the same subnet) and from a computer pinged successfully both addresses. However if I disconnect the cable for the first NIC both interfaces goes down (eth0 and eth1) and both pings fails. If I disconnect the cable for the second NIC (with the first one connected) both pings still running without any disturbance.
I worked also in a second server with different hardware (different kind of motherboard, different NIC manufacturer, etc.) but the problem is also present in this second server. I was reading about NIC bonding or teaming, but this configuration is not present in the modprobe.conf or in the ifcfg-eth0 files, so I believe the problem is not related with this feature. Do you know what is happening with the NICs and how can I get two really, fully independent NICs?
