I have a plain vanilla Centos source (not 100% sure where we got it from), but I can't seem to get a build that installs correctly. I tried the method described at http://wiki.centos.org/HowTos/Custom_Kernel, but rpm doesn't like the output file, and even if I install it with -F, nothing seems to happen - no new kernel, now initrd, nothing. When I tried following the directions in the README file that came with the source, I built the kernel just fine, but the instructions then go on to describe how to modify LILO to make the install work, and my boot loader is GRUB - not sure how to reconcile those two. So, I built yet another kernel (rpm) following the guide at http://www.howtoforge.com/kernel_compilation_centos, and the rpm built just fine, but when I run mkinitrd, it complains that I don't have the ahci module in my kernel. The only reference I have found to ahci is in my boot setup, and it is already enabled, so, once again, I am stuck. Anyone have any ideas here? I'm running Centos 2.6.9-42.0.3ELsmp on a Dell Precision 390 (P4/HT 3GHz, 2Gb mem, ATI FireGL 4700, 160Gb SATA, ... Thanks (again).
On 1/25/07, Mark Hull-Richter <mhull-richter at datallegro.com> wrote:> I have a plain vanilla Centos source (not 100% sure where we got it > from), but I can't seem to get a build that installs correctly.Welcome to the joy of building custom kernels.> I tried the method described at > http://wiki.centos.org/HowTos/Custom_Kernel, but rpm doesn't like the > output file, and even if I install it with -F, nothing seems to happen - > no new kernel, now initrd, nothing.Something in your build process has likely failed. Also, -F is to 'freshen' an existing package. This is something you most definitely DO NOT want to do with a kernel.> When I tried following the directions in the README file that came with > the source, I built the kernel just fine, but the instructions then go > on to describe how to modify LILO to make the install work, and my boot > loader is GRUB - not sure how to reconcile those two.Look at your /etc/grub.conf and add a stanza like the others, but with your kernel info. It should be pretty straight forward.> > So, I built yet another kernel (rpm) following the guide at > http://www.howtoforge.com/kernel_compilation_centos, and the rpm built > just fine, but when I run mkinitrd, it complains that I don't have the > ahci module in my kernel. The only reference I have found to ahci is in > my boot setup, and it is already enabled, so, once again, I am stuck. > Anyone have any ideas here?Yes. Follow one guide at a time. This will keep you from dragging your problem around with you. Troubleshoot why your build failed the first time around.> > I'm running Centos 2.6.9-42.0.3ELsmp on a Dell Precision 390 (P4/HT > 3GHz, 2Gb mem, ATI FireGL 4700, 160Gb SATA, ...Seems fairly common hardware. Are you sure you need to rebuild? Perhaps the centos wiki was not stern enough in discouraging custom builds for a plethora of reasons. What feature is it that you wish to enable in your custom kernel? -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell
Thanks - I'm still working on it. Does anyone know where there is a clean, working source for Centos 2.6.9-42.0.3 (supposedly the 4.4 final)? I'm pretty sure the one I have is NOT the right one.... -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Jim Perrin Sent: Thursday, January 25, 2007 2:47 PM To: CentOS mailing list Subject: Re: [CentOS] Problems with building a complete kernel On 1/25/07, Mark Hull-Richter <mhull-richter at datallegro.com> wrote:> I have a plain vanilla Centos source (not 100% sure where we got it > from), but I can't seem to get a build that installs correctly.Welcome to the joy of building custom kernels.> I tried the method described at > http://wiki.centos.org/HowTos/Custom_Kernel, but rpm doesn't like the > output file, and even if I install it with -F, nothing seems to happen-> no new kernel, now initrd, nothing.Something in your build process has likely failed. Also, -F is to 'freshen' an existing package. This is something you most definitely DO NOT want to do with a kernel.> When I tried following the directions in the README file that camewith> the source, I built the kernel just fine, but the instructions then go > on to describe how to modify LILO to make the install work, and myboot> loader is GRUB - not sure how to reconcile those two.Look at your /etc/grub.conf and add a stanza like the others, but with your kernel info. It should be pretty straight forward.> > So, I built yet another kernel (rpm) following the guide at > http://www.howtoforge.com/kernel_compilation_centos, and the rpm built > just fine, but when I run mkinitrd, it complains that I don't have the > ahci module in my kernel. The only reference I have found to ahci isin> my boot setup, and it is already enabled, so, once again, I am stuck. > Anyone have any ideas here?Yes. Follow one guide at a time. This will keep you from dragging your problem around with you. Troubleshoot why your build failed the first time around.> > I'm running Centos 2.6.9-42.0.3ELsmp on a Dell Precision 390 (P4/HT > 3GHz, 2Gb mem, ATI FireGL 4700, 160Gb SATA, ...Seems fairly common hardware. Are you sure you need to rebuild? Perhaps the centos wiki was not stern enough in discouraging custom builds for a plethora of reasons. What feature is it that you wish to enable in your custom kernel? -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos
My bad - I rechecked and it is the correct source. AND I found that the make install (with make modules_install first) takes care of GRUB for me. BUT: Now I can't boot because the installed Centos 4.4 was from the distribution DVD, and it depends on the lvm to load. My build doesn't know about the lvm and it refuses to boot - it dies coming up with an error from lvm, followed by two more where it can't find a file system, then the kernel panics (and hangs the machine). How do I get around lvm? Thanks (again). -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Will McDonald Sent: Thursday, January 25, 2007 4:21 PM To: CentOS mailing list Subject: Re: [CentOS] Problems with building a complete kernel On 26/01/07, Mark Hull-Richter <mhull-richter at datallegro.com> wrote:> Thanks - I'm still working on it. > > Does anyone know where there is a clean, working source for Centos > 2.6.9-42.0.3 (supposedly the 4.4 final)? I'm pretty sure the one Ihave> is NOT the right one....The source tarball should be included in the SRPM for your kernel, I'd imagine. http://mirror.centos.org/centos-4/4.4/updates/SRPMS/kernel-2.6.9-42.0.3. EL.src.rpm Once installed (if installed as root) it'll be in /usr/src/redhat/SOURCES, otherwise it'll be in wherever your .rpmmacros file points. Will. _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos
I haven't actually made any changes to the kernel yet - I need a working build, hopefully one that matches my current installation, but a working build to start. (Otherwise I won't know if the kernel I'm running and one I've modified contain anything I don't know about....) I used the config that the installed version had as my base, and I don't think I changed anything. I ran make menuconfig and set the version to something different, then ran make oldconfig to see what changes were needed (none), then built. In theory, if lvm support was in the installed kernel, it should have built into my new one, right? I'll be making a minor mod to xfs first, then there's a device driver we want to add (I think). I got a ton of "attempt to assign to nonexistent symbol" notices after exiting make menuconfig - I'm assuming that these are harmless. Thanks again. -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Jim Perrin Sent: Friday, January 26, 2007 3:47 PM To: CentOS mailing list Subject: Re: [CentOS] Problems with building a complete kernel On 1/26/07, Mark Hull-Richter <mhull-richter at datallegro.com> wrote:> My bad - I rechecked and it is the correct source. AND I found thatthe> make install (with make modules_install first) takes care of GRUB for > me. > > BUT: > > Now I can't boot because the installed Centos 4.4 was from the > distribution DVD, and it depends on the lvm to load. My build doesn't > know about the lvm and it refuses to boot - it dies coming up with an > error from lvm, followed by two more where it can't find a filesystem,> then the kernel panics (and hangs the machine). > > How do I get around lvm?Build your kernel with lvm support. It sounds like you're changing far more than you need to in the config. If you follow the how-to on the centos wiki, you'd only be changing the things you need to, and all else will stay the same. This keeps you from running into things like you're experiencing. Again, are you certain you need to rebuild? What feature is it that you need? -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos
Mark Hull-Richter wrote:> I have a plain vanilla Centos source (not 100% sure where we got it > from), but I can't seem to get a build that installs correctly. > > I tried the method described at > http://wiki.centos.org/HowTos/Custom_Kernel, but rpm doesn't like the > output file, and even if I install it with -F, nothing seems to happen - > no new kernel, now initrd, nothing.My 30-second glance at it suggests it's not very good; the prep stage is quite wrong. For example, kernel-devel is a part of the output of the build process. You cannot install it before you have built your kernel. I suggest you start with the src.rpm. rpm -i ... rpmbuild -bp ... <wherevr the spec went> Install whatever is says you need:-) Here is a script that works for _at least some_ RHEL4 & FC3 kernels. I suggest you read it, understand it and adapt it to what you want. Then, maybe fix that wiki. #!/bin/bash set -xe rpmbuild=rpmbuild\ --define\ "_topdir${HOME}/redhat" rpm=rpm\ --define\ "_topdir${HOME}/redhat" if [ -n "$1" ] ; then K=$1 else K=$(dir -d1rt ~/Fedora/kernel*src.rpm ~/RH/FC3/updates/SRPMS/kernel*src.rpm | tail -1) fi DirName=$(rpm -qp --qf '%{name}-%{version}\n' ${K}) ${rpm} -i ${K} date=$(date "+%a %b %d %Y") sed -r <redhat/SPECS/kernel-2.6.spec >redhat/SPECS/kernel-2.6-dl.spec \ -e 's=FC\>=dl=g' \ -e 's=FC2\>=dl2=g' \ -e 's=FC3\>=dl3=g' \ -e 's=%define builddoc 0=%define builddoc 1=' \ -e "s=%changelog=%changelog\n* ${date} John Summerfield <summer at herakles.homelinux.org>\n- autobuild for dl %{release}\n=" : : : : diff -u redhat/SPECS/kernel-2.6.spec redhat/SPECS/kernel-2.6-dl.spec || : ${rpmbuild} -bp --target i686 redhat/SPECS/kernel-2.6-dl.spec echo Fixing configs ( set -x cd $(find ~/redhat -type d -name ${DirName})/lin* ls -la for f in configs/*.config do : make -s mrproper sed < $f >.config \ -e 's+# CONFIG_NTFS_FS is not set+CONFIG_NTFS_FS=m\nCONFIG_NTFS_DEBUG=n\nCONFIG_NTFS_RW=y+' grep -q 'CONFIG_NTFS_FS is not set' .config && exit grep -4 NTFS .config # make -s oldconfig cp -bvp .config ~/redhat/SOURCES/$(basename $f) head -9 $f .config ~/redhat/SOURCES/$(basename $f) mv -b .config $f done ) echo Fixed configs BO="-ba" for arch in i686 do : ${rpmbuild} ${BO} --clean --target ${arch} redhat/SPECS/kernel-2.6-dl.spec BO="-bb --rmsource" done In my case, I'm building a brace of kernels with NTFS support. the resultant kernals install on nahant/FC3 just fine. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list
Yes. Here is what happens: Booting (CentOS 2.6.9MHRsmp)' kernel direct mapping nodes[?] up to 10100000000 @ 8000-d000 root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.9MHRsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet [Linux-bzImage, setup=0x1400, size=0x190795] initrd /initrd-2.6.9MHRsmp.img [Linux-initrd @ 0x3706300, 0x18caf6 bytes] . Decompressing Linux...done Booting the kernel audit (1170068438.664:0): initialized Red Hat nash version 4.2.1.8 starting Reading all physical volumes. This may take a while... No volume groups found Volume group "VolGroup00" not found ERROR: /bin/lvm exited abnormally! (pid 206) mount: error 6 mounting ext3 mount: error 2 mounting none switchresest: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init Then the system halts. I'm using the same config file as the installed CentOS 2.6.9-42.0.3, and here are my /etc/fstab and grub.conf contents: [root at localhost linux]# cat /etc/fstab # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrecorder auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0 /dev/fd0 /media/floppy auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0 [root at localhost linux]# cat /etc/grub.conf # grub.conf generated by anaconda # # 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/sda default=2 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu password **************************************************** title CentOS (2.6.9MHRsmp) root (hd0,0) kernel /vmlinuz-2.6.9MHRsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9MHRsmp.img title CentOS (2.6.9MHRsmp2) root (hd0,0) kernel /vmlinuz-2.6.9MHRsmp2 ro root=/dev/sda1 rhgb quiet initrd /initrd-2.6.9MHRsmp2.img title CentOS (2.6.9-42.0.3.ELsmp) root (hd0,0) kernel /vmlinuz-2.6.9-42.0.3.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-42.0.3.ELsmp.img title CentOS (2.6.9-42.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-42.0.3.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-42.0.3.EL.img title CentOS-4 x86_64 (2.6.9-42.ELsmp) root (hd0,0) kernel /vmlinuz-2.6.9-42.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-42.ELsmp.img title CentOS-4 x86_64-up (2.6.9-42.EL) root (hd0,0) kernel /vmlinuz-2.6.9-42.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-42.EL.img Any hints, suggestions, comments, etc. would be most welcome. Thanks. mhr -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Marcin Mazurek Sent: Saturday, January 27, 2007 1:03 AM To: CentOS mailing list Subject: Re: [CentOS] Problems with building a complete kernel Mark Hull-Richter (mhull-richter at datallegro.com) napisa?(a):> I haven't actually made any changes to the kernel yet - I need a working > build, hopefully one that matches my current installation, but a working > build to start. (Otherwise I won't know if the kernel I'm running and > one I've modified contain anything I don't know about....) > > I used the config that the installed version had as my base, and I don't > think I changed anything. I ran make menuconfig and set the version to > something different, then ran make oldconfig to see what changes were > needed (none), then built. In theory, if lvm support was in the > installed kernel, it should have built into my new one, right? >Do You have an initrd file for new kernel? If not You should create one with mkinird. hth -- Marcin Mazurek http://www.netsync.pl/ - :::: - nic-hdl: MM3380-RIPE GnuPG 6687 E661 98B0 AEE6 DA8B 7F48 AEE4 776F 5688 DC89 _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos
Not exactly. 1) I will be modifying the kernel and possibly writing one or more device drivers. I'd like to start with a build that works - that's been one of the best ways I've found to ensure that any added or modified code can be reasonably inferred to cause whatever problems I might find. Why is it a problem for one to want to be able to build a working kernel? 2) The build log was clean - where would I find the error log? Wait - that's kind of secondary. I then moved to the instructions in the README file, which are, yes, drastically different - they don't involve rpm, using the exact same source for the exact same kernel. The only fundamental difference is that make doesn't necessarily generate an rpm package (actually, this one does), and I don't need to use rpm for anything. Later on that may be a problem, but not right now. 3) The modification to xfs is a sample based on what I have been assigned to do - I'm not trying to generate the latest and greatest xfs that's available out there. Maybe I should, in the ideal world, but working in corporate America is pretty far from the ideal world. 4) This is all true, but not particularly relevant. I need a base kernel with NO modifications that I can then start to use to create any customizations, like a new device driver or twiddling with some other code that we need to customize because, perhaps, for compatibility reason, we can't just upgrade to a new version of <some_module>. As for the lvm "incompatibility," this is the main one I don't understand. If I am building from the same source as the distribution I am running on this box, why would there be an incompatibility here? Here's what the boot panel displays (copied by hand but missing all indents since it hangs at the end and I don't know if there's a better way to capture the display): Booting (CentOS 2.6.9MHRsmp)' kernel direct mapping nodes[?] up to 10100000000 @ 8000-d000 root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.9MHRsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet [Linux-bzImage, setup=0x1400, size=0x190795] initrd /initrd-2.6.9MHRsmp.img [Linux-initrd @ 0x3706300, 0x18caf6 bytes] . Decompressing Linux...done Booting the kernel audit (1170068438.664:0): initialized Red Hat nash version 4.2.1.8 starting Reading all physical volumes. This may take a while... No volume groups found Volume group "VolGroup00" not found ERROR: /bin/lvm exited abnormally! (pid 206) mount: error 6 mounting ext3 mount: error 2 mounting none switchresest: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init [system halts] Thanks. mhr -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Jim Perrin Sent: Friday, January 26, 2007 5:36 PM To: CentOS mailing list Subject: Re: [CentOS] Problems with building a complete kernel 1. There was no need specified for why a custom kernel was needed. If such a need was spelled out, it's possible that much better help could be provided, or it could even be added to the centosplus kernel. 2. No build log or error of any kind was shown to help troubleshoot. And rather than figuring out what went wrong, the user moved to a drastically different set of instructions, which use a drastically different kernel. Doing so without proper understanding could (and likely would) lead to problems down the road. (The install with --nodeps on the howtoforge listing is a nice touch) 3. The user in question seems to have not done homework regarding centos and XFS, and will be modifying the 2.6.9 xfs code instead of using the much nicer xfs code backported by ex-SGI folks specifically for centos. 4. There are many considerations in building a custom kernel for centos, such as the audit libs, utmp compatability, current system compatability (as demonstrated by the lvm troubles) and so on.
I am building on an x86_64 machine for itself. "Jim's tutorial" - unfamiliar reference. Please elaborate. Thanks. Mhr
I shoulda knowd....
Okay, this may seem dumb, but I imagine I've already been there....
Here's what I get when I try the install with rpm:
[root at localhost x86_64]# rpm -ivh kernel-*.rpm
Preparing... ###########################################
[100%]
package kernel-2.6.9MHRsmp-1 (which is newer than
kernel-2.6.9-42.0.3.mhr) is already installed
[root at localhost x86_64]#
Now, I _really_ want to install this, but when I try yum localinstall, I
get this:
[root at localhost x86_64]# yum localinstall kernel-*.rpm
Setting up Local Package Process
Examining kernel-2.6.9-42.0.3.mhr.x86_64.rpm: kernel -
2.6.9-42.0.3.mhr.x86_64
Examining kernel-debuginfo-2.6.9-42.0.3.mhr.x86_64.rpm: kernel-debuginfo
- 2.6.9-42.0.3.mhr.x86_64
Examining kernel-devel-2.6.9-42.0.3.mhr.x86_64.rpm: kernel-devel -
2.6.9-42.0.3.mhr.x86_64
Examining kernel-largesmp-2.6.9-42.0.3.mhr.x86_64.rpm: kernel-largesmp -
2.6.9-42.0.3.mhr.x86_64
Examining kernel-largesmp-devel-2.6.9-42.0.3.mhr.x86_64.rpm:
kernel-largesmp-devel - 2.6.9-42.0.3.mhr.x86_64
Examining kernel-smp-2.6.9-42.0.3.mhr.x86_64.rpm: kernel-smp -
2.6.9-42.0.3.mhr.x86_64
Examining kernel-smp-devel-2.6.9-42.0.3.mhr.x86_64.rpm: kernel-smp-devel
- 2.6.9-42.0.3.mhr.x86_64
Marking kernel-debuginfo-2.6.9-42.0.3.mhr.x86_64.rpm to be installed
Marking kernel-largesmp-2.6.9-42.0.3.mhr.x86_64.rpm to be installed
Marking kernel-2.6.9-42.0.3.mhr.x86_64.rpm as an update to kernel -
2.6.9-42.EL.x86_64
Marking kernel-2.6.9-42.0.3.mhr.x86_64.rpm as an update to kernel -
2.6.9-42.0.3.EL.x86_64
Marking kernel-devel-2.6.9-42.0.3.mhr.x86_64.rpm as an update to
kernel-devel - 2.6.9-42.0.3.EL.x86_64
Marking kernel-devel-2.6.9-42.0.3.mhr.x86_64.rpm as an update to
kernel-devel - 2.6.9-42.EL.x86_64
Marking kernel-largesmp-devel-2.6.9-42.0.3.mhr.x86_64.rpm as an update
to kernel-largesmp-devel - 2.6.9-42.0.3.EL.x86_64
Marking kernel-smp-2.6.9-42.0.3.mhr.x86_64.rpm as an update to
kernel-smp - 2.6.9-42.EL.x86_64
Marking kernel-smp-2.6.9-42.0.3.mhr.x86_64.rpm as an update to
kernel-smp - 2.6.9-42.0.3.EL.x86_64
Marking kernel-smp-devel-2.6.9-42.0.3.mhr.x86_64.rpm as an update to
kernel-smp-devel - 2.6.9-42.0.3.EL.x86_64
kernel-2.6.9-42.0.3.mhr.x86_64.rpm: does not update installed package.
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package kernel-largesmp-devel.x86_64 0:2.6.9-42.0.3.mhr set to be
updated
---> Package kernel-smp.x86_64 0:2.6.9-42.0.3.mhr set to be installed
---> Package kernel.x86_64 0:2.6.9-42.0.3.mhr set to be installed
---> Package kernel-smp-devel.x86_64 0:2.6.9-42.0.3.mhr set to be
updated
---> Package kernel-largesmp.x86_64 0:2.6.9-42.0.3.mhr set to be updated
---> Package kernel-devel.x86_64 0:2.6.9-42.0.3.mhr set to be installed
---> Package kernel-debuginfo.x86_64 0:2.6.9-42.0.3.mhr set to be
updated
--> Running transaction check
Dependencies Resolved
===========================================================================
Package Arch Version Repository
Size
===========================================================================Installing:
kernel x86_64 2.6.9-42.0.3.mhr
kernel-2.6.9-42.0.3.mhr.x86_64.rpm 34 M
kernel-debuginfo x86_64 2.6.9-42.0.3.mhr
kernel-debuginfo-2.6.9-42.0.3.mhr.x86_64.rpm 961 M
kernel-devel x86_64 2.6.9-42.0.3.mhr
kernel-devel-2.6.9-42.0.3.mhr.x86_64.rpm 11 M
kernel-largesmp x86_64 2.6.9-42.0.3.mhr
kernel-largesmp-2.6.9-42.0.3.mhr.x86_64.rpm 39 M
kernel-smp x86_64 2.6.9-42.0.3.mhr
kernel-smp-2.6.9-42.0.3.mhr.x86_64.rpm 34 M
Updating:
kernel-largesmp-devel x86_64 2.6.9-42.0.3.mhr
kernel-largesmp-devel-2.6.9-42.0.3.mhr.x86_64.rpm 11 M
kernel-smp-devel x86_64 2.6.9-42.0.3.mhr
kernel-smp-devel-2.6.9-42.0.3.mhr.x86_64.rpm 11 M
Transaction Summary
===========================================================================Install
5 Package(s)
Update 2 Package(s)
Remove 0 Package(s)
Total download size: 1.1 G
Is this ok [y/N]: N
Exiting on user Command
Complete!
[root at localhost x86_64]#
Since this is going to update the two *-devel packages, I need to know
if this is safe to do, i.e., will this damage anything I need to get
back to if the new installed kernel doesn't boot or work right (even
though rpm says it's the same one)?
Thanks again.
mhr
CentOS newbie (duh!)
Many, many thanks - it is up and running! mhr -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Phil Schaffner Sent: Wednesday, January 31, 2007 6:20 AM To: CentOS mailing list Subject: RE: [CentOS] Problems with building a complete kernel On Tue, 2007-01-30 at 16:38 -0500, Mark Hull-Richter wrote:> I shoulda knowd.... > > Okay, this may seem dumb, but I imagine I've already been there.... > > Here's what I get when I try the install with rpm: > > [root at localhost x86_64]# rpm -ivh kernel-*.rpm > Preparing...###########################################> [100%] > package kernel-2.6.9MHRsmp-1 (which is newer than > kernel-2.6.9-42.0.3.mhr) is already installedIf the "newer" package is the non-working kernel from earlier attempts, and not the one you are running, it should be safe to do # yum remove kernel-2.6.9MHRsmp-1 or # rpm -e kernel-2.6.9MHRsmp-1 Your naming convention seems to be confusing RPM.> [root at localhost x86_64]# > > Now, I _really_ want to install this, but when I try yum localinstall,I> get this: > > [root at localhost x86_64]# yum localinstall kernel-*.rpm > Setting up Local Package Process > Examining kernel-2.6.9-42.0.3.mhr.x86_64.rpm: kernel -... snip ...> --> Running transaction check > > Dependencies Resolved > >=======================================================================> ====> Package Arch Version Repository> Size >=======================================================================> ====> Installing:> kernel x86_64 2.6.9-42.0.3.mhr > kernel-2.6.9-42.0.3.mhr.x86_64.rpm 34 M > kernel-debuginfo x86_64 2.6.9-42.0.3.mhr > kernel-debuginfo-2.6.9-42.0.3.mhr.x86_64.rpm 961 M > kernel-devel x86_64 2.6.9-42.0.3.mhr > kernel-devel-2.6.9-42.0.3.mhr.x86_64.rpm 11 M > kernel-largesmp x86_64 2.6.9-42.0.3.mhr > kernel-largesmp-2.6.9-42.0.3.mhr.x86_64.rpm 39 M > kernel-smp x86_64 2.6.9-42.0.3.mhr > kernel-smp-2.6.9-42.0.3.mhr.x86_64.rpm 34 M > Updating: > kernel-largesmp-devel x86_64 2.6.9-42.0.3.mhr > kernel-largesmp-devel-2.6.9-42.0.3.mhr.x86_64.rpm 11 M > kernel-smp-devel x86_64 2.6.9-42.0.3.mhr > kernel-smp-devel-2.6.9-42.0.3.mhr.x86_64.rpm 11 M > > Transaction Summary >=======================================================================> ====> Install 5 Package(s)> Update 2 Package(s) > Remove 0 Package(s) > Total download size: 1.1 G > Is this ok [y/N]: N > Exiting on user Command > Complete! > [root at localhost x86_64]# > > Since this is going to update the two *-devel packages, I need to know > if this is safe to do, i.e., will this damage anything I need to get > back to if the new installed kernel doesn't boot or work right (even > though rpm says it's the same one)?The -devel packages should have nothing to do with booting (unless you have dkms packages installed that want to rebuild drivers at boot time - not standard CentOS stuff). If you want to install rather than update the "-devel" packages, put the following (or something like it tailored to your preferences) in /etc/yum.conf: installonlypkgs=kernel kernel-smp kernel-largesmp kernel-devel kernel-smp-devel kernel-largesmp-devel Phil _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos