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

Bug#308809: marked as done (Inst. report, IBM RS6k 43P-140)

Your message dated Wed, 08 Sep 2010 03:57:58 +0000
with message-id <E1OtBnK-0004fn-PP@ravel.debian.org>
and subject line Closing old installation report #308809
has caused the Debian Bug report #308809,
regarding Inst. report, IBM RS6k 43P-140
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.)


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

INSTALL REPORT

Debian-installer-version: 28.04.2005, weekly snapshot
uname -a: Linux x118 2.6.8-powerpc #1 Sun Mar 20 14:09:41 CET 2005 ppc GNU/Linux
Date: Thu, 12 May 2005 12:52:46 +0200
Method: 
CD-based installation, network sources added later
Boot with CD (El Torito)

Machine: IBM RS/6000 PReP IBM 43P-140 (Tiger1)
Processor: Power 604ev
Memory: 64MiB
Root Device: /dev/sda3
Root Size/partition table:
major minor  #blocks  name
   8     0    4406935 sda
   8     1       8001 sda1
   8     2     289170 sda2
   8     3    4104607 sda3

Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 30)
0000:00:0b.0 ISA bridge: IBM Fire Coral (rev 03)
0000:00:0c.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 16)
0000:00:0d.0 ff00: IBM MPIC interrupt controller
0000:00:10.0 SCSI storage controller: LSI Logic / Symbios Logic 53c825 (rev 13)
0000:00:16.0 VGA compatible controller: IBM GXT250P/GXT255P Graphics Adapter (rev 02)
0000:00:17.0 PCI bridge: IBM IBM27-82351 (rev 01)

0000:00:00.0 0600: 1057:0002 (rev 30)
0000:00:0b.0 0601: 1014:000a (rev 03)
0000:00:0c.0 0200: 1022:2000 (rev 16)
0000:00:0d.0 ff00: 1014:0046
0000:00:10.0 0100: 1000:0003 (rev 13)
0000:00:16.0 0300: 1014:003c (rev 02)
0000:00:17.0 0604: 1014:0022 (rev 01)

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

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

* Only worked with Ext3. With JFS, failed while creating the FS (#308769), with ReiserFS, debootstrap has failed (#308774).

Comments/Problems:


Things that did not work (BUGS or important features missing):

 - automated creation of a prep partition in "guided partitioning" mode
 - boot loader configuration, read: installing of the image into the magic
   partition, the vmlinuz itself has been created (but see below). And the
   message about having no boot loader shows hints about using /boot/vmlinux
   etc. which are not applicapble on prep.
 - prep partition is displayed as mountable, and the installer complains when
   it was choosen not to be mounted. In fact, it must NOT be mounted, so the
   installer confuses $USER and implies that it may need to be mounted as /boot
   or so. Call it a layer 8 problem, IMO it is missing documentation and
   useability bug.
 - the initrd (and so vmlinuz) images have been buggy. I needed to rebuild it
   with MODULES=dep in mkinitrd.conf as well as vmlinuz image (#290329)
 - default kernel command line not prepared for the initrd ram disk of d-i
   (needed to edit the kernel command line and add root=/dev/ram0 by hand)
 - the getty on ttyS0 has not been enabled in inittab (maybe because I
   have used the ssh-console-server for the final steps, but I still want to have a
   configured local console when I began to install from one, damnit)

i18n partially broken, strings cut on umlauts when using the serial console
(works via SSH though). I guess you set LANG=de_DE and LC_CTYPE=C which causes
that behaviour. Better would be using LC_CTYPE=C//translit (which would display
ASCII transliterations) or just allow UTF-8 since this is a UTF-8-enabled
console (urxvt & screen & UTF-8 locale).
OTOH the whole thing does not make sense. The boxes are drawn correctly, only
the strings are truncated.

If /boot is too small (8MB), the installer fails with a meaningless message
("look at Console 3 please". I cannot even reach that console since I am on a
serial one. And OTOH, this problem should have been detected before in the
partitioner by a plausibility check and appropriate warning).

Missing in documentation:

 - firmware upgrade requirement (see lupr howto)
 - pointer about the unsupported framebuffer console
 - the fact that one needs either to remove the unsupported video card or
   remove the second console=tty0 argument from the kernel command line
 - the requirement of adding root=/dev/ram0, the requirement of adding anything
   at all (it is really not obvious that the presented line with arguments
   can/must be edited)
 - about mkvmlinuz usage and how to copy the boot image to the magic partition
 - for non-standard installation methods (not just booting via El-Torrito):
   - know-how about the syntax of OpenFirmware's command line (or even how to invoke it, pressing 8)
   - the path and image name of the prep-vmlinuz.initrd image
 - a few times the installer just froze after language configuration (blue
   screen). Pressing the yellow reset button twice made it continue (I know,
   sounds strange but that is what happened, at least from my subjective view)
 
Things that did work just by luck or copy/paste operation:

the bot configuration of my root FS as root=/dev/sda3 (fortunately this
is the default in that kernel image, but in a slightly different
scenario, it would fail since there is no boot loader to pass the root=
setting).

Some log files attached.

Regards,
Eduard.
-- 
"The quiet ones are the ones who change the universe.
 The loud ones only take the credit."
                                                               L.M. ItB

Attachment: partman.gz
Description: Binary data

Attachment: status.gz
Description: Binary data

Attachment: syslog.gz
Description: Binary data

Attachment: hardware-summary.gz
Description: Binary data

Attachment: messages.gz
Description: Binary data


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