15 Jan
2005
15 Jan
'05
8:23 p.m.
Hi,
just for fun and for learning the system, I wanted to write a
small script which automatically configures any soundcards
(similar to alsaconf).
Based on PCI, I wanted to get all vendor and card IDs and
modprobe each ALSA module to each card found and check the
result.
Unfortunately, this doesn't seem to be that easy. Could anyone
confirm, that I cannot load a module to a certain PCI card?
Furthermore, modprobe does not give any error when probing a
module for a card I do not have.
And I found no way to get backwards the card ID for a loaded
module :( .
Does anyone know a way how I can find out which cards are in
the system and which module fits to it?
Any wee small hint is very welcome.
Best regards
ce
15 Jan
15 Jan
10:29 p.m.
Last Sunday 16 January 2005 00:24, Christoph Eckert was like:
Hi,
just for fun and for learning the system, I wanted to write a
small script which automatically configures any soundcards
(similar to alsaconf).
Based on PCI, I wanted to get all vendor and card IDs and
modprobe each ALSA module to each card found and check the
result.
Unfortunately, this doesn't seem to be that easy. Could anyone
confirm, that I cannot load a module to a certain PCI card?
Furthermore, modprobe does not give any error when probing a
module for a card I do not have.
And I found no way to get backwards the card ID for a loaded
module :( .
Does anyone know a way how I can find out which cards are in
the system and which module fits to it?
Any wee small hint is very welcome.
At a guess & I ain't an expert, I would have thought that a look at the source
code for alsaconf, kudzu &/ discover or even soundconfig or whatever would be
enlightening here. Or even just the man pages:
Kudzu detects the current hardware, and checks it against
a database stored in /etc/sysconfig/hwconf.
discover provides an extensible hardware detection and reporting inter-
face. Hardware information is stored in an XML data format and can be
retrieved across the network. Try /usr/share/list.xml.
If you can come up with something that works better than alsaconf on Debian
(i.e. works ;-) I for one will be interested in your results.
Not quite in the same league, but also very useful is
http://alsa.opensrc.org/?aadebug for simple alsa diagnostics.
cheers
tim hall
http://glastonburymusic.org.uk
16 Jan
16 Jan
9:46 a.m.
Hi,
At a guess & I ain't an expert, I would have
thought that a
look at the source code for alsaconf, kudzu &/ discover or
even soundconfig or whatever would be enlightening here. Or
even just the man pages:
Kudzu detects the current hardware, and checks it against
a database stored in /etc/sysconfig/hwconf.
discover provides an extensible hardware detection and
reporting inter- face. Hardware information is stored in
an XML data format and can be retrieved across the network.
Try /usr/share/list.xml.
Well, I'm not really a programmer, but I have of course read
alsaconf (still I didn't understand everything) and yesterday
I downloaded soundconfig from the knoppix distribution.
If you can come up with something
that works better than alsaconf on Debian (i.e. works ;-) I
for one will be interested in your results.
Hehe, most probably I will give up ;-) .
Not quite in
the same league, but also very useful is
http://alsa.opensrc.org/?aadebug for simple alsa
diagnostics.
OK, I'll have a look at it.
Thanks for your thouhts, and BTW I liked f_f__f_f ;-) .
Best regards
ce
17 Jan
17 Jan
7:32 a.m.
Last Sunday 16 January 2005 13:47, Christoph Eckert was like:
cheers, actually it's called f+f-f+f, but you can't use +/- in filenames,
perhaps I should spell it out. I'm quite close to finishing the larger piece
that it's part of. Unfortunately I can't run Ardour at the same time as
Rosegarden (600Mhz CPU / 256 MB RAM), which is frustrating, so I'm having to
think of some interesting workarounds in order to realise the piece.
I may be some time.
cheers
tim hall
http://glastonburymusic.org.uk
Hehe, most probably I will give up ;-) .
Oh well, I'm no C programmer either, maybe one day.
... Scripting is fun. :)
Not quite in
the same league, but also very useful is
http://alsa.opensrc.org/?aadebug for simple alsa
diagnostics.
OK, I'll have a look at it.
Thanks for your thouhts, and BTW I liked f_f__f_f ;-) . 
18 Jan
18 Jan
4:13 a.m.
On Mon, Jan 17, 2005 at 11:32:12AM +0000, tim hall wrote:
cheers, actually it's called f+f-f+f, but you
can't use +/- in filenames,
Actually, you can. I do it all the time. It's not a good idea to use
"-" as the first character, though, because it becomes almost impossible
to use the name on the command line without it being interpreted as an
option to whatever command you're using.
Chuck
4:45 a.m.
Chuck Martin wrote:
Actually, you can. I do it all the time. It's not a good idea to use
"-" as the first character, though, because it becomes almost impossible
to use the name on the command line without it being interpreted as an
option to whatever command you're using.
In that case, you can always use absolute paths, or adding ./ in front
the filename. I have some directories which begin with a -; to go there,
cd ./-whatever is ok. It may cause problems for some scripting features,
but I've never encoutered any so far,
David
9:49 a.m.
Last Tuesday 18 January 2005 08:14, Chuck Martin was like:
On Mon, Jan 17, 2005 at 11:32:12AM +0000, tim hall
wrote:
Sorry, I meant url not filename.
and that should be 'f+f--f+f' anyway. ;-]
cheers
tim hall
http://glastonburymusic.org.uk
cheers, actually it's called f+f-f+f, but you
can't use +/- in filenames,
Actually, you can. I do it all the time. It's not a good idea to use
"-" as the first character, though, because it becomes almost impossible
to use the name on the command line without it being interpreted as an
option to whatever command you're using.
20 Jan
20 Jan
1:02 a.m.
On Tue, Jan 18, 2005 at 01:49:31PM +0000, tim hall wrote:
Sorry, I meant url not filename.
and that should be 'f+f--f+f' anyway. ;-]
They can be used in URLs, too. Actually, all characters can be used if
they're encoded as a "%" followed by a two character hex code, but that
shouldn't be necessary for either "+" or "-". The ones that need
to be
encoded are listed in RFC 1738.
Chuck
16 Jan
16 Jan
2:16 a.m.
Vendor IDs can be found under the /proc/pci. Most modules do actually
give the option of loading with a certain vendor id if they support more
than one chipset.
A more reliable thing you can do is check to see which card was loaded
by comparing /proc/pci with /proc/asound/cards, both of which list
unique characteristics that can be used to determine if a card was
loaded (or if more than one was loaded, etc). Just to be
clear, /proc/pci lists everything on your PCI bus. /proc/asound/cards
lists all cards for which you have loaded modules.
This technique could easily generalize to also checking other buses,
such as USB, firewire, or CardBus.
I wonder if any of the hardware detection systems use this approach
(looking through proc to see what turned up)?
On Sun, 2005-01-16 at 01:24 +0100, Christoph Eckert wrote:
Hi,
just for fun and for learning the system, I wanted to write a
small script which automatically configures any soundcards
(similar to alsaconf).
Based on PCI, I wanted to get all vendor and card IDs and
modprobe each ALSA module to each card found and check the
result.
Unfortunately, this doesn't seem to be that easy. Could anyone
confirm, that I cannot load a module to a certain PCI card?
Furthermore, modprobe does not give any error when probing a
module for a card I do not have.
And I found no way to get backwards the card ID for a loaded
module :( .
Does anyone know a way how I can find out which cards are in
the system and which module fits to it?
Any wee small hint is very welcome.
Best regards
ce
--
9:52 a.m.
Vendor IDs can be found under the /proc/pci. Most
modules
do actually give the option of loading with a certain
vendor id if they support more than one chipset.
When using modinfo $MODULENAME, I see the parameters:
parm: index:Index value
parm: id:ID string
But what are the ID and index strings compared to
cat /proc/pci, and how can I use them in conjunction with
modprobe?
I have googled yesterday, but I didn't find matching pages.
Most people load modules without parameters.
A more reliable thing you can do is check to see which
card
was loaded by comparing /proc/pci with /proc/asound/cards,
both of which list unique characteristics that can be used
to determine if a card was loaded (or if more than one was
loaded, etc). Just to be clear, /proc/pci lists everything
on your PCI bus. /proc/asound/cards lists all cards for
which you have loaded modules.
Interesting idea, thanks.
Best regards
ce
8:30 a.m.
On Sun, 16 Jan 2005 01:24:32 +0100
mchristoph.eckert(a)t-online.de (Christoph Eckert) wrote:
Furthermore, modprobe does not give any error when
probing a
module for a card I do not have.
I think this is a feature of the 2.6.x kernels.. I'm not sure though
what reason is behind changing the module loading behavior like this
(maybe for hotplugging??).
flo
--
Palimm Palimm!
http://affenbande.org/~tapas/
9:54 a.m.
I think this is a feature of the 2.6.x kernels..
I'm not
sure though what reason is behind changing the module
loading behavior like this (maybe for hotplugging??).
Maybe. I load the snd-usb-audio-module during boottime, even
if my USB cards are not present, and it does.
Best regards
ce
7295
days inactive
7300
days old
linux-audio-user@lists.linuxaudio.org
11 comments
6 participants
participants (6)
-
Chuck Martin -
David Cournapeau -
Florian Schmidt -
mchristoph.eckert＠t-online.de -
Rusty Phillips -
tim hall