linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Crusman" <Crusman@wanadoo.fr>
To: <paubert@iram.es>
Cc: "ppc_mailing" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: -= MVME 2300 =-
Date: Thu, 13 Jul 2000 22:03:00 +0200	[thread overview]
Message-ID: <002901bfed05$5b73d340$29e58aa4@crusman> (raw)


>The configurations I have are for 2600 with a PMC graphics board, remove
>CONFIG_VT from the setup and it will use a serial console.
>
>BTW use PrePboot for these boards (CONFIG_PREPBOOT) since it gives a nicer
>PCI layout to access the VMEbus...
>
>Please use the patches mvme2600.*.bz2...

I have tested the patches but the new kernel don't see the scsi device...so
I can't try it anyway !


>My systems work with an SCSI disk (the basic 2600 NCR53c825).
>Did you try to directly boot one of the images I have on my ftp site ?
>
>(If it works, you've got a configuration problem.)
>
> Gabriel

Yes, I have tested your kernel, but there is a message ( PC keyb error... or
something like this) wich lock the kernel during the boot ! It's probably
due to the Virtual Terminal support in the kernel !
I always use the "console=ttyS0,9600" kernel option.

In short :

- I can't use your kernel because of the PC_key error !
- I can't patch & build a new kernel because this new kernel don't see my
SCSI PMC !

What can I do ?

Lionel

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-07-13 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-13 20:03 Crusman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-12 17:00 -= MVME 2300 =- Lionel TAILLURAT
2000-07-12 18:59 ` Ben Sapp
2000-07-13  7:15 ` Gabriel Paubert

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='002901bfed05$5b73d340$29e58aa4@crusman' \
    --to=crusman@wanadoo.fr \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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;
as well as URLs for NNTP newsgroup(s).