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

Bug#350527: marked as done (Booting error on IBM RS6000 7046-B50)

Your message dated Wed, 08 Sep 2010 03:58:10 +0000
with message-id <E1OtBnW-00053j-3C@ravel.debian.org>
and subject line Closing old installation report #350527
has caused the Debian Bug report #350527,
regarding Booting error on IBM RS6000 7046-B50
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.)


-- 
350527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350527
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: CD
Image version: vmlinuz-chrp.initrd  from http://people.debian.org/~luther/d-i/images/2005-12-28/powerpc/cdrom/
Date: 2006.1.30

Machine: IBM 7046-B50
Processor: IBM RS6000 ,PPC, CHRP
Memory: 256MB
Partitions: 

Output of lspci and lspci -n:

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:
I tried booting on IBM 7046-B50.
I used the image, vmlinuz-chrp.initrd, from 2005.12.28 and 2005.8.15 directory.
Because the initrd.gz in daily folder couldn't be unzipped, I tried two older images.
But it was failed as the following
I upgraded this machine's firmware about 10 days ago.
My machine is now IBM RS6000 7046-B50, CHRP with 512MB.
.
Frindly,
Nobel

Booting message
================
RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000
RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000

          1 = SMS Menu                          5 = Default Boot List
          8 = Open Firmware Prompt              6 = Stored Boot List

       memory      keyboard     network      scsi      speaker
 ok
0 > boot cdrom:,\vmlinuz-chrp.initd console=ttyS0
 ok
0 > boot cdrom;,\vmlinuz-chrp.initrd console=ttyS0
LOAD: Waiting 60 seconds for Spanning Tree
LOAD:BOOTP: do-BOOTP-req failed : 1
LOAD:BOOTP: do-BOOTP-req failed : 2
LOAD:BOOTP: do-BOOTP-req failed : 3
LOAD:BOOTP: do-BOOTP-req failed : 4
LOAD:BOOTP: do-BOOTP-req failed : 5

LOAD:BOOTP: ERROR!!! BOOTP request failed, ABORT
!20A80004 !

 ok
0 >


MKISOFS command I used
====================
alpha:/home/datatek#  mkisofs -r -J -o vmlinuz-chrp.initrd.iso vmlinuz-chrp.initrd
INFO:   ISO-8859-1 character encoding detected by locale settings.
   Assuming ISO-8859-1 encoded filenames on source filesystem,
   use -input-charset to override.
Total translation table size: 0
Total rockridge attributes bytes: 260
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 22000
3336 extents written (6 MB)
alpha:/home/datatek#


Gunzip output message I got from DOS and Linux
==================================
C:\Download>gzip -d initrd.gz
gzip: initrd.gz: not in gzip format

alpha:/home/datatek# alpha:/home/datatek# gunzip -d initrd.gz
alpha:/home/datatek# gunzip: initrd.gz: not in gzip format

　

DataTek                       정  기  용
Top in Data Protection                                        기술영업/이사

　

데이터텍주식회사
www.datatek.co.kr

서울 중구 만리동 KCC 파크타운 101-108호
Tel : 02-365-5766  Fax : 02-365-5765
Mobile : 016-390-5763
E-mail : kyjung@datatek.co.kr, support@datetek.co.kr


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