SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, Trying to figure out how come when I update kernel via YOU and run system update through YaST I get a
-Dependancy Conflict:
-Kernel - smp 2.6.8-24 conflict
-conflict resolution:
*downgrade kernel - smp -2.6.8-24.14 to version 2.6.8-24
*delete kernel - smp - nongpl
*ignore conflict & risk system inconsistencies
If you are supposed to do this from boot then why is it enabled in YOU?
How does one use a boot disc to update the kernel?
I used Mandrake before and it would give you an option to install or upgrade upon boot. I do not see this in SuSE 9.2 DVD. Also there is no newer disc to upgrade from to my knowledge (but this means nothing), is there?
What am I missing here, do I have to compile a new kernel and then boot to it?
Did you run YOU after doing some modifications? Or did you run it a second time without rebooting? Usually you don't need to run kernel updates from a boot CD, but you need to reboot after the update.
I guess you mixed-up 'System Update' and YOU. A system update doesn't make sense for you as long as 9.3 hasn't been released on FTP. YOU only installs bugfixes and security updates, but keeps the same base version of your kernel.
Ran YOU downloaded all patches, then rebooted, then did the system update, which shows that error.
If one does not need to run system update then why does it show this error?
I basically thought that system update was like a gui updatedb.
Even if I am entirely wrong, how do I update the kernel? As SuSE Watcher is not happy after I choose to downgrade kernel-smp-2.6.8-24.14 back to version 2.6.8-24.
So what I am saying is the it still tells me I need this patch, but when I download it, reboot, run system update via YaST, this same patch shows conflict.
So are you saying ignore it all completely and do not use system update, unless 9.3 is out?
Originally posted by cjae
I basically thought that system update was like a gui updatedb.
Even if I am entirely wrong, how do I update the kernel? As SuSE Watcher is not happy after I choose to downgrade kernel-smp-2.6.8-24.14 back to version 2.6.8-24.
So what I am saying is the it still tells me I need this patch, but when I download it, reboot, run system update via YaST, this same patch shows conflict.
So are you saying ignore it all completely and do not use system update, unless 9.3 is out?
YOU will update the kernel for you when there are security issues or bug fixes. It's all you need to use. System update is not a gui updatedb. It's for updating your system with a newer version that you have on a disc. Don't run system update after YOU.
Not trying to query your judgment, but does anyone else agree with this?
Definitely to 100% !
I am not sure why they offer the option 'System Update' at all. SUSE/Novell state that a system update should only be performed by booting from CD.
I am not sure how to reverse the problems of a failed 'System Update'. It depends on which packages have been installed that do not belong to your system. I would recommend to run YOU again and tick 'Reload all patches from server' and tick the kernel-patch again, even if already installed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.