linux-kernel - Re: problem with codec discovery on HP 2530p

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hy6md600u.wl%tiwai@suse.de>
Date:	Wed, 11 Nov 2009 07:36:17 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Bdale Garbee <bdale@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: problem with codec discovery on HP 2530p

At Tue, 10 Nov 2009 15:56:38 -0500,
Bdale Garbee wrote:
> 
> On Tue, 2009-11-10 at 17:43 +0100, Takashi Iwai wrote:
> 
> > Could you give alsa-info.sh output (run with --no-upload option)
> > on the working (2.6.30.x) kernel?
> > 
> > Also, what module options do you give to snd-hda-intel?
> 
> None intentionally.  Will include alsa-info.sh output for 2.6.32-rc6 too
> since it appears to show the module options in use.
> 
> Bdale
> 
> ====== alsa-info output on 2.6.30.9 =====
(snip)
> !!Modprobe options (Sound related)
> !!--------------------------------
> 
> snd-atiixp-modem: index=-2
> snd-intel8x0m: index=-2
> snd-via82xx-modem: index=-2
> snd-pcsp: index=-2
> snd-hda-intel: enable_msi=1
> snd-hda-intel: single_cmd=1
> snd-hda-intel: model=laptop

The problems are these options for snd-hda-intel.
enable_msi=1 should be OK, as long as it works.

But, single_cmd=1 is obviously not good.  This options is just for
debugging purpose.  That's why that commit hits.

model=laptop looks still needed for your device.  I'll add the quirk
entry if this model really works well.

So, just remove single_cmd=1 option and try again.


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/