[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#298623: installation report (i386 laptop failure)

On Wed, Mar 09, 2005 at 12:09:43AM +0100, Frans Pop wrote:
> The dump probably happens because the OSS (i810_audio) audio driver does 
> not like something about your hardware. I think you will have more luck 
> with the ALSA (snd_intel8x0) modules. I would think this problem should 
> be solved after you install the alsa packages as IIRC they include 
> blacklisting for the OSS modules.
> Can you confirm if this is correct?

Yes, the ALSA module loads without problems.  I can't verify whether
installing the alsa-* packages blacklists the i810_audio driver, because
I no longer have the laptop with me.  In any event, I kept the manual
blacklist entries in place, because I don't ever want the user to come
back to me saying "the laptop doesn't boot, or respond to ctrl-alt-del,
and by the way it says something about Oops and a lot of numbers on
the screen".

(He may have to bring it back to me today, depending on whether I got the
PPPOE configuration right on the first try.  I won't know until later.)

> [1] http://bugs.debian.org/287344 (hp pavilion ze4900)

Same as mine, except that I fumbled around more than he did.

> [2] http://bugs.debian.org/277691 (laptop Dell D600)

Definitely milder symptoms.  He didn't mention having to boot with
init=/bin/sh as I did, or doing any chroot tricks from the install CD.

> [3] http://bugs.debian.org/296188 (HP Pavillion zd8000)

Same symptom as mine.

> P.S.
> My own Toshiba Satellite A40 laptop has:
> i810_audio: Connection 0 with codec id 0
> ac97_codec: AC97 Audio codec, id: ADS116 (Unknown)
> i810_audio: AC'97 codec 0 supports AMAP, total channels = 2
> While yours has:
> i810_audio: Connection 0 with codec id 0
> ac97_codec: AC97 Modem codec, id: CXT48 (Unknown)
> i810_audio: codec 0 is a softmodem - skipping.

Hmm.  I don't know whether this is a difference between pre-rc2 and
whichever installer you used, or a difference caused by the presence of
a "winmodem".

> It looks like this could be a kernel driver bug.

That was my assumption too.

Reply to: