From: Robin Neatherway <neatherway@gmail.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Jack sense fails on Fujitsu p7120
Date: Sun, 23 Jan 2011 19:55:13 +0000 [thread overview]
Message-ID: <AANLkTim2ch5-QHoh67SuKwMmTMQL=HM6VG1iVCxxoo9+@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimb+yqOhWP1Rc78F9pc+j6VEGp7v0SYvGi7mGrb@mail.gmail.com>
> If you compiled the driver in debug mode, you can select model=test for
> alc260
>
> http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=7cf51e48315d87b4c1cf600d611894f45f661142
Thanks for the suggestion. I tried compiling both the stable versions
and the latest snapshots. The result was that new modules appeared in
/lib/modules/`uname -r`/updates/alsa, which I think is the idea.
However, when trying to use these modules, I received
$ sudo modprobe snd-hda-intel
FATAL: Error inserting snd_hda_intel
(/lib/modules/2.6.35-24-generic/updates/alsa/pci/hda/snd-hda-intel.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
And dmesg contains the following:
syslog:Jan 23 16:47:03 baldur kernel: [ 23.389315] snd: Unknown
symbol unregister_sound_special (err 0)
syslog:Jan 23 16:47:03 baldur kernel: [ 23.390067] snd: Unknown
symbol register_sound_special_device (err 0)
After reinstalling the alsa and linux-sound packages for Ubuntu, I
recovered sound, but I can't try the "test" parameter without being
able to load the module.
Do you know what this error means?
Robin
next prev parent reply other threads:[~2011-01-23 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 10:32 Jack sense fails on Fujitsu p7120 Robin Neatherway
2011-01-20 14:12 ` Robin Neatherway
2011-01-21 6:25 ` Raymond Yau
2011-01-23 19:55 ` Robin Neatherway [this message]
2011-01-25 1:17 ` Raymond Yau
2011-02-01 1:49 ` Robin Neatherway
2011-02-01 2:24 ` Raymond Yau
2011-02-02 0:04 ` Robin Neatherway
2011-02-02 3:14 ` Raymond Yau
2011-02-02 16:00 ` Takashi Iwai
2011-02-02 23:38 ` Robin Neatherway
2011-02-03 7:31 ` Takashi Iwai
2011-02-03 23:49 ` Robin Neatherway
2011-02-04 6:20 ` Takashi Iwai
2011-02-04 10:17 ` Robin Neatherway
2011-02-05 23:36 ` Raymond Yau
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='AANLkTim2ch5-QHoh67SuKwMmTMQL=HM6VG1iVCxxoo9+@mail.gmail.com' \
--to=neatherway@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@gmail.com \
/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).