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

Bug#226420: marked as done (install-doc: [MIPS] missing module/configuration information.)

Your message dated Thu, 13 Oct 2005 17:55:11 -0400
with message-id <20051013215511.GA30512@kitenet.net>
and subject line closing bugs in the old install-doc package
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 6 Jan 2004 16:21:57 +0000
Return-path: <cananian@lesser-magoo.csail.mit.edu>
Received: from catfish.lcs.mit.edu [] 
	by master.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1AVd7q-0001u1-00; Sun, 14 Dec 2003 14:46:02 -0600
Received: from localhost (localhost [])
	by catfish.lcs.mit.edu (8.12.10/8.12.8) with ESMTP id hBEKk12c007236
	for <submit@bugs.debian.org>; Sun, 14 Dec 2003 15:46:01 -0500 (EST)
Date: Sun, 14 Dec 2003 15:46:01 -0500 (EST)
From: "C. Scott Ananian" <cananian@lesser-magoo.csail.mit.edu>
X-Sender: cananian@catfish.lcs.mit.edu
Reply-To: "C. Scott Ananian" <cscott@cscott.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: install-doc: [MIPS] missing module/configuration information.
In-Reply-To: <E1AVOHF-000127-00@indy.dyndns.org>
Message-ID: <Pine.GSO.4.10.10312141544560.12158-100000@catfish.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: submit@bugs.debian.org
Status: RO
Content-Length: 3227
Lines: 87

Package: install-doc
Version: 3.0.23
Severity: normal

I just installed Debian/MIPS/stable on an Indy (then upgraded to
unstable, which was an adventure for another bug report).

It would be helpful if the installation manual mentioned in the
'modconf' section that 'hal2' (which uses 'soundconf') is the
module providing sound support on the SGI Indy.  You probably
also want to add users to the 'audio' group.

For X configuration, the driver to use on the Indy is 'newport'.
The best information on X-on-Indy (and Indigo2) is:

In the partitioning section, a sample disk partition would be
extremely useful.  For my system:
indy# fdisk /dev/sdb

Command (m for help): p

Disk /dev/sdb (SGI disk label): 66 heads, 62 sectors, 1008 cylinders
Units = cylinders of 4092 * 512 bytes

----- partitions -----
Pt#     Device  Info     Start       End   Sectors  Id  System
 1:  /dev/sdb1  boot         5       928   3779541  83  Linux native
 2:  /dev/sdb2  swap       929      1007    324735  82  Linux swap
 9:  /dev/sdb3               0         4     20460   0  SGI volhdr
11:  /dev/sdb4               0      1007   4124736   6  SGI volume
----- Bootinfo -----
Bootfile: /unix
----- Directory Entries -----
 0: linux      sector    4 size 2031824
 1: newlinux   sector 3973 size 2627527

Command (m for help): q


The information I needed (which the manual did not explain) were:
 a) partitions start at 1, despite the special 'volume header' 
    partitions at 9 and 11, and user partitions 'overlap' with
    9 and 11 in a way that's best shown by example above.
 b) It's not enough that the swap partition be named 'swap', it
    must also have type 82. [I was misled here by installing
    Debian/PowerPC immediately prior.]
 c) It doesn't matter that the 'Bootfile' parameter doesn't match the 
    name of the boot kernel.

I forget if the manual includes sufficient information on dvhtool, but
a sample invocation can't hurt if it's currently missing:
 indy# dvhtool -d /dev/sdb --unix-to-vh /boot/vmlinux-2.4.22-r4k-ip22 linux

Finally, I found the following information on the Indy's boot prom
 IRIX manual on the use of the PROM:
 Resetting a bad ethernet address in the PROM (caused by dead batteries, etc)

 Proper PROM boot options for linux:
In particular, for my case (booting off sdb1, scsi id 4; note that 
partition(8) corresponds to what fdisk called partition 9):
   setenv OSLoader linux
   setenv SystemPartition scsi(0)disk(4)rdisk(0)partition(8)
   setenv OSLoadPartition /dev/sdb1
   setenv OSLoadOptions ""
where OSLoadOptions contains the linux boot arguments, if any.

Hopefully this information will help future Debian/MIPS installers.

-- System Information:
Debian Release: testing/unstable
Architecture: mips
Kernel: Linux indy 2.4.22-r4k-ip22 #1 Mon Dec 1 20:24:13 CET 2003 mips

-- no debconf information

Received: (at 226420-done) by bugs.debian.org; 13 Oct 2005 21:55:12 +0000
>From joey@kitenet.net Thu Oct 13 14:55:12 2005
Return-path: <joey@kitenet.net>
Received: from kitenet.net [] (postfix)
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EQB2e-0002SS-00; Thu, 13 Oct 2005 14:55:12 -0700
Received: from dragon.kitenet.net (97-148-dial.xtn.net [])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
	by kitenet.net (Postfix) with ESMTP id EA1A917F72;
	Thu, 13 Oct 2005 21:55:09 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
	id CF6D5BFA45; Thu, 13 Oct 2005 17:55:11 -0400 (EDT)
Date: Thu, 13 Oct 2005 17:55:11 -0400
From: Joey Hess <joey@kitenet.net>
To: 137991-done@bugs.debian.org, 148509-done@bugs.debian.org,
	136698-done@bugs.debian.org, 140579-done@bugs.debian.org,
	142420-done@bugs.debian.org, 142881-done@bugs.debian.org,
	162710-done@bugs.debian.org, 176436-done@bugs.debian.org,
	182849-done@bugs.debian.org, 183490-done@bugs.debian.org,
	190003-done@bugs.debian.org, 220917-done@bugs.debian.org,
	226419-done@bugs.debian.org, 226420-done@bugs.debian.org,
	232998-done@bugs.debian.org, 238945-done@bugs.debian.org,
	286149-done@bugs.debian.org, 311325-done@bugs.debian.org,
	162143-done@bugs.debian.org, 159738-done@bugs.debian.org,
	169000-done@bugs.debian.org, 230137-done@bugs.debian.org,
	54003-done@bugs.debian.org, 129790-done@bugs.debian.org,
	147833-done@bugs.debian.org, 149420-done@bugs.debian.org,
	153691-done@bugs.debian.org, 161219-done@bugs.debian.org,
	168666-done@bugs.debian.org, 151176-done@bugs.debian.org
Subject: closing bugs in the old install-doc package
Message-ID: <20051013215511.GA30512@kitenet.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT"
Content-Disposition: inline
User-Agent: Mutt/1.5.10i
Delivered-To: 226420-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
X-CrossAssassin-Score: 24

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I'm closing these bugs because install-doc was the documentation for the
boot-floppies, which have reached end of life.

Current installation documentation is in the debian-installer-manual
package. If you think that your documentation issue is still not
adequately covered in the sarge installer manual, please reopen your bug
report and reassign it to debian-installer-manual.

see shy jo

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

Version: GnuPG v1.4.2 (GNU/Linux)



Reply to: