On Sun, 2006-01-29 at 23:13 -0500, Nick Zentena wrote:

On Sunday 29 January 2006 23:00, Marshall Lake wrote:

...

I posted the description below here three or four days ago of a problem I encountered. So far I've found no help.

Is reinstalling the system the only thing to do to correct the problem?

If there is someplace else I could go to seek help please direct me.

Any chance you're low on disk space? I've had the same problem. I guess on reboot the system needs some disk space to load the modules. Have you watched it boot ?

This has absolutely nothing to do with booting (other than tmp space), modules don't load onto the harddrive they load into memory. harddrive space != memory (RAM) -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

...

Sound has been fine from initial installation a few months ago until suddenly there was no sound a couple of days ago. Reboot, no change. Reboot into XP and the sound is fine. Reboot into Linux, no sound.

I went into YaST->Hardware->Sound and the SB Audigy shows up as properly configured. I removed the SB Audigy configuration and then tried to set it up again. I got an error message saying that the module snd-emu10k1 cannot be loaded. Checking /lib/modules shows snd-emu10k1.ko, snd-emu10k1-synth.ko and snd-emu10k1x.ko

How do I procede from here to correct the problem?

Maybe the error message was telling you the module was still loaded from the previous boot? What does lsmod show?

lsmod | grep snd returns nothing. I assume this is because I've rebooted since unconfiguring the soundcard.

You could try (as root) modprobe -r snd-emu10k1*, delete the file /etc/modprobe.d/sound and run YaST to install the card "from scratch" again.

modprobe -r snd-emu10k1* found nothing. I deleted /etc/modprobe.d/sound but trying to reconfigure the soundcard via YaST gave me the same error as mentioned above ... module snd-emu10k1 cannot be loaded. -- Marshall Lake -- mlake@mlake.net -- http://mlake.net

...

modprobe -r snd-emu10k1* found nothing. I deleted /etc/modprobe.d/sound but trying to reconfigure the soundcard via YaST gave me the same error as mentioned above ... module snd-emu10k1 cannot be loaded.

I think you would enjoy and benefit greatly from 'man modprobe' and 'man depmod' to understand better the dynamic loading and unloading of modules in Linux. The "- r" flag was meant to unload the snd-emu10k1* modules that, in theory, were still loaded and preventing YaST from configuring the card. That was just a guess on my part and it's moot, anyway, since it appears the modules aren't loading at boot now.

I ran: modprobe snd-emu10k1 depmod -A The proper modules seemed to get loaded, but I still get a same error when configuring the sound card.

In any event, it appears your problem is a known hardware/module specific bug. I don't have that hardware so I can't really help you with it. The good news is you are in extremely excellent and competent hands with Anders paying attention (grovel grovel!) :-)

So, I guess there's nothing left for me to do until I hear back from Anders? -- Marshall Lake -- mlake@mlake.net -- http://mlake.net

...

I'm running 10.0 on an HP Media Center PC 873N containing an SB Audigy board.

Sound has been fine from initial installation a few months ago until suddenly there was no sound a couple of days ago. Reboot, no change. Reboot into XP and the sound is fine. Reboot into Linux, no sound.

I went into YaST->Hardware->Sound and the SB Audigy shows up as properly configured. I removed the SB Audigy configuration and then tried to set it up again. I got an error message saying that the module snd-emu10k1 cannot be loaded. Checking /lib/modules shows snd-emu10k1.ko, snd-emu10k1-synth.ko and snd-emu10k1x.ko

This is a problem I experienced as well. The problem isn't that the module never gets loaded, the problem is that when it does, udev fails to work. It never creates the device nodes in /dev/snd that it's supposed to create. That's what YaST looks for when it tries to determine if the module is loaded or not

I filed a bug for it, but unfortunately, the bug seems to be intermittant and fairly random, so it's very difficult to debug. On my last boot, I got the nodes (it may have something to do with the latest update of the kernel, not sure, have you updated?)

My system auto-updates everything but the kernel once per week. And now that you mention it the problem did first show up after auto-updating last week. When I reboot the system sound still doesn't work for me. -- Marshall Lake -- mlake@mlake.net -- http://mlake.net

On Monday 30 January 2006 9:40 am, Mike McMullin wrote:
> On Sun, 2006-01-29 at 23:00 -0500, Marshall Lake wrote:
> > I posted the description below here three or four days ago of a
> > problem I encountered.  So far I've found no help.
> >
> > Is reinstalling the system the only thing to do to correct the
> > problem?
> >
> > If there is someplace else I could go to seek help please direct
> > me.
> >
> > --------------------original post-------------------------
> > I'm running 10.0 on an HP Media Center PC 873N containing an SB
> > Audigy board.
> >
> > Sound has been fine from initial installation a few months ago
> > until suddenly there was no sound a couple of days ago.  Reboot, no
> > change. Reboot into XP and the sound is fine.  Reboot into Linux,
> > no sound.
> >
> > I went into YaST->Hardware->Sound and the SB Audigy shows up as
> > properly configured.  I removed the SB Audigy configuration and
> > then tried to set it up again.  I got an error message saying that
> > the module snd-emu10k1 cannot be loaded.  Checking /lib/modules
> > shows snd-emu10k1.ko, snd-emu10k1-synth.ko and snd-emu10k1x.ko
> >
> > How do I procede from here to correct the problem?

> 1) How do you know "I went into YaST->Hardware->Sound and the SB
> Audigy shows up as properly configured.", this?  Was this the actual
> original config from when the card was first working, or did someone
> with the same card confirm this driver module?


Following this thread I wondered if you checked the Volume in your 
configuration was actually set at the level you originally set? I used 
to have a random problem w/ the system somehow resetting the volume to 
nearly zero periodically. It was most annoying. And would sometimes 
happen when I was actually listening to the radio ..  Never could 
figure out why ? Might have been Anders 'random bug'  or not... but I 
haven't had it happen on this box so I can't join the hunt.. 


I would recommend that you open yast hardware configuration and when you 
see the card is "configured" check the volume settings ... reset to 
your desired levels if need be ...  It's annoying but might solve the 
problem whilst the rest of the gang chases the bug.. and supplies a 
fix.

Reinstalling isn't usually necessary unless something really bad has 
happened. Keeping backups of assorted config files that work for you 
can save a system you mess up yourself. ( been there , done that.... )


-- 
j
Once in a while you get shown the light
In the strangest of places if you look at it right -- song lyric

On Tuesday 31 January 2006 01:09, Marshall Lake wrote:

My problem is that I can't even configure the card.

try alsaconf instead of yast, plus my tip in previuos mail.

On Monday 30 January 2006 18:57, Marshall Lake wrote:

That worked using alsaconf! Thanks very much for your help.

Great work, Andrei, and congratulations, Marshall! - Carl