Re: ESS 1868 driver, again
Peter Wemm wrote: As to why the 1869 isn't working for you, that's anybody's guess. You might try posting the 'dmesg' output (not from syslog) and your complete config file, as well as any other pertinant information you can think of. Ok here is the (hopefully) complete information. -current cvsupped ~2 hours ago. If seems there will no interrupts be generated. If I try to play something, nothing happens, if I run "vmstat -i" then, there are 0 interrupts for irq 5 (pcm0). Daniel kernel config file: machine i386 ident LAPTOP maxusers6 options PQ_LARGECACHE cpu I686_CPU options COMPAT_43 options SYSVSHM options SYSVSEM options SYSVMSG options MD5 options DDB options KTRACE options PERFMON options UCONSOLE options INET pseudo-device ether pseudo-device loop pseudo-device bpf pseudo-device tun options ICMP_BANDLIM options FFS options NFS options NFS_NOSERVER options CD9660 options MSDOSFS options PROCFS options FFS_ROOT options SOFTUPDATES options QUOTA options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L controller scbus0 device da0 device pass0 pseudo-device pty options MSGBUF_SIZE=20480 controller isa0 controller pnp0 options PNPBIOS controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP="german.iso" device psm0at atkbdc? irq 12 options PSM_HOOKAPM options PSM_RESETAFTERSUSPEND device vga0at isa? port ? conflicts options VGA_WIDTH90 options VESA pseudo-device splash device sc0 at isa? options MAXCONS=6 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso options SC_PIXEL_MODE device npx0at nexus? port IO_NPX flags 0x0 irq 13 controller ata0 device atadisk0 device atapicd0 options ATA_ENABLE_ATAPI_DMA controller fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device ed0 device pcm0 device apm0at nexus? device joy0at isa? port IO_GAME controller pci0 controller pcic0 at isa? irq 10 controller pcic1 at isa? irq 10 controller card0 options PCIC_RESUME_RESET controller ppbus0 controller vpo0at ppbus? device lpt0at ppbus? device ppi0at ppbus? device ppc0at isa? port? irq 7 drq 3 controller uhci0 controller usb0 device ugen0 options HZ=500 dmesg output of verbose boot: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #241: Sun Nov 7 13:48:17 CET 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ROCK Calibrating clock(s) ... TSC clock: 232125177 Hz, i8254 clock: 1193284 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Xeon/Celeron (232.11-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x002ef000 - 0x03ffafff, 64012288 bytes (15628 pages) avail memory = 62169088 (60712K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f66a0 bios32: Entry = 0xfd7e0 (c00fd7e0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x203 pnpbios: Found PnP BIOS data at 0xc00f66d0 pnpbios: Entry = f:a62f Rev = 1.0 Other BIOS signatures found: ACPI: VESA: information block 56 45 53 41 00 02 6b 00 00 c0 00 00 00 00 f6 8c 00 c0 10 00 00 00 b4 27 00 c0 b5 27 00 c0 b6 27 00 c0 b7 27 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 11 mode(s) found VESA: v2.0, 1024k memory, flags:0x0, mode table:0xc00c8cf6 (c0008cf6) VESA: Copyright 1994 TRIDENT MICROSYSTEMS INC. VESA: Pentium Pro MTRR support enabled pci_open(1):mode 1 addr port (0x0cf8) is 0x80001010 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71928086) npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2
Re: ESS 1868 driver, again
Peter Wemm wrote: "D. Rock" wrote: I read the last mails regarding problems with their ESS 1868 boards. Well, at least it is partially working for them. I didn't have any luck with the driver for some time now. I couldn't get a single tone. With the old voxware driver, sound worked at least partially (44.1 kHz, 8 Bit, mono), but with the new driver I didn't have any luck at all. Here my configuration: device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15 Err, the ESS1868 is a PNP device. You should only have "device pcm0" and nothing more. You might also try "options PNPBIOS". You are running -current, right? What does "options PNPBIOS" do. I didn't find it in LINT? This one doesn't seem to be a PNP device. I set all the resources manually via BIOS. If it was a PNP device, it shouldn't be detected any longer by the old voxware driver. # pnpinfo Checking for Plug-n-Play devices... No Plug-n-Play devices were found Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868 driver, again
"D. Rock" wrote: Here my configuration: device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15 Err, the ESS1868 is a PNP device. You should only have "device pcm0" and nothing more. You might also try "options PNPBIOS". You are running -current, right? What does "options PNPBIOS" do. I didn't find it in LINT? This one doesn't seem to be a PNP device. I set all the resources manually via BIOS. If it was a PNP device, it shouldn't be detected any longer by the old voxware driver. # pnpinfo Checking for Plug-n-Play devices... No Plug-n-Play devices were found Uups, forget my previous post. I added "options PNPBIOS" to my configuration and also only a line "device pcm0", but the problem remains: Probe message: Nov 7 03:34:45 /kernel.new: pcm0: ESS1869 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,5 on isa0 And then later, if I try to play something: Nov 7 03:34:45 /kernel.new: sb_dspwr(0xd0) timed out. Nov 7 03:34:45 /kernel.new: sb_dspwr(0xc0) timed out. Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868 driver, again
"D. Rock" wrote: "D. Rock" wrote: Here my configuration: device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15 Err, the ESS1868 is a PNP device. You should only have "device pcm0" and nothing more. You might also try "options PNPBIOS". You are running -current, right? What does "options PNPBIOS" do. I didn't find it in LINT? This one doesn't seem to be a PNP device. I set all the resources manually via BIOS. If it was a PNP device, it shouldn't be detected any longer by the old voxw are driver. # pnpinfo Checking for Plug-n-Play devices... No Plug-n-Play devices were found Uups, forget my previous post. I added "options PNPBIOS" to my configuration and also only a line "device pc m0", but the problem remains: Probe message: Nov 7 03:34:45 /kernel.new: pcm0: ESS1869 at port 0x220-0x22f,0x388-0x38b ,0x330-0x331 irq 5 drq 1,5 on isa0 And then later, if I try to play something: Nov 7 03:34:45 /kernel.new: sb_dspwr(0xd0) timed out. Nov 7 03:34:45 /kernel.new: sb_dspwr(0xc0) timed out. Daniel PNPBIOS turns on the interface between the computer and the motherboard bios so that it can obtain all the PNP information for all the motherboard devices. This means we can do PNP-style configuration for motherboard resources (eg: serial, parallel, floppy drive, keyboard, etc etc) As to why the 1869 isn't working for you, that's anybody's guess. You might try posting the 'dmesg' output (not from syslog) and your complete config file, as well as any other pertinant information you can think of. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ESS 1868 driver (again)
I got the one email that said that there was some trouble with the ESS
1868 sound driver under FreeBSD-current. Is there an issue with -current
and newpcm that is causing the 1868 sound driver to not work? Also, I'd
like to know how to compile the newpcm sound driver as a loadable kernel
module, so that I can just load and unload it with kld{load,unload}.
I tried the patch Sanpei gave me, but no dice (ESS 1868). When I try
playing certain RealPlayer clips, for example, a 2 minute clip will finish
in about 10 seconds with short bursts of sound along the way. Actually,
it does play the entire clip through, but the entire clip goes wizzing by
at an extremely high rate of speed with only short bursts of sound along
the way. Video+audio clips will show a "fast-forwarding" effect with no
or short bursts of sound.
- Donn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868 driver (again)
I got the one email that said that there was some trouble with the ESS
1868 sound driver under FreeBSD-current. Is there an issue with -current
and newpcm that is causing the 1868 sound driver to not work? Also, I'd
guys, you should realize that the ESS1868 codecs (and friends)
are extremely unfriendly to the programmer, and possibly
(according to Sanpei comments) broken in their handling of
auto-dma. As a consequence i cannot believe anyone wants to
write a driver for this chip fighting against all idiosincracies
of the hardware and its ugly design.
If you have a machine with that card, just replace it with a better
supported one. If you have a laptop with that card, well, you have
bad luck, but chances are that your laptop is already obsolete and
in 1yrs you will have to replace it because the battery has died, the
keyboard has broken keys, and the hard disk starts failing on some sectors.
Just be patient...
cheers
luigi
module, so that I can just load and unload it with kld{load,unload}.
I tried the patch Sanpei gave me, but no dice (ESS 1868). When I try
playing certain RealPlayer clips, for example, a 2 minute clip will finish
in about 10 seconds with short bursts of sound along the way. Actually,
it does play the entire clip through, but the entire clip goes wizzing by
at an extremely high rate of speed with only short bursts of sound along
the way. Video+audio clips will show a "fast-forwarding" effect with no
or short bursts of sound.
- Donn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ESS 1868 driver, again
I read the last mails regarding problems with their ESS 1868 boards. Well, at least it is partially working for them. I didn't have any luck with the driver for some time now. I couldn't get a single tone. With the old voxware driver, sound worked at least partially (44.1 kHz, 8 Bit, mono), but with the new driver I didn't have any luck at all. Here my configuration: device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15 and during boot: pcm0: ESS1868 rev 11 at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 If I try to play something, I only get the following error from the driver: sb_dspwr(0xc0) timed out. The old voxware driver: controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? port 0x220 irq 5 drq 5 conflicts device sbmidi0 at isa? port 0x330 device opl0at isa? port 0x388 device mpu0at isa? port 0x330 sb0 at port 0x220 irq 5 drq 1 on isa0 Hmm... Could this be an ESS688 based card (rev 11) snd0: SoundBlaster Pro 3.1 isa_compat: didn't get ports for sbxvi sbxvi0 at port 0x220 irq 5 drq 5 on isa0 isa_compat: didn't get ports for sbxvi snd0: SoundBlaster 16 3.1 WARNING: "snd" is usurping "snd"'s cdevsw[] opl0 at port 0x388 on isa0 snd0: Yamaha OPL3 FM WARNING: "snd" is usurping "snd"'s cdevsw[] Any hints are welcome. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868 driver (again)
On Thu, 4 Nov 1999, Luigi Rizzo wrote: guys, you should realize that the ESS1868 codecs (and friends) are extremely unfriendly to the programmer, and possibly (according to Sanpei comments) broken in their handling of auto-dma. As a consequence i cannot believe anyone wants to write a driver for this chip fighting against all idiosincracies of the hardware and its ugly design. If you have a machine with that card, just replace it with a better supported one. If you have a laptop with that card, well, you have Which members of the SoundBlaster family are supported? Is the SoundBlaster 16 WavEffects supported? I'd like to get one of the wavetable synth models. Thanks. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868 driver (again)
All, I'm having trouble with my old Yamaha OPL based ISA soundcard. It used to work flawlessly, but now as Don, I get `bursty' sound. Most pronounced effect is when using `rvplayer'. If I open rvplayer and click to play a sound clip everything is just peachy until I move the mouse, causing a window to autoraise or some such (basically generating X activity) at which point the clip starts `bursting'. For fun I tried running rvplayer with `rtprio'. Folks don't try this at home :) . The clip plays flawlessly _but_ my machine is completely locked up for the duration. Further, when playing short clips through `nas', I typically only get to hear one burst of the clip. The effect is kind of like what one hears when cruising for tunes using an old AM `dial' radio. Interestingly enough, mpg123 and xanim seem unaffected. Here's how my card is currently detected - pcm0: Yamaha SA2 at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 Yamaha: ver 0x21 DMA config 0x84 pcm: setmap 3, ff00; 0xc77e9000 - 3 pcm: setmap 4, ff00; 0xc77f9000 - 4 unknown0: OPL3-SAX Sound Board at port 0x201 on isa0 If I'm not mistaken the old pcm preferred MSS emulation for this card. Is it possible that the new pcm tries to use SB emulation ? I ask because I know my SB emulation settings for this card are _wrong_. With old pcm, this didn't appear to matter, but with new pcm, h. Something to try out I guess when I get home tonight :) .. Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868 driver (again)
Luigi Rizzo [EMAIL PROTECTED] writes: guys, you should realize that the ESS1868 codecs (and friends) are extremely unfriendly to the programmer, and possibly (according to Sanpei comments) broken in their handling of auto-dma. ?? I wouldn't say the interface is *pretty*, but the only problem we had with these chips under NetBSD was figuring out how to differentiate the various models. They work reasonably well, and we do use auto-initialize DMA. (Several people are even using them in stereo systems, as the ES1887 is what's in the Shark.) ok, the comment about auto-dma was just related to what i heard from other people who tried to add ESS support to the pcm driver. I should also mention that one of the goals of "pcm" was support of full duplex audio. I just gave up on the ESS after seeing how complex it would have been (in terms of changes to the pcm driver) to make it work in full duplex as well as in other modes. cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
