When attempting a system update, i get the following 3 conflicts:

kernel-default 2.6.8-24 conflict
Required by:
kernel-default-nongpl requires kernel-default = 2.6.8-24
Conflict Resolution:
( ) Downgrade kernel-default-2.6.8-24.10 to Version 2.6.8-24
( ) Remove the Referring Package
Delete kernel-default-nongpl
( ) Ignore Conflict and Risk System Inconsistencies

libxine1 1.0-0.pm.0 conflict
Required by:
kaffeine requires libxine1 >= 1-
Conflicts with:
xine-lib obsoletes xine
xine-lib obsoletes xine-lib
Conflict Resolution:
( ) Remove the Conflicting Package
Delete xine-lib
( ) Remove the Referring Package
Delete kaffeine

xine-lib 0.99.rc6a-4 conflict
Conflicts with:
libxine1 obsoletes xine-lib
libxine1 obsoletes xine
Conflict Resolution:
( ) Do Not Update xine-lib
( ) Remove All 2 Conflicting Packages
Delete kaffeine
Do Not Install libxine1

I don't understand the first conflict. Can someone explain this?
The other 2...I don't want to remove kaffiene.
Can't kaffiene just use the newer version of libxine1 and xine-lib?

System updates should always be run from a boot-CD of the higher version. Otherwise the old kernel is still in memory and may interfere with the installation (because 'uname -r', which is used in many installation scripts, returns the wrong kernel version).

I don't think i have a boot-cd of the higher (kernel) version.
I installed the system from dvd, the later updated the kernel via download.

Did you also download and install the correct kernel-default-nongpl package?

You will find a boot CD on any SUSE/Novell FTP server.

>>Did you also download and install the correct kernel-default-nongpl package?
yes

I should believe what you are telling me, though I have some doubts

Try rpm -q kernel-default and rpm -q kernel-default-nongpl and see if their versions are matching. On my 9.2 system (after YOU) it reads
Note 24.11 !

Again: update is easier with a boot-CD ( ftp://ftp.suse.com/pub/suse/i386/9.2...stallation.iso )

# rpm -q kernel-default
kernel-default-2.6.8-24.10
SuSEBox:/home/mickeydog # rpm -q kernel-default-nongpl
kernel-default-nongpl-2.6.8-24.10

not .11 but they are the same

Deepest apologies for mistrusting you

The version 11 came with an online update.

What about 'uname -r'? There must be something that is causing the dependency problem. Still: try the boot-CD

>>Deepest apologies for mistrusting you
no sweat, best to be a bit skeptical

# uname -r
2.6.8-24.10-default

what does this mean?

Nothing. Everything is alright. I asked this question to be sure that the new kernel is also residing in memory, not only in rpm-database. Now I really have no clue why the dependency error occurred. What happens if you ignore the warning?

>>What happens if you ignore the warning?
I haven't tried this. What are the potential consequences? Could I end up trashing my system?

Yes you could, but if you have a bootable SUSE CD on hand, you can always restore the previously installed kernel.

getting back to this....
i've downloaded the iso you suggested and burned the image onto a cd
the setup is such that it looks first to the CD drive to boot.
It appears to start booting from the CD, however, i get a menu that says:

Boot from Hard Disk
Installation
Installation - ACPI Disabled
Installation - Safe Settings
Manual Installation
Rescue System
Memorty Test

I don't want any of these, i want Boot from CDROM
What do I do?

Where did you get the system update you tried the first time? Was it YOU? I don't understand why you wouldn't get updates for both the default and nongpl kernel if you were updating thru YOU.

Anyway, you need to delete xine-lib before you install libxine-1. You can ignore any warnings you get about deleting xine-lib. You don't need to delete kaffeine.

As far as using the boot cd, choose installation and then you will get the upgrade option.

The 'Rescue System' gives you a usable system to do the kernel reinstallation. The basic steps would be:
booting
login (empty password)
mounting the root partition
chroot to this mountpoint
reinstall the kernel-rpm (should be available on disk/CD, network will probably not work)
reboot