vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| After having 'discovered' the right parameter to pass to the sound module in order to have midi in activated (modprobe -v snd-cmipci mpu_port=0x300) now i need know which is the right procedure to have that module with that parameter loaded by default on boot. (i guess something around /etc/mod* plus some command perhaps) Thanks in advance. -- Bob. RRB SoHE |
| |||
| RRB wrote: > After having 'discovered' the right parameter to pass to the sound module > in order to have midi in activated (modprobe -v snd-cmipci mpu_port=0x300) > now i need know which is the right procedure to have that module with that > parameter loaded by default on boot. > (i guess something around /etc/mod* plus some command perhaps) Well, if you think it won't be a permanent addition, or you are concerned you will forget where you put it, you can add it to /etc/rc.local and test it out. -- Paul Lutus http://www.arachnoid.com |
| |||
| Paul Lutus wrote: > RRB wrote: .... >>now i need know which is the right procedure to have that module with that >>parameter loaded by default on boot. >>(i guess something around /etc/mod* plus some command perhaps) .... > Well, if you think it won't be a permanent addition, or you are concerned > you will forget where you put it, you can add it to /etc/rc.local and test > it out. oh-no, it should be a permanent setup. Most distro's have simply a /etc/modules.conf in which put various module load information but debian don't, i can't find a document where it is explained. (and i indeed cannot understand why they setup to default the sound module to deliberately omitting to load some of it's capabilities...) -- Assioma di Baskerwill: Se fai retromarcia, qualcuno passera' dietro. RRB SoHE |
| |||
| RRB wrote: > Paul Lutus wrote: >> RRB wrote: > ... >>>now i need know which is the right procedure to have that module with that >>>parameter loaded by default on boot. >>>(i guess something around /etc/mod* plus some command perhaps) > ... >> Well, if you think it won't be a permanent addition, or you are concerned >> you will forget where you put it, you can add it to /etc/rc.local and test >> it out. > > oh-no, it should be a permanent setup. > Most distro's have simply a /etc/modules.conf in which put various module > load information but debian don't, i can't find a document where it is > explained. (and i indeed cannot understand why they setup to default the > sound module to deliberately omitting to load some of it's capabilities...) I take it you're running debian. Create a file in /etc/modprobe.d/ (say midi, or snd-cmipci) with the following text: options snd-cmipci mpu_port=0x300 That should do it. For more info look at the man page for modprobe.conf. Also, note that "If the file /etc/modprobe.conf exists, all contents of /etc/modprobe.d/ are ignored by default." (from the man page) HTH Luca |
| ||||
| Luca Pireddu wrote: > RRB wrote: .... >>Most distro's have simply a /etc/modules.conf in which put various module >>load information but debian don't, i can't find a document where it is >>explained. (and i indeed cannot understand why they setup to default the >>sound module to deliberately omitting to load some of it's capabilities...) .... > I take it you're running debian. Create a file in /etc/modprobe.d/ (say midi, > or snd-cmipci) with the following text: > options snd-cmipci mpu_port=0x300 Thanks for now. I'll try it. > That should do it. For more info look at the man page for modprobe.conf. > Also, note that "If the file /etc/modprobe.conf exists, all contents > of /etc/modprobe.d/ are ignored by default." (from the man page) That's interesting. There was (or still is) a command like 'modprobe-update' or similar which should update modprobe.conf with the options contained in the modprobe.d directory, but i'm not sure... -- Bob. RRB SoHE |