linux-kernel - Can someone update alsa in the kernel?

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 14 Feb 2009 12:34:28 -0500
From:	Dylan Taft <d13f00l@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Can someone update alsa in the kernel?

I've been using alsa compiled outside the kernel for several months,
it broke some time ago around 2.6.27 for my hardware.
alsa-driver-1.0.19 works fine, for snd-hda-intel

With whatever version is in the kernel now, when the modules are
loaded, dmesg fills up with
hda_codec: invalid dep_range_val 0:7fff

alsa driver 1.0.19 will work, but
ALSA /var/tmp/portage/media-sound/alsa-driver-1.0.18a/work/alsa-driver-1.0.18a/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:623:
hda_intel: azx_get_response timeout, switching to polling mode: last
cmd=0x100f0000
ALSA /var/tmp/portage/media-sound/alsa-driver-1.0.18a/work/alsa-driver-1.0.18a/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1258:
hda_intel: Codec #1 probe error; disabling it...
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
d13f00l-desktop diefool #

shows in dmesg,it works totally fine though
lspci -k
00:1b.0 Audio device: Intel Corporation Device 3a3e
	Kernel driver in use: HDA Intel
	Kernel modules: snd-hda-intel

If you do a quick google on invalid_dep_range_val, a bunch of bugs
have been filed for various distros, but it's been fixed in later
versions of alsa.  This would save a lot of headaches for newer users
unfamiliar with alsa if it was merged into the kernel.

Any comments?

Thanks!

Dylan
--
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/