On Fri, 27 Apr 2007 08:03:42 +0200 Mike Galbraith wrote: > On Fri, 2007-04-27 at 07:40 +0200, Jan Engelhardt wrote: > > On Apr 26 2007 05:06, Mike Galbraith wrote: > > >On Wed, 2007-04-25 at 22:30 +0200, Sam Ravnborg wrote: > > > > > >> > There are general funnies in the menuconfig world (my preference) here. > > >> > For instance, I recently had reason to change/test different default IO > > >> > schedulers, and found that no matter what I did, I couldn't select a > > >> > default IO scheduler any more, though I used to be able to do so. > > > > > >> Tried it now with latest -git from Linus and here it works. > > >> Notice that you need to make the scheduler a built-in <*> > > >> before you can select it as default. > > >> A scheduler selected as a module <M> cannot be made default. > > > > > >Ok, I guess my ncurses is ill. (all built in) Thanks. > > > > CONFIG_MODULES=n? > > No, I have more modules that you can shake a stick at. > > CONFIG_MODULES=y > CONFIG_MODULE_UNLOAD=y > CONFIG_MODULE_FORCE_UNLOAD=y > CONFIG_MODULE_SRCVERSION_ALL=y
I don't see a menuconfig problem either. Perhaps posting your full .config would help. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/