Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Disagreement about versions following CVS update
Date: Mon, 22 Aug 2005 14:14:42 +0200	[thread overview]
Message-ID: <s5hll2up3rh.wl%tiwai@suse.de> (raw)
In-Reply-To: <43063408.60402@redfish-solutions.com>

At Fri, 19 Aug 2005 13:33:28 -0600,
Philip Prindeville wrote:
> 
> I did a CVS update yesterday, and a rebuild and tried to reinstall, and
> I'm seeing:
> 
> WARNING: Error inserting snd_seq_device 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/seq/snd-seq-device.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting snd_rawmidi 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/snd-rawmidi.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting snd_mpu401_uart 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting snd_timer 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/snd-timer.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting snd_timer 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/snd-timer.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting snd_pcm 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/snd-pcm.ko): Unknown 
> symbol in module, or unknown parameter (see dmesg)
> WARNING: Error running install command for snd_pcm
> WARNING: Error inserting snd_ac97_codec 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/pci/ac97/snd-ac97-codec.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting snd_via82xx 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/pci/snd-via82xx.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> 
> Stupid question:  did a version number get changed somewhere?  And if
> so, what's the fix?  I did a:
> 
> % make -C alsa-driver clean
> 
> and a rebuild, but I'm still seeing these.  What did I miss?

After "alsasound stop", unload all remaining snd* modules including
snd-page-alloc.  "alsasound stop" keeps this module intentionally for
the buffer management.

Then start alsasound again.


Takashi


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-08-22 12:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 19:33 Disagreement about versions following CVS update Philip Prindeville
2005-08-19 20:36 ` Lee Revell
2005-08-19 21:11   ` Philip Prindeville
2005-08-19 21:14     ` Lee Revell
2005-08-19 22:17       ` Philip Prindeville
2005-08-19 22:25         ` Lee Revell
2005-08-19 23:20           ` Philip Prindeville
2005-08-19 23:28             ` Lee Revell
2005-08-19 23:43               ` Philip Prindeville
2005-08-19 23:47                 ` Lee Revell
2005-08-19 23:53                   ` Philip Prindeville
2005-08-19 23:56                     ` Lee Revell
2005-08-20  0:06                       ` Philip Prindeville
2005-08-22 12:12                         ` Takashi Iwai
2005-08-22 16:30                           ` Philip Prindeville
2005-08-22 16:33                             ` Takashi Iwai
2005-08-20  7:17 ` Raymond
2005-08-20 21:06   ` Lee Revell
2005-08-21  0:55     ` Raymond
2005-08-22 12:09       ` Takashi Iwai
2005-08-22 15:13         ` Raymond
2005-08-22 15:29           ` Takashi Iwai
2005-08-22 12:14 ` Takashi Iwai [this message]
2005-08-22 16:27   ` Philip Prindeville
2005-08-22 16:29     ` Takashi Iwai

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=s5hll2up3rh.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=philipp_subx@redfish-solutions.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