From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.62)
(envelope-from <gentoo-mips+bounces-232-garchives=archives.gentoo.org@gentoo.org>)
id 1H9OIS-0007i5-By
for garchives@archives.gentoo.org; Tue, 23 Jan 2007 16:14:57 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0NEOoAf002668;
Tue, 23 Jan 2007 14:24:50 GMT
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185])
by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id l0NEOjc6002563
for <gentoo-mips@lists.gentoo.org>; Tue, 23 Jan 2007 14:24:48 GMT
Received: by nf-out-0910.google.com with SMTP id c31so469605nfb
for <gentoo-mips@lists.gentoo.org>; Tue, 23 Jan 2007 06:24:42 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
b=ZZHH21v5TADH6c30/+XQ5l0ZstFE+zHWaBqzGM9u60hkjtRNX1hEGjaKxYFZa/pGwljm7Vx1FOmktjYG1eaDoZmtgX2nRqxVlptGva8bgjTXlwwtcLvnQuY9f5mKi14uMeTAb6WSrIbrE6/bTj+aQbtYXmPx96u6CHtSRKJqAJg=
Received: by 10.48.217.11 with SMTP id p11mr1109392nfg.1169562282444;
Tue, 23 Jan 2007 06:24:42 -0800 (PST)
Received: by 10.49.67.16 with HTTP; Tue, 23 Jan 2007 06:24:41 -0800 (PST)
Message-ID: <855e88d00701230624q2c525093gdc0ed5c2826739cf@mail.gmail.com>
Date: Tue, 23 Jan 2007 09:24:41 -0500
From: "Mike Martin" <mikemartin@linux.ca>
Sender: sydneymartin@gmail.com
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Question - Kumba LiveCD RC6
In-Reply-To: <45B56F9E.2080606@gentoo.org>
Precedence: bulk
List-Post: <mailto:gentoo-mips@lists.gentoo.org>
List-Help: <mailto:gentoo-mips+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-mips+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-mips+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-mips.gentoo.org>
X-BeenThere: gentoo-mips@gentoo.org
Reply-to: gentoo-mips@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_135333_28294455.1169562281919"
References: <Pine.SGI.4.62.0701181319170.2314@morpheus.tetracon-eng.net>
<45B4C1D5.2040905@gentoo.org>
<855e88d00701220612h670dbb1dud376b605d44aebc5@mail.gmail.com>
<45B56F9E.2080606@gentoo.org>
X-Google-Sender-Auth: 152c1a6876a4a42c
X-Archives-Salt: d4d387cb-0c58-4157-be69-618ecfe42ce9
X-Archives-Hash: 22d74c215acb7516097c1cd76f227843
------=_Part_135333_28294455.1169562281919
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Thanks for your help. I will try another burn. I'm using cdrecord and am
using (I believe) good media. What command parameters for cdrecord would you
recommend?
For fun I tried booting with a different external CD-ROM drive ... with
identical results.
I will also try the disk out on a R4600 Indy.
Thanks for your hard work.
MikeMartin
On 1/22/07, Kumba <kumba@gentoo.org> wrote:
>
> Mike Martin wrote:
> > I recently downloaded and attempted to boot an Octane with this disk. It
> > died mounting the root partition:
> >
> > mount: Mounting /newroot/dev/loop0 on /newroot/mnt/livecd failed:
> > Invalid argument
> >
> > Not sure what happened. I assume I burnt the disk correctly else it
> > wouldn't have made it that far. Any suggestions?
> >
> > MikeM
>
>
> It's really hard to say. I tested it on all of my systems before
> uploading, and
> with the Octane, this means an external drive (funny enough, an O2 CD
> drive
> jammed into a Sun 411 case). And that booted fine on both my Octane and
> Indy.
>
> "Invalid Argument" from mount could mean a wide array of things (yay for
> Unix's
> legacy of non-descriptive, ambiguous errors). The process that occurs on
> an SGI
> bootcd for us is a rather complex one:
>
> 1. arcload boots from the DVh partition of the CD
> (yes, these CDs have partitions)
> 2. arcload finds and boots a kernel
> 3. kernel loads, and executes /init in an embedded initramfs file linked
> into the kernel
> 4. /init does some prep work, and launches `getdvhoff` to scan the CD
> for the offset of the next partition (where / lives), and passes a
> number representing this offset back to `losetup`.
> 5. losetup uses this number to "point" /dev/loop0 at this offset, which
> effectively makes /dev/loop0 a block device with data on it.
> 6. mount tries to mount /dev/loop0 and pivot_root into the real Gentoo
> filesystem.
>
>
> Quite likely, step #5 might've failed somewheres along the line. The
> offset has
> to be exact to the bit, so maybe something got whacked in the burn and the
> detected offset is invalid. Hard to say without more information. Thus,
> when
> it got to step #6, boom.
>
> I'd try re-burning the disk at a slower speed, use only CD-R's of decent
> quality
> (TDK, Memorex, Sony, Ricoh/Ritek, etc,.. brands), and use cdrecord (or
> whatever
> license-unencumbered version is out there. stupid license wars). A few
> people
> reported getting it to work with a windows burn tool, but we have little
> data on
> that, thus why cdrecord is the suggested tool.
>
> Mostly, you were able to read the kernel into memory, which is ~8MB. It's
> possible the disc you burned was good enough to get those 8MB off to boot
> the
> kernel, but when it went looking for the meat, it got denied and pwned.
>
>
>
> --Kumba
>
> --
> Gentoo/MIPS Team Lead
>
> "Such is oft the course of deeds that move the wheels of the world: small
> hands
> do them because they must, while the eyes of the great are
> elsewhere." --Elrond
> --
> gentoo-mips@gentoo.org mailing list
>
>
------=_Part_135333_28294455.1169562281919
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Thanks for your help. I will try another burn. I'm using cdrecord and am using (I believe) good media. What command parameters for cdrecord would you recommend?<br><br>For fun I tried booting with a different external CD-ROM drive ... with identical results.
<br><br>I will also try the disk out on a R4600 Indy.<br><br>Thanks for your hard work.<br>MikeMartin<br><br><div><span class="gmail_quote">On 1/22/07, <b class="gmail_sendername">Kumba</b> <<a href="mailto:kumba@gentoo.org">
kumba@gentoo.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Mike Martin wrote:<br>> I recently downloaded and attempted to boot an Octane with this disk. It
<br>> died mounting the root partition:<br>><br>> mount: Mounting /newroot/dev/loop0 on /newroot/mnt/livecd failed:<br>> Invalid argument<br>><br>> Not sure what happened. I assume I burnt the disk correctly else it
<br>> wouldn't have made it that far. Any suggestions?<br>><br>> MikeM<br><br><br>It's really hard to say. I tested it on all of my systems before uploading, and<br> with the Octane, this means an external drive (funny enough, an O2 CD drive
<br>jammed into a Sun 411 case). And that booted fine on both my Octane and Indy.<br><br>"Invalid Argument" from mount could mean a wide array of things (yay for Unix's<br>legacy of non-descriptive, ambiguous errors). The process that occurs on an SGI
<br>bootcd for us is a rather complex one:<br><br>1. arcload boots from the DVh partition of the CD<br> (yes, these CDs have partitions)<br>2. arcload finds and boots a kernel<br>3. kernel loads, and executes /init in an embedded initramfs file linked
<br> into the kernel<br>4. /init does some prep work, and launches `getdvhoff` to scan the CD<br> for the offset of the next partition (where / lives), and passes a<br> number representing this offset back to `losetup`.
<br>5. losetup uses this number to "point" /dev/loop0 at this offset, which<br> effectively makes /dev/loop0 a block device with data on it.<br>6. mount tries to mount /dev/loop0 and pivot_root into the real Gentoo
<br> filesystem.<br><br><br>Quite likely, step #5 might've failed somewheres along the line. The offset has<br>to be exact to the bit, so maybe something got whacked in the burn and the<br>detected offset is invalid. Hard to say without more information. Thus, when
<br>it got to step #6, boom.<br><br>I'd try re-burning the disk at a slower speed, use only CD-R's of decent quality<br>(TDK, Memorex, Sony, Ricoh/Ritek, etc,.. brands), and use cdrecord (or whatever<br>license-unencumbered version is out there. stupid license wars). A few people
<br>reported getting it to work with a windows burn tool, but we have little data on<br>that, thus why cdrecord is the suggested tool.<br><br>Mostly, you were able to read the kernel into memory, which is ~8MB. It's<br>
possible the disc you burned was good enough to get those 8MB off to boot the<br>kernel, but when it went looking for the meat, it got denied and pwned.<br><br><br><br>--Kumba<br><br>--<br>Gentoo/MIPS Team Lead<br><br>"Such is oft the course of deeds that move the wheels of the world: small hands
<br>do them because they must, while the eyes of the great are elsewhere." --Elrond<br>--<br><a href="mailto:gentoo-mips@gentoo.org">gentoo-mips@gentoo.org</a> mailing list<br><br></blockquote></div><br>
------=_Part_135333_28294455.1169562281919--
--
gentoo-mips@gentoo.org mailing list