Hi all, I hope this is not too off topic. I've searched the -devel archives, but haven't found clear-cut information on this, so thought I'd ask.
I am trying to determine the kernel configuration used to build the kernel used on the installation media (CD #1 or the vmlinuz/initrd.img files in their respective images/boot.iso or images/diskboot.img files).
My guess is the kernel configurations are not identical to the ones ultimately used to build the kernels used on the system once it is up and running....
I ask because I am interested in rebuilding the kernel used on CD #1 to boot into the installer.
Thanks for any pointers.
Ray
Am Donnerstag, den 22.02.2007, 17:42 -0800 schrieb Ray Van Dolson:
Hi all, I hope this is not too off topic. I've searched the -devel archives, but haven't found clear-cut information on this, so thought I'd ask.
I am trying to determine the kernel configuration used to build the kernel used on the installation media (CD #1 or the vmlinuz/initrd.img files in their respective images/boot.iso or images/diskboot.img files).
My guess is the kernel configurations are not identical to the ones ultimately used to build the kernels used on the system once it is up and running....
I ask because I am interested in rebuilding the kernel used on CD #1 to boot into the installer.
Thanks for any pointers.
Ray
I can only point you to the anaconda-runtime package. I know I used it som time ago to do what you want to do now. I cannot tell you how to use it thought, since i don't know it anymore. But i bet the docs in the RPM and some googling will give you everything you need.
Chris
On 2/22/07, Ray Van Dolson rvandolson@esri.com wrote:
Hi all, I hope this is not too off topic. I've searched the -devel archives, but haven't found clear-cut information on this, so thought I'd ask.
I am trying to determine the kernel configuration used to build the kernel used on the installation media (CD #1 or the vmlinuz/initrd.img files in their respective images/boot.iso or images/diskboot.img files).
My guess is the kernel configurations are not identical to the ones ultimately used to build the kernels used on the system once it is up and running....
I suspect, if your referring to Centos 4.x it is the same as the kernel-smp kernel. Before RHEL 4, there was a kernel-BOOT kernel and that is what anaconda used, but it is not built anymore.
Note, though, I'm only telling you what I suspect and not what I know for a fact. If you posted this question on the anaconda-devel list someone there would know the answer for sure.
Cheers...james
On Fri, Feb 23, 2007 at 10:38:18AM -0500, James Olin Oden wrote:
I suspect, if your referring to Centos 4.x it is the same as the kernel-smp kernel. Before RHEL 4, there was a kernel-BOOT kernel and that is what anaconda used, but it is not built anymore.
Pretty sure the installer uses the non-smp kernel.
On 2/23/07, Matthew Miller mattdm@mattdm.org wrote:
On Fri, Feb 23, 2007 at 10:38:18AM -0500, James Olin Oden wrote:
I suspect, if your referring to Centos 4.x it is the same as the kernel-smp kernel. Before RHEL 4, there was a kernel-BOOT kernel and that is what anaconda used, but it is not built anymore.
Pretty sure the installer uses the non-smp kernel.
Well sure is much better than suspect, so I'd go with that (-:
Thanks...james
-- Matthew Miller mattdm@mattdm.org http://mattdm.org/ Boston University Linux ------> http://linux.bu.edu/ _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
James Olin Oden spake the following on 2/23/2007 10:09 AM:
On 2/23/07, Matthew Miller mattdm@mattdm.org wrote:
On Fri, Feb 23, 2007 at 10:38:18AM -0500, James Olin Oden wrote:
I suspect, if your referring to Centos 4.x it is the same as the kernel-smp kernel. Before RHEL 4, there was a kernel-BOOT kernel and that is what anaconda used, but it is not built anymore.
Pretty sure the installer uses the non-smp kernel.
Well sure is much better than suspect, so I'd go with that (-:
Thanks...james
Doesn't the rescue system use the same kernel as the installer? If so, you could uname -a from a prompt in the rescue system.
On Fri, Feb 23, 2007 at 02:58:51PM -0800, Scott Silva wrote:
James Olin Oden spake the following on 2/23/2007 10:09 AM:
On 2/23/07, Matthew Miller mattdm@mattdm.org wrote:
On Fri, Feb 23, 2007 at 10:38:18AM -0500, James Olin Oden wrote:
I suspect, if your referring to Centos 4.x it is the same as the kernel-smp kernel. Before RHEL 4, there was a kernel-BOOT kernel and that is what anaconda used, but it is not built anymore.
Pretty sure the installer uses the non-smp kernel.
Well sure is much better than suspect, so I'd go with that (-:
Thanks...james
Doesn't the rescue system use the same kernel as the installer? If so, you could uname -a from a prompt in the rescue system.
True! I'm just going to try the normal kernel configs and see what happens. :)
Ray Van Dolson wrote:
Hi all, I hope this is not too off topic. I've searched the -devel archives, but haven't found clear-cut information on this, so thought I'd ask.
I am trying to determine the kernel configuration used to build the kernel used on the installation media (CD #1 or the vmlinuz/initrd.img files in their respective images/boot.iso or images/diskboot.img files).
My guess is the kernel configurations are not identical to the ones ultimately used to build the kernels used on the system once it is up and running....
I ask because I am interested in rebuilding the kernel used on CD #1 to boot into the installer.
look in the distro tree : http://mirror.centos.org/centos/4/os/i386/CentOS/RPMS ( eg, for the i386 ) the kernel-2.6.9-*.<i686|i586>.rpm are the ones used for the installer, each contain a .config file which will give you the config file used at build time for that kernel rpm.
Why do you need to rebuild the installer kernel ? doing DriverDisks for some piece of non-supported-by-default-hardware isnt hard.
On Sat, Feb 24, 2007 at 12:06:03AM +0000, Karanbir Singh wrote:
Ray Van Dolson wrote:
Hi all, I hope this is not too off topic. I've searched the -devel archives, but haven't found clear-cut information on this, so thought I'd ask.
I am trying to determine the kernel configuration used to build the kernel used on the installation media (CD #1 or the vmlinuz/initrd.img files in their respective images/boot.iso or images/diskboot.img files).
My guess is the kernel configurations are not identical to the ones ultimately used to build the kernels used on the system once it is up and running....
I ask because I am interested in rebuilding the kernel used on CD #1 to boot into the installer.
look in the distro tree : http://mirror.centos.org/centos/4/os/i386/CentOS/RPMS ( eg, for the i386 ) the kernel-2.6.9-*.<i686|i586>.rpm are the ones used for the installer, each contain a .config file which will give you the config file used at build time for that kernel rpm.
K, so just the same kernel then that's used on the OS. That makes it fairly straightforward.
Why do you need to rebuild the installer kernel ? doing DriverDisks for some piece of non-supported-by-default-hardware isnt hard.
Well, the driver is an updated ata_piix and libsata driver for the ICH8 chipset. Neither Intel nor Dell appears to have a driver for download on their page.
jbaron's beta release of the -48 kernel for RHEL4 includes driver support for it, but obviously the .ko's in his kernel are for the -48 kernel. I would either have to backport the driver to the kernel used on the U4/CentOS install CD's or update the kernel on those CD's to be -48 and work with the new drivers out of the box.
I haven't taken a stab at backporting these drivers into the current stable kernels (and kernel used on the boot CD), maybe that would be easier...
Ray Van Dolson spake the following on 2/23/2007 4:18 PM:
On Sat, Feb 24, 2007 at 12:06:03AM +0000, Karanbir Singh wrote:
Ray Van Dolson wrote:
Hi all, I hope this is not too off topic. I've searched the -devel archives, but haven't found clear-cut information on this, so thought I'd ask.
I am trying to determine the kernel configuration used to build the kernel used on the installation media (CD #1 or the vmlinuz/initrd.img files in their respective images/boot.iso or images/diskboot.img files).
My guess is the kernel configurations are not identical to the ones ultimately used to build the kernels used on the system once it is up and running....
I ask because I am interested in rebuilding the kernel used on CD #1 to boot into the installer.
look in the distro tree : http://mirror.centos.org/centos/4/os/i386/CentOS/RPMS ( eg, for the i386 ) the kernel-2.6.9-*.<i686|i586>.rpm are the ones used for the installer, each contain a .config file which will give you the config file used at build time for that kernel rpm.
K, so just the same kernel then that's used on the OS. That makes it fairly straightforward.
Why do you need to rebuild the installer kernel ? doing DriverDisks for some piece of non-supported-by-default-hardware isnt hard.
Well, the driver is an updated ata_piix and libsata driver for the ICH8 chipset. Neither Intel nor Dell appears to have a driver for download on their page.
jbaron's beta release of the -48 kernel for RHEL4 includes driver support for it, but obviously the .ko's in his kernel are for the -48 kernel. I would either have to backport the driver to the kernel used on the U4/CentOS install CD's or update the kernel on those CD's to be -48 and work with the new drivers out of the box.
I haven't taken a stab at backporting these drivers into the current stable kernels (and kernel used on the boot CD), maybe that would be easier...
See if you can get a src rpm. He probably added that patch the "approved" RedHat way, and it should be in the src rpm. You could add it to the current src and check at what point the .spec file adds that patch. Then just build and see.
Ray Van Dolson wrote:
jbaron's beta release of the -48 kernel for RHEL4 includes driver support for it, but obviously the .ko's in his kernel are for the -48 kernel. I would either have to backport the driver to the kernel used on the U4/CentOS install CD's or update the kernel on those CD's to be -48 and work with the new drivers out of the box.
I haven't taken a stab at backporting these drivers into the current stable kernels (and kernel used on the boot CD), maybe that would be easier...
you might want to readup on how EL/CentOS kernels work w.r.t KABI/VerMagic
Also, have you actually *tried* using the .ko's ? :) you might need more than just the .ko itself ( like, the dep chain )
On Fri, 2007-02-23 at 16:18 -0800, Ray Van Dolson wrote:
On Sat, Feb 24, 2007 at 12:06:03AM +0000, Karanbir Singh wrote:
Ray Van Dolson wrote:
Hi all, I hope this is not too off topic. I've searched the -devel archives, but haven't found clear-cut information on this, so thought I'd ask.
I am trying to determine the kernel configuration used to build the kernel used on the installation media (CD #1 or the vmlinuz/initrd.img files in their respective images/boot.iso or images/diskboot.img files).
My guess is the kernel configurations are not identical to the ones ultimately used to build the kernels used on the system once it is up and running....
I ask because I am interested in rebuilding the kernel used on CD #1 to boot into the installer.
look in the distro tree : http://mirror.centos.org/centos/4/os/i386/CentOS/RPMS ( eg, for the i386 ) the kernel-2.6.9-*.<i686|i586>.rpm are the ones used for the installer, each contain a .config file which will give you the config file used at build time for that kernel rpm.
K, so just the same kernel then that's used on the OS. That makes it fairly straightforward.
Why do you need to rebuild the installer kernel ? doing DriverDisks for some piece of non-supported-by-default-hardware isnt hard.
Well, the driver is an updated ata_piix and libsata driver for the ICH8 chipset. Neither Intel nor Dell appears to have a driver for download on their page.
jbaron's beta release of the -48 kernel for RHEL4 includes driver support for it, but obviously the .ko's in his kernel are for the -48 kernel. I would either have to backport the driver to the kernel used on the U4/CentOS install CD's or update the kernel on those CD's to be -48 and work with the new drivers out of the box.
I haven't taken a stab at backporting these drivers into the current stable kernels (and kernel used on the boot CD), maybe that would be easier...
Just for the record ... the ko's will work across kernels because they can be inserted by just doing depmod -a as long as the are built by the same major gcc (3.4) and this is the same major kernel (2.6.9) and the same type (normal, smp, hughmem, largesmp).
BUT .. you really need to rebuild the initrd that does the isntall to, as well as use that newer kernel (there are going to most likely be pieces missing in the older kernel that the new module needs) ... but who knows, you might get lucky :P
-
Christoph Maser -
James Olin Oden -
Johnny Hughes -
Karanbir Singh -
Matthew Miller -
Ray Van Dolson -
Scott Silva