I am trying to upgrade the kernel through yum to the one from ASL channel and I get this error after i run yum install kernel
Error: lksctp-tools conflicts with kernel >= 2.6.10
Any help or pointers would be greatly appreciated. I need to upgrade the kernel as my server is crawling with the iowait issue.
Here is the full screen from yum
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package kernel.i686 1:2.6.14-4.art set to be installed
--> Running transaction check
--> Processing Dependency: gradm for package: kernel
--> Processing Conflict: lksctp-tools conflicts kernel >= 2.6.10
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for gradm to pack into transaction set.
gradm-2.1.8-5.rhel4.art.i 100% |=========================| 11 kB 00:00
---> Package gradm.i386 0:2.1.8-5.rhel4.art set to be updated
--> Running transaction check
--> Processing Conflict: lksctp-tools conflicts kernel >= 2.6.10
--> Finished Dependency Resolution
Error: lksctp-tools conflicts with kernel >= 2.6.10
Thanks in advance.
Error: lksctp-tools conflicts with kernel >= 2.6.10
Please ignore my last post. I simply uninstalled lksctp-tools and it seems to do the trick.
The only thing I got after the install is these warnings:
WARNING: /lib/modules/2.6.14-4.art/kernel/drivers/pci/hotplug/pciehp.ko needs unknown symbol pcibios_set_irq_routing
WARNING: /lib/modules/2.6.14-4.art/kernel/drivers/pci/hotplug/shpchp.ko needs unknown symbol pcibios_set_irq_routing
Not sure if they are serious.
The only thing I got after the install is these warnings:
WARNING: /lib/modules/2.6.14-4.art/kernel/drivers/pci/hotplug/pciehp.ko needs unknown symbol pcibios_set_irq_routing
WARNING: /lib/modules/2.6.14-4.art/kernel/drivers/pci/hotplug/shpchp.ko needs unknown symbol pcibios_set_irq_routing
Not sure if they are serious.
-
- Atomicorp Staff - Site Admin
- Posts: 8355
- Joined: Wed Dec 31, 1969 8:00 pm
- Location: earth
- Contact:
What distro are you on? I might be able to resolve that kind of conflict message(its harmless) in the next release.
Those warnings are of an informational nature, I dont know why the report to stdout like that. What it means is that those kernel modules are looking for features in a hotplug IDE controller that doesnt exist on your system. Its a harmless, if annoying message.
Those warnings are of an informational nature, I dont know why the report to stdout like that. What it means is that those kernel modules are looking for features in a hotplug IDE controller that doesnt exist on your system. Its a harmless, if annoying message.
Its a Centos 4.3. Installed your kernel package and it solved the iowait issue we were having and the server is running great. Not very familiar with the security settings compiled into this kernel, but I am not able to load some modules, and Zend modules give this error.
Failed loading /usr/local/Zend/lib/ZendExtensionManager.so: /usr/local/Zend/lib/ZendExtensionManager.so: cannot enable executable stack as shared object requires: Permission denied
Also Drweb stoped working due to this. Any pointers?
Failed loading /usr/local/Zend/lib/ZendExtensionManager.so: /usr/local/Zend/lib/ZendExtensionManager.so: cannot enable executable stack as shared object requires: Permission denied
Also Drweb stoped working due to this. Any pointers?
-
- Atomicorp Staff - Site Admin
- Posts: 8355
- Joined: Wed Dec 31, 1969 8:00 pm
- Location: earth
- Contact:
Yeah, Ive been getting a lot of people using the kernel just because of the IO fixes.
Your installation of Zend, thats not from an RPM is it? Internally its pretty difficult for me to detect non-rpm packages, so I do what I can with some scripts. That being said, I always miss something.
In reference to dr.web, I recommend trying the kernel/gradm from the asl-testing channel, if you havent already. They have a number of extra checks that should clean up some of its drweb's internals.
Your installation of Zend, thats not from an RPM is it? Internally its pretty difficult for me to detect non-rpm packages, so I do what I can with some scripts. That being said, I always miss something.
In reference to dr.web, I recommend trying the kernel/gradm from the asl-testing channel, if you havent already. They have a number of extra checks that should clean up some of its drweb's internals.
Same here, Dr. Web error during the yum update on the gradm scriptlet execution with a message about text file being locked. Does anyone know the best fix or workaround? I'd prefer to use the main channel if a solution exists, since this will be a production box. Any advice is appreciated. New to ASL, but I'm a quick learner... usually 
Running CentOS 4.3
Thanks in advance.

Running CentOS 4.3
Thanks in advance.