Bug#265831: Debian kernels are unusable on TITAN-based systems because of LEGACY_START_ADDRESS

To: Steve Langasek <vorlon@debian.org>, 265831@bugs.debian.org
Subject: Bug#265831: Debian kernels are unusable on TITAN-based systems because of LEGACY_START_ADDRESS
From: Norbert Tretkowski <tretkowski@inittab.de>
Date: Sun, 15 Aug 2004 13:47:13 +0200
Message-id: <[🔎] 20040815114713.GC8411@rollcage.inittab.de>
Reply-to: Norbert Tretkowski <tretkowski@inittab.de>, 265831@bugs.debian.org
In-reply-to: <[🔎] 20040815083712.1CBA23AE0@quetzlcoatl.dodds.net>
References: <[🔎] 20040815083712.1CBA23AE0@quetzlcoatl.dodds.net>

* Steve Langasek wrote:
> The DS15, DS25, DS45, and ES47 alpha systems require a kernel built
> with LEGACY_START_ADDRESS=n. Some MILO-based systems, however, can't
> boot *without* LEGACY_START_ADDRESS being set. Please add another
> kernel-image variant so that Debian can properly support both types
> of systems.
> 
> http://lists.debian.org/debian-alpha/2004/08/msg00012.html

Should we fix this for sarge? I suppose the d-i people will kill us
when we introduce a new flavour for the 2.4.26 kernel-images.

Norbert

Reply to:

Follow-Ups:
- Bug#265831: Debian kernels are unusable on TITAN-based systems because of LEGACY_START_ADDRESS
  - From: Steve Langasek <vorlon@debian.org>

References:
- Bug#265831: Debian kernels are unusable on TITAN-based systems because of LEGACY_START_ADDRESS
  - From: Steve Langasek <vorlon@debian.org>

Prev by Date: Bug#261893: kernel-image-2.6.6-1-generic: Kernel bug at mm/slab.c:1530
Next by Date: Bug#261734: similar problem
Previous by thread: Bug#265831: Debian kernels are unusable on TITAN-based systems because of LEGACY_START_ADDRESS
Next by thread: Bug#265831: Debian kernels are unusable on TITAN-based systems because of LEGACY_START_ADDRESS
Index(es):
- Date
- Thread