linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Gwyn Judd <b.judd@xtra.co.nz>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: X still locks up
Date: Sun, 09 Jul 2000 13:25:17 +0100	[thread overview]
Message-ID: <200007091225.NAA19777@hyperion.valhalla.net> (raw)


Sun, Jul 9, 2000 Gwyn Judd wrote:
> On Sun, Jul 09, 2000 at 01:58:42AM +0100, Iain Sandoe wrote:
>>
>> > On Sat, Jul 08, 2000 at 11:06:40PM +0100, Iain Sandoe wrote:
>> >> Three things:
>> >>
>> >> 1/ did you try the backported audio stuff I posted yesterday - there were
>> >> some issues that were resolved between 2.2.xx and 2.3/4.xx these should be
>> >> present in the backport.  It does work OK against 2.2.17pre10-ben1.
>> >
>> > Oh whoops can you send that to me or tell me where I can get it? I
>> > thought it was part of bens kernel.
>>
>> Well, I wish it might be one day - but it's quite new (yesterday) and it
>> will take a bit more testing before it's accepted.
>>
>> here's the URL:
>>
>> http://quimby.gnus.org/circus/dmasound_backport.patch.bz2
>>
>> (but there's no reference to it anywhere higher up so use something like
>> anarchie/interarchy get via http - or whatever).
>
> Okay I tried that one by applying the patch to the current stable kernel
> (2.2.17 I believe).

It was against 2.2.17pre7 (linuxcare linux-pmac-stable tree) - but tested
against Ben's pre10-ben1 as well rsync'ed as of yesterday.

>Once gnome started up I got an error message "No
> mixers found".

Are you using modules - or complied in?  Modules currently require a
different insertion thingy:

modprobe soundcore
modprobe dmasound_core
modprode dmasound_awacs

I asked Geert about this - will get back to you/list when this is resolved.

check you have action with cat /proc/modules and cat /dev/sndstat before
doing anything too exotic.

suggestion ;-) boot 'single' do the modprobes and a simple check before
going to init 5.

Also please remind me what machine you are on and whether you have any OSS
stuff enabled as well.

>When I tried to play an mp3 through xmms X locked up
> completely although I was able to change VT's, however I was unable to
> kill X or reboot properly. Oh well at least fsck is getting a work-out
> this week :).

Does Magic SysRq work for you (alt-F13) on my G3
try:
 alt-f13-k  (kill processes in current vt)
 alt-f13-s  (emergency sync)
 alt-f13-e  (kill everything except init)

This *should* at least save some fsking time :-)

thanks for the report...
Iain.

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

             reply	other threads:[~2000-07-09 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-09 12:25 Iain Sandoe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-09 20:56 X still locks up Iain Sandoe
     [not found] <200007090058.BAA22277@hyperion.valhalla.net>
2000-07-09 10:29 ` Gwyn Judd
2000-07-09 19:24   ` Michel Dänzer
2000-07-08 22:06 Iain Sandoe
2000-07-07  2:26 Gwyn Judd
2000-07-07  3:22 ` Dan Foster
2000-07-07  3:35   ` Gwyn Judd
2000-07-07 10:47     ` Martin Costabel
2000-07-07 16:39       ` Gregorio Gervasio Jr.
2000-07-07  6:07 ` Michel Lanners
2000-07-07  9:09 ` Michel Dänzer
     [not found] ` <20000707105332.11070@mailhost.mipsys.com>
2000-07-08 19:15   ` Gwyn Judd

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=200007091225.NAA19777@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=b.judd@xtra.co.nz \
    --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).