i have 5.4 installed on a super-micro server motherboard (has two gigabit ether ports). when i boot while its initializing everything it gets to the "starting eth0" and just stays there?
right before it boots up and says press any key for options i press a key and choose "centos (2.6.18-164.el5)" and it boots up fine but when i choose "centos (2,6,18-164.el5xen)" the problem occurs. and that is the default boot option.
i install kernel rpm after i boot that kernel network not working kernel name : kernel-rt-trace-2.6.24.7-132.el5.centos.i686 [URL] error "Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring."
View 1 Replies View RelatedInstalled 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."
View 3 Replies View RelatedI just finished installing Fedora 12 on a rack mount server. I was modifying the /etc/sysconfig/network-scripts/ifcfg-eth0 file to use a static IP address, but now nothing works. The device does not boot on start up or anything.Currently, ifcfg-eth0 looks like:
Quote:
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none[code].....
The eth0 device does not start on boot; the server does not get the IP address, is not reachable over the network, and will not connect to the internet....
I have 2 network cards eth0 and eth1, for eth0 i set a manual MACADDR in network scripts. Ok so every time i boot, if the cable is plugged in, my eth0 fails to mount or i don't know.. i get this after bood when i type ifoncifg eth0 (eth0: error fetching interface information:Device not found). So i have to unplug the cable when i boot, then plug it in and do a service network restart.
View 5 Replies View RelatedMy network name is eth2 it was changed by some reason and now i got these errors... i installed, reinstalled, re re installed, tried to run the asistant but no luck :/
Code:
* Stopping the Firestarter firewall...
eth0: error fetching interface information: Device not found
eth0: error fetching interface information: Device not found
eth0: error fetching interface information: Device not found
[code]....
im trying to setup eth0 with subdevice eth0.0 and eth0.99 to come up at boot
eth0 is dhcp clint
eth0:0 is static ip
eth0.99 is 802.1q vlan interface
/etc/network/interfaces
Code:
auto lo
[Code]....
This on a Vostro 1220 Laptop w/ Intel 5300 wireless:
A.I have long boot up time.I think it's because of the eth0 network search which I don't use.I have an intel wireless 5300 card running.How can I speed up the boot time, i.e. disable or change the eth0 at boot, the searching?
B:When I restart or shutdown, the screen flashes repeatedly and gets some garbled colors along the top before finally rebooting looks like windows ME or something).This vostro has an intel x4500HD vid chipset in it.
C.How do I get into gnome configuration editor to turn on Metacity compositing? Alt-F2 and run gconf-editor doesn't do it. I don't do compiz, but need compositing.
D.I need to install Chromium Browser as it sync my bookmarks.I have RPMforge enabled btw also...how can I do that? I.e. rpm repo for chromium?
This will help me get off to a running start so I can get up to speed on CentOS..
after a yum update on my CentOS 5.3 I got this error when shutting down eth0 on reboot...
Shutting down interace eth0: Device eth0 has MAC address XXX instead of configured address XXX ignoring [FAILED]
I have just upgraded a CentOS 5.2 box to Centos 5.3
I did have a bridged networking setup for Virtualbox which worked well. eth0 was bridged with br0. br0 boot protocol was DHCP and it sent its DHCP_HOSTNAME to the windows DHCP servers.
since the upgrade the br0 does not get an address but the eth0 does. I found that the scripts in /etc/sysconfig/network-scripts/ifcfg-* are getting rewritten.
I figure I may not need to have a bridge any more so I stripped that out to try to get a simple network setup working. I now just have eth0. I edited /etc/sysconfig/network-scripts/ifcfg-eth0 so that it looked like this,
~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Attansic Technology Corp. L1 Gigabit Ethernet Adapter
DEVICE=eth0
BOOTPROTO=dhcp
[Code].....
why does hal daemon hangs? but if i try the interactive booting and disable the hal upon starting,it will boot up. so maybe i can just disable this every time it boots, how can i do this?
View 2 Replies View RelatedI installed Centos 5.5 yesterday and discovered that the hal daemon was failing to start on boot.
The messages showed that the hal daemon was hanging because nss_ldap could not connect to the ldap server. It eventually failed and the system came up multiuser without it.
When I started looking into the problem I discovered that hald was being started quite early in the boot process. It's sequence number was 26 (if I remember correctly). This was even before nscd.
If I chkconfiged it off and booted, I could start it successfully once the system was up.
I changed the sequence number to 98 and bring it up relatively close to the end of the boot process.
This works and it starts normally.
Is starting it as early as 26 in the boot process done for a reason? It seems to me that it should definitely not be started before nscd. Does it matter that I moved it to the end of the boot process?
I've looked today on my logs /var/log/message and I find device eth0 entered promiscuous mode I don't remember putting eth0 in promiscuous mode I'm connected to the net thru a router how do i turn that off ?
View 1 Replies View RelatedI am trying to boot the CentOS live cd off of usb. I used unetbootin to put CentOS on my 8gb usb drive after downloading the DVD iso. During boot it loads the image and continues until it reaches this point.
>Linux agpgart interface v0.101 (c) Dave Jones
>Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
After this it hangs and won't continue. I am using a Compaq evo n800w and the bios is just updated to the latest version.
System has a boot partition on raid1. The root filesystem is on RAID1/LVM.During the boot process, it gets to here:
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel(R) Celeron(R) CPU E1200 @ 1.60GHz stepping 0d
[code]...
most of the time, it will not reboot. I can cycle power, and, eventually, it does boot. So, hardware issue perhaps? Something else?What can I do, or add to the configuration to help debug this and figure out why? For boot options, I have tried noapic, apm=off, noht, nomce, nousb, nousbstorage, and none of those helped. As the machine is remote, to mess with console stuff, I have to get a KVM over IP hooked up, which I can do.
Let me start off with the usual: I'm a linux newbie but am doing pretty good so far with google by my side. I've come across a problem I cant seem to find an answer to:
I just got a CyberPower 685 AVR UPS. I Installed their power panel software and it works great in CentOS 5.4. When I reboot, the system hangs right after the "Red Hat Nash 5.6..... Starting" message. I've left it for 20 mins so far and it's still hanging. If I unplug the USB data/shutdown cable, within about 10 seconds it starts detecting hard drives and continues booting...
Ive even returned the UPS for another to see if it was bad, and it still is giving me problems.
Reboot and select proper boot device or insert boot media in selected boot device and press a key. I got this error after: Reducing my Windows 7 partition by about 100gb. Creating a new partition (100gb) and copying my Ubuntu partition (10gb) to the new partition. After it was copied, and pasted, the original partition was deleted. I now had two partitions a new 100gb Ubuntu partition and a 600gb (or so) Windows 7 partition.
All of this was done using a bootable USB with Ubuntu 10.10 and GParted partition editor. Now when I boot I get the "Reboot and select proper boot device or insert boot media in selected boot device and press a key." error.
I had no issue with F11 until yesterday. After I installed the security updates and rebooted F11, a message showed there forever " r8169 eth0 link up" and nothing happened
View 1 Replies View RelatedI'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
I have to do a project on network security.For that i have to capture the packets from the device. I installed libpcap tool in ubuntu. If I give ifconfig -a it lists out eth0, wlan0, lo. I am able to connect to the internet via eth0. But when I give
#include <stdio.h>
#include <pcap.h>
int main()
{
char *dev, errbuf[PCAP_ERRBUF_SIZE];
[Code]...
It says device is null. I'm not able to run sniffex.c program also. All I want to do is to capture the live network level packets and analyse them.
While i am configuring network setting on backtrack4. i was running my backtrack on vmware workstation and NAT is bridged to physical mem like it was said on the tutorial that watched. i typed ifconfig eth0 up, and hit enter, as well as dhclient eth0 up, but resulted in different output. it says "no such device" is written and i would like to configre this problem.
View 2 Replies View RelatedI'm having a consistent problem with instances on Amazon EC2, which a lot of searching including here has resulted in no solution.During boot I see the following message on the console (or "System Log" in the Amazon console):Code:Mounting local filesystems: mount: /dev/sdg already mounted or /apps busy(I'll append a extract from the full log below).Once I log into the instance, I can access the filesystem so it's mounted somehow but I can't figure out what's going on:
Code:
# df -k /apps
Filesystem 1K-blocks Used Available Use% Mounted on
[code]....
when I first installed it on my IBM thinkpad, the eth0 was working correctly. I had someone try to install the network card for me, and something was changed to where now the wired connection is displaying "device not managed".
View 2 Replies View RelatedI am trying to perform VM cloning using KVM in a centos 5.6 machines. I copy the memory contents of a running vm to an external state file and try to use that to start another VM in a different machine. While starting the cloned VM I provide a different mac address but once it resumes it has the old one . I tried changing the mac address in ifcfg-eth0 but I get the error: Device eth0 has a mac address xx:xx instead of configured xx:xx.Ignoring .
Is there some way to change the ip/mac of the cloned vm without the need to restart the VM ( Then the purpose of cloning will be defeated). Thanks a lot for the info.
When i wan to activate device in network configuration, it pop out with "CANNOT ACTIVATE NETWORK DEVICE ETH0". There is a sentence after this also : "rlt8129 device eth0 does not seem to be present, delaying initialization."
View 14 Replies View Relatedsolve this error "3c501 device eth0 does not seem to be present, delaying initialization".
View 3 Replies View RelatedI 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 am running a CentOS 5.6 as a Virtual Machine on my Laptop. And, to connect to internet I am using a datacard (usb modem) device (Tata Photon +).
Now, internet is working well on my VM through interface ppp0
The problem is that when I start my interface eth0, internet (running through ppp0) stops.
Quote:
[root@kick ~]# ip route show
172.29.242.9 dev ppp0 proto kernel scope link src 14.99.211.189
default dev ppp0 scope link
[root@kick ~]# ip addr sh
1: lo: <LOOPBACK> mtu 16436 qdisc noop
[Code]....
The server comes up after rebooting and after setting the hostname it starts setting up logical volume management. It says that 2 logical volume(s) in volume group "VolGroupOO" now active But then it starts to check the file system and errors with fsck.ext3: Device or resource busy while trying to open /dev/sdb1 [failed]
***An error occured during the file system check
***Droppping you to a shell, the system will reboot when you leave the shell
Give root password for maintenace
After I log in with the root I get the message mesg: error tty device is not owned by group 'tty' Can the forum tell me how to troubleshoot this issue so I can boot back up again? I have 2 harddrives in this server and only 1 drive was detected when I first installed CentOS. The error first appeared when I mounted the 2nd drive at the mount point /UserGeneratedData. drive was formatted with ext3 before mounting and did not have any data on it I don't want any software RAID if thats what seems to be going on with "VolGroup00"
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.
View 4 Replies View Related