Linux PARISC architecture development
 help / color / mirror / Atom feed
From: David Huggins-Daines <dhd@linuxcare.com>
To: Helge Deller <deller@gmx.de>
Cc: James Waterhouse <james.waterhouse@videotron.ca>,
	"parisc-linux@thepuffingroup.com"
	<parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] booting on 712/60
Date: 18 Oct 2000 10:41:42 -0400	[thread overview]
Message-ID: <87aec22oux.fsf@linuxcare.com> (raw)
In-Reply-To: Helge Deller's message of "Wed, 18 Oct 2000 09:30:34 +0200"

Helge Deller <deller@gmx.de> writes:

> I'm seeing the same here. The kernel switches independend of your 
> kernel-settings (STI-Console - no STI-Console) to serial-console and just 
> puts some of it's error-messages to the STI-console. 
> If you don't have a nullmodem cable, you could try to ping/telnet your 
> parisc, to see if it's still alive.
> I currently don't know which change in CVS disallowed us to use just 
> STI-Console, but will try to figure out later today. 

Very strange, because it worked for me.  But perhaps I had a magical
combination of .config settings that eludes others.

Of course sticon and the keyboard driver are so broken that I have a
hard time imagining that anyone is actually using them for serious
work, so I don't feel a great urgency here.

I will look into it now if it's not already fixed.

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

  reply	other threads:[~2000-10-18 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-18  7:03 [parisc-linux] booting on 712/60 James Waterhouse
2000-10-18  7:30 ` Helge Deller
2000-10-18 14:41   ` David Huggins-Daines [this message]
2000-10-18 15:17     ` David Huggins-Daines
2000-10-18 16:54 ` Grant Grundler
2000-10-18 17:04   ` David Huggins-Daines
2000-10-18 18:22     ` Helge Deller
2000-10-18 21:13       ` James Waterhouse
2000-10-19 21:36         ` Helge Deller

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=87aec22oux.fsf@linuxcare.com \
    --to=dhd@linuxcare.com \
    --cc=deller@gmx.de \
    --cc=james.waterhouse@videotron.ca \
    --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