From: Scott Sams <sbsams@eos.ncsu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: AWACS Bug
Date: Mon, 24 May 1999 18:00:36 -0400 [thread overview]
Message-ID: <3749CC04.146B318D@eos.ncsu.edu> (raw)
Paul Mackerras <paulus@cs.anu.edu.au> wrote:
> What's happening is I think the same as what happens on the iMac: when
> you run the BootX app to boot linux, and it asks macos to shut down,
> macos shuts down the awacs, in such a fashion that the only thing that
> will start it up again is a hard reset. :-(
I believe the same thing has happened on my box, although a hardware
reset has yet to fix the problem! :-<
Sound does not come out of either the internal speaker, or the line out
jack. Playing a .wav or a CD produces no sound. MacOS will not play any
sounds too. I have tried everything from hard resets to power cycling to
zapping the PRAM 3 times, and nothing has brought my sound back. Do any
of you hardware gurus out there know if it is possible to manually reset
the AWACS chip? Does this mean I fried my AWACS chip? How could I
replace it if necessary? Please help.
Thanks,
Scott Sams
--
____ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Scott Sams
(____ _ _-|-|- sbsams@eos.ncsu.edu
_____)(__(_)| | http://www.catt.ncsu.edu/~sbsams
~~~~~~~~~~~~~~~~
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-05-24 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-24 22:00 Scott Sams [this message]
1999-05-25 10:42 ` AWACS Bug Benjamin Herrenschmidt
[not found] <Pine.GSO.4.05.9905251646130.14882-100000@mail.wesleyan.edu>
1999-05-27 4:42 ` Scott Sams
1999-05-27 5:19 ` Jason Y. Sproul
-- strict thread matches above, loose matches on Subject: below --
1999-01-28 19:03 Trevor Woerner
1999-01-28 14:01 Russell Hires
1999-02-02 4:53 ` Paul Mackerras
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=3749CC04.146B318D@eos.ncsu.edu \
--to=sbsams@eos.ncsu.edu \
--cc=linuxppc-dev@lists.linuxppc.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).