CS4232 with pcm driver returns device_probe_and_attach: pcm0 attach returned 6
this is 4.3-STABLE, cvsup'd last week, on a Toshiba Tecra 720cdt. Dmesg shows pcm detecting the card at 0x530 (BIOS says the card is at 0x534). Setting port 0x534 in the kernel config results in nothing being detected at all. Using the sbc0 driver in conjuntion with pcm, with the same args will result in a semi-functional (only 8-bit, 22KHz) sound output. I have had this card working at full capacity under Linux, so the hardware is functional to that extent. Any suggestions? -- [EMAIL PROTECTED] Graham Dunn || ||| | ||| | | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: CS4232 with pcm driver returns device_probe_and_attach: pcm0attach returned 6
On Thu, 7 Jun 2001, Graham Dunn wrote: this is 4.3-STABLE, cvsup'd last week, on a Toshiba Tecra 720cdt. Dmesg shows pcm detecting the card at 0x530 (BIOS says the card is at 0x534). Setting port 0x534 in the kernel config results in nothing being detected at all. Please send the output of 'pciconf -lv' and 'pnpinfo'. It might be there's some glue which isn't supported by newpcm. -- +---+-+ |George Reid| FreeBSD Committer | | +44 7740 197460 | [EMAIL PROTECTED] | +---+-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: CS4232 with pcm driver returns device_probe_and_attach: pcm0 attach returned 6
Dmesg shows pcm detecting the card at 0x530 (BIOS says the card is at 0x534). Setting port 0x534 in the kernel config results in nothing being detected at all. some details (boot -v dmesg, pnpinfo, relevant bits of kernel config) would be nice... -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: CS4232 with pcm driver returns device_probe_and_attach: pcm0 attach returned 6
If I specify device pcm0 at isa? port 0x534 irq 7 I get: mss_detect, busy still set (0xff) pcm0 failed to probe at port 0x534-0x53b irq 7 on isa0 with device pcm0 at isa? port? irq? drq1 flags 0x15 [snip] avail memory = 77828096 (76004K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f8dc0 bios32: Entry = 0xfe95b (c00fe95b) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xde53 pnpbios: Bad PnP BIOS data checksum Other BIOS signatures found: ACPI: Preloaded elf kernel kernel at 0xc03c7000. Preloaded userconfig_script /boot/kernel.conf at 0xc03c70a8. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1):mode 1 addr port (0x0cf8) is 0x80001850 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06011179) apm0: APM BIOS on motherboard apm: found APM BIOS v1.1, connected at v1.1 npx0: math processor on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 131233595 bytes/sec bzero() bandwidth = 195045835 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=06011179) pcib0: Host to PCI bridge on motherboard found- vendor=0x1179, dev=0x0601, revid=0x11 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x102c, dev=0x00e0, revid=0x04 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base fe00, size 24 pci0: PCI bus on pcib0 pci0: Chips Technologies 65550 SVGA controller (vendor=0x102c, dev=0x00e0) at 4.0 isa0: ISA bus on motherboard Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: NEC 765 or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x ata0: mask=03 status0=50 status1=00 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=00 b=00 ata0: mask=03 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=01 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x ata1: mask=03 status0=50 status1=00 ata1: mask=03 ostat0=50 ostat2=00 ata1-master: ATAPI probe a=14 b=eb ata1-slave: ATAPI probe a=14 b=eb ata1: mask=03 status0=00 status1=00 ata1: devices=0c ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d psm0: current command byte:0047 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0-00, 2 buttons psm0: config:, flags:, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa 0x2 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 01 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 05 f0 9c 0e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 00 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 01 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 05 f0 9c 0e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 00 00 00 00 00 00 10 0e 00 ff sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) mss_probe: no address given, try 0x530 mss_detect - chip revision 0x0a mss_detect() - Detected CS4232 pcm0: CS4232 at port 0x530-0x537 drq 1 flags 0xa115 on isa0 device_probe_and_attach: pcm0 attach returned 6 pcic0: Intel i82365 at port 0x3e0 iomem 0xd on isa0 pcic0: Polling mode stat is fe stat is f2 pccard0: PC Card bus -- kludge version on pcic0 pccard1: PC Card bus -- kludge version on pcic0 pcic1: not probed (disabled) sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: irq maps: 0x41 0x41 0x41 0x41 sio0: probe failed test(s): 0 1 2 4 6 7 9 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: irq
Re: CS4232 with pcm driver returns device_probe_and_attach: pcm0 attach returned 6
If I specify device pcm0 at isa? port 0x534 irq 7 I get: mss_detect, busy still set (0xff) pcm0 failed to probe at port 0x534-0x53b irq 7 on isa0 with device pcm0 at isa? port? irq? drq1 flags 0x15 You *should* just be able to use the PnP BIOS. However: pnpbios: Bad PnP BIOS data checksum Try ignoring the PnP BIOS checksum error (yes, believe it or not, some people either can't add, or can't be bothered to, and you wonder why PC systems have a reputation for being crap?). /sys/i386/i386/bios.c: 127 } 128 /* If checksum is OK, enable use of the entrypoint */ 129 if (ck == 0) { Change this to if (1) { 130 PnPBIOStable = pt; 131 if (bootverbose) { and just put device pcm in your kernel config, and see how that goes. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pcm driver
On Mon, Sep 25, 2000 at 09:18:38AM +0200, Roman Shterenzon wrote: Quoting Gary Kline [EMAIL PROTECTED]: According to Daniel O'Connor: On 25-Sep-00 Gary Kline wrote: ppi0: Parallel I/O on ppbus0 sbc0: Soundblaster 16 at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 sbc0: alloc_resource device_probe_and_attach: sbc0 attach returned 6 I don't know what the last line means. I just remade snd0... The last line means its busted :) Are you sure you have 'device pcm' in your kernel config _as well_ as sbc0? device pcm device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x15 Should this be pcm0, perhaps? I've exactly the same hardware and had this problem because of irq conflict. The sb is ISA and BIOS assigned IRQ to USB for some unclear reason. I then set IRQ5 to be assigned to Legacy ISA in BIOS and it worked again. The BIOS behavior was quite weird since it worked before. Check if any other devices use irq5. Hope that it helps. It may well help. This m'board is 2+ years old and we probably have dissimilar BIOS setups; I'll see if there is a way to associate irq5 with ISA. ...There is something bizarre going on because in switching my ``muuz'' display panels around there is a several second delay. This is brand new. With 3.X, no problems; with 4.1, there are these weird issues. --For the time being, I've gone back to the older obsolete snd stuff. Haven't tried it again, tho. Tonight... thanks for your input. gary -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pcm driver
On Tue, Sep 26, 2000 at 08:23:04AM +1000, Phil Homewood wrote: Dave Edmondson wrote: I finally got a Sound Blaster 16 non-PnP model working. Both pcm and sbc had to be in the old ISA: pcm0at isa? ... sbc0at isa? ... ...format. After remaking sbc0, it seemed to work fine. Can the `at isa' lines be identical: device pcmat isa? port 0x220 irq 5 drq 1 flags 0x15 device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x15 Like so? gary Mine "works" with just "device pcm" and "device sbc", in the same way that it "works" using the old "at isa?" syntax. However I have a weird problem - an attempt to play any given track will fail about 10% of the time, all I get is static from the speakers. Restarting the play generally works. It sounds to me like maybe something isn't being reset properly before the device is opened. Has anyone seen this behaviour, or is there anything anyone can suggest for tracking this down? I've tried swapping the card, and the symptoms persist. This is under 4.1-STABLE, cvsupped yesterday, and has been happening since 4.0-STABLE as of at least May (when I first installed this box.) pdh@minotaur:~% dmesg | egrep 'sb|pcm' sbc0: Creative ViBRA16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 sbc0: setting card to irq 5, drq 1, 3 pcm0: SB DSP 4.16 (ViBRA16X) on sbc0 pdh@minotaur:~% cat /dev/sndstat FreeBSD Audio Driver (newpcm) Sep 26 2000 07:43:54 Installed devices: pcm0: SB DSP 4.16 (ViBRA16X) at io 0x220 irq 5 drq 1:3 (1p/1r channels duplex) pdh@minotaur:~% Also, I've just noticed that the volume control in xmms has just ceased to have any effect, hmm... -- Phil Homewood [EMAIL PROTECTED] Senior Technician +61 7 3620 1930 Asia Online (Brisbane)http://www.asiaonline.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pcm driver
On Mon, Sep 25, 2000 at 05:44:33PM -0500, Dave Uhring wrote: On Mon, 25 Sep 2000, Phil Homewood wrote: Dave Edmondson wrote: I finally got a Sound Blaster 16 non-PnP model working. Both pcm and sbc had to be in the old ISA: pcm0 at isa? ... sbc0 at isa? ... ...format. After remaking sbc0, it seemed to work fine. [[ ... ]] This topic has been hashed to death previously on this forum. The SB16, SB Vibra16, the Ensoniq 1371-1373 and many other sound cards use *only* device pcm. device pcm is 16 bit sound, device sbc0 is 8 bit sound. I presently have a SB16 installed and am using RealPlayer7 to listen to Beethoven's Emperor Concerto in vivid 16 bit clear stereo. I previously had the SB Vibra 16 and Ensoniq 1373 installed. Using ONLY device pcm, all of them worked perfectly. See the attached kernel config file "dave" and dmesg. Note the kernel build date. It is the same date as cvsup and make buildworld. If sbc1 or pcm1 appear in your dmesg, you have to "sh /dev/MAKEDEV snd1". If sbc0 or pcm0 appear in your dmest, you "sh /dev/MAKEDEV snd0". Trying this now and will let the list know. --At least the word about sound and 4.X is spreading, so there are that many more to help next time. thanks, gary PS: In my other FBSD platform I've got an AWE64 and device pcm seems to have been correct. -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pcm driver
On Mon, 25 Sep 2000, Gary Kline wrote: On Tue, Sep 26, 2000 at 08:23:04AM +1000, Phil Homewood wrote: Dave Edmondson wrote: I finally got a Sound Blaster 16 non-PnP model working. Both pcm and sbc had to be in the old ISA: pcm0 at isa? ... sbc0 at isa? ... ...format. After remaking sbc0, it seemed to work fine. Can the `at isa' lines be identical: device pcmat isa? port 0x220 irq 5 drq 1 flags 0x15 device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x15 Like so? I don't have a Vibra 16 (I do have an ISA AWE64, however), but, FWIW, I have the following in my config file: device pcm device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x15 and it works great, except in vmware. In vmware, I get crackling, crappy sound *except* when playing CDs; however, vmware does not make use of my subwoofer. -- Chris BeHanna Software Engineer (at yourfit.com) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pcm driver
Mr. O'Connor et al: More accurately, the last line would indicate your second DMA channel is set incorrectly. use the 'boot -c' configurator to play with the flags line (I had a similar problem with FreeBSD 3-STABLE and mine works with flags 0x16). If your secondary DMA channel is C, your flags should be (C | 0x10) (that's a bitwise OR). This is from the pcm manpage and it works for me. * Daniel O'Connor ([EMAIL PROTECTED]) [000925 11:47]: I don't know what the last line means. I just remade snd0... The last line means its busted :) -- Hasan Diwan [[EMAIL PROTECTED]] :) Rensselaer Polytechnic Institute Computer Science Department http://hdwork.dhs.org/~hdiwan PGP signature
pcm driver
After more than an hour tracking down a bug in an X program--yes, I should have used gdb immediately, I found it was due to my KERNEL not being set up for sound. I am still using my SB16. Okay, I copied over the below which was in my FreeBSD-3.2 KERNEL file and tried to rebuild. I spotted the heads-up that snd0 was being deprecated in favor of pcm. I don't have any problem replacing this: device snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x3000 ###Pro Audio Spectrum. For Yamaha OPL-2/OPL-3 FM support: device opl0 at isa? port 0x388 with: device pcm but will is work for my ancient SB16?? thanks for any insights here. gary -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message