From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Chris Chiapusio <chipper@llamas.net>
Cc: Alex deVries <adevries@engsoc.carleton.ca>, linux@cthulhu.engr.sgi.com
Subject: Re: Challange S question..
Date: Fri, 12 Feb 1999 00:29:15 +0100 [thread overview]
Message-ID: <19990212002915.A4561@alpha.franken.de> (raw)
In-Reply-To: <Pine.LNX.4.05.9902111059380.683-100000@chipsworld.llamas.net>; from Chris Chiapusio on Thu, Feb 11, 1999 at 11:05:23AM -0500
On Thu, Feb 11, 1999 at 11:05:23AM -0500, Chris Chiapusio wrote:
> where can i find info on what the kernel is doing at each stage of the
> boot process for a 'install' kernel like this so i can try to debug this
> without buggin you guys for each problem?
the kernel has already booted. The HardHat kernel isn't able to work
with a serial console, and in mine is /dev/ram missing.
> mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
> /dev/ram: Operation not supported by device while setting up superblock
> creating 100k of ramdisk space... done
> mounting /tmp from ramdisk... failed.
ok, I didn't include the ramdisk driver in the kernel. Please try:
ftp://ftp.linux.sgi.com/pub/linux/mips/test/vmlinux-indy-990212.gz
This kernel boots with the Rough Cut CD I have here.
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
next prev parent reply other threads:[~1999-02-11 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-10 21:34 Challange S question Chris Chiapusio
1999-02-10 21:58 ` Alex deVries
1999-02-10 23:25 ` Thomas Bogendoerfer
1999-02-11 16:05 ` Chris Chiapusio
1999-02-11 23:29 ` Thomas Bogendoerfer [this message]
1999-02-11 1:12 ` Richard Hartensveld
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=19990212002915.A4561@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=adevries@engsoc.carleton.ca \
--cc=chipper@llamas.net \
--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