I am having trouble compiling kernel 2.4.24 (kernel.org source code).
I am starting with a fresh rh9 installation (kernel 2.4.20-8).

from within /usr/src/linux-2.4.24, I run:
make menuconfig # this works and creates my .config file
make dep # this appears to work

then,
make bzimage # returns the following

make: *** No rule to make target `bzimage'. Stop.

any ideas as to why this is happening?

Peter

PM uttered the immortal words:

> make: *** No rule to make target `bzimage'. Stop.

IIRC it's "make bzImage" with a capital I.

--
Andy.

PM wrote:
> I am having trouble compiling kernel 2.4.24 (kernel.org source code).
> I am starting with a fresh rh9 installation (kernel 2.4.20-8).
>
> from within /usr/src/linux-2.4.24, I run:
> make menuconfig # this works and creates my .config file
> make dep # this appears to work
>
> then,
> make bzimage # returns the following
>
> make: *** No rule to make target `bzimage'. Stop.
>
> any ideas as to why this is happening?

make mrproper
make menuconfig
make dep
make clean
make bzImage <<< Notice the capital letter "I"
make modules
make modules_install

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.24 SMP i686 (GCC) 3.3.2
Uptime: 41 days, 3:32, 3 users, load average: 0.72, 1.13, 0.9

"David" <thunderbolt01@netscape.net> wrote in message
news:NURXb.42924$uV3.79089@attbi_s51...
> PM wrote:
> > I am having trouble compiling kernel 2.4.24 (kernel.org source code).
> > I am starting with a fresh rh9 installation (kernel 2.4.20-8).
> >
> > from within /usr/src/linux-2.4.24, I run:
> > make menuconfig # this works and creates my .config file
> > make dep # this appears to work
> >
> > then,
> > make bzimage # returns the following
> >
> > make: *** No rule to make target `bzimage'. Stop.
> >
> > any ideas as to why this is happening?
>
> make mrproper
> make menuconfig
> make dep
> make clean
> make bzImage <<< Notice the capital letter "I"
> make modules
> make modules_install

Or stop trying to outsmart it and use "make all" and "make install", which
do it automatically for you. Remember to first edit your Makefile to give
your kernel a slightly different name to keep your old kernel around and
keep your modules distinct, though!

David <thunderbolt01@netscape.net> wrote in message news:<NURXb.42924$uV3.79089@attbi_s51>...
> PM wrote:
> > I am having trouble compiling kernel 2.4.24 (kernel.org source code).
> > I am starting with a fresh rh9 installation (kernel 2.4.20-8).
> >
> > from within /usr/src/linux-2.4.24, I run:
> > make menuconfig # this works and creates my .config file
> > make dep # this appears to work
> >
> > then,
> > make bzimage # returns the following
> >
> > make: *** No rule to make target `bzimage'. Stop.
> >
> > any ideas as to why this is happening?
>
> make mrproper
> make menuconfig
> make dep
> make clean
> make bzImage <<< Notice the capital letter "I"
> make modules
> make modules_install

I must be blind!
Thanks.
I have another question. When I compile the source that comes with my
distribution (rh9) everthing works fine. I have tried to compile
2.4.24 & 2.6.1 that I downloaded from kernel.org and:

make mrproper \
make menuconfig \
make dep \
make clean \ these all appear "o.k."
make bzImage /
make modules /
make modules_install /

but when I do make install I get the following:

No module 3w-xxxx found for kernel 2.4.24
mkinitrd failed
make[1]: ***[install] Error 1
make[1]: Leaving directory '/usr/src/linux-2.4.24/arch/i386/boot'
make: *** [install] Error 2

Some advice or direction as to where to find the info will be greatly
appreciated.

Pete

PM wrote:
> David <thunderbolt01@netscape.net> wrote in message news:<NURXb.42924$uV3.79089@attbi_s51>...
>
>>PM wrote:
>>
>>>I am having trouble compiling kernel 2.4.24 (kernel.org source code).
>>>I am starting with a fresh rh9 installation (kernel 2.4.20-8).
>>>
>>>from within /usr/src/linux-2.4.24, I run:
>>>make menuconfig # this works and creates my .config file
>>>make dep # this appears to work
>>>
>>>then,
>>>make bzimage # returns the following
>>>
>>>make: *** No rule to make target `bzimage'. Stop.
>>>
>>>any ideas as to why this is happening?
>>
>>make mrproper
>>make menuconfig
>>make dep
>>make clean
>>make bzImage <<< Notice the capital letter "I"
>>make modules
>>make modules_install
>
>
> I must be blind!
> Thanks.
> I have another question. When I compile the source that comes with my
> distribution (rh9) everthing works fine. I have tried to compile
> 2.4.24 & 2.6.1 that I downloaded from kernel.org and:
>
> make mrproper \
> make menuconfig \
> make dep \
> make clean \ these all appear "o.k."
> make bzImage /
> make modules /
> make modules_install /
>
> but when I do make install I get the following:
>
> No module 3w-xxxx found for kernel 2.4.24
> mkinitrd failed
> make[1]: ***[install] Error 1
> make[1]: Leaving directory '/usr/src/linux-2.4.24/arch/i386/boot'
> make: *** [install] Error 2
>
> Some advice or direction as to where to find the info will be greatly
> appreciated.
>
> Pete
Why bother? Just type
cp arch/i386/boot/bzImage /boot/linux-2.4.24-2

--
copyright is copywrong
copyleft is copyright

PM wrote:
>
> I must be blind!
> Thanks.
> I have another question. When I compile the source that comes with my
> distribution (rh9) everthing works fine. I have tried to compile
> 2.4.24 & 2.6.1 that I downloaded from kernel.org and:
>
> make mrproper \
> make menuconfig \
> make dep \
> make clean \ these all appear "o.k."
> make bzImage /
> make modules /
> make modules_install /
>
> but when I do make install I get the following:
>
> No module 3w-xxxx found for kernel 2.4.24
> mkinitrd failed
> make[1]: ***[install] Error 1
> make[1]: Leaving directory '/usr/src/linux-2.4.24/arch/i386/boot'
> make: *** [install] Error 2
>
> Some advice or direction as to where to find the info will be greatly
> appreciated.

Install the kernel manually. You have already installed the modules.

cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.24
cp System.map /boot/System.map-2.4.24

Edit /etc/lilo.conf or grub.conf and add the new kernel to it.
DO NOT remove the old kernel until you know the new one works.
Especially if you don't know how to fix it if the new one fails
to boot.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.25 SMP i686 (GCC) 3.3.3
Uptime: 22:28, 3 users, load average: 0.01, 0.07, 0.19

David <thunderbolt01@netscape.net> wrote in message news:<SzeZb.348316$I06.3676463@attbi_s01>...
> PM wrote:
> >
> > I must be blind!
> > Thanks.
> > I have another question. When I compile the source that comes with my
> > distribution (rh9) everthing works fine. I have tried to compile
> > 2.4.24 & 2.6.1 that I downloaded from kernel.org and:
> >
> > make mrproper \
> > make menuconfig \
> > make dep \
> > make clean \ these all appear "o.k."
> > make bzImage /
> > make modules /
> > make modules_install /
> >
> > but when I do make install I get the following:
> >
> > No module 3w-xxxx found for kernel 2.4.24
> > mkinitrd failed
> > make[1]: ***[install] Error 1
> > make[1]: Leaving directory '/usr/src/linux-2.4.24/arch/i386/boot'
> > make: *** [install] Error 2
> >
> > Some advice or direction as to where to find the info will be greatly
> > appreciated.
>
> Install the kernel manually. You have already installed the modules.
>
> cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.24
> cp System.map /boot/System.map-2.4.24
>
> Edit /etc/lilo.conf or grub.conf and add the new kernel to it.
> DO NOT remove the old kernel until you know the new one works.
> Especially if you don't know how to fix it if the new one fails
> to boot.

I will definitely be keep old working kernel(s) even after the new
works (especially when I am testing a few things our).

I now get the following error message:
VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic. VFS: Unable to mount root fs on 00:00.


I am noticing a theme here...most of my docs suggests exactly what you
advised me to do but I see no mention of an initrd.img file. I have
found that if I remove the initrd line in grub.conf, I made a working
kernel have the exact same kernel panic.
Is there something in the kernel config that I can do to resolve this?
Is it as simple as setting the root= in grub.conf?
Should I look to rdev?
Am I even going in the right direction with this?
Thanks for your suggestions.

Pete

pmorfidis@yahoo.com (PM) wrote in message news:<849b291e.0402201135.4bb709ca@posting.google. com>...
> David <thunderbolt01@netscape.net> wrote in message news:<SzeZb.348316$I06.3676463@attbi_s01>...
> > PM wrote:
> > >
> > > I must be blind!
> > > Thanks.
> > > I have another question. When I compile the source that comes with my
> > > distribution (rh9) everthing works fine. I have tried to compile
> > > 2.4.24 & 2.6.1 that I downloaded from kernel.org and:
> > >
> > > make mrproper \
> > > make menuconfig \
> > > make dep \
> > > make clean \ these all appear "o.k."
> > > make bzImage /
> > > make modules /
> > > make modules_install /
> > >
> > > but when I do make install I get the following:
> > >
> > > No module 3w-xxxx found for kernel 2.4.24
> > > mkinitrd failed
> > > make[1]: ***[install] Error 1
> > > make[1]: Leaving directory '/usr/src/linux-2.4.24/arch/i386/boot'
> > > make: *** [install] Error 2
> > >
> > > Some advice or direction as to where to find the info will be greatly
> > > appreciated.
> >
> > Install the kernel manually. You have already installed the modules.
> >
> > cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.24
> > cp System.map /boot/System.map-2.4.24
> >
> > Edit /etc/lilo.conf or grub.conf and add the new kernel to it.
> > DO NOT remove the old kernel until you know the new one works.
> > Especially if you don't know how to fix it if the new one fails
> > to boot.
>
> I will definitely be keep old working kernel(s) even after the new
> works (especially when I am testing a few things our).
>
> I now get the following error message:
> VFS: Cannot open root device "LABEL=/" or 00:00
> Please append a correct "root=" boot option
> Kernel panic. VFS: Unable to mount root fs on 00:00.
>
>
> I am noticing a theme here...most of my docs suggests exactly what you
> advised me to do but I see no mention of an initrd.img file. I have
> found that if I remove the initrd line in grub.conf, I made a working
> kernel have the exact same kernel panic.
> Is there something in the kernel config that I can do to resolve this?
> Is it as simple as setting the root= in grub.conf?
> Should I look to rdev?
> Am I even going in the right direction with this?
> Thanks for your suggestions.
>
> Pete

I got it working by setting root=/dev/sda2 and it works fine.

Thanks for all your help.

Pete

PM wrote:
> David <thunderbolt01@netscape.net> wrote in message news:<SzeZb.348316$I06.3676463@attbi_s01>...
>
>>PM wrote:
>>
>>>I must be blind!
>>>Thanks.
>>>I have another question. When I compile the source that comes with my
>>>distribution (rh9) everthing works fine. I have tried to compile
>>>2.4.24 & 2.6.1 that I downloaded from kernel.org and:
>>>
>>>make mrproper \
>>>make menuconfig \
>>>make dep \
>>>make clean \ these all appear "o.k."
>>>make bzImage /
>>>make modules /
>>>make modules_install /
>>>
>>>but when I do make install I get the following:
>>>
>>>No module 3w-xxxx found for kernel 2.4.24
>>>mkinitrd failed
>>>make[1]: ***[install] Error 1
>>>make[1]: Leaving directory '/usr/src/linux-2.4.24/arch/i386/boot'
>>>make: *** [install] Error 2
>>>
>>>Some advice or direction as to where to find the info will be greatly
>>>appreciated.
>>
>>Install the kernel manually. You have already installed the modules.
>>
>>cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.24
>>cp System.map /boot/System.map-2.4.24
>>
>>Edit /etc/lilo.conf or grub.conf and add the new kernel to it.
>>DO NOT remove the old kernel until you know the new one works.
>>Especially if you don't know how to fix it if the new one fails
>>to boot.
>
>
> I will definitely be keep old working kernel(s) even after the new
> works (especially when I am testing a few things our).
>
> I now get the following error message:
> VFS: Cannot open root device "LABEL=/" or 00:00
> Please append a correct "root=" boot option
> Kernel panic. VFS: Unable to mount root fs on 00:00.
>
>
> I am noticing a theme here...most of my docs suggests exactly what you
> advised me to do but I see no mention of an initrd.img file. I have
> found that if I remove the initrd line in grub.conf, I made a working
> kernel have the exact same kernel panic.
> Is there something in the kernel config that I can do to resolve this?
> Is it as simple as setting the root= in grub.conf?
> Should I look to rdev?
> Am I even going in the right direction with this?
> Thanks for your suggestions.

Just make a new initrd image in the /boot directory. It's been a
while since I used an initrd image but it is something like this.

mkinitrd 2.4.xx # using the correct kernel version of course.

Or if you get an error about raid modules then you add an option
to the command. It is listed in the man pages but I think it was
something like this.

mkinitrd --noraid 2.4.xx

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.25 SMP i686 (GCC) 3.3.3
Uptime: 2 days, 29 min, 3 users, load average: 1.00, 1.04, 1.0