LSI SAS 1064 Linux kernel build on x4600
Has anyone built a newer Linux kernel on a x4600 that uses the LSI SAS 1064 controller?
I don't seem to be able to get it to mount the partition after it reads the ramdisk.
Thanks in advance.
Message was edited by:
AragonX
I performed all these steps from the FAQ (skipped # mount /dev/sdx boot/ (your /boot partition) as I have no dedicated boot partition)
# mkdir /mnt/arch
# mount /dev/sdx /mnt/arch (your root partition)
# cd /mnt/arch
# mount -t proc proc proc/
# mount -t sysfs sys sys/
# mount -o bind /dev dev/
# chroot . /bin/bash
# pacman -Syu
# pacman -S udev
# pacman -S mkinitcpio
# mkinitcpio -p linux
does not fix the problem but brings up other errors when executing
# pacman -S udev
# pacman -S mkinitcpio
warning: could not get filesystem information for /bootmnt: No such file or directory
warning: could not get filesystem information for /cowspace: No such file or directory
warning: could not get filesystem information for /sfs/root-image: No such file or directory
warning: could not get filesystem information for /sfs/lib-modules: No such file or directory
warning: could not get filesystem information for /sfs/usr-shares: No such file or directory
warning: could not get filesystem information for /repo/core/x86_64: No such file or directory
warning: could not get filesystem information for /repo/core/any: No such file or directory
warning: could not get filesystem information for /bootmnt: No such file or directory
warning: could not get filesystem information for /dev/pts: No such file or directory
warning: could not get filesystem information for /dev/shm: No such file or directory
Similar Messages
-
Hello.
I have a v20z server with Red Hat Enterprise V3 installed(kernel 2.4.21) and I want to upgrade to 2.6.14 kernel for real time reasons. I just compile and install this kernel(using http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html as guide), but when I restart the computer, a kernel panic appears after load the modules. This is the message :
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0).
I think grub is not the problem. When I boot up with 2.4.21 kernel, when the mptscsih module is loaded, some information about my scsi disks appears, but with 2.6.14 mptscsih, I can��t see any information. I suppose my kernel��s configuration is incorrect, but I don��t know where is the mistake. The scsi support is compiled as part of the kernel.
Any ideas will be wellcome.
Well, and sorry for my horrible englishSorry Bill, I should have made that point myself, I actually noticed the thread and answered it without thinking about what furum it should be. Aside from the fact that the thread is incorrectly posted here on the hardware forum, Ivan has also overlooked basic troubleshooting for custom Linux kernels: if the complied kernel fails to boot on a systems that a standard kernel loads perfectly, the configuration file did not include support for that device. The only way to recover is to reconfigure and recompile including support for the device. If Ivan links to the forum that he moves the thread to I'd be happy to continue discussing it there. Perhaps the V6x forum should be renamed to x86:
http://cobalt-forum.sun.com/forum/index.php?t=thread&frm _id=6&</a> -
Nikal linux kernel 2.6.11.8 build fails
I am trying to install nidaqmxbase-1.5.0-f2, but the install keeps failing. I tried installing with a stock FC3 kernel, but the build has failed. I have since tried again after building a stock linux 2.6.11.8 kernel, but I get the same error message. The "warning: `packed' attribute ignored" in particular is one I haven't seen before.
Attachments:
nikal.log.txt 5 KBmyric wrote:
I am trying to install nidaqmxbase-1.5.0-f2, but the install keeps failing. I tried installing with a stock FC3 kernel, but the build has failed. I have since tried again after building a stock linux 2.6.11.8 kernel, but I get the same error message. The "warning: `packed' attribute ignored" in particular is one I haven't seen before.
I found the answer to my question in another thread:
http://forums.ni.com/ni/board/message?board.id=250&message.id=11286&requireLogin=False
It appears that NI-KAL doesn't like the 2.6.10+ linux kernel due to a change in the API. Both the kernels I tried were 2.6.10 plus.
Perhaps in the next release if nidaqmxbase the latest kernel will be supported? Hint, hint, pretty-please from a paying customer. ;-) -
[Solved]The linux kernel with build in bootloader?
First of let me apologize if I'm making no sense at all. This isn't really my area of expertise.
I just recently stumbled upon some rather interesting "news" about the linux kernel developers working to implement a an EFI/GTP (I think) bootloader in the kernel it self. I would very much like to know if this is actually true, I'd like to learn more and follow the development, but I haven't been able to find any relevant information, appart from the incomplete mailing list I stumbled upon.
I suspect that I'm simply using the wrong search parameters. Again, it's not like I know too much about what I'm doing.
In any case, if you have even the slightest idea what I'm talking about, please do guide me in the right direction.
Best regards.
Last edited by zacariaz (2012-03-01 20:02:04)Gusar wrote:
litemotiv wrote:I was mainly thinking about a way to boot straight into Arch from rEFIt without chainloading grub/syslinux first.
Thanks to the info and links the.ridikulus.rat provided, I've now learned a bit more about this stuff (I'm probably still missing a lot ). Basically, rEFIt is a manager that launches bootloaders. With EFI_STUB, the kernel is it's own bootloader, so what you say is indeed possible - start linux from rEFIt without going through grub/syslinux. Well, it would be possible if there wasn't for one huge problem - rEFIt doesn't allow passing options, which is needed in this case. But that's where rEFIt's fork (rEFInd) comes into play.
Further, there are patches on the kernel mailing list that will make it possible for an EFI_STUB kernel to read options from a file. Then not even rEFInd will be needed. Strictly speaking it isn't needed even now, but you need to type the options manually on the efi shell, which isn't very convenient. Fun stuff all this, innit? . It's a whole new crazy world.
Cool, thanks for the pro-active research! -
Is RDAC supported in Oracle Unbreakable Linux kernel 2.6.32-100.0.19.el5?
Dear,
Is RDAC supported in Oracle Unbreakable Linux Kernel 2.6.32-100.0.19.el5?
If supported, please point to the download link.
We require this in order to plan for the OEL 5.5 kernel upgrade to ULK and to connect SUN SAN storage array 6180.
Thanks,
...bashaFrom what I can gather you will need to compile the driver from source in order to use the RDAC driver with the UEK kernel. Chances are that it won't compile properly under the UEK kernel, which is more up to date than the RHEL kernel.
You will have to start the system from the supplied original RHEL kernel in order to use the binary IBM RDAC driver distribution. The following is available: http://www.lsi.com/sep/Pages/rdac/ds4000.aspx and http://www.lsi.com/sep/Pages/rdac/ds3000.aspx
You may however be able to use Multipath, which is build in also in the UEK kernel. To get the current supported configurations for IBM System Storage it is best to use the interoperability matrices located at http://www-03.ibm.com/systems/storage/product/interop.html. You can use the link to the "System Storage Interoperation Center (SSIC)" to query your specific configuration (http://www-03.ibm.com/systems/support/storage/ssic/interoperability.wss)
Edited by: Dude on Feb 12, 2012 2:17 PM -
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? -
OK...I'm close! I got a package to build, but even though I changed EXTRAVERSION from -ARCH to -RT I get this error when trying to install:
kernel26rt: /usr/src/linux-2.6.21-ARCH/include/sound/cs46xx_dsp_scb_types.h: exists in filesystem
kernel26rt: /usr/src/linux-2.6.21-ARCH/include/sound/cs46xx_dsp_spos.h: exists in filesystem
etc. forever.
I did make menuconfig and I know I changed it...for sure.
PKGBUILD:
pkgname=kernel26rt
_basekernel=2.6.21
pkgver=2.6.21.1
pkgrel=1
pkgdesc="The Linux Kernel and modules + RT patchset"
arch=(i686)
url="http://www.kernel.org"
backup=('boot/kconfig26' etc/mkinitcpio.d/${pkgname}.preset)
depends=('module-init-tools' 'mkinitcpio>=0.5.13')
install=kernel26.install
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$_basekernel.tar.bz2
config
kernel26rt.preset
mkinitcpio-$pkgname.conf
http://people.redhat.com/mingo/realtime … .6.21-rt1)
md5sums=('1b515f588078dfa7f4bab2634bd17e80' 'dd0ab2770aa77868a0ca73822daecdfe'\
'9285f4e91bd1b34ef18f4a35884a6419' '36858bd6a0bca63d2aa901b2e42d4a05'\
'7db73b1fbf3cd47adf9d3d86a6edc1d6')
build() {
[ "${CARCH}" = "i686" ] && KARCH=i386
[ "${CARCH}" = "x86_64" ] && KARCH=x86_64
cd $startdir/src/linux-$_basekernel
#RT Patchset
patch -Np1 -i ../patch-2.6.21-rt1 || return 1
# remove the extraversion from Makefile
#sed -i 's|^EXTRAVERSION = .*$|EXTRAVERSION =-rc7|g' Makefile
sed -i 's|^EXTRAVERSION = .*$|EXTRAVERSION =|g' Makefile
# get rid of the 'i' in i686
carch=`echo $CARCH | sed 's|i||'`
cat ../config | sed "s|#CARCH#|$carch|g" >./.config
# build the full kernel version to use in pathnames
. ./.config
#_kernver="2.6.21-rc7${CONFIG_LOCALVERSION}"
_kernver="${_basekernel}${CONFIG_LOCALVERSION}"
# load configuration
make menuconfig # build!
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
install -D -m644 .config $startdir/pkg/boot/kconfig26
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel
for i in acpi asm-generic asm-$KARCH config linux math-emu media net pcmcia scsi sound video; do
cp -a include/$i $startdir/pkg/usr/src/linux-${_kernver}/include/
done
etc...
copied from kerenel26 from here out.
Maybe I have to do more editing in the build dir?
Thanksmy guess: he got it (sorta) working
-
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 -
The latest stable version of the Linux kernel is: 2.6.25 !!!
The latest stable version of the Linux kernel is: 2.6.25
as u know
http://www.kernel.org/
after testing ,hope included in final core iso
2008.04ekerazha wrote:
brain0 wrote:First of all, ext4 is under heavy development and possibly buggy. Furthermore, the on-disk format is not guaranteed to be stable yet.
No, it's not under heavy development, it is almost complete. The only missing part is the "dalayed allocation". The on-disk format, as I've already said, shouldn't change anymore.
With this patch series, it is expected that ext4 format should be settling
down. We still have delayed allocation and online defrag which aren't
quite ready to merge, but those shouldn't affect the on-disk format.
I don't expect any other on-disk format changes to show up after this
point, but I've been wrong before.... any such changes would have to
have a Really Good Reason, though.
Source: http://lkml.org/lkml/2008/1/21/392
If you read this carefully, you don't want to use ext4 just now. You also should consider that ext4 is virtually untested compared to filesystems like ext3 which has been used for years in many production environments. I wouldn't read "I don't expect any other on-disk format changes" as "There will be no more changes" if I had important data.
brain0 wrote:Second, we don't have a single filesystem built into the kernel, they are all modular - and I don't see a reason why this should ever change.
I remembered some filesystems were "built-in". Evidently I remember wrong (well... and I remember the filesystem for the root partition had to be built into the kernel, but my knowledge on this point is not very updated).
You're so 90's. If we would build everything into the kernel that everyone needed to boot, it would be 5MB or 10MB instead of just 2MB. Everything is as modular as possible now (there are some exceptions which should be ironed out in one of the next releases). -
Modifying the stock arch linux kernel and kernel timer frequency
so if i understand correctly, if we want to modify the stock arch linux kernel, we have to pull it off of abs. ie "ABSROOT=. abs core/linux" then modify the pkgbuild, uncommenting out make menuconfig and setting the pkgbase name to something different than stock. ie, "linux-custom" then update the checksums followed by importing the gpg keys, ie "gpg --recv-keys 79BE3E4300411886 and gpg --recv-keys 38DBBDC86092693E" for the kernel and patches. then run makepkg -s.
we can't just run make menuconfig on the current kernel that's installed?
and if we pull the linux kernel from abs to customize, does it already come preconfigured with all the arch changes and settings? like its no different than the current one installed?
i just ask because for the most part, i like the current arch kernel, there are just a few minor things i want to change but kept everything else the same as stock arch linux kernel.
also, i herd arch uses 300hz for its timer. whats the benefits and disadvantage of using 300hz over 1000hz for a desktop system?orlfman wrote:we can't just run make menuconfig on the current kernel that's installed?
No you can't, because the kernel then has to be compiled so the kernel will run with the different tick rate.
orlfman wrote:
and if we pull the linux kernel from abs to customize, does it already come preconfigured with all the arch changes and settings? like its no different than the current one installed?
i just ask because for the most part, i like the current arch kernel, there are just a few minor things i want to change but kept everything else the same as stock arch linux kernel.
As I understand it from the Wiki, the ABS pulls the PKGBUILD and other arch-specific sources from the ArchLinux script server. However, I don't use the ABS, but pull the files I need directly from the ArchLinux SVN and build using makepkg[1] after making the necessary changes.
orlfman wrote:Also, I heard arch uses 300hz for its timer. whats the benefits and disadvantage of using 300hz over 1000hz for a desktop system?
You're in for a technical discussion here. This has a reasonably friendly discussion on kernel tick rates.
Basically, higher tick rates = a higher level of timing precision & higher processor load, lower tick rates = lower level of timing precision & lower processor load.
[1] Technically, I use the clean chroot manager package, which is a wrapper for makechrootpkg (which in turn is a wrapper for running makepkg in a clean chroot if I'm not mistaken). -
GRUB corrupted after custom kernel build
Hi
I have developed my ARCH installation for development purpose.
I am new to linux kernel development.
I compiled the kernel and placed the kernel image in the /boot folder and modified grub.cfg to point at it.
After that I selected my arch installation and it didnt succesfully boot the manually compiled kernel.
Then I rebooted and selected the arch-fallback and it booted succesfully.
After that the book I am referring to suggested to use the 'make modules_install' to load modules and then I rebooted.
After that grub is giving me a "minimum bash like interface"
How can I boot the machine from this interface. (if i can)?
Also i tried to reinstall grub (from an ubuntu live disk) but it said it couldnt' find /boot/grub
Re-installing grub from an Arch live disk was succesful but it didn't fix the problem
Please Help
Thanks in advance!I think you are missing a driver that you need to boot. Is your kernel still using the initrd, or did you build in all of the modules you need in order to boot?
If you are depending on the initrd to provide modules during boot, then the modules burned into that initrd need to be compatible with your custom kernel -and- (I think) the kernel has to have the same name as the stock kernel.
When I build a custom kernel, I usually do away with the initrd and build the required modules to boot into the kernel. I only modularize those that I do not need everytime I boot; for example USB based device drivers.
To boot, you need your disk controller, the file systems drivers of the volumes to be mounted at boot, video hardware drivers, keyboard drivers, maybe some real time clock drivers, PCI Drivers, Maybe ISA and LPC bus drivers.
Take a look at this site. The guy who runs it is legendary on the Gentoo forums, his site might provide some insight into how to configure your kernel.
tl;dr: The problem is not Grub.
Edit: You may also want to look at the Gentoo Handbook. Being Gentoo, they have some pretty good information on how to configure a kernel.
Last edited by ewaller (2013-05-09 18:15:30) -
MDM Not Able To Load Linux Kernel Images Larger Than 32MB?
Hi All,
I've been building linux initramfs images for use with a Kintex7 (KC705) running a MicroBlaze processor and have been running into an issue with loading the images using the MicroBlaze Debug Module. It seems the system won’t boot if the image is larger than 32 MB. Unfortunately, my use case requires all application code to be contained in the kernel image and I won't have local non-volatile to boot from.
Some key factors:
Petalinux 2014.4
FPGA image built using Vivado 2014.4 on Windows 7
1GB RAM on KC705
Loading images using TCL script on XMD on Windows 7
As an example, I built an image that would fit within the 32 byte "limit" and booted it with no issues:
Image Type: MicroBlaze Linux Kernel Image (uncompressed)
Data Size: 31035828 Bytes = 30308.43 kB = 29.60 MB
MicroBlaze Processor Configuration :
Version............................9.4
Optimization.......................Performance
Interconnect.......................AXI-LE
MMU Type...........................Full_MMU
No of PC Breakpoints...............1
No of Read Addr/Data Watchpoints...0
No of Write Addr/Data Watchpoints..0
Instruction Cache Support..........on
Instruction Cache Base Address.....0x80000000
Instruction Cache High Address.....0xbfffffff
Data Cache Support.................on
Data Cache Base Address............0x80000000
Data Cache High Address............0xbfffffff
Exceptions Support................on
FPU Support.......................off
Hard Divider Support...............on
Hard Multiplier Support............on - (Mul64)
Barrel Shifter Support.............on
MSR clr/set Instruction Support....on
Compare Instruction Support........on
PVR Supported......................on
PVR Configuration Type.............Full
Data Cache Write-back Support......off
Fault Tolerance Support............off
Stack Protection Support...........off
Connected to "mb" target. id = 0
Starting GDB server for "mb" target (id = 0) at TCP port no 1234
System Reset .... DONE
Downloading Program -- simpleImage.mb
section, .text: 0x80000000-0x802a2b27
section, .init.text: 0x80359000-0x803727a3
section, .init.ivt: 0x803749c0-0x803749e7
section, .note.gnu.build-id: 0x00000000-0x00000023
section, __fdt_blob: 0x802a2b28-0x802aab27
section, .rodata: 0x802ab000-0x8032085f
section, __ksymtab: 0x80320860-0x803254f7
section, __ksymtab_gpl: 0x803254f8-0x80327f17
section, __ksymtab_strings: 0x80327f18-0x803380f6
section, __param: 0x803380f8-0x80338417
section, __modver: 0x80338418-0x80338fff
section, __ex_table: 0x80339000-0x8033a59f
section, .sdata2: 0x8033a5a0-0x8033afff
section, .data: 0x8033b000-0x8035809f
section, .init.data: 0x803727a4-0x803749bf
section, .init.setup: 0x803749e8-0x80374cdb
section, .initcall.init: 0x80374cdc-0x80374fa3
section, .con_initcall.init: 0x80374fa4-0x80374fab
section, .init.ramfs: 0x80374fac-0x81d991b3
section, .bss: 0x81d9a000-0x81dabb7b
Then, I added a 10MB random file (created using dd from /dev/urandom) to the same rootfs and tried booting again unsuccessfully:
Image Type: MicroBlaze Linux Kernel Image (uncompressed)
Data Size: 41521588 Bytes = 40548.43 kB = 39.60 MB
MicroBlaze Processor Configuration :
Version............................9.4
Optimization.......................Performance
Interconnect.......................AXI-LE
MMU Type...........................Full_MMU
No of PC Breakpoints...............1
No of Read Addr/Data Watchpoints...0
No of Write Addr/Data Watchpoints..0
Instruction Cache Support..........on
Instruction Cache Base Address.....0x80000000
Instruction Cache High Address.....0xbfffffff
Data Cache Support.................on
Data Cache Base Address............0x80000000
Data Cache High Address............0xbfffffff
Exceptions Support................on
FPU Support.......................off
Hard Divider Support...............on
Hard Multiplier Support............on - (Mul64)
Barrel Shifter Support.............on
MSR clr/set Instruction Support....on
Compare Instruction Support........on
PVR Supported......................on
PVR Configuration Type.............Full
Data Cache Write-back Support......off
Fault Tolerance Support............off
Stack Protection Support...........off
Connected to "mb" target. id = 0
Starting GDB server for "mb" target (id = 0) at TCP port no 1234
System Reset .... DONE
Downloading Program -- simpleImage.mb
section, .text: 0x80000000-0x802a2b27
section, .init.text: 0x80359000-0x803727a3
section, .init.ivt: 0x803749c0-0x803749e7
section, .note.gnu.build-id: 0x00000000-0x00000023
section, __fdt_blob: 0x802a2b28-0x802aab27
section, .rodata: 0x802ab000-0x8032085f
section, __ksymtab: 0x80320860-0x803254f7
section, __ksymtab_gpl: 0x803254f8-0x80327f17
section, __ksymtab_strings: 0x80327f18-0x803380f6
section, __param: 0x803380f8-0x80338417
section, __modver: 0x80338418-0x80338fff
section, __ex_table: 0x80339000-0x8033a59f
section, .sdata2: 0x8033a5a0-0x8033afff
section, .data: 0x8033b000-0x8035809f
section, .init.data: 0x803727a4-0x803749bf
section, .init.setup: 0x803749e8-0x80374cdb
section, .initcall.init: 0x80374cdc-0x80374fa3
section, .con_initcall.init: 0x80374fa4-0x80374fab
section, .init.ramfs: 0x80374fac-0x827991b3
section, .bss: 0x8279a000-0x827abb7b
I've also tried the same test with a plain Petalinux image and none of my application code or other customizations to rule out a configuration issue. Additionally, I've tried updating Vivado to 2015.2 and rebuilding the FPGA image, also with no success.
FYI, here is the TCL script used to load the images:
fpga -f system_top.bit
connect mb mdm
after 2000
dow simpleImage.mb
con
disconnect 0
I've done a bunch of research on initramfs and haven't seen anything that points to a size limit (except as it relates to RAM size). Anyone have an idea what's going on?
Thanks!
-NickSome additional information:
When the system fails to boot, there is no error message displayed either on the XMD window or the linux console output. The console remains blank.
I have been able to add random files to the ramdisk that do not push the size over the 32MB boundary and the system successfully boots. -
How can I pause resume kernel building
Hello,
I have an idea.
I want to build android kernel, but I afraid I cannot finished, because sometimes I haven't enough time. I need to reboot, or switch off the pc.
So how can I pause, save state or resume the build process.
I though about it from virtualbox, but mine problems are. The VB do full virtual pc, I dont want to separate cpu, memory and something, and install new arch linux to guest.
I want only save and resume the build process.
How can I do?
I wait your answer.
Thanks Gyu..If you are compiling kernel "by hand", cancel it with ctrl+c for example, and restart the compilation later, it won't recompile the parts you had already compiled (unless you change your .config or something).
so basically the kernel building should be resumed automatically.
this probably won't work if your building the kernel with makepkg though. -
FX5600 fails under Linux kernel 2.4.22
I’m attempting to make an FX 5600 graphics card work with Red Hat Linux 9 kernel 2.4.22 1 2115 n.
I’ve downloaded and installed the NVIDIA driver from http://www.nvidia.com/object/linux_display_ia32_1.0-4496
It worked fine last week when I was running the 2.4.20 kernel. The NVIDIA driver for the FX 5600 card installed without error and worked fine. But Linux 2.4.20 would not recognize the Ethernet card that is onboard the MSI 875P Neo motherboard. The website http://www.linuxhardware.org/article.pl?sid=03/08/19/1521256&mode=thread
Says I must have a newer kernel, 2.4.21 or higher before Linux would work with all the features of the MSI 875P Neo motherboard.
With a lot of help from a friend at work the new kernel, 2.4.22, has been installed. But it’s disabled my NVIDIA driver for the FX 5600. And the NVIDIA driver won’t install under the new kernel, returning an error message saying:
“ERROR: Unable to build the NVIDIA kernel module.”
I’ve been studying the support documentation, the README text file for the driver linked to on the NVIDIA download page. But I’ve not found an answer to this problem.
The NVIDIA page, under support, says to contact the manufacturer if you have any problems. So here I am. Any suggestions?
Any estimates on how long it will be before the NVIDIA driver set is updated to support Linux kernel 2.4.22 ?Maybe this thread will help you:
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:30011178429375
C. -
Linux: Kernel Preemption, To Enable Or Not To Enable
The default 2.6.4 Arch Linux kernel .config has 'CONFIG_PREEMPT=y'.
Not everyone has been happy with kernel preemption, however. There is an interesting discussion of this under the title "Linux: Kernel Preemption, To Enable Or Not To Enable at http://kerneltrap.org/node/view/2702
The text of the article is repeated here:
"A recent bug report on the lkml complained of significant performance degradation from enabling CONFIG_PREEMPT, kernel preemption. 2.6 kernel maintainer Andrew Morton [interview] pointed out that such degradation from enabling kernel preemption is not normal, instead likely from it triggering a bug. However, an interesting conversation on the merits of kernel preemption followed.
Andrea Arcangeli, author of the 2.4 virtual memory subsystem, bluntly suggested, "keep preempt turned off always, it's useless. Preempt just wastes cpu with tons of branches in fast paths that should take one cycle instead." Andrew Morton noted, "preempt is overrated." However, he went on to point out that kernel preemption has been very useful in detecting locking bugs. He added, "it has been demonstrated that preempt improves the average latency. But not worst-case, because those paths tend to be under spinlock."
Robert Love [interview] replied directly to Andrea's comments saying, "I think you are really blowing the overhead of kernel preemption out of proportion," going on to agree with Andrew's statements. He further explained:
"I also feel you underestimate the improvements kernel preemption gives. Yes, the absolute worst case latency probably remains because it tends to occur under lock (although, it is now easier to pinpoint that latency and work some magic on the locks). But the variance of the latency goes way down, too. We smooth out the curve. And these are differences that matter."
There is more discussion and feedback with the article (including the original bug report).I like preemption. it the "democracy" heaven of processes and threads. This post was interesting, but the point is this bug..?
if the bug is found, who can say that preemption in the kernel is not a good idea?
thanks for posting though ;P
Maybe you are looking for
-
Warranty clarification required
Hi, I am based in the UK and purchased an Apple iPad3 new back in March this year. Recently I noticed my iPad was not charging and did some basic swap tests with a friends AC adapter unit. The AC adapter is faulty so I contacted the retailer (Comet)
-
PHOTOSHOP ELEMENTS 12 EDITOR NOT WORKING
THE EDITOR HAS SUDDENLY STOPPED WORKING ON MY ELEMENTS 12. ALL I KEEP GETTING IS " PHOTOSHOP EDITOR HAS STOPPED WORKING, WINDOWS WILL CLOSE THE PROGRAM AND INFORM YOU IF IT FINDS A SOLUTION ". WE ALL KNOW THAT WINDOWS NEVER FINDS A. SOLUTION
-
SAP TDMS / CCS (for utilities)
The TDMS is compatible with SAP CCS OIl/gas refining industry? Thank you Rogério
-
Tracking down .log file creators?
I have had disk space getting eaten up and discovered using "WhatSize" a number of files in the private/var folder set (see discussion on similar in Nov 2008) The response to the query then was to track down what was writing the files in the first pl
-
If I already have an Itunes I.D. and account, how do I set up a rescue email and change my security questions?