On Wed, Oct 25, 2006 at 08:52:08AM -0400, hendrik@topoi.pooq.com wrote: > > > But only after you have finished > > investigating what is causing the badness in the current install. > > If I knew how to do this (besides a few variations on rebooting and > fsck) I wouldn't be considering a reinstall. > I assume that all your efforts so far are producing no results.... Do you have any older kernels on the etch system that you can try? Maybe there's a kernel bug that you're hitting (some random combination of kernel version and hardware). If you can boot an older kernel that might help. If you don't have one, and want to try, you could chroot into the system and install an older kernel maybe (from debian snapshots?). I only suggest this because I had a booting problem after a kernel upgrade on an older machine (300 mhz celeron). I just went back to an old kernel and stayed there. Anyway. I'm concerned that you've got some problem that will come back after the reinstall. Or maybe, by reinstalling, you'll leapfrog the problem, I suppose. Regardless, if you can't figure out what the problem is you may have trouble avoiding it in the future. Just a hunch, did you change kernel architecture? to the wrong one accidently perhaps? A
Attachment:
signature.asc
Description: Digital signature