|
Home > Archive > Red Hat Kernel > January 2004 > kernel make install fails, cannot find aic7xxx module?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
kernel make install fails, cannot find aic7xxx module?
|
|
| Aviram Carmi 2004-01-23, 7:28 pm |
| Hi all,
I am trying to compile the kernel from the RPM source tree (Red Hat 9
RH9)
main reason is to try and install lm_sensors and i2c in my system (IBM
xSeries 220) I had to tweak the code for lm_senesors, since it will not
run on any IBM mother boards because of issues with the ThinkPad
EPROM, which does not apply to my server...
so I cd to /usr/src/linux-2.4
make mrproper
make xconfig
[might as well customize to my system, so I went over all the options
and hopefully selected/de-selected all the right choices... I chose to
not install any modules other than the i2c, i.e. all the options I
selected are compiled right into the kernel. I de-selected a lot of
option that do not apply to my machine, no audio, no PC card, etc.]
make bzImage
[initially gave me some compile errors, so I just de-selected an option
that was not needed anyway, still strange that it gave compile
errors...]
make modules
[initially gave me some compile errors for on of the i2c modules, so I
de-selected that one module]
make modules_install
make install
[fails with this message, even though aic7xxx is supposedly compiled
into the kernel, and is not a module]
tools/build -b bbootsect bsetup compressed/bvmlinux.out CURRENT >
bzImage
Root device is (8, 3)
Boot sector 512 bytes.
Setup is 2611 bytes.
System is 1498 kB
warning: kernel is too big for standalone boot from floppy
sh -x ./install.sh 2.4.20-20.9avi bzImage
/usr/src/linux-2.4.20-20.9/System.map ""
+ '[' -x /root/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
+ exec /sbin/installkernel 2.4.20-20.9avi bzImage
/usr/src/linux-2.4.20-20.9/System.map ''
No module aic7xxx found for kernel 2.4.20-20.9avi
mkinitrd failed
make[1]: *** [install] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.20-20.9/arch/i386/boot'
make: *** [install] Error 2
[root@ns4 linux-2.4]#
The interesting part is that if I go back to make mrproper/make xconfig,
and select the aic7xxx as a module, it works just fine.
do I have to have the aic7xxx as a module?
is there any advantage of modules vs compiling into the kernel?
Thanks,
-avi
| |
| Keith Clark 2004-01-23, 7:28 pm |
| RedHat source RPMs don't compile for some time now. Don't waste your time
on them. I can't get the Adaptec source to compile as either built-in or
modules.
Go to www.kernel.org and download the full source and comple that and
you'll be fine, I've been doing that for quite a while. I have two scsi
controllers dependent on the aic7xxx module.
--Keith
On Fri, 24 Oct 2003 14:27:39 -0700, Aviram Carmi wrote:
quote:
> Hi all,
>
> I am trying to compile the kernel from the RPM source tree (Red Hat 9
> RH9)
>
> main reason is to try and install lm_sensors and i2c in my system (IBM
> xSeries 220) I had to tweak the code for lm_senesors, since it will not
> run on any IBM mother boards because of issues with the ThinkPad
> EPROM, which does not apply to my server...
>
> so I cd to /usr/src/linux-2.4
>
> make mrproper
>
> make xconfig
> [might as well customize to my system, so I went over all the options
> and hopefully selected/de-selected all the right choices... I chose to
> not install any modules other than the i2c, i.e. all the options I
> selected are compiled right into the kernel. I de-selected a lot of
> option that do not apply to my machine, no audio, no PC card, etc.]
>
> make bzImage
> [initially gave me some compile errors, so I just de-selected an option
> that was not needed anyway, still strange that it gave compile
> errors...]
>
> make modules
> [initially gave me some compile errors for on of the i2c modules, so I
> de-selected that one module]
>
> make modules_install
>
> make install
>
> [fails with this message, even though aic7xxx is supposedly compiled
> into the kernel, and is not a module]
>
> tools/build -b bbootsect bsetup compressed/bvmlinux.out CURRENT >
> bzImage
> Root device is (8, 3)
> Boot sector 512 bytes.
> Setup is 2611 bytes.
> System is 1498 kB
> warning: kernel is too big for standalone boot from floppy
> sh -x ./install.sh 2.4.20-20.9avi bzImage
> /usr/src/linux-2.4.20-20.9/System.map ""
> + '[' -x /root/bin/installkernel ']'
> + '[' -x /sbin/installkernel ']'
> + exec /sbin/installkernel 2.4.20-20.9avi bzImage
> /usr/src/linux-2.4.20-20.9/System.map ''
> No module aic7xxx found for kernel 2.4.20-20.9avi
> mkinitrd failed
> make[1]: *** [install] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.4.20-20.9/arch/i386/boot'
> make: *** [install] Error 2
> [root@ns4 linux-2.4]#
>
> The interesting part is that if I go back to make mrproper/make xconfig,
> and select the aic7xxx as a module, it works just fine.
>
> do I have to have the aic7xxx as a module?
>
> is there any advantage of modules vs compiling into the kernel?
>
> Thanks,
>
> -avi
| |
| Alexander Dalloz 2004-01-23, 7:28 pm |
| Keith Clark <clarkphotography@hotmail.com> wrote:
quote:
> RedHat source RPMs don't compile for some time now. Don't waste your time
> on them. I can't get the Adaptec source to compile as either built-in or
> modules.
That is not true. On my Redhat 9 the kernel compiled well, even with the
aic7xxx module (old and new):
/lib/modules/2.4.20-20.9ad/kernel/drivers/scsi/aic7xxx_old.o
/lib/modules/2.4.20-20.9ad/kernel/drivers/scsi/aic7xxx
/lib/modules/2.4.20-20.9ad/kernel/drivers/scsi/aic7xxx/aic79xx.o
/lib/modules/2.4.20-20.9ad/kernel/drivers/scsi/aic7xxx/aic7xxx.o
quote:
> Go to www.kernel.org and download the full source and comple that and
> you'll be fine, I've been doing that for quite a while. I have two scsi
> controllers dependent on the aic7xxx module.
Then you will loose all patches from Redhat.
quote:
> --Keith
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| Keith Clark 2004-01-23, 7:28 pm |
| On Sat, 25 Oct 2003 18:13:49 +0200, Alexander Dalloz wrote:
quote:
> Keith Clark <clarkphotography@hotmail.com> wrote:
>
>
> That is not true. On my Redhat 9 the kernel compiled well, even with the
> aic7xxx module (old and new):
>
> /lib/modules/2.4.20-20.9ad/kernel/drivers/scsi/aic7xxx_old.o
> /lib/modules/2.4.20-20.9ad/kernel/drivers/scsi/aic7xxx
> /lib/modules/2.4.20-20.9ad/kernel/drivers/scsi/aic7xxx/aic79xx.o
> /lib/modules/2.4.20-20.9ad/kernel/drivers/scsi/aic7xxx/aic7xxx.o
>
>
> Then you will loose all patches from Redhat.
>
>
> Alexander
It *is* true. Just because one kernel version copiles proves nothing. Talk
to me again when you've tried 20 different ones.
Some RedHat kernels compile and some don't. I got one of their 2.6
versions to compile, then they did something to break the next version. I
got so frustrated with their broken cr@p I stopped trying to compile it a
long time ago.
The pure source from kernel.org *always* compiles, so RedHat can do
whatever they want. I have better things to do with my time than figure
out why their kernels don't compile so many times while "pure" kernels
compile fine.
So what's the point of "losing RedHat pathes" and why should I care? Do
you even know exactly what they do? Besides, patches are generally
released back to the kernel maintainers, so if the pacthes are deemed to
be good by someone besides RedHat, they'll be adopted in the source @
kernel.org anyway, as I understand it. Big whoop. The up-to-date approved
pathes are always at kernel.org.
|
|
|
|
|