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

Bug#382787: marked as done (failed boot on RS/6000 H50)



Your message dated Wed, 08 Sep 2010 03:58:16 +0000
with message-id <E1OtBnc-0005HA-Li@ravel.debian.org>
and subject line Closing old installation report #382787
has caused the Debian Bug report #382787,
regarding failed boot on RS/6000 H50
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.)


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

Debian-installer-version: as supplied on Debian 3.1r2 net-install CD
uname -a: didn't get that far

Date: 2005-08-10
Method: CD-rom from Debian 3.1r2 as-is and altered per instructions on 
	debian-ppc mailing list
Machine: IBM RS/6000 H50
Processor:dual PowerPC 604e
Memory:128 MB
Root Device: didn't get that far; intended to be /dev/sda
Root Size/partition table: didn't get that far
Output of lspci and lspci -n: didn't get that far

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 purpose of this phase of install is for my vendor to confirm that
linux will run on the H50 prior to shipping it.  All we want is to get
some indication that linux will work.  Even getting the plain kernel to
load without parameters and then panic with no init would be OK.  Don't
need to actually run the installer until I get the unit here.  The
vendor is not a unix person and not a command-line type; they
normally only run the diagnostics and then ship.

The CD as is doesn't boot.  Debian-PPC mailing list said that the
problem was that the RS/6000 looks for some boot stuff in an extra
directory and that yaboot looks for its config in /etc/yaboot.conf.

I made these changes and burned a new CD calling it -alt.iso

It still doesn't boot.

Manually from the OF command line boot cdrom:,\install\yaboot
works, but yaboot is looking on /dev/sda:/etc for yaboot.conf instead of
the CDROM.

Manually from the OF command line boot cdrom:,\install\powerpc\vmlinux
get error 'claim failed' printed right after the command line on the
same line.  No other change to the display.

In an attempt to isolate the problem, have also tried to boot the LFS
live-cd which uses a parameterless monolithic kernel and also got the
'claim failed' error.  I don't know what is generating the message.

I have suggested to my vendor that from the yaboot boot: promt he enter 
	boot cdrom:,/install/powerpc/vmlinux 

followed by all the parameters that the yaboot.conf shows for the
install image, and including video=ofonly.  I've never seen yaboot and
the manual boot section in the documentation is rather sparse.

He has been using a video card with keyboard.  I've suggested that he
remove the video card and use the terminal on ttyS0.

I haven't heard back on these last two suggestions due to the weekend.

Any suggestions?

Thanks,

Doug Tutty.



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