Understanding newPCM driver
Hi I wish to teach FreeBSD (5.0-CURRENT, somewhere in mid-may, last cvsup was week ago) make use of that fancy S/P-DIF connector on my Yamaha soundcard. OTOH, I want to implement it in a Right Way (tm), so that one can choose, whether he wish to use or not to use this feature, if it's present. Which is the Right Way(tm) to add such functionality to existing newPCM driver? PS: I'm crossposting both -hackers and -current... -- Artem 'Zazoobr' Ignatjev [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
newpcm audio recording
Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? -- Patrik Sundberg - email: [EMAIL PROTECTED] || [EMAIL PROTECTED] --- telefon: 013-178 567 - mobiltelefon: 070-760 22 40 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm audio recording
Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? I believe this may be related to the soundcard driver, which soundcard are you using? I am using an SB Live 1024 in my computer, and I am reading from the audio input, 16 bits at 44.1KHz, although only in mono, doing fourier transform on the data, and displaying the results graphically, without any problems. --- Erik H. Bakke Don't ask "Who invented time?", the real question is "When was time invented?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm audio recording
On Tue, Jan 09, 2001 at 02:29:59PM +0100, Erik H. Bakke wrote: Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? I believe this may be related to the soundcard driver, which soundcard are you using? I am using an SB Live 1024 in my computer, and I am reading from the audio input, 16 bits at 44.1KHz, although only in mono, doing fourier transform on the data, and displaying the results graphically, without any problems. I have a SB32 isa-card. -- Patrik Sundberg - email: [EMAIL PROTECTED] || [EMAIL PROTECTED] --- telefon: 013-178 567 - mobiltelefon: 070-760 22 40 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm audio recording
I have a SB32 isa-card. what revision of sys/dev/sound/isa/sb16.c ? -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm/kobj
in the near future, i intend to commit my kobjified newpcm. this gives us several benefits, including: * easier extensibility- new optional methods can be added to ac97/mixer/channel classes without having to fixup every driver. * forward compatibility for drivers, provided no new mandatory methods are added. however, all drivers not in the tree at this time will need to be updated. i hope to mfc to -stable in approximately one month, along with the kobj system. newbus in -stable will not be kobjified. the diff for newpcm/kobj is at http://people.freebsd.org/~cg/kobj.diff.gz -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm/kobj
in the near future, i intend to commit my kobjified newpcm. this gives us several benefits, including: * easier extensibility- new optional methods can be added to ac97/mixer/channel classes without having to fixup every driver. * forward compatibility for drivers, provided no new mandatory methods are added. however, all drivers not in the tree at this time will need to be updated. i hope to mfc to -stable in approximately one month, along with the kobj system. newbus in -stable will not be kobjified. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Neomagic] newpcm problems under current
According to Cameron Grant: is the irq shared? have your printf display the neomagic status - i'll bet it's 0 indicating the irq was not generated by the neomagic. Ahem, yes it is shared, by almost everything on the machine. Should have thought of that... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Neomagic] newpcm problems under current
Hmmm. I'm seeing something like this. I have an Gravis UltraSound MAX and mpg123 will play a list of songs correctly, but if I ^C out of it and try again, I see the "pcm0: play interrupt timeout, channel dead" message and it don't want to play again until a reboot. The gusc0 device is the only one using irq 5 and I have used this setup for quite a while. gusc0: Gravis UltraSound MAX at port 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 pcm0: GUS CS4231 on gusc0 John -- John Hay -- [EMAIL PROTECTED] "me too" pcm0: NeoMagic 256AV mem 0xfda0-0xfdaf,0xfac0-0xfaff irq 5 at device 0.1 on pci1 pcm0: play interrupt timeout, channel dead Then EBUSY until the cows come home. I chatted with Cam some this evening; this problem seems to have come about as a result of driver restructuring. This chipset used to "just work" on my Dell notebook under some earlier 4.0 revision. On Sun, 6 Aug 2000, Ollivier Robert wrote: FreeBSD sidhe.freenix.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Aug 3 19:19:36 CEST 2000 roberto@sidhe:/src/src/sys/compile/nSIDHE i386 FreeBSD Audio Driver (newpcm) Aug 3 2000 17:03:04 Installed devices: pcm0: NeoMagic 256AV at memory 0xfe00, 0xfea0 irq 9 (1p/1r channels duplex) The first time I run mpg123, it does nothing (that is, no sound is emitted) and afterwards, /dev/dsp can't be opened at all... Robert N M Watson [EMAIL PROTECTED] http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[Neomagic] newpcm problems under current
FreeBSD sidhe.freenix.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Aug 3 19:19:36 CEST 2000 roberto@sidhe:/src/src/sys/compile/nSIDHE i386 FreeBSD Audio Driver (newpcm) Aug 3 2000 17:03:04 Installed devices: pcm0: NeoMagic 256AV at memory 0xfe00, 0xfea0 irq 9 (1p/1r channels duplex) The first time I run mpg123, it does nothing (that is, no sound is emitted) and afterwards, /dev/dsp can't be opened at all... 404 [20:24] roberto@sidhe:~ mpg123 Lily_Was_Here.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. Version 0.59r (1999/Jun/15). Written and copyrights by Michael Hipp. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Can't open /dev/dsp! $FreeBSD: src/sys/dev/sound/pci/neomagic.c,v 1.13 2000/07/03 20:52:27 cg Exp $ $FreeBSD: src/sys/dev/sound/pci/neomagic.h,v 1.1 2000/01/09 08:14:11 cg Exp $ Any idea ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Neomagic] newpcm problems under current
The first time I run mpg123, it does nothing (that is, no sound is emitted) and afterwards, /dev/dsp can't be opened at all... Any idea ? this is a known problem. it seems the neomagic driver never worked right, so when newpcm became dependant on interrupts it ceased functioning. now we trap the lack of irqs and disable the channel and emit a warning to the console. access to hardware would make this easier to fix. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Neomagic] newpcm problems under current
According to Cameron Grant: this is a known problem. it seems the neomagic driver never worked right, Well, it used to work :) so when newpcm became dependant on interrupts it ceased functioning. now we trap the lack of irqs and disable the channel and emit a warning to the console. I do get lots of interrupt. I patched my kernel in June to generate a printf for each interrupt and I was seeing lots of them without even running mpg123. Aug 3 19:17:28 sidhe /kernel: getting an intr Aug 3 19:17:59 sidhe last message repeated 33 times Aug 3 19:18:57 sidhe last message repeated 73 times Aug 3 19:18:58 sidhe /kernel: getting an intr Aug 3 19:19:29 sidhe last message repeated 53 times Aug 3 19:20:37 sidhe last message repeated 93 times access to hardware would make this easier to fix. I would be difficult to send you my laptop, I do use it :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Neomagic] newpcm problems under current
According to Cameron Grant: this is a known problem. it seems the neomagic driver never worked right, Well, it used to work :) it used to *appear* to work. so when newpcm became dependant on interrupts it ceased functioning. now we trap the lack of irqs and disable the channel and emit a warning to the console. I do get lots of interrupt. I patched my kernel in June to generate a printf for each interrupt and I was seeing lots of them without even running mpg123. is the irq shared? have your printf display the neomagic status - i'll bet it's 0 indicating the irq was not generated by the neomagic. access to hardware would make this easier to fix. I would be difficult to send you my laptop, I do use it :-) :) -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm broken in -current for SB16
Subject says it all. Everytime I am trying to use my SB16PNP card to play any sound file (WAV, MP3), all I am getting is garbled sound because driver plays sound at increased rate (i.e. it takes less than 10 sec for mpg123 to decode 5 min long song). FreeBSD Audio Driver (newpcm) Apr 19 2000 09:43:52 Installed devices: pcm0: SB DSP 4.13 at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) -- E-Mail: Alexander N. Kabaev [EMAIL PROTECTED] Date: 19-Apr-00 Time: 12:16:37 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: newpcm broken in -current for SB16
Correction to my own message. The problem is not with newpcm driver per se but with esd/newpcm combination. mpg123 recompiled without OPT_ESOUND works just fine, so does xmms when using OSS output plugin. Only when I force these two to use ESD for output, then I am getting "fast forward"-like cacophony I was describing in my previous message. Subject says it all. Everytime I am trying to use my SB16PNP card to play any sound file (WAV, MP3), all I am getting is garbled sound because driver plays sound at increased rate (i.e. it takes less than 10 sec for mpg123 to decode 5 min long song). FreeBSD Audio Driver (newpcm) Apr 19 2000 09:43:52 Installed devices: pcm0: SB DSP 4.13 at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) -- E-Mail: Alexander N. Kabaev [EMAIL PROTECTED] Date: 19-Apr-00 Time: 12:43:51 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
no audio with newpcm driver on TP600E
Hi, I'm having problems with the newpcm driver. Basically, I can't get audio from the speakers. This while trying to play a cd. The output of mixer looks reasonable. Hardware is a ThinkPad 600E. "audio" portions of the config attached along with the output of dmesg. Help would be greatly appreciated. Thanks, Kent === # For PnP/PCI sound cards #device pcm #device sbc #device csa # For non-PnP cards: device pcm0 at isa? irq 10 drq 1 flags 0x0 device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x15 device csa device gusc0 at isa? port 0x220 irq 5 drq 1 flags 0x13 # Not controlled by `snd' device pca0 at isa? port IO_TIMER1 device matcd0 at isa? port 0x230 = Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-2331-SNAP #5: Sat Apr 1 20:32:28 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/TP Calibrating clock(s) ... TSC clock: 29462 Hz, i8254 clock: 1193150 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/Pentium II Xeon/Celeron (297.79-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 = 66912256 (65344K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x003ce000 - 0x03fc7fff, 62889984 bytes (15354 pages) avail memory = 61317120 (59880K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fd800 bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x0 pnpbios: Found PnP BIOS data at 0xc00fe700 pnpbios: Entry = f:e724 Rev = 1.0 pnpbios: Event flag at 415 Other BIOS signatures found: ACPI: 000fd6e0 Preloaded elf kernel "kernel" at 0xc03b5000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1):mode 1 addr port (0x0cf8) is 0x38c8 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard found- vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base 4000, size 26, enabled found- vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1secondarybus=1 found- vendor=0x104c, dev=0xac1d, revid=0x00 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=4secondarybus=2 intpin=a, irq=11 map[10]: type 1, range 32, base 50102000, size 12, enabled found- vendor=0x104c, dev=0xac1d, revid=0x00 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=7secondarybus=5 intpin=b, irq=11 map[10]: type 1, range 32, base 50101000, size 12, enabled found- vendor=0x1013, dev=0x6001, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 5010, size 12, enabled map[14]: type 1, range 32, base 5000, size 20, enabled found- vendor=0x8086, dev=0x7110, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 1, range 32, base fcf0, size 4, enabled found- vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=11 map[20]: type 1, range 32, base 8400, size 5, enabled found- vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[90]: type 1, range 32, base efa0, size 4, enabled pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 found- vendor=0x10c8, dev=0x0005, revid=0x12 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base d000, size 24, enabled map[14]: type 1, range 32, base 7
Re: no audio with newpcm driver on TP600E
Kent Hauser wrote: I'm having problems with the newpcm driver. Basically, I can't get audio from the speakers. This while trying to play a cd. The output of mixer looks reasonable. How recently has your kernel been built? I've been running -current for a long time, and my ESS 1868 ALWAYS worked until I built a kernel on Mar 30. It looks like the pcm driver was overhauled as of Mar 29 or 30. Basically, my sound still works, but sound apps are acting real flaky. The sound is really flaky, and the sound chokes bad under any CPU load. I had to revert back to a kernel I built around midnight Mar 28 before the changes to pcm were committed. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no audio with newpcm driver on TP600E
# For PnP/PCI sound cards #device pcm #device sbc #device csa # For non-PnP cards: device pcm0 at isa? irq 10 drq 1 flags 0x0 device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 device csa device gusc0 at isa? port 0x220 irq 5 drq 1 flags 0x13 this is wrong. try: options PNPBIOS device pcm - cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?)
This is an old debate. However, if the user is not smart enough to know that a "not" release is new and should be tested, well, that speaks volumes itself doesn't it? Tom Veldhouse [EMAIL PROTECTED] - Original Message - From: David Murphy [EMAIL PROTECTED] To: Brad Knowles [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, March 21, 2000 10:37 AM Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Quoting v04220821b4fd4f825554@[195.238.1.121] by Brad Knowles [EMAIL PROTECTED]: We just got our official shrink-wrapped versions of Solaris 8 from Sun. Do you think we're actually going to be stupid enough to try to put this into production any time within the next few months? It's an x.0 release from Sun, and we're going to treat it just like we do with x.0 releases from *any* vendor. We may play with it on our desktops, we may do some prototyping with it, etc Right, and if you try to upgrade your Solaris 7 desktop, which, while not a production server, is a machine you personally need to do your job, to Solaris 8, and it fails, and you call Sun about it, and they tell you "Hey, what do you think you're doing? That's not ready for real use yet!". You wouldn't be too impressed, would you? That's basically the scenario I'm seeing with FreeBSD. Thing is, it's *not* a beta anymore. It's more like a gamma version. Call it -GAMMA then. Bascially, I'm saying I think it should be called something other than -RELEASE until the average user can install it, and upgrade to it from the prior version. The *only* way to proceed from here is to actually release the thing, let people start trying to use it, and then report bugs back. But we wouldn't be acting in good faith if we didn't at least warn people that it's not quite ready for use on production servers. IMHO the place for that warning is the release announcement and the release notes, and it wasn't in either last I looked. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kern/16487: please apply newpcm fix
Seigo Tanimura [EMAIL PROTECTED] wrote in list.freebsd-current: On Mon, 6 Mar 2000 01:22:41 +0100 (CET), Oliver Fromme [EMAIL PROTECTED] said: Oliver Would someone please (pretty please) have a look at kern/16487 Oliver and commit the trivial fix in it? It's just one line, and it Oliver makes AvanceLogic-100 soundcards work again. The logical ID of ALS100 conflicts with the one of CMI8330(mss), so we also have to check the vendor ID. Could you please give it to me? It is likely to be 0x00019305. (ALS110 is 0x10019305 and ALS120 is 0x20019305, so...) pnpinfo says: Vendor ID ALS0001 (0x01009305), Serial Number 0x0100 Logical Device ID: @@@0001 0x0100 #0 But I think there is already a check for the vendor ID of the card, look at the beginning of sbc_probe() in sbc.c. So I think it's really sufficient to add that line to the array of logical IDs. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can't record with newpcm CS423x
With my Acer AW35/Pro (CS4236) and -current I can play sound just fine, but I can't record. (Recording and full duplex worked fine with 3.4-stable.) When I run rec -c 1 -f s -r 44100 -s w test.wav rec just sits, blocked in pcmrd, and rec can't be interrupted with ctl-c. The output file test.wav never increases in size, always remaining 0 bytes long. My kernel config file has "device pcm". Any ideas? Matt - cat /dev/sndstat FreeBSD Audio Driver (newpcm) Feb 4 2000 14:51:04 Installed devices: pcm0: CS423x at io 0x534 irq 5 drq 1:0 (1p/1r channels duplex) - FreeBSD 4.0-CURRENT #0: Fri Feb 4 14:52:00 PST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/BILBO Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA T,PSE36,MMX,FXSR,XMM real memory = 134205440 (131060K bytes) avail memory = 126857216 (123884K bytes) Preloaded elf kernel "kernel" at 0xc0316000. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: NVidia Riva TNT2 graphics accelerator mem 0xe200-0xe3ff,0xe0 00-0xe0ff irq 11 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 ATA-33 controller port 0xd800-0xd80f at device 4.1 on pc i0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 4.2 irq 10 chip1: Intel 82371AB Power management controller port 0xe800-0xe80f at device 4.3 on pci0 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xd000-0xd07f mem 0xdf80-0xdf80 007f irq 10 at device 9.0 on pci0 xl0: Ethernet address: 00:10:5a:ab:87:55 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppi0: Parallel I/O on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port pcm0: CS423x at port 0x534-0x537,0x388-0x38f,0x220-0x22f irq 5 drq 1,0 on isa0 joy0: CSC0001 PnP Joystick at port 0x200-0x207 on isa0 unknown0: CTRL at port 0x120-0x127 on isa0 unknown1: MPU at port 0x330-0x331 irq 9 on isa0 IPsec: Initialized Security Association Processing. ad0: 8223MB ST38422A [16708/16/63] at ata0-master using UDMA33 acd0: CDROM ATAPI 44X CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a - pnpinfo: Card assigned CSN #1 Vendor ID CSCd937 (0x37d9630e), Serial Number 0x PnP Version 1.0, Vendor Version 1 Device Description: AW35/Pro (Resource R2.2-D7) Logical Device ID: CSC 0x630e #0 Device Description: WSS/SB TAG Start DF Good Configuration DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Type A DMA: channel(s) 0 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 - only one type (true/edge) I/O Range 0x534 .. 0x534, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x8 [16-bit addr] I/O Range 0x220 .. 0x220, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Acceptable Configuration DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Type A DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 7 9 11 12 15 - only one type (true/edge) I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x8 [16-bit addr] I/O Range 0x220 .. 0x260, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 7 9 11 12 15 - only one type (true/edge) I/O Range 0x534 .. 0xffc
Re: newpcm (or newpnp?)
Cameron Grant wrote: would everyone who currently has an issue outstanding with newpcm please report it to me in the next few days directly, please, so i can get an idea of what needs work before release. i need as much detail as possible. Well, since you asked... Since rebuilding -CURRENT with newpcm and newpnp about a month ago, my soundcard, a Soundblaster AWE64, ISA PnP, will only play the first second or less of a sound file. Audio apps often claim "unable to open /dev/dsp". I notice that my modem, a Diamond SupraExpress 56i Sp, is now attaching to irq 5, and the soundcard attaches to irq 9. Previous to newpnp, I forced the modem (sio2) to irq 15 and the soundcard to irq 5 via pnp commands in my /boot/kernel.conf. I did this because I had found by experimentation that this was the only combination of the supposedly available PnP configurations which enabled both devices to work. Now that pnp attaches sio2 to irq 5, the soundcard refuses to work on irq9, even though irq9 is available and supposedly valid for that card. So I'd like to be able to get it to work on irq9 (preferably), but failing that, at least try to return to my original PnP configuration to see if that works. I don't know how to force this since the removal of pnp(4), though, and have searched the mailing list archives to no avail. I have tried configuring a kernel to force irq 5 on the soundcard with no success. Any advice would be greatly appreciated. My kernel config and other info is attached. Chris Giordano [EMAIL PROTECTED] $ /opt/home/cgiordan uname -a FreeBSD boston 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Jan 17 02:15:15 EST 2000 root@boston:/opt/src/src/sys/compile/BOSTON i386 $ /opt/home/cgiordan cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 17 2000 02:13:33 Installed devices: pcm0: SB DSP 4.16 at io 0x220 irq 9 drq 0:5 (1p/1r channels duplex) # # BOSTON -- Generic machine with WD/AHx/NCR/BTx family disks #-- added PnP and sound support #-- added ATAPI LS-120/Zip support #-- switched over to Luigi's new sound driver #-- added SCSI/CAM devices for 3.X # # For more information read the handbook part System Administration - # Configuring the FreeBSD Kernel - The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # URL:http://www.FreeBSD.ORG/ # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.107 1998/02/16 23:57:03 msmith Exp $ machine i386 cpu I686_CPU ident BOSTON maxusers64 ## config kernel root on da0 dumps on da0 ## options HZ=100 #use 10 ms clock tick options INET#InterNETworking # # Implement system calls compatible with 4.3BSD and older versions of # FreeBSD. You probably do NOT want to remove this as much current code # still relies on the 4.3 emulation. # options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT#allow user level control of i386 LDT options MD5 options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor #optionsMROUTING# Multicast routing #optionsIPFIREWALL #firewall #optionsIPFIREWALL_VERBOSE #print information about # dropped packets #optionsIPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity #optionsIPDIVERT#divert sockets options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options NTFS#NT File System options PROCFS #Process filesystem options CD9660 #ISO 9660 Filesystem options EXT2FS options FFS_ROOT#FFS usable as root device [keep this!] options NFS_ROOT#NFS usable as root device options CD9660_ROOT #CD-ROM usable as root device options SOFTUPDATES #in Alpha test! options NSWAPDEV=20 # Don't enable both of these in a real config. #optionsMATH_EMULATE#Support for x87 emulation options GPL_MATH_EMULATE#Support for x87 emulation via #new math emulator options NBUF=512 options NMBCLUSTERS=8192#workaround for mbuf bug # This provides support fo
Re: newpcm (or newpnp?)
Chris Giordano wrote: Previous to newpnp, I forced the modem (sio2) to irq 15 and the soundcard to irq 5 via pnp commands in my /boot/kernel.conf. I did this because I had found by experimentation that this was the only combination of the supposedly available PnP configurations which enabled both devices to work. I can report similar problems with my US Robotics internal 56K Fax/Modem and my SoundBlaster 16 isa card. On Freebsd 3.4 I "hard wire" the cards using kernel.conf file. On -Current I found that the only way I can get the cards to work is to configure my IWILL XA100P motherboard so that irq 3 and 5 are set up for "legacy" cards and are not automagically assigned. (I disable the 2nd serial port as well so that irq 3 is available.) When I do this reconfiguration of the motherboard, the modem and sound card work together with few problems. I can play sound and do a compilation without problems. I do have 192MB of memory add a 450Mhz processor so there is plenty of spare "horsepower" for essentially a "single user" system. I do occasionally get a flutter on startup and can reliably see a cutoff of sound at the end of reading a wave or midi file. But for most things it seems to work fine. The "say" program from the rsynth port provides a good demonstration of the "cutoff" phenomena. George Dinolt ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm: ESS1688, simplex problems, stuttering
I've just upgraded my wheezing P120Mhz Dell Lattitude LM to a recent
-current (Jan24 snap) the sound *almost* works!
The first problem I had was to get the card recognized. I needed to
patch the sbc bridge driver to recognize the ESS 1688:
Index: sys/dev/sound/isa/sbc.c
===
RCS file: /home/ncvs/src/sys/dev/sound/isa/sbc.c,v
retrieving revision 1.16
diff -u -r1.16 sbc.c
--- sbc.c 2000/01/12 11:16:23 1.16
+++ sbc.c 2000/01/25 04:29:06
@@ -205,6 +205,7 @@
{0x0110, "Avance Asound 110"}, /* @@@1001 */
{0x0120, "Avance Logic ALS120"},/* @@@2001 */
+ {0x02017316, "ESS ES1688"}, /* ESS1688 */
{0x68187316, "ESS ES1868"}, /* ESS1868 */
{0x69187316, "ESS ES1869"}, /* ESS1869 */
{0xacb0110e, "ESS ES1869 (Compaq OEM)"},/* CPQb0ac */
The second problem I had was that this laptop gives its sound card
only one DMA channel (drq 1). Newpcm seems to have horrible problems
on simplex cards:
The sound card is now recognized when I run amp I don't hear any
output. If I run ktrace on the amp session, it doesn't look like any
writes are initiated to /dev/dsp from the child process. I don't see
any interrupts on irq5 nor do I hear any sound.
The problem is that in getchns() (in dsp.c), the channel is set to
fakechan if the channel is simplex (eg, 1 DMA channel) and if the
priority hasn't been set. It looks like SD_F_PRIO_WR is only set on
the channel in dsp_write(). But apparently dsp_write() never gets
called (or gets called after getchns()), so this prevents newpcm from
working on a simplex channel. I have the following crude hack in
place:
Index: sys/dev/sound/pcm/dsp.c
===
RCS file: /home/ncvs/src/sys/dev/sound/pcm/dsp.c,v
retrieving revision 1.14
diff -u -r1.14 dsp.c
--- dsp.c 2000/01/10 07:05:15 1.14
+++ dsp.c 2000/01/25 04:27:12
@@ -54,6 +54,8 @@
KASSERT((d-flags SD_F_PRIO_SET) != SD_F_PRIO_SET, \
("getchns: read and write both prioritised"));
+if(!(d-flags (SD_F_PRIO_RD | SD_F_PRIO_WR))) d-flags |= SD_F_PRIO_WR;
+
if (d-flags SD_F_SIMPLEX) {
*rdch = (d-flags SD_F_PRIO_RD)? d-arec[chan] : d-fakechan;
*wrch = (d-flags SD_F_PRIO_WR)? d-aplay[chan] : d-fakechan;
This gets me to the point where I can actually hear my laptop make
noise! Unfortunately, I seem to be having the same symptoms as Nick
Hibma Donn Miller are reporting in the "pcm - stutters" thread.
Since my box is dog-slow, I only hear stuttering from amp. It is a
little better with RealPlayerG2, but not great.
Thanks for any help!
Drew
--
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
newpcm problem -- patch -- problem
Hi,
I upgraded from an early December -current to a current -current
(CVSupped yesterday, buildworld took 16 hours). Works fine,
except that the soundcard (ISA PnP, Avance Logic ALS100+, SB16-
compatible) does not work anymore. It worked fine before.
(``Does not work anymore'' == it just blocks when I try to play
something, and half of the mixer settings aren't recognized
anymore. I can't get a single beep from the boxes. Yes, I do
have ``device sbc0'' in my kernel.)
Early December dmesg says:
pcm0: Avance Asound 100 at port 0x220-0x22f irq 5 drq 5,1 on isa0
And current dmesg says:
pcm0: CMI8330 at port 0x220-0x22f irq 5 drq 5,1 on isa
Obviously, the card is probed as something completely different,
which is wrong. No wonder that it doesn't work.
The following patch fixes it, and the soundcard works just like
before, but...
--- src/sys/dev/sound/isa/mss.c.origThu Jan 13 07:11:32 2000
+++ src/sys/dev/sound/isa/mss.c Mon Jan 24 00:38:08 2000
@@ -1328,7 +1328,9 @@
static struct isa_pnp_id pnpmss_ids[] = {
{0x630e, "CS423x"}, /* CSC */
{0x0001630e, "CS423x-PCI"}, /* CSC0100 */
- {0x0100, "CMI8330"},/* @@@0001 */
+#if 0
+ {0x0100, "CMI8330"},/* @@@0001 */
+#endif
{0x2100a865, "Yamaha OPL-SAx"}, /* YMH0021 */
{0x1110d315, "ENSONIQ SoundscapeVIVO"}, /* ENS1011 */
{0x1093143e, "OPTi931"},/* OPT9310 */
--- src/sys/dev/sound/isa/sbc.c.origWed Jan 12 12:16:23 2000
+++ src/sys/dev/sound/isa/sbc.c Mon Jan 24 00:44:28 2000
@@ -202,6 +202,7 @@
{0x44008c0e, "Creative SB AWE64 Gold"}, /* CTL0044 */
{0x45008c0e, "Creative SB AWE64"}, /* CTL0045 */
+ {0x0100, "Avance Logic ALS100+"}, /* @@@0001 */
{0x0110, "Avance Asound 110"}, /* @@@1001 */
{0x0120, "Avance Logic ALS120"},/* @@@2001 */
... of course, now a real ``CMI8330'' would probably not be
detected correctly anymore. I don't have such a card (and I've
never heard of it before). If it really has the same device ID
as the ALS100+, we're in trouble, I guess.
BTW, with the above patch, my card is probed like this:
sbc0: Avance ALS100+ at port 0x220-0x22f irq 5 drq 5,1 on isa0
sbc0: setting card to irq 5, drq 5, 1
pcm0: SB DSP 4.02 on sbc0
and works happily.
Regards
Oliver
--
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])
"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
(Terry Pratchett)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Hi ... URL:http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=245121+249137+/usr/local/www/db/text/1998/freebsd-multimedia/19980215.freebsd-multimedia I (and many others, I'm sure) would be very grateful if somebody would implement Luigi's first suggestion, to wit: I get the hint :) 1) complete the SETFRAGMENT (or whatever it is called) implementation (not hard, you just need to reduce the blocksize in the dma buffer descriptor and reset the dma channel; I had a look at the current pcm in -current ... there is code to change the second snd buffer size when it is requested ... but I'm not exactly sure what is the difference between the first and second buffer I stil have to find out how to "reset" the dma channel ... because I don't see that that is done anywhere Anyone with some help :) The ioctl in question is SNDCTL_DSP_SETFRAGMENT. Its semantics are described in the "Making audio complicated" section of the OSS Programmer's Guide: URL:http://www.opensound.com/pguide/audio2.html. I'm having a look at this too :) Reinier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Chris Giordano [EMAIL PROTECTED] writes: Luigi Rizzo explained this behavior in the old pcm driver about a year or so ago. I believe it was due to some applications setting a fixed buffering size with the SETFRAGMENT(?) ioctl, which was not implemented in old pcm and then mistakenly writing smaller than intended sound samples because they assumed a different buffer size. I don't know if this applies to newpcm, but it sounds like the same symptoms. Check the -current mailing list archives for pcm0 and xgalaga. -multimedia, actually: URL:http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=245121+249137+/usr/local/www/db/text/1998/freebsd-multimedia/19980215.freebsd-multimedia I (and many others, I'm sure) would be very grateful if somebody would implement Luigi's first suggestion, to wit: 1) complete the SETFRAGMENT (or whatever it is called) implementation (not hard, you just need to reduce the blocksize in the dma buffer descriptor and reset the dma channel; The ioctl in question is SNDCTL_DSP_SETFRAGMENT. Its semantics are described in the "Making audio complicated" section of the OSS Programmer's Guide: URL:http://www.opensound.com/pguide/audio2.html. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Peter Wemm [EMAIL PROTECTED] writes: Dag-Erling Smorgrav wrote: My SB128 still doesn't attach: Does the following hack work? Beautifully! DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
On Wed, Jan 12, 2000 at 10:08:17AM -0800, Glendon Gross wrote: Are there any tricks to enabling Awe64 support? I initially removed my Awe64 card from my first FreeBSD machine to avoid interrupt conflicts, and now I would like to try to integrate it back again. Would you mind sending me your /sys/i386/conf/GENERIC or correct kernel build file? Thanks! --Glen Gross The relevent bit from my kernel config is: device pcm0 :-) Way back in the dim dark ages I used to use a boot.config command which set it to "os" configuration mode and explicity configured IRQ, DRQ's and port numbers to the same values I was using in my old "controller sbc0" configuration line, but I don't need to do that anymore. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
"Cameron Grant" [EMAIL PROTECTED] writes: would everyone who currently has an issue outstanding with newpcm please report it to me in the next few days directly, please, so i can get an idea of what needs work before release. i need as much detail as possible. My SB128 still doesn't attach: root@des ~# pciconf -l | grep none none0@pci0:10:0:class=0x040100 card=0x13711274 chip=0x13713274 rev=0x06 hdr=0x00 root@des ~# grep 1371 /var/run/dmesg.boot pci0: unknown card (vendor=0x3274, dev=0x1371) at 10.0 irq 5 DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
"Cameron Grant" [EMAIL PROTECTED] writes: would everyone who currently has an issue outstanding with newpcm please report it to me in the next few days directly, please, so i can get an idea of what needs work before release. i need as much detail as possible. My ess1869, current as of Sunday, still repeats the end of wav and au files 0-3 times and I get no sound from amp playing a mp3. It acts as though the volume were down, and cpu usage drops off to nothing and it never finishes. It just blocks sound until it is killed. Mpg movies have sound with no repeating using mtvp. These conditions seem to change some everything there is a change in buffering. This is especially noticeable if you enable sound in kde. Is anyone else seeing this with an ess186? ? Thanks, ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Dag-Erling Smorgrav wrote:
"Cameron Grant" [EMAIL PROTECTED] writes:
would everyone who currently has an issue outstanding with newpcm please
report it to me in the next few days directly, please, so i can get an idea
of what needs work before release. i need as much detail as possible.
My SB128 still doesn't attach:
root@des ~# pciconf -l | grep none
none0@pci0:10:0:class=0x040100 card=0x13711274 chip=0x13713274 rev=0x
06 hdr=0x00
root@des ~# grep 1371 /var/run/dmesg.boot
pci0: unknown card (vendor=0x3274, dev=0x1371) at 10.0 irq 5
Hmm.. different vendor id?
peter@overcee[11:16pm]~src/sys/dev/sound/pci-383 grep ES1371_PCI_ID *
es137x.c:#define ES1371_PCI_ID 0x13711274
es137x.c: } else if (pci_get_devid(dev) == ES1371_PCI_ID) {
es137x.c: if (pci_get_devid(dev) == ES1371_PCI_ID) {
Does the following hack work?
Index: es137x.c
===
RCS file: /home/ncvs/src/sys/dev/sound/pci/es137x.c,v
retrieving revision 1.10
diff -u -r1.10 es137x.c
--- es137x.c2000/01/05 02:03:55 1.10
+++ es137x.c2000/01/11 15:18:52
@@ -70,6 +70,7 @@
/* PCI IDs of supported chips */
#define ES1370_PCI_ID 0x50001274
#define ES1371_PCI_ID 0x13711274
+#define ES1371_PCI_ID2 0x13713274
/* device private data */
struct es_info;
@@ -703,7 +704,8 @@
if (pci_get_devid(dev) == ES1370_PCI_ID) {
device_set_desc(dev, "AudioPCI ES1370");
return 0;
- } else if (pci_get_devid(dev) == ES1371_PCI_ID) {
+ } else if (pci_get_devid(dev) == ES1371_PCI_ID ||
+ pci_get_devid(dev) == ES1371_PCI_ID2) {
device_set_desc(dev, "AudioPCI ES1371");
return 0;
}
@@ -766,7 +768,8 @@
goto bad;
}
- if (pci_get_devid(dev) == ES1371_PCI_ID) {
+ if (pci_get_devid(dev) == ES1371_PCI_ID ||
+ pci_get_devid(dev) == ES1371_PCI_ID2) {
if(-1 == es1371_init(es, pci_get_revid(dev))) {
device_printf(dev, "unable to initialize the card\n");
goto bad;
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
newpcm - duplex/simplex
On my notebook I have pnp CS4232. It has to work in duplex mode - 2 dmas, but it's buggy, and works only in simplex mode - 1 dma (play + capture). Is it possible to add a option to force using of simplex mode on pnp cards? Thanks, Val __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
"Cameron Grant" [EMAIL PROTECTED] writes: would everyone who currently has an issue outstanding with newpcm please report it to me in the next few days directly, please, so i can get an idea of what needs work before release. i need as much detail as possible. SB AWE64 (ISA) works fine for most things, but audio is *very* scratchy and up to five seconds behind the action in Quake-II (these problems didn't exist with the old snd0 controller). Linux RealPlayer, mpg123, and just about everything else I've tried it with are happy, though. -current from Jan 9, dmesg is: sbc0: Creative SB AWE64 at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 0,5 on isa0 sbc0: setting card to irq 9, drq 0, 5 pcm0: SB DSP 4.16 on sbc0 /dev/sndstat says: newton@atdot cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 11 2000 09:18:06 Installed devices: pcm0: SB DSP 4.16 at io 0x220 irq 9 drq 0:5 (1/1 channels duplex) - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Reinier Bezuidenhout wrote: I'm also experiencing a dely in sound on most games ... on some it's up to 7 seconds behind the action of the game ... Xgalaga is an example of this delay Any ideas ... Luigi Rizzo explained this behavior in the old pcm driver about a year or so ago. I believe it was due to some applications setting a fixed buffering size with the SETFRAGMENT(?) ioctl, which was not implemented in old pcm and then mistakenly writing smaller than intended sound samples because they assumed a different buffer size. I don't know if this applies to newpcm, but it sounds like the same symptoms. Check the -current mailing list archives for pcm0 and xgalaga. Chris Giordano [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm
would everyone who currently has an issue outstanding with newpcm please report it to me in the next few days directly, please, so i can get an idea of what needs work before release. i need as much detail as possible. - cameron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM issue
I've noticed the same thing on my Soundblaster Vibra 16X = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sat, 8 Jan 2000, Theo van Klaveren wrote: Second in the series of errors recompiling current after a month is a bug I noticed in the NewPCM driver. It skips the last half second or so of its output. This isn't noticeable when playing music, but sound effects really suck. Relevant dmesg output: . sbc0: Creative SB16/SB32 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: SB DSP 4.13 on sbc0 . The card is a Creative SoundBlaster AWE32. It worked about a month ago. Does this also have something to do with the buffering issues I've seen coming by on -current? /^\ | Theo van Klaveren [EMAIL PROTECTED] /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 \_/-|-\_/ | / | This email was powered by FreeBSD `He's the mad scientist, and I'm his beautiful daughter.' - opening sentence from Heinlein's 'The number of the beast' 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
Re: NewPCM issue
I believe I get the same thing too on my nonpnp SB16. Only noticed it when playing short au files (didn't test anything else because it wasnt noticable) On Sat, 8 Jan 2000, Kenneth Wayne Culver wrote: I've noticed the same thing on my Soundblaster Vibra 16X = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq| | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sat, 8 Jan 2000, Theo van Klaveren wrote: Second in the series of errors recompiling current after a month is a bug I noticed in the NewPCM driver. It skips the last half second or so of its output. This isn't noticeable when playing music, but sound effects really suck. Relevant dmesg output: . sbc0: Creative SB16/SB32 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: SB DSP 4.13 on sbc0 . The card is a Creative SoundBlaster AWE32. It worked about a month ago. Does this also have something to do with the buffering issues I've seen coming by on -current? /^\ | Theo van Klaveren [EMAIL PROTECTED] /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 \_/-|-\_/ | / | This email was powered by FreeBSD `He's the mad scientist, and I'm his beautiful daughter.' - opening sentence from Heinlein's 'The number of the beast' 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm can't play wave files after cvsup+make world...
Hello! I think after some -stable period -current stay now like current :-) I can't play wave files after upgrade my -current... % ls -al /dev/MAKEDEV -r-xr-xr-x 1 root wheel 35926 8 ÑÎ× 23:11 /dev/MAKEDEV % uname -a FreeBSD ozz.freebsd.org.ru 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jan 9 02:10:04 MSK 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/SONIC i386 % cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 9 2000 02:09:08 Installed devices: pcm0: AudioPCI ES1370 at io 0xe800 irq 10 (1/1 channels duplex) % dmesg | grep pcm pcm0: AudioPCI ES1370 port 0xe800-0xe83f irq 10 at device 11.0 on pci0 At kernel description of my card looks like this: device pcm0# Sound Blaster 128 PCI device sbc0# device joy0 at isa? port IO_GAME # Rgdz, Sergey A. Osokin aka oZZ, [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.freebsd.org.ru/~osa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm problems
With yesterday's current I get bounce buffer panics in isa_dmastart doing cat foo.pcm /dev/dsp. The same thing happens with mss.c v1.42 modified to reduce MSS_BUFSIZE by 48k. The card is ESS1869 in this case: Jan 5 02:16:55 avalon /kernel: unknown0: ESS ES1869 Plug and Play AudioDrive at port 0x800-0x807 on isa0 Jan 5 02:16:55 avalon /kernel: sbc0: ESS ES1869 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 Jan 5 02:16:55 avalon /kernel: pcm0: SB DSP 3.01 (ESS mode) on sbc0 Jan 5 02:16:55 avalon /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 5 02:16:55 avalon /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 5 02:16:55 avalon /kernel: joy1: ESS0001 PnP Joystick at port 0x200 on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM causes kernel panics !
On Tue, 4 Jan 2000, Pascal Hofstee wrote: Hi, With CURRENT sources updated earlier today ... my system now crash-and-burns when trying to play audio. i have foudn these messages in /var/log/messages: Jan 4 01:30:26 shadowmere /kernel: gusc0: Gravis UltraSound MAX at port 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 Jan 4 01:30:26 shadowmere /kernel: pcm0: GUS CS4231 on gusc0 Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 If any more info is needed let me know. This looks like a buffer which spans 1 non-contiguous physical ranges. Was the buffer allocated with contigmalloc? -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA))
On Tue, Jan 04, 2000 at 10:30:22AM +, Alex [EMAIL PROTECTED] wrote: and I apologise for wrongfully accusing it. The panic is in fact caused by newpcm (Cameron CC'd). DDB trace can be provided upon request (is there a way to save it into a file instead of having to write it down on a piece of paper?) Sure. Hook up serial console or some terminal program to appropriate serial port using null-modem cable, then rebuild your kernel and boot with right flag. Look at sys/i386/LINT, man sio(4) and man boot(8). -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM causes kernel panics !
On Tue, Jan 04, 2000 at 09:27:54AM +, Doug Rabson wrote: On Tue, 4 Jan 2000, Pascal Hofstee wrote: Hi, With CURRENT sources updated earlier today ... my system now crash-and-burns when trying to play audio. i have foudn these messages in /var/log/messages: Jan 4 01:30:26 shadowmere /kernel: gusc0: Gravis UltraSound MAX at port 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 Jan 4 01:30:26 shadowmere /kernel: pcm0: GUS CS4231 on gusc0 Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 If any more info is needed let me know. This looks like a buffer which spans 1 non-contiguous physical ranges. Was the buffer allocated with contigmalloc? I don't know this is what came directly from the NewPCM-probe/attach code. -- Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic in newpcm ( was Re: Ouch! Something broke (possibly ATA))
Soren Schmidt wrote: It seems Alex wrote: pcm0: CS4231 at port 0x530-0x537,0x538-0x539 irq 5 drq 1 flags 0xa110 on isa0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xbff21000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0214ffe stack pointer = 0x10:0xc02f6b58 frame pointer = 0x10:0xc02f6b8c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam trap number = 12 panic: page fault Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort % nm /kernel.test | grep c0214f c0214f68 T bus_dmamap_load c0214f28 T bus_dmamem_free Those are not used by the ata driver -Søren and I apologise for wrongfully accusing it. The panic is in fact caused by newpcm (Cameron CC'd). DDB trace can be provided upon request (is there a way to save it into a file instead of having to write it down on a piece of paper?) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA))
On Tue, 4 Jan 2000, Alex wrote: and I apologise for wrongfully accusing it. The panic is in fact caused by newpcm (Cameron CC'd). DDB trace can be provided upon request (is there a way to save it into a file instead of having to write it down on a piece of paper?) Serial consoles are your friend. I recently started using them and am never going back. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NewPCM causes kernel panics !
Hi, With CURRENT sources updated earlier today ... my system now crash-and-burns when trying to play audio. i have foudn these messages in /var/log/messages: Jan 4 01:30:26 shadowmere /kernel: gusc0: Gravis UltraSound MAX at port 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 Jan 4 01:30:26 shadowmere /kernel: pcm0: GUS CS4231 on gusc0 Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 If any more info is needed let me know. -- Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Newpcm is broken again for mpg123 (ESS 1868 isa sound card)
Seigo Tanimura wrote: On Mon, 27 Dec 1999 16:08:01 +0900, Seigo Tanimura [EMAIL PROTECTED] said: Seigo Another fix was made on feeding and sucking pcm data. Now chn_wrfeed() Seigo and the other functions do not attempt excessive feeding during DMA Seigo transfer to eat up the whole processor. The patch is at: Ouch, the patch broke Rollemup, so I fixed just now. The URI is the same. Seigo http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz I just recently did another cvsup, and now newpcm is broken again. When I try to play a clip with mpg123, I hear a very short burst of the beginning of the clip repeated indefinitely, like so: "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS 1868, of course. Well, I (wisely) saved my old kernel as /kernel.good and just booted into that. Could you also say what was fixed if you get around to it? I'd to learn a little more about the sound driver. Thanks for your help. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm and non-PnP SoundBlaster Vibra 16 4.13
Hi. I have been following the thread(s) about getting the SoundBlaster Vibra 16 sound-cards working in -current, and it appears that if you have a PnP card, it seems to be working. I do not have a PnP version of this card, and the last time I was able to get the sound card recognised was October 2nd. A verbose boot of that kernel reveals sb_probe: no addr, trying (0x220, 0x240) pcm: SoundBlaster 16 4.13) at irq 10 drq 3 flags 0x17 on isa0 sb_probe: no addr, trying (0x220, 0x240) pcm: setmap 4c, ff00; 0xc80b500 - 4c000 pcm: setmap 4d, ff00; 0xc80c500 - 4d000 and /dev/sndstat reveals FreeBSD Audio Driver (newpcm) Oct 2 1999 14:30:27 Installed devices: pcm0: SoundBlaster 16 4.13 at io 0x220 irq 10 drq 3:7 (1/1 channels duplex) With subsequent kernels, including a -current kernel from 20 Dec, the sound card is not detected. The definitions I'm using in my kernel currently (no pun intended :) are #sound card device pcm0 device sbc0 at isa? port ? irq 10 drq 3 flags 0x17 as compared to what I had device pcm0 at isa? port ? irq 10 drq 3 flags 0x17 The card is probed if the machine is booted with a kernel of Oct 2, and not probed if the machine is botted with a kernel of Dec 20. The only other thing I can think of is that the old kernel had support for PnP, whereas the new ones doesn't. This shouldn't matter though if I'm supplying the parameters directly to the card. Khetan Gajjar. --- [EMAIL PROTECTED] * [EMAIL PROTECTED]* PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za/ * http://www.freebsd.org/ * information at System Administration * http://link.os.org.za/ * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm, and Linux RealPlayer 5.0
On Mon, 20 Dec 1999, Cameron Grant wrote: On Sat, 18 Dec 1999, Donn Miller wrote: I just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. The ESS 18xx support seems to be broken at the moment. I have one here and I'll fix it as soon as I get a chance to work on it. a recent commit changed the assumptions made by the upper layer code, breaking devices not using auto-init dma. last night i committed a fix to make the ess cards use autoinit, so they should work now. Great. Thanks Cameron. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm, and Linux RealPlayer 5.0
On Sat, 18 Dec 1999, Donn Miller wrote: I just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. The ESS 18xx support seems to be broken at the moment. I have one here and I'll fix it as soon as I get a chance to work on it. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm, and Linux RealPlayer 5.0
On Sat, 18 Dec 1999, Donn Miller wrote: I just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. The ESS 18xx support seems to be broken at the moment. I have one here and I'll fix it as soon as I get a chance to work on it. a recent commit changed the assumptions made by the upper layer code, breaking devices not using auto-init dma. last night i committed a fix to make the ess cards use autoinit, so they should work now. - cameron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm,
Cameron, Thanks, my sound now works but something is different. I am getting very high frequency oscillations that I've never had and don't understand. It must have something to to with the mike and the speakers on my laptop but there has never been regenerative feedback between them before. Could the driver somehow be responsible? Thanks again, ed Cameron Grant wrote: On Sat, 18 Dec 1999, Donn Miller wrote: I just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. The ESS 18xx support seems to be broken at the moment. I have one here and I'll fix it as soon as I get a chance to work on it. a recent commit changed the assumptions made by the upper layer code, breaking devices not using auto-init dma. last night i committed a fix to make the ess cards use autoinit, so they should work now. - cameron 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
Re: ESS 1868, newpcm, and Linux RealPlayer 5.0
Edwin Culp wrote: You're lucky, you got to the realplayer.:-) My ESS1869 hangs on a simple cat gong.au/dev/audio. Do you have sound with everything except realplayer? Nope. Just tried cat hello.au /dev/dsp. Nothing. It hangs at the command line. Same with cat *.au /dev/audio. Hangs. Same behavior with RealPlayer in fact; RealPlayer just hangs when I press "play", and I get no sound. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm, and Linux RealPlayer 5.0
Donn, Thanks for the feedback. Misery loves company, they say.:-) We seem to have the same problem. Does anyone with a ESS 186[89] have their sound working with a recent world and device pcm0 device sbc0 Thanks, ed Donn Miller wrote: Edwin Culp wrote: You're lucky, you got to the realplayer.:-) My ESS1869 hangs on a simple cat gong.au/dev/audio. Do you have sound with everything except realplayer? Nope. Just tried cat hello.au /dev/dsp. Nothing. It hangs at the command line. Same with cat *.au /dev/audio. Hangs. Same behavior with RealPlayer in fact; RealPlayer just hangs when I press "play", and I get no 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, newpcm, and Linux RealPlayer 5.0
I just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problem with sbc driver and/or newpcm
The sbc driver seems to correctly detect my soundcard for the first time since the introduction of newpcm but I don't actually get sound out of it. I think the IRQ it's detecting might be wrong. Both Windows 98 and the old pcm driver always used IRQ 10. Unfortunately my BIOS is too brain-damaged to report IRQ's for ISA devices at boot so I can't be sure. I have tried options PNPBIOS as well as trying to specify irq 10 to sbc to no avail. I'd appreciate any assistance. Here's output from dsmesg and pnpinfo: 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-19991214-CURRENT #0: Wed Dec 15 02:44:58 CST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/NIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350796172 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 134217728 (131072K bytes) avail memory = 127004672 (124028K bytes) Preloaded elf kernel "kernel" at 0xc02ac000. md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: AcerLabs M1541 (Aladdin-V) PCI host bridge on motherboard pci0: PCI bus on pcib0 pcib1: AcerLabs M5243 PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 chip1: AcerLabs M15x3 Power Management Unit at device 3.0 on pci0 isab0: AcerLabs M1533 portable PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 xl0: 3Com 3c905B-TX Fast Etherlink XL irq 9 at device 9.0 on pci0 xl0: Ethernet address: 00:50:da:24:3a:c5 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: Adaptec 2910/15/20/30C SCSI adapter irq 9 at device 10.0 on pci0 ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs vga-pci0: Matrox MGA 1024SG/1064SG/1164SG graphics accelerator irq 11 at device 11.0 on pci0 ata-pci0: AcerLabs Aladdin ATA controller irq 0 at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 sbc0: Creative ViBRA16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 pcm0: SB DSP 4.16 on sbc0 unknown0: Game at port 0x201 on isa0 ad0: WDC AC28400R/17.01J57 ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: WDC AC36400L/09.09M08 ATA-4 disk at ata0 as slave ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 acd0: CD-ROM CDU4011/UY04 CDROM drive at ata1 as master acd0: read 6890KB/s (6890KB/s), 120KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad1s1a cd0 at ahc0 bus 0 target 4 lun 0 cd0: SCSI-CD ReWritable-2x2x6 2.00 Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0x PnP Version 1.0, Vendor Version 16 Device Description: Creative ViBRA16X PnP Logical Device ID: CTL0043 0x43008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignme
Re: ESS1688 newpcm support, soundblaster panics at boot
On Tue, 14 Dec 1999, Andrew Gallatin wrote: I have an old, wheezing Dell Lattitude LM with an ESS1688 sound chip. (specs at http://support.dell.com/docs/systems/pespmmx/specs.htm) I have managed to get newpcm to find the 1688 via 'options PNPBIOS' and the following patch: I've added this to my sources. I'll commit it after I get the rest working. However, the machine now panics on boot in sbchan_init(), at line 821 of sb.c with a page fault on access to virtual address 0x14: I strongly suspect that this is due to the fact that this card has only 1 dma channel. I suspect the panic is caused by rman_get_start(sb-drq2) when sb-drq2 is null. Does newpcm even support simplex operations on soundblaster chips? I ask because I simply could not get simplex operations to work on my wss cards, so I suspect that simplex operation is simply not well tested. It is supposed to support simplex but that support has changed recently so perhaps it broke. I already have a report that the ESS1888 is broken at the moment and I will be fixing it as soon as I find a spare couple of hours to tackle it (I have an ESS1888 in my miata). Can anybody who is more familiar with newpcm please point me in the right direction? Not sure where to look yet. Something is probably passing a NULL channel. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with sbc driver and/or newpcm
On Wed, 15 Dec 1999, Jeremy L. Stock wrote: The sbc driver seems to correctly detect my soundcard for the first time since the introduction of newpcm but I don't actually get sound out of it. I think the IRQ it's detecting might be wrong. Both Windows 98 and the old pcm driver always used IRQ 10. Unfortunately my BIOS is too brain-damaged to report IRQ's for ISA devices at boot so I can't be sure. I have tried options PNPBIOS as well as trying to specify irq 10 to sbc to no avail. I'd appreciate any assistance. It is perfectly reasonable for the kernel to choose irq 5 for this card since its free and the soundcard supports it. There is a known problem with the vibra16x at the moment. Last I heard, Cameron was part way through fixing it. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with sbc driver and/or newpcm
On Wed, Dec 15, 1999 at 03:09:10AM -0600, Jeremy L. Stock wrote: The sbc driver seems to correctly detect my soundcard for the first time since the introduction of newpcm but I don't actually get sound out of it. Just a quick check: Can you type "mixer" at a shell prompt and check whether the reason you're getting no sound is because the master volume level defaults to 0? - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with sbc driver and/or newpcm
Same here: henny:n_hibma# mixer Mixer vol is currently set to 75:75 Mixer synthis currently set to 0:0 Mixer pcm is currently set to 75:75 Mixer line is currently set to 75:75 Mixer mic is currently set to 0:0 Mixer cd is currently set to 75:75 sbc0: ESS ES1879 at port 0x220-0x22f,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: SB DSP 3.01 on sbc0 Nick On Wed, 15 Dec 1999, Mark Newton wrote: On Wed, Dec 15, 1999 at 03:09:10AM -0600, Jeremy L. Stock wrote: The sbc driver seems to correctly detect my soundcard for the first time since the introduction of newpcm but I don't actually get sound out of it. Just a quick check: Can you type "mixer" at a shell prompt and check whether the reason you're getting no sound is because the master volume level defaults to 0? - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ESS1688 newpcm support, soundblaster panics at boot
I have an old, wheezing Dell Lattitude LM with an ESS1688 sound chip.
(specs at http://support.dell.com/docs/systems/pespmmx/specs.htm)
I have managed to get newpcm to find the 1688 via 'options PNPBIOS'
and the following patch:
Index: sys/dev/sound/isa/sbc.c
===
RCS file: /home/ncvs/src/sys/dev/sound/isa/sbc.c,v
retrieving revision 1.7
diff -u -r1.7 sbc.c
--- sbc.c 1999/12/12 02:30:19 1.7
+++ sbc.c 1999/12/14 04:47:41
@@ -187,6 +187,7 @@
{0x0111, "Avance Asound 110"},
{0x0121, "Avance Logic ALS120"},
+ {0x02017316, "ESS ES1688"}, /* ESS1688 */
{0x68187316, "ESS ES1868"}, /* ESS1868 */
{0x69187316, "ESS ES1869"}, /* ESS1869 */
{0xacb0110e, "ESS ES1869 (Compaq OEM)"},
However, the machine now panics on boot in sbchan_init(), at line 821
of sb.c with a page fault on access to virtual address 0x14:
810 static void *
811 sbchan_init(void *devinfo, snd_dbuf *b, pcm_channel *c, int dir)
812 {
813 struct sb_info *sb = devinfo;
814 struct sb_chinfo *ch = (dir == PCMDIR_PLAY)? sb-pch : sb-rch;
815
816 ch-parent = sb;
817 ch-channel = c;
818 ch-buffer = b;
819 ch-buffer-bufsize = DSP_BUFFSIZE;
820 if (chn_allocbuf(ch-buffer, sb-parent_dmat) == -1) return NULL;
821 ch-buffer-chan = (dir == PCMDIR_PLAY)? rman_get_start(sb-drq2)
822 : rman_get_start(sb-drq1);
823 return ch;
824 }
I strongly suspect that this is due to the fact that this card has
only 1 dma channel. I suspect the panic is caused by
rman_get_start(sb-drq2) when sb-drq2 is null.
Does newpcm even support simplex operations on soundblaster chips? I
ask because I simply could not get simplex operations to work on my
wss cards, so I suspect that simplex operation is simply not well
tested.
Can anybody who is more familiar with newpcm please point me in the
right direction?
Thanks,
Drew
--
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Fast forward bug and newpcm (again)
On Tue, 30 Nov 1999 02:30:41 -0500 (EST), Donn Miller [EMAIL PROTECTED] said: sbc driver does not probe ESS1868 at this moment. Donn Question: will the ESS 1868 bridge driver be incorporated into the sbc Donn driver, or should we devise a whole new bridge driver for the ess? I.e., Donn we would have: Donn device ess0 # ESS bridge driver I prefer ess0. ESS is the name of soundcards as well, so the name of the driver matches those of the cards. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More newpcm breakage
On Tue, Nov 30, 1999 at 10:30:28AM +0900, [EMAIL PROTECTED] wrote: On 29 Nov 1999 19:19:24 +0100, Dag-Erling Smorgrav [EMAIL PROTECTED] said: Dag-Erling My SB32 PnP, which had so far worked nicely with newpcm except for the Dag-Erling "fast forward" bug, stopped working after the newmidi import. This Dag-Erling means that none of my sound cards (except for the GUS PnP, which I Dag-Erling haven't tested) work any more, and I am seriously losing faith in the Dag-Erling authors' ability to maintain a device driver. Did you add sbc into your kernel configuration? Maybe I should add a warning in sb.c... I don't if DES did, but I did. Turns out from his dmesg that he has a very similar hardware config (which is why I don't include a copy of my dmesg) and I am seeing *exactly* the same problems - suddenly my AWE32 is not recognized any more. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More newpcm breakage
On Tue, 30 Nov 1999, Timo Geusch wrote: On Tue, Nov 30, 1999 at 10:30:28AM +0900, [EMAIL PROTECTED] wrote: On 29 Nov 1999 19:19:24 +0100, Dag-Erling Smorgrav [EMAIL PROTECTED] said: Dag-Erling My SB32 PnP, which had so far worked nicely with newpcm except for the Dag-Erling "fast forward" bug, stopped working after the newmidi import. This Dag-Erling means that none of my sound cards (except for the GUS PnP, which I Dag-Erling haven't tested) work any more, and I am seriously losing faith in the Dag-Erling authors' ability to maintain a device driver. Did you add sbc into your kernel configuration? Maybe I should add a warning in sb.c... I don't if DES did, but I did. Turns out from his dmesg that he has a very similar hardware config (which is why I don't include a copy of my dmesg) and I am seeing *exactly* the same problems - suddenly my AWE32 is not recognized any more. Sounds like a missing pnp id. What does the output from pnpinfo look like? -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
can't use vat (and only vat) with newpcm
I'm having problems running vat with newpcm: after opening the device the sound begins for a fraction of a second, then stops. Maybe this has to do with the fact that vat uses /dev/audio and not /dev/dsp; I've tried to open /dev/dsp instead and change the device format but the result is the same. Or maybe this has to do with the non-blocking opening done by vat (I've changed this too, same result). But strangely enough, a cat /dev/audio, amp or mpg123 all work ok. The chip is the following. The kernel is configured with just "device pcm0". From a ktrace, vat does nothing but writes to the device. pcm0: CS4236B at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown0: Game at port 0x3a0-0x3a7 on isa0 unknown1: Ctrl at port 0xf00-0xf07 on isa0 unknown2: MPU at port 0x330-0x331 on isa0 -- Pierre Beyssac [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
More newpcm breakage
My SB32 PnP, which had so far worked nicely with newpcm except for the "fast forward" bug, stopped working after the newmidi import. This means that none of my sound cards (except for the GUS PnP, which I haven't tested) work any more, and I am seriously losing faith in the authors' ability to maintain a device driver. I've attached the output of dmesg and pnpinfo from the affected box, both with and without the PNPBIOS option. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] 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 #17: Wed Nov 24 20:31:13 CET 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/NIOBE Calibrating clock(s) ... TSC clock: 166192956 Hz, i8254 clock: 1193180 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/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x002e5000 - 0x07ff7fff, 131149824 bytes (32019 pages) avail memory = 126554112 (123588K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f8630 bios32: Entry = 0xf8080 (c00f8080) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x80b0 pnpbios: Found PnP BIOS data at 0xc00fc730 pnpbios: Entry = f:c760 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: Preloaded elf kernel "kernel" at 0xc02cc000. Intel Pentium detected, installing workaround for F00F bug VESA: information block 56 45 53 41 00 02 d9 6c 00 c0 00 00 00 00 22 00 00 01 24 00 00 00 eb 6c 00 c0 eb 6c 00 c0 eb 6c 00 c0 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0c 01 22 01 24 01 2a 01 1d 01 VESA: 52 mode(s) found VESA: v2.0, 2304k memory, flags:0x0, mode table:0xc027d742 (122) VESA: Tseng Labs ET6000 VESA: pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=12508086) npx0: math processor on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 173731758 bytes/sec bzero() bandwidth = 736377025 bytes/sec pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=12508086) pcib0: Host to PCI bridge on motherboard found- vendor=0x8086, dev=0x1250, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 1, range 32, base e800, size 4 found- vendor=0x100c, dev=0x3208, revid=0x70 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base f900, size 24 map[14]: type 1, range 32, base e000, size 8 found- vendor=0x8086, dev=0x1229, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base fa80, size 12 map[14]: type 1, range 32, base d800, size 5 map[18]: type 1, range 32, base f880, size 20 found- vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base d400, size 8 map[14]: type 1, range 32, base f800, size 12 pci0: PCI bus on pcib0 i4b_pci_probe: unknown PCI type 307265670l! isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 I/O Recovery Timing: 8-bit 3.5 clocks, 16-bit 3.5 clocks Extended BIOS: disabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: IRQ12, B: disabled, C: IRQ9, D: IRQ9 MB0: IRQ15, MB1: isa0: ISA bus on isab0 ata-pci0: Intel PIIX3 IDE controller at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=00 status0=fe status1=fe i4b_pci_probe: unknown PCI type 839389196l! vga-pci0: Tseng Labs ET6000 graphics accelerator irq 9 at device 9.0 on pci0 fxp0: Intel EtherExpress Pro 10/100B Ethernet irq
MAKEDEV newpcm driver
So, is the right command to make the audio device entries ./MAKEDEV snd0, or does newpcm have a different method to create the audio device entries? Also, I have an ESS 1868, and I'm getting the "fast forward" effect with the newpcm driver. It's a SB compatible card. I'll attach the output of dmesg. -- - Donn 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 #0: Mon Nov 29 13:40:20 EST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/CUSTOM Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (166.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 62914560 (61440K bytes) avail memory = 57962496 (56604K bytes) Preloaded elf kernel "kernel" at 0xc02f5000. Intel Pentium detected, installing workaround for F00F bug npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: SiS 85c503 PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 ide_pci0: SiS 5591 Bus-master IDE Controller irq 11 at device 1.1 on pci0 ed0: NE2000 PCI Ethernet (RealTek 8029) irq 10 at device 10.0 on pci0 ed0: address 00:c0:df:ed:0b:17, type NE2000 (16 bit) vga-pci0: SiS model 0200 VGA-compatible display device irq 11 at device 19.0 on pci0 devclass_alloc_unit: ed0 already exists, using next available unit number fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): FUJITSU MPB3032ATU, DMA, 32-bit, multi-block-16 wd0: 3093MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): M1614TA, DMA, 32-bit, multi-block-16 wd1: 1040MB (2130912 sectors), 2114 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 0 (atapi): BCD-24X 1997-06-27/VER 2.0, removable, accel, dma, iordy wcd0: drive speed 515 - 1718KB/sec, 128KB cache wcd0: supported read types: CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: CD-ROM 120mm data disc loaded, unlocked atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 mse0 at port 0x23c irq 3 on isa0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0: not probed (disabled) sio1: not probed (disabled) sio2 at port 0x3e8-0x3ef irq 4 on isa0 sio2: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 unknown0: ESS ES1868 Plug and Play AudioDrive at port 0x800-0x807 on isa0 pcm0: ESS1868 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 unknown1: ESS ES1868 Plug and Play AudioDrive at port 0x201 on isa0 Mounting root from ufs:/dev/wd0s1a
Re: More newpcm breakage
On 29 Nov 1999 19:19:24 +0100, Dag-Erling Smorgrav [EMAIL PROTECTED] said: Dag-Erling My SB32 PnP, which had so far worked nicely with newpcm except for the Dag-Erling "fast forward" bug, stopped working after the newmidi import. This Dag-Erling means that none of my sound cards (except for the GUS PnP, which I Dag-Erling haven't tested) work any more, and I am seriously losing faith in the Dag-Erling authors' ability to maintain a device driver. Did you add sbc into your kernel configuration? Maybe I should add a warning in sb.c... -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV newpcm driver
On Mon, Nov 29, 1999, Donn Miller wrote: So, is the right command to make the audio device entries ./MAKEDEV snd0, or does newpcm have a different method to create the audio device entries? Also, I have an ESS 1868, and I'm getting the "fast forward" effect with the newpcm driver. It's a SB compatible card. If you read -current, you'd see the HEADS UP about the bridge drivers. Please pay more attention. -- |Chris Costello [EMAIL PROTECTED] |Programming is an unnatural act. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Fast forward bug and newpcm (again)
Yes, I DO have the bridge drivers in my kernel config files, and I still get the "fast forward" effect with my ESS 1868. My guess is that it's just a bug with the ESS 1868 driver, I don't know. Maybe my ordering is wrong? I've had the sbc driver for the ESS ever since the bridge drivers came out. And people want to accuse me of not paying attention. Here's an excerpt from my kernel config: device sbc0 device pcm0 See that, I clearly have the bridge driver in my kernel config. Now, the question is, do I use the Sound Blaster bridge driver for the ESS 1868? And, is my ordering wrong? Actually, I've had the "Fast forward" bug with -current since the beginning of Oct. Maybe it's a thing with the ESS 1868, I don't know. But I did in fact have the bridge drivers in my config file, and compiled/installed the kernel with the sbc bridge driver. One person mentioned that the ESS doesn't want to work unless it's in mss mode (instead of SB compatibility mode). - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fast forward bug and newpcm (again)
On Tue, 30 Nov 1999 01:41:20 -0500, Donn Miller [EMAIL PROTECTED] said: Donn Now, the question is, do I use the Sound Blaster bridge driver Donn for the ESS 1868? And, is my ordering wrong? sbc driver does not probe ESS1868 at this moment. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More newpcm breakage
-On [19991129 19:49], Dag-Erling Smorgrav ([EMAIL PROTECTED]) wrote: My SB32 PnP, which had so far worked nicely with newpcm except for the "fast forward" bug, stopped working after the newmidi import. This means that none of my sound cards (except for the GUS PnP, which I haven't tested) work any more, and I am seriously losing faith in the authors' ability to maintain a device driver. This is CURRENT des, things are expected to not work or even break at times. And instead of just throwing out and voicing this `loss of faith' you could have taken a more active approach and try and help and see what was causing the actual problems with the not-detection of the cards. Cameron and Tanimura-san have done great work and we getting further and further where we want to go with the new sound support. The FreeBSD Project taught me that it is easy to just bitch and moan, but that the real work only comes when you help with it yourself. That's a lesson you must have learned way before I even joined helping on the project. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html Sometimes the Heart wanders in fantasies, keeping the mind in its power constantly... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fast forward bug and newpcm (again)
On Tue, 30 Nov 1999, Seigo Tanimura wrote: On Tue, 30 Nov 1999 01:41:20 -0500, Donn Miller [EMAIL PROTECTED] said: Donn Now, the question is, do I use the Sound Blaster bridge driver Donn for the ESS 1868? And, is my ordering wrong? sbc driver does not probe ESS1868 at this moment. Question: will the ESS 1868 bridge driver be incorporated into the sbc driver, or should we devise a whole new bridge driver for the ess? I.e., we would have: device ess0 # ESS bridge driver if we write a separate ess bridge driver. I'll look over some of the bridge driver source code to see what needs to be done. Hopefully, I can help out in some way. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Adding soundcards to newpcm
Doug Rabson wrote: Well, I finally decided to try to get my sound card working again. It is not detected as a PNP device, but rather as a motherboard resource using PNPBIOS. It is supposed to be an ESS1869 and, indeed, I use ESS drivers on Windows. But Compaq obviously decided to lay it's fingerprints on the poor thing. Here is the (relavant parts of) dmesg: Use this program. It translates to/from EISAIDs. Well, I got farther, but no luck yet. The device is identified, but incorrectly: pcm0: ESS1888 at port 0x220-0x22f irq 5 drq 1 on isa0 it still shows up in the PNPBIOS information, though: unknown: CPQb0ac can't assign resources Finally, cat sndstat shows yet another thing: FreeBSD Audio Driver (newpcm) Nov 17 1999 19:30:14 Installed devices: pcm0: ESS1868 rev 11 at io 0x220 irq 5 drq 1 (1/1 channels) Also, I have a warning showing up: WARNING: "pca" is usurping "pca"'s cdevsw[] (yes, I have pca in my kernel) When I try to output something to dsp or audio, it just blocks without doing anything. Mixer *apparently* works. I can't hear anything, but at least it sets and retrieves values. Anyone seen such behavior? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Adding soundcards to newpcm
On Wed, 17 Nov 1999, Daniel C. Sobral wrote: Doug Rabson wrote: Well, I finally decided to try to get my sound card working again. It is not detected as a PNP device, but rather as a motherboard resource using PNPBIOS. It is supposed to be an ESS1869 and, indeed, I use ESS drivers on Windows. But Compaq obviously decided to lay it's fingerprints on the poor thing. Here is the (relavant parts of) dmesg: Use this program. It translates to/from EISAIDs. Well, I got farther, but no luck yet. The device is identified, but incorrectly: pcm0: ESS1888 at port 0x220-0x22f irq 5 drq 1 on isa0 That is from a driver which I added mainly for alphas. I might disable this for x86 or modify it to coexist with PNPBIOS. Stick a 'return' in es1888_identify in sys/dev/pcm/isa/es1888.c. it still shows up in the PNPBIOS information, though: unknown: CPQb0ac can't assign resources This is because the ES1888 device is holding the resources. Also the driver needs CPQb0ac adding to its list of IDs. Finally, cat sndstat shows yet another thing: FreeBSD Audio Driver (newpcm) Nov 17 1999 19:30:14 Installed devices: pcm0: ESS1868 rev 11 at io 0x220 irq 5 drq 1 (1/1 channels) This I also know about. I might add a workaround for this. Basically the description is changed after the device was printed. Also, I have a warning showing up: WARNING: "pca" is usurping "pca"'s cdevsw[] (yes, I have pca in my kernel) Nothing to do with me :-) When I try to output something to dsp or audio, it just blocks without doing anything. Mixer *apparently* works. I can't hear anything, but at least it sets and retrieves values. Hmm. The ess driver works nicely with the ESS1888 in my alpha box. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Adding soundcards to newpcm
Well, I finally decided to try to get my sound card working again. It is not detected as a PNP device, but rather as a motherboard resource using PNPBIOS. It is supposed to be an ESS1869 and, indeed, I use ESS drivers on Windows. But Compaq obviously decided to lay it's fingerprints on the poor thing. Here is the (relavant parts of) dmesg: unknown0: PCI Bus at port 0xcf8-0xcff on isa0 unknown1: Plug and Play System Board at port 0x80,0x22-0x24,0x92,0x370-0x371,0xec-0xef,0x40b,0x4d6,0x480-0x48f iomem 0xfffc-0x on isa0 unknown2: PNP0c01 at iomem 0-0x9,0xe-0xf,0x10-0x5ff on isa0 unknown3: PNP0200 at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: PNP can't assign resources unknown4: PNP0100 at port 0x41-0x44 irq 0 on isa0 unknown5: PNP0b00 at port 0x70-0x71 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown6: PNP0c04 at port 0xf0-0xff irq 13 on isa0 unknown: PNP0800 can't assign resources unknown7: CPQb0ac at port 0x220-0x22f,0x388-0x38b,0x300-0x301 irq 5 drq 0,1 on isa0 ^^^ obviously... unknown: PNP0f13 can't assign resources unknown8: ESS0006 at port 0x800-0x807 on isa0 ^^^ unknown9: ESS0001 at port 0x201 on isa0 ^^^ though it seems they did not care about other capabilities of the chipset... unknown: PNP0501 can't assign resources unknown10: PNP0400 at port 0x378-0x37f irq 7 on isa0 unknown: PNP0700 can't assign resources unknown: CPQb0a2 can't assign resources unknown11: PNP0e03 at port 0x3e0-0x3e1 on isa0 So, the question is... how do I get the logical identifier for it? pnpinfo doesn't show anything. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Adding soundcards to newpcm
On Wed, 17 Nov 1999, Daniel C. Sobral wrote:
Well, I finally decided to try to get my sound card working again.
It is not detected as a PNP device, but rather as a motherboard
resource using PNPBIOS. It is supposed to be an ESS1869 and, indeed,
I use ESS drivers on Windows. But Compaq obviously decided to lay
it's fingerprints on the poor thing. Here is the (relavant parts of)
dmesg:
So, the question is... how do I get the logical identifier for it?
pnpinfo doesn't show anything.
Use this program. It translates to/from EISAIDs.
#include sys/param.h
#include stdio.h
int
main(int argc, char** argv)
{
u_int32_t id;
if (argc != 2)
exit(1);
if (!strncmp(argv[1], "0x", 2)) {
id = strtol(argv[1] + 2, NULL, 16);
#define B0(n) (((n) 0) 0xff)
#define B1(n) (((n) 8) 0xff)
#define B2(n) (((n) 16) 0xff)
#define B3(n) (((n) 24) 0xff)
printf("%c%c%c%02x%02x\n",
((B0(id) 0x7c) 2) + 64,
(((B0(id) 0x03) 3) | ((B1(id) 0xe0) 5)) + 64,
(B1(id) 0x1f) + 64, B2(id), B3(id));
} else {
#define PNP_HEXTONUM(c) ((c) = 'a' \
? (c) - 'a' + 10 \
: ((c) = 'A' \
? (c) - 'A' + 10\
: (c) - '0'))
#define PNP_EISAID(s) \
s[0] - '@') 0x1f) 2) \
| (((s[1] - '@') 0x18) 3) \
| (((s[1] - '@') 0x07) 13)\
| (((s[2] - '@') 0x1f) 8) \
| (PNP_HEXTONUM(s[4]) 16) \
| (PNP_HEXTONUM(s[3]) 20) \
| (PNP_HEXTONUM(s[6]) 24) \
| (PNP_HEXTONUM(s[5]) 28))
printf("0x%08x\n", PNP_EISAID(argv[1]));
}
return 0;
}
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: newpcm and Vibra16X
I don;t need it back...so I don't mind... Peter Wemm also had an idea, of setting up a clean installed box here allowing certain hosts into the network and giving a serial console to work from. I don;t mind doing this either. Let me know. If you want me to ship it, give me your address and I'll ship it in the morning. The machine I do use the Vibra16X in is at work, and for now I'm without music again. Too bad we can't have both oldpcm and newpcm for a while ;) but with the new pnp stuff I'm not sure whether I can use the old pcm stuff anymore anyway, but I've been away for 3 weeks traveling across the United States to visit my grandmother in AZ, US. Haven't has a chance to catch up on -current totally yet. -Pat ___ Pat Lynch [EMAIL PROTECTED] [EMAIL PROTECTED] Systems Administrator Rush Networking ___ On Mon, 20 Sep 1999, Doug Rabson wrote: On Sun, 19 Sep 1999, Pat Lynch wrote: I have an extra Vibra16X if you haven't gotten one yet, I'm dying to have my sound working again. -Pat If you don't mind shipping it to the UK, I can give you my address. Cameron is in the process of moving and I don't have his new address. I'm very keen to get all the cards covered by the old pcm driver (and the voxware driver as far as possible) supported again. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd.Phone: +44 181 442 9037 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
Re: newpcm broke the Esoniq 1371 Driver Hack?
I have a *VERY*preliminary version of the 1371 driver working with the newpcm code. Testing includes playing one mp3 track and adjusting the volume a few times. In other words I'm not making any promises. If anybody really needs to play with it. ftp://ftp.thebarn.com/outgoing/es1371-newpcm.src4.patch Thomas Stromberg wrote: I've been using the Esoniq 1371 Driver from http://www.freebsd.org/~ghelmer/es1371/ (written by Russell Cattelan?) on my 4.0-CURRENT box for a few weeks now. It's just a hack replacement for es1370.c/es1370_reg.h, but it worked fine up until a week ago or so when I presume the newpcm code went into place. It works against my 27AUG99 kernel however. -- Russell Cattelan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm and Vibra16X
On Tue, 14 Sep 1999, Jordan K. Hubbard wrote: If this is a card you own, please just wrap it up and put it in the post to Cameron so that he has a chance to see what is going on. If only it were - it's the on-board sound on my Tyan Thunder 100 Mobo. If you or anyone else knows of a particular card which uses this chip, however, then I'd be happy to pick one up. I have a friend with one of these. I will find out what it is, and let you know. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm and Vibra16X
On Tue, 14 Sep 1999, Jordan K. Hubbard wrote: If this is a card you own, please just wrap it up and put it in the post to Cameron so that he has a chance to see what is going on. If only it were - it's the on-board sound on my Tyan Thunder 100 Mobo. If you or anyone else knows of a particular card which uses this chip, however, then I'd be happy to pick one up. Peter mumbled something about 'borrowing' the card from his wife's machine to see if it was one of the bad ones. I don't know if it was though. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm and Vibra16X
On Mon, 13 Sep 1999, Jordan K. Hubbard wrote: Card assigned CSN #1 Vendor ID CTL0070 (0x70008c0e), Serial Number 0x PnP Version 1.0, Vendor Version 16 Device Description: Creative ViBRA16C PnP And JFYI, this: Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0x PnP Version 1.0, Vendor Version 16 Device Description: Creative ViBRA16X PnP Does *not* work with newpcm. :) If this is a card you own, please just wrap it up and put it in the post to Cameron so that he has a chance to see what is going on. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm and rvplayer
Hello-
This is a second try at this. I updating my kernel to current as
of September 12 1999 and have been consistently able to panic my
machine when attempting to use real audio (rvplayer5 under linux
compatibility) The panic is in feeder.c of the newpcm device with
$FreeBSD: src/sys/dev/pcm/feeder.c,v 1.3 1999/09/04 17:08:30 cg Exp$
The hardware is a Crystal CS4236B:
pcm0: CS4236B at port 0x530-0x533,0x388-0x38b,0x220-0x22f irq 5 drq 0,1 on isa0
Error message is:
panic: feed_root: count == 0
Bactrace:
(kgdb) bt
#0 boot (howto=260) at ../../kern/kern_shutdown.c:281
#1 0xc013008d in panic (fmt=0xc01ea614 "from debugger")
at ../../kern/kern_shutdown.c:531
#2 0xc01194c5 in db_panic (addr=-1071896353, have_addr=0, count=-1,
modif=0xc7cdbc3c "") at ../../ddb/db_command.c:433
#3 0xc0119465 in db_command (last_cmdp=0xc020fae8, cmd_table=0xc020f948,
aux_cmd_tablep=0xc02288d4) at ../../ddb/db_command.c:333
#4 0xc011952a in db_command_loop () at ../../ddb/db_command.c:455
#5 0xc011b5af in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71
#6 0xc01c269c in kdb_trap (type=3, code=0, regs=0xc7cdbd30)
at ../../i386/i386/db_interface.c:157
#7 0xc01cda58 in trap (frame={tf_fs = -1060569072, tf_es = 16,
tf_ds = -1061158896, tf_edi = -942817540, tf_esi = 256,
tf_ebp = -942817928, tf_isp = -942817956, tf_ebx = -1071659632,
tf_edx = -1071635441, tf_ecx = 0, tf_eax = 18, tf_trapno = 3,
tf_err = 0, tf_eip = -1071896353, tf_cs = 8, tf_eflags = 598,
tf_esp = -1071635457, tf_ss = -1071721021}) at ../../i386/i386/trap.c:534
#8 0xc01c28df in Debugger (msg=0xc01ed5c3 "panic") at machine/cpufunc.h:64
#9 0xc0130084 in panic (fmt=0xc01fc590 "feed_root: count == 0")
at ../../kern/kern_shutdown.c:529
#10 0xc01a9501 in feed_root (feeder=0xc021d600, buffer=0xc6d34efe "\025\r",
count=0, stream=0xc7cdbefc) at ../../dev/pcm/feeder.c:112
#11 0xc01a8afc in chn_write (c=0xc0a4da00, buf=0xc7cdbefc)
at ../../dev/pcm/channel.c:286
#12 0xc01a7bec in dsp_write (d=0xc0682400, chan=0, buf=0xc7cdbefc, flag=17)
at ../../dev/pcm/dsp.c:187
#13 0xc01a7099 in sndwrite (i_dev=0xc0b6f100, buf=0xc7cdbefc, flag=17)
at ../../dev/pcm/sound.c:310
#14 0xc0163ca4 in spec_write (ap=0xc7cdbeb4)
at ../../miscfs/specfs/spec_vnops.c:369
#15 0xc0195d3c in ufsspec_write (ap=0xc7cdbeb4)
at ../../ufs/ufs/ufs_vnops.c:1858
#16 0xc0196251 in ufs_vnoperatespec (ap=0xc7cdbeb4)
at ../../ufs/ufs/ufs_vnops.c:2313
#17 0xc015df1e in vn_write (fp=0xc0c91100, uio=0xc7cdbefc, cred=0xc0c04e00,
flags=0) at vnode_if.h:331
#18 0xc013ccd0 in dofilewrite (p=0xc74e4b80, fp=0xc0c91100, fd=6,
buf=0x81d78c8, nbyte=132, offset=-1, flags=0)
at ../../kern/sys_generic.c:363
#19 0xc013cbdf in write (p=0xc74e4b80, uap=0xc7cdbf80)
at ../../kern/sys_generic.c:298
#20 0xc01ce26a in syscall (frame={tf_fs = 135921711, tf_es = -1078001617,
tf_ds = -1078001617, tf_edi = 135922760, tf_esi = -1077947048,
tf_ebp = -1077947152, tf_isp = -942817324, tf_ebx = 6, tf_edx = 132,
tf_ecx = 136149192, tf_eax = 4, tf_trapno = 22, tf_err = 2,
tf_eip = 674069812, tf_cs = 31, tf_eflags = 582, tf_esp = -1077947156,
tf_ss = 47}) at ../../i386/i386/trap.c:1056
#21 0xc01c2f96 in Xint0x80_syscall ()
#22 0x80f3b44 in ?? ()
#23 0x80f2e40 in ?? ()
#24 0x80ef1cd in ?? ()
#25 0x80d79f0 in ?? ()
#26 0x80d7709 in ?? ()
#27 0x80d5f5c in ?? ()
#28 0x80cbf2d in ?? ()
#29 0x80cafb7 in ?? ()
#30 0x807ee36 in ?? ()
#31 0x807d230 in ?? ()
#32 0x8094ccd in ?? ()
#33 0x80797b4 in ?? ()
#34 0x8076fb8 in ?? ()
#35 0x8076abb in ?? ()
(kgdb)
--
---
Sean O'ConnellEmail: [EMAIL PROTECTED]
Institute of Statistics and Decision Sciences Phone: (919) 684-5419
Duke University Fax: (919) 684-8594
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: newpcm and Vibra16X
On 12 Sep, Dag-Erling Smorgrav wrote: What's the verdict on newpcm and Vibra16X? Has anyone had any luck in finding out why it doesn't work, or how to make it work? Mine won't make any sound at all (except for the usual noise) no matter what I do - play mp3s, cat my kernel into /dev/audio0, whatever. Kernel config, I havo no problems with it (but it's more a Vibra16C). (90) root@ttyp2 # pnpinfo -l Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL0070 (0x70008c0e), Serial Number 0x PnP Version 1.0, Vendor Version 16 Device Description: Creative ViBRA16C PnP Logical Device ID: CTL0001 0x01008c0e #0 Device Description: Audio pcm0: Vibra16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on is a0 controller pnp0 device pcm0 Bye, Alexander. -- The boat sank. Get over it. http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm and Vibra16X
What's the verdict on newpcm and Vibra16X? Has anyone had any luck in finding out why it doesn't work, or how to make it work? Mine won't make any sound at all (except for the usual noise) no matter what I do - play mp3s, cat my kernel into /dev/audio0, whatever. Kernel config, dmesg.boot and pnpinfo output are included below. If you want a more verbose dmesg.boot, say the word, but I'd rather not boot this box unless I really must. DES (wants his music back...) -- Dag-Erling Smorgrav - [EMAIL PROTECTED] # Kernel configuration for des.follo.net machine i386 cpu I586_CPU cpu I686_CPU ident DES maxusers32 makeoptions DEBUG=-g options AUTO_EOI_1 options AUTO_EOI_2 options COMPAT_43 options FFS options FFS_ROOT options ICMP_BANDLIM options INCLUDE_CONFIG_FILE options INET options IPFIREWALL options IPFIREWALL_VERBOSE options KTRACE options NMBCLUSTERS=8192 options PROCFS options SOFTUPDATES options SYSVMSG options SYSVSEM options SYSVSHM options TCP_DROP_SYNFIN options TCP_RESTRICT_RST options UCONSOLE options USERCONFIG options VESA options VISUAL_USERCONFIG config kernel controller isa0 controller pci0 controller pnp0 device npx0at nexus? port IO_NPX irq 13 device apm0at isa? disable device pcm0 controller fdc0at isa? port IO_FD1 irq 6 drq 2 diskfd0 at fdc0 drive 0 controller wdc0at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff diskwd0 at wdc0 drive 0 controller wdc1at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff diskwd2 at wdc1 drive 0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? conflicts pseudo-device splash device sc0 at isa? options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso options MSGBUF_SIZE=32768 options SC_HISTORY_SIZE=1024 device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device ppc0at isa? port? irq 7 controller ppbus0 device lpt0at ppbus? device plip0 at ppbus? device ppi0at ppbus? controller miibus0 device xl0 pseudo-device loop pseudo-device ether pseudo-device tun 4 pseudo-device bpf 4 pseudo-device pty 64 pseudo-device vn 4 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 #12: Sat Sep 11 11:02:43 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/DES Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 134201344 (131056K bytes) avail memory = 127094784 (124116K bytes) Preloaded elf kernel "kernel" at 0xc02c1000. Preloaded splash_image_data "/boot/splash.pcx" at 0xc02c109c. Preloaded elf module "splash_pcx.ko" at 0xc02c10ec. VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc0238de2 (122) VESA: Matrox Graphics Inc. npx0: math processor on motherboard npx0: INT 16 interface pcib0: AcerLabs M1541 (Aladdin-V) PCI host bridge on motherboard pci0: PCI bus on pcib0 pcib1: AcerLabs M5243 PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: Matrox model 0521 graphics accelerator irq 11 at device 0.0 on pci1 chip1: AcerLabs M15x3 Power Management Unit at device 3.0 on pci0 isab0: AcerLabs M1533 portable PCI-ISA bridge at device 7.0 on pci0 devclass_alloc_unit: apm0 already exists, using next available unit number isa0: ISA bus on isab0 xl0: 3Com 3c900-COMBO Etherlink XL irq 12 at device 11.0 on pci0 xl0: Ethernet address: 00:60:08:cf:a8:e4 xl0: selecting 10baseT transceiver, half duplex ide_pci0: Acer Aladdin IV/V (M5229) Bus-master IDE controller irq 0 at device 15.0 on pci0 apm1: not probed (disabled) fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): IBM-DTTA-371010, DMA, 32-bit, multi-block-16 wd0: 9641MB (19746720 sectors), 19590 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f
Re: Yamaha OPL-SA2 newpcm: recognized but no sound
On Sat, 11 Sep 1999, Vladimir Kushnir wrote: Hi, Since a newpcm/new PnP code commitment I'm desperately trying to get sound out of my soundcard (Yamaha Sound Origins, OPL3-SA2 ISA pnp card). It is recognized (see dmesg output below), seems to get right resources - but no sound at all. It used to work under VoxWare as css device friends, but does not want to anymore either :-( I added some code to the mss driver to implement more mixer functionality for the yamaha but I wasn't able to test it properly since the sound hardware on my laptop seems to be wired up a bit differently from 'normal' opl3-sa2 cards. Can you check with e.g. aumix or kmix to see if any of the mixer controls affect this? -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM and Quake :)
I am having a few problems with newpcm. I often play a whole bunch of Sesame Street AVIs to keep the 1 and 3 year olds happy while I read email. I usually play them like so (straight from the CD-ROM): foreach blah ( /cdrom/letters/tv/*.avi ) xanim -Zr +Ze +Av`mixer | grep pcm | cut -d: -f2` $blah /dev/null end This worked fine with the old sound drivers but now I find that I have to put in a 1 second sleep after xanim or the sound will usually stop completely after the first AVI. I am also now getting the following messages on the console: "dsp sync" I get 4 of these at the start of each invocation of xanim and then I get 1 at the end of each invocation of xanim. When the sound has stopped completely I have to reboot to get it back. My -CURRENT is about 3 days old. (9/9/99 my time which is UTC +9.5 hours) elf make world started on Thu Sep 9 09:29:09 CST 1999 elf make world completed on Thu Sep 9 11:01:23 CST 1999 I have a PnP SB16 and "device pcm0" in my kernel (along with "controller pnp0") of course. The most recently updated file in /usr/src/sys/dev/pcm for me is channel.c at version 1.3 if thats usefull. On Fri, 10 Sep 1999, Daniel O'Connor wrote: Hi, I am trying NewPCM on -current with an AWE64. It works fine for normal sound apps like esd, splay etc etc.. but Quake 1 2 which use the DMA buffers to play their sound. It is allowed to do this (the ioctl is supported), but it stutters very badly. Its a bit hard to explain :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum -- /===\ | Work: [EMAIL PROTECTED] | Home: [EMAIL PROTECTED] | \===/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM and Quake :)
On Fri, 10 Sep 1999, Daniel O'Connor wrote: On 10-Sep-99 Mike Muir wrote: I also get this, on an SB32-PNP, with the pcm0 device (setup for pnp) I havnt tried q3atest on the sb0 stuff though.. I might do this weekend. Ahh.. I've only tried Q1 2, and they both get the problem, but work fine using sb0 and friends. The mmap support is fairly new and hasn't been tested too widely. I suggest you work with Cameron to find out what is happening. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Stuttering mtv with newpcm es1370 card
On Thu, 9 Sep 1999, Chris Piazza wrote: Hi, Earlier today I was trying to watch a short mpeg and found out that it's impossible with newpcm. The sound (and picture) stutters constantly. It works with a kernel from August, 31 (oldpcm). Anyone else able to reproduce this or have any ideas? pcm0: AudioPCI ES1370 irq 5 at device 10.0 on pci0 http://www.r33t.org/files/cute.mpg for a laugh. Not just this mpeg has this problem, though. I can't exactly reproduce it, but for the past couple of days with -current, mtvp/mtv just freezes for no apparent reason. This is under both the old snd0 and new pcm driver. Of course NOTHING works with the new pcm driver -- its almost like buffer is filling up and never emptying, I've had it loop through the same small bit of sound continuously until I cat /dev/null /dev/dsp. WM -- The difference between genius and stupidity is that genius has its limits. Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm broke the Esoniq 1371 Driver Hack?
I've been using the Esoniq 1371 Driver from http://www.freebsd.org/~ghelmer/es1371/ (written by Russell Cattelan?) on my 4.0-CURRENT box for a few weeks now. It's just a hack replacement for es1370.c/es1370_reg.h, but it worked fine up until a week ago or so when I presume the newpcm code went into place. It works against my 27AUG99 kernel however. Does anyone here have plans to integrate the ES-1371 patch into the -CURRENT tree? I'm afraid my skills are not in the driver development area. For reference, the old kernel boots up with this info: pcm0: AudioPCI ES1371 irq 11 at device 12.0 on pci0 pcm0: using I/O space register mapping at 0x1080 es1371: codec vendor revision 0 es1371: codec features none es1371: stereo enhancement: no 3D stereo enhancement -- === Thomas Stromberg, Assistant IS Manager / Systems Guru smtp:[EMAIL PROTECTED] Research Triangle Consultants, Inc. http://afterthought.org 919.380.9771 x3210 irc://Mithra@EFnet FreeBSD Contributor / BeOS Dev 18330 === "if you do nothing enough, something's bound to happen.." === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm broke the Esoniq 1371 Driver Hack?
I'm looking at it... It shouldn't be too difficult to get the 1371 working again. I'm going to try and use as much of the newpcm code as I can, notably the ac97 routines. I'm kind of busy right now so it may take a week or two before I get it working again. Hopefully when I'm done it won't be a "hack" and it can be committed. -- Russell Cattelan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM and Quake :)
I get this two, it sounds like its playing at the wrong sampling speed, but none of them (speeds) sound right. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - On Fri, 10 Sep 1999, Daniel O'Connor wrote: Hi, I am trying NewPCM on -current with an AWE64. It works fine for normal sound apps like esd, splay etc etc.. but Quake 1 2 which use the DMA buffers to play their sound. It is allowed to do this (the ioctl is supported), but it stutters very badly. Its a bit hard to explain :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM and Quake :)
I also get this, on an SB32-PNP, with the pcm0 device (setup for pnp) I havnt tried q3atest on the sb0 stuff though.. I might do this weekend. Daniel O'Connor wrote: Hi, I am trying NewPCM on -current with an AWE64. It works fine for normal sound apps like esd, splay etc etc.. but Quake 1 2 which use the DMA buffers to play their sound. It is allowed to do this (the ioctl is supported), but it stutters very badly. Its a bit hard to explain :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM and Quake :)
On 09-Sep-99 Adam Strohl wrote: I get this two, it sounds like its playing at the wrong sampling speed, but none of them (speeds) sound right. I didn't try that.. I was wondering if the DMA buffer switching wasn't done correctly. I'll try and work up a test program which exibits the problem over the weekend. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum PGP signature
Re: VibraX audio broken with newpcm
On Tue, 07 Sep 1999 at 23:19:14 -0700, Jordan K. Hubbard wrote: Using: controller pnp0 devicepcm0 In my kernel and "pnp aware OS" turned both on and off in my BIOS, I get this on probe: pcm0: Vibra16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa I'm having the same problem, however, I get drq 0,1 rather than 1,3 since I have ppc0 using drq 3. It doesn't work if I take ppc0 off drq 3 either. But just catting a .au file to /dev/audio (yep, MAKEDEV snd0 run previously) results in the cat hanging and no sound. Ditto. Playing mp3s seem to start (i.e., CPU usage goes up but then stops), then it just hangs and gqmpeg/mpg123 needs to be killed. Just for comparison, from a kernel of August 29th using: controller pnp0 devicepcm0 at nexus? port ? irq 5 drq 1 flags 0x13 I get this on probe: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0x Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp Vibra16X sn 0x) at 0x220-0x22f irq 5 drq 1 flags 0x13 on isa That was the last working build for me as well. I've since downgraded to 3.3-RC. Here's the probe from 3.3-RC.. Probing for PnP devices: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0x Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp Vibra16X sn 0x) at 0x220-0x22f irq 9 drq 1 flags 0x10 on isa And here's my kernel config.. controller pnp0 device pcm0 at isa ? port? tty irq 9 drq 1 flags 0x10 Which works fine. I think part of the problem I'm having is that newpcm won't find it on it's actual irq, which is 9 instead of 5. -- - Jim Mock - [EMAIL PROTECTED] - systems administrator - ghis.NET - - work: http://www.ghis.net/ - personal: http://www.ghis.net/~jim/ - - FreeBSD 'zine: http://www.freebsdzine.org/ - [EMAIL PROTECTED] - - The FreeBSD Project -- http://www.FreeBSD.org/ - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sb16 not found with newpcm
I thought I'd try kicking sb0 out of my kernel and try pcm for a change, but I cannot get it to work with simply "device pcm0". My sb16 is not pnp, and adding controller pnp0 did not help. With just device pcm0, the kernel mentions nothing of pcm at all. sb0 worked fine with: controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 port 0x0 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 AND pcm does work with: device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 as someone else suggested on the list. pcm0: SoundBlaster 16 4.11 at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 If dmesg from sb0 would help I could get it.. Anything else I could help with in making "device pcm0" work without params? or is that pnp only? Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sb16 not found with newpcm
Adam McDougall wrote: I thought I'd try kicking sb0 out of my kernel and try pcm for a change, but I cannot get it to work with simply "device pcm0". My sb16 is not pnp, and adding controller pnp0 did not help. With just device pcm0, the kernel mentions nothing of pcm at all. sb0 worked fine with: controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 port 0x0 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 AND pcm does work with: device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 as someone else suggested on the list. pcm0: SoundBlaster 16 4.11 at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 If dmesg from sb0 would help I could get it.. Anything else I could help with in making "device pcm0" work without params? or is that pnp only? Why you can't be happy with "device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15" if it works? -Max -- "We believe in the Power and the Might!" (Manowar, 1996) Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: [EMAIL PROTECTED] ICQ: #42290709 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sb16 not found with newpcm
On Wed, 08 Sep 1999 16:53:37 +0300, Maxim Sobolev wrote: Why you can't be happy with "device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15" if it works? I think Adam's just trying to make sure that he hasn't done something silly which is preventing him from using a more graceful configuration than he has to. He hasn't done anything silly, he does have to specify parameters, but it wasn't unreasonable to ask. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sb16 not found with newpcm
pcm0: SoundBlaster 16 4.11 at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 If dmesg from sb0 would help I could get it.. Anything else I could help with in making "device pcm0" work without params? or is that pnp only? Yes, that is for pnp-only. -- we are but packets in the internet of life To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: another newpcm casualty
On Sun, 5 Sep 1999, David Scheidt wrote: On Sun, 5 Sep 1999, Doug Rabson wrote: On Sun, 5 Sep 1999, David Scheidt wrote: Yesterday's -current fails to find my soundcard. It's an Opti chipset thing that worked fine (for a $12 soundcard...) with the old driver. What is decent soundcard that works with the new driver?pnpinfo and dmesg snippet for the thing: Try this patch: The card is now found, but when I try to use it, I get hundreds and hundreds of messages like Sep 5 19:09:33 tumbolia /kernel: AD_WAIT_INIT FAILED 201 0xff in /var/log/messages followed by Sep 5 19:09:33 tumbolia /kernel: mss: Auto calibration timed out(1). So the patch didn't change the behaviour at all? -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
