Hi Alan, Have you considered blacklisting the offending module? (or are they the same module and intet is a typo?) Anyway, I can't answer with authority your question about scripts, because I've only really had to mess with it once or twice, but this page may be helpful:
https://help.ubuntu.com/community/UbuntuBootupHowto I think that similar to what someone else suggested, you core of it is to put your script in /etc/init.d and then create the appropriate links in /etc/rcN.d or what have you. In Debian-based distros there's a specific tool for creating these links, the update-rc.d command. You might consult the man page. The other thing that may be worth noting is that Ubuntu is switching away from this old rc script way of doing things (I think this is known as the Sys V init process) to something called Upstart...so there may also be some better way of adding start-up scripts. Hope that helps a little, Nick Alan Bromborsky wrote: > I have an ASUS motherboard with a builtin realtek sound chip. I am > running Ubuntu 8.10 amd64 and there is a problem with the os finding > the sound chip. A work around is to enter 'sudo rmmod snd_hda_intel' > and 'sudo modprobe snd_hda_intet' after the system boots. I wish to > automate this with a script. Obviously the script would be: > > #!/bin/sh > rmmod snd_hda_intel > modprobe snd_hda_intet > > The question is how do I give the script permission to run 'rmmod' and > 'modprobe' and how do I have it executed after the system has booted, > but before the logon prompt and where should I put it? Thank you.
