Skip to contentSkip to conversation

1.0.4rc1 release

DISCUSSION guan yim 5 participants 18 messages Mar 29, 2004 – Apr 6, 2004 2 messages not in the archive

lore
Share & tools
lore

guan yim

author
#0 lore raw

Hi,

alsa-driver:

if simply just do ./configure then make, here is what I get:

In file included from mpu401.c:4:
../../alsa-kernel/drivers/mpu401/mpu401.c:31:27: acpi/acpi_bus.h: No such file or directory make[3]: *** [fastdep] Error 1
make[3]: Leaving directory `/root/alsa104rc1/alsa-driver-1.0.4rc1/drivers/mpu401' make[2]: *** [_sfdep_mpu401] Error 2
make[2]: Leaving directory `/root/alsa104rc1/alsa-driver-1.0.4rc1/drivers' make[1]: *** [dep] Error 1
make[1]: Leaving directory `/root/alsa104rc1/alsa-driver-1.0.4rc1'
make: *** [include/sndversions.h] Error 2

But if I were to use something like ./configure --with-cards=emu10k1 then make, no problem.

alsa-lib: ./configure;make;make install, no problem.
alsa-utils: ./configure;make;make install, no problem. other packages not tested.

System configuration: Redhat 7.3 distro, original GCC (2.96), kernel 2.4.20

Thanks.

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#1 lore raw
Quoted 4 lines · guan yim

alsa-driver:

if simply just do ./configure then make, here is what I get:

Quoted 11 lines

In file included from mpu401.c:4:
../../alsa-kernel/drivers/mpu401/mpu401.c:31:27: acpi/acpi_bus.h: No such file or directory
make[3]: *** [fastdep] Error 1
make[3]: Leaving directory `/root/alsa104rc1/alsa-driver-1.0.4rc1/drivers/mpu401' make[2]: *** [_sfdep_mpu401] Error 2
make[2]: Leaving directory `/root/alsa104rc1/alsa-driver-1.0.4rc1/drivers' make[1]: *** [dep] Error 1
make[1]: Leaving directory `/root/alsa104rc1/alsa-driver-1.0.4rc1'
make: *** [include/sndversions.h] Error 2

Is somewhere defined acpi_walk_resources() function in your kernel tree?

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#2 lore raw
Quoted 1 line · Jaroslav Kysela

1.0.4rc1 packages are out. Please, report compilation problems.

On a 2.2.19 kernel:

depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-*
depmod:         synchronize_irq
depmod:         tqueue_lock
depmod:         waitqueue_lock
depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-au88?0.o
depmod:         snd_pci_compat_disable_device
depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd.o
depmod:         kernel_flag

How long do we want to support 2.2.x?

Regards,
Clemens

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#3 lore raw
Quoted 9 lines · Clemens Ladisch
Quoted 1 line · Jaroslav Kysela

1.0.4rc1 packages are out. Please, report compilation problems.

On a 2.2.19 kernel:

depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-*
depmod:         synchronize_irq
depmod:         tqueue_lock
depmod:         waitqueue_lock

Missing inclusion of some header files?

Quoted 2 lines

depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-au88?0.o
depmod: snd_pci_compat_disable_device

Fixed.

Quoted 2 lines

depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd.o
depmod: kernel_flag

What's this?

Quoted 1 line

How long do we want to support 2.2.x?

At least for 1.0.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#4 lore raw
Quoted 7 lines · Jaroslav Kysela
Quoted 4 lines · Clemens Ladisch

On a 2.2.19 kernel:

depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-*
...

Missing inclusion of some header files?

Sorry, my error. Wrong kernel configuration. (The result of "Hey, this old file looks like a kernel -- let's see what happens if I boot it ..." ;-)

But now:

# modprobe snd
modprobe: Too deep recursion in module dependencies!
modprobe: Circular dependency? snd-page-alloc snd

snd_pci_compat_get_pci_driver() is called from pci_compat_pm_callback() in misc.c. I think the 2.2.x CONFIG_APM stuff in misc.c could be moved into pci_compat_22.c, but OTOH it might make more sense to move the PCI functions that don't do page allocation from the snd-page-alloc module into snd. What's your opinion on this?

Regards,
Clemens

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#5 lore raw
Quoted 8 lines · Clemens Ladisch

But now:

# modprobe snd
modprobe: Too deep recursion in module dependencies!
modprobe: Circular dependency? snd-page-alloc snd

snd_pci_compat_get_pci_driver() is called from pci_compat_pm_callback() in misc.c. I think the 2.2.x CONFIG_APM

I don't see the circular dependency for this function. snd_pci_compat_get_pci_driver() is defined in snd-page-alloc and pci_compat_pm_callback() does not define it. I'm missing something?

Quoted 4 lines

stuff in misc.c could be moved into pci_compat_22.c, but OTOH it might make more sense to move the PCI functions that don't do page allocation from the snd-page-alloc module into snd. What's your opinion on this?

I don't mind so much. But having related compatibility stuff at one place also makes sense.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#6 lore raw
Quoted 4 lines · Jaroslav Kysela
Quoted 2 lines · Clemens Ladisch

But now:

Quoted 8 lines
Quoted 6 lines
# modprobe snd
modprobe: Too deep recursion in module dependencies!
modprobe: Circular dependency? snd-page-alloc snd

snd_pci_compat_get_pci_driver() is called from
pci_compat_pm_callback() in misc.c.

I don't see the circular dependency for this function.

Sorry, I didn't remember that snd-page-alloc should not depend on snd.

The circular dependency is caused by snd_pci_compat_request_region() which calls request_region() which is #defined to be snd_wrapper_request_region() in wrappers.c.

snd_pci_compat_request_region() clearly didn't intend to use the wrapper function, so I added another wrapper function to call the original function.

Now the modules load. However, loading snd-usb-audio doesn't do anything, and unloading and reloading it results in a crash or a hang. Still debugging ...

Regards,
Clemens

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#7 lore raw
Quoted 2 lines · I wrote:

Now the modules load. However, loading snd-usb-audio doesn't do anything, and unloading and reloading it results in a crash or a hang.

Fixed. Apparently, snd-usb-audio has never been working on 2.2.x, and nobody noticed ...

No remaining 2.2.x bugs AFAICS.

Clemens

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#8 lore raw
Quoted 8 lines · Clemens Ladisch
Quoted 2 lines · I wrote:

Now the modules load. However, loading snd-usb-audio doesn't do anything, and unloading and reloading it results in a crash or a hang.

Fixed. Apparently, snd-usb-audio has never been working on 2.2.x, and nobody noticed ...

No remaining 2.2.x bugs AFAICS.

Thanks.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#9 lore raw

period size

In reply to Clemens Ladisch

Hi

I am trying to write a pcm app which receives sound over the network and outputs it through the speakers. The network protocol is udp. From what I can tell, each packet is a single period with interleaved channels. My problem is that the period size appears to be below the minimum that my hardware will go. For example:

rate: 48000 Hz
channels: 2
packet size: 512 bytes
sample size: 16 bit

ok so far... (correct me if I'm wrong)

period size = (packet size * 8) / (channels * sample size)

			=  (512 * 8) / (16 * 2)
			= 128

buffer size = (whatever i like...? latency/network stability...?)

When I try to set the period size exactly I get an error. If I set the period size near I get 192. How do I make this work? Should I reconfigure the network sound source? Do I put the packets together into larger periods? Can alsa do this for me?

cheers
Tim

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#10 lore raw

Re: period size

Quoted 15 lines · Tim Hollingsworth

Hi

I am trying to write a pcm app which receives sound over the network and outputs it through the speakers. The network protocol is udp.
From what I can tell, each packet is a single period with interleaved
channels. My problem is that the period size appears to be below the
minimum that my hardware will go. For example:

rate: 48000 Hz
channels: 2
packet size: 512 bytes
sample size: 16 bit

ok so far... (correct me if I'm wrong)

Quoted 8 lines

period size = (packet size * 8) / (channels * sample size)

			=  (512 * 8) / (16 * 2)
			= 128

buffer size = (whatever i like...? latency/network stability...?)

When I try to set the period size exactly I get an error. If I set the period size near I get 192. How do I make this work? Should I

Your hardware (probably emu10k1 or audigy) does not support this period size for capture.

Quoted 2 lines

reconfigure the network sound source? Do I put the packets together into larger periods? Can alsa do this for me?

You can read/write any size.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#13 lore raw

Re: period size

Thanks for your help so far Jaroslav.

I have taken another look at my project and now it's behaving differently! It still won't go down to a period size of 128.

I have downloaded the example sine wave generator. It works with the default settings, which give a period size of 4410. If I change the period time using the command line, it will successfully go down to 441/10000us. Any further and I get this error:

ALSA lib pcm.c:824:(snd_pcm_sw_params) snd_pcm_sw_params: params->avail_min problem for start_threshold Unable to set sw params for playback: Invalid argument
Setting of swparams failed: Invalid argument

Quoted 8 lines · Jaroslav Kysela
Quoted 5 lines · Tim Hollingsworth
Quoted 1 line

You can read/write any size.

well I can't write at 128. the question is, do I need to buffer the periods myself and sequence them into larger periods or will alsa do this for me?

Quoted 9 lines

The you have wrong sw_params settings. Check xfer_align.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#14 lore raw

Re: period size

Quoted 10 lines · Tim Hollingsworth

Thanks for your help so far Jaroslav.

I have taken another look at my project and now it's behaving differently! It still won't go down to a period size of 128.

I have downloaded the example sine wave generator. It works with the default settings, which give a period size of 4410. If I change the period time using the command line, it will successfully go down to 441/10000us. Any further and I get this error:

Quoted 4 lines

ALSA lib pcm.c:824:(snd_pcm_sw_params) snd_pcm_sw_params:
params->avail_min problem for start_threshold Unable to set sw params for playback: Invalid argument Setting of swparams failed: Invalid argument

Fixed in CVS.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#15 lore raw

src pointer parameter in copy operator

Hi all,

I have question according to the src pointer in the copy operator:
I'm writing an ALSA driver for the cogent CSB337 board. I'm testing the driver but there are some problem.
I'm trying to playback a wav file, but i hear some strange noise, not the data corresponding to the wav file.
I compared the data of the wav file and the data in the copy operator (before they sent to the codec). They are different.

Why the data pointed by the src pointer (parameter of the playback copy operator) and the data of the wav file to playback are different?

Thanks for any help.

best regards,

Mathieu rondonneau

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#16 lore raw

Re: src pointer parameter in copy operator

Quoted 10 lines · Mathieu Rondonneau

Hi all,

I have question according to the src pointer in the copy operator:
I'm writing an ALSA driver for the cogent CSB337 board. I'm testing the driver but there are some problem.
I'm trying to playback a wav file, but i hear some strange noise, not the data corresponding to the wav file.
I compared the data of the wav file and the data in the copy operator (before they sent to the codec). They are different.

Quoted 2 lines

Why the data pointed by the src pointer (parameter of the playback copy operator) and the data of the wav file to playback are different?

What prints the 'aplay -v' command?

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#17 lore raw

Re: src pointer parameter in copy operator

I don't use aplay to play the wav file but i use:
dd of=thefile.wav of=/dev/audio0

Do you think i should use aplay instead?
Is this the problem?

I'm trying to cross-compile the alsa-util library but, i have some trouble at the compilation (configure: error: No linkable libasound was found). libasound is in the --with-alsa-prefix path, so i don't understand the problem.
I'm working on it.

Thanks for any help/solution.
regards,
Mathieu Rondonneau

----- Original Message -----
From: "Jaroslav Kysela" <[email protected]>
To: "Mathieu Rondonneau" <[email protected]>
Cc: <[email protected]>
Sent: Sunday, April 04, 2004 3:10 AM
Subject: Re: [Alsa-devel] src pointer parameter in copy operator

Quoted 8 lines · Mathieu Rondonneau
Quoted 7 lines

Hi all,

I have question according to the src pointer in the copy operator:
I'm writing an ALSA driver for the cogent CSB337 board. I'm testing the driver but there are some problem.
I'm trying to playback a wav file, but i hear some strange noise, not

the

Quoted 17 lines
Quoted 6 lines

data corresponding to the wav file.
I compared the data of the wav file and the data in the copy operator (before they sent to the codec). They are different.

Why the data pointed by the src pointer (parameter of the playback copy operator) and the data of the wav file to playback are different?

What prints the 'aplay -v' command?

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

Quoted 10 lines

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#18 lore raw

Re: src pointer parameter in copy operator

Quoted 2 lines · Mathieu Rondonneau

I don't use aplay to play the wav file but i use:
dd of=thefile.wav of=/dev/audio0

This is definitely wrong. The /dev/audio devices expect mu-Law format at 8000Hz.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

#19 lore raw

Re: period size

In reply to Jaroslav Kysela
Quoted 12 lines · Jaroslav Kysela
Quoted 10 lines · Tim Hollingsworth

Thanks for your help so far Jaroslav.

I have taken another look at my project and now it's behaving differently! It still won't go down to a period size of 128.

I have downloaded the example sine wave generator. It works with the default settings, which give a period size of 4410. If I change the period time using the command line, it will successfully go down to 441/10000us. Any further and I get this error:

Quoted 6 lines
Quoted 4 lines

ALSA lib pcm.c:824:(snd_pcm_sw_params) snd_pcm_sw_params:
params->avail_min problem for start_threshold Unable to set sw params for playback: Invalid argument Setting of swparams failed: Invalid argument

Fixed in CVS.

OK cool that error has gone now. Back to newbie period size problems (*groan*). The target system has a VIA VT8233 sound chip. I tried the sine generator on another system which has a soundblaster live, and it will indeed take very low period sizes. As you said.

Can I configure the VIA chip to take the period size I want, or is it a hardware limitation? Which settings do I mess with?

TIA
Tim

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click