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.
View 2 RepliesI had a Centos 5.5 system working great...and then due to crazy curiosity, installed the kernel update. Did this through the graphical interface, uncheck all update other than kernel. It downloaded, installed fine..After reboot now all I get is GRUB_ and then nothing else! I waited 3-4 minutes and had to shut down system. Have been googling around but thought I will post it here as well..When I boot with Win7 and use Ext2fsd to check, the boot folder is empty. Not sure if this is because ext2fsd does not read boot folder or it got wiped out by the yum upgrade process.
View 9 Replies View RelatedI have recently run an update and now we are unable to boot the newer kernel. We get stuck as below;
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
Red Hat nash version 5.1.19.6 starting
Unable to access resume device (/dev/VolGroup00/LogVol06)
[Code]...
The kernel version we were at was 2.6.18-194.el5 and the update move us to 2.6.18-194.17.1.el5. I've done some googleing but I'm unable to work out exactly what I need to do. I'm guessing the new kernal is missing a module?
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.
View 2 Replies View RelatedI 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.
View 2 Replies View Relatedafter 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:
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0b.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 0c)
And the Intel one, makes the problems with the new kernel.
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:
# cat /etc/grub.conf
default=0
timeout=20
[code]....
i'm currently running centos 5 with kernel version 2.6.18-92.1.22.el5 is there any way to update to kernel version >= 2.6.27 via yum ? if not via yum is it advisable to compile from source?
View 5 Replies View RelatedI compiled my kernel, compiled scsi support into kernel, used the new kernel and initrd, the boot failed.Then ,i unzip my initrd, found that sd_mod.ko can't be insert, i added it manual, and reboot OK.so, why! in the kernel configure , the sd_mod.ko is set to <M> , but why it can't be found in initrd?
View 1 Replies View RelatedUpdate to 5.3 went OK a few days ago.Today there is updated kernel packages available but it fails dependencies on ecryptfs-utils.
View 3 Replies View RelatedI try to update my kernel to 2.6.18.128.4.1.el5 using
# yum update
After # yum update # rpm -qa kernel*|sort gives the following:
kernel-2.6.18-128.1.14.el5
kernel-2.6.18-128.1.16.el5.centos.plus
kernel-2.6.18-128.4.1.el5.centos.plus
kernel-2.6.18-92.1.18.el5
kernel-2.6.18-92.el5
kernel-devel-2.6.18-128.1.14.el5 .....
This my grub.conf:
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=5.....
yum update installed:
CentOS (2.6.18-128.4.1.el5.centos.plusxen) and
CentOS (2.6.18-128.4.1.el5.centos.plus)
both are not working. I have to run the system using: 2.6.18-128.1.14.el5. Upon trying again #yum update it says that no packages are marked for update. Can I manually install the desired kernel? Do you know a reason why yum update is not automatically installing the proper kernel?
I am running CentOS 5.x and want to yum update, but I do not want to touch the kernel. How can I exclude the kernel update and prevent yum from removing my current kernel?
View 3 Replies View RelatedI'm using Cpanel on my server, before upgrade to new kernel, i could see 8 cores on my i7 server, now i only see 4 cores, is there anything that i need to do to have another time the 8 cores?
View 2 Replies View RelatedI have 2.6.18-164.2.1.e15 running on Hyper-v. I did yum update and noticed that kernel is upgraded to 2.6.18-164.9.1.e15. If I try to boot into the new kernel it hangs with message first "switchroot mount failed" and then "kernel panic". This is probably related to Hyper-v drivers installed in the old kernel. First question: Do you think this is correct? Is it possible to somehow disable Hyper-v drivers so I can boot into the new kernel and then reinstall drivers? There is nothing in Microsoft documentation about uninstalling Linux Integration Components.
View 9 Replies View RelatedI installed the Centos 5.5 with XEN and put 03 virtual machines (Centos 5.5 too). I did this correctly, but I have a problem. In the virtual machine, I need update the kernel. I used "yum update kernel" and this is downloaded correctly and the menu.lst file is updated too, but the kernel not ran. I ran "grub-install /dev/sda" or "grub-install /dev/xvda" and received a error return. I read the device.map file and i ran "grub-install /dev/sde" and received a error return too.
The errors:
[root@vm01 ~]# grub-install /dev/sda
/dev/sda: Not found or not a block device.
[root@vm01 ~]# grub-install /dev/sde
/dev/sda1 does not have any corresponding BIOS drive.
[root@vm01 ~]# grub-install /dev/xvda
/dev/xvda: Not found or not a block device.
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.
Last I upgraded one of our cent 5 boxes which is running kvm with a mix of centos and windows VMs.After the update performance just tanked on the XP guest, but the others (including other windows VMs) are just fine.I checked with our good friend google and didn't really get any help there.We're hoping to NOT have to rebuild the XP guest, so I thought I'd check in here first.
This is CentOS release 5.5 (Final) with kernel
2.6.18-194.32.1.el5 #1 SMP (64bit)
After update to 5.3 and reboot I got this error. googling for it I found that it is a known bug in kernel REHL 5.3 and there is also a patch for it [URL]. I am very new to linux, so how to apply, or just wait for a new kernel?
View 4 Replies View Relatedafter updating freshly installed CentOS 5.2 to 5.3, the new - updated kernel remains invisible to GRUB (at least in GRUB boot menu). I've tried reinstalling, adding the entry manually (although one entry for the new kernel already exists, and is default boot target), altering the old kernel entry to refer to the new kernel and initrd (since it is the only entry visible), and nothing worked. Also, the new boot entry added manually didn't show up on the boot menu either. After trying to edit the entry for the old kernel and initrd and boot it i got the following message:
Error 13: Invalid or unsupported executable format. I've searched and found:
13 : Invalid or unsupported executable format
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD). The hardware I installed CentOS on is Dell Optiplex 755 with RAID 1 configured - using onboard controller (if this can be of any relevance).
I installed the PAE kernel package on a Compaq DL380 G3 with 6GB of RAM, CentOS 5.5, vanilla install.
Upon reboot, GRUB cannot boot any of the kernels. I get an invalid device string error. Poking around in GRUB, it detects root correctly at hd(0,0) Beyond that, it cannot even find /boot/grub/stage1. I got out of the bind by reinstalling the kernel that ships with the installer. I'd like to use the 6GB RAM if possible. I attempted to follow GRUB's documentation here: [URL] but there is no grub-mkimage in centos5.5.
Also, the 5.5 installer detects, but appears to have no way to mount usb flash drives. I used the installer disc 1 to get into rescue mode. From there, I inserted a usb flash drive. dmesg and lsusb show the device, but there's no device node and resultant messages when a flash drive is inserted. There is no usb-storage module when doing an lsmod from the installer. I don't have this issue in other distro installers.
I decided to try Linux recently. I downloaded CentOS-5.3-i386-bin-DVD.iso. Installation was successful but the OS reports Kernel Panic while booting. At first I can see messages:
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not usin MMCONFIG
The OS continues to boot, but then shows kernel panic.
I tried to solve this problem during several days. I've installed the OS at least 10 times changing conditions. I tried x86-64 version, disabled PAE in BIOS, performed manual partitioning without LVM. The result is the same.
My PC has Intel Core 2 Duo E8400 CPU (no overclocking), 4GB RAM (DDR2-800), ATI 3470 GPU. Windows is working smoothly on it, I can encode video during several hours without problem. All fans are working, the system is not overheated. MemTest86 showed no errors.
I've installed CentOS on my laptop (Core 2 T5600 CPU, 2GB RAM, Intel G945 Video), it works nice, i like it very much.
For testing I've installed OpenSUSE 11.1 on the PC, everything is ok, I'm writing this message from it.
vmware virtual machine, the system is centos 5.4 want to upgrade the kernel 2.6.32. make menuconfig is based on the default. make; make modules_install; make install no problem, reboot the system to choose a new kernel, new kernel can not boot, the following is vastly map, right in the / boot directory, there is no 2.6.32 of the config files, do not know how the matter , in the compilation before I put / boot directory of the original system config files to the source directory cp The following is the contents of the screenshot
[Code]....
i installed xen kernel on centOs 5.6 Final 32 bit and i edit and configure grub.cfg but xen kernel won't boot and boot from default Kernel .
what do i do??
i paste grub.cfg here :
default=0
timeout=5
title CentOS (2.6.18-274.el5xen)
kernel /xen.gz-2.6.18-274.el5
module /vmlinuz-2.6.18-274.el5xen root=/dev/sda2 ro
[Code]....
During boot from CentOS5.4 DVD and after choose linux rescue mode, encounters with error:
Code: 8b 5e 04 83..... ........ 3d c0
EIP:[<c0417656>]__modify_IO_APIC_irq+0x40/0x62 SS:ESP 0068:df94eed4
<0> Kernel panic - not syncing : Fatal exception
I have installed Centos and after few days I used it as a web server, database server (MySQL) and have some very important for me applications installed.
Today - I have read about "yum -update" function and I (a dummy one...) tried it. After some minutes the process was finished. But unfortunatelly - my server did not boot any more.
As startup options I have:
CentOS (2.6.18-164.6.1.el5)
CentOS (2.6.18.-164.6.1.el5PAE)
CentOS (2.6.18-128.2.1.el5PAE)
CentOS (2.6.18-128.2.1.el5)
CentOS (2.6.18-128.1.14.el5)
CentOS (2.6.18-92.el5)
I'm not sure what are these options. Anyway - I have tried to choose every one and the result is aways the same : red Hat Nash version 5.1.19.6 starting
Then starts the clock [ok],
Then starts the "udev" [ok]
And then My screen goes to suspend mode, with the text "no signal".
The most important thing is to backup the data from the hard disk. Do I have any chance to repair this installation ?
The first server I installed installed fine. The second server, installed with the same config, went to "kernel panic not syncing no init found try passing init= option in kernel" error. I tried reinstalling but it keeps going to that error after install reboot. The storage is ISCSI connected via Intel Server Adapter, which allows it to boot from ISCSI. Not sure if that's the cause for the problem, but the first server is connected to the same ISCSI and installed just fine.
Is there a way that I can make sure ISCSI module installs during installation? Although I think it is installed since it's able to copy the files and setup /dev/sda. I just wana make sure that it installs during setup.
I built a home server (NAS/WWW/SSH/media server etc) and chose CentOS 5 as the OS (stability, easy of configuration).I was just about to start tuning the power consumption when I realised that the kernel CentOS uses is so "old" that it does not support the latest reduced power consumption enhancements that Linux has achieved in big strides in the recent past (we are probably still talking 6-12+ months ago e.g. tickless kernel)..
So my questions; 1) I know CentOS was maybe not meant for home servers (certainly its not its primary purpose), but if it is, any ideas of what kind of power consumption it takes (I know its relative) and if there are particular power consumptions that are worthwhile?
2) Do you recommend me compiling my own 2.6.21+ kernel from kernel.org or am I just likely to have compatibility issues (I really did not want to do that) or when is CentOS 5.4 supposed to have a newer 2.6.21+ version kernel?
Was it wrong of me in principle to choose CentOS for a home server when I am power conscious? (I don't have a low-power VIA processor either but a P4 so I am really just hoping to make do with software changes).
If you select "support virtualization" during install, you get the xen kernel installed.
Some things do not work with this kernel (e.g. nVidia drivers). So my question is whether it is possible to install both kernels (xen and ordinary) and select between them with grub at boot time?
I did try this a while ago, by first installing with xen and then manualy adding the ordinary kernel, but the ordinary kernel failed to boot (for reasons I don't now recall - sorry). Clearly, there must be differences in the "virtualization" build other than the kernel.
The alternative, if I want to play with virtualization, would be to have two entirely separate installations, but this seems like a waste of space when surely almost everything must be identical?
I can't find anything in the Centos Xen documentation about this.
Before I try again I would just like to check if anyone actually knows if this is possible, or if not why not?
Or can it be done with KVM?
I'm setting up a raid 5 on several hard disks with a layer of lvm on top for good measure.I know the recent kernels support growing software raid, but since centos runs 2.6.18, I wanted to make sure it'll work. Does the centos kernel support growing raid devices?
View 1 Replies View RelatedI installed ubuntu on a second hard drive.Nowhere did the fracken ubuntu installer ask my permission to over-write my mbr but that's exactly what it did.I'm booted off the rescue CD trying to restore the mbr to how centos left it (I'll add ubuntu to grub manually) but I can't boot into rescue.linux rescue results in a kernel panic suggesting I need the noapic argument. Makes sense, I needed that to install and need that in grub.linux rescue noapic boots into the installer, not rescue.How do I boot into rescue mode with the noapic kernel argument?
View 2 Replies View Related