Mailing List Archive

On Thursday 21 July 2005 13:39, Shahzad Chohan wrote:

> Can someone help me figure out a way to compile a 2.4 kernel in a 2.6
> system. Basically it keeps failing because it needs the genksyms
> package, which is provided in the modutils package from redhat, but
> obviously this isn't presetn on the 2.6 kernel.

Well, genksyms is present on my 2.6 systems, so I'd say redhat is at fault
here for not providing it any more. (or they did it intentionally to prevent
ppl from running old 2.4 kernels with their new distros)

If you install genksyms, does the kernel compile then?

Does your distro run at all with a 2.4 kernel? depending on how they
configured their glibc, it might not even start with a 2.4 kernel...


/Ernst

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 7/21/05, Ernst Bachmann <e.bachmann@xebec.de> wrote:
> On Thursday 21 July 2005 13:39, Shahzad Chohan wrote:
>
> > Can someone help me figure out a way to compile a 2.4 kernel in a 2.6
> > system. Basically it keeps failing because it needs the genksyms
> > package, which is provided in the modutils package from redhat, but
> > obviously this isn't presetn on the 2.6 kernel.
>
> Well, genksyms is present on my 2.6 systems, so I'd say redhat is at fault
> here for not providing it any more. (or they did it intentionally to prevent
> ppl from running old 2.4 kernels with their new distros)
>
> If you install genksyms, does the kernel compile then?
>
> Does your distro run at all with a 2.4 kernel? depending on how they
> configured their glibc, it might not even start with a 2.4 kernel...
>

Hi

Thanks for the reply.

To be honest I just want the 2.4 xenU. This isn't available from the
unstbale tree by default, so I have to compile it. I've got rhel 4
(similar to fc 3) and redhat haven't provided the genksyms package.
The problem I have if I install the modutils package its going to
overwrite the pakages (e.g lsmod,rmod etc) that are needed for the 2.6
kernel. Is there a way to just retrieve the genksyms package?

Thanks
Shaz

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi,

> Basically it keeps failing because it needs the genksyms
> package, which is provided in the modutils package from redhat, but
> obviously this isn't presetn on the 2.6 kernel.

Have a look at:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=162195

Basically, they moved genksyms to the "kernel-devel" package, and the file is
in "/lib/modules/$(uname -r)/build/scripts/genksyms" now... symlinking it
from there into the $PATH might fix the xen kernel makefiles.

/Ernst

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Shahzad Chohan wrote:

> Can someone help me figure out a way to compile a 2.4 kernel in a 2.6
> system. Basically it keeps failing because it needs the genksyms
> package, which is provided in the modutils package from redhat, but
> obviously this isn't presetn on the 2.6 kernel.

genksyms comes from the modutils package. Either install modutils from
RPM or compile it from source:
http://www.kernel.org/pub/linux/utils/kernel/modutils/

Beware that 2.4 kernel doesn't play well with module-init-tools. You'll
need to have both modutils and module-init-tools installed, while e.g.
/sbin/modprobe will come from m-i-tools and /sbin/modprobe.old will be
the one of modutils. Ditto for insmod, depmod, rmmod, lsmod.

Michal Ludvig
--
* Personal homepage: http://www.logix.cz/michal

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 7/21/05, Ernst Bachmann <e.bachmann@xebec.de> wrote:
> Hi,
>
> > Basically it keeps failing because it needs the genksyms
> > package, which is provided in the modutils package from redhat, but
> > obviously this isn't presetn on the 2.6 kernel.
>
> Have a look at:
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=162195
>
> Basically, they moved genksyms to the "kernel-devel" package, and the file is
> in "/lib/modules/$(uname -r)/build/scripts/genksyms" now... symlinking it
> from there into the $PATH might fix the xen kernel makefiles.
>

Excellent.

Thanks for that, it really helped.

Now that I've tried compiling it I get the following errors:, any
ideas what this could be?

make[4]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/netif'
make -C arch/xen/drivers/usbif CFLAGS="-D__KERNEL__
-I/root/xen/xen-unstable/linux-2.4.30-xenU/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2
-march=i686 -fno-unit-at-a-time -DMODULE -DMODVERSIONS -include
/root/xen/xen-unstable/linux-2.4.30-xenU/include/linux/modversions.h"
MAKING_MODULES=1 modules
make: *** arch/xen/drivers/usbif: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown
directorymake[3]: *** [_mod_arch/xen/drivers/usbif] Error 2
make[3]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU'
make[3]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU'
make -C kernel modules_install
make[4]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/kernel'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/kernel'
make -C drivers modules_install
make[4]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/drivers'
make -C block modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/block'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/block'
make -C cdrom modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/cdrom'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/cdrom'
make -C char modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/char'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/char'
make -C hotplug modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/hotplug'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/hotplug'
make -C media modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/media'
make -C radio modules_install
make[6]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/media/radio'
make[6]: Nothing to be done for `modules_install'.
make[6]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/media/radio'
make -C video modules_install
make[6]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/media/video'
make[6]: Nothing to be done for `modules_install'.
make[6]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/media/video'
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/media'
make -C misc modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/misc'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/misc'
make -C net modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/net'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/net'
make -C parport modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/parport'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/parport'
make -C scsi modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/scsi'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/scsi'
make -C sound modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/sound'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/drivers/sound'
make[4]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/drivers'
make -C mm modules_install
make[4]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/mm'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/mm'
make -C fs modules_install
make[4]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/fs'
make -C nls modules_install
make[5]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/fs/nls'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/fs/nls'
make[4]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/fs'
make -C net modules_install
make[4]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net'
make -C 802 modules_install
make[5]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net/802'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net/802'
make -C core modules_install
make[5]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net/core'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net/core'
make -C ipv4 modules_install
make[5]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net/ipv4'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net/ipv4'
make -C ipv4/netfilter modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/net/ipv4/netfilter'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/net/ipv4/netfilter'
make -C netlink modules_install
make[5]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/net/netlink'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/net/netlink'
make -C sched modules_install
make[5]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net/sched'
make[5]: Nothing to be done for `modules_install'.
make[5]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net/sched'
make[4]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/net'
make -C ipc modules_install
make[4]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/ipc'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/ipc'
make -C lib modules_install
make[4]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/lib'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/lib'
make -C crypto modules_install
make[4]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU/crypto'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU/crypto'
make -C arch/xen/kernel modules_install
make[4]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/kernel'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/kernel'
make -C arch/xen/mm modules_install
make[4]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/mm'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/mm'
make -C arch/xen/lib modules_install
make[4]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/lib'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/lib'
make -C arch/xen/drivers/console modules_install
make[4]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/console'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/console'
make -C arch/xen/drivers/evtchn modules_install
make[4]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/evtchn'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/evtchn'
make -C arch/xen/drivers/blkif modules_install
make[4]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/blkif'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/blkif'
make -C arch/xen/drivers/netif modules_install
make[4]: Entering directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/netif'
make[4]: Nothing to be done for `modules_install'.
make[4]: Leaving directory
`/root/xen/xen-unstable/linux-2.4.30-xenU/arch/xen/drivers/netif'
make -C arch/xen/drivers/usbif modules_install
make: *** arch/xen/drivers/usbif: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown
directorymake[3]: *** [_modinst_arch/xen/drivers/usbif] Error 2
make[3]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU'
make[2]: *** [build] Error 2
make[2]: Leaving directory `/root/xen/xen-unstable'
make[1]: *** [linux-2.4-xenU-build] Error 2
make[1]: Leaving directory `/root/xen/xen-unstable'
make: *** [kernels] Error 1

Thanks a lot
Shaz

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thursday 21 July 2005 14:15, Shahzad Chohan wrote:
...
> /root/xen/xen-unstable/linux-2.4.30-xenU/include/linux/modversions.h"
> MAKING_MODULES=1 modules
> make: *** arch/xen/drivers/usbif: No such file or directory. Stop.
> make: Entering an unknown directorymake: Leaving an unknown
> directorymake[3]: *** [_mod_arch/xen/drivers/usbif] Error 2
> make[3]: Leaving directory `/root/xen/xen-unstable/linux-2.4.30-xenU'
> make[3]: Entering directory `/root/xen/xen-unstable/linux-2.4.30-xenU'

Looks like a breakage in the sparse kernel tree for 2.4...

Its for a xenU? do you need to share USB devices? If not, disable all that
looks like usb in your kernel config, and retry..

otherwise, you could try to "make -k" and "make -k modules_install"
(-k means: go on even if an error occurs)
and see if the result is bootable...


/Ernst

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users