Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: hitsware on July 21, 2012, 06:41:17 PM

Title: ALSA aconnect
Post by: hitsware on July 21, 2012, 06:41:17 PM

When I type:

$ aconnect -o

I get:

ALSA lib seq_hw.c:457:(snd_seq_hw_open) /dev/snd/seq failed:
No such file or directory

This is similar to the problem I had with SmallBasic.
What am I missing here ?

Title: Re: ALSA aconnect
Post by: Rich on July 21, 2012, 11:40:13 PM

Hi hitsware
You need to learn to provide more relevant information when asking questions.
What kind of audio card do you have.
Enter  dmesg | less  and use the PageDown key to view the result. Is your card recognized during the boot process?
What does the output of   lsmod   show?
Does the  /dev/snd  directory exist?

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 01:13:51 AM

> What kind of audio card do you have ?

http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-d425kt.html

Title: Re: ALSA aconnect
Post by: Rich on July 22, 2012, 01:47:44 AM

Hi hitsware
Install  pci-utils.tcz  and run  lspci -k, post the results.

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 11:04:13 AM

Rich,
Thank You again :)

I think the soundcard (motherboard) is recognized because $speaker-test works.
The problem is in the midi .......$aconnect doesn't work

$dmesg | less
HDA Intel

$cat /proc/asound/cards
0[Intel  ]: HDA-Intel

$lsmod
I don't see any /dev/snd

$lsmod | grep mid
nothing

$lspci -k
usb controller
pci bridge
isa bridge
ide interface
smbus
ethernet controller

Title: Re: ALSA aconnect
Post by: curaga on July 22, 2012, 11:55:12 AM

I don't think any integrated card does midi. You'll need to emulate it (use timidity for example).

Title: Re: ALSA aconnect
Post by: Rich on July 22, 2012, 12:05:55 PM

Hi hitsware

Quote

$lsmod
I don't see any /dev/snd

Nor would I expect you to. Lsmod tells you which modules (drivers) you currently have loaded.
If you execute   ls /dev/snd  , does it return any entries?
If you can't post directly from this machine, you can redirect the output of commands to a file like this:

Code: [Select]

lsmod > lsmod.txt
ls /dev/snd > devsnd.txtYou can then copy those files to a USB thumb drive and access them from the machine you use to post.
I don't see any audio controller returned by the lspci command. Install  gzip.tcz  and  wget.tcz. Then:

Code: [Select]

sudo update-pciids
lspci knn

Quote

I don't think any integrated card does midi. You'll need to emulate it (use timidity for example).

If he can get  amidi  to work he might be able to call that from his sbasic program, if that suits his purpose.

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 12:36:44 PM

Quote from: curaga on July 22, 2012, 11:55:12 AM

I don't think any integrated card does midi. You'll need to emulate it (use timidity for example).

Right ........... Windows uses:
"
Microsoft GS Wavetable SW Synth
The Microsoft GS Wavetable SW Synth included in versions of Direct X as an integral part of DirectMusic is a version of the Roland Virtual Sound Canvas with GS sound set licensed by Microsoft from Roland Corporation in 1996.[1] The wavetable file about 3 MiB in size is named "GM.DLS" which tells us that the wavetable is in DLS format.
"

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 12:52:07 PM

$ls /dev/snd

by-path/ control IC0 hw C0D0 pcm C0D0c pcm C0D0p timer

I got Fluidsynth since supposedly it has the soundbank built in.

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 12:59:22 PM

> If he can get  amidi  to work he might be able to call
> that from his sbasic program, if that suits his purpose.

Preciseamundo !

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 06:44:47 PM

Evedently I should have with            $ lsmod | grep mid
something like:

snd_seq_midi
snd_rawmidi
snd_seq_midi_event
snd_seq
snd_seq_device

And I have nothing
Where do I find these and how do I load them ?

Title: Re: ALSA aconnect
Post by: Rich on July 22, 2012, 08:11:10 PM

Hi hitsware
Maybe try the modprobe command?

Code: [Select]

sudo modprobe snd_seq_midi

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 09:19:43 PM

I think none of them are there.
How can I list available modules ?
( I really gotta get a hardcopy Linux primer. Any suggestions ?)
Maybe Linux for Dimwits ?

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 09:34:06 PM

Nevermind      Duh      forgot the ' sudo '

Title: Re: ALSA aconnect
Post by: hitsware on July 22, 2012, 11:15:45 PM

Still yet ..........

> How can I list available modules ?

Title: Re: ALSA aconnect
Post by: Rich on July 23, 2012, 01:16:52 AM

Hi hitsware

Quote

> How can I list available modules ?

To see which modules are available on you machine, look under:
/usr/local/lib/modules/3.0.21-tinycore/kernel/
Or if you are just want to see what's available in an extension, you could, for example, open AppBrowser,
go to alsa-modules-3.0.21-tinycore.tcz, and click on the Files tab.

Title: Re: ALSA aconnect
Post by: hitsware on July 23, 2012, 11:54:09 AM

What's the whole command for finding the list ?
My modprobe worked before, but I started over
and now get files not found.
Are those (snd_seq et al) there to begin with,
or do the apps put them there on installation ?

Title: Re: ALSA aconnect
Post by: hitsware on July 23, 2012, 12:32:00 PM

Alsa loads them. Now they're back (after installing Alsa)
But OSS doesn't ............ OSS doesn't need them ?
Maybe the modprobe isn't needed. It doesn't make sense
to have to do that. Alsa should do that itself if needed.

Title: Re: ALSA aconnect
Post by: Rich on July 23, 2012, 02:49:27 PM

Hi hitsware
You should not be installing both Alsa and OSS.

Title: Re: ALSA aconnect
Post by: tinypoodle on July 23, 2012, 04:07:01 PM

Last I checked midi support under OSS was kind of work in progress...

Title: Re: ALSA aconnect
Post by: hitsware on July 23, 2012, 04:49:29 PM

> You should not be installing both Alsa and OSS.

I'm not. 2 differant sticks.

> Last I checked midi support under OSS was kind of work in progress...

??? ...... The new version is 4.2xxx     The page is not succint on whether midi is
supported but from the detail given hints at it.

http://manuals.opensound.com/developer/MIDI.html

 Jack with OSS shows a sorta midimapper but claims I'm missing something
and won't hook up the midi. Sorta like the same thing Alsa does. I'm missing
something basic here and there seems not to be an abundance of documentation.
 

Title: Re: ALSA aconnect
Post by: tinypoodle on July 23, 2012, 05:05:16 PM

Quote from: hitsware on July 23, 2012, 04:49:29 PM

> Last I checked midi support under OSS was kind of work in progress...

??? ...... The new version is 4.2xxx     The page is not succint on whether midi is
supported but from the detail given hints at it.

http://manuals.opensound.com/developer/MIDI.html

My last post was written in full awareness/knowledge of the page you link to...

Title: Re: ALSA aconnect
Post by: tinypoodle on July 23, 2012, 05:15:10 PM

Quote from: hitsware on July 23, 2012, 04:49:29 PM

Jack with OSS shows a sorta midimapper but claims I'm missing something
and won't hook up the midi. Sorta like the same thing Alsa does. I'm missing
something basic here and there seems not to be an abundance of documentation.

Maybe you are still missing the implication of Reply #5 ??

Title: Re: ALSA aconnect
Post by: hitsware on July 23, 2012, 06:46:23 PM

> My last post was written in full awareness/knowledge of the page you link to...

You mean it might not work even they give instructions that imply it does ?

> Maybe you are still missing the implication of Reply #5 ??

I understand about the need for a synth. Is the implication it should be Timidity ?
Let me restate that I do get sound with both OSS and Alsa. Just can't get midi going.

Title: Re: ALSA aconnect
Post by: tinypoodle on July 24, 2012, 02:47:06 AM

Please post output of:

cat /proc/asound/devices
cat /proc/asound/seq/clients

Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 07:29:41 AM

tc@box:~$ cat/proc/asound/devices
sh: cat/proc/asound/devices: not found
tc@box:~$
c@box:~$ cat/proc/asound/seq/clients
sh: cat/proc/asound/seq/clients: not found
tc@box:~$

Title: Re: ALSA aconnect
Post by: Juanito on July 24, 2012, 07:37:22 AM

You need a space between "cat" and "/proc":

Code: [Select]

$ cat /proc/asound/devices
  1:        : sequencer
  2: [ 0- 8]: digital audio playback
  3: [ 0- 7]: digital audio playback
  4: [ 0- 3]: digital audio playback
  5: [ 0- 1]: digital audio playback
  6: [ 0- 1]: digital audio capture
  7: [ 0- 0]: digital audio playback
  8: [ 0- 0]: digital audio capture
  9: [ 0- 3]: hardware dependent
 10: [ 0- 0]: hardware dependent
 11: [ 0]   : control
 33:        : timer

$ cat /proc/asound/seq/clients
Client info
  cur  clients : 3
  peak clients : 3
  max  clients : 192

Client   0 : "System" [Kernel]
  Port   0 : "Timer" (Rwe-)
  Port   1 : "Announce" (R-e-)
    Connecting To: 15:0
Client  14 : "Midi Through" [Kernel]
  Port   0 : "Midi Through Port-0" (RWe-)
Client  15 : "OSS sequencer" [Kernel]
  Port   0 : "Receiver" (-we-)
    Connected From: 0:1


Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 08:25:07 AM

tc@box:~$ cat /proc/asound/devices
  2: [ 0- 1]: digital audio playback
  3: [ 0- 0]: digital audio playback
  4: [ 0- 0]: digital audio capture
  5: [ 0- 2]: hardware dependent
  6: [ 0]   : control
 33:        : timer
tc@box:~$ cat /proc/asound/seq/clients
cat: can't open '/proc/asound/seq/clients': No such file or directory
tc@box:~$

Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 08:34:03 AM

FWIW

tc@box:~$ /usr/local/etc/init.d/alsasound start

rmmod: can't unload 'snd_pcm': Operation not permitted
rmmod: can't unload 'snd_timer': Operation not permitted
rmmod: can't unload 'snd': Operation not permitted
rmmod: can't unload 'snd_hda_codec_idt': Operation not permitted
rmmod: can't unload 'snd_hda_intel': Operation not permitted
rmmod: can't unload 'snd_hda_codec': Operation not permitted
rmmod: can't unload 'snd_hwdep': Operation not permitted
rmmod: can't unload 'snd_pcm': Operation not permitted
rmmod: can't unload 'snd_timer': Operation not permitted
rmmod: can't unload 'snd': Operation not permitted
rmmod: can't unload 'snd_hda_codec_idt': Operation not permitted
rmmod: can't unload 'snd_hda_intel': Operation not permitted
rmmod: can't unload 'snd_hda_codec': Operation not permitted
rmmod: can't unload 'snd_hwdep': Operation not permitted
rmmod: can't unload 'snd_pcm': Operation not permitted
rmmod: can't unload 'snd_timer': Operation not permitted
rmmod: can't unload 'snd': Operation not permitted
rmmod: can't unload 'snd_hda_codec_idt': Operation not permitted
rmmod: can't unload 'snd_hda_intel': Operation not permitted
rmmod: can't unload 'snd_hda_codec': Operation not permitted
rmmod: can't unload 'snd_hwdep': Operation not permitted
rmmod: can't unload 'snd_pcm': Operation not permitted
rmmod: can't unload 'snd_timer': Operation not permitted
rmmod: can't unload 'snd': Operation not permitted
rmmod: can't unload 'snd_hda_codec_idt': Operation not permitted
rmmod: can't unload 'snd_hda_intel': Operation not permitted
rmmod: can't unload 'snd_hda_codec': Operation not permitted
rmmod: can't unload 'snd_hwdep': Operation not permitted
rmmod: can't unload 'snd_pcm': Operation not permitted
rmmod: can't unload 'snd_timer': Operation not permitted
rmmod: can't unload 'snd': Operation not permitted
rmmod: can't unload 'snd_hda_codec_idt': Operation not permitted
rmmod: can't unload 'snd_hda_intel': Operation not permitted
rmmod: can't unload 'snd_hda_codec': Operation not permitted
rmmod: can't unload 'snd_hwdep': Operation not permitted
rmmod: can't unload 'snd_pcm': Operation not permitted
rmmod: can't unload 'snd_timer': Operation not permitted
rmmod: can't unload 'snd': Operation not permitted
rmmod: can't unload 'snd_hda_codec_idt': Operation not permitted
rmmod: can't unload 'snd_hda_intel': Operation not permitted
rmmod: can't unload 'snd_hda_codec': Operation not permitted
rmmod: can't unload 'snd_hwdep': Operation not permitted
rmmod: can't unload 'snd_pcm': Operation not permitted
rmmod: can't unload 'snd_timer': Operation not permitted
rmmod: can't unload 'snd': Operation not permitted
Starting sound driver: snd-hda-intel 
modprobe: can't load module snd_mixer_oss (kernel.tclocal/sound/core/oss/snd-mixer-oss.ko.gz): Operation not permitted
modprobe: can't load module snd_seq_device (kernel.tclocal/sound/core/seq/snd-seq-device.ko.gz): Operation not permitted
modprobe: can't load module snd-mixer-oss (kernel.tclocal/sound/core/oss/snd-mixer-oss.ko.gz): Operation not permitted
cut: /proc/asound/seq/drivers: No such file or director

Title: Re: ALSA aconnect
Post by: Juanito on July 24, 2012, 08:42:17 AM

How about :

Code: [Select]

$ sudo /usr/local/etc/init.d/alsasound start

Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 08:57:25 AM

Geez ...... Should have the 'sudo' on the apps info directions
Or should I have known that ?
If so what's the indicator ?

Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 09:08:47 AM

c@box:~$ sudo /usr/local/etc/init.d/alsasound start
rmmod: can't unload 'snd_hda_codec_idt': Resource temporarily unavailable
rmmod: can't unload 'snd_hda_codec': Resource temporarily unavailable
rmmod: can't unload 'snd_hwdep': Resource temporarily unavailable
rmmod: can't unload 'snd_pcm': Resource temporarily unavailable
rmmod: can't unload 'snd_timer': Resource temporarily unavailable
rmmod: can't unload 'snd': Resource temporarily unavailable
Starting sound driver: snd-hda-intel 
tc@box:~$

Title: Re: ALSA aconnect
Post by: Juanito on July 24, 2012, 09:11:40 AM

'Probably better to reboot and then try.

Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 09:29:00 AM

tc@box:~$ sudo /usr/local/etc/init.d/alsasound start
rmmod: can't unload 'snd_hda_codec_idt': Resource temporarily unavailable

rmmod: can't unload 'snd_hda_codec': Resource temporarily unavailable
rmmod: can't unload 'snd_hwdep': Resource temporarily unavailable
rmmod: can't unload 'snd_pcm': Resource temporarily unavailable
rmmod: can't unload 'snd_timer': Resource temporarily unavailable
rmmod: can't unload 'snd': Resource temporarily unavailable
Starting sound driver: snd-hda-intel 
tc@box:~$
tc@box:~$

Title: Re: ALSA aconnect
Post by: tinypoodle on July 24, 2012, 09:42:31 AM

So you neither have any sequencer nor any raw midi device.

alsa wouldn't load any drivers for non existent hardware (here they get autoloaded).

Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 10:58:00 AM

After downloading FluidSynth (should install itself ?)

tc@box:~$ sudo /usr/local/etc/init.d/alsasound start
rmmod: can't unload 'snd_hda_codec_idt': Resource temporarily unavailable


rmmod: can't unload 'snd_hda_codec': Resource temporarily unavailable
rmmod: can't unload 'snd_hwdep': Resource temporarily unavailable
rmmod: can't unload 'snd_pcm': Resource temporarily unavailable
rmmod: can't unload 'snd_timer': Resource temporarily unavailable
rmmod: can't unload 'snd': Resource temporarily unavailable
Starting sound driver: snd-hda-intel 
tc@box:~$
tc@box:~$
tc@box:~$

Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 04:31:38 PM

Does this have any revelence ?

http://www.alsa-project.org/main/index.php/Matrix:Module-hda-intel

Title: Re: ALSA aconnect
Post by: hitsware on July 24, 2012, 07:17:36 PM

Or maybe this :

https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture#Configuration