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

Bug#717511: marked as done (Kernel does not start up on Pegasos-2)

Your message dated Sun, 21 Jul 2013 20:36:41 -0400
with message-id <51EC7E99.9030704@physics.harvard.edu>
and subject line Re: Bug#717511: Kernel does not start up on Pegasos-2
has caused the Debian Bug report #717511,
regarding Kernel does not start up on Pegasos-2
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 owner@bugs.debian.org
immediately.)


-- 
717511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717511
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.2.0-4-powerpc
Version: 3.2.46-1

 Hello!
 I  have  just upgraded Linux installation on my Pegasos-II machine to
Debian  7.1.0  Wheezy.  The installer worked flawlessly, but the newly
installed  kernel  refused  to  boot up. Attempt to boot up the kernel
ends  up  in  a  text-mode  screen  filled  up  with  garbage  (randon
characters and attributes).
 What's up ? Did you drop Pegasos support ?

-- 
С уважением,
 Pavel                          mailto:pavel_fedin@mail.ru

--- End Message ---
--- Begin Message --- 
Control: notfound -1 yaboot-installer/1.1.26

On 07/21/2013 04:55 PM, Ben Hutchings wrote:

Control: reassign -1 yaboot-installer 1.1.26

On Mon, 2013-07-22 at 00:38 +0400, Pavel Fedin wrote:
[...]

  So,  it's  not  kernel's  fault. It seems to be installer fault which
does  not generate correct vmlinuz image when not using separate /boot
partition.  vmlinux,  i  know,  is another thing. It's a "plain" image
meant to be ran from GRUB or yaboot. It cannot be run from OFW.
  So,  we  can  close  this,  probably with a notification to Installer
guys.


There is no need to close it.  I'm reassigning to the relevant part of
the installer.
The particular partition/file-system layout reported in this bug report cannot work.
This platform does not have a boot loader at all. Firmware knows how to load kernel directly from affs1, ext2 or older implementations of ext3 file systems. It is possible to tweak options while creating ext3 with current tools to make it work, but it is not worth the trouble.
In practice this means you have to have ext2 boot partition, to place the kernel onto, for this machine to boot.
Installer correctly creates ext2 boot partition and ext4 root partition. The identical mkinitramfs and mkvmlinuz commands are issued during installation as those during kernel upgrades. The generated vmlinuz loads and kernel works fine. 

Closing this bug report. This is not a bug.


Milan

--- End Message ---
Reply to: