script, possibly?  | | |
March 7th, 2005, 12:46 AM
|
#1 (permalink)
| | Member
Join Date: Jan 2004
Posts: 242
|
I have just recently got my sound working on my laptop. BUT, the only way it works is if i su then type :
modprobe snd-xx blah blah blah blah blah
I would like the sound to function when i boot up, so i dont have to keep retyping that....and im on a pretty slow proc, so kernel rebuild isnt really preference. I have never written a script before...but im guessing this would be the one-liner with the
#! /bin/bash, but where would it go, one of the rc.d's? Im running debian sarge under 2.4.27-2 kernel
thanks |
| |
March 7th, 2005, 05:48 AM
|
#2 (permalink)
| | may contain mild peril
Join Date: Oct 2001 Location: UK
Posts: 3,329
|
Any modules you list in /etc/modules should be loaded at startup. Its quite possible that ALSA has its own mechanism for loading any modules it requires, however I am not familiar with it.
Regards
ed |
| |
March 7th, 2005, 06:07 AM
|
#3 (permalink)
| | Member
Join Date: May 2004
Posts: 224
|
Add the modprobe snd-xx blah blah to /etc/rc.local or whatever the Deb local startup file is called.
HTH
lynch |
| |
March 7th, 2005, 02:23 PM
|
#4 (permalink)
| | Member
Join Date: Jan 2004
Posts: 242
|
dont know what the local startup file is... i have /etc/rc0.d through rc6.d but they seem to have numbered sym-links in them not actual files
my /etc/modules only has edit: i thought the etc/modules were kernel start things and if i made changes they wouldnt be recognized
any other suggestions? |
| |
March 7th, 2005, 02:29 PM
|
#5 (permalink)
| | may contain mild peril
Join Date: Oct 2001 Location: UK
Posts: 3,329
| Quote:
NAME
/etc/modules - kernel modules to load at boot time
DESCRIPTION
The /etc/modules file contains the names of kernel modules that are to be loaded at boot time, one per line. Arguments can be given in the same line as the module name. Comments begin with a `#', and everything on the line after them are ignored.
| You have a kernel module and you want to load it at boot, sounds just the ticket to me *shrug*
Regards
ed |
| |
March 7th, 2005, 03:05 PM
|
#6 (permalink)
| | Member
Join Date: Jan 2004
Posts: 242
|
didnt work...unless im doing something wrong? Code: modprobe snd-opl3sa2 dma1=1 dma2=0 fm_port=0x388 irq=5 isapnp=0 midi_port=0x330 port=0x538 sb_port=0x220 wss_port=0x530 thats what i need to type in at CLI to get sound to go...i put it into the modules but it didnt work. maybe modules.conf? ->testing now |
| |
March 7th, 2005, 03:10 PM
|
#7 (permalink)
| | may contain mild peril
Join Date: Oct 2001 Location: UK
Posts: 3,329
|
You don't need to put the modprobe in.
Regards
ed |
| |
March 7th, 2005, 03:29 PM
|
#8 (permalink)
| | Member
Join Date: Jan 2004
Posts: 242
|
neither of those worked. I took out the modprobe and just had snd-xx blah blah in my modules file and also tried in the modules.conf file |
| |
March 7th, 2005, 04:01 PM
|
#9 (permalink)
| | may contain mild peril
Join Date: Oct 2001 Location: UK
Posts: 3,329
|
Not sure what the problem is then. On a debian box /etc/modules is definately the place to list any modules you want loading on boot. Alsa used to load its modules from within its init script, they changed it afaik but you could always try that.
Regards
ed |
| |
March 7th, 2005, 05:39 PM
|
#10 (permalink)
| | Member
Join Date: Jan 2004
Posts: 242
|
well weird thing was i couldnt get alsa to actually configure my card correctly so a google brought me to the modprobe code and that amazingly worked. what about the script idea? i guess its a cheap workaround but i know it works. just dont know where i should be putting it or exactly how its supposed to be written. |
| | | Thread Tools | Search this Thread | | | | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | | | Most Active Discussions | | | | | Recent Discussions  | | | | | |