KMS on new kernel

Hello
I am currently using the 2.6.30 kernel with the Intel 2.7.1 driver and no KMS. I think I will make the switch to the newest Intel driver and KMS, but first I would like to know if I have to do anything at all to have KMS after upgrading to .31 kernel and 2.8.1 Intel, or the upgrade will bring it to me effortlessly
TIA

Yes, you will have to read our wiki

Similar Messages

How do I use a newer kernel in the netinstall USB image

Hi,
trying to install Arch onto my laptop. My laptop is a Acer 1410 and it seems to have a new wireless card. dmesg | grep firmware shows something like iwlwifi-1000-2.ucode firmware file req failed: -2
The problem is I can only find iwlwifi-1000-3.ucode on intel's website. So I assume a newer kernel will help. Replacing the kernel on the live USB with vmlinuz-2.6.31-17-generic copied from by ubuntu install makes it not able to boot.
Thanks

The error message means that the firmware is not installed. Did you actually try the 1000-3.ucode before assuming you need a new kernel?
Also, there are various places where you could get an older firmware package, if you really need the 1000-2 version. Have a look at the wiki's Downgrade page for details.

Failed to install the new kernel pkg

I just downloaded a new kernel pkg from
archlive-pkg
this is the new kernel pkg I downloaded.
kernel26-snapshot-2.6.31-rc6-git6-i686.pkg.tar.gz
when I ran
pacman -U kernel26-snapshot-2.6.31-rc6-git6-i686.pkg.tar.gz
, it complaint there is a conflict issue~
How can i install the package? thanks!
loading package data...
checking dependencies...
(1/1) checking for file conflicts [#####################] 100%
error: failed to prepare transaction (conflicting files)
kernel26-snapshot-2.6.31: /boot/System.map26 exists in filesystem
kernel26-snapshot-2.6.31: /boot/vmlinuz26 exists in filesystem
kernel26-snapshot-2.6.31: /etc/mkinitcpio.d/kernel26.kver exists in filesystem
kernel26-snapshot-2.6.31: /etc/mkinitcpio.d/kernel26.preset exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/3com/typhoon.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/acenic/tg1.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/acenic/tg2.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/adaptec/starfire_rx.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/adaptec/starfire_tx.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/advansys/3550.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/advansys/38C0800.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/advansys/38C1600.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/advansys/mcode.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/atmsar11.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/bnx2/bnx2-mips-09-4.6.17.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/bnx2/bnx2-rv2p-06-4.6.16.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/bnx2/bnx2-rv2p-09-4.6.15.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/cis/LA-PCM.cis exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/cxgb3/t3b_psram-1.1.0.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/cxgb3/t3c_psram-1.1.0.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/e100/d101m_ucode.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/e100/d101s_ucode.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/e100/d102e_ucode.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/edgeport/boot.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/edgeport/boot2.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/edgeport/down.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/edgeport/down2.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/edgeport/down3.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/emi26/bitstream.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/emi26/firmware.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/emi26/loader.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/emi62/bitstream.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/emi62/loader.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/emi62/midi.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/emi62/spdif.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/ess/maestro3_assp_kernel.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/ess/maestro3_assp_minisrc.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/kaweth/new_code.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/kaweth/new_code_fix.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/kaweth/trigger_code.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/kaweth/trigger_code_fix.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/keyspan_pda/keyspan_pda.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/keyspan_pda/xircom_pgs.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/korg/k1212.dsp exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/mts_cdma.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/mts_edge.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/mts_gsm.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/ositech/Xilinx7OD.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/qlogic/1040.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/qlogic/12160.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/qlogic/1280.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/sun/cassini.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/tehuti/bdx.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/ti_3410.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/ti_5052.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/tigon/tg3.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/tigon/tg3_tso.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/tigon/tg3_tso5.bin exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/whiteheat.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/whiteheat_loader.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/yamaha/ds1_ctrl.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/yamaha/ds1_dsp.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/yamaha/ds1e_ctrl.fw exists in filesystem
kernel26-snapshot-2.6.31: /lib/firmware/yamaha/yss225_registers.bin exists in filesystem
errors occurred, no packages were upgraded.

yunkwan wrote:
bangkok_manouel wrote:another option:
pacman -Rd kernel26-firmware && pacman -U kernel26-snapshot-2.6.31-rc6-git6-i686.pkg.tar.gz
after I run
pacman -Rd kernel26-firmware mkinitcpio
loading package data...
checking dependencies...
(1/1) checking for file conflicts [#####################]
100%
error: failed to prepare transaction (conflicting files)
kernel26-snapshot-2.6.31: /boot/System.map26 exists in filesystem
kernel26-snapshot-2.6.31: /boot/vmlinuz26 exists in filesystem
which pkg else should I remove?
your kernel. i'd recommend you to do that first:
cp /boot/System.map26 /boot/System.map26.old
cp /boot/vmlinuz26 /boot/vmlinuz26.old
in case of problem with your newly installed kernel, edit the grub entry at boot according to the new back-up names above.
then simply:
pacman -Uf kernel26-snapshot-2.6.31-rc6-git6-i686.pkg.tar.gz
also, why has mkinitcpio been removed? reinstall it before installing your new kernel.

Can't get Nvidia to work in new kernel

Hi,
Yes, I know, loads of people have problems getting this to work and it has been posted thousands of times...but yet I can't do it! I've been trying for days, googling, reading the wikis and forums, but it won't work for me at all! I guess I'm doing something really evidently wrong, but what?
I've compiled a low latency kernel to allow me to run some midi applications that my wife absolutely must have (and she won't accept my move to Arch until I get them to work ) Now, this part is OK - I've succeeded here no probs. But no amount of work will get that Nvidia card up and running. I've tried this using abs in the following way: I've copied /var/abs/extra/nvidia-96xx to /var/abs/local/nvidia-96xx/ In nvidia.install I've changed KERNEL_VERSION from 2.6.25-ARCH to 2.6.21-rt; I've done the same thing in PKGBUILD; and I've changed pkgname in PKGBUILD to nvidia-custom. Then I've run makepkg -i -c...nothing. It seemed to build the first time I tried, however on booting into the new kernel I got greeted by a blank screen (and pacman won't let me re-install the NVIDIA driver, either) However, the second time it refused (I think it was a permissions problem). So I tried the same manipulation, this time copying /var/abs/extra/nvidia-96xx to my home directory. Still nothing. What am I doing wrong? Sorry for being such an Arch noob!
Thanks in advance!

OK, here is the exact error message when I try to do this manually:
The CC version check failed.
The compiler used to compile the kernel (gcc 4.2) does not exactly match the current compiler (gcc 4.3). The Linux 2.6 kernel module rejects kernel modules built with a version of gcc that does not exaclt match that of the compiler used to build the running kernel.
If you know what you are doing and want to ignore the gcc version to check, select "No" to continue installation. Otherwise, select "yes" to abort installation, set the CC environment to the name of the compiler used to compile your kernel, and restart installation. Abort now?
Does the fact that I find nvidia.ko where it should be mean that this is the problem when I try to install Nvidia with abs? How do I set the CC environment like it says? I don't really understand this message.
Last edited by Flapjack (2008-06-21 05:49:29)

NEW KERNEL V47, and a new hope for 720p video play...

thats right people, after matan's strange disappearing, we now have pali getting us new kernels, and his first kernel with loads of new awesome patches is in the extras devels ( v47 ) , you can try it out, same installation method as the old v46 (or v42 from the extras ), and same overclocking method too .
and now he is working on a 720p video playback patch, he already got the 720p media codecs (finally) and many users reported that they are able to play 720p mpeg4 videos on the n900 (this patch isn't in the extras devel version....yet ! ) so now we don't have a hardware problem to play 720p videos, the problem is in gstreamer (video player in the default media player) but thank god, we have MohamadAG to work on that openmedia player so we can finally get 720p video playback .
and if we can play 720p videos, we can shoot them too .
and i can say that after 40 minutes of hard usage of this new kernel my phone seems a lot smoother and abit faster than the old v46 or v42 with the same overclocking settings .
Use Hildon Application Manager or via apt-get
Step 1 Installation:
In Hildon Application Manager install package: Linux Kernel for power user
Or via apt-get package: kernel-power-flasher
Step 2 Multiboot support:
First see step 1.
Then in Hildon Application Manager install package: Linux Kernel for power user (boot image)
Or via apt-get package: kernel-power-bootimg
this is not for noobs right now, but it will be soon, and it might become a part of the cssu .
and btw if you get a 400 degrees temprature in conky don't panic, its a false value, its 40
ORIGINAL THREAD BY PALI AT talk.maemo.org .
Reality is wrong....dreams are for real... 2pac .
don't forget to hit that green kudos

ceroberts75 wrote:
i am boping we get another community udate soon. the last one brought us a great camera update, but the email is still messed up.
it will be coming...... its just tat Mag is busy with the new facebook app...... and so far i know that it includes multiple proflies support... and the camera ui has been updated 2-3 times since the last cssu update .
and for 720 p playback we are porbably going to use open medi pllayer, for anyone that wants to use it, search this forum for "open media player" , its a faster version of the original one, with more effects and smoothness .
Reality is wrong....dreams are for real... 2pac .
don't forget to hit that green kudos

[Solved] Kernel 3.2 wont re-patch vmware for new kernel build

Hi, I looked for the same thing and didnt find it, I had vmplayer running great -> enter new kernel 3.2. When it went to build the new modules because the kernel changed it failed with log of:
2012-01-19T06:10:49.389-06:00| vthread-3| I120: Log for VMware Workstation pid=3928 version=8.0.1 build=build-528992 option=Release
2012-01-19T06:10:49.389-06:00| vthread-3| I120: The process is 64-bit.
2012-01-19T06:10:49.389-06:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2012-01-19T06:10:49.388-06:00| vthread-3| I120: Msg_Reset:
2012-01-19T06:10:49.388-06:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2012-01-19T06:10:49.388-06:00| vthread-3| I120: ----------------------------------------
2012-01-19T06:10:49.388-06:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2012-01-19T06:10:49.389-06:00| vthread-3| I120: Msg_Reset:
2012-01-19T06:10:49.389-06:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2012-01-19T06:10:49.389-06:00| vthread-3| I120: ----------------------------------------
2012-01-19T06:10:49.389-06:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/redhat-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/redhat_version: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/sun-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/SuSE-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/novell-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/sles-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/debian_version: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/debian_release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/mandrake-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/mandriva-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/mandrakelinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/turbolinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/fedora-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/gentoo-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/nld-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/lsb-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/annvix-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: Cannot work with empty file.
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/arklinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/aurox-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/blackcat-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/cobalt-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/conectiva-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/immunix-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/knoppix_version: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/lfs-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/linuxppc-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/mklinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/pld-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/slackware-version: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/slackware-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/e-smith-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/tinysofa-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/ultrapenguin-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/UnitedLinux-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/va-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoReadDistroFile: could not open file/etc/yellowdog-release: 2
2012-01-19T06:10:49.395-06:00| vthread-3| W110: HostinfoOSData: Error: no distro file found
2012-01-19T06:10:49.396-06:00| vthread-3| W110: Logging to /tmp/vmware-root/modconfig-3928.log
2012-01-19T06:10:49.497-06:00| vthread-3| I120: modconf query interface initialized
2012-01-19T06:10:49.498-06:00| vthread-3| I120: modconf library initialized
2012-01-19T06:10:49.544-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.548-06:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.548-06:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-01-19T06:10:49.548-06:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-01-19T06:10:49.548-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.550-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.563-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.592-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:49.592-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.594-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.608-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.636-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:49.672-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.674-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.676-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.679-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.681-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.715-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.717-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.719-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.721-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.724-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.726-06:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.726-06:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-01-19T06:10:49.726-06:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-01-19T06:10:49.726-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.728-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.741-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.769-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:49.804-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.806-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.809-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.811-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.813-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.815-06:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.815-06:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-01-19T06:10:49.815-06:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-01-19T06:10:49.815-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:49.817-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.830-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:49.858-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:49.926-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.928-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.930-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.933-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:49.935-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:50.059-06:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.1-1-ARCH.
2012-01-19T06:10:50.059-06:00| vthread-3| I120: Validating path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH
2012-01-19T06:10:50.061-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:50.076-06:00| vthread-3| I120: Your GCC version: 4.6
2012-01-19T06:10:50.105-06:00| vthread-3| I120: Header path /lib/modules/3.2.1-1-ARCH/build/include for kernel release 3.2.1-1-ARCH is valid.
2012-01-19T06:10:50.105-06:00| vthread-3| I120: Building module vmmon.
2012-01-19T06:10:50.105-06:00| vthread-3| I120: Extracting the sources of the vmmon module.
2012-01-19T06:10:50.116-06:00| vthread-3| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.1-1-ARCH/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6.2
2012-01-19T06:10:51.838-06:00| vthread-3| I120: Failed to compile module vmmon!
So I thought ok maybe it needs the 3.2 patch, so I un-installed then reinstalled but it wouldn't let me run the patch saying that my sources are alreay patched, I need this machine to do my work and I now at a dead stop.
thanks for your help on this.
--jerry
Last edited by jk121960 (2012-01-19 23:16:22)

OK it all worked accept for one small bit, with the new patch there is a bug in the script. It calls for
/sbin/lsmod which doesn't exist.
It exists in /bin/lsmod
So I guess you could mod the script but I just symlinked the path and it worked fine.
ln -s /bin/lsmod /sbin/lsmod
thanks again for your help and I hope this little bit gets found by who needs it.
--jerry

New kernel prevents computer from booting

i installed kernel26-scsi 2.6.13.4-1 by means of pacman about a week ago, ran lilo, rebooted to find that before lilo loaded the screen had a bunch of "99"s printing across the screen. Once they stopped printing the processor hung. Every time i restart this happens. I booted to knoppix and installed the same kernel again but it still wouldn't boot. so I booted to knoppix again copied the contents of my scsi that i was trying to boot from to my ide and wiped my scsi. I put in the arch 0.7 cd and did an ftp install on the scsi drive. I installed kernel24-scsi since i had trouble with doing a fresh install with udev, lilo, and the kernel26-scsi, hoping that when i got it running i would be able to put kernel 2.6 on it. it still boots to a bunch of "99"s printed accross the screen and stalls the cpu. Is this some kind of hardware issue with the new kernel or can anyone help me solve this problem?

rocknice wrote: gosh Moo-Crumpus.
What do you blame me for? I payed deference to phrakture for not giving up. Unlike him, I am tired of asking again and again if one has read this or that. He is constantly helpful, isn't he, while I tend to be snubbed.
As you have not told us you where prepared for udev/devfs - and 80% of help calls here and in irc have been udev related - phrakture had to guess - he did a quick shot and missed. So what?
Let's see if we can help you.
Unfortunately, I don't use or kn ow lilo very well. As far as I know, lilo has some strange issues if beeing used in a dual boot to windows or linux scenario, and some other strange behaviours. Furthermore, 99 99 99 99 99 99 99 99 etc seemes to be a lilo message that should tell you lilo can't get further then stage one. This can be a damaged mbr, for example, or if windows has repaired the mbr and destroyed lilo, or a physically damaged hard disk. Have you rerun "lilo" or "liloconf"? They will reinstall LILO to the drive and make the second stage loader look in the right spot...which apparently it is not, hence the L 99 99 99 99 ...
As you tried a reinstall using ftp, I think you could try cd based install, to be sure. I would recommend to use grub instead of lilo.

What's the deal with Intel and the new kernel?

Hi
I have trouble understanding the whole deal behind Intel's video drivers and the new kernel. What doesn't work and why? Could someone please try to explain what the problem is in a way so that a newbie like me can understand it?
Thanks

Intel and Linux are transitioning to a new graphics system. We're in the middle of the transition, so everything's kinda suckish right now. Old kernel and drivers are better, development kernel and drivers are almost as good, and they will get much better soon.
www.phoronix.com for up-to-date info.

ATI display driver fails to work with new kernel

Hi,
I've just upgraded from
OEL kernel-2.6.18-194.11.3.0.1.el5.x86_64
to most current
OEL kernel-2.6.18-194.11.4.0.1.el5.x86_64
and got the problem with ATI display driver. Whenever I perform kernel upgrade, I have to recompile vendor-provided ATI display driver downloadable from AMD/ATI site, because system ATI driver, provided by OEL/RHEL as kernel module, doesn't work properly (too slow). I did that hundred times and never had a problem. This time the problem is that after upgrading to new kernel and recompiling the existing ATI display driver (Revision 10.8), it doesn't work anymore, even though it worked perfectly with previous kernel. I cannot even start X11 (glibc problem reported with stack traces!!!). The newest ATI display driver (Revision 10.9) "works" with new kernel, but display is awfully slow making any serious work impossible. It is even slower than system-provided ATI driver.
I am pretty sure the problem is in new kernel. As I have no backup of old kernel files and couldn't download the previous OEL kernel files from ULN, neither binary nor source (the files do not exist on ULN anymore, only the recent kernel files), I downloaded the previous kernel source from ftp.redhat.com, compiled the kernel and downgraded to it, recompiled ATI display driver, and everything works properly and fast as before upgrading. I can remember that ULN site used to have all kernel versions prior to actual one and cannot understand why Oracle dropped this practice. As I have an ULN account, I certainly want to have OEL patched kernel.
My question is: does anybody know how and where I can download the previous OEL kernel-2.6.18-194.11.3.0.1.el5.x86_64 binary rpm files or at least source rpm file?
Maybe Sergio or Tommy can help?
Thanks in advance.
NJ

I have experienced the same with Ubuntu some years ago - specific feature (hack?) that was implemented in the kernel was deprecated. This was used by the display driver for an onboard Intel graphics chipset. Beryl (which was subsequently merged with Compiz) turned into a horribly slow experience. As far as I recall, a subsequent kernel patch "fixed" things as a number of users were affected, of which many complained very loudly.
Anyway, I think the lesson here is that OEL is not really the correct distro to use for a desktop. A broken ATI driver for the OEL kernel? Does not really feature in the scheme of things for OEL support. Oracle Grid/RAC/Enterprise/Standard Edition do not care. Oracle's application servers (Apache, Weblogic, etc) do not care. Etc.
Sure, GUI desktop access to an OEL server is needed (like when running dbca or an installer) - but that can easily and effectively be done using vncserver for example and running twm.
You may be able to fix/work-around the problem with the current kernel update.. you may be able to roll back the update. But what about the next time when some other component does not work after a patch or an update? Surely it is a lot less stressful and frustrating to rather use a desktop distro, like Ubuntu, instead?

[SOLVED - Doh!] New kernel doesn't show up in grub menu

I've decided to play around with a new kernel, so I followed the instructions in the wiki for building the linux-pf kernel (ie, used the AUR). Although it doesn't include this step, I also ran grub-mkconfig. I can see a new Linux kernel in my /boot/grub/grub.cfg file.
However, it doesn't show up in the Grub menu when I reboot. I don't see any other step in the wiki, for either linux kernels or grub. What am I missing?
Last edited by jdarnold (2013-09-18 23:55:16)

@op - If you see it in /boot/grub/grub.cfg and that is the file grub is reading, you will see it when grub goes live. Do you have a separate /boot partition and did you have it mounted when you updated the config? I'm guess you didn't and your config went on the root file system under /boot rather than to a mounted filesystem mount in /boot.

Load new kernel

I am running arch on Thinkpad x230t and I found this guide with recommendations for running arch on this particular laptop:
https://wiki.archlinux.org/index.php/Le … nkPad_X230
I am trying to install the linux-ck kernel and am having some trouble. I downloaded the tarball and ran the PKGBUILD and ran for a while and finished without doinging anything alarming.
I made the recomended changes to:
/etc/mkinitcpio.conf
/etc/modprobe.d/modprobe.conf
And then tried to run:
mkinitcpio -p linux && mkinitcpio -p linux-ck
It created the first linux image without any problems but failed on the linux-ck, here is the full post:
mkinitcpio -p linux && mkinitcpio -p linux-ck
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.10.9-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.10.9-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
[john@X230T-John ld.so.conf.d]$ sudo mkinitcpio -p linux-ck
==> Building image from preset: /etc/mkinitcpio.d/linux-ck.preset: 'default'
-> -k /boot/vmlinuz-linux-ck -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-ck.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux-ck'
==> Building image from preset: /etc/mkinitcpio.d/linux-ck.preset: 'fallback'
-> -k /boot/vmlinuz-linux-ck -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-ck-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux-ck'
(Also, what do the 3 warning lines, on the linux image mean?)
What's going on here? Thanks for any help.
Last edited by lampwins (2013-08-27 18:36:13)

What is the output of
# pacman -Qm
From the error that you posted, it clearly states that it can't find the specified linux-ck kernel, which if you installed should be hanging out inside of your /boot directory.
You might as well post the output of
ls /boot/
As for installing/compiling the linux-ck kernel, the Linux-ck ArchWiki, gives you a general idea, however its the same as installing any custom package (for me at least). Below are the steps that I personally do, keep in mind that there might be other/easier ways.
1. Download the latest linux-ck tarball from the AUR, and if you are using an nvidia card you can also grab the proper nvidia-ck package.
2. Extract the tarball, and cd into the newly created folder
3. edit the PKGBUILD, the only things I change in this file, are the variables in the code below that are set equal to y (enabling the option)
### PATCH AND BUILD OPTIONS
# Set these variables to ANYTHING that is not null (y or hello or 2 or "I like icecream") to enable them
_pstates_pat=y # Enable Haswell support for the new Intel pstate drive
_makenconfig= # Tweak kernel options prior to a build via nconfig
_localmodcfg=y # Compile ONLY probed modules
_use_current= # Use the current kernel's .config file
_BFQ_enable_=y # Enable BFQ as the default I/O scheduler
_NUMAdisable=y # Disable NUMA in kernel config
I personally have just started messing around with the kernel configuration so I'm using localmodconfig as a starting point. You can however load your own config, or start one from scratch.
4.Save & quit the file, then I personally run the command below, which compiles the package and if successful it installs it. Keep in mind I'm pretty sure you have to have 'Sudo' set up on the system.
makepkg -ci
If you don't have 'Sudo' or whatever, you can still just run
$ makepkg
# pacman -U pkgname-pkgver.pkg.tar.xz
5. If all is well, I update my grub2
# grub-mkconfig -o /boot/grub/grub.cfg
At this point, you should be able to boot into your new kernel. Hopefully you use nvidia, and will notice that you have no X working. You can follow the same outline to compile and install the proper nvidia-ck driver package.
Hope this helps.
Last edited by luisgmarine (2013-08-29 21:34:37)

Arch-0.7.2-ftp.iso can't handle the new kernel [SOLVED]

hallo arch mates is there any problem when installer a fresh install from ftp with the new kernel some of my friends need to edit grup after install is it a error or is the arch-0.7.2-ftp.iso not build to handle the new kernel ??
Over And Out :?:

Mh? I don't see a problem using 0.7.2 ftp install cd. Also not when editing grub file.
But if you get problems you might try this one http://bbs.archlinux.org/viewtopic.php?t=25236
cheers,
deTTo

[Solved] New Kernel Update, 3.15.2-1 not booting

After an update to the kernel, which is 3.15.2-1, I'm now not able to boot. It hangs on Realtime IRQ line which I believe is from the rtirq script in AUR. After disabling the rtirq via `systemctl disable rtirq` it now hangs at a `Has reached Graphics`.
Anyone else having issues booting with the new kernel?
Last edited by dsreyes1014 (2014-06-29 02:32:22)

You will need to provide more information. Your machine is booting, but X is not starting or your login manager isn't working.
Provide details about your setup; DM, DE etc, what else was included in that upgrade, etc...
Not a Kernel issue, moving to NC...

What is the best way to upgrade to a new kernel?

I would like to upgrade to the new kernel: kernel26-2.6.23.14-1 from the one from core (on the CD).
What is the best way to do this? Also, is there a way to find out what is new / has changed in the new kernel?
Thanks for any insights.

Gilneas wrote:
Surely you have tried pacman -Syu?
Kernel changelogs are on kernel.org. Perhaps it's more interesting to read articles on kerneltrap.org though.
I have had a kernel panic one time I upgraded a kernel. I had to walk back step-by-step to backtrack what I did.
I basically uninstalled the nv kernel driver for xorg and installed the proprietary drivers from their website (which I shouldn't have uninstalled nv drivers, but nonetheless I learned from it). But, somehow I think one of the packages I installed automatically upgraded to the lastest kernel. When I reverted to the properietary drivers it somehow uninstalled the latest kernel. The key thing I learned was "install the right drivers the first time!" But, yes, I know about "Pacman -Syu" in general, but didn't know that was the appropriate way to do it. It's just my two cents.
Last edited by smitty (2008-02-05 12:28:48)

OEL 6.2 new kernel new problems

Hi dears,
I was very happy about new updates and of course I installed these new update hoping that some
problems related to incompatibility in my system will be solved, but after I reboot my machine
I saw this
http://picfront.de/d/8s0p
How can I fix this or although rollback to old kernel ?
Please help.
old kernel = 2.6.32.100
new kernel = 2.6.32.300
OS OEL 6 (PVM) in Oracle VM 3.0.2
./thanks in advance

Avi Miller wrote:
__OUTSIDER___ wrote:
How can I fix this or although rollback to old kernel ?The old kernel is still installed -- the upgrade just installs a new one as well. What's happened is that your root device line seems to have changed, though I'm unsure why. There appears to be a /dev/ missing from the root= parameter on the command-line.
Log into the Dom0 of your Oracle VM Server and start the guest manually and connect to the console using:
# xm create -c /OVS/Repositories/<UUID>/VirtualMachines/<UUID>/vm.cfg You'll need to work out what the two <UUID> values are, though. The first one is the UUID of the repository that contains your Virtual Machine configuration file. The second is the UUID of the Virtual Machine itself. You can find the repository path by running df -h to see all the mounted repositories on your server. The VirtualMachine UUID is on the Info screen of the Virtual Machine under the "ID" field.
When you start the guest using the xm command, you'll be presented with the GRUB boot loader screen, which will allow you to chose the previous kernel. When the machine boots, check /boot/grub/grub.conf and ensure that the root= parameter is the same as the previous kernel lines.Thanks Avi for speed of light support (I'm surprised :) )
Everything as you say I was able to run my old kernel and ssh to machine but root= parameter is fine (I think).
Can you check please if I am wrong
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Oracle Linux Server (2.6.32-300.3.1.el6uek.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-300.3.1.el6uek.x86_64 ro root=/dev/mapper/vg_rac1-lv_root rd_LVM_LV=vg_rac1/lv_root rd_LVM_LV=vg_rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
title Oracle Linux Server (2.6.32-220.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-220.el6.x86_64 ro root=/dev/mapper/vg_rac1-lv_root rd_LVM_LV=vg_rac1/lv_root rd_LVM_LV=vg_rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
title Oracle Linux Server-uek (2.6.32-100.34.1.el6uek.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-100.34.1.el6uek.x86_64 ro root=/dev/mapper/vg_rac1-lv_root rd_LVM_LV=vg_rac1/lv_root rd_LVM_LV=vg_rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
initrd /initramfs-2.6.32-100.34.1.el6uek.x86_64.img
title Oracle Linux Server (2.6.32-131.0.15.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-131.0.15.el6.x86_64 ro root=/dev/mapper/vg_rac1-lv_root rd_LVM_LV=vg_rac1/lv_root rd_LVM_LV=vg_rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto rhgb quiet
initrd /initramfs-2.6.32-131.0.15.el6.x86_64.img

KMS on new kernel

Similar Messages

Maybe you are looking for