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 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
