Wow Shafe1:
That is some strange goings on in your neighbourhood.
Ok lets see .. you have a module for zip being loaded up? Check out dmesg to confirm the error.
Segmentation failure could be for a vast number of reasons, post your logs here or email them to me.
The fsck after a hard reboot is normal, that is the way ext2 was designed to function.
Regarding framebuffers, its always a good thing, if you have VESA2.0 cards and 2.2.xx kernels .. is your card VESA2.0? S3 Virge and S3 Trio cards have NASTY probs cos they are VESA1.2 [I think its 1.2], [see what I mean abt it being helpful to know the hardware] .. try applying patches for these cards, if you have one of those ..
ftp://ccssu.crimea.ua/pub/linux/kernel/v2.2/unofficial/s3new.diff.gz
We've seen a few failing mobo's & mobo IDE controllers that cause problems with data integrity of a very similar nature as you described.
At this point I dont even know if this is distribution specific. However if you'd like to put up your logs, lilo.conf, rc.sysinit into my email or put it on an http address and mail me the URL, I'll look into it as soon as I get a chance.
How did you shut off the apmd?
|