Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Emmanuel Mogenet <mgix@nothingreal.com>
To: linux@cthulhu.engr.sgi.com
Subject: Step by step of my experience
Date: Wed, 22 Oct 1997 15:26:58 -0700	[thread overview]
Message-ID: <344E7DB2.167E@nothingreal.com> (raw)

Hi guys,

I've tried to boot Linux on my old clunky R5k this morning, and
I thought I'd share the step by step with the list.

Basically, I've tried to boot off an EFS filesystem (d4), and here's
how I went about it:

1. /d4 is my third scsi disk, with EFS (/dev/sdc under linux)

2. My irix kernel is in /unix on first disk (/dev/sda), which is XFS.
   Which is OK, since only the kernel is on XFS and the loader can
   handle it.

3. mkdir /d4/lsgi

4. Put ftp://ftp.linux.sgi.com/pub/test/vmlinux-970916-efs.gz in
   /d4/lsgi

5. Put ftp://ftp.linux.sgi.com:/pub/mips-linux/root-be-0.00.cpio.gz in
   /d4/lsgi

6. Extract root-be-0.00.cpio.gz in /d4:
        cd /d4
        gzip -dc lsgi/root-be-0.00.cpio.gz | cpio -icvd

7. Install kernel on /
        cd /d4/lsgi
        gzip -d vmlinux-970916-efs.gz
        cp vmlinux-970916-efs /vmlinux

8. Reboot, go to maintenance mode, launch sash and type:
        scsi(0)disk(1)rdisk(0)partition(0)/vmlinux root=/dev/sdc1

7. The kernel booted, said a great many (good) things and froze with the
   following messages:
        VFS: mounted root (efs filesystem) readonly
        EFS: inode 0x30301 has >EFS_MAX_EXTENTS (43)
        EFS: <6> attempt to access beyond end of device
        08:21 rw=0 want=1190802192, limit=4191574

Conclusion: Wait for Ralf to finish the EFS driver !
This is the exact bug he was talking about.

Also: I read a few mails about typing, under sash, the following:
        boot /vmlinux root=/dev/sdc1

Well, it doesn't work.
First, the syntax for the sash boot command in my PROM is: boot -f
<file> -n <args>
Second, when I did boot -f /vmlinux -n root=/dev/sdc1, it just loaded
the kernel,
but didn't jump into it. It just told me: the entry address is <some hex
number>.

When I did go <some hex number>, it ran linux, but tried to boot off 
tftp.
Obviously it ignored the args.

I'm just wondering: is there many different versions of sash out there ?

I'm off trying to boot off tftpd.
I'll keep the list posted.

Ciao,

        - Mgix


-- 

________________________________________________________________________________
Emmanuel Mogenet <mgix@nothingreal.com>                       PGP Key on
Request

             reply	other threads:[~1997-10-22 22:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-22 22:26 Emmanuel Mogenet [this message]
1997-10-23  0:10 ` Step by step of my experience Ariel Faigon
1997-10-23  0:10   ` Ariel Faigon
1997-10-23  6:24   ` Mike Shaver
1997-10-29 18:14   ` Alan Cox
1997-10-29 21:50     ` Miguel de Icaza
1997-10-29 22:42       ` Alan Cox
1997-10-29 22:42         ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
1997-10-24 17:07 Mike Hill
1997-10-24 21:12 ` Ralf Baechle
1997-10-24 21:12   ` Ralf Baechle

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=344E7DB2.167E@nothingreal.com \
    --to=mgix@nothingreal.com \
    --cc=linux@cthulhu.engr.sgi.com \
    /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