Sound Driver Fails on Boot; 1394 Driver fails on Compile
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am recompiling the Suse kernel to try and make VMware work with Suse8. But now when I boot I get the error message: <notice>/etc/init.d/rc5.d/S13alsasound start Starting sound driver<notice>'/etc/init.d/rc5.d/S13alsasound start' exits with status 0 : snd_cs46xxmodprobe: Can't locate module snd_cs46xx failed A check in modules.conf shows indeed that snd_cs46xx is being called, but the module is actually cs46xx. So I presume there is some invisible massaging, that has now broken. I did disable most sound modules, leaving only the generic ones, Soundblaster, Crystal, and OPL. In addition to the sound driver problem on boot with my custom kernel, when trying to compile modules, it fails on the TI 1394 driver: make[2]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/ieee1394' gcc -D__KERNEL__ -I/usr/src/linux-2.4.18.SuSE/include -Wall - -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer - -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 - -march=i686 -DMODULE -DKBUILD_BASENAME=pcilynx -c -o pcilynx.o pcilynx.c pcilynx.c: In function `mem_open': pcilynx.c:647: `num_of_cards' undeclared (first use in this function) pcilynx.c:647: (Each undeclared identifier is reported only once pcilynx.c:647: for each function it appears in.) pcilynx.c:647: `cards' undeclared (first use in this function) pcilynx.c: In function `aux_poll': pcilynx.c:706: `cards' undeclared (first use in this function) make[2]: *** [pcilynx.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/ieee1394' make[1]: *** [_modsubdir_ieee1394] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers' make: *** [_mod_drivers] Error 2 hydra:/usr/src/linux # This is something we need. As I am not a C programmer, I cannot know what is wrong. Does anyone see what's wrong? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2bEdMACgkQnQ18+PFcZJvamwCfXVnnJ6RCTALzzRk/TQBppBi5 hW0An155biVzQkjrSoATr3MTSBvfRm14 =/Urs -----END PGP SIGNATURE-----
Hi Carl Whenever you recompile a new Kernel (this means that you had e.g kernel version 2.4.18 running and you compiled kernel version 2.4.19), you have to recompile the ALSA sources too because YaST and the init scripts depend on the ALSA modules. The module you found is the kernel module for your sound card. After compiling ALSA you will have all the snd-* modules and YaST will find your sound card again and the init scripts will load the sound card modules correctly. SuSE provides pretty recent Sources for ALSA so I would give you the advice to take them (I did the same thing after building the 2.4.19 Kernel). So what you need to do is to open YaST and install the km_alsa package. You will find the source in /usr/src/kernel-modules/alsa-driver. type ./configure make make install depmod -a and then you should be all set ;-) You should compile the ALSA sources with the new Kernel running (at least I did that since I have 3 Kernels and 3 different directories for modules in the /lib/modules directory so that the configure script knows in which of the modules directories it should install the ALSA sound modules) I hope this works for you, it did it for me ;-) With kind regards Igor Boehm On Wednesday 02 October 2002 17:33, Carl wrote:
I am recompiling the Suse kernel to try and make VMware work with Suse8.
But now when I boot I get the error message:
<notice>/etc/init.d/rc5.d/S13alsasound start Starting sound driver<notice>'/etc/init.d/rc5.d/S13alsasound start' exits with status 0
: snd_cs46xxmodprobe: Can't locate module snd_cs46xx
failed
A check in modules.conf shows indeed that snd_cs46xx is being called, but the module is actually cs46xx. So I presume there is some invisible massaging, that has now broken. I did disable most sound modules, leaving only the generic ones, Soundblaster, Crystal, and OPL.
In addition to the sound driver problem on boot with my custom kernel, when trying to compile modules, it fails on the TI 1394 driver:
make[2]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/ieee1394' gcc -D__KERNEL__ -I/usr/src/linux-2.4.18.SuSE/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DKBUILD_BASENAME=pcilynx -c -o pcilynx.o pcilynx.c pcilynx.c: In function `mem_open': pcilynx.c:647: `num_of_cards' undeclared (first use in this function) pcilynx.c:647: (Each undeclared identifier is reported only once pcilynx.c:647: for each function it appears in.) pcilynx.c:647: `cards' undeclared (first use in this function) pcilynx.c: In function `aux_poll': pcilynx.c:706: `cards' undeclared (first use in this function) make[2]: *** [pcilynx.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/ieee1394' make[1]: *** [_modsubdir_ieee1394] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers' make: *** [_mod_drivers] Error 2 hydra:/usr/src/linux #
This is something we need. As I am not a C programmer, I cannot know what is wrong.
Does anyone see what's wrong?
T U X .-. /v\ L I N U X // \\ /( )\ ^^-^^ ########################################################## E-Mail Home: igor@cyberdsl.at E-Mail Business: ij-software@cyberdsl.at ##########################################################
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thank you Igor. I've been running Linux exclusively for two years, and for firewall for 4, and have never heard of this. But I'll compile Alsa sources. Is it necessary to have Arts turned on as well? (KControl) WTF is Arts, and how does it relate to Alsa? I've only been able to find Suse's 2.4.18 kernel. Are you using an official Suse 2.4.19? Where is it in the tree? Any idea what's wrong with the TILynx 1394 module? (below) My brother says it appears to be missing a .h file. Is your KAlarm working? Mine never alarms. On Wednesday, 02 October 2002 12:02, igor boehm wrote:
Hi Carl
Whenever you recompile a new Kernel (this means that you had e.g kernel version 2.4.18 running and you compiled kernel version 2.4.19), you have to recompile the ALSA sources too because YaST and the init scripts depend on the ALSA modules. The module you found is the kernel module for your sound card. After compiling ALSA you will have all the snd-* modules and YaST will find your sound card again and the init scripts will load the sound card modules correctly.
SuSE provides pretty recent Sources for ALSA so I would give you the advice to take them (I did the same thing after building the 2.4.19 Kernel). So what you need to do is to open YaST and install the km_alsa package. You will find the source in /usr/src/kernel-modules/alsa-driver. type ./configure make make install depmod -a and then you should be all set ;-) You should compile the ALSA sources with the new Kernel running (at least I did that since I have 3 Kernels and 3 different directories for modules in the /lib/modules directory so that the configure script knows in which of the modules directories it should install the ALSA sound modules)
I hope this works for you, it did it for me ;-)
With kind regards
Igor Boehm
On Wednesday 02 October 2002 17:33, Carl wrote:
I am recompiling the Suse kernel to try and make VMware work with Suse8.
But now when I boot I get the error message:
<notice>/etc/init.d/rc5.d/S13alsasound start Starting sound driver<notice>'/etc/init.d/rc5.d/S13alsasound start' exits with status 0
: snd_cs46xxmodprobe: Can't locate module snd_cs46xx
failed
A check in modules.conf shows indeed that snd_cs46xx is being called, but the module is actually cs46xx. So I presume there is some invisible massaging, that has now broken. I did disable most sound modules, leaving only the generic ones, Soundblaster, Crystal, and OPL.
In addition to the sound driver problem on boot with my custom kernel, when trying to compile modules, it fails on the TI 1394 driver:
make[2]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/ieee1394' gcc -D__KERNEL__ -I/usr/src/linux-2.4.18.SuSE/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DKBUILD_BASENAME=pcilynx -c -o pcilynx.o pcilynx.c pcilynx.c: In function `mem_open': pcilynx.c:647: `num_of_cards' undeclared (first use in this function) pcilynx.c:647: (Each undeclared identifier is reported only once pcilynx.c:647: for each function it appears in.) pcilynx.c:647: `cards' undeclared (first use in this function) pcilynx.c: In function `aux_poll': pcilynx.c:706: `cards' undeclared (first use in this function) make[2]: *** [pcilynx.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/ieee1394' make[1]: *** [_modsubdir_ieee1394] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers' make: *** [_mod_drivers] Error 2 hydra:/usr/src/linux #
This is something we need. As I am not a C programmer, I cannot know what is wrong.
Does anyone see what's wrong?
T U X .-. /v\ L I N U X // \\ /( )\ ^^-^^ ##########################################################
E-Mail Home: igor@cyberdsl.at E-Mail Business: ij-software@cyberdsl.at
##########################################################
- -- "I don't believe in astrology. But then I'm an Aquarius, and Aquarians don't believe in astrology." -- James R. F. Quirk -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2bSqoACgkQnQ18+PFcZJsC9QCbBb06SwVn72PmnKDQ2V7sNZ0n ZrMAnAvGqGkXQUubcRYZUS2KpRvF44m/ =BJe2 -----END PGP SIGNATURE-----
On Wednesday 02 October 2002 21.36, Carl wrote:
Is it necessary to have Arts turned on as well? (KControl) WTF is Arts, and how does it relate to Alsa?
Cool, finally a KDE related question. arts is the KDE sound daemon. It is the glue between kde and whatever sound architecture is used by the system. alsa is one such architecture, OSS is another. OSS is the one built into the kernel, alsa - as you've discovered - is separate, but is the one used in the 2.5 development tree and will be the new default. //Anders
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks Anders. KAlarm is also a 'KDE related question', since we're rigid.... - -- "Being disintegrated makes me ve-ry an-gry!" <huff, huff> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2bTVkACgkQnQ18+PFcZJvuSwCfU3Ugqaqq54+FyxrDsDucNj7t CogAn3DmbioMF/pjjfIt01uMjhtAfOgx =fCVJ -----END PGP SIGNATURE-----
participants (3)
-
Anders Johansson -
Carl -
igor boehm