On Sat, 28 Jul 2012 17:30:38 +0100 Mick <michaelkintz...@gmail.com> wrote:
> On Saturday 28 Jul 2012 16:59:10 Pandu Poluan wrote: > > On Jul 28, 2012 10:29 PM, "Neil Bothwick" <n...@digimed.co.uk> > > wrote: > > > On Sat, 28 Jul 2012 13:22:24 +0300, v...@ukr.net wrote: > > > > Hello again! > > > > > > > > The problem is solved by adding the following kernel config > > > > option: CONFIG_HID_GENERIC=M > > > > > > > > This option was not present in the old configuration files, > > > > that is > > > > > > > > why simple 'make oldconfig' did not do the job. > > > > > > make oldconfig should pick up new options, that's what it's for. > > > I've just upgraded a box from 3.4.4 to 3.5.0 and it prompted for > > > this option, defaulting to Y (there's little point in making > > > something that is always required a module). > > > > I myself prefer make menuconfig to make oldconfig, because I can > > easily see new options, and also invoke some help text that (tries > > to) explain what the option is about. Not to mention an > > easy-to-read "chain of dependencies" of an option. > > > > Rgds, > > Hmm .... but the "H" option in 'make oldconfig' allows you to see the > help text before you decide to accept it or not. Of course, the help > text itself may require you to obtain a University degree in kernel > hacking to decipher it ... but to some extent that's the fun of it > all. ;-) I use both: first oldconfig to find the newly added stuff. Not dealing with these right away breaks things horribly. then menuconfig, mostly looking for driver pages that have lots of things set - I can't possibly have all of that hardware so logically few things must be set. menuconfig also lets me easily see things I hve never explicitly set (which oldconfig can't do) and labels them (NEW) which is distinctly different to what oldconfig calls new stuff And in menuconfig, the / key engages search, just like in vim -- Alan McKinnon alan.mckin...@gmail.com
