asfxload on 2.6.18.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have a AWE64 card:

kernel: isapnp: Card 'Creative SB AWE64  PnP'

I am having problems getting it to play midi files using aplaymidi,
playmidi and the like. It has worked happily in the past.

Yesterday, after several hours of experimentation I mananaged to get
asfxload to load fonts, and playmidi would then work with some of them.
Since I was floundering around, I don't have a clear idea of what I did,
but I certainly had to manually load a large number of modules before
the messages like "No Emux synth hwdep device is found" from afsxload
went away. (This is on a debian sarge system, but with stock 2.6.18.3
kernel). Likewise, playmidi eventually stopped complaining "No playback
device found". (strace showed at that point that /dev/sequencer was
being opened successfully, but then a couple of ioctls failed.)

Above is background information and shows that the hardware is fine and
can (almost) work with 2.6.18.3 with the modules that I have compiled.

Today, I had hoped to dig a bit deeper understand the problem, but I
cannot even get as far as yesterday :-(

At this point I have:

$ asfxload
No Emux synth hwdep device is found

The modules loaded are:
----------------------------------------------------------------------------------
~# lsmod|grep snd
snd_rtctimer            2688  0
snd_emux_synth         34560  0
snd_seq_virmidi         5504  1 snd_emux_synth
snd_seq_midi_emul       6752  1 snd_emux_synth
snd_seq_oss            31904  0
snd_seq_midi            6528  0
snd_seq_midi_event      5728  3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq                47056  8
snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_util_mem            3520  1 snd_emux_synth
snd_sbawe              31168  0
snd_opl3_lib            9088  1 snd_sbawe
snd_sb16_dsp            9376  1 snd_sbawe
snd_sb16_csp           18368  1 snd_sbawe
snd_sb_common          14592  3 snd_sbawe,snd_sb16_dsp,snd_sb16_csp
snd_hwdep               7268  3 snd_emux_synth,snd_opl3_lib,snd_sb16_csp
snd_mpu401_uart         6688  1 snd_sbawe
snd_rawmidi            19520  3 snd_seq_virmidi,snd_seq_midi,snd_mpu401_uart
snd_seq_device          6636  7
snd_emux_synth,snd_seq_oss,snd_seq_midi,snd_seq,snd_sbawe,snd_opl3_lib,snd_rawmidi
snd_pcm_oss            44160  0
snd_mixer_oss          16288  1 snd_pcm_oss
snd_pcm                72392  3 snd_sbawe,snd_sb16_dsp,snd_pcm_oss
snd_timer              20132  4 snd_rtctimer,snd_seq,snd_opl3_lib,snd_pcm
snd                    44612  17
snd_emux_synth,snd_seq_virmidi,snd_seq_oss,snd_seq,snd_sbawe,snd_opl3_lib,snd_sb16_dsp,snd_sb16_csp,snd_sb_common,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
snd_page_alloc          8232  1 snd_pcm
soundcore               7328  1 snd
rtc                    10132  2 snd_rtctimer
-------------------------------------------------------------------------------------------------

I am thus puzzled why asfxload can't see the device.

I am also puzzled by
-------------------------------------------------------
#cat /proc/asound/oss/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.12rc1 emulation code)
Kernel: Linux conquest3 2.6.18.3 #1 Sun Nov 19 13:23:25 GMT 2006 i686
Config options: 0

Installed drivers:
Type 10: ALSA emulation

Card config:
Sound Blaster 16 at 0x220, irq 10, dma 1&5

Audio devices:
0: DSP v4.16 (DUPLEX)

Synth devices: NOT ENABLED IN CONFIG

Midi devices:
0: Sound Blaster 16 MIDI

Timers:
7: system timer

Mixers:
0: CTL1745

--------------------------------------------------------------

The above
  Synth devices: NOT ENABLED IN CONFIG
yet
  snd_seq_oss, snd_emux_synth and snd_seq_device
are all loaded.

An extract from strace on asfxload gives:
-----------------------------------

open("/dev/snd/controlC0", O_RDONLY)    = 3
close(3)                                = 0
open("/dev/snd/hwC0D2", O_RDONLY)       = -1 ENODEV (No such device)
open("/dev/snd/controlC0", O_RDONLY)    = 3
close(3)                                = 0
open("/dev/snd/hwC0D2", O_RDONLY)       = -1 ENODEV (No such device)
stat64("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=7640,
...}) = 0
open("/dev/snd/controlC1", O_RDONLY)    = -1 ENODEV (No such device)
open("/dev/aloadC1", O_RDONLY)          = -1 ENODEV (No such device)
stat64("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=7640,
...}) = 0
open("/dev/snd/controlC2", O_RDONLY)    = -1 ENODEV (No such device)
open("/dev/aloadC2", O_RDONLY)          = -1 ENODEV (No such device)
stat64("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=7640,
...}) = 0
open("/dev/snd/controlC3", O_RDONLY)    = -1 ENODEV (No such device)
open("/dev/aloadC3", O_RDONLY)          = -1 ENODEV (No such device)
stat64("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=7640,
...}) = 0
open("/dev/snd/controlC4", O_RDONLY)    = -1 ENOENT (No such file or
directory)
open("/dev/aloadC4", O_RDONLY)          = -1 ENOENT (No such file or
directory)
stat64("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=7640,
...}) = 0
open("/dev/snd/controlC5", O_RDONLY)    = -1 ENOENT (No such file or
directory)
open("/dev/aloadC5", O_RDONLY)          = -1 ENOENT (No such file or
directory)
stat64("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=7640,
...}) = 0
open("/dev/snd/controlC6", O_RDONLY)    = -1 ENOENT (No such file or
directory)
open("/dev/aloadC6", O_RDONLY)          = -1 ENOENT (No such file or
directory)
stat64("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=7640,
...}) = 0
open("/dev/snd/controlC7", O_RDONLY)    = -1 ENOENT (No such file or
directory)
open("/dev/aloadC7", O_RDONLY)          = -1 ENOENT (No such file or
directory)
write(2, "No Emux synth hwdep device is fo"..., 36No Emux synth hwdep
device is found
) = 36
----------------------------------------------------

Before I go any further, can someone tell me what is wrong at this
stage? Perhaps the modules must be loaded in  different order?

In passing, I would also be grateful for pointers for introductory
documentation for alsa. I did browse some of the API documentation, but
lacked any overview to put the details in context.

Thanks in anticipation for any help or hints...

A Lawrence

PS. I found many messages reporting similar problems, but all seemed to
be either simple failure to load modules, or were not apparently
resolved. Sometimes people were told to use timidity instead!

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user

[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux