When I try to update from FC5 to FC6 I get this:
Error: hal conflicts with kernel < 2.6.17
Error: autofs conflicts with kernel < 2.6.17
However, when I do: uname -r I get:
2.6.19-1.2911.fc6
With yum list | grep kernel I get:
kernel.i686 2.6.19-1.2911.fc6 installed
kernel-smp.i686 2.6.15-1.2054_FC5 installed
kernel-smp.i686 2.6.18-1.2239.fc5 installed
kernel.i586 2.6.19-1.2911.fc6 updates
kernel-PAE.i686 2.6.19-1.2911.fc6 updates
kernel-PAE-debug.i686 2.6.19-1.2911.fc6 updates
kernel-PAE-debug-devel.i686 2.6.19-1.2911.fc6 updates
kernel-PAE-devel.i686 2.6.19-1.2911.fc6 updates
kernel-debug.i686 2.6.19-1.2911.fc6 updates
kernel-debug-devel.i686 2.6.19-1.2911.fc6 updates
kernel-devel.i586 2.6.19-1.2911.fc6 updates
kernel-devel.i686 2.6.19-1.2911.fc6 updates
kernel-doc.noarch 2.6.19-1.2911.fc6 updates
kernel-headers.i386 2.6.19-1.2911.fc6 updates
kernel-kdump.i686 2.6.19-1.2911.fc6 updates
kernel-kdump-devel.i686 2.6.19-1.2911.fc6 updates
kernel-xen.i686 2.6.19-1.2911.fc6 updates
kernel-xen-devel.i686 2.6.19-1.2911.fc6 updates
yum-kernel-module.noarch 1.0.3-1.fc6 extras
I am confused, and a newbie.
Best regards,
Peter Lauri
http://www.dwsasia.com/ www.dwsasia.com - company web site
http://www.lauri.se/ www.lauri.se - personal web site
http://www.carbonfree.org.uk/ www.carbonfree.org.uk - become Carbon Free
Try: rpm -qa | grep kernel and see what you get... and then you can: rpm -e <kernel sources you don't need ( older versions, less then 2.6.17)> -Brad
Peter Lauri wrote:
When I try to update from FC5 to FC6 I get this:
Error: hal conflicts with kernel < 2.6.17
Error: autofs conflicts with kernel < 2.6.17
However, when I do: uname –r I get:
2.6.19-1.2911.fc6
With yum list | grep kernel I get:
kernel.i686 2.6.19-1.2911.fc6 installed
kernel-smp.i686 2.6.15-1.2054_FC5 installed
kernel-smp.i686 2.6.18-1.2239.fc5 installed
kernel.i586 2.6.19-1.2911.fc6 updates
kernel-PAE.i686 2.6.19-1.2911.fc6 updates
kernel-PAE-debug.i686 2.6.19-1.2911.fc6 updates
kernel-PAE-debug-devel.i686 2.6.19-1.2911.fc6 updates
kernel-PAE-devel.i686 2.6.19-1.2911.fc6 updates
kernel-debug.i686 2.6.19-1.2911.fc6 updates
kernel-debug-devel.i686 2.6.19-1.2911.fc6 updates
kernel-devel.i586 2.6.19-1.2911.fc6 updates
kernel-devel.i686 2.6.19-1.2911.fc6 updates
kernel-doc.noarch 2.6.19-1.2911.fc6 updates
kernel-headers.i386 2.6.19-1.2911.fc6 updates
kernel-kdump.i686 2.6.19-1.2911.fc6 updates
kernel-kdump-devel.i686 2.6.19-1.2911.fc6 updates
kernel-xen.i686 2.6.19-1.2911.fc6 updates
kernel-xen-devel.i686 2.6.19-1.2911.fc6 updates
yum-kernel-module.noarch 1.0.3-1.fc6 extras
I am confused, and a newbie.
Best regards,
Peter Lauri
www.dwsasia.com http://www.dwsasia.com/ - company web site
www.lauri.se http://www.lauri.se/ - personal web site
www.carbonfree.org.uk http://www.carbonfree.org.uk/ - become Carbon Free
On 2/26/07, Peter Lauri lists@dwsasia.com wrote:
When I try to update from FC5 to FC6 I get this:
Error: hal conflicts with kernel < 2.6.17
Error: autofs conflicts with kernel < 2.6.17
However, when I do: uname –r I get:
2.6.19-1.2911.fc6
With yum list | grep kernel I get:
kernel.i686 2.6.19-1.2911.fc6 installed
kernel-smp.i686 2.6.15-1.2054_FC5 installed
kernel-smp.i686 2.6.18-1.2239.fc5 installed
What kind of system do you have? Do you really need the FC5 kernels after you installed FC6?
Error: hal conflicts with kernel < 2.6.17 Error: autofs conflicts with kernel < 2.6.17
They only work with a kernel of 2.6.17 or higher
However, when I do: uname -r I get: 2.6.19-1.2911.fc6
This is your running kernel not the only kernel you have and the rpm system is smart enough to realise this.
kernel-smp.i686 2.6.15-1.2054_FC5 installed
kernel-smp.i686 2.6.18-1.2239.fc5 installed
So you need to get rid of 2.6.15-1.2054_FC5
Basically the packaging system has realised that if you choose to boot the old kernel 2.6.15-1.2054_FC5 which you have installed and it let you update hal or autofs, then the result would not work.
If you know you have another kernel which does work then you can remove the 2.6.15-1.2054_FC5 kernel.
Yes now it works, it is starting to update. However, new problem:
warning: /etc/passwd created as /etc/passwd.rpmnew warning: /usr/lib/security/classpath.security created as /usr/lib/security/classpath.security.rpmnew warning: /etc/pam.d/system-auth created as /etc/pam.d/system-auth.rpmnew
What does that actually mean? Could I just copy the passwd to passwd.bak and then rename passwd.rpmnew to passwd? And same for the others?
Best regards, Peter Lauri
www.dwsasia.com - company web site www.lauri.se - personal web site www.carbonfree.org.uk - become Carbon Free
-----Original Message----- From: Alan [mailto:alan@lxorguk.ukuu.org.uk] Sent: Tuesday, February 27, 2007 12:05 AM To: For users of Fedora Cc: lists@dwsasia.com Subject: Re: Error, but uname -r give different indications
Error: hal conflicts with kernel < 2.6.17 Error: autofs conflicts with kernel < 2.6.17
They only work with a kernel of 2.6.17 or higher
However, when I do: uname -r I get: 2.6.19-1.2911.fc6
This is your running kernel not the only kernel you have and the rpm system is smart enough to realise this.
kernel-smp.i686 2.6.15-1.2054_FC5 installed
kernel-smp.i686 2.6.18-1.2239.fc5 installed
So you need to get rid of 2.6.15-1.2054_FC5
Basically the packaging system has realised that if you choose to boot the old kernel 2.6.15-1.2054_FC5 which you have installed and it let you update hal or autofs, then the result would not work.
If you know you have another kernel which does work then you can remove the 2.6.15-1.2054_FC5 kernel.
And now I get even more errors:
I/O warning : failed to load external entity " " Failed to open ` ': No such file or directory I/O warning : failed to load external entity " " Failed to open ` ': No such file or directory
What does that mean? :/
Best regards, Peter Lauri
www.dwsasia.com - company web site www.lauri.se - personal web site www.carbonfree.org.uk - become Carbon Free
-----Original Message----- From: Alan [mailto:alan@lxorguk.ukuu.org.uk] Sent: Tuesday, February 27, 2007 12:05 AM To: For users of Fedora Cc: lists@dwsasia.com Subject: Re: Error, but uname -r give different indications
Error: hal conflicts with kernel < 2.6.17 Error: autofs conflicts with kernel < 2.6.17
They only work with a kernel of 2.6.17 or higher
However, when I do: uname -r I get: 2.6.19-1.2911.fc6
This is your running kernel not the only kernel you have and the rpm system is smart enough to realise this.
kernel-smp.i686 2.6.15-1.2054_FC5 installed
kernel-smp.i686 2.6.18-1.2239.fc5 installed
So you need to get rid of 2.6.15-1.2054_FC5
Basically the packaging system has realised that if you choose to boot the old kernel 2.6.15-1.2054_FC5 which you have installed and it let you update hal or autofs, then the result would not work.
If you know you have another kernel which does work then you can remove the 2.6.15-1.2054_FC5 kernel.
On Mon, 26 Feb 2007 23:46:33 +0200 "Peter Lauri" lists@dwsasia.com wrote:
And now I get even more errors:
I/O warning : failed to load external entity " " Failed to open ` ': No such file or directory I/O warning : failed to load external entity " " Failed to open ` ': No such file or directory
What does that mean? :/
Without any context I've no idea. You need to say where things appear and what you were typing when they did ?
I am doing an update from FC5 to FC6
Best regards, Peter Lauri
www.dwsasia.com - company web site www.lauri.se - personal web site www.carbonfree.org.uk - become Carbon Free
-----Original Message----- From: Alan [mailto:alan@lxorguk.ukuu.org.uk] Sent: Tuesday, February 27, 2007 12:53 AM To: For users of Fedora Cc: lists@dwsasia.com Subject: Re: Error, but uname -r give different indications
On Mon, 26 Feb 2007 23:46:33 +0200 "Peter Lauri" lists@dwsasia.com wrote:
And now I get even more errors:
I/O warning : failed to load external entity " " Failed to open ` ': No such file or directory I/O warning : failed to load external entity " " Failed to open ` ': No such file or directory
What does that mean? :/
Without any context I've no idea. You need to say where things appear and what you were typing when they did ?