There was also a thread about 1 week ago that indicated that
if CONFIG_LOG_BUF_SHIFT=<some very large number here>,
the kernel won't boot and won't tell you why.
E.g., if someone sets CONFIG_LOG_BUF_SHIFT to a buffer size in bytes
(or KB) instead of a shift value, it causes a very large log buffer
declaration and that's about all she wrote.
~Randy
On 17 Apr 2003 19:46:34 +0200 Mads Christensen <mfc@krycek.org> wrote:
| You have to get
| CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
| inorder for you to see anything =)
|
| On tor, 2003-04-17 at 19:16, Paul Rolland wrote:
| > Got the same starting with 2.5.67...
| > I took the .config from the booting 2.5.66, made a 2.5.67 kernel,
| > and when booting, booh :-(
| >
| > It was a RH8 base, Lilo... I'll try tonite to find out which option
| > is responsible of that...
| >
| > Regards,
| > Paul
| >
| > > I have a rh9 installation, grub is properly configured, and
| > > when I select
| > > to boot a 2.5 kernel it does not even decompress it. It stops
| > > even before
| > > printing the kernel version.
-
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/
This archive was generated by hypermail 2b29 : Wed Apr 23 2003 - 22:00:22 EST