Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
when i try to install the module riptidesound.o i get the
modprob can't find module riptidesound.o
what does this indicate? I know that I have the module, and I am running the command in the directory that the module is located (/lib/modules/2.4.19-7/misc)
I tried rebuilding the module and that didn't seem to help either
is the insmod command equiv. to the modprob command? i'm trying to use this to load the sound driver for my Riptide audio device. when I use insmod, it claims that the modules already exist.
insmod is for "insert module". It will load a module into the kernel "on the fly". To see if the module is already loaded, you can run lsmod. This will show all of the modules currently loaded.
hmm, i looks like the module is loading just fine. But I still get no sound. do you know how I would associate that module with the sound device? when I open up harddrake it shows the device but doesn't seem to relate the module to that device.
From what I understand about modules, they are "automatically" related - by the nature of the device, it's chipset, the type of call, etc. Basically, a device makes a call to do something and the kernel provides the method for the device to perfom the action - by way of the module. So, I don't think you need to explicitly relate the module and the device. I haven't used Mandrake, so I'm not familiar with the view you have within Harddrake.
For sound problems, a couple of things I've run into are;
Permissions on /dev/dsp and /dev/mixer. Make sure you have access to these devices either by way of the rwx permissions on the file or you are a member of the associated group.
If you're running GNOME or KDE, the "Enlightened Sound Daemon" (esd) may be running and this can cause a problem. You can do a ps x from a console window and see if esd is running. If it is, stop it and try your sound app again.
ok, I'm trying to change the file permissions on dsp and mixer. I can change them ok, but they won't stick. if I log off then they change back when i log on again. how can I get the permissions to stick?
I am changing them by browsing to the file in Konqueror, right clicking and selecting properties, and using the Permissions tab.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.