From: Jeff Coffin <jcoffin@sv.usweb.com>
To: linux@cthulhu.engr.sgi.com
Subject: Re: Partial Success Report
Date: 21 Oct 1998 17:56:11 -0700 [thread overview]
Message-ID: <m3vhldwh1w.fsf@lil.sv.usweb.com> (raw)
Fogot to CC the list on this....
Thomas Bogendoerfer <tsbogend@alpha.franken.de> writes:
> Could you please lookup major and minor number of /dev/console on
> your root filesystem ? It should be major 5 and minor 2 to work
> properly with the serial console.
I fixed it, do I need to change systty too perhps?:
[root@lil dev]# ls -l
total 0
crw------- 1 root disk 5, 2 Oct 21 13:25 console
crw------- 1 root disk 4, 0 May 11 08:48 console.dist
crw-rw-r-- 1 root root 1, 3 May 11 08:48 null
brw-r----- 1 root disk 1, 1 May 11 08:48 ram
crw------- 1 root disk 4, 0 May 11 08:48 systty
crw------- 1 root root 4, 1 May 11 08:48 tty1
crw------- 1 root root 4, 2 May 11 08:48 tty2
crw------- 1 root root 4, 3 May 11 08:48 tty3
crw------- 1 root root 4, 4 May 11 08:48 tty4
crw------- 1 root root 4, 5 May 11 08:48 tty5
> please try to boot these kernels with bootp()/vmlinux console=ttyS0 (also
> try ttyS1) and a terminal hooked up to one of the serial ports (in .116
> ttyS0 is port 2 and ttyS1 is port 1; I've changed that in .121, but I'm not
> sure if this fix is already in the precompiled kernel). It's possible,
> that I've messed up the card detection so, that it panics, when there is
> no newport installed.
Nope, didn't work. The 116 kernel makes the power light blink red to
green ad infinitum and the 121 version appears to load, but the
console is elsewhere. I'm using port 1 for the serial connection
(it's setup thusly in the PROM)
The default kernel still boots OK and appears to mount the nfsroot:
Looking up port of RPC 100003/2 on 192.168.0.20
Looking up port of RPC 100005/1 on 192.168.0.20
VFS: Mounted root (nfs filesystem).
Adv: done running setup()
but then nothing....
BTW, I'm doing the whole thing from a serial console (minicom). The
gfx card doesn't work from IRIX either. One of these days I'll
replace it, but it's not real high on my list of things to buy for
$200+.
--jeff
next reply other threads:[~1998-10-22 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-22 0:56 Jeff Coffin [this message]
1998-10-22 19:06 ` Partial Success Report Thomas Bogendoerfer
-- strict thread matches above, loose matches on Subject: below --
1998-10-15 20:50 Jeff Coffin
1998-10-15 22:17 ` Ulf Carlsson
1998-10-15 23:46 ` Jeff Coffin
1998-10-16 19:46 ` Ulf Carlsson
1998-10-17 2:01 ` ralf
1998-10-18 0:09 ` Ulf Carlsson
1998-10-19 0:15 ` William J. Earl
1998-10-19 0:13 ` William J. Earl
1998-10-17 9:16 ` Thomas Bogendoerfer
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=m3vhldwh1w.fsf@lil.sv.usweb.com \
--to=jcoffin@sv.usweb.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