Your message dated Mon, 27 Jul 2009 01:06:30 +0200
with message-id <[email protected]>
and subject line Re: Bug#377152: debian-installer: BootX of (hd-media|cdrom)
vmlinux and initrd.gz fails; miBoot works
has caused the Debian Bug report #377152,
regarding debian-installer: BootX of (hd-media|cdrom) vmlinux and initrd.gz
fails; miBoot works
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
377152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377152
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debian-installer
Severity: important
Tags: powerpc debian-installer
For Old World PowerPC Macintosh BootX hangs at the 'MMU:exit' line of
the kernel boot for both hd-media and cdrom kernel and initrd images,
but the miBoot floppy works. All methods use a variant of
2.6.16-2-powerpc, but the miBoot uses a different .config.
For BootX booting, the 2006-03-30 images are the last ones that
work. 2006-04-01 was the first use of 2.6.16-1-powerpc kernels and
initrds, however, as with the current situation, the miBoot floppies
worked (until the abi change, as change over to wouter doing the builds).
I didn't detect this situation because I only used BootX for a Beta2
install, and subsequently used the miBoot floppies.
The following system information is irrelevant; it's from a completely
different machine & architecture, but I leave it because reportbug
puts it there.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (50, 'testing'), (7, 'unstable'), (3, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.16-2-k7
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
On Sat, Feb 07, 2009 at 03:25:05PM +0100, Moritz Muehlenhoff wrote:
> On Sun, Jan 04, 2009 at 10:45:26PM -0500, Daniel Dickinson wrote:
> > On Thu, 25 Dec 2008 23:20:05 +0100
> > Moritz Muehlenhoff <[email protected]> wrote:
> > >
> > > Does this error still occur with more recent kernel versions?
> >
> > I will try later this week.
>
> Have you been able to reproduce the problem?
No further feedback, closing the bug.
If anyone reencounters the problem, please reopen this bug.
Cheers,
Moritz
--- End Message ---
