|
From: Jules <ju...@ds...> - 2004-09-09 08:35:04
|
> > >It may be outdated and may not apply to your >problem, but it is probably worth looking at >the sig 11 FAQ: >http://www.bitwizard.nl/sig11/ > Thanks. I'm pretty sure this isn't hardware related, as the same system runs the kernel supplied with the binary package just fine, plus kernels compiled by myself work OK without colinux. I've compiled a copy of the kernel with the config file supplied in the colinux source distribution, and that seems to be working, I'm going through a second compile of it now, with it running, and it seems to be pretty stable. It's got a lot farther than the last one did, at least. So I guess it was one of the config options that did it. Are there any that are known to be dangerous with colinux? The main changes I made were optimising for my processor environment (changed from CONFIG_M586 to CONFIG_MK7, disabled CONFIG_X86_GENERIC, all consequential changes from this). I also killed support for a.out binaries, moved binfmt_misc to a module, switched off the kernel debugging options, and added support for unloading modules. There were other changes too, but mostly relating to filesystems, which I don't think are likely candidates. Any suggestions on what may have caused the problem? |