linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jeff Rugen" <jprugen@earthlink.net>
To: "Tom Rini" <trini@kernel.crashing.org>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: RTC and SCSI for PowerStack/2.4.6 Kernel
Date: Mon, 9 Jul 2001 07:38:58 -0700	[thread overview]
Message-ID: <000e01c10884$e4201e60$0401a8c0@trex> (raw)
In-Reply-To: 20010708120006.D825@opus.bloom.county


> That looks like an OK version of util-linux.  Try compiling CONFIG_RTC_PPC
in
> and not CONFIG_RTC.

That fixed /sbin/hwclock from hanging, thanks.

>
> > Second, I am getting SCSI timeouts when running 2.4.6.  I don't know
enough
> > about SCSI, but the log to the console is the following:
>
> Consistant?  I saw this once when booting off the HD but not the next
time.
> Then I went back to NFS rooted.

I've booted 2.4.6 successfully 4 times so far -- 2 times it crashed with
SCSI timeouts, and 2 times it hung for unknown reasons (with no oops output
or anything).  The second time it might have been framebuffer or network
related (I'd installed clgenfb, changed video modes, and then did 'dir' in
an ftp session to a site with a long directory listing twice -- the second
time it hung).

Did anything change in regards to oops output on crashes since 2.2.x?  I'm
not suprised that the kernel would crash/hang without producing any, but I
thought I'd ask to make sure.

> > Which leads me to believe that I at least have the correct SCSI driver
build
> > (NCR53C8XX, as the revision of 0x2 is less than the 16 that
Configure.help
> > seems to indicate).  Should I instead be using the 53c7,8xx driver?  Or
the
> > sym53c8xx?
>
> sym53c8xx will tell you unsupported chip.  I don't know if 53c7,8xx will
work
> but give it a shot, please. :)

53c7,8xx compiled after fixing two lines, but didn't work.  I emailed the
(old) driver supporter with the information (some of the output indicated to
email him, so I did).  I did try with the 10MHz support, and plan to try it
without, but haven't had the opportunity yet.

Jeff Rugen


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-07-09 14:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-08  7:49 RTC and SCSI for PowerStack/2.4.6 Kernel Jeff Rugen
2001-07-08 19:00 ` Tom Rini
2001-07-09 14:38   ` Jeff Rugen [this message]
2001-07-09 14:47     ` Benjamin Herrenschmidt
2001-07-09 14:57     ` Tom Rini
2001-07-09 15:08       ` Geert Uytterhoeven
2001-07-09 15:17         ` Tom Rini
2001-07-09 15:25         ` Jeff Garzik
2001-07-09 16:20       ` Jeff Rugen
2001-07-09 18:48         ` Olaf Hering
2001-07-09 20:37           ` Jeff Rugen
2001-07-09 20:54             ` Olaf Hering
2001-12-13 16:13 ` Tom Rini

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='000e01c10884$e4201e60$0401a8c0@trex' \
    --to=jprugen@earthlink.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).