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@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
