Sponsored Content
Full Discussion: Alsa Boot Script
Top Forums Shell Programming and Scripting Alsa Boot Script Post 302874851 by RudiC on Sunday 17th of November 2013 02:53:36 PM
Old 11-17-2013
It may depend on other modules. Try running it towards the end of the boot process. And, include some error checking + output.
 

We Also Found This Discussion For You

1. Slackware

HD-Audio: ALSA settings not persistent across reboots.

Hi: The OS is Slackware 14.0. When, after 14.0 install I first ran alsamixer, I got an error message and it quit. After some googling, I created /etc/modprobe.d/alsa.conf with these lines: alias snd-card-0 snd_hda_intel alias sound-slot-0 snd_hda_intel options snd_hda_intel... (0 Replies)
Discussion started by: stf92
0 Replies
MODULES-LOAD.D(5)						  modules-load.d						 MODULES-LOAD.D(5)

NAME
modules-load.d - Configure kernel modules to load at boot SYNOPSIS
/etc/modules-load.d/*.conf /run/modules-load.d/*.conf /usr/lib/modules-load.d/*.conf DESCRIPTION
systemd-modules-load.service(8) reads files from the above directories which contain kernel modules to load during boot in a static list. Each configuration file is named in the style of /etc/modules-load.d/program.conf. Note that it is usually a better idea to rely on the automatic module loading by PCI IDs, USB IDs, DMI IDs or similar triggers encoded in the kernel modules themselves instead of static configuration like this. In fact, most modern kernel modules are prepared for automatic loading already. CONFIGURATION FORMAT
The configuration files should simply contain a list of kernel module names to load, separated by newlines. Empty lines and lines whose first non-whitespace character is # or ; are ignored. Each configuration file shall be named in the style of program.conf. Files in /etc/ override files with the same name in /usr/lib/ and /run/. Files in /run/ override files with the same name in /usr/lib/. Packages should install their configuration files in /usr/lib/, files in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed from vendor packages. If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in /etc/modules-load.d/ bearing the same filename. EXAMPLE
Example 1. /etc/modules-load.d/virtio-net.conf example: # Load virtio-net.ko at boot virtio-net SEE ALSO
systemd(1), systemd-modules-load.service(8), systemd-delta(1), modprobe(8) systemd 208 MODULES-LOAD.D(5)
All times are GMT -4. The time now is 09:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy