Help! Can't get sound card to work anymore. Whats going on?
From: Max Webb AKA "the new, meat head" I have a Creative sound blaster Live sound card and cant get it to work anymore. In the past, on this system, I have successfully installed the card when I installed the OS or later via YaST2 and I have always been able to reinstall or configure the card later. I did not change any hardware before this problem occurred, and the sound card had been working fine. The problem is not alsa or volumes. I have checked with rcalsasound status and restart. The only thing I have done around the time this problem started was configure and recompile my kernel so as to enable SCSI emulation for my second CDROM/DVD drive, so that i could use it as a read device with Xcdroast. I used the following proceedure to configure and compile my kernel: $ su $ password # cd /usr/src/ linux-2.4.18.SuSE/ # make oldconfig # make xconfig used xconfig to setup up options for SCSI emulation. # make dep # make clean # make bzImage # cd arch/i386/boot # mv /boot/vmlinuz /boot/vmlinuz.old # cp bzImage /boot/vmlinuz # /sbin/lilo # cd /usr/src/ linux-2.4.18.SuSE/ # make modules # make modules_install This may or may not have something to do with the problem. I have compiled my kernel before without it effecting the sound card and indeed SCSI emulation now works. when the problem originally started and after checking alsa, I ran yast2 and got some sort of message about the amount of installed sound cards not matching some config. At that point I saw that SB Live! EMU10k1 was installed. So I uninstalled it and tried to reinstall it and got the following error message: Error an error occurred during installation of SB Live! Emu10k1 The kernel module snd-emu10k1 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters. I have check to make sure the appropriate modules have be compiled into the kernel and that alsa is installed. no mater what I do I keep getting this message. So what gives? Any help would be greatly appreciated. Max -- Be positive and you will prevail.
On Monday 19 August 2002 06:57 am, Max Webb wrote:
I have a Creative sound blaster Live sound card and cant get it to work anymore. ------------snip---------------------------------- The only thing I have done around the time this problem started was configure and recompile my kernel so as to enable SCSI emulation for my second CDROM/DVD drive, ---------------snip------------------- ALSA needs to be compiled for the kernel you are using. I would suggest downloading the alsa source and following the install instructions. be sure to read about the configure flags - I use --with-isapnp=yes --with-sequencer=yes for alsa 0.5.12a but I know tha. there is a newer version that may work w/ your kernel. HTH -- dh
Thanks but but I am using the standard SuSE 8.0 kernal and kernal source and the standard alsa and alsa source that shiped with SuSE 8.O . Any suggestions? On Monday 19 August 2002 02:47 pm, dh wrote:
On Monday 19 August 2002 06:57 am, Max Webb wrote:
I have a Creative sound blaster Live sound card and cant get it to work anymore.
------------snip----------------------------------
The only thing I have done around the time this problem started was configure and recompile my kernel so as to enable SCSI emulation for my second CDROM/DVD drive,
---------------snip------------------- ALSA needs to be compiled for the kernel you are using. I would suggest downloading the alsa source and following the install instructions. be sure to read about the configure flags - I use --with-isapnp=yes --with-sequencer=yes for alsa 0.5.12a but I know tha. there is a newer version that may work w/ your kernel. HTH
On Monday, 19 Agosto 2002 12:37 PM, Max Webb wrote:
Thanks but but I am using the standard SuSE 8.0 kernal and kernal source...
The only thing I have done around the time this problem started was configure and recompile my kernel so as to enable SCSI emulation for my second CDROM/DVD drive,
Correction: since you compiled your own kernel, you're no longer using the kernel which came with the distro, for which ALSA was originally compiled,
ALSA needs to be compiled for the kernel you are using.
so you have to compile it now for the new kernel. My 1-1/2¢. -- Regards, gr, in the /usually/ sunny, balmy Florida Suncoast.
Again this does not help because I have recompiled my kernal on another installation based on the standard linux-2.4.18.SuSE only changing SCSI emulation like this instance. I have done this before and not had a problem with sound afterward. This compilation was based on the stock SuSE distro install source code configuration. I have reinstalled alsa. I have also recompiled as sugested to no avail. I now suspect that it is a device conflict problem. Possible the same device being listed twice. Where is the master configuration file for detected hardware devices? /etc/? Thanks. Max On Monday 19 August 2002 07:25 pm, gilson redrick wrote:
On Monday, 19 Agosto 2002 12:37 PM, Max Webb wrote:
Thanks but but I am using the standard SuSE 8.0 kernal and kernal source...
The only thing I have done around the time this problem started was configure and recompile my kernel so as to enable SCSI emulation for my second CDROM/DVD drive,
Correction: since you compiled your own kernel, you're no longer using the kernel which came with the distro, for which ALSA was originally compiled,
ALSA needs to be compiled for the kernel you are using.
so you have to compile it now for the new kernel.
My 1-1/2¢.
No you have another issue. You shouldn't have to recompile ALSA if you just compiled a new kernel from the same default src's that shipped with the distribution. Otherwise I would have to do it everytime there is a kernel update (hint it's a new build ;)..and I don't. It just works. I would suggest doing it again. Remove the config file again and do a makecloneconfig to get the same config as the running kernel and choose the new options you wish. Maybe you checked something that you don't remember..etc..etc. We've all done it :) * - (hbwebb@citlink.net) [020819 22:41]: ::Again this does not help because I have recompiled my kernal on another ::installation based on the standard linux-2.4.18.SuSE only changing SCSI ::emulation like this instance. I have done this before and not had a problem ::with sound afterward. This compilation was based on the stock SuSE distro ::install source code configuration. I have reinstalled alsa. I have also ::recompiled as sugested to no avail. I now suspect that it is a device ::conflict problem. Possible the same device being listed twice. Where is the ::master configuration file for detected hardware devices? /etc/? :: ::Thanks. Max :: :: ::On Monday 19 August 2002 07:25 pm, gilson redrick wrote: ::> On Monday, 19 Agosto 2002 12:37 PM, Max Webb wrote: ::> > Thanks but but I am using the standard SuSE 8.0 kernal and kernal ::> > source... ::> > ::> > The only thing I have done around the time this problem started was ::> > configure and recompile my kernel so as to enable SCSI emulation for ::> > my second CDROM/DVD drive, ::> ::> Correction: since you compiled your own kernel, you're no longer using the ::> kernel which came with the distro, for which ALSA was originally compiled, ::> ::> > ALSA needs to be compiled for the kernel you are using. ::> ::> so you have to compile it now for the new kernel. ::> ::> My 1-1/2¢. :: :: ::-- ::Check the headers for your unsubscription address ::For additional commands send e-mail to suse-linux-e-help@suse.com ::Also check the archives at http://lists.suse.com ::Please read the FAQs: suse-linux-e-faq@suse.com :: -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
Ben I totally agree with you as I have recompiled without have to alter alsa afterward. None the less I recompiled alsa from the src directory and I was then able to install my sound card. I did not know the make cloneconfig command. Thank you for letting me know about that. Please read the following which I sent to Gilson and thanks for all your help: Gilson, I just recompiled Alsa from the stock SuSE 8.0 /usr/src/kernel-modules/alsa-driver/ instead of other sources. It worked this time. Thank you for your suggestion. I still don't think it had to do with the recompile which I have done before under the same conditions with no alsa problems. My belief is that all of these problems are due to what I feel is a botched or corrupted SuSE YoU update a few days ago. Looking back right after I did the update, I had a problem involving pppd, in which files were missing from my pppd directory and had to be copied from another installation for pppd to work. It was at that time that the sound card stopped working. None the less, your suggestion of alsa recompilation did the trick. And I am greatly indebted to you. Thank you. Max On Monday 19 August 2002 10:50 pm, Ben Rosenberg wrote:
No you have another issue. You shouldn't have to recompile ALSA if you just compiled a new kernel from the same default src's that shipped with the distribution. Otherwise I would have to do it everytime there is a kernel update (hint it's a new build ;)..and I don't. It just works. I would suggest doing it again. Remove the config file again and do a makecloneconfig to get the same config as the running kernel and choose the new options you wish. Maybe you checked something that you don't remember..etc..etc. We've all done it :)
* - (hbwebb@citlink.net) [020819 22:41]: ::Again this does not help because I have recompiled my kernal on another ::installation based on the standard linux-2.4.18.SuSE only changing SCSI ::emulation like this instance. I have done this before and not had a :: problem with sound afterward. This compilation was based on the stock :: SuSE distro install source code configuration. I have reinstalled alsa. :: I have also recompiled as sugested to no avail. I now suspect that it :: is a device conflict problem. Possible the same device being listed :: twice. Where is the master configuration file for detected hardware :: devices? /etc/? :: ::Thanks. Max :: ::On Monday 19 August 2002 07:25 pm, gilson redrick wrote: ::> On Monday, 19 Agosto 2002 12:37 PM, Max Webb wrote: ::> > Thanks but but I am using the standard SuSE 8.0 kernal and kernal ::> > source... ::> > ::> > The only thing I have done around the time this problem started was ::> > configure and recompile my kernel so as to enable SCSI emulation for ::> > my second CDROM/DVD drive, ::> ::> Correction: since you compiled your own kernel, you're no longer using ::> the kernel which came with the distro, for which ALSA was originally ::> compiled, ::> ::> > ALSA needs to be compiled for the kernel you are using. ::> ::> so you have to compile it now for the new kernel. ::> ::> My 1-1/2¢. :: ::-- ::Check the headers for your unsubscription address ::For additional commands send e-mail to suse-linux-e-help@suse.com ::Also check the archives at http://lists.suse.com ::Please read the FAQs: suse-linux-e-faq@suse.com
-=Ben
--=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
-- Be positive and you will prevail.
On the issue of "make cloneconfig" -- I don't seem to have that option! The message I get is that there is no target or something similar for cloneconfig. I would assume that I am perhaps missing a package that is required for making cloneconfig - if so which package should I install. I'm running 8.0 pro. TIA, Curtis On Tuesday 20 August 2002 00:50, Ben Rosenberg wrote:
No you have another issue. You shouldn't have to recompile ALSA if you just compiled a new kernel from the same default src's that shipped with the distribution. Otherwise I would have to do it everytime there is a kernel update (hint it's a new build ;)..and I don't. It just works. I would suggest doing it again. Remove the config file again and do a makecloneconfig to get the same config as the running kernel and choose the new options you wish. Maybe you checked something that you don't remember..etc..etc. We've all done it :)
* - (hbwebb@citlink.net) [020819 22:41]: ::Again this does not help because I have recompiled my kernal on another ::installation based on the standard linux-2.4.18.SuSE only changing SCSI ::emulation like this instance. I have done this before and not had a :: problem with sound afterward. This compilation was based on the stock :: SuSE distro install source code configuration. I have reinstalled alsa. :: I have also recompiled as sugested to no avail. I now suspect that it :: is a device conflict problem. Possible the same device being listed :: twice. Where is the master configuration file for detected hardware :: devices? /etc/? :: ::Thanks. Max :: ::On Monday 19 August 2002 07:25 pm, gilson redrick wrote: ::> On Monday, 19 Agosto 2002 12:37 PM, Max Webb wrote: ::> > Thanks but but I am using the standard SuSE 8.0 kernal and kernal ::> > source... ::> > ::> > The only thing I have done around the time this problem started was ::> > configure and recompile my kernel so as to enable SCSI emulation for ::> > my second CDROM/DVD drive, ::> ::> Correction: since you compiled your own kernel, you're no longer using ::> the kernel which came with the distro, for which ALSA was originally ::> compiled, ::> ::> > ALSA needs to be compiled for the kernel you are using. ::> ::> so you have to compile it now for the new kernel. ::> ::> My 1-1/2¢. :: ::-- ::Check the headers for your unsubscription address ::For additional commands send e-mail to suse-linux-e-help@suse.com ::Also check the archives at http://lists.suse.com ::Please read the FAQs: suse-linux-e-faq@suse.com
-=Ben
--=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
On Tue. Aug. 20, 2002 at 08:28:58 -0500 GMT, a lone cry was heard from
Curtis Rey
On the issue of "make cloneconfig" -- I don't seem to have that option!
Are you trying to compile a non-SuSE kernel? This option does not exist outside of SuSE. What you need to do in this case is to copy the .config file from the top level of the old source to the top level of the new one and do: make oldconfig Charles -- Avoid the Gates of Hell. Use Linux (Unknown source)
No, I'm using the k_deflt and the kernel_source-SuSE kernels I got it to work, Thanx for the help to all. Curtis On Tuesday 20 August 2002 09:45, Charles Philip Chan wrote:
On Tue. Aug. 20, 2002 at 08:28:58 -0500 GMT, a lone cry was heard from
Curtis Rey
in the wasteland called the Internet: On the issue of "make cloneconfig" -- I don't seem to have that option!
Are you trying to compile a non-SuSE kernel? This option does not exist outside of SuSE. What you need to do in this case is to copy the .config file from the top level of the old source to the top level of the new one and do:
make oldconfig
Charles
I'm experiencing the same problem, with the original kernel-sources from SuSE 7.2. I used a document from SuSE (I searched for modversion) , which also says to use "make cloneconfig". I get the error : no rule to make target 'cloneconfig'. Any help ? Charles Philip Chan wrote:
On Tue. Aug. 20, 2002 at 08:28:58 -0500 GMT, a lone cry was heard from Curtis Rey
in the wasteland called the Internet: On the issue of "make cloneconfig" -- I don't seem to have that option!
Are you trying to compile a non-SuSE kernel? This option does not exist outside of SuSE. What you need to do in this case is to copy the .config file from the top level of the old source to the top level of the new one and do:
make oldconfig
Charles
-- Avoid the Gates of Hell. Use Linux (Unknown source)
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
On Wed. Aug. 21, 2002 at 08:01:15 +0200 GMT, a lone cry was heard from
Koenraad Lelong
I'm experiencing the same problem, with the original kernel-sources from SuSE 7.2. I used a document from SuSE (I searched for modversion) , which also says to use "make cloneconfig". I get the error : no rule to make target 'cloneconfig'. Any help ?
This is really strange. I have never seen this problem with a SuSE kernel before. You could try the method that I have posted before and see if it works. I recap: What you need to do in this case is to copy the .config file from the top level of the old source to the top level of the new one and do: make oldconfig Charles -- "How should I know if it works? That's what beta testers are for. I only coded it." (Attributed to Linus Torvalds, somewhere in a posting)
I would like to, but what are those top levels ? I'm not compiling a kernel, but a driver (a loadable module). This needs modversions.h, which I can't find. So I searched SDB, with the forementioned results. I also searched my SuSE-pc for a .config, and the only one I found is one for that driver. Could it be possible that not all source files are present ? Charles Philip Chan wrote:
On Wed. Aug. 21, 2002 at 08:01:15 +0200 GMT, a lone cry was heard from Koenraad Lelong
in the wasteland called the Internet: I'm experiencing the same problem, with the original kernel-sources from SuSE 7.2. I used a document from SuSE (I searched for modversion) , which also says to use "make cloneconfig". I get the error : no rule to make target 'cloneconfig'. Any help ?
This is really strange. I have never seen this problem with a SuSE kernel before. You could try the method that I have posted before and see if it works. I recap:
What you need to do in this case is to copy the .config file from the top level of the old source to the top level of the new one and do:
make oldconfig
Charles
-- "How should I know if it works? That's what beta testers are for. I only coded it." (Attributed to Linus Torvalds, somewhere in a posting)
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
On Wed. Aug. 21, 2002 at 13:55:52 +0200 GMT, a lone cry was heard from
Koenraad Lelong
I would like to, but what are those top levels ?
The top level directory of the kernel source is: /usr/src/linux-version which is usually symlinked to /usr/src/linux
I'm not compiling a kernel, but a driver (a loadable module).
I see, I got in to this thread a bit late.
This needs modversions.h, which I can't find.
There are two modversions.h. They are both part of the kernel source. They are located at: /usr/src/linux/include/config and /usr/src/linux/include/linux
I also searched my SuSE-pc for a .config
This file will only exist if you have previously compiled the kernel yourself.
Could it be possible that not all source files are present ?
It looks like you haven't installed the full kernel source package. Charles -- "Are [Linux users] lemmings collectively jumping off of the cliff of reliable, well-engineered commercial software?" (By Matt Welsh)
On my system : /usr/src/linux/include/config does NOT exist ! /usr/src/linux/include/linux does exist, but no modversions.h. "kernel-source" and "linux" were installed (from the 7.2 pro DVD), anything else ? What about sending it to me ? Of course this needs to be the right version. About jumping in : so did I, because the first guy discribed something I did also to solve my problem. Charles Philip Chan wrote:
On Wed. Aug. 21, 2002 at 13:55:52 +0200 GMT, a lone cry was heard from Koenraad Lelong
in the wasteland called the Internet: I would like to, but what are those top levels ?
The top level directory of the kernel source is:
/usr/src/linux-version
which is usually symlinked to
/usr/src/linux
I'm not compiling a kernel, but a driver (a loadable module).
I see, I got in to this thread a bit late.
This needs modversions.h, which I can't find.
There are two modversions.h. They are both part of the kernel source. They are located at:
/usr/src/linux/include/config
and
/usr/src/linux/include/linux
I also searched my SuSE-pc for a .config
This file will only exist if you have previously compiled the kernel yourself.
Could it be possible that not all source files are present ?
It looks like you haven't installed the full kernel source package.
Charles
-- "Are [Linux users] lemmings collectively jumping off of the cliff of reliable, well-engineered commercial software?" (By Matt Welsh)
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
I don't know why, but I looked in /usr/src/linux/Rules.make. There are lines containing modversions.h (update-modverfile). Any use ? Koenraad Lelong wrote:
On my system : /usr/src/linux/include/config does NOT exist ! /usr/src/linux/include/linux does exist, but no modversions.h. "kernel-source" and "linux" were installed (from the 7.2 pro DVD), anything else ? What about sending it to me ? Of course this needs to be the right version. About jumping in : so did I, because the first guy discribed something I did also to solve my problem.
Charles Philip Chan wrote:
On Wed. Aug. 21, 2002 at 13:55:52 +0200 GMT, a lone cry was heard from Koenraad Lelong
in the wasteland called the Internet: I would like to, but what are those top levels ?
The top level directory of the kernel source is:
/usr/src/linux-version
which is usually symlinked to
/usr/src/linux
I'm not compiling a kernel, but a driver (a loadable module).
I see, I got in to this thread a bit late.
This needs modversions.h, which I can't find.
There are two modversions.h. They are both part of the kernel source. They are located at:
/usr/src/linux/include/config
and
/usr/src/linux/include/linux
I also searched my SuSE-pc for a .config
This file will only exist if you have previously compiled the kernel yourself.
Could it be possible that not all source files are present ?
It looks like you haven't installed the full kernel source package.
Charles
-- "Are [Linux users] lemmings collectively jumping off of the cliff of reliable, well-engineered commercial software?" (By Matt Welsh)
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
------------------------------------------------------------------------ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
I downloaded the kernel source for 7.3 and modversions.h is right there in /usr/src/linux/include/linux It looks like you do not install the full source. The full kernel source is located in d2. In case you can't find it on your DVD, here is a download link: ftp://ftp.rpmfind.net/linux/SuSE-Linux/i386/7.3/suse/d2/kernel-source.rpm Charles -- "Even more amazing was the realization that God has Internet access. I wonder if He has a full newsfeed?" (By Matt Welsh)
Just to verify, I checked both the DVD and de CD's of my distri, and neither have the modversions.h. This morning I downloaded both V7.2 and V7.3 kernel-source RPM, and again : V7.2 has no modversions.h, V7.3 indeed has it. I hope I can use that V7.3 file on my V7.2 machine. Comments ? Or should I compile the whole kernel and install it (shiver and shake, never done this) ? Thanks very much anyway. Charles Philip Chan wrote:
I downloaded the kernel source for 7.3 and modversions.h is right there in
/usr/src/linux/include/linux
It looks like you do not install the full source. The full kernel source is located in d2. In case you can't find it on your DVD, here is a download link:
ftp://ftp.rpmfind.net/linux/SuSE-Linux/i386/7.3/suse/d2/kernel-source.rpm
Charles
-- "Even more amazing was the realization that God has Internet access. I wonder if He has a full newsfeed?" (By Matt Welsh)
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v.
Gilson, I just recompiled Alsa from the stock SuSE 8.0 /usr/src/kernel-modules/alsa-driver/ instead of other sources. It worked this time. Thank you for your suggestion. I still don't think it had to do with the recompile which I have done before under the same conditions with no alsa problems. My belief is that all of these problems are due to what I feel is a botched or corrupted SuSE YoU update a few days ago. Looking back right after I did the update, I had a problem involving pppd, in which files were missing from my pppd directory and had to be copied from another installation for pppd to work. It was at that time that the sound card stopped working. None the less, your suggestion of alsa recompilation did the trick. And I am greatly indebted to you. Thank you. Max On Monday 19 August 2002 07:25 pm, gilson redrick wrote:
On Monday, 19 Agosto 2002 12:37 PM, Max Webb wrote:
Thanks but but I am using the standard SuSE 8.0 kernal and kernal source...
The only thing I have done around the time this problem started was configure and recompile my kernel so as to enable SCSI emulation for my second CDROM/DVD drive,
Correction: since you compiled your own kernel, you're no longer using the kernel which came with the distro, for which ALSA was originally compiled,
ALSA needs to be compiled for the kernel you are using.
so you have to compile it now for the new kernel.
My 1-1/2¢.
participants (8)
-
-
-
Ben Rosenberg
-
Charles Philip Chan
-
Curtis Rey
-
dh
-
gilson redrick
-
Koenraad Lelong
-
Max Webb