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 linux-image-2.6.16-2-powerpc: Can't boot with bootx on a beige G3 
(oldworld)
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: linux-image-2.6.16-2-powerpc
Version: 2.6.16-17
Severity: important

I wanted to upgrade from 2.6.15 to 2.6.16, but this kernel seems to be 
unbootable for my 
oldworld G3. The kernel just writes a welcome-message, writes strange green 
signs on the 
top of the screen and freezes. Because quik doesn't seem to work on the beige 
G3, I'm 
forced to use the bootx-extension for MacOS - Maybe it has sth. to do with this?

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-powerpc
Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.16-2-powerpc depends on:
ii  initramfs-tools [linux-initra 0.69b      tools for generating an initramfs
ii  mkvmlinuz                     23         create a kernel to boot a PowerPC 
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo

linux-image-2.6.16-2-powerpc recommends no packages.

-- debconf information:
  linux-image-2.6.16-2-powerpc/postinst/old-system-map-link-2.6.16-2-powerpc: 
true
  linux-image-2.6.16-2-powerpc/postinst/create-kimage-link-2.6.16-2-powerpc: 
true
  linux-image-2.6.16-2-powerpc/preinst/overwriting-modules-2.6.16-2-powerpc: 
true
  linux-image-2.6.16-2-powerpc/postinst/depmod-error-2.6.16-2-powerpc: false
  linux-image-2.6.16-2-powerpc/preinst/abort-overwrite-2.6.16-2-powerpc:
  linux-image-2.6.16-2-powerpc/prerm/removing-running-kernel-2.6.16-2-powerpc: 
true
  linux-image-2.6.16-2-powerpc/postinst/depmod-error-initrd-2.6.16-2-powerpc: 
false
  
linux-image-2.6.16-2-powerpc/prerm/would-invalidate-boot-loader-2.6.16-2-powerpc:
 true
  linux-image-2.6.16-2-powerpc/preinst/lilo-has-ramdisk:
  linux-image-2.6.16-2-powerpc/postinst/old-dir-initrd-link-2.6.16-2-powerpc: 
true
  linux-image-2.6.16-2-powerpc/preinst/bootloader-initrd-2.6.16-2-powerpc: true
  linux-image-2.6.16-2-powerpc/preinst/lilo-initrd-2.6.16-2-powerpc: true
  linux-image-2.6.16-2-powerpc/postinst/old-initrd-link-2.6.16-2-powerpc: true
  linux-image-2.6.16-2-powerpc/preinst/already-running-this-2.6.16-2-powerpc:
  linux-image-2.6.16-2-powerpc/preinst/initrd-2.6.16-2-powerpc:
  linux-image-2.6.16-2-powerpc/preinst/failed-to-move-modules-2.6.16-2-powerpc:
  linux-image-2.6.16-2-powerpc/preinst/abort-install-2.6.16-2-powerpc:
  linux-image-2.6.16-2-powerpc/preinst/elilo-initrd-2.6.16-2-powerpc: true
  linux-image-2.6.16-2-powerpc/postinst/kimage-is-a-directory:
  linux-image-2.6.16-2-powerpc/postinst/bootloader-error-2.6.16-2-powerpc:
  linux-image-2.6.16-2-powerpc/postinst/bootloader-test-error-2.6.16-2-powerpc:


--- 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 ---

Reply via email to