[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



On Sun, Aug 15, 2004 at 01:47:13PM +0200, Norbert Tretkowski wrote:
> * 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.

It shouldn't hurt anything if you make the change before sarge, but I
don't expect the TITAN systems to be supported for 3.1r0.

The conundrum is that I think "generic" would be a better fit for the
packages with LEGACY_START_ADDRESS=n, but this could cause upgrade
problems for users currently using the -generic images on MILO-based
systems that could have been installed from woody.  It's probably best
to make this change coincide with a package name change so that systems
don't break on upgrade -- either the introduction of 2.4.27, or the
kernel flavor rename that I understand you have pending.

Thanks,
-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: