Skip to contentSkip to conversation

[2.5.69] Fails on "Uncompressing Kernel" (detailed)

DISCUSSION walt 3 participants 3 messages May 6, 2003 1 message not in the archive

lore
Share & tools
lore

walt

author
#1 lore raw
In reply to a message not in the archive
Quoted 2 lines · David van Hoose

I've managed to get 2.5.69 to boot *once*. Not trusting the kernel to report the numerous problems until I can boot the kernel more than once. I lost my config so I can't figure out what I managed to do so right. I have tried a couple other configs that I normally use for 2.4.x, but with the new 2.5.x options. Those I have attached. All I get is the "Uncompressing Linux" and then no more output. However, it appears that my system is booting anyway as if it is on another TTY.

The configuration menu has changed recently so that support for normal console operation is not included by default. To activate the usual console on VT and on VGA requires selecting options that are buried in the 'Character device' 'Input device' and 'Graphics support' menu sections. Go all the way to the bottom of each section and you will see the obvious items you need to select. Rather a confusing change.

#2 lore raw
Quoted 6 lines · walt

The configuration menu has changed recently so that support for normal console operation is not included by default. To activate the usual console on VT and on VGA requires selecting options that are buried in the 'Character device' 'Input device' and 'Graphics support' menu sections. Go all the way to the bottom of each section and you will see the obvious items you need to select. Rather a confusing change.

Was that deliberate? I have to wonder if having a default which doesn't work for most people is worth the gain (which I don't see, but assume is there).

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#3 lore raw
In reply to walt
Quoted 11 lines · walt
Quoted 2 lines · David van Hoose

I've managed to get 2.5.69 to boot *once*. Not trusting the kernel to report the numerous problems until I can boot the kernel more than once. I lost my config so I can't figure out what I managed to do so right. I have tried a couple other configs that I normally use for 2.4.x, but with the new 2.5.x options. Those I have attached. All I get is the "Uncompressing Linux" and then no more output. However, it appears that my system is booting anyway as if it is on another TTY.

The configuration menu has changed recently so that support for normal console operation is not included by default. To activate the usual console on VT and on VGA requires selecting options that are buried in the 'Character device' 'Input device' and 'Graphics support' menu sections. Go all the way to the bottom of each section and you will see the obvious items you need to select. Rather a confusing change.

That's all nice, but why have those options been removed if input devices are created as modules? This somewhat breaks compatibility with a lot of 2.4.x scripts. I run both kernels so I can compare things and send bug reports with both trees. Also, 2.5.x has been rather cruel to me in the past, so I tend to run the stable branch more often than not. Can the VT and VGA options be placed back into the config if input devices are created as modules? It would remove some confusion imo.

Thanks,
David