Re: 2.5.70 hangs on boot

Vojtech Pavlik (vojtech@ucw.cz)
Sat, 14 Jun 2003 00:12:09 +0200


On Fri, Jun 13, 2003 at 10:49:44PM +0100, Dave Jones wrote:
> On Thu, Jun 12, 2003 at 09:08:39PM -0400, OverrideX wrote:
> > Hi all,
> >
> > I've tried 2.5.70, 2.5.70-mm8 and 2.5.70-bk17. All of them hang while
> > booting, the last message they display is "Uncompressing Linux... Ok,
> > booting the kernel." then they just sit blank and boot no further. I've
> > booted previous 2.5.x kernels on this system, the last I had used was
> > 2.5.63. My Hardware and other info is below, .config is attached. Is
> > anyone else experiencing this problem? Is there any other information I
> > can provide to help debuging? Please cc me any replies as my mailbox
> > can't take the full brunt of this mailing list, thanks -Dan
>
> Ugh, what a mess. Take a look at http://www.codemonkey.org.uk/post-halloween-2.5.txt
> You'll notice that your .config doesn't contain most of those in the
> 'gotchas' section that it suggests you make sure you have.
>
> The root cause of this is that you have CONFIG_INPUT=m.
>
> CONFIG_VT only shows up if you have CONFIG_INPUT=y.
> With it set to =m a whole bunch of options never ever show up in the
> configuration.
>
> This really wants fixing badly. The source of this problem seems to be
> people taking 2.4 configs (where CONFIG_INPUT=m was fine), and it all
> going pear-shaped when people make oldconfig. I'm aware of the problems
> that oldconfig can't override variables set in .config, so how about
> just renaming CONFIG_INPUT to something else ?

I'm considering CONFIG_INPUT_ADVANCED, which would default to 'n', like
with the font and parition config and if set to 'n', all the modules
needed for 2.4 functional compatibility would be automatically built in.
What do you think?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/