From: Helge Deller <deller@gmx.de>
To: James Waterhouse <james.waterhouse@videotron.ca>,
"parisc-linux@thepuffingroup.com"
<parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] booting on 712/60
Date: Thu, 19 Oct 2000 23:36:44 +0200 [thread overview]
Message-ID: <00101923364400.00717@P100> (raw)
In-Reply-To: <39EE1294.B447BF1D@videotron.ca>
Am Wednesday 18 October 2000 23:13 schrieb James Waterhouse:
> Hello Helge,
>
> Helge Deller wrote:
> >
> > Am Wednesday 18 October 2000 19:04 schrieb David Huggins-Daines:
> > > Grant Grundler <grundler@cup.hp.com> writes:
> > >
> > > > James Waterhouse wrote:
> > > > > Hello,
> > > > > I just compiled a ramdisk using mondays cvs src for everything.
I'm
> > > > > using the graphics console ramdisk file off the
puffin.external.hp.com
> > > > > (ramdisk20000530-sticon.tgz) to make the ramdisk. Now when I got to
boot
> > > > > it boots up until the point where the kernel says...
> > > >
> > > > iirc, ramdisk20000530-sticon.tgz uses a "kluge" /dev/tty major/minor
> > number.
> > > > I was reading old mail on this and the kluge to use a different
> > > > major/minor confused me. I was told this was no longer needed.
> > > > So you can use a newer/regular ramdisk.
> > >
> > > Ah! Actually that triggers my memory. You *must* append
> > > 'console=tty' to the kernel command line in order to use sticon (or
> > > probably fbcon too for that matter), or else it will default to
> > > serial.
> > >
> > > Usually the PALO makefile handles this for you though.
> >
> > Yeah, that was the problem ! I just found it too !
> > (And you need to enable getty in /etc/inittab).
>
> So what did you do to get it to work? You gave 'console=tty' to the
> kernel command line? Where is it that you give the command line? Do you
> have to modify a make file or what? Or are you just running palo/palo
> with args as given in the palo doc? Which ramdisk did you have to modify
> inittab in?
>
> Jame
>
Hi James,
Here are some hints:
1. I'm using no ramdisk, but the nfsroot-20001009.tgz, which you can get from
ftp://puffin.external.hp.com/pub/parisc/binaries/nfsroot/
This has the great advantage, that you can modify all configuration files
without the need to build a new kernel for every change - but you will need
to setup one of your machines as nfs-server and export that directory.
More than that, the ramdisks on puffin.external.hp.com are mostly outdated !
2. Take a look at the documention in palo/Makefile.
There I modified the NFSROOT = 10.10.10.2 to
NFSROOT = 192.168.100.100:/tftpboot/nfsroot with 192.168.100.100 as the
IP-address of my local nfs-server and the contents of nfsroot-20001009.tgz in
/tftpboot/nfsroot.
3. Follow the hints from Thomas Marteau (copied from his mail):
>cat /etc/inittab (! just the interesting thing!)
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
1:2345:respawn:/sbin/getty 38400 tty1
#2:23:respawn:/sbin/getty 38400 tty2
#3:23:respawn:/sbin/getty 38400 tty3
#4:23:respawn:/sbin/getty 38400 tty4
#5:23:respawn:/sbin/getty 38400 tty5
#6:23:respawn:/sbin/getty 38400 tty6
>cat /etc/securetty
# /etc/securetty: list of terminals on which root is allowed to login.
# See securetty(5) and login(1).
ttyS0
tty1
Helge.
prev parent reply other threads:[~2000-10-19 21:35 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
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 [this message]
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=00101923364400.00717@P100 \
--to=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