Linux PARISC architecture development
 help / color / mirror / Atom feed
From: willy@thepuffingroup.com
To: 5116@telia.com
Cc: Paul Bame <bame@endor.fc.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] PALO and ramdisk micro-howto
Date: Wed, 22 Mar 2000 22:02:29 -0500	[thread overview]
Message-ID: <20000322220229.D10226@thepuffingroup.com> (raw)
In-Reply-To: <200003222233.XAA11675@zaphod.halden.lillfab.se>; from 5116@telia.com on Wed, Mar 22, 2000 at 11:33:21PM +0100

On Wed, Mar 22, 2000 at 11:33:21PM +0100, 5116@telia.com wrote:
> I tried this with my 715/50 and current CVS kernel and palo as of today.

> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> SCSI clock: 50000000
> Lasi Scsi (53c700) found at 0xf0825100
> scsi-ncr53c7xx : unsupported SCSI chip 700

hehehe... someone's going to have to fix that someday...

> scsi : 0 hosts.
> scsi : detected total.
> IP-Config: No network devices available.
> RAMDISK: ext2 filesystem found at block 0
> RAMDISK: Loading 600 blocks [1 disk] into ram disk... done. 
> kernel BUG at block_dev.c:411! 
> kernel BUG at block_dev.c:411!

those two are OK, they should disappear when we go to the latest Linus
tree.  What's happening at this point is that it's switching to serial
console.  You should be able to stay with PDC console for the time being,
though you can't use it as an input device, only output.  In the fullness
of time, we'll have a proper graphics console.  Stay tuned :-)

  reply	other threads:[~2000-03-23  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-21 17:44 [parisc-linux] PALO and ramdisk micro-howto Paul Bame
2000-03-21 21:40 ` Paul Bame
2000-03-22 22:33 ` 5116
2000-03-23  3:02   ` willy [this message]
2000-03-23 19:05     ` [parisc-linux] Eth0 trouble Thierry SIMONNET

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=20000322220229.D10226@thepuffingroup.com \
    --to=willy@thepuffingroup.com \
    --cc=5116@telia.com \
    --cc=bame@endor.fc.hp.com \
    --cc=parisc-linux@thepuffingroup.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