CentOS 5 Networking :: Eth0 Now Broken After Last Kernel Update
Nov 23, 2010
I am currently working to get to a stable dual boot Win7/CentOS 5.5 configuration on a Dell Latitude E6510 with the Intel 82577LM chipset. I haven't gotten the Centrino N WiFI chipset working yet, but the Eth0 device was working just fine.However, yesterday I did a system update. I did not pay close attention, but I believe the update did mention networking, because I thought it might help me get my wireless going. Now, Eth0 fails with the message, "Determining IP information for eth0... failed; no link present. Check cable?" It does this at boot up and if we try reactivating it once the system is up. We have tried unstalling and re-installing the driver.The Window 7 boot sees the adapter and runs just fine. I was at a different site location yesterday when everything was working, but my co-workers and I can't help but think it might be related to the update yesterday, since everything worked prior to the update and Windoze 7 works fine with the adapter.
I have not been able to mount my NTFS harddrive on the CentOS side, despite installing fuse, and I don't have wireless, which makes it difficult to get access to new drivers. I also have a FAT32 partition that would be great to share between the boots for passing info, but I haven't found a way to mount a FAT32 partition in CentOS.
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."
I just upgraded the kernel on my Ubuntu laptop from 2.6.32-24-generic to 2.6.32-25-generic (using the update manager under gnome). After the update, the wireless network controller shows up as UNCLAIMED when I do lshw -C network.When I try to install the driver with the commands sudo modprobe lib80211 sudo insmod wl.ko
i get this error message: insmod: error inserting 'wl.ko': -1 Invalid module format
I have compiled the driver using the 2.6.32-24 kernel. Do I have to re-compile with the new kernel?I'm a unix user, but not a kernel hacker, so I'm wondering if I will run into problems every time I get a kernel update? Or is this problem an exception?
So I know I should have known better then to turn my updates back on after the 15 and 16 kernel updates crashed ubuntu and grub but I did anyway and once again after a new kernel gets installed I'm stuck at the grub sh prompt.
Been down the road before... tried using linux /boot/vml....... root=/dev/sda1 loop=/ubuntu/disks/root.disk ro When I use the 16 or 17 kernel I get an error stating "invalid imaginary number"...
So I use the 14 kernal and enter initrd /boot/initrd..... boot
And it boots like it did the last time this crashed. I went to the terminal and entered sudo apt-get install grub 2 sudo update-grub2
And then rebooted like I did last time expecting the problem to be fixed and at least be able to boot up the 14-generic. It didn't fixed this time. So now what do I do to fix grub and what do I do about having 2 unbootable kernals??
After updating to version 2.6.31-20-generic, my desktop computer with an ATi HD4850 graphics card, using the fglrx driver, now won't boot to X. It goes through the boot process and displays the splash screen, but after that there is nothing on the screen. Choosing an older kernel version from GRUB doesn't make a difference. I don't even know how to diagnose the problem properly. I can boot into recovery mode and get to the command line, however, starting x from there only leaves me with a blank screen.
so the source of the problem is that I had installed the catalyst driver from amd.com, which needs to be reinstalled with every kernel update. I didn't know this in advance, so now I'd like a way to revert back to fglrx from the repos. Sadly, the community docs only seem to cover the graphical way of doing this, which is kind of useless to me at the moment.The ATi driver docs gave me a way to uninstall the catalyst driver using only the command line. So now I've booted back into Ubuntu and selected to install the fglrx driver from System → Hardware Drivers. However, now when I boot up, I get the message: "(EE) Unable to initialize PCS database
Ubuntu 10.10 latest kernel 2.6.35-28.49 update is broken. update just stalls when it gets to this.Quote:
Sub-process /usr/bin/dpkg returned an error code (1)...generating grub.cfg I have tried the following to no avail..Quote: sudo apt-get install -f sudo dpkg --configure -a sudo apt-get update && sudo apt-get upgrade
I use Arch Linux and the kernel got upgraded, and it broke VirtualBox. It says to run "/etc/init.d/vboxdrv setup", but such a file does not exist. The Arch Wiki says "/etc/rc.d/rc.vboxdrv setup", but that doesn't exist either. What should I do?
And is it possible to write a script that runs on startup that automatically fixes VirtualBox whenever the kernel is upgraded?
The kernel-PAE-2.6.30.5-43 upgrade will not boot on my Dell 1545 notebook. The initialization stops and the systems freezes right at the point that the login prompt should appear. I do not have invidia drivers. I have Intel video drivers. Also there is a loud 'pop' in the sound system early in the initialization sequence. For the time being, I have removed the 2.6.30.5-43 upgrade via yum.
I was doing a kernel update and can no longer boot into 11.3. I am dual booting with XP. I get Grub screen but no longer see Suse as a boot option, only Windows. I have tried to reinstall, but for some reason I can't get it to boot with DVD. So, is there a way that I can repair my computer without doing a reinstall?
I tried to run some virtual machine using Virtual Machine Manager but the guest OS (windows server 2003) was not able to "see" the rest of my network. I believe VMM did some NAT-ing (192.168.122.x subnet) so i'm not able to "see" my network. I tried various network setting in VMM but couldnt get it to pull my network IP (192.168.1.x subnet).So i installed VirtualBox as a work around because i know VB work when i tried it on my windows machine. I ran into some issue getting VB to run, i think it was that i need to compile the kernel to "optimize" it for VB. I am fairly new to linux so that the impression that i get when i research for the fix to get VB working. In some of the forum post people suggest few things and it seem to me like it to compile the kernel. After a few hours of working i finally got it to compile but the computer crashed during compilation.
I am guess what happened is that i was trying to optimize the kernel for VB but the version of kernel i was using (2.6.18-164.6.1.el5xen) is already optimized for xen (VMM) so it crashed. I am looking to restore or recompile the 2.6.18-164.6.1.el5xen kernel. I am not sure if this is the right thing to do to fix it. With my limited knowledge of linux that all i can think of.
Initially installed 5.3 on a 64-bit platform and was able to compile just fine. Foolhardily updated to 5.5. Somewhere in that process I lost the ability to compile even the simplest "hello, world" C program.
$ gcc hello.c In file included from /usr/include/_G_config.h:44, from /usr/include/libio.h:32, from /usr/include/stdio.h:72, from hello.c:1:
I have a hardware device with two ethernet ports, eth0 and eth1 running Centos 5. Basically my goal is to forward packets from eth0->eth1 and eth1->eth0 as well as get a copy of these packets for analysis. If I set IP routing to do the forwarding then I won't get a copy of the packets for analysis.
I'm trying to install a BCM 4312 wireless driver following the Centos howto. Howtos>Laptops>Witeless>Broadcom
On step 3, compiling ... module.I get No rule to make target `build' Stop.When I go to the /lib/modules/2.6.18.194.3.1.el5 directory, the Build file link is broken.If i go to the link source /usr/src/kernels/2.6 ...x86_64 does not exist. The /kernels folder is empty.I think I need to reinstall the identified kernel in that directory and reestablish a link to it. but am not savy enough to do that on my own.
I modified the file /etc/yum.repos.d/CentOS-Base.repo and when I tried to do a yum install on some packages, i ran into "error performing checksum" on all mirror sites. Then I fell upon a comment on this site that gave a suggestion to type this: "yum -y remove yum-fastestmirror" to correct it. not a good command to use apparently since it removed yum and yum-fastestmirror. I re-installed them both but since then there doesn't seem to be automatic software update notifications nor any actions to do so in "system tools" under applications. I can still probably do a yum update but it'd be nice to have the system notifications.
My challenge today is a broken sound mixer in gnome. Yesterday I run 'yum update' and it installed about 200 updates. This morning I rebooted, when double-clicking the 'speaker' icon in the top right corner of my gnome and I got a "crash".
(I have to go to mixer and enable 'front speakers' before I get any sound - thats something else i'd like to fix one day) Here is what bug-buddy has to say:
Any advice would be great - i think I should start by reinstalling the gnome mixer, but not sure which 'yum' that is contained in. I did do some reading about rolling back, but I read that is by default disabled!! Arh! why! only when you broke something you realise you need to turn it on.... o well hey ho.
I'm running a fresh install on an intel i7 system on an asus p6t deluxe v2 motherboard with the onboard NIC (Marvell Technology pci-e). I know the NIC is working as when I boot into the onboard OS that Asus provides (Asus Express Gate SSD)I have a working net connection.Booting up CentOS hangs at determining IP information for eth0 and eventually fails with the following error:PING xxx.170.30.1 from xxx.170.31.231 eth0: 56(84) bytes of data---xxx.170.30.1 ping statistics ---4 packets transmitted, o received, +3 errors, 100% packet loss, time 2999ms, pipe 3 failed.
after update to kernel-2.6.18-164.el5 one of the 2 NIC's of my machine are only found at 1 of 4 reboots. Using the old one kernel-2.6.18-128.7.1.el5 all is fine. This are the to NIC's:
The server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
I need to downgrade glibc due to a broken kernel after a libc6 upgrade attempt. See:[URL]..Especially with the reduced capabilities I have right now (few if any programs are working), how might I go about downgrading glibc to 2.6?
I installed the Ubuntu Desktop 10.4 on my new MacBook Pro under a Parallels Desktop (VM).The install wend fine and after rebooting I was a happy new Ubuntu user.Had to reconfigure the ethernet port of my virtual machine and I had internet access.After 5 minutes, Ubuntu displayed a message that there were updates available, which I ran successfully.After the reboot however I got the following message :"An error occurred while mounting /media/psfPress S to skip mounting or M for manual recovery"After pressing M, a maintenance shell started under "root@ubuntu".As new user, I did not want to mess around as root (I would know what to enter).So I pressed ctrl-D which brought me back to the above message and I typed S.Ubuntu started ok however I lost my eth0 interface.In the network tools, I only find the Loopback interface, no eth0 anymore.Do I have to reinstall from scratch ?
I am an old days RH release user(from 6.x) and just switching back from Debian/Ubuntu to CentOS on some servers, but I can not understand the kernel update strategy currently enabled in CentOS.There are two boxes, with almost identical installation, but recently there was an auto update of kernel on one box. This auto update also seems to issue an auto reboot on the machine, which is unacceptable on server machines.
I had a working ubuntu 10.10 system two days ago with kernel 2.6.35-24. I have a gtx 460 card so I have the driver from Jockey/Additional Drivers installed.
Two days ago update manager prompted me to install 2.6.35-25. I've never had problems updating kernels so I did. I Rebooted my machine and gdm/gnome no longer starts. I always get stuck on the tty1 screen. I did some troubleshooting and figured out that my current NVidia drivers seems to be messing it up. So I booted into my older kernel (2.6.35-24) and removed my NVidia driver.
I used these steps to switch from nvidia to nouveau: NvidiaDriverSwitching
I can now boot into my latest kernel (2.6.35-25) but now I'm having problems trying to reinstall the nvidia drivers.
jockey sometimes doesn't list any available drivers. and when it does, it gives me an "System InstallArchive() error" when trying to install.
I tried installing nvidia-current via apt-get and I get these errors:
Code: Setting up nvidia-current (260.19.06-0ubuntu1) ... Removing old nvidia-current-260.19.06 DKMS files... dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified. dkms.conf: Error! No 'PACKAGE_NAME' directive specified. dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
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."
I have centos 5.3 workin on mini itx atom 330. i have some problem with the network when i use Samba. when i move big files the network goes down. i wanna to install the new kernel on my centos to try to fix the network problem with the new drivers includes on the new kernel.
I applied the Kernel update that showed in the updater via the GUI.It now won't boot anymore.Memory for crash kernel (0x0 to 0x0) notwithin permissible range.WARNING calibrate_APIC_clock: the APIC timer calibration may be wrong.
I have been running into network issues lately with my CentOS 5 (installed on AMD Athlon X2 - 64 bit machine about 2 years ago). It was able to connect to the network fine until yesterday when I installed more memory into the machine restarted it.
Upon restart, the boot up was paused at 'Determining IP information for eth0' step for a while and booted with out connecting to the network. I tried restarting the network (/sbin/service network restart), but this is the error message I continuously get: Determining IP information for eth0...PING xxx.1.226.1 (xxx.1.226.1) from xxx.1.226.83 eth0: 56(84) bytes of data
I have a Proliant DL 120 G5 with CentOS 5.4 and I have installed a Brodcom Corporation Netxtrem BCM 5722 Gigabit Ethernet PCI. So I have two interfaces: eth0 broadcom eth1 Intel The eth1 works, instead eth0 don't work. I can ping itself and 127.0.0.1 but I can't ping the gateway. The results of netstat -nr is:
