Vmlinux file in lib/modules/ kernel /build
Wasn't really sure if this should be in newbie forum, or kernel forum to be honest! It should be a simple question to answer for someone who compiles their own kernel etc
Can someone please confirm or explain the purpose of this file:
-rw-r--r-- 1 root root 18M May 12 19:56 /usr/lib/modules/3.14.3-2-ARCH/build/vmlinux
As far as I can tell from searching/my own knowledge - I think it is only necessary for compiling new kernel modules associated with the kernel shown in the path. Is that correct, or does it have another use?
At a first glance, I misread it as vmlinuz and assumed it was the kernel, oops!
Look here.
From what I remember, /usr/lib/modules/$(uname -r)/build points to a kernel source which is indeed prepared to build external modules. Prepared in that it it's partially configured which is a requirement for building external modules.
Vmlinuz is your bootable kernel.
Similar Messages
-
[Solved] Kernel 3.2 wont re-patch vmware for new kernel build
Hi, I looked for the same thing and didnt find it, I had vmplayer running great -> enter new kernel 3.2. When it went to build the new modules because the kernel changed it failed with log of:
2012-01-19T06:10:49.389-06:00| vthread-3| I120: Log for VMware Workstation pid=3928 version=8.0.1 build=build-528992 option=Release
2012-01-19T06:10:49.389-06:00| vthread-3| I120: The process is 64-bit.
2012-01-19T06:10:49.389-06:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2012-01-19T06:10:49.388-06:00| vthread-3| I120: Msg_Reset:
2012-01-19T06:10:49.388-06:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2012-01-19T06:10:49.388-06:00| vthread-3| I120: ----------------------------------------
2012-01-19T06:10:49.388-06:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2012-01-19T06:10:49.389-06:00| vthread-3| I120: Msg_Reset:
2012-01-19T06:10:49.389-06:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2012-01-19T06:10:49.389-06:00| vthread-3| I120: ----------------------------------------
2012-01-19T06:10:49.389-06:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/redhat-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/redhat_version: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/sun-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/SuSE-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/novell-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/sles-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/debian_version: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/debian_release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/mandrake-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/mandriva-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/mandrakelinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/turbolinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/fedora-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/gentoo-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/nld-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/lsb-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/annvix-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: Cannot work with empty file.
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/arklinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/aurox-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/blackcat-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/cobalt-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/conectiva-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/immunix-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/knoppix_version: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/lfs-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/linuxppc-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/mklinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/pld-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/slackware-version: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/slackware-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/e-smith-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/tinysofa-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/ultrapenguin-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/UnitedLinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/va-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/yellowdog-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoOSData: Error: no distro file found
2012-01-19T06:10:49.396-06:00| vthread-3| W110: Logging to /tmp/vmware-root/modconfig-3928.log
2012-01-19T06:10:49.497-06:00| vthread-3| I120: modconf query interface initialized
2012-01-19T06:10:49.498-06:00| vthread-3| I120: modconf library initialized
2012-01-19T06:10:49.544-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.548-06:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.548-06:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-01-19T06:10:49.548-06:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-01-19T06:10:49.548-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.550-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.563-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.592-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:49.592-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.594-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.608-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.636-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:49.672-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.674-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.676-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.679-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.681-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.715-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.717-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.719-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.721-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.724-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.726-06:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.726-06:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-01-19T06:10:49.726-06:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-01-19T06:10:49.726-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.728-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.741-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.769-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:49.804-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.806-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.809-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.811-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.813-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.815-06:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.815-06:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-01-19T06:10:49.815-06:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-01-19T06:10:49.815-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.817-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.830-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.858-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:49.926-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.928-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.930-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.933-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.935-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:50.059-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:50.059-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:50.061-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:50.076-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:50.105-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:50.105-06:00| vthread-3| I120: Building module vmmon.
2012-01-19T06:10:50.105-06:00| vthread-3| I120: Extracting the sources of the vmmon module.
2012-01-19T06:10:50.116-06:00| vthread-3| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.1-1-ARCH/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6.2
2012-01-19T06:10:51.838-06:00| vthread-3| I120: Failed to compile module vmmon!
So I thought ok maybe it needs the 3.2 patch, so I un-installed then reinstalled but it wouldn't let me run the patch saying that my sources are alreay patched, I need this machine to do my work and I now at a dead stop.
thanks for your help on this.
--jerry
Last edited by jk121960 (2012-01-19 23:16:22)OK it all worked accept for one small bit, with the new patch there is a bug in the script. It calls for
/sbin/lsmod which doesn't exist.
It exists in /bin/lsmod
So I guess you could mod the script but I just symlinked the path and it worked fine.
ln -s /bin/lsmod /sbin/lsmod
thanks again for your help and I hope this little bit gets found by who needs it.
--jerry -
/lib/modules/2.6.33-ARCH/build: no such file or directory catalyst
i am trying to install catalyst on my laptop (more so the fans will work better than anything else at this stage) and i am following the wiki's guide to doing so but when i input makepkg --asroot it all appears to be going well until it gives the error
/lib/modules/2.6.33-ARCH/build no such file or directory
this is rather frustrating and i pray someone can give another fantastic response soon!
thank youI have no idea how catalyst works (or doesn't ;P), but have you tried the [catalyst] repo:
[catalyst]
# ATI Catalyst proprietary drivers.
Server = http://catalyst.apocalypsus.net/repo/catalyst/$arch -
Build v4l ( make error /lib/modules )
I upgraded to kernel version 3 and I rebooted. Then trying to compile v4l from source. And get error :
make -C /home/poes/APP/tvdriver/v4l-dvb/v4l
make[1]: Entering directory `/home/poes/APP/tvdriver/v4l-dvb/v4l'
Updating/Creating .config
Preparing to compile for kernel version
File not found: /lib/modules//build/.config at ./scripts/make_kconfig.pl line 32.
make[1]: *** [.config] Error 2
make[1]: Leaving directory `/home/poes/APP/tvdriver/v4l-dvb/v4l'
make: *** [all] Error 2
Uname :
uname -a
Linux fanadir 3.0-ARCH #1 SMP PREEMPT Sat Aug 6 16:49:00 CEST 2011 i686 Intel(R) Pentium(R) CPU P6100 @ 2.00GHz GenuineIntel GNU/Linux
I'm totally newbie, please help. Thanks You.I'm not certain how to fix it the right way, but basically it can't determine your kernel version. You might have to edit the ./scripts/make_kconfig.pl file it's referring to and ensure that the kernel variable is being set. Note the double slash in:
File not found: /lib/modules//build/.config at ./scripts/make_kconfig.pl line 32.
There should be 3.0-ARCH in between them (or whatever directory is in /lib/modules/). Just find some way to change that and it should be fixed. -
Glibc update and /lib/modules/extramodules-3.4-ARCH/kernel/oss/ folde
so I made the steps mentioned here: https://wiki.archlinux.org/index.php/De … iki:usrlib
after doing "find /lib -exec pacman -Qo -- '{}' \+" I see I have a lot of stuff in "/lib/modules/extramodules-3.4-ARCH/kernel/oss/" folder, BUT I don't even have oss installed. So I wonder, why are they there, and if I can delete this folder?Like Capoeira, I also have some files left in my /lib folder:
[pieter@laptop ~]$ find /lib -exec pacman -Qo -- '{}' \+
error: cannot determine ownership of directory '/lib'
/lib/ld-linux.so.2 is owned by glibc 2.16.0-1
/lib/libcrypt.so.1 is owned by glibc 2.16.0-1
/lib/libSegFault.so is owned by glibc 2.16.0-1
/lib/libnss_dns.so.2 is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
/lib/libresolv.so.2 is owned by glibc 2.16.0-1
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/libc.so.6 is owned by glibc 2.16.0-1
/lib/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libnss_compat.so.2 is owned by glibc 2.16.0-1
/lib/libthread_db-1.0.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod-2.16.so is owned by glibc 2.16.0-1
/lib/libresolv-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale-2.16.so is owned by glibc 2.16.0-1
/lib/libmemusage.so is owned by glibc 2.16.0-1
/lib/libdl.so.2 is owned by glibc 2.16.0-1
/lib/libutil-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libthread_db.so.1 is owned by glibc 2.16.0-1
/lib/libnss_files-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_dns-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_db.so.2 is owned by glibc 2.16.0-1
/lib/libnsl-2.16.so is owned by glibc 2.16.0-1
/lib/libc-2.16.so is owned by glibc 2.16.0-1
/lib/libcrypt-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/ld-2.16.so is owned by glibc 2.16.0-1
error: cannot determine ownership of directory '/lib/modules'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/bcma'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bcma/bcma.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btmrvl.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btusb.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/ath3k.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btwilink.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bcm203x.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btuart_cs.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/dtl1_cs.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btsdio.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btmrvl_sdio.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/hci_vhci.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bt3c_cs.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bpa10x.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bfusb.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bluecard_cs.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/hci_uart.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/misc'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/misc/eeprom'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/broadcom'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/broadcom/b44.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atlx'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atlx/atl2.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atlx/atl1.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atl1c'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atl1c/atl1c.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atl1e'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atl1e/atl1e.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/hidp'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/hidp/hidp.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/rfcomm'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/rfcomm/rfcomm.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/bnep'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/bnep/bnep.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/bluetooth.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/cmtp'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/cmtp/cmtp.ko
/lib/libm-2.16.so is owned by glibc 2.16.0-1
/lib/libanl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_db-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn-2.16.so is owned by glibc 2.16.0-1
/lib/libdl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
/lib/libnss_hesiod.so.2 is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
error: cannot determine ownership of directory '/lib/udev'
error: cannot determine ownership of directory '/lib/udev/rules.d'
error: No package owns /lib/udev/rules.d/50-compat_firmware.rules
error: No package owns /lib/udev/compat_firmware.sh
/lib/libnss_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libutil.so.1 is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/libnss_nis-2.16.so is owned by glibc 2.16.0-1
/lib/librt-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn.so.1 is owned by glibc 2.16.0-1
If a file is not owned by any package, as is the case for all files in this list (except for the ones owned by glibc), can I then just remove it? I might make a backup of those files just to be sure, but it doesn't make sense to just copy this stuff to /usr/lib.
Last edited by Ailurus (2012-07-14 15:57:28) -
Missing extramodules in /lib/modules in custom kernel compiling.
Hello.
Im totally a newbie when it comes to compiling a kernel.And i have this little thing.
I follow this guide https://wiki.archlinux.org/index.php/Ke … ut_ABS.And everything works fine and i do make modules_install.
But when i look inside /lib/modules i see extramodules-3.1-ARCH from standard kernel there. I missing extramodules for my kernel. Should i not have one for my kernel??
I wonder if i miss to tick something in make menuconfig and if so where should i look for it??(i must be blind) or is it something else that i do wrong?
thanks
freddieLook here.
From what I remember, /usr/lib/modules/$(uname -r)/build points to a kernel source which is indeed prepared to build external modules. Prepared in that it it's partially configured which is a requirement for building external modules.
Vmlinuz is your bootable kernel. -
In trying to update iTunes, I am finding that my macbook pro cannot connect to the app store at all. I am getting this error over and over in the logs.
error:kernel[0]: TMCCFS 78942 MSG execveHook skip scan the file(/usr/lib/dyld)
tried relaunching app store, itunes, etc and no look. Internet connectivity is fine and so is DNS.Try:
Troubleshooting iTunes installation on Mac OS X
Next, post in the iTunes for Mac forum -
I am having a application in Visual Studio 2003 on Windows XP , Now I am Migrating the application in Visual Studio 2005 on Windows-7 .
In my Development PC , I was install Measurement Studio 2009 , NI DAQ 7.01 and Field Point 6.05.
my application is Showing following error:
Linking...
LINK : fatal error LNK1104: cannot open file 'NiFieldPoint71D.lib'
Build log was saved at "file://c:\EdacsNt\Source\SaftyServices\NICfpDAQDl?l\Debug\BuildLog.htm"
NICfpDAQDll - 1 error(s), 0 warning(s)
When I copy from NiFieldPoint71D.lib library from Measurement Studio 7.1 and put in :\Program Files\National Instruments\MeasurementStudioVS2005\VCNET\Lib.
my application is Showing following error:
1>Linking...
1>atlsd.lib(atltrace.obj) : error LNK2005: "unsigned int (__stdcall* ATL::g_pfnGetThreadACP)(void)" (?g_pfnGetThreadACP@ATL@@3P6GIXZA) already defined in NiFieldPoint71D.lib(StdAfx.obj)
1>atlsd.lib(atlbase.obj) : error LNK2005: "class ATL::CAtlWinModule ATL::_AtlWinModule" (?_AtlWinModule@ATL@@3VCAtlWinModule@1@A) already defined in NiFieldPoint71D.lib(StdAfx.obj)
1> Creating library ..\..\lib\debug\NICfpDAQDll.lib and object ..\..\lib\debug\NICfpDAQDll.exp
1>..\..\bin\debug\NICfpDAQDll.dll : fatal error LNK1169: one or more multiply defined symbols found
I want to ignore NiFieldPoint71D.lib from using project setting(Linker->Input->ignore Specific Library ) but still it is showing same error.
In the project Setting I am done following setting:
"C:\Program Files\National Instruments\MeasurementStudioVS2005\VCNET\Lib";"
C:\Program Files\National Instruments\NI-DAQ\Lib"
Linker->Input->ignore Specific Library: mfcs71d.lib;libc.lib;'NiFieldPoint71D.lib
Please provide some solution.
Thanks
NityanandYou posted this in the LabVIEW forum.
Are you programming in LabVIEW?
There is a separate Measurement Studio for VC++ forum. http://forums.ni.com/t5/Measurement-Studio-for-VC/bd-p/231 -
I am Migrating a application in Visual Studio 2005.
In my development PC I install the Measurement Studio 2005.
my application is Showing following error:
1>Linking...
1>LINK : fatal error LNK1104: cannot open file 'NiFieldPoint71D.lib'
1>Build log was saved at "file://c:\EdacsNt\Source\SaftyServices\NICfpDAQDll\Debug\BuildLog.htm"
1>NICfpDAQDll - 1 error(s), 0 warning(s)
In the project Setting I am done following setting
"C:\Program Files\National Instruments\MeasurementStudioVS2005\VCNET\Lib";"
C:\Program Files\National Instruments\NI-DAQ\Lib"
but in "C:\Program Files\National Instruments\MeasurementStudioVS2005\VCNET\Lib";" directory Not having the 'NiFieldPoint71D.lib' because Measurement Studio 2009 not provide this dll.
Please provide some solution.
Thanks
NityanandYou posted this in the LabVIEW forum.
Are you programming in LabVIEW?
There is a separate Measurement Studio for VC++ forum. http://forums.ni.com/t5/Measurement-Studio-for-VC/bd-p/231 -
[svn:osmf:] 13605: Update build-config files for libs.
Revision: 13605
Revision: 13605
Author: [email protected]
Date: 2010-01-18 17:10:01 -0800 (Mon, 18 Jan 2010)
Log Message:
Update build-config files for libs.
Modified Paths:
osmf/trunk/libs/VAST/vast-build-config.flex
osmf/trunk/libs/VAST/vast-build-config.flexcov
osmf/trunk/libs/VAST/vast-build-config.xml
osmf/trunk/libs/adobe/NetMocker/netmocker-build-config.xmlThanks Brian. I would certainly appreciate the maintenance and documentation of some of these. The one that most comes to mind is the OSMFTest suite. This would be valuable if only so that developers have some idea of the coverage that's going on under the hood. It would also help for diagnosing what's going on when behavior is not as expected. I was pleased that when I figured out how to compile this directory, I could see that there were 1109 tests, all of which passed except for one that failed due to not being on my local security whitelist.
-
Virtualbox - install build and header files for your current kernel
I have initially installed virtualbox before upgrading the Arch
Also took backup of the kernle before upgrading since kernel26 2.6.30 is having problem with virtualbox
After upgrading I have configure the grub to use the previous kernel i.e 2.6.28
Later installed xorg and want to install the video drivers from VBox additions
but running
sh VBoxLinuxAdditions_x86.run
i get the following
install build and header files for your current kernel
The current kernel version is 2.6.28 Arch
What are the build and header files I have to install or search with pacman
And since i have upgraded the system will I able to look up the header and build files needed for kernel 2.6.28dmartins - he's talking about his kernel's headers, not the kernel-headers package - they are two very differnet things.
sant527 - when you backed up the 2.6.28 kernel, did you remember the files in /usr/src/linux-2.6.28-ARCH/ ? They're what VBox is looking for. -
I have a question.
How do I configure the resulting package so that it won't attempt to overwrite the module and header directories that are set by the current ARCH kernel?
For example, I get this error if I do "sudo pacman -A kernel26201-ARCH-2.6.20.1-1.pkg.tar.gz"
loading package data... done. checking for file conflicts... error: the
following file conflicts were found:
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/build: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/crypto/aes-i586.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/crypto/twofish-i586.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/cpu/cpufreq/p4-clockmod.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-ich.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-lib.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-smi.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/cpu/mcheck/non-fatal.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/cpuid.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/arch/i386/kernel/msr.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/aes.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/anubis.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/arc4.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/crypto/blowfish.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/cast5.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/cast6.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/crc32c.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/crypto/crypto_null.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/deflate.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/ecb.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/crypto/gf128mul.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/khazad.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/lrw.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/md4.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/crypto/michael_mic.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/serpent.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/sha1.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/sha256.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/sha512.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/tcrypt.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/tea.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/tgr192.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/twofish.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/crypto/twofish_common.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/wp512.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/crypto/xcbc.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ata/ahci.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ata/ata_generic.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ata/ata_piix.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ata/libata.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ata/pata_mpiix.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ata/pata_oldpiix.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/block/floppy.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/block/nbd.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/block/pktcdvd.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/cdrom/cdrom.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/agp/agpgart.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/agp/intel-agp.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/drm/drm.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/drm/i810.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/drm/i915.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/dtlk.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/genrtc.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/hangcheck-timer.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/hw_random/intel-rng.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/ipmi/ipmi_devintf.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/ipmi/ipmi_msghandler.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/ipmi/ipmi_poweroff.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/ipmi/ipmi_si.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/ipmi/ipmi_watchdog.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/nvram.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/char/rtc.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/connector/cn.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/cpufreq/cpufreq_ondemand.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/cpufreq/cpufreq_stats.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/cpufreq/freq_table.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/crypto/geode-aes.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/crypto/padlock-aes.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/crypto/padlock-sha.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/crypto/padlock.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/dma/ioatdma.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/edac/edac_mc.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/edac/i82860_edac.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/edac/i82875p_edac.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/hid/hid.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/i2c/algos/i2c-algo-pca.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/i2c/algos/i2c-algo-pcf.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/i2c/busses/i2c-i801.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/i2c/busses/i2c-i810.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/i2c/busses/i2c-parport-light.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/i2c/busses/i2c-piix4.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/i2c/i2c-dev.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ide/ide-cd.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ide/ide-core.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ide/ide-disk.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ide/ide-generic.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ide/pci/generic.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ide/pci/piix.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/ide/pci/rz1000.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/input/evdev.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/input/joydev.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/kvm/kvm-intel.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/kvm/kvm.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/media/video/compat_ioctl32.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/media/video/ov511.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/media/video/ovcamchip/ovcamchip.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/media/video/stv680.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/media/video/v4l1-compat.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/media/video/v4l2-common.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/media/video/videodev.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/message/fusion/mptctl.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/message/i2o/i2o_block.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/message/i2o/i2o_bus.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/message/i2o/i2o_config.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/message/i2o/i2o_core.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/message/i2o/i2o_proc.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/message/i2o/i2o_scsi.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/misc/tifm_core.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/8139cp.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/8139too.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/bonding/bonding.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/dummy.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/e100.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/e1000/e1000.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/eql.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/act200l-sir.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/actisys-sir.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/ali-ircc.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/donauboe.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/esi-sir.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/girbil-sir.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/irda-usb.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/irtty-sir.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/litelink-sir.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/ma600-sir.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/mcp2120-sir.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/mcs7780.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/nsc-ircc.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/old_belkin-sir.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/sir-dev.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/smsc-ircc2.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/stir4200.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/tekram-sir.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/toim3232-sir.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/via-ircc.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/vlsi_ir.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/irda/w83977af_ir.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/ixgb/ixgb.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/mii.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/netconsole.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/tulip/de2104x.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/tulip/de4x5.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/tulip/dmfe.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/tulip/tulip.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/tulip/uli526x.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/tulip/winbond-840.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/net/tun.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/rtc/rtc-core.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/rtc/rtc-dev.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/rtc/rtc-lib.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/rtc/rtc-proc.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/rtc/rtc-sysfs.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/rtc/rtc-test.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/eata.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/gdth.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/ide-scsi.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/libsrp.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/osst.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/scsi_tgt.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/scsi_transport_sas.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/sd_mod.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/sg.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/scsi/sr_mod.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/class/usblp.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/core/usbcore.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/host/ehci-hcd.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/host/ohci-hcd.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/host/uhci-hcd.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/input/usbhid.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/misc/ldusb.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/misc/sisusbvga/sisusbvga.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/misc/trancevibrator.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/misc/usbtest.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/usb/storage/usb-storage.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/video/backlight/backlight.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/drivers/video/backlight/lcd.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/configfs/configfs.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/cramfs/cramfs.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/dlm/dlm.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/ext2/ext2.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/ext3/ext3.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/ext4/ext4dev.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/fuse/fuse.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/jbd/jbd.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/jbd2/jbd2.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/mbcache.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/nls/nls_ascii.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/nls/nls_cp437.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/nls/nls_cp950.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/nls/nls_iso8859-15.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/nls/nls_iso8859-2.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/nls/nls_iso8859-3.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/fs/nls/nls_iso8859-4.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/ntfs/ntfs.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/quota_v1.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/fs/quota_v2.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/lib/crc-ccitt.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/lib/crc16.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/lib/libcrc32c.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/lib/ts_bm.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/lib/ts_fsm.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/lib/ts_kmp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/lib/zlib_deflate/zlib_deflate.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/802/p8022.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/802/p8023.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/802/psnap.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/8021q/8021q.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/appletalk/appletalk.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/atm/atm.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/atm/br2684.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/atm/clip.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/atm/lec.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/atm/mpoa.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/bridge.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_802_3.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_among.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_arp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_arpreply.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_dnat.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_ip.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_limit.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_log.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_mark.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_mark_m.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_pkttype.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_redirect.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_snat.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_stp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_ulog.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebt_vlan.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebtable_broute.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebtable_filter.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebtable_nat.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/bridge/netfilter/ebtables.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ieee80211/ieee80211.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ieee80211/ieee80211_crypt.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ieee80211/ieee80211_crypt_ccmp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ieee80211/ieee80211_crypt_wep.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ieee80211/softmac/ieee80211softmac.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ah4.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/esp4.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ip_gre.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipcomp.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipip.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_dh.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_ftp.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_lblc.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_lblcr.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_lc.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_nq.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_rr.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_sed.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_sh.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_wlc.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/ipvs/ip_vs_wrr.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/multipath_drr.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/multipath_random.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/multipath_rr.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/multipath_wrandom.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/arp_tables.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/arpt_mangle.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/arptable_filter.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ip_queue.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ip_tables.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_CLUSTERIP.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_ECN.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_LOG.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_MASQUERADE.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_NETMAP.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_REDIRECT.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_REJECT.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_SAME.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_TCPMSS.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_TOS.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_TTL.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_ULOG.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_addrtype.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_ah.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_ecn.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_iprange.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_owner.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_recent.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_tos.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/ipt_ttl.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/iptable_filter.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/iptable_mangle.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/iptable_nat.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/iptable_raw.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_conntrack_ipv4.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_amanda.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_ftp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_h323.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_irc.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_pptp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_proto_gre.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_sip.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_snmp_basic.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/netfilter/nf_nat_tftp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/tunnel4.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/xfrm4_mode_beet.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/xfrm4_mode_transport.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/xfrm4_mode_tunnel.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv4/xfrm4_tunnel.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/ah6.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/esp6.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/ip6_tunnel.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/ipcomp6.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/ipv6.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6_queue.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6_tables.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_HL.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_LOG.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_REJECT.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_ah.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_eui64.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_frag.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_hbh.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_hl.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_ipv6header.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_owner.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6t_rt.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6table_filter.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6table_mangle.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/ip6table_raw.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/netfilter/nf_conntrack_ipv6.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/sit.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/tunnel6.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/xfrm6_mode_beet.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/xfrm6_mode_ro.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/xfrm6_mode_transport.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/xfrm6_mode_tunnel.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/ipv6/xfrm6_tunnel.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/ipx/ipx.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/irda/ircomm/ircomm-tty.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/irda/ircomm/ircomm.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/irda/irda.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/irda/irlan/irlan.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/key/af_key.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/llc/llc.ko:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/llc/llc2.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_amanda.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_ftp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_h323.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_irc.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_netbios_ns.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_netlink.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_pptp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_proto_gre.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_proto_sctp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_sip.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nf_conntrack_tftp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nfnetlink.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nfnetlink_log.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/nfnetlink_queue.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/x_tables.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_CLASSIFY.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_CONNMARK.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_CONNSECMARK.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_DSCP.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_MARK.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_NFLOG.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_NFQUEUE.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_NOTRACK.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_SECMARK.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_comment.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_connbytes.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_connmark.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_conntrack.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_dccp.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_dscp.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_esp.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_hashlimit.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_helper.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_length.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_limit.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_mac.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_mark.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_multiport.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_physdev.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_pkttype.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_policy.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_quota.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_realm.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_sctp.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_state.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_statistic.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_string.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_tcpmss.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/netfilter/xt_tcpudp.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/net/sctp/sctp.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/net/xfrm/xfrm_user.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/security/capability.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/security/commoncap.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/security/root_plug.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/sound/ac97_bus.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/oss/snd-mixer-oss.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/oss/snd-pcm-oss.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/seq/oss/snd-seq-oss.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/seq/snd-seq-device.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/seq/snd-seq-midi-event.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/seq/snd-seq-midi.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/seq/snd-seq.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/snd-page-alloc.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/snd-pcm.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/snd-rawmidi.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/snd-rtctimer.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/core/snd-timer.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/kernel/sound/core/snd.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/drivers/snd-dummy.ko: exists in
filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/pci/ac97/snd-ac97-codec.ko:
exists in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/pci/ca0106/snd-ca0106.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/pci/hda/snd-hda-codec.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/pci/hda/snd-hda-intel.ko: exists
in filesystem
kernel26201-ARCH:
/lib/modules/2.6.20.1-ARCH/kernel/sound/soundcore.ko: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.alias: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.ccwmap: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.dep: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.ieee1394map:
exists in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.inputmap: exists
in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.isapnpmap: exists
in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.ofmap: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.pcimap: exists in
filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.seriomap: exists
in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.symbols: exists
in filesystem
kernel26201-ARCH: /lib/modules/2.6.20.1-ARCH/modules.usbmap: exists in
filesystem errors occurred, no packages were upgraded.
(was able to receive full output by piping pacman's output to nano)
Last edited by NoOneImportant (2007-03-06 23:42:41)I just ran into this problem today.
The document no longer makes any reference to 'LOCALVERSION'
The doc itself implies
Modify pkgbase for your custom package name, e.g.:
pkgbase=linux-custom
So I did this
#pkgbase=linux # Build stock -ARCH kernel
pkgbase=linux-iwlwifidebug # Build kernel with a different name
However, when running pacman -U, It clearly is trying to overwrite the existing kernel's files:
loading packages...
resolving dependencies...
:: Proceed with installation? [Y/n]
Packages (1): linux-iwlwifidebug-3.12.1-1
Total Installed Size: 68.98 MiB
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
error: failed to commit transaction (conflicting files)
linux-iwlwifidebug: /usr/lib/modules/3.12.1-1-ARCH/extramodules exists in filesystem
linux-iwlwifidebug: /usr/lib/modules/3.12.1-1-ARCH/kernel/arch/x86/crypto/ablk_helper.ko.gz exists in filesystem
linux-iwlwifidebug: /usr/lib/modules/3.12.1-1-ARCH/kernel/arch/x86/crypto/aes-x86_64.ko.gz exists in filesystem
linux-iwlwifidebug: /usr/lib/modules/3.12.1-1-ARCH/modules.softdep exists in filesystem
linux-iwlwifidebug: /usr/lib/modules/3.12.1-1-ARCH/modules.symbols exists in filesystem
linux-iwlwifidebug: /usr/lib/modules/3.12.1-1-ARCH/modules.symbols.bin exists in filesystem
linux-iwlwifidebug: /usr/src/linux-3.12.1-1-ARCH/vmlinux exists in filesystem
Errors occurred, no packages were upgraded.
I don't know what the 'right' way to do this is that will allow all of the automated tools to work right.. i.e. mkinitcpio and bootloader...
Suggestions? -
Custom Kernel Build Help + Errors
Hi,
I hope everyone is doing well. I am a newbie and I have been trying to create a custom Kernel with the following steps
1- sudo pacman -Syu
2- reboot
3- download https://www.kernel.org/pub/linux/kernel … .37.tar.xz
4- tar -xvJf linux-3.14.37.tar.xz
5- sudo pacman -S bc
6- make mrproper
7- zcat /proc/config.gz > .config
8- make menuconfig -->
General setup --->
append to kernel release 'emraldinho'
9- make -j4
10- sudo make modules_install
After step 10 I get the following error:
DEPMOD 3.14.37-emraldinho
depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor information. Ignoring.
Any ideas what's going on here? I tried doing it over a few times, but it does not seem to help
Thanks in advance!Thank you. I am trying to get it done for my own learning I guess.
I was thinking if I just echoed each command one by one, would that not get it done?
I guess I have to check if any of the commands are puking out an error though
snakeroot wrote:
emraldinho wrote:
Thank you for the responses.
I want to write a bash script that does this, is there anything specific that I have to pay attention to, or can I just echo these commands one by one?
Thanks!
Here's what I use; note that it is for a somewhat non-standard gummiboot install and has a few other peculiarities, but hopefully you may find it vaguely useful. Obviously, you break your system, you keep the pieces.
#!/bin/bash
MKFLG="-j5"
cp -r "$(pwd)" /tmp
cd /tmp/"$(basename $(pwd))"
make kernelrelease
kn=$(make kernelrelease)
gb="/mnt/sda1/loader/entries"
ko=$(uname -r)
usl="/usr/src/${kn}"
ax="arch/x86"
uslax="${usl}/${ax}"
time make $MKFLG all
sudo make modules_install
# make headers_install
sudo install -v -m=644 arch/x86/boot/bzImage /boot/vmlinuz-"${kn}".efi
sudo install -v -m=644 System.map "/boot/System.map-${kn}"
sudo install -v -m=644 .config /boot/config-"${kn}"
sudo mkinitcpio -k "${kn}" -g /boot/initramfs-"${kn}".img
sudo cp -v /boot/System.map-"${kn}" /boot/System.map
sudo cp -v "${gb}/Arch_${ko}.conf" "${gb}/Arch_${kn}.conf"
sudo sed -i -e "s:${ko}:${kn}:g" "${gb}/Arch_${kn}.conf"
sudo mkdir -pv "${usl}"
for i in "Makefile" "kernel/Makefile" ".config"; do
sudo install -Dv -m644 "${i}" "${usl}/${i}"
done
sudo mkdir -pv "${usl}/include"
for i in acpi asm-generic config crypto drm generated linux math-emu \
media net scsi sound trace uapi video xen; do
sudo cp -a include/${i} "${usl}/include/"
done
sudo mkdir -pv "${uslax}"
sudo cp -a "${ax}/include" "${uslax}/"
sudo cp Module.symvers "${usl}"
sudo cp -a scripts "${usl}"
sudo chmod og-w -R "${usl}/scripts"
sudo mkdir -p "${usl}/.tmp_versions"
sudo mkdir -p "${uslax}/kernel"
sudo cp "${ax}/Makefile" "${uslax}/"
sudo cp "${ax}/kernel/asm-offsets.s" "${uslax}/kernel/"
sudo install -D -m644 Documentation/DocBook/Makefile "${uslax}/Documentation/DocBook/Makefile"
sudo mkdir -p "${uslax}/drivers/md"
sudo cp drivers/md/*.h "${uslax}/drivers/md"
# mkdir -p "${usl}/include/linux"
# cp include/linux/inotify.h "${us}/include/linux/"
sudo mkdir -p "${usl}/fs/xfs"
sudo mkdir -p "${usl}/mm"
sudo cp fs/xfs/xfs_sb.h "${usl}/fs/xfs/xfs_sb.h"
for i in $(find . -name 'Kconfig*'); do
sudo mkdir -p "${usl}/$(echo ${i} | sed 's|/Kconfig.*||')"
sudo cp ${i} "${usl}/${i}"
done
sudo chown -R root.root "${usl}"
sudo find "${usl}" -type d -exec chmod 755 {} \;
sudo find "${usl}/scripts" -type f -perm -u+w 2>/dev/null | while read binary ; do
case "$(file -bi "${binary}")" in
*application/x-sharedlib*) # Libraries (.so)
sudo /usr/bin/strip ${STRIP_SHARED} "${binary}";;
*application/x-archive*) # Libraries (.a)
sudo /usr/bin/strip ${STRIP_STATIC} "${binary}";;
*application/x-executable*) # Binaries
sudo /usr/bin/strip ${STRIP_BINARIES} "${binary}";;
esac
done
for i in source build; do
sudo rm -r "/usr/lib/modules/${kn}/${i}"
sudo ln -sf "${usl}" "/usr/lib/modules/${kn}/${i}"
done -
You knew it was coming: kernel build issues after kmod upgrade
Good morning,
After reading the BIG SCARY NOTE on the mailing list, I just *had* to upgrade my system and kernel. Following a -Syu, i built a kernel from the latest source (3.5.0-rc5+). Naturally, it built just fine. However, when i ran 'make modules_install', it installed the modules into /lib, which i was expecting. Moving on from *that* test, i ran:
make INSTALL_MOD_PATH=/usr/ modules_install
(Note that the INSTALL_MOD_PATH is /usr, NOT /usr/lib/modules/. This is because of how the variable is used)
Anyway, that command installed the modules correctly, but shot this error when it tried to depmod (paraphrasing. the important bit here is the path):
ERROR: Failed to open /usr//usr/lib/modules/98.99.3.5.0-rc5-custom+: no such file or directory
Interestingly enough, running a simple 'depmod 3.5.0-rc5-custom+' works fine, and all is well. the kernel runs fantasticly, right up to the nvidia module.
So, i submit to you:
What is the prepended "98.99." in the file structure about, and why is the kernel's built-in depmod prepending usr twice?
Thanks folks,
Aaron
EDIT: For clarity, the 98.99 isn't actually there in the file structure, just in the depmod command the kernel makefile runs following modules_install.
Last edited by usagi (2012-07-04 11:02:30)falconindy wrote:No... the error is being generated from the same depmod.sh script which is called in the temporary root that is created by Kbuild when you call tar-pkg. The same fix of removing the hack in this script will fix your tarball creation.
The sequence goes something like this:
In a clean, vanilla tree, make tar-pkg borks with this message (the same one the OP reported):
ERROR: could not open directory /home/sujith/dev/wireless-testing/build/tar-install/usr/usr/lib/modules/99.98.3.5.0-rc5-wl: No such file or directory
After adding the fix you posted:
ERROR: could not open directory /home/sujith/dev/wireless-testing/build/tar-install/usr/lib/modules/3.5.0-rc5-wl: No such file or directory
After fixing the 'buildtar' script to use '/usr' as the install-prefix (note the extra 'usr'):
ERROR: could not open directory /home/sujith/dev/wireless-testing/build/tar-install/usr/usr/lib/modules/3.5.0-rc5-wl: No such file or directory
After a dirty hack using dirname to strip the extra 'usr' (at this point, I just wanted to move on :-) ):
Tarball successfully created in /home/sujith/dev/wireless-testing/build/linux-3.5.0-rc5-wl.tar
Hope that clears things a bit ! -
Warning: /lib/modules/3.14.17-1-lts/modules.devname not found
I am trying to use linux-lts but get this error, I'm using rEFInd. I am able to boot the standard arch kernel, but when selecting the other entry in refind I just get the error.
Warning: /lib/modules/3.14.17-1-lts/modules.devname not found - ignoring
The file does exist though.I sorted it, though not exactly as I want it. I had to change the initrd line in /boot/refind_linux.conf to be initramfs-linux-lts.img, I had previously copied the boot line and created a new one with that initrd line, but that didn't work. As I have things now I can only boot the lts kernel, if I want to change to the other I need to manually change that line before rebooting.
Maybe you are looking for
-
Excel 2011 for Mac No Longer Works. Wonder if it is Maverick?
I am hoping someone can help me. I am wondering if this my problem has something to do with Maverick update but my Mac Excel no longer works. I can save a file and it will open once but after that it will open but be completely blank. As for older fi
-
Macbook Pro won't boot into safe mode or via bootable USB key
Hi, Am running OSX Lion latest version on my Macbook Pro 4,1 and can't get the thing to boot from any source. Always get's stuck at the grey screen with apple logo. Have tried all the following... - Straight Boot (power on) - Boot via Recovery HD (
-
Viewing and uploading documents when using a business package in the portal
DMS works fine in the ECC backend and we are able to create and view documents but when attempting to view a document via the Business Package Maintenance Supervisor or Maintenance Technician, error returns with "No originals available for the docume
-
How to create own SplitPaneDivider and how to use it
Hi, I'm trying to create my own SplitPaneDivider and set it for one of my SplitPanes by doing: JSplitPane splitterPanel = new JSplitPane(JSplitPane.HORIZONTAL_SPLIT, true,listTablePanel, editorPanel); splitterPanel.setOneTouchExpandable(true); splitt
-
I have error 1669 .how to solve that?
I have issue my iphone error 1669 i can't restore and update my iphone so please help me