Dear Pete Thanks for pointing out the existence of that config in /boot. I did somehow manage to miss it. Unfortunately though, it has failed to do the trick. It appears to be a generic config to me - not really related to the build of my running kernel 2.4.18-14.
As it happens you referred to the kernel I am trying to leave behind and hence I possess a config by the same name in /boot. > Woah, flashbacks to sluglets on Friday night. :-) > The config is provided in the kernel RPM, as /boot/config-2.4.18-14, or > whichever version you currently have installed. I think that this is a generic config - not a config that is going to assist me recreate a compile of the kernel version 2.4.18-14 for my machine. Is is possible that you could email me your /boot/config-2.4.18-14 so that I can confirm that our configs are merely identical generic starting configs. If they were real working configs then they should be tailored to our individual hardware and in all probability should be quite different. I will certainly let you know if they are the same. I think it is a very important piece of information to know whether or not you have your hands on a genuine copy of the .config that built the kernel from which you are trying to upgrade. It is very important if you run into problems thats for sure. It appears to me that you are under the impression that the .config in /boot is a genuine reflection of your kernel. I am less than convinced of this. I think it is intended merely as a file to get you started. I would really appreciate your assistance. Paul Davies ----- Original Message ----- From: "Peter Hardy" <[EMAIL PROTECTED]> To: "Paul Cameron Davies" <[EMAIL PROTECTED]> Sent: Sunday, August 31, 2003 12:50 PM Subject: Re: [SLUG] Compiling the kernel > On Sun, 2003-08-31 at 12:19, Paul Cameron Davies wrote: > > However with Redhat 8.0 feedback is provided during boot time and it claims > > that the USB mouse has been installed successfully and that mouse services > > have been > > started successfully. The USB mouse still doesn't work though. > > Oh, OK. I'll admit to not being too familiar with how redhat boots. > > > PS: The configs supplied with the kernel are merely a framework to work > > off. > > The kernel was never actually built from one of these sample configs. If it > > was I wouldn't > > be having any problems because I am working from these. I assume that > > during the installation > > process my hardware is probed and the kernel is linked from precompiled > > binaries. It > > doesn't seem to me that they have probed my hardware and compiled and linked > > a kernel during the installation process. Hence no need for .config. > > When you install a binary kernel package (_not_ a source package), it > puts a file in /boot/ containing the configuration that kernel was > compiled with. > > For example, the Redhat 9 installation I built and ran in a virtual > machine for my sluglets talk on Friday night has kernel 2.4.21 > installed. Checking the contents of the kernel package: > [EMAIL PROTECTED] peter]$ rpm -q -l kernel-2.4.21 > /boot/System.map-2.4.21 > /boot/config-2.4.21 > /boot/vmlinuz-2.4.21 > > And I can confirm the config-2.4.21 is identical to the .config file I > used when compiling the kernel. Before sending my mail, I downloaded > the latest redhat 8 kernel from a RH mirror and extracted its contents > to check it had a similar file. > > Redhat generally build their kernels with pretty much every available > driver compiled as modules. Somewhere during the install or boot > process, hardware is probed and appropriate modules loaded. So yeah, > you were fairly close there. :-) > > Cheers, > -- > Pete > > -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
