Twice over the past few months I had problems with KDM crashing on boot-up and killing X. Once this started, there was no way out other than to re-install the liblcms rpm. (A little detective work showed that it died loading liblcms.) As I say, this happened twice, but I haven't seen the problem for quite some time. But, just a few minutes ago, When I booted my Thinkpad, I spotted a couple of error messages go by during the boot process: <2>EXT2-fs error (device ide0(3,7)): ext2_read_inode: unable to read inode block - inode=539900, block=1081356 <2>EXT2-fs error (device ide0(3,7)): ext2_read_inode: unable to read inode block - inode=850817, block=1703956 Turned out that inode 539900 is in liblcms.so.1! (inode 850817 was in the directory /usr/lib/i686.) Even so, X and KDM/KDE came up without problem. I booted the rescue system off of CD1 and did an e2fsck which reported no errors. I remembered one change I made to boot.local based on a message in this mailing list. I added: hdparm -c1 -k1 /dev/hda I removed that before rebooting and everything was back to normal. I'll see if the problem *stays* fixed, but I really won't know for quite some time since it only happened about once a month or less anyway. And I'm not even sure the problem started after that change. So, does this make sense to anyone? If the problem was with the hard disk (or its parameters as set by hdparm) how come it always showed up with the same file, even after two re-installations? I know that at least with the first re-install I removed all the KDE rpms before re-installing them so I don't think the file was at the same physical location on the hard disk each time. P.S. SuSE 7.3 on IBM Thinkpad T21 (Intel) -- ____________________________________________________________________ Robert Paulsen robert@paulsenonline.net My old email address (paulsen@texas.net) will soon be discontinued.