Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jens Oeser <oeser@darmstadt.gmd.de>
To: linux@cthulhu.engr.sgi.com
Subject: Re: Booting linux does not work fine.
Date: Fri, 27 Aug 1999 11:59:43 +0200	[thread overview]
Message-ID: <37C6618F.8FFA2D80@darmstadt.gmd.de> (raw)
In-Reply-To: 37C4F2A9.543E0E98@darmstadt.gmd.de

Hi!

I got it working now, with vmlinux-r4400 ... other kernels are booting
but kflushd messes up my screen. The kflush always want to tell me when
he flushes something ... i really would have the sound kernel, but i
cannot use it because of kflushd trouble, anyone expierences with that?
I modified syslog.conf, but it doesn't work. Seems to be direct from the
kernel. I try i selfcompiled kernel today, maybe this helps me.
Another problem, If i try to add a swap partition, it only get's a size
of 20mb with fx, if i resize, the partition is not longer recognized as
swap, and the hardhat install program does not let me make it to a swap.
Is there i way to get it managed, without using linux tools for that?

regards.
Jens Oeser.









Jens Oeser wrote:
> 
> Hi!
> 
> I tried to install linux to my sgi indy yesterday, kernel starts up
> normally and hangs after "Freeing unused kernel memory 44k freed". Then
> i only can reboot the machine. I really don't find the thing causing
> that, maybe someone can give me an advise to get linux to work fine.
> Hardware:
> ip22 175mhz
> 64/128mb ram (Depends which machine)
> 2gb hdd (2nd machine 2x1GB).
> hinv says that i have a indy 24bit ... does this card is supported? I
> think so, because kernel messages are printed on the screen, so entire
> linux should do so.
> So how can i get linux working?
> 
> regards.
> Jens Oeser

      parent reply	other threads:[~1999-08-27 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-26  7:54 Booting linux does not work fine Jens Oeser
1999-08-26 13:46 ` ANgus
1999-08-26 22:22 ` Cory Jon Hollingsworth
1999-08-27  9:59 ` Jens Oeser [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=37C6618F.8FFA2D80@darmstadt.gmd.de \
    --to=oeser@darmstadt.gmd.de \
    --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