Le Wed, 4 May 2005 10:51:57 +0100 Declan Moriarty <[EMAIL PROTECTED]> a �crit :
> The es1371 chip is _not_ your average soundcard, more like the > "winsoundard" (think of winmodemds :-o). The cpu does a lot more work > and in windows it uses megabytes of drivers. Have a look in your kernel > source ~/Documentation/sound/oss/es1371.txt for a good description of > the problems. Well, I investigated the problem a little. It doesn't seem to be the sound after all. My installation is correct, and no, I'm not the kind of szcrumlfbold to forget to read the docs before posting :-) I'm of course in the audio group. > > I know it comes from sound because before I was belonging to the audio > > group, I had no trouble. Now, some games definitly freeze the system > > (or just X, but I don't know how to get out). It looks I have problems with SDL, or something like that (something strongly related to games, anyway :-). I'll try some strace stuff to find out what is happening. > I would start by reading > ~/Documentation/sound/alsa/ALSA-Configuration.txt where it refers to > your card. Build a kernel with modules and allowing forced unloading > of them. That way you can have options in modprobe.conf to help you. > When things go horribly wrong, you can use Ctrl_Alt_F<something> open a > root console, and forcibly remove the module or kill processes. I compiled the alsa driver in module, but it doesn't seem to solve the problem. And I did NO udev configuration ;-) The sound works, not the games (crash after a while). When I say "crash", let's be precise : - if the game is running full screen, my keyboard is inoperant, I CAN'T get back to a console to kill anything. So hard reboot (smash the keyboard, throw away the 30 pounds monitor, axe the tower... and finally press the little button) is my only option. - if the game is running windowed, I loose the use of anything in X, but at least I can reach a console and kill the crashed game. But game in window is no fun :-( > If your problem is simply that you have to join the audio group again, > please arrange to have yourself shot at dawn for asking us to debug your > system, when we should have been debugging the sysadmin :). The sysadmin learned from his past experiences ;-) > > Do you have a solution ? Do I have to compile the driver in module > > form ? And if so, how do I configure uudev ? > Join the audio group. If that fixes it, the instructions are above. > Have fun with udev. What is that anyhow?:-) The trouble with living 'on > the bleeding edge' is that you bleed. When all you guys have grey > hair from debugging it, then I'll think about using it.But linux > crashing is stupid. You have a setup, compile, or permissions error. > If you change everything in the sound area to 666 you'll soon find out > if permissions was your problem. Then fix it. Sound works fine without permissions hack, no ? Or is it sometimes necessary to go threw this ? Thanks anyway for your (sarcastic :-) response. \bye -- Nicolas FRANCOIS http://nicolas.francois.free.fr We are the Micro$oft. Resistance is futile. You will be assimilated. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
