Now my problem is solve Which way ? Well....
I recompile the kernel with sound card support and only es1371 drivers compiled...All is fine now May the force be with you Pierre [EMAIL PROTECTED] David P James wrote: > Pierre Dupuis was roused into action on 09/11/02 09:58 and wrote: > >> Hi All :) >> >> So i'm back on woody this time.... >> But i always got one little problem, my soundcard which is a Creative >> SB128PCI, does not respond....I'm using kernel 2.4.18. Can someone >> tell me which module must i compile in the kernel to make my sound >> card working properly :) >> > > Same setup, similar problem. I can get it to work, but it is not a > pretty method and not terribly efficient (and it has to be done each > time the computer reboots). > > The module is es1371 (or possibly es1370). I've tried loading it with > io and irq specifications, but it is still not enough. > > I also have the sound and soundcore modules set to load. > > Here's what happens when I boot: > > -no mention of loading the module(s) in the boot messages, despite it > being in /etc/modules with the correct io and irq parameters > -when starting Gnome or KDE, off in the background (if you switch to > one of the other virtual consols) I see the following message repeated: > > Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 > sb: No ISAPnP cards found, trying standard ones... > sb: dsp reset failed > > At this stage, apps like XMMS complain about the sound card. Not only > that, the directory /var/log/ksymoops starts filling up quite quickly > with files with .ksyms and .modules extensions - I've filled up my > /var partition a few times because of this, forcing me to clean out > that directory. > > Through trial and error, I've figured out how to stop this - by > running sndconfig. The problem there is that the configuration fails, > but it does stop the previous problems of the infinite messages and > the infinite files in /var/log/ksymoops. I used to then try a manual > configuration in sndconfig, but that just fails as well and restarts > the problem, so I now just exit once the automatic config fails. > > But after that, everything seems to work, even though, as I said, > sndconfig failed to actually configure anything. > > That is just plain wierd as far as I'm concerned... > > For what it is worth, my system has elected to put my soundcard, my > PCI ethernet card and the onboard USB controller all on the same IRQ - > 11. I've got an AHA-2940UW SCSI card occupying IRQ 10 and an older > AHA-1502 at IRQ 9 (for a Microtek scanner). I would have expected the > soundcard to take IRQ 5 like my old ISA SB16 did, but it did not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
