From: Takashi Iwai <tiwai@suse.de>
To: Jan De Luyck <lkml@kcore.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.9-rc2] ALSA nm256 driver causes system lockup
Date: Tue, 28 Sep 2004 18:22:32 +0200 [thread overview]
Message-ID: <s5h1xgm1hyv.wl@alsa2.suse.de> (raw)
In-Reply-To: <200409281755.14844.lkml@kcore.org>
At Tue, 28 Sep 2004 17:55:14 +0200,
Jan De Luyck wrote:
>
> On Tuesday 28 September 2004 17:48, Takashi Iwai wrote:
> > At Tue, 28 Sep 2004 14:47:17 +0200,
> >
> > Jan De Luyck wrote:
> > > Hello list,
> > >
> > > I'm trying to configure a laptop (Dell Latitude CXs) with 2.6.9-rc2. All
> > > runs well, except the ALSA nm256 driver for the Neomagic Audio chip.
> > > Loading this driver results in an immediate and complete system
> > > lockup....
> > >
> > > I've tried appending "vaio_hack=1" on the kernel command line, but that
> > > didn't really do anything.
> > >
> > > ALSA is compiled as modules.
> > >
> > > Any pointers?
> >
> > Try to load snd-nm256 driver before X. The chip uses the video RAM
> > for the sound buffer. It seems that X clears all video RAM that
> > confuses the sound driver. I.e. if you already started X, there is no
> > way back :)
>
> Yups, so I read in the documentation accompanying the kernel. It's being
> loaded by hotplug during bootup, but even at that early stage it locks up
> completely.
Does changing latitude_workaround = 0 in nm256.c have any influence?
Takashi
prev parent reply other threads:[~2004-09-28 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 12:47 [2.6.9-rc2] ALSA nm256 driver causes system lockup Jan De Luyck
2004-09-28 15:48 ` Takashi Iwai
2004-09-28 15:55 ` Jan De Luyck
2004-09-28 16:22 ` Takashi Iwai [this message]
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=s5h1xgm1hyv.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@kcore.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