Disagreement about versions following CVS update

Disagreement about versions following CVS update

[Philip Prindeville]

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?

-Philip



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

Re: Disagreement about versions following CVS update

[Lee Revell]

On Fri, 2005-08-19 at 13:33 -0600, Philip Prindeville wrote:
> 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?

Your kernel sources probably do not match the running kernel.

Lee



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

Re: Disagreement about versions following CVS update

[Philip Prindeville]

Lee Revell wrote:

>On Fri, 2005-08-19 at 13:33 -0600, Philip Prindeville wrote:
>  
>
>>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?
>>    
>>
>
>Your kernel sources probably do not match the running kernel.
>
>Lee
>
>  
>


No, that's not the issue:

[root@media alsa]# make
...
checking for kernel version... 2.6.12-1.1372_FC3
...
checking for directory to store kernel modules... 
/lib/modules/2.6.12-1.1372_FC3/kernel/sound
...
make -C /lib/modules/2.6.12-1.1372_FC3/source 
SUBDIRS=/root/Downloads/alsa/alsa-driver 
O=/lib/modules/2.6.12-1.1372_FC3/build modules
...
install: cannot create regular file `/sbin/init.d/alsasound': No such 
file or directory
...

ALSA modules were successfully compiled.

...
/sbin/depmod -a -F /lib/modules/2.6.12-1.1372_FC3/source/System.map 
2.6.12-1.1372_FC3
...
[root@media alsa]# uname -a
Linux media 2.6.12-1.1372_FC3 #1 Fri Jul 15 00:55:23 EDT 2005 x86_64 
x86_64 x86_64 GNU/Linux
[root@media alsa]#



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

Re: Disagreement about versions following CVS update

[Lee Revell]

On Fri, 2005-08-19 at 15:11 -0600, Philip Prindeville wrote:
> No, that's not the issue:

No idea then.  Try blowing away your tree and getting a fresh checkout?

Lee



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

Re: Disagreement about versions following CVS update

[Philip Prindeville]

Lee Revell wrote:

>On Fri, 2005-08-19 at 15:11 -0600, Philip Prindeville wrote:
>  
>
>>No, that's not the issue:
>>    
>>
>
>No idea then.  Try blowing away your tree and getting a fresh checkout?
>
>Lee
>  
>


No joy.  Changes nothing.

-Philip



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

Re: Disagreement about versions following CVS update

[Lee Revell]

On Fri, 2005-08-19 at 16:17 -0600, Philip Prindeville wrote:
> Lee Revell wrote:
> 
> >On Fri, 2005-08-19 at 15:11 -0600, Philip Prindeville wrote:
> >  
> >
> >>No, that's not the issue:
> >>    
> >>
> >
> >No idea then.  Try blowing away your tree and getting a fresh checkout?
> >
> >Lee
> >  
> >
> 
> 
> No joy.  Changes nothing.

Did you update alsa-kernel as well as alsa-driver?

Lee



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

Re: Disagreement about versions following CVS update

[Philip Prindeville]

Lee Revell wrote:

>On Fri, 2005-08-19 at 16:17 -0600, Philip Prindeville wrote:
>  
>
>>Lee Revell wrote:
>>
>>    
>>
>>>On Fri, 2005-08-19 at 15:11 -0600, Philip Prindeville wrote:
>>> 
>>>
>>>      
>>>
>>>>No, that's not the issue:
>>>>   
>>>>
>>>>        
>>>>
>>>No idea then.  Try blowing away your tree and getting a fresh checkout?
>>>
>>>Lee
>>> 
>>>
>>>      
>>>
>>No joy.  Changes nothing.
>>    
>>
>
>Did you update alsa-kernel as well as alsa-driver?
>
>Lee
>
>  
>

Yep.

-Philip



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

Re: Disagreement about versions following CVS update

[Lee Revell]

On Fri, 2005-08-19 at 17:20 -0600, Philip Prindeville wrote:
> Yep.
> 

What does dmesg say?

Lee



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

Re: Disagreement about versions following CVS update

[Philip Prindeville]

Lee Revell wrote:

>On Fri, 2005-08-19 at 17:20 -0600, Philip Prindeville wrote:
>  
>
>>Yep.
>>
>>    
>>
>
>What does dmesg say?
>
>Lee
>
>  
>

It says:

snd_seq_device: disagrees about version of symbol snd_info_register
snd_seq_device: Unknown symbol snd_info_register
snd_seq_device: disagrees about version of symbol 
snd_info_create_module_entry
snd_seq_device: Unknown symbol snd_info_create_module_entry
snd_seq_device: disagrees about version of symbol snd_info_free_entry
snd_seq_device: Unknown symbol snd_info_free_entry
snd_seq_device: disagrees about version of symbol snd_seq_root
snd_seq_device: Unknown symbol snd_seq_root
snd_seq_device: disagrees about version of symbol snd_device_new
snd_seq_device: Unknown symbol snd_device_new
snd_seq_device: disagrees about version of symbol snd_info_unregister
snd_seq_device: Unknown symbol snd_info_unregister
snd_rawmidi: disagrees about version of symbol snd_info_register
snd_rawmidi: Unknown symbol snd_info_register
snd_rawmidi: disagrees about version of symbol 
snd_ctl_unregister_ioctl_compat
snd_rawmidi: Unknown symbol snd_ctl_unregister_ioctl_compat
snd_rawmidi: Unknown symbol snd_seq_device_new
snd_rawmidi: disagrees about version of symbol snd_info_free_entry
snd_rawmidi: Unknown symbol snd_info_free_entry
snd_rawmidi: Unknown symbol snd_unregister_oss_device
snd_rawmidi: Unknown symbol snd_register_oss_device
snd_rawmidi: disagrees about version of symbol snd_ctl_register_ioctl
snd_rawmidi: Unknown symbol snd_ctl_register_ioctl
snd_rawmidi: disagrees about version of symbol snd_card_file_add
snd_rawmidi: Unknown symbol snd_card_file_add
snd_rawmidi: Unknown symbol snd_oss_info_register
snd_rawmidi: disagrees about version of symbol snd_unregister_device
snd_rawmidi: Unknown symbol snd_unregister_device
snd_rawmidi: disagrees about version of symbol snd_device_new
snd_rawmidi: Unknown symbol snd_device_new
snd_rawmidi: disagrees about version of symbol snd_ctl_unregister_ioctl
snd_rawmidi: Unknown symbol snd_ctl_unregister_ioctl
snd_rawmidi: disagrees about version of symbol snd_ctl_register_ioctl_compat
snd_rawmidi: Unknown symbol snd_ctl_register_ioctl_compat
snd_rawmidi: disagrees about version of symbol snd_info_create_card_entry
snd_rawmidi: Unknown symbol snd_info_create_card_entry
snd_rawmidi: disagrees about version of symbol snd_device_free
snd_rawmidi: Unknown symbol snd_device_free
snd_rawmidi: disagrees about version of symbol snd_card_file_remove
snd_rawmidi: Unknown symbol snd_card_file_remove
snd_rawmidi: disagrees about version of symbol snd_info_unregister
snd_rawmidi: Unknown symbol snd_info_unregister
snd_rawmidi: disagrees about version of symbol snd_device_register
snd_rawmidi: Unknown symbol snd_device_register
snd_rawmidi: disagrees about version of symbol snd_register_device
snd_rawmidi: Unknown symbol snd_register_device
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_mpu401_uart: disagrees about version of symbol snd_device_free
snd_mpu401_uart: Unknown symbol snd_device_free
snd_timer: disagrees about version of symbol snd_info_register
snd_timer: Unknown symbol snd_info_register
snd_timer: disagrees about version of symbol snd_info_create_module_entry
snd_timer: Unknown symbol snd_info_create_module_entry
snd_timer: disagrees about version of symbol snd_info_free_entry
snd_timer: Unknown symbol snd_info_free_entry
snd_timer: Unknown symbol snd_oss_info_register
snd_timer: disagrees about version of symbol snd_unregister_device
snd_timer: Unknown symbol snd_unregister_device
snd_timer: disagrees about version of symbol snd_device_new
snd_timer: Unknown symbol snd_device_new
snd_timer: disagrees about version of symbol snd_info_unregister
snd_timer: Unknown symbol snd_info_unregister
snd_timer: disagrees about version of symbol snd_register_device
snd_timer: Unknown symbol snd_register_device
snd_timer: disagrees about version of symbol snd_info_register
snd_timer: Unknown symbol snd_info_register
snd_timer: disagrees about version of symbol snd_info_create_module_entry
snd_timer: Unknown symbol snd_info_create_module_entry
snd_timer: disagrees about version of symbol snd_info_free_entry
snd_timer: Unknown symbol snd_info_free_entry
snd_timer: Unknown symbol snd_oss_info_register
snd_timer: disagrees about version of symbol snd_unregister_device
snd_timer: Unknown symbol snd_unregister_device
snd_timer: disagrees about version of symbol snd_device_new
snd_timer: Unknown symbol snd_device_new
snd_timer: disagrees about version of symbol snd_info_unregister
snd_timer: Unknown symbol snd_info_unregister
snd_timer: disagrees about version of symbol snd_register_device
snd_timer: Unknown symbol snd_register_device
snd_pcm: disagrees about version of symbol snd_info_register
snd_pcm: Unknown symbol snd_info_register
snd_pcm: disagrees about version of symbol snd_info_create_module_entry
snd_pcm: Unknown symbol snd_info_create_module_entry
snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl_compat
snd_pcm: Unknown symbol snd_ctl_unregister_ioctl_compat
snd_pcm: Unknown symbol snd_timer_notify
snd_pcm: Unknown symbol snd_timer_interrupt
snd_pcm: disagrees about version of symbol snd_info_free_entry
snd_pcm: Unknown symbol snd_info_free_entry
snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl
snd_pcm: Unknown symbol snd_ctl_register_ioctl
snd_pcm: disagrees about version of symbol snd_card_file_add
snd_pcm: Unknown symbol snd_card_file_add
snd_pcm: disagrees about version of symbol snd_unregister_device
snd_pcm: Unknown symbol snd_unregister_device
snd_pcm: Unknown symbol snd_timer_new
snd_pcm: disagrees about version of symbol snd_device_new
snd_pcm: Unknown symbol snd_device_new
snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl
snd_pcm: Unknown symbol snd_ctl_unregister_ioctl
snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl_compat
snd_pcm: Unknown symbol snd_ctl_register_ioctl_compat
snd_pcm: disagrees about version of symbol snd_info_create_card_entry
snd_pcm: Unknown symbol snd_info_create_card_entry
snd_pcm: disagrees about version of symbol snd_power_wait
snd_pcm: Unknown symbol snd_power_wait
snd_pcm: disagrees about version of symbol snd_device_free
snd_pcm: Unknown symbol snd_device_free
snd_pcm: disagrees about version of symbol snd_card_file_remove
snd_pcm: Unknown symbol snd_card_file_remove
snd_pcm: disagrees about version of symbol snd_info_unregister
snd_pcm: Unknown symbol snd_info_unregister
snd_pcm: disagrees about version of symbol snd_device_register
snd_pcm: Unknown symbol snd_device_register
snd_pcm: disagrees about version of symbol snd_register_device
snd_pcm: Unknown symbol snd_register_device
snd_ac97_codec: disagrees about version of symbol snd_info_register
snd_ac97_codec: Unknown symbol snd_info_register
snd_ac97_codec: disagrees about version of symbol snd_ctl_add
snd_ac97_codec: Unknown symbol snd_ctl_add
snd_ac97_codec: disagrees about version of symbol snd_info_free_entry
snd_ac97_codec: Unknown symbol snd_info_free_entry
snd_ac97_codec: Unknown symbol snd_interval_refine
snd_ac97_codec: disagrees about version of symbol snd_ctl_find_id
snd_ac97_codec: Unknown symbol snd_ctl_find_id
snd_ac97_codec: disagrees about version of symbol snd_ctl_new1
snd_ac97_codec: Unknown symbol snd_ctl_new1
snd_ac97_codec: disagrees about version of symbol snd_ctl_remove_id
snd_ac97_codec: Unknown symbol snd_ctl_remove_id
snd_ac97_codec: disagrees about version of symbol snd_component_add
snd_ac97_codec: Unknown symbol snd_component_add
snd_ac97_codec: Unknown symbol snd_pcm_hw_rule_add
snd_ac97_codec: disagrees about version of symbol snd_device_new
snd_ac97_codec: Unknown symbol snd_device_new
snd_ac97_codec: disagrees about version of symbol snd_info_create_card_entry
snd_ac97_codec: Unknown symbol snd_info_create_card_entry
snd_ac97_codec: disagrees about version of symbol snd_info_unregister
snd_ac97_codec: Unknown symbol snd_info_unregister
snd_via82xx: disagrees about version of symbol snd_ctl_add
snd_via82xx: Unknown symbol snd_ctl_add
snd_via82xx: Unknown symbol snd_ac97_resume
snd_via82xx: Unknown symbol snd_pcm_new
snd_via82xx: Unknown symbol snd_pcm_limit_hw_rates
snd_via82xx: disagrees about version of symbol snd_card_register
snd_via82xx: Unknown symbol snd_card_register
snd_via82xx: disagrees about version of symbol snd_card_free
snd_via82xx: Unknown symbol snd_card_free
snd_via82xx: Unknown symbol snd_pcm_lib_preallocate_pages_for_all
snd_via82xx: disagrees about version of symbol snd_card_proc_new
snd_via82xx: Unknown symbol snd_card_proc_new
snd_via82xx: Unknown symbol snd_ac97_set_rate
snd_via82xx: Unknown symbol snd_pcm_format_physical_width
snd_via82xx: Unknown symbol snd_ac97_update_bits
snd_via82xx: Unknown symbol snd_ac97_mixer
snd_via82xx: Unknown symbol snd_ac97_bus
snd_via82xx: disagrees about version of symbol snd_ctl_find_id
snd_via82xx: Unknown symbol snd_ctl_find_id
snd_via82xx: disagrees about version of symbol snd_ctl_new1
snd_via82xx: Unknown symbol snd_ctl_new1
snd_via82xx: disagrees about version of symbol snd_card_new
snd_via82xx: Unknown symbol snd_card_new
snd_via82xx: Unknown symbol snd_ac97_suspend
snd_via82xx: Unknown symbol snd_pcm_lib_malloc_pages
snd_via82xx: Unknown symbol snd_pcm_lib_ioctl
snd_via82xx: Unknown symbol snd_pcm_lib_free_pages
snd_via82xx: Unknown symbol snd_pcm_set_ops
snd_via82xx: disagrees about version of symbol snd_card_set_pm_callback
snd_via82xx: Unknown symbol snd_card_set_pm_callback
snd_via82xx: Unknown symbol snd_pcm_hw_constraint_list
snd_via82xx: disagrees about version of symbol snd_device_new
snd_via82xx: Unknown symbol snd_device_new
snd_via82xx: Unknown symbol snd_pcm_sgbuf_ops_page
snd_via82xx: Unknown symbol snd_mpu401_uart_interrupt
snd_via82xx: Unknown symbol snd_ac97_get_short_name
snd_via82xx: Unknown symbol snd_pcm_suspend_all
snd_via82xx: Unknown symbol snd_pcm_hw_constraint_integer
snd_via82xx: Unknown symbol snd_mpu401_uart_new
snd_via82xx: Unknown symbol snd_pcm_period_elapsed
snd_via82xx: Unknown symbol snd_ac97_tune_hardware




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

Re: Disagreement about versions following CVS update

[Lee Revell]

On Fri, 2005-08-19 at 17:43 -0600, Philip Prindeville wrote:
> nd_seq_device: disagrees about version of symbol snd_info_register
> snd_seq_device: Unknown symbol snd_info_register
> snd_seq_device: disagrees about version of symbol 
> snd_info_create_module_entry 

Did you make sure to remove the previous modules with rmmod before
modprobe'ing the new ones?

Lee



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

Re: Disagreement about versions following CVS update

[Philip Prindeville]

Lee Revell wrote:

>On Fri, 2005-08-19 at 17:43 -0600, Philip Prindeville wrote:
>  
>
>>nd_seq_device: disagrees about version of symbol snd_info_register
>>snd_seq_device: Unknown symbol snd_info_register
>>snd_seq_device: disagrees about version of symbol 
>>snd_info_create_module_entry 
>>    
>>
>
>Did you make sure to remove the previous modules with rmmod before
>modprobe'ing the new ones?
>
>Lee
>
>  
>

Yessir.



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

Re: Disagreement about versions following CVS update

[Lee Revell]

On Fri, 2005-08-19 at 17:53 -0600, Philip Prindeville wrote:
> Lee Revell wrote:
> 
> >On Fri, 2005-08-19 at 17:43 -0600, Philip Prindeville wrote:
> >  
> >
> >>nd_seq_device: disagrees about version of symbol snd_info_register
> >>snd_seq_device: Unknown symbol snd_info_register
> >>snd_seq_device: disagrees about version of symbol 
> >>snd_info_create_module_entry 
> >>    
> >>
> >
> >Did you make sure to remove the previous modules with rmmod before
> >modprobe'ing the new ones?
> >
> >Lee
> >
> >  
> >
> 
> Yessir.
> 
> 

Then I'm completely out of ideas.  This is either a bug in the Fedora
kernel, or a bug in ALSA.

Lee



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

Re: Disagreement about versions following CVS update

[Philip Prindeville]

Lee Revell wrote:

>On Fri, 2005-08-19 at 17:53 -0600, Philip Prindeville wrote:
>  
>
>>Lee Revell wrote:
>>
>>    
>>
>>>On Fri, 2005-08-19 at 17:43 -0600, Philip Prindeville wrote:
>>> 
>>>
>>>      
>>>
>>>>nd_seq_device: disagrees about version of symbol snd_info_register
>>>>snd_seq_device: Unknown symbol snd_info_register
>>>>snd_seq_device: disagrees about version of symbol 
>>>>snd_info_create_module_entry 
>>>>   
>>>>
>>>>        
>>>>
>>>Did you make sure to remove the previous modules with rmmod before
>>>modprobe'ing the new ones?
>>>
>>>Lee
>>>
>>> 
>>>
>>>      
>>>
>>Yessir.
>>
>>
>>    
>>
>
>Then I'm completely out of ideas.  This is either a bug in the Fedora
>kernel, or a bug in ALSA.
>
>Lee
>
>  
>

Yup.  I even pulled a fresh tree, too.

Say, there's another issue that I'm struggling with...  I'm trying to get
the makefiles to be a little more Fedora-friendly...

As they are, things like libdir and datadir aren't set correctly by
default...

Not sure why the top-level Makefile has:

HOST            = "$(ARCH)-suse-linux-gnu"

either...

Shouldn't that be passed in or discovered dynamically?

-Philip


-Philip



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

Re: Disagreement about versions following CVS update

[Raymond]

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?
> 
> -Philip

It seem that ALSA version has been changed from 1.0.9b to 1.10.0-rc1 on CVS.

alsa-driver and alsa-lib can be rebuilded except alsa-utils.
I follow the instruction but cannot compile alsa-utils (CVS) on FC1.


cvs/alsa-utils]# ./cvscompile
Copying file ABOUT-NLS
Copying file config.rpath
Copying file mkinstalldirs
Not copying intl/ directory.
Copying file po/Makefile.in.in
Copying file po/boldquot.sed
Copying file po/en@boldquot.header
Copying file po/en@quot.header
Copying file po/insert-header.sin
Copying file po/Makevars.template
Copying file po/quot.sed
Copying file po/remove-potcdate.sin
Copying file po/Rules-quot
Copying file m4/codeset.m4
Copying file m4/gettext.m4
Copying file m4/glibc21.m4
Copying file m4/iconv.m4
Copying file m4/intdiv0.m4
Copying file m4/inttypes.m4
Copying file m4/inttypes_h.m4
Copying file m4/inttypes-pri.m4
Copying file m4/isc-posix.m4
Copying file m4/lcmessage.m4
Copying file m4/lib-ld.m4
Copying file m4/lib-link.m4
Copying file m4/lib-prefix.m4
Copying file m4/nls.m4
Copying file m4/po.m4
Copying file m4/progtest.m4
Copying file m4/stdint_h.m4
Copying file m4/uintmax_t.m4
Copying file m4/ulonglong.m4
Updating configure.in (backup is in configure.in~)

Please use AM_GNU_GETTEXT([external]) in order to cause autoconfiguration
to look for an external libintl.

Please run 'aclocal -I m4' to regenerate the aclocal.m4 file.
You need aclocal from GNU automake 1.5 (or newer) to do this.
Then run 'autoconf' to regenerate the configure file.

You might also want to copy the convenience header file gettext.h
from the /usr/share/gettext directory into your package.
It is a wrapper around <libintl.h> that implements the configure 
--disable-nls
option.

Press Return to acknowledge the previous three paragraphs.

CFLAGS=-O2 -Wall -pipe -g
./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for style of include used by make... GNU
checking for gcc... gcc32
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc32 accepts -g... yes
checking for gcc32 option to accept ANSI C... none needed
checking dependency style of gcc32... gcc3
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
./configure: line 4415: syntax error near unexpected token `<<<'
./configure: line 4415: `<<<<<<< configure.in'


cvs/alsa-utils]# aclocal --version
aclocal (GNU automake) 1.7.8

cvs/alsa-utils]# aclocal -I m4

cvs/alsa-utils]# autoconf --version
autoconf (GNU Autoconf) 2.57

cvs/alsa-utils]# autoconf

cvs/alsa-utils]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for style of include used by make... GNU
checking for gcc... gcc32
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc32 accepts -g... yes
checking for gcc32 option to accept ANSI C... none needed
checking dependency style of gcc32... gcc3
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
./configure: line 4415: syntax error near unexpected token `<<<'
./configure: line 4415: `<<<<<<< configure.in'







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

Re: Re: Disagreement about versions following CVS update

[Lee Revell]

On Sat, 2005-08-20 at 15:17 +0800, Raymond wrote:
> ./configure: line 4415: syntax error near unexpected token `<<<'
> ./configure: line 4415: `<<<<<<< configure.in' 

This indicates a CVS merge conflict.  Try a fresh checkout.

Lee



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

Re: Disagreement about versions following CVS update

[Raymond]

Lee Revell wrote:
> On Sat, 2005-08-20 at 15:17 +0800, Raymond wrote:
> 
>>./configure: line 4415: syntax error near unexpected token `<<<'
>>./configure: line 4415: `<<<<<<< configure.in' 
> 
> 
> This indicates a CVS merge conflict.  Try a fresh checkout.
> 
> Lee
> 

It's strange to find the following mixer controls in CAPTURE VIEW of 
alsamixer v1.0.10rc1 :-


# amixer -version
amixer version 1.0.10rc1

Simple mixer control '3D Control Sigmatel - Depth',0
   Capabilities: volume volume-joined
   Playback channels: Mono
   Capture channels: Mono
   Limits: 0 - 3
   Mono: 0 [0%]
Simple mixer control '3D Control Sigmatel - Rear Depth',0
   Capabilities: volume volume-joined
   Playback channels: Mono
   Capture channels: Mono
   Limits: 0 - 3
   Mono: 0 [0%]


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

Re: Re: Disagreement about versions following CVS update

[Takashi Iwai]

At Sun, 21 Aug 2005 08:55:37 +0800,
Raymond wrote:
> 
> Lee Revell wrote:
> > On Sat, 2005-08-20 at 15:17 +0800, Raymond wrote:
> > 
> >>./configure: line 4415: syntax error near unexpected token `<<<'
> >>./configure: line 4415: `<<<<<<< configure.in' 
> > 
> > 
> > This indicates a CVS merge conflict.  Try a fresh checkout.
> > 
> > Lee
> > 
> 
> It's strange to find the following mixer controls in CAPTURE VIEW of 
> alsamixer v1.0.10rc1 :-
> 
> 
> # amixer -version
> amixer version 1.0.10rc1
> 
> Simple mixer control '3D Control Sigmatel - Depth',0
>    Capabilities: volume volume-joined
>    Playback channels: Mono
>    Capture channels: Mono
>    Limits: 0 - 3
>    Mono: 0 [0%]
> Simple mixer control '3D Control Sigmatel - Rear Depth',0
>    Capabilities: volume volume-joined
>    Playback channels: Mono
>    Capture channels: Mono
>    Limits: 0 - 3
>    Mono: 0 [0%]

This must be a bug of new simple abstraction code.


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

Re: Disagreement about versions following CVS update

[Takashi Iwai]

At Fri, 19 Aug 2005 18:06:41 -0600,
Philip Prindeville wrote:
> 
> Lee Revell wrote:
> 
> >On Fri, 2005-08-19 at 17:53 -0600, Philip Prindeville wrote:
> >  
> >
> >>Lee Revell wrote:
> >>
> >>    
> >>
> >>>On Fri, 2005-08-19 at 17:43 -0600, Philip Prindeville wrote:
> >>> 
> >>>
> >>>      
> >>>
> >>>>nd_seq_device: disagrees about version of symbol snd_info_register
> >>>>snd_seq_device: Unknown symbol snd_info_register
> >>>>snd_seq_device: disagrees about version of symbol 
> >>>>snd_info_create_module_entry 
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>Did you make sure to remove the previous modules with rmmod before
> >>>modprobe'ing the new ones?
> >>>
> >>>Lee
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >>Yessir.
> >>
> >>
> >>    
> >>
> >
> >Then I'm completely out of ideas.  This is either a bug in the Fedora
> >kernel, or a bug in ALSA.
> >
> >Lee
> >
> >  
> >
> 
> Yup.  I even pulled a fresh tree, too.
> 
> Say, there's another issue that I'm struggling with...  I'm trying to get
> the makefiles to be a little more Fedora-friendly...
> 
> As they are, things like libdir and datadir aren't set correctly by
> default...
> 
> Not sure why the top-level Makefile has:
> 
> HOST            = "$(ARCH)-suse-linux-gnu"
> 
> either...
>
> Shouldn't that be passed in or discovered dynamically?

I can't find any HOST in Makefile...


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

Re: Disagreement about versions following CVS update

[Takashi Iwai]

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

Re: Disagreement about versions following CVS update

[Raymond]

Takashi Iwai wrote:
> At Sun, 21 Aug 2005 08:55:37 +0800,
> Raymond wrote:
> 
>>
>>It's strange to find the following mixer controls in CAPTURE VIEW of 
>>alsamixer v1.0.10rc1 :-
>>
>>
>># amixer -version
>>amixer version 1.0.10rc1
>>
>>Simple mixer control '3D Control Sigmatel - Depth',0
>>   Capabilities: volume volume-joined
>>   Playback channels: Mono
>>   Capture channels: Mono
>>   Limits: 0 - 3
>>   Mono: 0 [0%]
>>Simple mixer control '3D Control Sigmatel - Rear Depth',0
>>   Capabilities: volume volume-joined
>>   Playback channels: Mono
>>   Capture channels: Mono
>>   Limits: 0 - 3
>>   Mono: 0 [0%]
> 
> 
> This must be a bug of new simple abstraction code.
> 
> 
> Takashi
> 
>

Not only AC97 3D control, also EQ Peaks and 10-bands stereo EQ controls


Simple mixer control 'EQ0 31Hz',0
   Capabilities: volume
   Playback channels: Front Left - Front Right
   Capture channels: Front Left - Front Right
   Limits: 0 - 32767
   Front Left: 16022 [49%]
   Front Right: 16022 [49%]
Simple mixer control 'EQ1 63Hz',0
   Capabilities: volume
   Playback channels: Front Left - Front Right
   Capture channels: Front Left - Front Right
   Limits: 0 - 32767
   Front Left: 16022 [49%]
   Front Right: 16022 [49%]







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

Re: Re: Disagreement about versions following CVS update

[Takashi Iwai]

At Mon, 22 Aug 2005 23:13:59 +0800,
Raymond wrote:
> 
> Takashi Iwai wrote:
> > At Sun, 21 Aug 2005 08:55:37 +0800,
> > Raymond wrote:
> > 
> >>
> >>It's strange to find the following mixer controls in CAPTURE VIEW of 
> >>alsamixer v1.0.10rc1 :-
> >>
> >>
> >># amixer -version
> >>amixer version 1.0.10rc1
> >>
> >>Simple mixer control '3D Control Sigmatel - Depth',0
> >>   Capabilities: volume volume-joined
> >>   Playback channels: Mono
> >>   Capture channels: Mono
> >>   Limits: 0 - 3
> >>   Mono: 0 [0%]
> >>Simple mixer control '3D Control Sigmatel - Rear Depth',0
> >>   Capabilities: volume volume-joined
> >>   Playback channels: Mono
> >>   Capture channels: Mono
> >>   Limits: 0 - 3
> >>   Mono: 0 [0%]
> > 
> > 
> > This must be a bug of new simple abstraction code.
> > 
> > 
> > Takashi
> > 
> >
> 
> Not only AC97 3D control, also EQ Peaks and 10-bands stereo EQ controls
> 
> 
> Simple mixer control 'EQ0 31Hz',0
>    Capabilities: volume
>    Playback channels: Front Left - Front Right
>    Capture channels: Front Left - Front Right
>    Limits: 0 - 32767
>    Front Left: 16022 [49%]
>    Front Right: 16022 [49%]
> Simple mixer control 'EQ1 63Hz',0
>    Capabilities: volume
>    Playback channels: Front Left - Front Right
>    Capture channels: Front Left - Front Right
>    Limits: 0 - 32767
>    Front Left: 16022 [49%]
>    Front Right: 16022 [49%]

Could you report this on ALSA BTS?

Thanks,


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

Re: Disagreement about versions following CVS update

[Philip Prindeville]

Takashi Iwai wrote:

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

The issue seemed to be that you can only rmmod/insmod the driver
a finite number of times, and then it will start reporting this error
about being the wrong kernel version number.

Rebooting fixed the problem.

-Philip



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

Re: Disagreement about versions following CVS update

[Takashi Iwai]

At Mon, 22 Aug 2005 10:27:13 -0600,
Philip Prindeville wrote:
> 
> Takashi Iwai wrote:
> 
> >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
> >  
> >
> 
> The issue seemed to be that you can only rmmod/insmod the driver
> a finite number of times, and then it will start reporting this error
> about being the wrong kernel version number.

No, the reason is that the old module remained because alsasound
hadn't removed it.  Since the other modules depend on the functions
snd-page-alloc provides, they couldn't be loaded.

> Rebooting fixed the problem.

That's another way to fix the above, instead of rmmod :)


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

Re: Disagreement about versions following CVS update

[Philip Prindeville]

Takashi Iwai wrote:

>At Fri, 19 Aug 2005 18:06:41 -0600,
>Philip Prindeville wrote:
>  
>
>>Lee Revell wrote:
>>
>>    
>>
>>>On Fri, 2005-08-19 at 17:53 -0600, Philip Prindeville wrote:
>>> 
>>>
>>>      
>>>
>>>>Lee Revell wrote:
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>On Fri, 2005-08-19 at 17:43 -0600, Philip Prindeville wrote:
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>>>nd_seq_device: disagrees about version of symbol snd_info_register
>>>>>>snd_seq_device: Unknown symbol snd_info_register
>>>>>>snd_seq_device: disagrees about version of symbol 
>>>>>>snd_info_create_module_entry 
>>>>>>  
>>>>>>
>>>>>>       
>>>>>>
>>>>>>            
>>>>>>
>>>>>Did you make sure to remove the previous modules with rmmod before
>>>>>modprobe'ing the new ones?
>>>>>
>>>>>Lee
>>>>>
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>Yessir.
>>>>
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>Then I'm completely out of ideas.  This is either a bug in the Fedora
>>>kernel, or a bug in ALSA.
>>>
>>>Lee
>>>
>>> 
>>>
>>>      
>>>
>>Yup.  I even pulled a fresh tree, too.
>>
>>Say, there's another issue that I'm struggling with...  I'm trying to get
>>the makefiles to be a little more Fedora-friendly...
>>
>>As they are, things like libdir and datadir aren't set correctly by
>>default...
>>
>>Not sure why the top-level Makefile has:
>>
>>HOST            = "$(ARCH)-suse-linux-gnu"
>>
>>either...
>>
>>Shouldn't that be passed in or discovered dynamically?
>>    
>>
>
>I can't find any HOST in Makefile...
>  
>

Odd.  I got the package via CVS, andthe Makefile is in the directory
above alsa-driver, alsa-lib, etc.

-Philip

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

Re: Disagreement about versions following CVS update

[Takashi Iwai]

At Mon, 22 Aug 2005 10:30:43 -0600,
Philip Prindeville wrote:
> 
> Takashi Iwai wrote:
> 
> >At Fri, 19 Aug 2005 18:06:41 -0600,
> >Philip Prindeville wrote:
> >  
> >
> >>Lee Revell wrote:
> >>
> >>    
> >>
> >>>On Fri, 2005-08-19 at 17:53 -0600, Philip Prindeville wrote:
> >>> 
> >>>
> >>>      
> >>>
> >>>>Lee Revell wrote:
> >>>>
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>>>On Fri, 2005-08-19 at 17:43 -0600, Philip Prindeville wrote:
> >>>>>
> >>>>>
> >>>>>     
> >>>>>
> >>>>>          
> >>>>>
> >>>>>>nd_seq_device: disagrees about version of symbol snd_info_register
> >>>>>>snd_seq_device: Unknown symbol snd_info_register
> >>>>>>snd_seq_device: disagrees about version of symbol 
> >>>>>>snd_info_create_module_entry 
> >>>>>>  
> >>>>>>
> >>>>>>       
> >>>>>>
> >>>>>>            
> >>>>>>
> >>>>>Did you make sure to remove the previous modules with rmmod before
> >>>>>modprobe'ing the new ones?
> >>>>>
> >>>>>Lee
> >>>>>
> >>>>>
> >>>>>
> >>>>>     
> >>>>>
> >>>>>          
> >>>>>
> >>>>Yessir.
> >>>>
> >>>>
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>Then I'm completely out of ideas.  This is either a bug in the Fedora
> >>>kernel, or a bug in ALSA.
> >>>
> >>>Lee
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >>Yup.  I even pulled a fresh tree, too.
> >>
> >>Say, there's another issue that I'm struggling with...  I'm trying to get
> >>the makefiles to be a little more Fedora-friendly...
> >>
> >>As they are, things like libdir and datadir aren't set correctly by
> >>default...
> >>
> >>Not sure why the top-level Makefile has:
> >>
> >>HOST            = "$(ARCH)-suse-linux-gnu"
> >>
> >>either...
> >>
> >>Shouldn't that be passed in or discovered dynamically?
> >>    
> >>
> >
> >I can't find any HOST in Makefile...
> >  
> >
> 
> Odd.  I got the package via CVS, andthe Makefile is in the directory
> above alsa-driver, alsa-lib, etc.

Of course, Makefile is in alsa-driver tree but the line you suggested
above isn't found in alsa-driver/Makefile.

The line with host is found in Makefiles of other packages, but they
are completely different things.  They are based on automake while
alsa-driver uses only autoconf and its home-made Makefile.


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