Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: Oddities with CVS Kernels, Memory on Indigo2
Date: Mon, 14 Apr 2003 11:53:47 -0400	[thread overview]
Message-ID: <3E9AD98B.90808@gentoo.org> (raw)
In-Reply-To: <20030414140717.GA805@simek>

Ladislav Michl wrote:
> I'd say you've tried cvs kernel at the times when support for R4400
> caches was broken. I put kernel I'm currently running at
> http://www.linux-mips.org/~ladis/vmlinux.gz (gunzip it :)), as you can
> see from dmesg at the end of this mail CPU used in your machine is the
> same. If kernel I provided doesn't boot for you I'd like to ask you for
> help with debugging (kernel was build from cvs updated at 8:30 CEST)
> 

Wow, this booted.  Several people I talked to thought it was originally 
a serial console issue.  Judging by the several times I've chosen to 
build a kernel, it seems R4400 cache gets broken quite often.  I'll run 
a cvs sync now and try to build my own kernel, since this appears to be 
built from recent code.  Your kernel lacked a few things gentoo requires 
to boot, but it at least proves I'm not going insane over here.



> This is known bug, but unfortunately I have not enough RAM to meet it...

A known bug?  Interesting.  I mentioned it many moons ago in #mipslinux, 
and Ralf seemed curious about it, but he said he looked in the kernel 
where the memory was detected and said he didn't see anything wrong 
there.  Anything I can do to help look into this bug and possibly fix?


>>parport0: PC-style at 0x278 [PCSPP,TRISTATE,EPP]
> 
>             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> it can't work ;)

It worked fine for me with printing :)

[root@angband root]# echo "Hello World" > /dev/lp0
[root@angband root]# echo "Wow, It works" > /dev/lp0
[root@angband root]# echo "Totally Cool" > /dev/lp0

^---  All printed out on paper, although scratchy.  I need new ink 
cartridges.  Canon BJC-620

Mind you, that's an ISA Parallel Port card I dropped in.  I noticed the 
SGI's parallel port never worked, so I dug up a spare and tried it.


--Kumba

  reply	other threads:[~2003-04-14 15:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13  5:13 Oddities with CVS Kernels, Memory on Indigo2 Kumba
2003-04-14 14:07 ` Ladislav Michl
2003-04-14 15:53   ` Kumba [this message]
2003-04-14 16:00     ` Marc Zyngier
2003-04-14 16:16       ` Kumba
2003-04-14 16:27         ` Marc Zyngier
2003-04-14 16:24       ` Kumba
2003-04-14 16:35         ` Ladislav Michl
2003-04-14 16:58           ` Kumba
2003-04-15  8:35   ` Kumba
2003-04-15  8:50     ` Ladislav Michl
2003-04-15  9:02       ` Kumba

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=3E9AD98B.90808@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.org \
    /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