Kernel patching with ABS

I have a problem with the newest kernel (kacpid takes 90% of cpu), so I found a patch on kernel.org bugzilla, located at http://bugzilla.kernel.org/show_bug.cgi?id=10224#c25
I really have no clue what I am doing, but I carried on regardless.
I copied /var/abs/core/kernel26 into ~/builds/, put the patch into kernel26/src called acpi.patch and edited the PKGBUILD like so:
I added   patch -Np1 -i $startdir/src/acpi.patch || return 1
# $Id: PKGBUILD 1759 2008-05-16 13:58:54Z thomas $
# Maintainer: Tobias Powalowski <[email protected]>
# Maintainer: Thomas Baechler <[email protected]>
pkgname=kernel26
_basekernel=2.6.25
pkgver=2.6.25.4
pkgrel=1
_patchname="patch-${pkgver}-${pkgrel}-ARCH"
pkgdesc="The Linux Kernel and modules"
arch=(i686 x86_64)
license=('GPL2')
groups=('base')
url="http://www.kernel.org"
backup=(etc/mkinitcpio.d/${pkgname}.preset)
depends=('coreutils' 'module-init-tools' 'mkinitcpio>=0.5.18')
# pwc, ieee80211 and hostap-driver26 modules are included in kernel26 now
# nforce package support was abandoned by nvidia, kernel modules should cover everything now.
# kernel24 support is dropped since glibc24
replaces=('kernel24' 'kernel24-scsi' 'kernel26-scsi'
'alsa-driver' 'ieee80211' 'hostap-driver26'
'pwc' 'nforce' 'squashfs' 'unionfs' 'ivtv'
'zd1211' 'kvm-modules' 'iwlwifi' 'rt2x00-cvs')
install=kernel26.install
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$_basekernel.tar.bz2
ftp://ftp.archlinux.org/other/kernel26/${_patchname}.bz2
# the main kernel config files
config config.x86_64
# standard config files for mkinitcpio ramdisk
kernel26.preset)
md5sums=('db95a49a656a3247d4995a797d333153'
'bf582e97c84be9abce998a8d640f4ae7'
'777d94911faa1cb480832b1c47bee307'
'2b19c2ff9abd0e6d0ad1e29f124021c3'
'25584700a0a679542929c4bed31433b6')
build() {
KARCH=x86
cd $startdir/src/linux-$_basekernel
# Add -ARCH patches
# See http://projects.archlinux.org/git/?p=linux-2.6-ARCH.git;a=summary
patch -Np1 -i $startdir/src/${_patchname} || return 1
patch -Np1 -i $startdir/src/acpi.patch || return 1
if [ "$CARCH" = "x86_64" ]; then
cat ../config.x86_64 >./.config
else
cat ../config >./.config
fi
# build the full kernel version to use in pathnames
. ./.config
### next line is only needed for rc kernels
_kernver="2.6.25${CONFIG_LOCALVERSION}"
#_kernver="${_basekernel}${CONFIG_LOCALVERSION}"
# load configuration
yes "" | make config
# build!
# stop here
# this is useful to configure the kernel
#msg "Stopping build"
#return 1
make bzImage modules || return 1
mkdir -p $startdir/pkg/{lib/modules,boot}
make INSTALL_MOD_PATH=$startdir/pkg modules_install || return 1
cp System.map $startdir/pkg/boot/System.map26
cp arch/$KARCH/boot/bzImage $startdir/pkg/boot/vmlinuz26
install -D -m644 Makefile \
$startdir/pkg/usr/src/linux-${_kernver}/Makefile
install -D -m644 kernel/Makefile \
$startdir/pkg/usr/src/linux-${_kernver}/kernel/Makefile
install -D -m644 .config \
$startdir/pkg/usr/src/linux-${_kernver}/.config
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include
for i in acpi asm-{generic,x86} config linux math-emu media net pcmcia scsi sound video; do
cp -a include/$i $startdir/pkg/usr/src/linux-${_kernver}/include/
done
# copy files necessary for later builds, like nvidia and vmware
cp Module.symvers $startdir/pkg/usr/src/linux-${_kernver}
cp -a scripts $startdir/pkg/usr/src/linux-${_kernver}
# fix permissions on scripts dir
chmod og-w -R $startdir/pkg/usr/src/linux-${_kernver}/scripts
#mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/.tmp_versions
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel
cp arch/$KARCH/Makefile $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
if [ "$CARCH" = "i686" ]; then
cp arch/$KARCH/Makefile_32.cpu $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
fi
cp arch/$KARCH/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel/
# add headers for lirc package
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video
cp drivers/media/video/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/
for i in bt8xx cpia2 cx25840 cx88 em28xx et61x251 pwc saa7134 sn9c102 usbvideo zc0301; do
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/$i
cp -a drivers/media/video/$i/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/$i
done
# add dm headers
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/md
cp drivers/md/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/md
# add inotify.h
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include/linux
cp include/linux/inotify.h $startdir/pkg/usr/src/linux-${_kernver}/include/linux/
# add CLUSTERIP file for iptables
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/net/ipv4/netfilter/
# add wireless headers
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/net/mac80211/
cp net/mac80211/*.h $startdir/pkg/usr/src/linux-${_kernver}/net/mac80211/
# add dvb headers for external modules
# in reference to:
# http://bugs.archlinux.org/task/9912
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-core
cp drivers/media/dvb/dvb-core/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/dvb/dvb-core/
# add xfs and shmem for aufs building
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/fs/xfs
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/mm
cp fs/xfs/xfs_sb.h $startdir/pkg/usr/src/linux-${_kernver}/fs/xfs/xfs_sb.h
# add vmlinux
cp vmlinux $startdir/pkg/usr/src/linux-${_kernver}
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/`echo $i | sed 's|/Kconfig.*||'`
cp $i $startdir/pkg/usr/src/linux-${_kernver}/$i
done
cd $startdir/pkg/usr/src/linux-${_kernver}/include && ln -s asm-$KARCH asm
chown -R root.root $startdir/pkg/usr/src/linux-${_kernver}
find $startdir/pkg/usr/src/linux-${_kernver} -type d -exec chmod 755 {} \;
cd $startdir/pkg/lib/modules/${_kernver} && \
(rm -f source build; ln -sf ../../../usr/src/linux-${_kernver} build)
# install fallback mkinitcpio.conf file and preset file for kernel
install -m644 -D $startdir/src/${pkgname}.preset $startdir/pkg/etc/mkinitcpio.d/${pkgname}.preset || return 1
# set correct depmod command for install
sed -i -e "s/KERNEL_VERSION=.*/KERNEL_VERSION=${_kernver}/g" $startdir/kernel26.install
echo -e "# DO NOT EDIT THIS FILE\nALL_kver='${_kernver}'" > ${startdir}/pkg/etc/mkinitcpio.d/${pkgname}.kver
# remove unneeded architectures
rm -rf $startdir/pkg/usr/src/linux-${_kernver}/arch/{alpha,arm,arm26,avr32,blackfin,cris,frv,h8300,ia64,m32r,m68k,m68knommu,mips,parisc,powerpc,ppc,s390,sh,sh64,sparc,sparc64,um,v850,xtensa}
It compiled fine and so I though all was well, but when installing, I get the following errors.
(1/1) upgrading kernel26 [####################################################################################################] 100%
>>>
>>> If you use the LILO bootloader, you should run 'lilo' before rebooting.
>>>
>>> Updating module dependencies. Please wait ...
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ata[-_]generic' not found
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ahci' not found
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ata[-_]piix' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
find: /lib/modules/2.6.25-ARCH: No such file or directory
:: Parsing hook [sata]
:: Parsing hook [uresume]
:: Parsing hook [keymap]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ata[-_]generic' not found
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ahci' not found
find: /lib/modules/2.6.25-ARCH: No such file or directory
ERROR: module 'ata[-_]piix' not found
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [sata]
:: Parsing hook [uresume]
:: Parsing hook [keymap]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS
Is that kernel safe to boot from or not - the No such file or directory errors are worrying.

The kernel config and patch are irrelevant - I have tried to compile the stock arch kernel just to make sure that it WASN'T the patch - I simple copied the folder from ABS, did makepkg and installed - no lucky. The problem seems to be that all of the kernels I compile end up with the folder in /lib/modules having -dirty on the end of them. How do I stop this '-dirty'?
I notice in the build I get this message -
==> Building the kernel
fatal: cannot describe '604d205b49b9a478cbda542c65bacb9e1fa4c840'
  CHK     include/linux/version.h

Similar Messages

  • Custom kernel compilation with abs..

    Been trying out custom kernel compilation with abs, since i only know the regular make menuconfig style, thought that this would be a good thing to learn.
    here is my kernel pkgbuild (showing only the part that i changed):
    # Contributor: dibblethewrecker <dibblethewrecker>
    pkgname=kernel26
    pkgver=2.6.17.13
    pkgrel=1
    pkgdesc="The Linux Kernel 2.6.x.y and modules (IDE support), built with ... patchset"
    url="http://www.kernel.org"
    depends=('module-init-tools')
    install=kernel26.install
    ##### if you are using a single patch from a patchset you can add the name, without it's extention, below
    patch=2.6.18-rc6-mm2
    ##### add the names of any patches to this section, ensure you have the correct extentions!
    source=($patch.bz2 config ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$pkgver.tar.bz2 )
    I want to install the 2.6.18-rc6-mm2, so i downloaded that patch and put it in the same folder as PKGBUILD.
    I copied kernel26.install and put it in the same folder as the PKGBUILD.
    when running makepkg it asks for a config file.. So i copied the config file in /var/abs/kernels/kernel26/. But this will build with an old config file.. how can i as when doing the manual way, do a make menuconfig and enter the settings i want for this kernel??
    thanks

    I'd say it does too, and I think the problem is here:
    jinn wrote:I copied kernel26.install and put it in the same folder as the PKGBUILD.
    Did you just copy the install script, or did you edit it to create an image with a unique name? The script is hardcoded to create an image called kernel26.img i.e. the image name required by the stock kernel, so if you ran it as it is, you have overwritten the images for your stock kernel with images for your new kernel.
    You might still be able to boot your new kernel with kernel26-fallback.img, but if not you will have to boot your stock kernel using the initrd image, which will have been unaffected.
    Once your system is running again, you need to regenerate the kernel26 images using mkinitcpio, and then you can start debugging the problem with your new kernel.
    Of course, if you've already edited kernel26.install for your new kernel, ignore the above, and I'll start again.

  • Kernel Patching with zones

    I have a T2000 installed with the Solaris 10 1/06 release with several zones created on it. 4 zones are "sparse" root, and one (zone-5) is a "whole root" zone.
    In order to apply and certify (internally) the latest sendmail patch, Solaris 10 needs a later kernel patch than I had installed (this is a subject for another discussion...). So I downloaded the latest patch cluster (4/6 Recommended cluster) to apply it.
    I shut down the non-global zones, and took the machine to single user mode, and installed the cluster. It seemed to go in fine, except for the following error:
    Zone zone-5
    Rejected patches:
    122856-01
    Patches that passed the dependency check:
    None.
    Fatal failure occurred - impossible to install any patches.
    zone-5: For patch 122856-01, required patch 118822-30 does not exist.
    Fatal failure occurred - impossible to install any patches.Now, 118822-30 is a kernel patch series that is prerequisite for the latest kernel patch (118833-03). Zone-5 is my only whole-root zone. I then looked at the patch cluster log, and discovered that a handful of patches (including 118822-30) had also failed:
    titan15n> grep failed /var/sadm/install_data/Solaris_10_Recommended_Patch_Cluster_log
    Pkgadd failed. See /var/tmp/119254-19.log.6615 for details
    Pkgadd failed. See /var/tmp/118712-09.log.9307 for details
    Pkgadd failed. See /var/tmp/119578-18.log.15160 for details
    Pkgadd failed. See /var/tmp/121308-03.log.18339 for details
    Pkgadd failed. See /var/tmp/119689-07.log.22068 for details
    Pkgadd failed. See /var/tmp/118822-30.log.9404 for details
    Pkgadd failed. See /var/tmp/119059-11.log.29911 for details
    Pkgadd failed. See /var/tmp/119596-03.log.4724 for details
    Pkgadd failed. See /var/tmp/119985-02.log.8349 for details
    Pkgadd failed. See /var/tmp/122032-02.log.13334 for details
    Pkgadd failed. See /var/tmp/118918-14.log.27743 for detailsLooking at any of these logs (in the non-global zone-5's /var/tmp directory shows failures like the following snippet:
    pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/cheetahregs.h6HaG8w>: (30) Read-only file sy
    stem
    pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/clock.h7HaG8w>: (30) Read-only file system
    pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/dvma.h8HaG8w>: (30) Read-only file systemQuestion(s):
    Why would there be read-only file systems where tmp files are getting written? Possibly a timing issue?
    Is there a "best practice" on applying patch clusters, and specifically, the kernel patch? Did I make a mistake in taking the zones down first? It seems like the zones were being booted up as the patches were getting applied, but I may be misinterpreting the output.
    Even though the patches failed to apply to zone-5, the uname -a output in the zone show the latest kernel patch, but does NOT show 118822-30 (118822-25 is what showrev -p in the non-global zone-5 shows -- which is the level I was at before attempting to patch).
    Any solutions?
    Thanks.

    The kernel config and patch are irrelevant - I have tried to compile the stock arch kernel just to make sure that it WASN'T the patch - I simple copied the folder from ABS, did makepkg and installed - no lucky. The problem seems to be that all of the kernels I compile end up with the folder in /lib/modules having -dirty on the end of them. How do I stop this '-dirty'?
    I notice in the build I get this message -
    ==> Building the kernel
    fatal: cannot describe '604d205b49b9a478cbda542c65bacb9e1fa4c840'
      CHK     include/linux/version.h

  • Kernel building with ABS

    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?

  • Kernel Patch Update

    Hi
    I have a question about updating the kernel patch to the latest version Can a kernel patch be directly updated from any lower version to the latest version by applying the latest patch even if the kernel patch number itself has changed like the below scenarios
    1. Can I directly update the kernel pacth 122300-51 to 122300-57
    2.Can I directly update the kernel patch 142909-17 to 144488-17
    Thanks in advance

    Basically, yes, but you need to take care of the patch dependencies. Usually a kernel patch with a new patch ID will require the last revision of each former kernel patch to be installed first.
    Either you use patchadd on the most recent kernel patch you want to apply and then work yourself back through the patch dependencies, or you use PCA (http://www.par.univie.ac.at/solaris/pca/) which will do this job for you. Use e.g. "pca -l 144488" to get a list of all the patches which have to be installed first to get the system up to the wanted kernel patch level.

  • Kernel debugging using git bisection method in combination with abs.

    Is there any way to use git bisection method for kernel debugging in combination with ABS for building the kernel via makepkg?

    Yes, but ABS for kernel uses some patches in order for the kernel to be successfully build.
    ftp://ftp.archlinux.org/other/kernel26/
    I wanted to know is if there is any way to distinguish what particular patch to use in every bisection point.

  • Recompile a compiled kernel with ABS

    I had been compiling my own kernel with the traditional method for ages. Sometimes ago, I decided to try the ABS method, modifying properly a PKGBUILD for the kernels provided by arch. I now appreciate the provided automation and the ease in combining arch patches with the patches I need or like.
    After a deep personalization of the PKGBUILD, there is now only a feature of the old method I continue to miss. It is when I decide to change something in the configuration of a kernel I have already compiled, and I want to recompile it. If I do so with the traditional method, the previous compilation is somewaht "cached"  and only what is actually different is compiled again: thus, the recompilation time is apparently shorter than the time needed by the first compilation.
    I am not able to do the same with the ABS method. It seems that the directory with the kernel source into src/ is rewritten every time (i.e., the kernel package is untarred also when is already there). Moreover, I also need to delete completely src/ or part of his content, otherwise makepkg complains about patches already being there. Is there a way to avoid this behaviour, so to shorten the recompilation time?

    Yes, ccache drastically reduces recompilation times (for my kernel, from 30 min to 5 min). However, when you change just a couple of peripheric things in config, 5 minutes are too much. Anyway, thanks a lot.

  • About compiling a kernel with ABS

    So I was following the guide on the wiki about compiling a new kernel with ABS. I wanted to try and make a kernel that didn't need to use initramfs. I thought I could do it by not enabling the kernel to have the ability to use initramfs, and I think I also added the right modules to be built into it not have them be modules ( any idea if I can make sure I chose the correct drivers). After I was done I needed to install in using pacman -U. It told me it conflicted with kernel26 or something, and it asked if I wanted to replace it. Do I want to replace the current with the new? Or can I have them side by side? I know I can have multiple kernels, so it confused me a little.

    Still new with all this, but I'm pretty sure you don't want to replace your current kernel, or you could mess your system up should your newly compiled kernel not work.
    When you created your PKGBUILD did you by any chance forget to change its name? You should have something like "pkgname=linux-custom" (there's more to change, check the wiki for the full list) instead, so that your new kernel will be called "linux-custom" (or whatever you call it), and it can be installed alongside the (Arch) official "linux"
    After that, you can put both in your bootloader, and boot the one you want. But yeah I think you definitely want to keep the official kernel alongside yours, just in case.

  • [Solved] Error compiling kernel 2.6.36.2 patched with MOSIX

    Hi, I'm a new user in this forum!
    I'm trying to compile manually the kernel version with MOSIX-2.29.0.1 for computer clustering. But When I try to compile it with make command there is an error:
    In file included from arch/x86/kernel/signal.c:17:0:
    include/linux/tracehook.h: In function ‘tracehook_unsafe_exec’:
    include/linux/tracehook.h:164:40: error: ‘struct task_struct’ has no member named ‘mflags’
    arch/x86/kernel/signal.c: In function ‘do_notify_resume’:
    arch/x86/kernel/signal.c:884:44: error: ‘struct task_struct’ has no member named ‘parent_waiting’
    make[2]: *** [arch/x86/kernel/signal.o] Error 1
    make[1]: *** [arch/x86/kernel] Error 2
    make: *** [arch/x86] Error 2
    I have launched make menuconfig and I have configured the kernel in this way:
    Configure the following option:
          CONFIG_FUSE_FS
            File systems  --->  FUSE (Filesystem in Userspace) support
          CONFIG_SYSVIPC
            General setup  --->  System V IPC
       But make sure that the following is NOT CONFIGURED:
       CONFIG_HEADERS_CHECK"
            'Kernel hacking' ---> 'Run 'make headers_check' when building vmlinux'
    What is the problem?
    Last edited by andychaser (2011-02-17 12:37:50)

    I've solved the issue, infact there was a problem with the patch. Now I am able to compile the kernel.
    Thanks anyway!

  • Compile Kernel with ABS

    I'm trying to figure out how to compile a kernel using the ABS.  My biggest problem is that I cant figure out where to get the stock config file.  A couple of wikis and posts refer to files that I don't seem to have.  I was also wondering how the initram used in the newer kernels affects compiling a new one.  Do I need to create one with my custom kernel or is it something I shouldn't worry about?  Thanks.

    Start here
    You can get the stock Arch config from abs (simply run abs with root perms and see /var/abs/kernels).
    However, whether you want to use initramfs is not yet covered in the wiki.  In theory, if you are building your own kernel for your machine and no other, you don't need to use initramfs, unless you want to use an encrypted root partition - you probably don't at this point.

  • ROSS CPU didn't work with kernel patch 112233-07

    Just noticed my HyperSPARC (ROSS CPU for S10/S20) had problem with kernel patch.
    Got 2 X 180Mhz ROSS CPUs running fine with Solaris 9 (kernel level 112233-07) on S20 until applied the Recommended patches set (kernel level 112233-12), once the patches set installed and reboot, the S20 won't boot up anymore and showed some error on the kernel...
    Reinstall again the Solaris 9 (kernel level 112233-07), and applied the Recommended patches set without kernel patch 112233-12, system boot up fine without issue.
    Was looking around but didn't find anyone else got same issue (even on Sunsolve site) like me, maybe the box is too old to play with...
    Cheers,

    Oops, put wrong patch ID in subject...

  • Steps for Kernel Patch Updation on Solaris 10 X4100 with 2disks mirrored

    Hi all,
    I have Solaris 10 10/06 (118855-19) installed on one of the X4100 server. This is the time for me to update the latest kernel patch (118855-36). We have two disks mirrored. My questions are,
    1) Do i need to detach any of the disk from the mirror before doing any patching.
    2) Is it possible to install the patches without detaching any disks from the mirror. (i.e. installeing patch on mirrored root filesystem)
    3) how to boot from the second disk in case the patch installation creates problem while booting up.
    Any suggestions or steps which you have already implemented for the above scenario.

    This isn't really a question for this forum, you may be better to look at some of the sys-admin forums for a complete answer.
    You should not need to break the mirror in order to apply the kernel patch, however doing so would allow for quicker recovery of the system should something go wrong during patching.
    I would strongly advise that you read the special install instructions for the kernel patch prior to installing it.
    http://sunsolve.sun.com/search/document.do?assetkey=1-21-118855-36-1
    You may also wish to use a patch cluster rather than smpatch/updatemanager, these can be downloaded from SunSolve:
    http://sunsolve.sun.com/private-cgi/show.pl?target=patchpage

  • Compiling custom kenel with ABS problems

    I am tring to install 2.6.32-rc6 kernel using. ABS. I have this in my PKGBUILD
    #pkgname=kernel26 # Build stock -ARCH kernel
    pkgname=kernel26-32rc6 # Build kernel with a different name
    _kernelname=${pkgname#kernel26}
    _basekernel=2.6.32-rc6
    But makepkg is complaining that hyphens are not allowed in _basekernel. With out that I cannot download the 32-rc6 kernel.
    Please help.

    Did you try with something like this ?
    # pkgname=kernel26 # Build stock -ARCH kernel
    pkgname=kernel26-32rc6 # Build kernel with a different name
    _kernelname=${pkgname#kernel26}
    _basekernel=2.6.32
    pkgver=${_basekernel}-rc6
    pkgrel=1
    #_patchname="patch-${pkgver}-${pkgrel}-ARCH"
    #install=kernel26.install
    source=(http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-$pkgver.tar.bz2
    # the main kernel config files
    config config.x86_64 kernel26.preset)
    If you'r using initramfs to boot, you should edit kernel26.install too.

  • Kernel Patch upgrade results into error

    Recently, we upgraded our R/3 640 kernel from patch number 196 to 327. It went successful.
    But now, the Sales and order team is having problem in saving the orders(VA02, VA01).
    While saving Sales order, error pops up saying "dialog step number missing". 
    Kindly suggest.

    Hi ppl,
    The problem has been resolved.
    As i said, problem wasnt with the upgrade, but came thereafter, functional team faced issues while switching between the windows.
    Problem was with the Gui level, it needed to be upgraded too after the kernel patch upgrade.
    Thanks a lot for putting your thoughts.
    Thanks

  • Linux 3.14.2-1 ARCH config error - will not build with ABS [SOLVED]

    Hi Guys,
    I need to compile my kernels with ABS because I need 16 DVB adaptors instead of 8. This works normally just fine. Today I tried to compile newest kernel and got following error during config. For the record 3.14.1-1 built just fine.
    Makefile:615: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
    SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h
    SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_64.h
    SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_x32.h
    SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_32.h
    SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_32_ia32.h
    CHK include/config/kernel.release
    SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_64_x32.h
    UPD include/config/kernel.release
    SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_64.h
    WRAP arch/x86/include/generated/asm/clkdev.h
    CHK include/generated/uapi/linux/version.h
    UPD include/generated/uapi/linux/version.h
    CHK include/generated/utsrelease.h
    UPD include/generated/utsrelease.h
    HOSTCC arch/x86/tools/relocs_32.o
    HOSTCC arch/x86/tools/relocs_64.o
    HOSTCC arch/x86/tools/relocs_common.o
    HOSTLD arch/x86/tools/relocs
    CC kernel/bounds.s
    gcc: error: unrecognized command line option ‘-fstack-protector-strong’
    /home/server/core/linux/src/linux-3.14/./Kbuild:35: recipe for target 'kernel/bounds.s' failed
    make[1]: *** [kernel/bounds.s] Error 1
    Makefile:884: recipe for target 'prepare0' failed
    make: *** [prepare0] Error 2
    ==> ERROR: A failure occurred in prepare().
    Aborting...
    Thanks for the help
    Last edited by wdirksen (2014-05-02 20:31:32)

    wdirksen wrote:...I just moved to New Zealand...
    Beautiful part of the the world... you just need to watch out for Saruman and his orc army
    wdirksen wrote:... and the packages in the NZ mirror are not all in sync at the same time.
    Use reflector....
    % which upp
    upp: aliased to reflector -c "United States" -a 1 -f 3 --sort rate --save /etc/pacman.d/mirrorlist && cat /etc/pacman.d/mirrorlist && sudo pacman -Syyu
    You need to `chmod youruser:yourgroup /etc/pacman.conf` for that to work if run by non-root.
    Last edited by graysky (2014-05-02 20:33:38)

Maybe you are looking for

  • Cannot delete photos from my desktop

    When I try to delete anything from my desktop, I am asked for my password to authenticate. This has never happened before and will not let me delete anything from my desktop saying I do not have sufficient privileges. Any idea why - last update was f

  • You're miraculous if you can solve this

    It involves the mini and the inMotion speakers I connected to. Because my AC to DC adapter broke that connected the inMotion to my iPod mini, I went out and got a replacement AC power adapter... well... I read directions, and set the adapter to 9V ou

  • How to lock panels in fullscreen mode

    Hi all This might be a silly question, but since I converted from CS3 on Windows to CS5 on Mac I´ve been unable to do the following with the layout: I want the panels to be locked to the main window in full screen mode, so that when I open and work w

  • HT1725 My movie rental wont complete download. stops at 1.52gb everytime. any help please!

    I tried renting batman dark night rises, but everytime it downloads it stops at 1.52gb and won't go any further, anyone know of any help?

  • Wildcards in aci's

    I would like to know if it is possible to use wildcards in the attribute list of an orclaci. For instance I would like to restrict access to all attributes starting with kg, but allow access to all others. I don't want to list them all, especially if