I once had a discussion about kernel modules with broch that went totally out of hand, so I would like to ask very carefully: Are you sure? Because I see the module in /lib/modules and find CONFIG_EXT3_FS=m in /boot/config-2.6.13-15.7-default

the 'fdisk -l' does not list the sata drive. there is no hdb* either.

Tricky!
Do you see the sis module loaded in lsmod?
If not, try loading with modprobe and do the fdisk again.
Maybe you could play with bios settings?

Probably, the kernel downgrade is the best solution...

I hate to jump in, but how did you read the lsmod file? and which did you read? Thanks.

I am just doing this for my own knowledge, and wanted to thank you for the info given. Thanks.

guys:

I chickened out. thanx for all the help. I got back the old kernael through
yast and everything is hungi dori again.

now the next question is what is the good practice for such kernel updates.
what do I back up and make sure i get back if something is wrong?

can i make some kind of bootable cd and copy files over?

I saw in original suse 10 cd a 'repair' feature but apparently did nto notice this (quite important, I must say) sata drive controller inconsistency.

If by boot drive was sata I would be out in the cold?

thanx once again

EclipseAgent:
'lsmod' is not a file but a command to list all modules that the kernel has loaded.


nanjil:
Sorry to hear that you couldn't solve the problem the other way. Usually, kerenl updates are quite safe. I know one more kernel update that broke minor functionallity in 9.1, but that was quickly solved by SUSE with another patch.
I would recommend to continue installing these updates, hoping for a fix of your current problem. Even if you've had your root filesystem on the s-ata drive, you could recover the system from a LiveCD.

what I di was I reported bug through bugzilla/novell and marked it as a show stopper. Hopefully it gets the attention of somebody