From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Martin Costabel <costabel@wanadoo.fr>,
Bastien Nocera <hadess@hadess.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: 2.4.8-p1 crash on startup (was Clock problem)
Date: Mon, 30 Jul 2001 17:44:59 +0100 [thread overview]
Message-ID: <20010730164850.104E02EFD8@apollo.valhalla.net> (raw)
> 2.4.8-pre1 boots if I don't let it find its modules. If it finds them,
> then something (probably dmasound_awacs) writes garbage into the
> framebuffer and produces a crash complete with zapped PRAM.
You need to apply the latest set of patches to 2.4.8p1 if you intend using
dmasound - AFAIK the BK version has a reference to an obsolete function.
Ben's tree has the latest patches (apart from the Power Computing stuff -
but that doesn't affect you).
If all those are 'true' as it were - can you confirm it is dmasound_pmac() ?
with the latest set of patches it is *supposed* to be much more friendly to
non-awacs chips (doesn't make them work, but is supposed to ignore stuff it
doesn't understand...).
If that's not the case I want to fix it...
It's also puzzling in a way because dmasound_pmac doesn't try to do DMA
unless you do SysBeep() or output a sound. Until then the only regs it
should touch are in mac-io.
----
2.4.8-p1 is fine on 9600/233, g3/beige & g4/500/sawtooth (but these all have
AWACS or Screamer). Haven't tied the Lombard yet (but don't expect any
difference really).
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-07-30 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 16:44 Iain Sandoe [this message]
2001-07-30 17:57 ` 2.4.8-p1 crash on startup (was Clock problem) Martin Costabel
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=20010730164850.104E02EFD8@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=costabel@wanadoo.fr \
--cc=hadess@hadess.net \
--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).