SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, Im posting here because I think I'll get better answers here than in the software forum.
The topic says it all really. I dont have an sfxload command to load soundfonts.
Is this normal in Slackware or is it something in the kernel that has to be activated or something?
If it is normal, how can I get it? I've searched google but havnt found anything good.
Hi, Im posting here because I think I'll get better answers here than in the software forum.
The topic says it all really. I dont have an sfxload command to load soundfonts.
Is this normal in Slackware or is it something in the kernel that has to be activated or something?
If it is normal, how can I get it? I've searched google but havnt found anything good.
On Debian you would need the awesfx package installed perhaps it is named similar in Slackware.
add the commands to your /etc/rc.d/rc.local file. if it doesnt exist, create it; if it isnt executable, make it. i think youll need to specify the full path to the command, like '/sbin/modprobe snd_emu10k1_synth'
The snd_seq_virmidi is the sequencer virtual midi device module, snd_seq_midi_emul is the sequencer midi emulation and the third I have not a clue. Good to hear it is working BTW.
add the commands to your /etc/rc.d/rc.local file. if it doesnt exist, create it; if it isnt executable, make it. i think youll need to specify the full path to the command, like '/sbin/modprobe snd_emu10k1_synth'
It worked great. I never knew that you had to specify the whole path to the command.
I also put in a few other commands that I've wanted to start automaticly.
I never knew that you had to specify the whole path to the command.
in the method that you are doing (adding the commands to the script file), yes, i believe you do have to specify the full path.. try it without the full path, maybe itll work but from the last experience i had with that it didnt. probably because the PATH environment variable isnt setup yet at that stage in booting.
Yeah I have tried whithout the full path before and it didnt work. The computer just hangs before the login.
And thats why I asked because I wasnt sure about how to do
Another reason for using the full path is if you have a local install of the package as well then if the local was in your PATH before the "normal" install and the "normal" was the one you wanted to use then the system would find the local version first and use it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.