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 RepliesI am running Slackware64-current(multi-lib) and I have stumbled across something that I don't fully understand.I have read that the kernel-headers should not be updated as glibc is compiled against them and therefore requires that set of kernel headers. Recently the kernel version has been bumped a couple of times but glibc has stayed the same.Should glibc be re-compiled each time there is a kernel update?
Perhaps someone can explain, in very simple terms, the relationship between the kernel, the kernel headers, the kernel modules and glibc.
After the bunch of updates with current, my custom kernel (2.6.33) can't boot.
The error is:
/sbin/e2fsck: No such file or directory while trying to open /dev/sda6
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
The /dev/sda6 is ext4 and is ok since it can boot with official huge smp kernel 2.6.33.
My custom kernel can boot before this bunch of updates in current.
What i missing in kernel?
I just ran "yum update" to download the latest kernel from the repository, and noticed that it's 2.6.18-164.11.1 while the latest on www.kernel.org is 2.6.32.4.Out of curiosity, why is there such a discripency between the two? Lack of resources to test and build binaries?
View 5 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 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 RelatedI 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 Replies View Relatedi'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 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 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'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)
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code:
# Linux bootable partition config begins
image = /other/spare4/boot/vmlinuz
[code]....
What's the command for installing kernel headers for the currently installed kernel?
View 2 Replies View RelatedAfter 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 RelatedI downloaded and installed beta1 a few days ago but have just noticed beta2 is now available. Do I need to download beta2 and re-install or will my current beta1 update to beta2 via update manager?
View 6 Replies View RelatedI have installed the fedora 14, but there is no kernel source tree.I read the doc "building a custom kernel".But I don't want to rebuild a new kernel.I just want to install the source tree of current kernel.Could someone tell me the way?
View 6 Replies View RelatedMy server started to throw the following errors at me:
Quote:Message from syslogd@ at Wed Nov 24 22:17:13 2010 ... server kernel: Uhhuh. NMI received for unknown reason 2d.
Message from syslogd@ at Wed Nov 24 22:17:13 2010 ... server kernel: Do you have a strange power saving mode enabled?
Message from syslogd@ at Wed Nov 24 22:17:13 2010 ... server kernel: Dazed and confused, but trying to continue
I want to keep my current Kernel (I wanted to keep the last one but read on... lol) Why? Fedora is stable as a rock right now and so is GNOME
Now: 2 updates ago I thought I was cool and I did this:
nano /etc/yum.conf
and I added.... this: exclude=kernel* nvidia*
But right after the next update.... all hell broke loose.... X errors and more... no need for details since I used tty2 to uncomment the "exclude" in yum.conf... updated and ALL is well and VERY stable (good job to Fedora.... it wasn't your fault... I just know I didn't exclude enough )
"What do I need to exclude in yum.conf if I want to keep the current Kernel as well as Nvidia driver while keeping everything updated besides "kernel* and besides "nvidia* packages"? I know I missed a dependency and that upgrade broke the "old"
I have got an Notebook whose CPU is 64bit.The Notebook has an CentOS installation. Now I want to find out if this CentOS is 32bit or 64bit.How can I check this?
uname -a
gives something with ....i686 i686 i386...."
What does that mean?Does that refer to the hardware or the CentOS OS? An 32bit CentOS can be installed on a 64bit hardware!I am interested in the OS capability not of the hardware!
I am attempting to bring my server up from etch to lenny and during that process I need to upgrade my kernel to at least 2.6.18. I am currently on 2.6.17-2 and get the following error for my sources.list file:
W: Couldn't stat source package list [URL].. stat (2 No such file or directory)
I need to download the Kernel sources add a few lines and then recompile and install the new files. I found the following lines that are suppose to do it on nVidia's forums:
Code:
# Install Kernel Sources
sudo apt-get build-dep linux-image-2.6.24-17-rt
sudo apt-get source linux-image-2.6.24-17-rt[code]........
what the Kernel Module Source packages are called?... This guide I am trying to follow is obviously dated but it is the only solid lead I have been able to find towards making my ram work...This is the original thread on the NVNEWs boards: Unable to install Nvidia driver on 9500M + Ubuntu - Page 2 - nV News Forums,Read through that thread I linked to the NVidia forums for a detailed run down of what is wrong.
The semi short version: There is some sort of issue with the NVidia driver on the G1Sn (and several other Asus Models) and the way the Linux Kernel address memory, the issue results in not being able to use more than 2 Gigs of ram with the Nivida drivers. There is a patch (again check the nvidia forum link) that people said they had applied to fix this issue. At this point I am seriously considering Vista again if I can't get this working I love Ubuntu but I hate having my hardware limited by my software...where to download the files I need to recompile in the Kernel with the patch I need for my ram to work?
I tried posting there but it seems like the thread is long dead.. how I can download the needed files and maybe how I add these lines to it?I also started a thread on the ubuntu forums here: [ubuntu] Downloading Current Kernel Sources.
Which is the current stable version of kernel in fedora 10 and how can I installed because right now I have unstable kernel:
uname -a
Linux blind 2.6.29.3-60.fc10.x86_64 #1 SMP Sat May 9 04:18:14 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
I just want to get back to latest stable kernel of fedora 10. I'm not able from the grub to choose an older because there are only kernels for fedora 9. The problem was that previously I used fedora 9 however I upgrade it but it was still with kernel of fedora 9 so I pick it the unstable of fedora 10 and I installed it. Right now I just want to get back to current version of kernel in fedora 10 so I can upgrade it to fedora 11.