Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
To: linux@cthulu.engr.sgi.com
Subject: success/ quirks.
Date: Sat, 8 May 1999 07:57:43 -0400 (EDT)	[thread overview]
Message-ID: <199905081157.HAA04442@sgi.com> (raw)


Hi guys,


just a little success / quirk report.  I got my hands on a 24 bit
R4600 Indy when my university ditched them all (they switched to Sun
machines), and I now use it as as very luxurious X-terminal to my
lowly linux PC.  After some tweaking I managed to boot Linux on the
machine as well, and installed it on the 2nd HD.

I have some remarks/bugreports:

  * the size of /proc/kcore was ludicrous for a 32 MB machine,

  -r--r--r--   1 root     root            0 May  6 23:24 ioports
  -r--------   1 root     root     167354368 May  6 23:24 kcore
  -r--------   1 root     root            0 May  6 23:22 kmsg

  * I  couldn't get g++ working.  The linker gave up after saying:

  /usr/lib/libstdc++.so: undefined reference to `__unwind_function'
  /usr/lib/libstdc++.so: undefined reference to
  `__find_first_exception_table_match'
  /usr/lib/libstdc++.so: undefined reference to
  `__register_exceptions'
collect2: ld returned 1 exit status

This was with Hard hat (snatched from a RH mirror), and
vmlinux-indy-2.2.1-990329 kernel.  I can send you a bootlog as well.

Finally, what is the status of Linux/Indy Xserver?  (I know I should
contribute instead of asking, but hey, I'm spending lots of time on
free s/w already.)

In any case, keep up the good work.  Blue computers are so cool!



-- 

Han-Wen Nienhuys, hanwen@cs.uu.nl ** GNU LilyPond - The Music Typesetter 
      http://www.cs.uu.nl/people/hanwen/lilypond/index.html 

             reply	other threads:[~1999-05-08 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-08 11:57 Han-Wen Nienhuys [this message]
     [not found] ` <19990508141838.A27219@thepuffingroup.com>
1999-05-10  8:50   ` success/ quirks Han-Wen Nienhuys

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=199905081157.HAA04442@sgi.com \
    --to=hanwen@cs.uu.nl \
    --cc=linux@cthulu.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