Re: [Alsa-user] es18xx soundcard troubles
On 08/02/2007 03:03 PM, Yan Seiner wrote: HAH! Success! Congrats :-) Here's the magic incantations on a Compaq Armada 1700, ess1869 chipset, and 2.6.21 kernel: boot with noapic acpi=off pci=biosirq I doubt the noapic makes a difference? acpi *must* be enabled in the bios, and disabled with a kernel parameter, otherwise the cooling fan will not work. I expect (and hope) the ACPI crowd would be interested in hearing about your ACPI trouble -- hard-locking is no fun... If you're willing to follow up on it, [EMAIL PROTECTED] and Len Brown [EMAIL PROTECTED] would be the addresses to poke! edit /etc/modprobe.d/sound to read: alias snd-card-0 snd-es18xx options snd-es18xx index=0 enable=1 port=0x220 fm_port=0x388 mpu_port=0x300 irq=5 dma1=0 dma2=1 *DO NOT* use the isapnp=0 parameter. This will cause insmod to fail. Without isapnp=0, you should in fact be able to leave out all the other parameters... Strangely, alsaplayer will not work, but xmms works just fine. aplay foo.wav is always the most direct ALSA test. Rene. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
Rene Herman napsal(a): On 08/01/2007 04:07 PM, Yan Seiner wrote: From the various threads I've found on this, it appears that the driver broke sometime fairly recently, and that it may indeed work with older kernels. Perhaps the fault is with the acpi system changes in recent kernels. The fact that the driver finds the chip at all at least means it's a very different problem than the problem Troy is having. I read through the things you posted, but it looks scary and probably not any of ALSA's doing... Yes, If you could try for example the latest 2.6.18.x and (if neccessary) progressively further down that would probably be the best way to start debugging it (and if it's more ACPI related, them linux-kernel would be the right list to post results). HAH! Success! Here's the magic incantations on a Compaq Armada 1700, ess1869 chipset, and 2.6.21 kernel: boot with noapic acpi=off pci=biosirq acpi *must* be enabled in the bios, and disabled with a kernel parameter, otherwise the cooling fan will not work. edit /etc/modprobe.d/sound to read: alias snd-card-0 snd-es18xx options snd-es18xx index=0 enable=1 port=0x220 fm_port=0x388 mpu_port=0x300 irq=5 dma1=0 dma2=1 *DO NOT* use the isapnp=0 parameter. This will cause insmod to fail. Strangely, alsaplayer will not work, but xmms works just fine. --Yan -- o__ ,/'_ o__ (_)\(_),/'_ o__ Yan Seiner (_)\(_) ,/'_ o__ o__ Certified Personal Trainer (_)\(_) ,/'_ ,/'_ Licensed Professional Engineer (_)\(_) (_)\(_) Linux stuff has made big progress over the competition. When things sit and don't start right away, we have a watch, and those poor guys have to settle for an hourglass. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
On 08/01/2007 02:57 AM, Troy Heidner wrote:
Thanks for the help!
Sure, but please always keep existing CCs intact on these kinds of messages.
Otherwise the next poor sod that googles for the same problem hits on these
first few messages of a conversation, but not the solution since that was in
private mail. Just always use reply to all when dealing with Linux lists.
Here's what I get when I cat those files:
[ ... ]
ESS0009
ESS1879
There's an ESS1879 in there, but I'm not sure what that tells me?
It tells you (and me...) that indeed the problem is just that the driver
does not know it should be driving your chip. The solution is to tell it
this, and the attached trivial patch to the driver would do this.
The ESS0009 is the chip's CTRL port but I assume from the single ESS1869
already present there that it's okay without.
If you are upto applying the attached patch and rebuilding the kernel please
do so, but assuming you are not, you can work-around the driver not knowing
about your chip by specifying all resources manually.
Please do a:
cat /sys/bus/pnp/devices/foo/resources
where foo is the directory in which the id file says ESS179. It might
just say
state = disabled
If it does, do (as root):
echo activate /sys/bus/pnp/devices/foo/resources
after which the next
cat /sys/bus/pnp/devices/foo/resources
should tell you something fairly close to:
state = active
io 0x220-0x22f
io 0x388-0x38b
io 0x330-0x331
irq 5
dma 1
dma 0
At this point, you can try loading the driver, specifying these resources:
modprobe snd-es18xx isapnp=0 port=0x220 fm_port=0x388\
mpu_port=0x330 irq=5 dma1=1 dma2=0
If all is well, you now have sound (remember to unmute and up the volumes
with a mixer such as alsamixer!).
If this method works for you, you'll have to figure out how to integrate it
into your bootscripts yourself as this is different with every distribution.
Simply doing the enabling/loading from an rc.local could be easiest...
If you can confirm that it works after this manual enabling (or after just
applying and testing the patch ofcourse), I'll make sure it ends up upstream
so that future drivers will work out of the box.
Rene.
diff --git a/sound/isa/es18xx.c b/sound/isa/es18xx.c
index f7732bf..69b1c8a 100644
--- a/sound/isa/es18xx.c
+++ b/sound/isa/es18xx.c
@@ -2042,6 +2042,7 @@ static int pnpc_registered;
static struct pnp_device_id snd_audiodrive_pnpbiosids[] = {
{ .id = ESS1869 },
+ { .id = ESS1879 },
{ .id = }/* end */
};
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
Rene Herman napsal(a): The ESS0009 is the chip's CTRL port but I assume from the single ESS1869 already present there that it's okay without. If you are upto applying the attached patch and rebuilding the kernel please do so, but assuming you are not, you can work-around the driver not knowing about your chip by specifying all resources manually. Please do a: cat /sys/bus/pnp/devices/foo/resources where foo is the directory in which the id file says ESS179. It might just say state = disabled If it does, do (as root): echo activate /sys/bus/pnp/devices/foo/resources after which the next cat /sys/bus/pnp/devices/foo/resources should tell you something fairly close to: state = active io 0x220-0x22f io 0x388-0x38b io 0x330-0x331 irq 5 dma 1 dma 0 At this point, you can try loading the driver, specifying these resources: modprobe snd-es18xx isapnp=0 port=0x220 fm_port=0x388\ mpu_port=0x330 irq=5 dma1=1 dma2=0 If all is well, you now have sound (remember to unmute and up the volumes with a mixer such as alsamixer!). If this method works for you, you'll have to figure out how to integrate it into your bootscripts yourself as this is different with every distribution. Simply doing the enabling/loading from an rc.local could be easiest... If you can confirm that it works after this manual enabling (or after just applying and testing the patch ofcourse), I'll make sure it ends up upstream so that future drivers will work out of the box. Hi Rene: I've also been trying to get this chip to work. This exchange gives me new hope. Here's what I have: debian:~# cat /sys/bus/pnp/devices/00:*/id | grep ESS ESS0006 ESS1869 debian:~# cd /sys/bus/pnp/devices/00:05 debian:/sys/bus/pnp/devices/00:05# ls bus id options power resources subsystem uevent debian:/sys/bus/pnp/devices/00:05# cat id ESS0006 debian:/sys/bus/pnp/devices/00:05# cat resources state = active io 0x250-0x257 debian:/sys/bus/pnp/devices/00:05# cd ../00:06 debian:/sys/bus/pnp/devices/00:06# cat resources state = active io 0x220-0x22f io 0x388-0x38b io 0x300-0x301 irq 5 dma 0 dma 1 So I've tried modprobe snd_es18xx isapnp=0 port=0x220 fm_port=0x388 mpu_port=0x330 irq=5 dma1=1 dma2=0 but in dmesg I get: reset at 0x220 failed!!! es18xx: [0x220] ESS chip not found PnPBIOS: get_dev_node: function not supported on this system pnp: Failed to disable device 00:06. ESS AudioDrive ES18xx soundcard not found or device busy And, of course, no sound. The system is a Compaq Armada 1700, an old laptop. Any suggestions? -- o__ ,/'_ o__ (_)\(_),/'_ o__ Yan Seiner (_)\(_) ,/'_ o__ o__ Certified Personal Trainer (_)\(_) ,/'_ ,/'_ Licensed Professional Engineer (_)\(_) (_)\(_) Linux stuff has made big progress over the competition. When things sit and don't start right away, we have a watch, and those poor guys have to settle for an hourglass. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
Yan Seiner napsal(a): Rene Herman napsal(a): The ESS0009 is the chip's CTRL port but I assume from the single ESS1869 already present there that it's okay without. If you are upto applying the attached patch and rebuilding the kernel please do so, but assuming you are not, you can work-around the driver not knowing about your chip by specifying all resources manually. Please do a: cat /sys/bus/pnp/devices/foo/resources where foo is the directory in which the id file says ESS179. It might just say state = disabled If it does, do (as root): echo activate /sys/bus/pnp/devices/foo/resources after which the next cat /sys/bus/pnp/devices/foo/resources should tell you something fairly close to: state = active io 0x220-0x22f io 0x388-0x38b io 0x330-0x331 irq 5 dma 1 dma 0 At this point, you can try loading the driver, specifying these resources: modprobe snd-es18xx isapnp=0 port=0x220 fm_port=0x388\ mpu_port=0x330 irq=5 dma1=1 dma2=0 If all is well, you now have sound (remember to unmute and up the volumes with a mixer such as alsamixer!). If this method works for you, you'll have to figure out how to integrate it into your bootscripts yourself as this is different with every distribution. Simply doing the enabling/loading from an rc.local could be easiest... If you can confirm that it works after this manual enabling (or after just applying and testing the patch ofcourse), I'll make sure it ends up upstream so that future drivers will work out of the box. Hi Rene: I've also been trying to get this chip to work. This exchange gives me new hope. Here's what I have: debian:~# cat /sys/bus/pnp/devices/00:*/id | grep ESS ESS0006 ESS1869 debian:~# cd /sys/bus/pnp/devices/00:05 debian:/sys/bus/pnp/devices/00:05# ls bus id options power resources subsystem uevent debian:/sys/bus/pnp/devices/00:05# cat id ESS0006 debian:/sys/bus/pnp/devices/00:05# cat resources state = active io 0x250-0x257 debian:/sys/bus/pnp/devices/00:05# cd ../00:06 debian:/sys/bus/pnp/devices/00:06# cat resources state = active io 0x220-0x22f io 0x388-0x38b io 0x300-0x301 irq 5 dma 0 dma 1 So I've tried modprobe snd_es18xx isapnp=0 port=0x220 fm_port=0x388 mpu_port=0x330 irq=5 dma1=1 dma2=0 but in dmesg I get: reset at 0x220 failed!!! es18xx: [0x220] ESS chip not found PnPBIOS: get_dev_node: function not supported on this system pnp: Failed to disable device 00:06. ESS AudioDrive ES18xx soundcard not found or device busy And, of course, no sound. The system is a Compaq Armada 1700, an old laptop. Any suggestions? Hmm.. More info: lspnp shows: 00:05 ESS0006 (unknown) 00:06 CPQb0ac (unknown) debian:/sys/bus/pnp/devices/00:06# cat id CPQb0ac ESS1869 Here's a thread from the ubuntu forums: http://ubuntuforums.org/archive/index.php/t-419855.html Basically I'm seeing the same problems, except that I am running Debian Lenny: debian:/sys/bus/pnp/devices/00:06# uname -a Linux debian 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 GNU/Linux The mixer comes up and I can manipulate all of the controls, but any attempt to write to the deice results in no sound and blocking. --Yan -- o__ ,/'_ o__ (_)\(_),/'_ o__ Yan Seiner (_)\(_) ,/'_ o__ o__ Certified Personal Trainer (_)\(_) ,/'_ ,/'_ Licensed Professional Engineer (_)\(_) (_)\(_) Linux stuff has made big progress over the competition. When things sit and don't start right away, we have a watch, and those poor guys have to settle for an hourglass. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
Yan Seiner napsal(a): Yan Seiner napsal(a): Hi Rene: I've also been trying to get this chip to work. This exchange gives me new hope. Here's what I have: debian:~# cat /sys/bus/pnp/devices/00:*/id | grep ESS ESS0006 ESS1869 debian:~# cd /sys/bus/pnp/devices/00:05 debian:/sys/bus/pnp/devices/00:05# ls bus id options power resources subsystem uevent debian:/sys/bus/pnp/devices/00:05# cat id ESS0006 debian:/sys/bus/pnp/devices/00:05# cat resources state = active io 0x250-0x257 debian:/sys/bus/pnp/devices/00:05# cd ../00:06 debian:/sys/bus/pnp/devices/00:06# cat resources state = active io 0x220-0x22f io 0x388-0x38b io 0x300-0x301 irq 5 dma 0 dma 1 So I've tried modprobe snd_es18xx isapnp=0 port=0x220 fm_port=0x388 mpu_port=0x330 irq=5 dma1=1 dma2=0 but in dmesg I get: reset at 0x220 failed!!! es18xx: [0x220] ESS chip not found PnPBIOS: get_dev_node: function not supported on this system pnp: Failed to disable device 00:06. ESS AudioDrive ES18xx soundcard not found or device busy And, of course, no sound. The system is a Compaq Armada 1700, an old laptop. Any suggestions? Hmm.. More info: lspnp shows: 00:05 ESS0006 (unknown) 00:06 CPQb0ac (unknown) debian:/sys/bus/pnp/devices/00:06# cat id CPQb0ac ESS1869 Here's a thread from the ubuntu forums: http://ubuntuforums.org/archive/index.php/t-419855.html Basically I'm seeing the same problems, except that I am running Debian Lenny: debian:/sys/bus/pnp/devices/00:06# uname -a Linux debian 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 GNU/Linux The mixer comes up and I can manipulate all of the controls, but any attempt to write to the deice results in no sound and blocking. Sorry to keep bothering the list, but I am so close to getting this On my laptop, acpi causes the system to hard-lock after a few minutes of activity. So I am booting with acpi-off. Just to test things, I installed a 2.6.21 486 kernel, and booted. I forgot to add the acpi=off parameter. Before the system hard-locked, I was able to look at /sys and check out the id for the sound card. debian:/sys/bus/pnp/devices# lspnp 00:00 PNP0a03 PCI bus 00:01 PNP0501 16550A-compatible serial port 00:02 PNP0700 PC standard floppy disk controller 00:03 SMCf010 SMC Fast Infrared Port 00:04 PNP0401 ECP printer port 00:05 PNP0c01 System board 00:06 PNP0c04 Math coprocessor 00:07 PNP0200 AT DMA controller 00:08 PNP0800 AT speaker 00:09 PNP0b00 AT real-time clock 00:0a PNP0303 IBM enhanced keyboard (101/102-key, PS/2 mouse support) 00:0b PNP0f13 PS/2 port for PS/2-style mice 00:0c ESS1869 (unknown) 00:0d PNPb02f Joystick/Game port 00:0e CPQb05b (unknown) 00:0f PNP0c01 System board 00:10 PNP0c01 System board 00:11 PNP0c02 Motherboard resources debian:/sys/bus/pnp/devices# cd 00:0c debian:/sys/bus/pnp/devices/00:0c# ls bus id options power resources subsystem uevent debian:/sys/bus/pnp/devices/00:0c# cat id ESS1869 debian:/sys/bus/pnp/devices/00:0c# cat resources state = disabled io 0x220-0x22f io 0x388-0x38b io 0x300-0x301 irq 5 dma 0 dma 1 OK, it shows up as unknown and disabled with acpi enabled. Of course the system locked before I was able to test the solution given earlier in this thread. From the various threads I've found on this, it appears that the driver broke sometime fairly recently, and that it may indeed work with older kernels. Perhaps the fault is with the acpi system changes in recent kernels. With acpi=off, the system acts as before: debian:/sys/bus/pnp/devices# cat 00:06/id CPQb0ac ESS1869 debian:/sys/bus/pnp/devices# cd 00:06 debian:/sys/bus/pnp/devices/00:06# ls bus id options power resources subsystem uevent debian:/sys/bus/pnp/devices/00:06# cat resources state = active io 0x220-0x22f io 0x388-0x38b io 0x300-0x301 irq 5 dma 0 dma 1 dmesg contains the following: es18xx: unable to grap ports 0x220-0x22f PNPBIOS fault.. attempting recovery. PnPBIOS: Warning! Your PnP BIOS caused a fatal error. Attempting to continue PnPBIOS: You may need to reboot with the pnpbios=off option to operate stably PnPBIOS: Check with your vendor for an updated BIOS PnPBIOS: set_dev_node: unexpected status 0x28 pnp: Failed to disable device 00:06. es18xx-pnpbios: probe of 00:06 failed with error -16 dsp_command: timeout (0xc0) dsp_command: timeout (0xc0) --Yan -- o__ ,/'_ o__ (_)\(_),/'_ o__ Yan Seiner (_)\(_) ,/'_ o__ o__ Certified Personal Trainer (_)\(_) ,/'_ ,/'_ Licensed Professional Engineer (_)\(_) (_)\(_) Linux stuff has made big progress over the competition. When things sit and don't start right away, we have a watch, and those poor guys have to settle for an hourglass. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration
Re: [Alsa-user] es18xx soundcard troubles
On 08/01/2007 04:07 PM, Yan Seiner wrote: From the various threads I've found on this, it appears that the driver broke sometime fairly recently, and that it may indeed work with older kernels. Perhaps the fault is with the acpi system changes in recent kernels. The fact that the driver finds the chip at all at least means it's a very different problem than the problem Troy is having. I read through the things you posted, but it looks scary and probably not any of ALSA's doing... Yes, If you could try for example the latest 2.6.18.x and (if neccessary) progressively further down that would probably be the best way to start debugging it (and if it's more ACPI related, them linux-kernel would be the right list to post results). Rene. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
Rene Herman wrote: On 08/01/2007 04:07 PM, Yan Seiner wrote: From the various threads I've found on this, it appears that the driver broke sometime fairly recently, and that it may indeed work with older kernels. Perhaps the fault is with the acpi system changes in recent kernels. The fact that the driver finds the chip at all at least means it's a very different problem than the problem Troy is having. I read through the things you posted, but it looks scary and probably not any of ALSA's doing... It's become a matter of pure stubbornness I refuse concede defeat. :-) Yes, If you could try for example the latest 2.6.18.x and (if neccessary) progressively further down that would probably be the best way to start debugging it (and if it's more ACPI related, them linux-kernel would be the right list to post results). By disabling both acpi and pnpbios, and then loading the module, I was able to produce a very loud continuous foghorn that varied in pitch as I turned the master volume up and down... I guess that's progress of sorts. :-| I'll try an older kernel. We'll see if that makes a difference. --Yan - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
Rene,
Holy crap, I've got sound! :)
You were right, that modprobe line did it. The state= line in the
resources file was already set to active. A couple of the resources were
different than you listed, but when I plugged the appropriate values into
the modprobe line, everything worked! The primary i/o port was 0x240 and
the second dma channel was 3, but that was it! I put the line in the
rc.local for now and it seems to be working fine. I'm working my way up to
recompiling kernels one day and I may try it the other way. In my reading
on the web I see proponents for both compiled kernel drivers and loaded
kernel modules. Are there any significant advantages or disadvantages to
one over the other?
Also, I apologize, I didn't even notice that my previous reply didn't go to
the list.
Thanks again very much!
Troy
On 8/1/07, Rene Herman [EMAIL PROTECTED] wrote:
On 08/01/2007 02:57 AM, Troy Heidner wrote:
Thanks for the help!
Sure, but please always keep existing CCs intact on these kinds of
messages.
Otherwise the next poor sod that googles for the same problem hits on
these
first few messages of a conversation, but not the solution since that was
in
private mail. Just always use reply to all when dealing with Linux
lists.
Here's what I get when I cat those files:
[ ... ]
ESS0009
ESS1879
There's an ESS1879 in there, but I'm not sure what that tells me?
It tells you (and me...) that indeed the problem is just that the driver
does not know it should be driving your chip. The solution is to tell it
this, and the attached trivial patch to the driver would do this.
The ESS0009 is the chip's CTRL port but I assume from the single ESS1869
already present there that it's okay without.
If you are upto applying the attached patch and rebuilding the kernel
please
do so, but assuming you are not, you can work-around the driver not
knowing
about your chip by specifying all resources manually.
Please do a:
cat /sys/bus/pnp/devices/foo/resources
where foo is the directory in which the id file says ESS179. It
might
just say
state = disabled
If it does, do (as root):
echo activate /sys/bus/pnp/devices/foo/resources
after which the next
cat /sys/bus/pnp/devices/foo/resources
should tell you something fairly close to:
state = active
io 0x220-0x22f
io 0x388-0x38b
io 0x330-0x331
irq 5
dma 1
dma 0
At this point, you can try loading the driver, specifying these resources:
modprobe snd-es18xx isapnp=0 port=0x220 fm_port=0x388\
mpu_port=0x330 irq=5 dma1=1 dma2=0
If all is well, you now have sound (remember to unmute and up the volumes
with a mixer such as alsamixer!).
If this method works for you, you'll have to figure out how to integrate
it
into your bootscripts yourself as this is different with every
distribution.
Simply doing the enabling/loading from an rc.local could be easiest...
If you can confirm that it works after this manual enabling (or after just
applying and testing the patch ofcourse), I'll make sure it ends up
upstream
so that future drivers will work out of the box.
Rene.
diff --git a/sound/isa/es18xx.c b/sound/isa/es18xx.c
index f7732bf..69b1c8a 100644
--- a/sound/isa/es18xx.c
+++ b/sound/isa/es18xx.c
@@ -2042,6 +2042,7 @@ static int pnpc_registered;
static struct pnp_device_id snd_audiodrive_pnpbiosids[] = {
{ .id = ESS1869 },
+ { .id = ESS1879 },
{ .id = }/* end */
};
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
On 08/01/2007 08:52 PM, Troy Heidner wrote: Holy crap, I've got sound! :) Good to hear. I'll submit the little patch for inclusion and (hopefully, it didn't really get tested, but oh well) future drivers should work a little better directly (that is, without you needing to specify the port/irq/dma values manually). You were right, that modprobe line did it. The state= line in the resources file was already set to active. A couple of the resources were different than you listed, but when I plugged the appropriate values into the modprobe line, everything worked! The primary i/o port was 0x240 and the second dma channel was 3, but that was it! I put the line in the rc.local for now and it seems to be working fine. Yup -- assuming there are no funny messages in dmesg after loading the driver, all should be well. I'm working my way up to recompiling kernels one day and I may try it the other way. In my reading on the web I see proponents for both compiled kernel drivers and loaded kernel modules. Are there any significant advantages or disadvantages to one over the other? Compiled into the kernel binary versus compiled into a standalone module that is. One advantage of the latter is that it's easier to try different modules and try with different parameters. But don't worry about it; that was not the important bit. Just that the driver, whether compiled into the kernel binary or compiled modular, needs to be recompiled with the patch applied to enable it to find it's resource values itself. But it'll work the way you have it setup now with the current driver fine, so all well... Rene. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] es18xx soundcard troubles
On 07/31/2007 05:44 AM, Troy Heidner wrote: I'm new to the list here, and I'm fairly new to linux as well. I have an older Gateway Solo 5150 laptop computer that I'm trying to run Fedora Core 6 on. It's a PII-400 with 288MB of RAM. I have gotten nearly EVERYTHING working splendidly with the exception of sound. I know that it is possible because I have found two accounts of others successfully using Linux with sound on this exact same model on the web. But there was no details on how to get it done. I have loaded Windows on this machine in the past so I could determine from there that the sound card installed is an ESS 1879. FC6 won't recognize it out of the box. I have found that ALSA is supposed to support drivers for it, but I don't know how to get them loaded. The trouble is probably as simple as the snd-es18xx driver (which is the one to try) not knowing it should be driving your sound chip. Nothing good happens if you do modprobe snd-es18xx (as root)? I expect your chip will announce itself via PNPBIOS. If you do a: $ cat /sys/bus/pnp/devices/00:*/id is there perhaps a ES1979 in the list? (current driver would work if it were ES1969). Rene. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
