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

Bug#339592: marked as done (installation-reports: [powerpc] CHRP workaround)



Your message dated Wed, 08 Sep 2010 03:58:07 +0000
with message-id <E1OtBnT-0004wg-1z@ravel.debian.org>
and subject line Closing old installation report #339592
has caused the Debian Bug report #339592,
regarding installation-reports: [powerpc] CHRP workaround
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.)


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

Debian-installer-version: Debian GNU/Linux testing "Etch" - Official Snapshot
powerpc Binary-1 (20051116)
uname -a: Linux gazam 2.6.12-1-powerpc64 #1 SMP Tue Sep 27 15:20:16 UTC 2005
ppc64 GNU/Linux
Date: 2005-11-16
Method: Netinst.iso

Machine: IBM Power5
Processor: POWER5 (gr) CHRP IBM,9406-520
Memory: 2047116 kB
Root Device: SCSI /dev/sda2
Root Size/partition table:
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda2               225838     84996    128794  40% /
/dev/sda5              4807056    237648   4325224   6% /usr
/dev/sda6              1829159    138266   1593300   8% /var
tmpfs                  1023556         0   1023556   0% /dev/shm
/dev/sda7              4807056    131260   4431612   3% /opt
/dev/sda8              9614116    131288   8994456   2% /home
/dev/sda10             2885780     65660   2673532   3% /tmp
Output of lspci and lspci -n:
lspci
0000:00:02.0 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03)
0000:00:02.2 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03)
0000:c0:01.0 SCSI storage controller: Mylex Corporation AcceleRAID
600/500/400/Sapphire support Device (rev 04)
0000:c8:01.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
Controller (rev 03)
0000:c8:01.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
Controller (rev 03)
lspci -n
0000:00:02.0 0604: 1014:0188 (rev 03)
0000:00:02.2 0604: 1014:0188 (rev 03)
0000:c0:01.0 0100: 1069:b166 (rev 04)
0000:c8:01.0 0200: 8086:1079 (rev 03)
0000:c8:01.1 0200: 8086:1079 (rev 03)

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

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

Comments/Problems:
At the install from the basesystem in expertmode it asks what kernel to install,
d-i defaults to a 2.6 smp kernel. This is not the right one, chosen
linux-image-2.6.12-1-powerpc64. 

There is no way to create a PreP boot partition with partman.
To create a Prep partition I have to escape to shell and use parted.

At the stage to install the bootloader I get the following error:
yaboot-installer: mkofboot: Error in /etc/yaboot.conf: `magicboot' scripts
cannot be used with fstype=raw
To install the bootloader I have to chroot the installed system and manually
dd /usr/lib/yaboot/yaboot to /dev/sda1.
In the installed yaboot.conf is a line "device=", I have to comment it out to
get it to work. 

Next we have our console at an HMC. I had todo the following to get the
console to work:
mknod hvc0 c 229 0
chown root:tty hvc0
chmod 600 hvc0

Add an entry in /etc/securetty for hvc0
Add an entry in /etc/inittab:
hvc0:12345:respawn:/sbin/getty -L hvc0 9600

System is now up 'n running



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