Oh no,
truthfully it isn't the only problem I am having with hardware. But I am
not so sure I will dump my distro do quick.
I got my internet connection down pat and now I have no interest in
starting from scratch.
I have tried Suse in the past but I just didn't like it.
I will try a little more tinkering and I will then try some more before
I give up.
this is strange for me because so many things work for me in Mandrake.
I now see the sequencer in /dev after i ran the script in the tar file.
what flags do I use with sfxtest?

could you go over again how I load sound fonts??
Thanks
Aaron

These are two issues I didn't touch.
Is there a way to test the /dev/sequencer directly.
What about permissions??

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


On Thu, 2003-01-16 at 02:02, Phil Kerr wrote:
> Mandrake..... Hmmmm :)
> 
> I've had the most problems with Mandrake, which is a real pity as it's  
> a nice dist.  I tried 9.0 when it came out and the network config was 
> badly broken so I didn't look at MIDI.   I recommend Suse as they 
> support the ALSA dev team directly and audio and MIDI works great 
> straight out of the box (although the installer with 8.1 is slightly 
> broken).
> 
> Put the symlink in and start it, if everything works.... hurrah!  if 
> not :(
> 
> A suggestion would be to totally remove ALSA from your system and then 
> install ALSA from the tarballs.
> 
>                                                                    
> *WARNING*
> This may break things, so the usual disclaimers apply :)  Back up your 
> important data.....
> 
>   Run the following command:
> 
> rpm -qa|grep alsa-
> 
> This will show all the alsa packages installed.  Check to see that the 
> list doesn't contain packages like alsamixer, if it does you will have 
> to remove the main packages by hand.  If  the list of installed 
> packages look ok (and *only* if the list looks good) run the following.
> 
> rpm -e `rpm -qa|grep alsa-`
> 
> You will probably have lots of dependancy warnings, it's your call now 
> to run this (and it is a dangerous command!):
> 
> rpm -e --nodeps `rpm -qa|grep alsa-`
> 
> Because you will be installing ALSA by hand, once everything is back on 
> these dependancy problems *should* be resolved again.
> 
> Next, following the install section in the HOWTO, install ALSA.
> 
> This has worked for me on a number of different systems including 
> Mandrake, but it has failed once or twice and it was easier to 
> reinstall everything then.
> 
> The ALSA community are normally good at solving problems which the 
> HOWTO can't resolve and Clemens is one of the main ALSA developers.
> 
> If this fails to fix the problem then things get very difficult for me 
> to diagnose via email, often it's a problem even when you are sitting 
> at the machine.  Your keyboard is a reasonable one so I doubt it's that 
> causing the problem.  As you are now Windows free and really need a 
> running system I suggest trying Suse.  Redhat is ok but the last 
> version (8.0 I think) I played with did not include ALSA (OSS was 
> installed) so you may have to install the tarballs by hand.
> 
> Just guessing from your ISP you are based in Israel..... I'm in 
> Scotland :)
> 
> Phil
> 
> On Thursday, Jan 16, 2003, at 01:03 Europe/London, Aaron Mehl wrote:
> 
> > wow thanks for the post,
> > I gather we are in different time zones.
> >
> > On Thu, 2003-01-16 at 00:14, Phil Kerr wrote:
> >> Hi,
> >>
> >> I've checked your posting to the alsa list and it looks like between
> >> Clemens and I we've covered most of the 'usual suspect' type of
> >> problems.
> > Thanks I was sort of worried about bothering on and off the list like
> > that, I really appreciate your help.
> >
> >>
> >> sndstat does show no on-board synth device as you point out so this
> >> does look like the problem.  Do you have any external MIDI devices you
> >> can use apart from your keyboard (what keyboard is it btw?).
> >
> > Roland E-28, when I use note edit I can add notes with no problem and I
> > (I may be wrong) think I heard it play from the computer speakers.
> >>   Your
> >> external MIDI port seems to be configured ok.  If you can send MIDI
> >> data to an external device using a midiplayer such as pmidi, as 
> >> Clemens
> >> suggested, it would indicate a problem loading the soundfonts.
> >>
> >> Can you run sxftest?  I guess it's going to fail but it's worth a test
> >> :)
> > -------------------snip---------------------------------
> > I wasn't sure what flag to run so I ran I
> >
> >> [root@aamehl midi2abc]# sfxtest I
> > init done
> > argc=2
> > [1] initialize chip
> > finishing..
> > [root@aamehl midi2abc]#
> > --------------------------------snip-----------------------
> >> Another thing is to check in /etc/init.d for the alsa start script and
> >> check if there is a symbolic link in the runlevel you normally use, 
> >> cat
> >> /etc/inittab and look for a line near the top of the file similar to
> >> this:
> >>
> >> id:5:initdefault:
> >>
> >> This is set for a machine to boot straight into X but if you boot into
> >> console mode it should be 3.  I've had weird problems before when the
> >> alsa startup script hasn't been run and it's been with /dev/sequencer,
> >> this is normally set-up when you run snddevices.
> >>
> >> Have a look in /etc/init.d/rcX.d for the symbolic link (X = your
> >> runlevel as noted above).
> >>
> >> If it's there try restarting it.
> >
> > no I don't see such a link or rc at all there is alsa.
> >>
> >> All the modules look ok so this is a bit of a long-shot :(  Have a 
> >> look
> >> in /var/log/messages to see if there are any errors showing up
> >> regarding ALSA or your soundcard.  Try running sfxload again and see 
> >> if
> >> anything is reported.
> >>
> >> What distribution of Linux are you using and what version of ALSA have
> >> you got.  Did you install it yourself or did your dist configure it 
> >> for
> >> you?
> > Mandrake 9.0 it has ALSA with the latest drivers. I didn't do it 
> > myself,
> > but in the course of these emails, I downloaded the tar of the drivers
> > to try running snddevices. which gave me errors. But they could be
> > because the drivers are already installed.
> >
> > The reason I am persisting is because I dumped windows and now only 
> > have
> > Linux. As a result I am doing my notation projects in Linux and I must
> > have the ability to hear the files I create.
> >
> > Thanks for you help so far.
> > Aaron
> >
> > [root@aamehl alsa-driver-0.9.0rc6]# sh sndd
> > snddevices     snddevices.in
> > [root@aamehl alsa-driver-0.9.0rc6]# sh snddevices
> > Creating /dev/mixer?... done
> > Creating /dev/sequencer... done
> > Creating /dev/midi?... done
> > Creating /dev/dsp?... done
> > Creating /dev/audio?... done
> > Creating /dev/sndstat... done
> > Creating /dev/music... done
> > Creating /dev/dmmidi?... done
> > Creating /dev/dmfm?... done
> > Creating /dev/amixer?... done
> > Creating /dev/adsp?... done
> > Creating /dev/amidi?... done
> > Creating /dev/admmidi?... done
> > create symbolic link `/dev/mixer' to `/dev/mixer0'
> > create symbolic link `/dev/midi' to `/dev/midi0'
> > create symbolic link `/dev/dsp' to `/dev/dsp0'
> > create symbolic link `/dev/audio' to `/dev/audio0'
> > create symbolic link `/dev/sequencer2' to `/dev/music'
> > create symbolic link `/dev/adsp' to `/dev/adsp0'
> > create symbolic link `/dev/amidi' to `/dev/amidi0'
> > mv: cannot move `/dev/sndstat' to `/dev/1sndstat': Operation not
> > permitted
> > rm: cannot remove `/dev/snd': Is a directory
> > mv: cannot stat `/dev/1sndstat': No such file or directory
> > rm: cannot remove `/dev/snd/controlC0': Operation not permitted
> > rm: cannot remove `/dev/snd/controlC1': Operation not permitted
> > rm: cannot remove `/dev/snd/controlC2': Operation not permitted
> > rm: cannot remove `/dev/snd/controlC3': Operation not permitted
> > rm: cannot remove `/dev/snd/controlC4': Operation not permitted
> > rm: cannot remove `/dev/snd/controlC5': Operation not permitted
> > rm: cannot remove `/dev/snd/controlC6': Operation not permitted
> > rm: cannot remove `/dev/snd/controlC7': Operation not permitted
> > rm: cannot remove `/dev/snd/hwC0D0': Operation not permitted
> > rm: cannot remove `/dev/snd/midiC0D0': Operation not permitted
> > rm: cannot remove `/dev/snd/midiC0D1': Operation not permitted
> > rm: cannot remove `/dev/snd/midiC0D2': Operation not permitted
> > rm: cannot remove `/dev/snd/pcmC0D0c': Operation not permitted
> > rm: cannot remove `/dev/snd/pcmC0D0p': Operation not permitted
> > rm: cannot remove `/dev/snd/pcmC0D1c': Operation not permitted
> > rm: cannot remove `/dev/snd/pcmC0D2c': Operation not permitted
> > rm: cannot remove `/dev/snd/pcmC0D3p': Operation not permitted
> > rm: cannot remove `/dev/snd/seq': Operation not permitted
> > rm: cannot remove `/dev/snd/timer': Operation not permitted
> > rmdir: `/dev/snd': Operation not permitted
> > ALSA dynamic sound device filesystem
> > create symbolic link `/dev/snd/dev' to `/proc/asound/dev'
> > ALSA loader devices
> > Creating /dev/aload?... done
> > Creating /dev/aloadSEQ... done
> >
> >>
> >> Setting up MIDI on Linux has improved *vastly* over the last few years
> >> but every now and again there are problems like this which are really
> >> difficult to diagnose.
> >>
> >> Phil
> >>
> >> On Wednesday, Jan 15, 2003, at 06:56 Europe/London, Aaron Mehl wrote:
> >>
> >>> On Wed, 2003-01-15 at 01:58, Phil Kerr wrote:
> >>>> Hi,
> >>>>
> >>>> Hmmm.....  It's difficult to say exactly what the problem is, but
> >>>> let's
> >>>> see what we can find out :)
> >>>>
> >>>> Have a look in /proc/asound and cat devices, you should see 
> >>>> something
> >>>> like:
> >>>>
> >>>> studio:/proc/asound # cat devices
> >>>>    0: [0- 0]: ctl
> >>>>    4: [0- 0]: hardware dependent
> >>>>    8: [0- 0]: raw midi
> >>>>   19: [0- 3]: digital audio playback
> >>>>   26: [0- 2]: digital audio capture
> >>>>   25: [0- 1]: digital audio capture
> >>>>   16: [0- 0]: digital audio playback
> >>>>   24: [0- 0]: digital audio capture
> >>>>    1:       : sequencer
> >>>>    9: [0- 1]: raw midi
> >>>>   10: [0- 2]: raw midi
> >>>>   33:       : timer
> >>> ----------------------------------- snip ----------------
> >>>> {so far so good} its the same
> >>> thanks for you help I have been posting to the ALSA group and I 
> >>> getting
> >>> nowhere.
> >>> So I really appreciate your help.
> >>> Aaron
> >>> --------------------------------- snip ------------------
> >>>
> >>>> Then cd into the oss directory and cat sndstat, you should have
> >>>> something similar to this:
> >>>>
> >>>> studio:/proc/asound/oss # cat sndstat
> >>>> Sound Driver:3.8.1a-980706 (ALSA v0.9.0rc3 emulation code)
> >>>> Kernel: Linux studio 2.4.19-4GB #1 Fri Sep 13 13:19:15 UTC 2002 i686
> >>>> Config options: 0
> >>>>
> >>>> Installed drivers:
> >>>> Type 10: ALSA emulation
> >>>>
> >>>> Card config:
> >>>> Sound Blaster Live! at 0xdc00, irq 10
> >>>>
> >>>> Audio devices:
> >>>> 0: EMU10K1 (DUPLEX)
> >>>>
> >>>> Synth devices:
> >>>> 0: Emu10k1
> >>>>
> >>>> Midi devices:
> >>>> 0: EMU10K1 MPU-401 (UART)
> >>>>
> >>>> Timers:
> >>>> 7: system timer
> >>>>
> >>>> Mixers:
> >>>> 0: SigmaTel STAC9721/23
> >>> --------------------------------- sniip ------------------------
> >>> Installed drivers:
> >>> Type 10: ALSA emulation
> >>>
> >>> Card config:
> >>> Sound Blaster Live! at 0xef40, irq 17
> >>>
> >>> Audio devices:
> >>> 0: EMU10K1 (DUPLEX)
> >>>
> >>> Synth devices: NOT ENABLED IN CONFIG {here it is ????}
> >>>
> >>> Midi devices:
> >>> 0: EMU10K1 MPU-401 (UART)
> >>>
> >>> Timers:
> >>> 7: system timer
> >>>
> >>> Mixers:
> >>> 0: mixer00
> >>> [root@aamehl
> >>> ---------------------------- snip ------------------------------
> >>>>
> >>>> I think you have a problem with your oss emulation, so check your
> >>>> /etc/modules.conf.
> >>>>
> >>>> Here's a snippet from mine (Suse 8.1).
> >>>>
> >>>> options snd-emu10k1 snd_enable=1 snd_index=0
> >>>> options snd snd_cards_limit=1 snd_major=116
> >>>>
> >>>> alias snd-card-0 snd-emu10k1
> >>>>
> >>>> # YaST2: sound system dependent part
> >>>> #
> >>>> alias sound-slot-0 snd-card-0
> >>>> alias sound-service-0-0 snd-mixer-oss
> >>>> alias sound-service-0-1 snd-seq-oss
> >>>> alias sound-service-0-3 snd-pcm-oss
> >>>> alias sound-service-0-8 snd-seq-oss
> >>>> alias sound-service-0-11 snd-mixer-oss
> >>>> alias sound-service-0-12 snd-pcm-oss
> >>> ------------------------ snip ----------------------
> >>> my module.conf
> >>> above snd-emu10k1 snd-pcm-oss
> >>> alias sound-slot-0 snd-emu10k1
> >>> #alias sound emu10k1
> >>> ------------------------- snip ---------------------
> >>> my modules
> >>> ---------snip-------------------
> >>>> snd-seq-midi            3712   1  (autoclean)
> >>> snd-emu10k1-synth       4316   1  (autoclean)
> >>> snd-emux-synth         26364   1  (autoclean) [snd-emu10k1-synth]
> >>> snd-seq-midi-emul       4928   0  (autoclean) [snd-emux-synth]
> >>> snd-seq-virmidi         3016   0  (autoclean) [snd-emux-synth]
> >>> snd-seq-oss            26752   0
> >>> snd-seq-midi-event      3496   0  [snd-seq-midi snd-seq-virmidi
> >>> snd-seq-oss]
> >>> snd-seq                35216   2  [snd-seq-midi snd-emux-synth
> >>> snd-seq-midi-emul snd-seq-virmidi snd-seq-oss snd-seq-midi-event]
> >>> snd-pcm-oss            37124   0
> >>> snd-mixer-oss           9496   1  [snd-pcm-oss]
> >>> snd-emu10k1            58768   3  [snd-emu10k1-synth]
> >>> snd-pcm                59392   0  [snd-pcm-oss snd-emu10k1]
> >>> snd-timer              10956   0  [snd-seq snd-pcm]
> >>> snd-hwdep               3840   0  [snd-emu10k1]
> >>> snd-util-mem            1472   0  [snd-emux-synth snd-emu10k1]
> >>> snd-rawmidi            13600   0  [snd-seq-midi snd-seq-virmidi
> >>> snd-emu10k1]
> >>> snd-seq-device          3952   0  [snd-seq-midi snd-emu10k1-synth
> >>> snd-emux-synth snd-seq-oss snd-seq snd-emu10k1 snd-rawmidi]
> >>> snd-ac97-codec         25764   0  [snd-emu10k1]
> >>> snd                    27140   2  [snd-seq-midi snd-emux-synth
> >>> snd-seq-virmidi snd-seq-oss snd-seq-midi-event snd-seq snd-pcm-oss
> >>> snd-mixer-oss snd-emu10k1 snd-pcm snd-timer snd-hwdep snd-util-mem
> >>> snd-rawmidi snd-seq-device snd-ac97-codec]
> >>> soundcore               4164   0  [snd]
> >>>
> >>>
> >>> ----------------------snip ---------------------------
> >>>> Another test is to check your modules, just in case.  With lsmod 
> >>>> look
> >>>> for something like this:
> >>>>
> >>>> snd-seq-oss            31520   0  (autoclean)
> >>>> snd-seq-midi            5056   2
> >>>> snd-emu10k1-synth       6364   0
> >>>> snd-emux-synth         32508   0  [snd-emu10k1-synth]
> >>>> snd-seq-midi-emul       5344   0  [snd-emux-synth]
> >>>> snd-seq-virmidi         4280   0  [snd-emux-synth]
> >>>> snd-seq-midi-event      3048   0  [snd-seq-oss snd-seq-midi
> >>>> snd-seq-virmidi]
> >>>> snd-seq                43280  14  [snd-seq-oss snd-seq-midi
> >>>> snd-emux-synth snd-seq-midi-emul snd-seq-virmidi snd-seq-midi-event]
> >>>> ipv6                  150036  -1  (autoclean)
> >>>> snd-emu10k1            75600   4  [snd-emu10k1-synth]
> >>>> snd-pcm                71264   1  [snd-pcm-oss snd-emu10k1]
> >>>> snd-timer              13156   0  [snd-seq snd-pcm]
> >>>> snd-hwdep               5376   0  [snd-emu10k1]
> >>>> snd-util-mem            1536   0  [snd-emux-synth snd-emu10k1]
> >>>> snd-rawmidi            15520   0  [snd-seq-midi snd-seq-virmidi
> >>>> snd-emu10k1]
> >>>> snd-seq-device          4588   0  [snd-seq-oss snd-seq-midi
> >>>> snd-emu10k1-synth snd-emux-synth snd-seq snd-emu10k1 snd-rawmidi]
> >>>> snd-ac97-codec         30052   0  [snd-emu10k1]
> >>>> snd                    35556   5  [snd-pcm-oss snd-mixer-oss
> >>>> snd-seq-oss snd-seq-midi snd-emu10k1-synth snd-emux-synth
> >>>> snd-seq-midi-emul snd-seq-virmidi snd-seq-midi-event snd-seq
> >>>> snd-emu10k1 snd-pcm snd-timer snd-hwdep snd-util-mem snd-rawmidi
> >>>> snd-seq-device snd-ac97-codec]
> >>>> soundcore               3716   0  [snd]
> >>>>
> >>>> snd-seq-oss and snd-seq-midi are required.
> >>>> ------------------------------ snip --------------
> >>>> If you have aconnect installed (part of alsa-utils) run it to see if
> >>>> your hardware devices show up:
> >>>>
> >>>> studio:~ # aconnect -i
> >>>> client 0: 'System' [type=kernel]
> >>>>      0 'Timer           '
> >>>>      1 'Announce        '
> >>>> client 64: 'External MIDI 0' [type=kernel]
> >>>>      0 'MIDI 0-0        '
> >>>> -----------------------snip --------------------
> >>>> This should cover most of the testing points to see what's wrong.
> >>>>
> >>>> Phil
> >>>>
> >>>> O
> >>>>> thanks again
> >>> Aaron
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >
> >
> 



-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate 
is essential in establishing user confidence by providing assurance of 
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to