Opened 20 years ago

Closed 19 years ago

#1812 closed defect (fixed)

modprobe.conf rules need full path to modprobe while booting

Reported by: dbn.lists@… Owned by: dnicholson@…
Priority: normal Milestone: 6.2
Component: Book Version: SVN
Severity: major Keywords: modprobe
Cc:

Description

Following the example modprobe rule ​here results in failures like these: 

Jun  9 18:19:29 silky kernel: snd_ac97_codec: Unknown symbol snd_interval_refine
Jun  9 18:19:29 silky kernel: snd_ac97_codec: Unknown symbol snd_pcm_hw_rule_add
Jun  9 18:19:29 silky kernel: snd_ymfpci: Unknown symbol snd_ac97_resume
Jun  9 18:19:29 silky kernel: snd_ymfpci: Unknown symbol snd_pcm_new

Here is the modprobe rule:

install snd-pcm modprobe -i snd-pcm; modprobe snd-pcm-oss

Running manually after boot showed now problems. Finally I realized that the problem was that modprobe was not actually being run at boot, so the snd-pcm module wasn't being loaded. Adding the full path to /sbin/modprobe in /etc/modprobe.conf solved the problem.

Change History (2)

comment:1 by dnicholson@…, 19 years ago

Owner: changed from lfs-book@… to dnicholson@…
Status: new → assigned

comment:2 by dnicholson@…, 19 years ago

Resolution: → fixed
Status: assigned → closed

Fixed in r7651.

Note: See TracTickets for help on using tickets.