I've been trying to work out how the various sound modules get loaded at boot time on CentOS 5 - but I can't find anything obvious under /etc/rc.d/
CentOS 4 did this in /etc/rc.d/rc.sysinit - but there is nothing equivalent in CentOS 5
Does anyone know how these modules get loaded?
Thanks
James Pearson
James Pearson wrote:
I've been trying to work out how the various sound modules get loaded at boot time on CentOS 5 - but I can't find anything obvious under /etc/rc.d/
CentOS 4 did this in /etc/rc.d/rc.sysinit - but there is nothing equivalent in CentOS 5
Does anyone know how these modules get loaded?
Have you tried system-config-soundcard?
mark
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of m.roth@5-cent.us Sent: Monday, February 07, 2011 12:41 PM To: CentOS mailing list Subject: Re: [CentOS] How and when are the sound modules loaded at system boot time on CentOS 5?
James Pearson wrote:
I've been trying to work out how the various sound modules
get loaded
at boot time on CentOS 5 - but I can't find anything obvious under /etc/rc.d/
CentOS 4 did this in /etc/rc.d/rc.sysinit - but there is nothing equivalent in CentOS 5
Does anyone know how these modules get loaded?
Have you tried system-config-soundcard?
It's pretty clear he's asking a question with an answer like:
"rc.sysinit->modprobe -a (assuming the correct aliases in /etc/modprobe.conf list the proper sound modules)"
Since my embedded headless CentOS target is also mute, I never worried the question and don't know the exact answer.
******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated**
m.roth@5-cent.us wrote:
James Pearson wrote:
I've been trying to work out how the various sound modules get loaded at boot time on CentOS 5 - but I can't find anything obvious under /etc/rc.d/
CentOS 4 did this in /etc/rc.d/rc.sysinit - but there is nothing equivalent in CentOS 5
Does anyone know how these modules get loaded?
Have you tried system-config-soundcard?
I have, but that wasn't the question :-)
Something has to load the sound kernel modules at system start up - and I would like to find out what does this and at what stage of the system start up process this happens.
James Pearson
James Pearson wrote:
m.roth@5-cent.us wrote:
James Pearson wrote:
I've been trying to work out how the various sound modules get loaded at boot time on CentOS 5 - but I can't find anything obvious under /etc/rc.d/
CentOS 4 did this in /etc/rc.d/rc.sysinit - but there is nothing equivalent in CentOS 5
Does anyone know how these modules get loaded?
Have you tried system-config-soundcard?
I have, but that wasn't the question :-)
Something has to load the sound kernel modules at system start up - and I would like to find out what does this and at what stage of the system start up process this happens.
cannot answer all your question but found that sometime around 5.3 -> 5.4 that the order of sound modules loading changed. I found that one needed to edit modprobe.conf and add index=0 or index=1 as needed to get the modules loading correctly and thus allowing related software to find them in the correct place. HTH
James Pearson _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
James Pearson wrote:
m.roth@5-cent.us wrote:
James Pearson wrote:
I've been trying to work out how the various sound modules get loaded at boot time on CentOS 5 - but I can't find anything obvious under /etc/rc.d/
CentOS 4 did this in /etc/rc.d/rc.sysinit - but there is nothing equivalent in CentOS 5
Does anyone know how these modules get loaded?
Have you tried system-config-soundcard?
I have, but that wasn't the question :-)
Something has to load the sound kernel modules at system start up - and I would like to find out what does this and at what stage of the system start up process this happens.
Oh! I thought you were just trying to get sound working. Yeah, as someone else noted, modprobe.conf, and, as I just looked and found, there's more in /etc/modprobe.d/modprobe.conf.dist, where I see excerpt: alias char-major-116-* snd alias sound-service-*-0 snd-mixer-oss alias sound-service-*-1 snd-seq-oss alias sound-service-*-3 snd-pcm-oss alias sound-service-*-8 snd-seq-oss alias sound-service-*-12 snd-pcm-oss
install sound-slot-* /sbin/modprobe snd-card-${MODPROBE_MODULE##sound[_-]slot[_-- ]}
install snd-pcm /sbin/modprobe --ignore-install snd-pcm && /sbin/modprobe snd-pcc m-oss && /sbin/modprobe snd-seq-device && /sbin/modprobe snd-seq-oss --- end excerpt --- right after USB and before NFS.
I don't know if that's read before or after depmod.d/depmod.conf.dist, but presumably it's used by udev.
mark
On Mon, 7 Feb 2011, James Pearson wrote:
To: CentOS mailing list centos@centos.org From: James Pearson james-p@moving-picture.com Subject: Re: [CentOS] How and when are the sound modules loaded at system boot time on CentOS 5?
m.roth@5-cent.us wrote:
James Pearson wrote:
I've been trying to work out how the various sound modules get loaded at boot time on CentOS 5 - but I can't find anything obvious under /etc/rc.d/
CentOS 4 did this in /etc/rc.d/rc.sysinit - but there is nothing equivalent in CentOS 5
Does anyone know how these modules get loaded?
Have you tried system-config-soundcard?
I have, but that wasn't the question :-)
Something has to load the sound kernel modules at system start up - and I would like to find out what does this and at what stage of the system start up process this happens.
Hi James.
Doesn't the kernel probe the machine's hardware at boot up time, and if it finds your soundcard, load the appropriate driver for it?
If the hardware is not detected by the kernel, then you probably would have to manually load the respective hardware driver with modprobe.
[root@karsites ~]# modprobe -l *cmi* /lib/modules/2.6.18-194.32.1.el5/kernel/sound/pci/snd-cmipci.ko
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
Keith Roberts wrote:
Doesn't the kernel probe the machine's hardware at boot up time, and if it finds your soundcard, load the appropriate driver for it?
I assume something does probe some how - which is what I trying to work out. i.e. what exactly does the probe and where in the startup sequence is this done?
Thanks
James Pearson
On Mon, 2011-02-07 at 19:43 +0000, James Pearson wrote:
I assume something does probe some how - which is what I trying to work out. i.e. what exactly does the probe and where in the startup sequence is this done?
I told you already...the kernel calls insmod first...then "init_moule" then a "another sub r gets called to an actual init_module r
lemme see if i can finds ya a book to read
Why not explain exactly your problem? Theres a reason you need to know and y?
John
JohnS wrote:
On Mon, 2011-02-07 at 19:43 +0000, James Pearson wrote:
I assume something does probe some how - which is what I trying to work out. i.e. what exactly does the probe and where in the startup sequence is this done?
I told you already...the kernel calls insmod first...then "init_moule" then a "another sub r gets called to an actual init_module r
That is how the kernel loads a module when insmod is run - but what tells the system to load the sound modules at system start-up?
Why not explain exactly your problem? Theres a reason you need to know and y?
I have a system with 2 sound 'cards', one on the motherboard and one on a PCI-E card. Both cards use the Intel HDA chipset (snd-hda-intel.ko driver). When the on-board card has been disabled via a jumper, none of the sound modules get loaded at system start-up. I can manually load the snd-hda-intel module and the PCI-E card is found.
Therefore, I would like to find out why the PCI-E card is not found and the driver not loaded at system start-up. Hence my original question, if anyone knows at what point in the start up procedure the system loads the sound modules.
Thanks
James Pearson
On Mon, 2011-02-07 at 20:37 +0000, James Pearson wrote:
JohnS wrote:
I told you already...the kernel calls insmod first...then "init_moule" then a "another sub r gets called to an actual init_module r
That is how the kernel loads a module when insmod is run - but what tells the system to load the sound modules at system start-up?
:-)
Why not explain exactly your problem? Theres a reason you need to know and y?
I have a system with 2 sound 'cards', one on the motherboard and one on a PCI-E card. Both cards use the Intel HDA chipset (snd-hda-intel.ko driver). When the on-board card has been disabled via a jumper, none of the sound modules get loaded at system start-up. I can manually load the snd-hda-intel module and the PCI-E card is found.
Therefore, I would like to find out why the PCI-E card is not found and the driver not loaded at system start-up. Hence my original question, if anyone knows at what point in the start up procedure the system loads the sound modules.
snd-hda-intel get blacklisted somehow. or it is not listed in the modprobe conf to load. An idea just thinking yo could remove the kernel reinstall it with only the cards you want enabled. You could look into the initrd for startup modules also with cpio. Back it up first though.
Also you should make sure the it has the right PCI Identfier for the *.ko . If My other questions are, is your init subsystem in working order; like it should work and look for extra modules to load in sysconfig? All fails create an insmod *.ko script for startup.
John
James Pearson wrote:
JohnS wrote:
On Mon, 2011-02-07 at 19:43 +0000, James Pearson wrote:
I assume something does probe some how - which is what I trying to work out. i.e. what exactly does the probe and where in the startup sequence is this done?
See dmesg and check when it finds your pci card and what it indicates is loaded for this.
I told you already...the kernel calls insmod first...then "init_moule" then a "another sub r gets called to an actual init_module r
That is how the kernel loads a module when insmod is run - but what tells the system to load the sound modules at system start-up?
Why not explain exactly your problem? Theres a reason you need to know and y?
I have a system with 2 sound 'cards', one on the motherboard and one on a PCI-E card. Both cards use the Intel HDA chipset (snd-hda-intel.ko driver). When the on-board card has been disabled via a jumper, none of the sound modules get loaded at system start-up. I can manually load the snd-hda-intel module and the PCI-E card is found.
Therefore, I would like to find out why the PCI-E card is not found and the driver not loaded at system start-up. Hence my original question, if anyone knows at what point in the start up procedure the system loads the sound modules.
Thanks
James Pearson _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Mon, 7 Feb 2011, James Pearson wrote:
To: CentOS mailing list centos@centos.org From: James Pearson james-p@moving-picture.com Subject: Re: [CentOS] How and when are the sound modules loaded at system boot time on CentOS 5?
Keith Roberts wrote:
Doesn't the kernel probe the machine's hardware at boot up time, and if it finds your soundcard, load the appropriate driver for it?
I assume something does probe some how - which is what I trying to work out. i.e. what exactly does the probe and where in the startup sequence is this done?
Hi James. Good question. I can't say for sure, but I guess it's some sort of h/w detection code in the kernel. This may be of some help:
http://www.ibm.com/developerworks/library/l-linuxboot/index.html
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
James Pearson wrote:
I assume something does probe some how - which is what I trying to work out. i.e. what exactly does the probe and where in the startup sequence is this done?
After adding various debug echo's to /etc/rc.d/rc.sysinit, the sound modules are loaded by udev (/sbin/start_udev)
So I now know how the sound modules are loaded at system start up
James Pearson
On Mon, 2011-02-07 at 17:38 +0000, James Pearson wrote:
I've been trying to work out how the various sound modules get loaded at boot time on CentOS 5 - but I can't find anything obvious under /etc/rc.d/
and you want
A call is done to "init_module" to sling it into memory then other things happen....addressing starts as in treeing or branching into it's address.
John