Arch Kernel Release Cycle

Hi guys,
I recently started compiling my own kernels, but I still use the arch packages as a guideline. For example I use the patches provided by Arch Linux, and at the moment I stay with the version which is in the arch repositories.
So for example if I want to compile 2.6.35.7, the PKGBUILD I use just downloads the source for 2.6.35, and the patch for .7 from Arch. Would it be 'possible' to use the stock kernel patches? What is different in the Arch packages (I know I can just diff, but why are there Arch specific patches)?
Arch gernerally updates the kernel rather fast. But some versions are skipped. Is there any policy on that? For example at the moment 2.6.36 is out, yet Arch packages 2.6.35.8 as the latest.
Thanks and kind regards
Julian

2.6.36 is in [testing]. Kernels usually do not make it to [core] until the around .2 version.
The Arch specific patches are rather small... http://projects.archlinux.org/linux-2.6 … ee/patches AUFS2 and some logo replacements.

Similar Messages

I do not understand kernel release cycles on Arch Linux

I see that [core] has kernel version 3.16.4 but upstream is 3.16.6. We have 3.17.1 in [testing] so it is getting quality controlled. I don't understand why 3.16.6 is not in [core]. It is tough to maintain two branches of the kernel? I see some major fixes in 3.16.6 that should be pushed to users. Thank you.

maggie wrote:I don't understand why 3.16.6 is not in [core].
You can compile 3.16.6 yourself from ABS with minor modifications to the PKGBUILD.
nomorewindows wrote:I think they went onto 3.17.2 in testing the other day.
3.17.1-1 unless you have a time machine

[Fake News] Arch Linux to change its release cycle

Today the Arch Linux community proclaimed that Arch Linux will change its release cycle and version numbering, as this was requested by billions of corporate goonies, Freemasons and Illuminati throughout the universe.
Releases will henceforth be scheduled in intervals deemed posh by the GNU/Linux community at the particular moment. The version numbering will be based on year the a new release is being published. Arch Linux "2016" will be released in early 2006. All following releases will have an offset of at least 10 years to underline how much more pure dead brilliant Arch Linux is compared to Mandrake.
To achieve a smooth transition, an transitional release will be made at once, named "Useless Marketing Edition". The Arch Linux FTP server will be configured allow one download of the iso image only. This will also be an experiment to find out how the community will be able to spread such a limited edition.
An Arch Linux user who wishes to remain nameless said in an exclusive interview with the almighty incinerator: "This is a great opportunity for Arch Linux, the new release numbering will confuse and divert computer illiterate lusers from installing our beloved Arch Linux, freeing us from answering stupid support requests. Now we can finally start to work towards our ultimate goal: To become the only GNU/Linux community being as elitist as OpenBSD's."

Ach guys, you don't get it :-(
The version numbering scheme was supposed to mock the fact Mandrake plans to release their "2006" version in 2005. That reminds of old times, when (computer) magazines were trying to beat each other releasing the most up-to-date issue to the market. The whole affair became absolutely silly, there were magazines that had the "April" issue hitting the shelves at the end of January. These "issue number wars" occur every now and then.
The funny scenario I can imagine is that other (GNU/Linux) vendors could jump onto that train and "predating" their releases further and further.
The rest is just various mockery about lusers and other things found in the Mandrake's press release. And of course the arrogantly elitist OpenBSD community always deserves getting their arses whipped ;-)

Arch Kernel Questions

(This is a really low-priority set of questions.)
I just wanted to know what some of the differences between the main stable 2.6 kernel and Arch's 2.6 kernel are. I'm not a fan of compiling kernels, so I'd like to know what decisions are made for the default kernel.
Let me be more specific;
1. linux-2.6.26.1/Documentation/java.txt: apparently, native support for java binaries is planned for the kernel. Will this be reflected in Arch's kernel as well?
2. Besides x86, what architectures are supported by the Arch kernel (linux-2.6.26.1/arch)?
3. Does the Arch kernel support virtualization by default?
4. Which drivers (if any) are excluded from Arch's kernel (linux-2.6.26.1/drivers)? (If any, why?)
5. Which filesystems are supported by the Arch kernel (linux-2.6.26.1/fs)? In the install, there are only 5 filesystems available so I'm guessing it's just those 5?
--- And any other major differences that are worth noting.
Thank you for reading!
- vsk

there is a bug with xen in kernels newer then 2.6.18.
arch's kernel is as vanilla as the stable release is from what I gather. Other then a few patches and some config changes. Arch tries to stay as close to vanilla as possible with all it's packages. just do a diff between the two configs.

[SOLVED] Arch Kernel causes problems

Since my very first time installing Arch, i was getting some errors like
Cannot parse block device ids for /dev/sdb2
Cannot find root device /dev/sdb2
and eventually i had found a work-around, by taking the kernel and initramfs files (both 2.6.25.20-114) from another Linux, and also the corresponding modules directory. (Works perfect, using Firefox on it at the moment.)
Now i want to upgrade my kernel eventually (don't have to actually, but i want to, and the problem should not happen anyway) and still, after retrieving the new kernel through pacman (creating the vmlinuz26 and kernel26.img files in /boot, as well as the modules directory) and using it, i get the SAME problem.
The Arch kernels just won't work for me...
Does anyone have an idea what it could be?
(And is there any way to copy the exact error-output i get while trying to boot?)
Thanks.
Last edited by TaylanUB (2009-10-18 03:23:36)

I'm using ext2 on the second partition (first being FAT32) of a Lexar USB Flash Stick.
# lspci
00:00.0 Host bridge: nVidia Corporation nForce2 IGP2 (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation MCP2A ISA bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP2A SMBus (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP2A USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP2A USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation MCP2A USB Controller (rev a2)
00:04.0 Bridge: nVidia Corporation MCP2A Ethernet Controller (rev a3)
00:06.0 Multimedia audio controller: nVidia Corporation MCP2S AC'97 Audio Controller (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP2A PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation MCP2A IDE (rev a3)
00:0b.0 IDE interface: nVidia Corporation nForce2 Serial ATA Controller (rev a3)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS [Radeon 9550]
01:00.1 Display controller: ATI Technologies Inc RV350 AS [Radeon 9550] (Secondary)
02:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev 46)
# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 05dc:a781 Lexar Media, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Last edited by TaylanUB (2009-10-17 11:47:41)

Why no bootsplash or fbsplash in arch kernel?

I'm not begging for a feature, if I wanted it I'd compile it myself, but I was genuinely wondering, why no bootsplash or fbsplash patches applied to the default arch kernel?
If a splash patch is included in the kernel, it doesn't have to be used if the user doesn't want, right? And bootsplash has been around for quite some time, and every time I used it it felt like stable software (as in, I had no problems with it). Now I never tried fbsplash, but why not include one of them?
I'm sure there's a good reason not to have arch patch the default kernel with either patch, I was just wondering what it is.

Amazingly, people use Arch on their laptops too.
IE Me, So I am constantly rebooting, software suspend isnt worth the effort when I boot up in under a minute.
bootsplash is also nice when you want to do some console based work, or operate entirely from the console.
As has been said, bootsplash isnt included because of Arch's keep it simple philosophy, developers only patch the kernel with what they need, no more.
Another reason, could well be that the patches are not well maintained, take a look at bootsplash.org, no recent kernels have patches. Sure bootsplash.de have them, but they always arent out until even a few weeks after the kernel.
And finally, compiling the kernel with either bootsplash or fbsplash would stop a user from having a choice between the two.
iphitus

Is the new release cycle really making Firefox faster?

The new release cycle of Firefox may help in increasing the overall speed and stability of Firefox and shorten the time, we have to wait for new features. However, at the moment this causes a lack in add-on support. If we gain speed and new features, but therefore abandon old features, that made us faster not by performance, but through a different style of using Firefox, then what have we won?
For example, with FF 5.0 - 7.0 the "Site Launcher" is not working anymore. Maybe Firefox is now loading pages faster, but I am at least twice as slow in navigating, because "Site Launcher" was - together with "All-in-one Gestures" - my most used Add-On.

Hi Patrice,
Within Apple’s slim new 21.5- and 27-inch iMacs are NVIDIA GeForce GPUs, based on our new Kepler-class architecture, which helps make them up to 60 percent faster than last year’s models. This follows news in June that Apple’s 15-inch MacBook Pro with Retina display uses Kepler GeForce GPUs.
The new 27-inch iMac offers the GeForce GTX 660M as its base GPU, with even faster GeForce GTX 675MX or GeForce GTX 680MX GPUs available. The 21.5-inch model comes with the GeForce GT 640M GPU, with an available upgrade to the GeForce GT 650M GPU.
http://blogs.nvidia.com/2012/10/big-imac-news-less-heft-more-kepler/
So, any Apps that use the GPU to assist GPU should be much faster.
Though I don't see it listed here, it may be too new, I suspect it may be supported...
http://www.adobe.com/products/premiere/tech-specs.html

[SOLVED] Can't build fglrx module for 3.4.5-1-ARCH kernel

Hello everyone!
I updated my system using
pacman -Syu --ignore glibc
everything was good, I rebooted and my fglrx module isn't working!
I tried:
sudo catalyst_build_module
Building fglrx module for 3.4.5-1-ARCH kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
Here is log
Here is quote from it: Kernel header files are absent: directory /lib/modules/3.3.4-1-ARCH/build doesn't exist! Game over
But I have the latest versions linux and linux-headers packages.
Help please. Thanks.
Last edited by metalex (2012-07-20 14:53:37)

Yes, this is my problem, I did all from here, but I still can't update glibc.
grep '^lib/' /var/lib/pacman/local/*/files
output:
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-linux-x86-64.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil.so.1
/var/lib/pacman/local/lib32-glibc-2.15-10/files:lib/
/var/lib/pacman/local/lib32-glibc-2.15-10/files:lib/ld-linux.so.2
I don't know what to do with lib32-glibc...

[SOLVED] Building fglrx module for 3.11.3-1-ARCH kernel error

I got this error today:
2013-09-28 14:07:59
Building fglrx module for 3.11.2-1-ARCH kernel ...
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
file /usr/lib/modules/3.11.2-1-ARCH/build/include/generated/autoconf.h says: SMP=1
file /usr/lib/modules/3.11.2-1-ARCH/build/include/generated/autoconf.h says: MODVERSIONS=1
file /usr/lib/modules/3.11.2-1-ARCH/build/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space
make: Entering directory `/usr/src/linux-3.11.2-1-ARCH'
CC [M] /tmp/catalyst.aHP3fa/firegl_public.o
CC [M] /tmp/catalyst.aHP3fa/kcl_acpi.o
CC [M] /tmp/catalyst.aHP3fa/kcl_agp.o
CC [M] /tmp/catalyst.aHP3fa/kcl_debug.o
CC [M] /tmp/catalyst.aHP3fa/kcl_ioctl.o
CC [M] /tmp/catalyst.aHP3fa/kcl_io.o
CC [M] /tmp/catalyst.aHP3fa/kcl_pci.o
CC [M] /tmp/catalyst.aHP3fa/kcl_str.o
CC [M] /tmp/catalyst.aHP3fa/kcl_iommu.o
CC [M] /tmp/catalyst.aHP3fa/kcl.o
CC [M] /tmp/catalyst.aHP3fa/kcl_wait.o
LD [M] /tmp/catalyst.aHP3fa/fglrx.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/catalyst.aHP3fa/fglrx.mod.o
LD [M] /tmp/catalyst.aHP3fa/fglrx.ko
make: Leaving directory `/usr/src/linux-3.11.2-1-ARCH'
Ok.
2013-10-05 14:20:34
Building fglrx module for 3.11.3-1-ARCH kernel ...
Kernel header files are absent: directory /usr/lib/modules/3.11.3-1-ARCH/build doesn't exist! Game over
2013-10-05 14:20:41
Building fglrx module for 3.11.3-1-ARCH kernel ...
Kernel header files are absent: directory /usr/lib/modules/3.11.3-1-ARCH/build doesn't exist! Game over
I don't know why, and I do not know if I care.
Last edited by patrickmaciel (2013-10-06 19:31:53)

fazo96 wrote:I think it's because of the new kernel. Reinstalling is not a solution, it's avoiding the problem ;D
Instead, I switched to catalyst-hook (I used catalyst) and upgraded to kernel 3.11.4, the latest version of xorg (there was a new one), gnome 3.10 and the module compiled perfectly, so now everything works on my system
You right, but you know... I have a lot projects in queue and not have time to search and test evertying
But, now... catalyst has installed successfully, but, I think isn't working 100%, because, when I click (for example), in a Google Chrome tab, and move to left/right, all tabs disappear or are blurry.
Anyway, thanks.

Content and your deployment/release cycle

Does anyone here have any best practices to share about how to integrate your content into the deployment and release cycle of software?
We are using a WebCenter Portal solution with content stored in the Content Server that is tightly related to the portal. So, if we deploy a new version of the portal to our test environment we wan t to export/import our content too, at the same time. Same for acceptance and production.
Is it still a manual task using the Archiver, or are you for example using scripts and RIDC?
A helpful link from Bex Huff: http://bexhuff.com/2009/04/scripting-oracle-ucm-with-jython

There are several ways to synchronize content from one system to another. Just here in the Czech republic we have used/proposed to be used:
- the Archiver
- DataGuard/file system clustering
- RIDC
There is probably not just one right solution. In your case, where I believe you need to export increments in batches, whose size will not be that big, I assume the Archiver, or some kind of BatchLoader, looks the right tool. It does not have to be fully manual - see e.g. Building IdcCommand command file to archive from UCM

TRIM command (as it applies to SSD) and the vanilla arch kernel

According to this wikipedia article, the TRIM command has been implemented in Linux since kernel version 2.6.28. I'm wondering if the vanilla Arch kernel (x86_64) has support for this compiled in and if so which module would one need to modprobe to use it?
Thanks!

graysky wrote:hmmmm... is NOMMU_INITIAL_TRIM_EXCESS the so-called "TRIM" support in the kernel?
I don't think so, that seems to be memory (ram) related (NOMMU.... MMU is related to memory access as far as I know).
All I could find with a quick google search were a few posts saying there are submitted patches and some scripts .... nothing too certain.
As always things seem to be going at the windows development speed instead of the pace technology could go, also it seems that the spec for the trim command is/was still being finalized.
http://www.linuxquestions.org/questions … ux-713006/
http://marc.info/?l=linux-kernel&m=124169431911648&w=2
http://forum.soft32.com/linux/Linux-ATA … 83626.html
http://www.ocztechnologyforum.com/forum … fb&t=60882

Glibc update and /lib/modules/extramodules-3.4-ARCH/kernel/oss/ folde

so I made the steps mentioned here: https://wiki.archlinux.org/index.php/De … iki:usrlib
after doing "find /lib -exec pacman -Qo -- '{}' \+" I see I have a lot of stuff in "/lib/modules/extramodules-3.4-ARCH/kernel/oss/" folder, BUT I don't even have oss installed. So I wonder, why are they there, and if I can delete this folder?

Like Capoeira, I also have some files left in my /lib folder:
[pieter@laptop ~]$ find /lib -exec pacman -Qo -- '{}' \+
error: cannot determine ownership of directory '/lib'
/lib/ld-linux.so.2 is owned by glibc 2.16.0-1
/lib/libcrypt.so.1 is owned by glibc 2.16.0-1
/lib/libSegFault.so is owned by glibc 2.16.0-1
/lib/libnss_dns.so.2 is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
/lib/libresolv.so.2 is owned by glibc 2.16.0-1
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/libc.so.6 is owned by glibc 2.16.0-1
/lib/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libnss_compat.so.2 is owned by glibc 2.16.0-1
/lib/libthread_db-1.0.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod-2.16.so is owned by glibc 2.16.0-1
/lib/libresolv-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale-2.16.so is owned by glibc 2.16.0-1
/lib/libmemusage.so is owned by glibc 2.16.0-1
/lib/libdl.so.2 is owned by glibc 2.16.0-1
/lib/libutil-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libthread_db.so.1 is owned by glibc 2.16.0-1
/lib/libnss_files-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_dns-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_db.so.2 is owned by glibc 2.16.0-1
/lib/libnsl-2.16.so is owned by glibc 2.16.0-1
/lib/libc-2.16.so is owned by glibc 2.16.0-1
/lib/libcrypt-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/ld-2.16.so is owned by glibc 2.16.0-1
error: cannot determine ownership of directory '/lib/modules'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/bcma'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bcma/bcma.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btmrvl.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btusb.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/ath3k.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btwilink.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bcm203x.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btuart_cs.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/dtl1_cs.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btsdio.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/btmrvl_sdio.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/hci_vhci.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bt3c_cs.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bpa10x.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bfusb.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/bluecard_cs.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/bluetooth/hci_uart.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/misc'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/misc/eeprom'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/broadcom'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/broadcom/b44.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atlx'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atlx/atl2.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atlx/atl1.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atl1c'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atl1c/atl1c.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atl1e'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/drivers/net/ethernet/atheros/atl1e/atl1e.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth'
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/hidp'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/hidp/hidp.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/rfcomm'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/rfcomm/rfcomm.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/bnep'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/bnep/bnep.ko
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/bluetooth.ko
error: cannot determine ownership of directory '/lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/cmtp'
error: No package owns /lib/modules/3.3.4-2-ARCH/updates/net/bluetooth/cmtp/cmtp.ko
/lib/libm-2.16.so is owned by glibc 2.16.0-1
/lib/libanl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_db-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn-2.16.so is owned by glibc 2.16.0-1
/lib/libdl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
/lib/libnss_hesiod.so.2 is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
error: cannot determine ownership of directory '/lib/udev'
error: cannot determine ownership of directory '/lib/udev/rules.d'
error: No package owns /lib/udev/rules.d/50-compat_firmware.rules
error: No package owns /lib/udev/compat_firmware.sh
/lib/libnss_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libutil.so.1 is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/libnss_nis-2.16.so is owned by glibc 2.16.0-1
/lib/librt-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn.so.1 is owned by glibc 2.16.0-1
If a file is not owned by any package, as is the case for all files in this list (except for the ones owned by glibc), can I then just remove it? I might make a backup of those files just to be sure, but it doesn't make sense to just copy this stuff to /usr/lib.
Last edited by Ailurus (2012-07-14 15:57:28)

Not able to increase SAP kernel release 6.40 patch level from 43 to 71

Hi Guru's,
I have to update SAP kernel release 6.40 patch level from 43 to 71 but not able to do.I am running solution manager 3.2 on Oracle 9i and Win-2003 OS.
Please provide the solutions .
I have downloaded kernel patch from Path at Service matket place ---Support Packages and Patches" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 3.2" Entry by Component" SAP Solution Manager-SAP KERNEL 6.40 32-BIT UNICODE-Windows Server on IA32 32bit-ORACLE-
SAR SAPEXEDB_71-20000254.SAR Kernel Part II (for Basis 640/620) 71
I followed following Steps:
1. Copied the patch into a temporary directory on system.
2. Unpacked the downloded SAPEXEDB_71-20000254.SAR Kernel Part II (for Basis 640/620) 71 patch .
3. Stoped the SAP System using MMC.
4. Saved the kernel directory by backup or by copying into a separate backup directory. (\usr\sap\<SAPSID>\sys\exe\run)
5. Re-started the server.
After logging again in SAP client 000 on checking found server patch level coming same as previous one .
Its not got updated and due to this in Tcode- SPAM I am getting error message :'The OCS package SAPKITL318 requires a kernel with Release 640 and patch number 71. The kernel you are currently using has a lower version.'.
Help!!!!
Regards
Gaurav

Hi Guru's,
Output for transaction SM51 enclosed below:
Application server gauravpc1_GSM_00
SAP R/3 Kernel information
SAP R/3 Kernel 640_REL
Database Client Library OCI_920_SHARE
created in NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
created on Nov 4 2004 23:42:53
Support Level 0
Kernel Patch number 43
Source ID 0.043
DBSL Patch No. 172
ICU Version 2.6.1 Unicode Version 4.0
libsapu16 Version 2.0023 Nov 4 2004 20:04:27
Supported environment
SAP database version
610 , 620 , 630, 640
Database ORACLE 9.2.0..
ORACLE 10.1.0..
ORACLE 10.2.0..
Operating system
Windows NT 5.0, Windows NT 5.1,Windows NT 5.2
one more thing I have aloso tried to upload Kernel latest patch level 175 using same procedure but that too was not working.
HELP!!!!!!!!!!!!!
Regards

Release Cycle of iTunes

Hello, I have recently updated my iTunes to iTunes v12.0.1
I noticed that from time to time an updated version of iTunes is available. I wonder whether there is a defined relese cycle of iTunes.
Is there a defined release cycle for iTunes releases?
Are there any release notes available to look up the changes an update introduces or see the issues that are fixed?
Are there different versions for iOS, Windows, other operating systems?
Thank you in advance for helping.

As far as I am aware Apple don't have a pre-defined cycle, but updates to iTunes can coincide with security patches, bug fixes, iOS updates and new devices.
The page Apple security updates has links to any security related release notes. This page has more blurb about the current release: http://support.apple.com/kb/dl1614. There are usually notes on the changes in Apple Software Update when that is used to upgrade, but I don't think Apple maintain a page where you can review past update notes. Wikipedia's iTunes Version History is an alternate resource for what has changed.
iTunes runs on Windows and Macintosh OS X. In iOS the functions of iTunes are split between a number of apps, App Store, iTunes Store, Music, Videos, iBooks, and Podcasts. iOS and the standalone apps with have their own update cycles but an update to one item may trigger updates elsewhere since there are interdependences.
tt2

Kernel Release 700 Patch Number 83

Hi,
I need help!!!
We load the kernel last night and the Instance won't start then re-applied the old kernel we have the same result. DO you guy have any ideas SAP ask me to IPL the system and don't have any luck.
We are on Kernel Release 700 patch number 80 for 2 weeks after the upgrade.
I received this message on the STARTSAP job and looking for the upgrade directory.
Message . . . . : collectSystemInfo: could not open
profile directory "/usr/sap/putr3/DEV/SYS/profile".
Ramon Mora

Hi Ramon,
as discussed with you, this problem occured because of your RMVSAP before. Therefore the IGS was deleted.
As you didn't implement note 937000 before, it was still deleted after APYSAP and therefore SAP was "unhappy" and stopped immediately after trying to start :-((
As the IGS in R3 systems is very RARELY used, a common workaround is to patch the start-profile that way, that IGS is no longer started.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Arch Kernel Release Cycle

Similar Messages

Maybe you are looking for