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

Bug#382433: marked as done (debian-installer: IBM RS/6000 7046-b50 doesn't boot)

Your message dated Wed, 08 Sep 2010 03:58:16 +0000
with message-id <E1OtBnc-0005Gq-HQ@ravel.debian.org>
and subject line Closing old installation report #382433
has caused the Debian Bug report #382433,
regarding debian-installer: IBM RS/6000 7046-b50 doesn't boot
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.)


-- 
382433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382433
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports
Boot method: CD. Image retrieved from http://cdimage.debian.org/ cdimage/daily-builds/daily/current/powerpc/iso-cd/ Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/ current/powerpc/iso-cd/debian-testing-powerpc-netinst.iso 2006-08-04 
Date:  2006-08-04 - 2006-08-09

Machine: IBM RS/6000 7046-b50
Processor: 604r 375 MHz
Memory: 1GB
Partitions: not applicable

Output of lspci and lspci -n: not applicable

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [E]
Configure network HW:   [ ]
Config network:         [ ]
Detect CD:              [ ]
Load installer modules: [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Create file systems:    [ ]
Mount partitions:       [ ]
Install base system:    [ ]
Install boot loader:    [ ]
Reboot:                 [ ]

Comments/Problems:
The stock image does not reach the yaboot boot: prompt but fails with a unexpected firmware error. If I modify the image by adding the yaboot.ibm boot loader by Open Suse 10 Enterprise beta for ppc I got there. I'm able to boot a kernel from install/powerpc, but not with an initrd image. When I try to use the initrd-image I got the same unexpected firmware error as with the stock yaboot. Without the initrd-image I run into the problem that the boooting stopps with not finding a root filesystem. The weird thing is that I could use the cd's from the Open Suse Enterprise 10.x beta and those boot and even install. On a RS/6000 with 2 two cpu's (h80?) the system installs the ppc64 without any major problems. I updated the firmware up to the recent version available at IBM. If I could be at further assistance do not hesitate to ask.

Attachment: PGP.sig
Description: Signierter Teil der Nachricht


--- End Message ---
--- Begin Message --- 
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---
Reply to: