public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Finley <afinley@gis.umn.edu>
To: gentoo-mips@lists.gentoo.org
Subject: [gentoo-mips] R5000 o2 X11 and kde?
Date: 01 Dec 2004 08:32:30 -0600	[thread overview]
Message-ID: <1101911550.18404.10.camel@populus> (raw)
In-Reply-To: <41ABB203.6080305@gentoo.org>

Hi Steve,
I went back through and double checked everything, rebooted, and
resetenv, and presto, arcboot booted properly.  Now we're cooking!

Then tried to emerge X-org, which compiled fine but could not build a
config file.  I looked for some documentation on the gentoo mips site
but didn't see much (and elsewhere).  Is it possible to get X and
eventually kde running?  Thanks again for your help.


On Mon, 2004-11-29 at 17:34, Stephen P. Becker wrote:
> Andrew Finley wrote:
> > Your Good Steve,
> > I did forget to mount boot the last time.  And got it to boot, part
> > way.  I got a "kernel panic - not syncing: No init found. Try passing
> > init= option to the kernel" 
> > 
> > Sorry to keep bugging you, but I'm not sure where to find help (google
> > only works so far) :-)
> > 
> > andy
> 
> Well, that's interesting.  It seems that both the kernel looks at 
> OSLoadPartition from the prom when being loaded via arcboot.  Arcboot 
> uses OSLoadPartition to determine where the kernel and arcboot.conf are 
> stored, and it uses the SGI naming scheme to do so (eg the 
> pci(0)scsi(0)disk(1)rdisk(0)partition(X) bit).  The kernel uses 
> OSLoadPartition to determine the root device, and apparently the 
> append="root=/dev/sda3" from arcboot.conf isn't getting passed, or is 
> being overridden.  Try changing OSLoadPartition to /dev/sda3 from the 
> prom.  Arcboot will spit an error that you should change it to something 
> else, but then will scan the other partitions for /etc/arcboot.conf and 
> should auto-detect what partition it really needs and then boot normally.
> 
> Steve
> 
> 
> 
> --
> gentoo-mips@gentoo.org mailing list
> 
> 

--
gentoo-mips@gentoo.org mailing list


  reply	other threads:[~2004-12-01 14:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 21:35 [gentoo-mips] PANIC: Unexpected exception at boot o2 R5000 Andrew Finley
2004-11-25  1:08 ` Kumba
2004-11-25  1:56   ` Andrew Finley
2004-11-25  2:02     ` Stephen P. Becker
2004-11-28 16:52   ` Andrew Finley
2004-11-28 21:05     ` Kumba
2004-11-29 21:30       ` [gentoo-mips] arcboot problem R5000 o2 Andrew Finley
2004-11-29 21:46         ` Stephen P. Becker
2004-11-29 22:32           ` Andrew Finley
2004-11-29 22:38             ` Stephen P. Becker
2004-11-29 23:07               ` Andrew Finley
2004-11-29 23:34                 ` Stephen P. Becker
2004-12-01 14:32                   ` Andrew Finley [this message]
2004-12-01 14:49                     ` [gentoo-mips] R5000 o2 X11 and kde? Christian Hartmann
2004-12-01 14:57                     ` Stephen P. Becker
2004-12-02 20:56                       ` [gentoo-mips] R5000 o2 X11 and kde Andrew Finley
2004-12-02 22:43                         ` Stephen P. Becker
     [not found]                           ` <1102433859.14535.3.camel@populus>
2004-12-07 16:03                             ` [gentoo-mips] Re: R5000 o2, kernel Stephen P. Becker
2004-12-07 22:47                               ` Andrew Finley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1101911550.18404.10.camel@populus \
    --to=afinley@gis.umn.edu \
    --cc=gentoo-mips@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox