search for: install_mod_path

...n-xen 6. diff -Naur linux-2.6.12 linux-2.6.12-xen0 > archive/linux-2.6.12-xen0.patch 7. cd linux-2.6.12 8. patch -p1 < ../archive/linux-2.6.12-xen0.patch 9. cd ../ 10. mkdir install 11. cd linux-2.6.12-xen0 12. cp arch/xen/configs/xen0_defconfig .config 13. ARCH=xen; INSTALL_PATH=../install; INSTALL_MOD_PATH=../install 14. export ARCH INSTALL_PATH INSTALL_MOD_PATH 15. make oldconfig 16. make menuconfig 17. make modules But I get an error: CHK include/linux/version.h CC arch/i386/kernel/asm-offsets.s In file included from include/asm-xen/asm/processor.h:18, from include/a...

...default %description LSI MPT Fusion HBA drivers (12gb SAS) %prep %setup set -- * mkdir source mv "$@" source/ mkdir obj %build for flavor in %flavors_to_build; do rm -rf obj/$flavor cp -r source obj/$flavor make -C %{kernel_source $flavor} M=$PWD/obj/$flavor done %install export INSTALL_MOD_PATH=$RPM_BUILD_ROOT export INSTALL_MOD_DIR=extra/%{name} for flavor in %flavors_to_build ; do make -C %{kernel_source $flavor} modules_install \ M=$PWD/obj/$flavor # Cleanup unnecessary kernel-generated module dependency files. find $INSTALL_MOD_PATH/lib/modules -iname 'modules.*' -exec rm...

Hi Am 24.03.20 um 12:59 schrieb Rodrigo Siqueira: > Hi Thomas, > > First of all, thanks for your patch! > > I applied all your series, compiled it, and when I tried > `make INSTALL_MOD_PATH=/PATH/ modules_instal` I got the following > message: > > depmod: ERROR: Cycle detected: drm_kms_helper -> drm -> drm_kms_helper > depmod: ERROR: Found 2 modules in dependency cycles! > make: *** [Makefile:1317: _modinst_post] Error 1 > > I cleaned up my local files...

...-3.0.1]# make linux-2.6-xen-build make -f buildconfigs/mk.linux-2.6-xen build make[1]: Entering directory `/usr/src/xen-3.0.1'' if grep "^CONFIG_MODULES=" linux-2.6.12-xen/.config ; then \ make -C linux-2.6.12-xen ARCH=xen modules ; \ make -C linux-2.6.12-xen ARCH=xen INSTALL_MOD_PATH=/usr/src/xen-3.0.1/dist/install modules_install ; \ fi CONFIG_MODULES=y make[2]: Entering directory `/usr/src/xen-3.0.1/linux-2.6.12-xen'' CHK include/linux/version.h make[3]: `arch/i386/kernel/asm-offsets.s'' is up to date. Building modules, stage 2. MODPOST *** W...

I'm trying to use guestmount to install some kernel modules in a guest: [mbooth at mbooth linux-2.6 (amit)]$ make modules_install INSTALL_MOD_PATH=~/etch ln: creating symbolic link `/home/mbooth/etch/lib/modules/2.6.32-rc6/source': No such file or directory make: *** [_modinst_] Error 1 I think something's screwy with symlinks. In the following, /tmp/source is a symlink, and I have previously attempted to create a source symlink i...

...x in zaptel.ko tor2.ko torisa.ko wcusb.ko wcfxo.ko wctdm.ko wctdm24xxp.ko ztdynamic.ko ztd-eth.ko wct1xxp.ko wcte11xp.ko pciradio.ko ztd-loc.ko ztdummy.ko zttranscode.ko; do \ rm -f /lib/modules/2.6.9-42.0.3.ELsmp/extra/$x ; \ done; \ make -C /usr/src/linux SUBDIRS=/usr/src/zaptel-1.2.13 INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install; make[1]: Entering directory `/usr/src/kernels/2.6.9-42.0.3.EL-i686' INSTALL /usr/src/zaptel-1.2.13/pciradio.ko INSTALL /usr/src/zaptel-1.2.13/tor2.ko INSTALL /usr/src/zaptel-1.2.13/torisa.ko INSTALL /usr/src/zaptel-1.2.13/wcfxo.ko INSTALL /...

...the bzImage with the bzImage from the new kernel. This amounts, after mounting the CF, to just a single ``cp" command. (*) also replace the /lib/modules tree on the CF with the /lib/modules tree from the new kernel. It is convienent to issue the command make modules_install INSTALL_MOD_PATH=<dir> and then remove the /lib/modules tree on the CF and then recursively copy the new tree under <dir>/lib/modules/<kernel-name>/* When I do these steps, and reboot, my system now displays the contents of display.txt (which is part of syslinux) and then appears to...

...arch/x86_64/boot/bzImage /var/tmp/kernel-2.6.18-53.el5.nx-root /boot/vmlinuz-2.6.18-53.el5.nx + '[' -f arch/x86_64/boot/zImage.stub ']' + '[' '' == kdump ']' + mkdir -p /var/tmp/kernel-2.6.18-53.el5.nx-root/lib/modules/2.6.18- 53.el5.nx + make -s ARCH=x86_64 INSTALL_MOD_PATH=/var/tmp/kernel-2.6.18-53.el5.nx-rootmodules_install KERNELRELEASE= 2.6.18-53.el5.nx + echo '**** GENERATING kernel ABI metadata ****' **** GENERATING kernel ABI metadata **** + gzip -c9 + chmod 0755 /home/rpmbuild/SOURCES/kabitool + '[' '!' -e /home/rpmbuild/SOURCES/kabi_wh...

...initramfs by hand (or on another system). A Debian initramfs is generally capable of booting Fedora 8, so I modified that: * I started with initrd.img-2.6.18-5-xen-686 from my Debian lenny dom0, which is for these purposes a fairly vanilla install. * I then copied the results of INSTALL_MOD_PATH=.... make modules_install into the initrd''s /lib/modules alongside the existing modules. * It was necessary to remove many drivers to reduce the size. The Linux startup code silently ignores an initrd if it is `too large''; I don''t know exactly what the threshol...

#!/bin/bash # a small shell script to: # 1) make a simple asm program # 2) compile that program with `nasm' # 3) convert resulting .bin to a .img with `dd' # 4) boot the reulting "hello.img" with qemu/kvm # I think this qualifies as a bootloader, sort of # sincerely hope it helps address Mr. Guilmette curiousity # -chris graff printf ' BITS 16 jmp

Hello! I have problems compiling zaptel (tried 1.2.11, 1.2.10 and 1.4.0-beta2 -- all give the same error) with 2.6.19 kernel CC [M] /home/roman/install/asterisk/zaptel-1.4.0-beta2/xpp/card_fxo.o In file included from /home/roman/install/asterisk/zaptel-1.4.0-beta2/xpp/xpd.h:26, from /home/roman/install/asterisk/zaptel-1.4.0-beta2/xpp/card_fxo.c:28:

Hi, I have successfully installed Xen unstable binary on SuSE 9.3. I am trying to do a source install and I got the following error. Will be glad for any help or guidance. In file included from include/asm-xen/asm/processor.h:18, from include/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from

.../zttool; \ fi for x in pciradio.ko tor2.ko torisa.ko wcfxo.ko wct1xxp.ko wctdm.ko wctdm24xxp.ko wcte11xp.ko wcusb.ko zaptel.ko ztd-eth.ko ztd-loc.ko ztdummy.ko ztdynamic.ko zttranscode.ko; do \ rm -f /lib/modules/2.6.8-2-386/extra/$x ; \ done; \ make -C /usr/src/linux SUBDIRS=/usr/src/zaptel-1.4.0 INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install; \ if [ -f datamods/syncppp.ko ]; then \ make -C datamods install; \ else \ rm -f /lib/modules/2.6.8-2-386/misc/{hdlc_*,syncppp}.ko; \ fi make[1]: Entering directory `/usr/src/kernel-source-2.6.8' INSTALL /usr/src/zaptel-1.4.0/pciradio.ko INSTALL /usr...

A call to drm_simple_encoder_init() initializes an encoder without further functionality. It only provides the destroy callback to cleanup the encoder's state. Only few drivers implement more sophisticated encoders than that. Most drivers implement such a simple encoder and can use drm_simple_encoder_init() instead. The patchset converts drivers where the encoder's instance is embedded in

A call to drm_simple_encoder_init() initializes an encoder without further functionality. It only provides the destroy callback to cleanup the encoder's state. Only few drivers implement more sophisticated encoders than that. Most drivers implement such a simple encoder and can use drm_simple_encoder_init() instead. The patchset converts drivers where the encoder's instance is embedded in

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio