[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: es1371



romain lerallut wrote:
> 
> Hello debian-users !
> 
> I have a problem using a es1371 sound card (it's really a SB128 PCI).
> In a nutshell: the system can't talk to the card...
> 
> I am using woody and a kernel 2.2.17
> 
> Here's what I did:
> 
> recompiling the kernel (sound support: module , es1371: module )
>  es1371.o and soundcore.o are in /lib/modules/2.2.17/misc,  OK
> 
> reboot.
> 
> I see something flashing about a char-major-14 but It's too fast.
>  adding a "alias char-major-14 es1371" to the /etc/modutils/aliases
>  seems to have fixed it. At least I don't get that error anymore.
> (I got this in reading Documentation/sound/Introduction in the kernel source tree.)
> 
> the es1371 driver gets loaded, no complaint
> "es1371:  es1371 card found rev8, io=0xe000 , IRQ=11 "  and so on.
> the card is in /proc/pci
> 
> lsmod shows:
> es1371  0   unused
> soundcore  4  [es1371]
> 
> It seems fine until  now.(at least to me)
> 
> BUT
> - there's nothing in /dev/sndstat  (the file "exists" but cat /dev/sndstat say no such device)
> - there's no /proc/sound file
> AND
> - if I try to use the sound card the whole system freezes.( I experience it mostly with
> xmms1.2.3 )
> 
> I'd REALLY appreciate someone who uses an es1371 to tell me exactly what I'm
> missing (option something or other).
> I've already  RTFMed  /usr/src/linux/Documentation/sound/es1371 , but there's
> scarcely any info in there.
> 
> Thanks
> Romain
> 
> PS: i've this sndconfig lurking around, is it useful ?
> 
Hi!
I have a SB128 working. However I compiled the es1371 into the kernel,
since I had problems with it as a module (don't remember what was the
reason, if I ever found it). Even that way it did not work initially. I
later found out, that my BIOS settings were at fault, since PnP was
enabled and that way the kernel did not see the SB. Now it's working.
You might also try the es1370 driver, since The SB128 can supposedly
also contain that chip.

BTW. You can look at the output during boot with "dmsg"

HTH
Thorsten



Reply to: