[Alsa-devel] alsa configure/install bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A couple of issues with the configure script and/or the install target of the makefile: a) the help for configure claims that the default location for the - --with-moddir parameter is /lib/modules//misc. However, after make install, the modules are apparently actually installed in subtrees of /lib/modules//kernel/sound. b) When modules are installed in the above directories, modprobe can't find them. Is this distribution specific? Is there a way to configure this behavior? I'm running RH 7.1 on a Toshiba Satellite. I'll also note that with a recent beta of the 0.9 code, modules were installed in the misc directory. Thanks - -- Derek Martin [EMAIL PROTECTED] - - I prefer mail encrypted with PGP/GPG! GnuPG Key ID: 0x81CFE75D Retrieve my public key at http://pgp.mit.edu Learn more about it at http://www.gnupg.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9F2VvdjdlQoHP510RApXFAJ0RNPn1lnOv4fc8C8Dy23LmoGbiKgCeLbuy mZ2VxwJokexuIfJ7Z3uQuxw= =aa5T -END PGP SIGNATURE- --- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] alsa configure/install bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Takashi, and thanks for replying. At some point hitherto, Takashi Iwai hath spake thusly: > > b) When modules are installed in the above directories, modprobe can't > > find them. Is this distribution specific? Is there a way to > > configure this behavior? I'm running RH 7.1 on a Toshiba Satellite. > > I'll also note that with a recent beta of the 0.9 code, modules were > > installed in the misc directory. > > iirc rh7.1 has already 2.4 kernel system, so it must be ok. It shipped with 2.4.2 IIRC, though I've updated it to stock 2.4.17. > most likely the configuration of alsa driver doesn't match with your > current kernel config. Not sure what you mean here... I only have kernel sources for my running 2.4.17 kernel, if that's what you mean. So it's not possible that they don't match, if that is what you mean... And both configure and make output indicate it's being compiled for the right kernel, in the right location, aside from the fact that it's installing them in kernel/sound, as opposed to misc. > please elaborate your prolbem. what says modprobe? The problem is that if the alsa modules are not installed in /lib/modules//misc, modprobe can't find them to load them. Once they are installed there, everything works fine. This is as it was with the 0.9.something beta something that I was using before this, also... meaning that when I installed the beta drivers previously, they installed in the misc directory (with out me telling them to do so specifically, as far as I can remember), and everything worked fine. Is it possible that this is due to the version of modutils that I have, and not related to the kernel at all? This is with Red Hat's modutils-2.4.13-0.7.1 rpm... > what happens if you run "depmod -ae"? Well, I set the command line for configure to place them in the misc directory, so everything is working now. There is no output from depmod -ae, but presumably there would be had I allowed the drivers to be installed in the kernel/sound directories? If you feel that it would be helpful, I could always blow away my modules, and install them in the other location. - -- Derek Martin [EMAIL PROTECTED] - - I prefer mail encrypted with PGP/GPG! GnuPG Key ID: 0x81CFE75D Retrieve my public key at http://pgp.mit.edu Learn more about it at http://www.gnupg.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9GLAedjdlQoHP510RAtaXAJ4kmSCmoy2SDtoaKMk+72QBPFoghwCgjLUe 4AJ0Hg9aGYnyIAO0fEwo0Lw= =kKL+ -END PGP SIGNATURE- --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] alsa configure/install bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At some point hitherto, Takashi Iwai hath spake thusly: > > The problem is that if the alsa modules are not installed in > > /lib/modules//misc, modprobe can't find them to load them. Once > > they are installed there, everything works fine. This is as it was > > with the 0.9.something beta something that I was using before this, > > also... meaning that when I installed the beta drivers previously, > > they installed in the misc directory (with out me telling them to do > > so specifically, as far as I can remember), and everything worked > > fine. > > can you check where the files are copied to? > just look at what "make install-modules" shows. Well, as I said, they're copied to the kernel/sound directory in the correct place for my running kernel. Specifically, /lib/modules/2.4.17ddm-mercury-1/kernel/sound/*. There are no symlinks, and that is the actual path used by make install. Actually, I'll just include the output, so you can see it for yourself (compilation parts snipped out): rm -f /lib/modules/2.4.17ddm-mercury-1/kernel/sound/snd*.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/persist.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/isapnp.o make[1]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore' mkdir -p /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore cp snd-hwdep.o snd-pcm.o snd-rawmidi.o snd-timer.o snd.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore make -C oss modules_install make[2]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore/oss' mkdir -p /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore/oss cp snd-mixer-oss.o snd-pcm-oss.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore/oss make[2]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore/oss' make -C seq modules_install make[2]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore/seq' mkdir -p /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore/seq cp snd-seq-device.o snd-seq-instr.o snd-seq-midi-emul.o snd-seq-midi-event.o snd-seq-midi.o snd-seq.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore/seq make -C instr modules_install make[3]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore/seq/instr' mkdir -p /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore/seq/instr cp snd-ainstr-fm.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore/seq/instr make[3]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore/seq/instr' make -C oss modules_install make[3]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore/seq/oss' mkdir -p /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore/seq/oss cp snd-seq-oss.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/acore/seq/oss make[3]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore/seq/oss' make[2]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore/seq' make[1]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/acore' make[1]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/i2c' make[1]: Nothing to be done for `modules_install'. make[1]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/i2c' make[1]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/drivers' make -C mpu401 modules_install make[2]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/drivers/mpu401' mkdir -p /lib/modules/2.4.17ddm-mercury-1/kernel/sound/drivers/mpu401 cp snd-mpu401-uart.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/drivers/mpu401 make[2]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/drivers/mpu401' make -C opl3 modules_install make[2]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/drivers/opl3' mkdir -p /lib/modules/2.4.17ddm-mercury-1/kernel/sound/drivers/opl3 cp snd-opl3-lib.o snd-opl3-synth.o /lib/modules/2.4.17ddm-mercury-1/kernel/sound/drivers/opl3 make[2]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/drivers/opl3' make[1]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/drivers' make[1]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/isa' make -C ad1816a modules_install make[2]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/isa/ad1816a' make[2]: Nothing to be done for `modules_install'. make[2]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/isa/ad1816a' make -C ad1848 modules_install make[2]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/isa/ad1848' make[2]: Nothing to be done for `modules_install'. make[2]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/isa/ad1848' make -C cs423x modules_install make[2]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/isa/cs423x' make[2]: Nothing to be done for `modules_install'. make[2]: Leaving directory `/usr/local/src/Alsa/alsa-driver-0.9.0rc2/isa/cs423x' make -C es1688 modules_install make[2]: Entering directory `/usr/local/src/Alsa/alsa-driver-0.9
Re: [Alsa-devel] alsa configure/install bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, I moved my misc directory aside, and reinstalled them in the kernel/sound directories. Here's some more info: At some point hitherto, Takashi Iwai hath spake thusly: > > > what happens if you run "depmod -ae"? > > > > Well, I set the command line for configure to place them in the misc > > directory, so everything is working now. There is no output from > > depmod -ae, but presumably there would be had I allowed the drivers to > > be installed in the kernel/sound directories? It turns out there's still no output to this command. > kernel/sound directory must be checked by modprobe. > all normal kernel modules are installed under kernel directory. It seems like it's checking, partially. After starting my X session, gnome complains that it's unable to open /dev/mixer. I looked at the output of lsmod, and the only sound-related modules that got loaded were these: $ lsmod Module Size Used byTainted: P snd-mixer-oss 8800 0 (autoclean) (unused) snd24200 0 (autoclean) [snd-mixer-oss] soundcore 3588 0 (autoclean) [snd] Note the 'P' flag in the Tainted header. I don't know what this means, but it wasn't there when the modules were located in misc. The man page for lsmod is remarkably unhelpful in determining the meaning of the 'P' that's there. I have a vague idea that this has to do with GPL issues, but beyond that no clue... Also, in my logs, I see these messages: Jun 26 15:30:49 mercury modprobe: modprobe: Can't locate module char-major-81 Jun 26 15:30:52 mercury modprobe: modprobe: Can't locate module sound-slot-0 Apparently, it's not loading any of the drivers in the kernel/sound/pci directory... Oddly, if I manually modprobe snd-ymfpci, it loads, along with the rest of the modules. All I can say is, WTF? Module Size Used byTainted: P snd-ymfpci 41444 0 (unused) snd-pcm48768 0 [snd-ymfpci] snd-opl3-lib5312 0 [snd-ymfpci] snd-timer 9760 0 [snd-pcm snd-opl3-lib] snd-hwdep 3456 0 [snd-opl3-lib] snd-mpu401-uart 2800 0 [snd-ymfpci] snd-rawmidi12352 0 [snd-mpu401-uart] snd-seq-device 3840 0 [snd-opl3-lib snd-rawmidi] snd-ac97-codec 23620 0 [snd-ymfpci] snd-mixer-oss 8800 0 (autoclean) (unused) snd24200 0 (autoclean) [snd-ymfpci snd-pcm snd-opl3-lib s nd-timer snd-hwdep snd-mpu401-uart snd-rawmidi snd-seq-device snd-ac97-codec snd -mixer-oss] soundcore 3588 4 (autoclean) [snd] - -- Derek Martin [EMAIL PROTECTED] - - I prefer mail encrypted with PGP/GPG! GnuPG Key ID: 0x81CFE75D Retrieve my public key at http://pgp.mit.edu Learn more about it at http://www.gnupg.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9GhoIdjdlQoHP510RAovgAJ97OLEPtEiCvABX6b3vzI2KUTbunACeLDaL 8tuWo7cttdSmb7o7bqkBD40= =+Pp9 -END PGP SIGNATURE- --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] alsa configure/install bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At some point hitherto, Takashi Iwai hath spake thusly: > kernel/sound directory must be checked by modprobe. > all normal kernel modules are installed under kernel directory. Hi Takashi, It occured to me that you're probably going to ask me what my modules.conf file looks like, so I'll save you the trouble: # ALSA Sound stuff alias char-major-116 snd options snd snd_major=116 snd_cards_limit=1 alias snd-card-0 snd-card-ymfpci options snd-card-ymfpci snd_index=0 snd_id="YMFPCI" alias char-major-14 soundcore alias sound-slot-0 snd-card-0 post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || : pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || : alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-12 snd-pcm-oss Now, looking at this, and matching it up against the modules that actually exist, I notice that the alias for snd-card-0 refers to a module that doesn't appear to exist. I suspect this is the culprate. However, this is the exact same configuration that I'm using when the modules are in the misc directory, and everything works fine. Looking back at the documentation, I think I understand what happened. The howto shows this in the modprobe section: # ALSA portion alias snd-card-0 snd-interwave alias snd-card-1 snd-card-es1370 I copied the form of the second entry, but that's not the name of the module for the ymfpci chipset. I've modified the alias, but I don't actually have time to test it to see if that fixed the problem. I believe it will... Gotta run. Thanks for your help. - -- Derek Martin [EMAIL PROTECTED] - - I prefer mail encrypted with PGP/GPG! GnuPG Key ID: 0x81CFE75D Retrieve my public key at http://pgp.mit.edu Learn more about it at http://www.gnupg.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9GhzZdjdlQoHP510RAkjlAKCrPcxJerxEHRhHZloUAse2MFI+4wCggHUs IFXlX2+9RamhqjRwXXFUQU0= =b9NM -END PGP SIGNATURE- --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
