Re: current status of pcm ??
I'm not running a recent current on my TP600E (it's pre 4.0-RELEASE). Sound works on this snapshot (4.0-2314-CURRENT). The relavent config bits... options PNPBIOS device pcm0 (notice no bridge drivers (like sbc0)) dmesg output ... unknown6: PNP0400 at port 0x3bc-0x3bf irq 7 on isa0 unknown: PNP0501 can't assign resources pcm0: CS423x-PCI at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq 1,0 on isa0 unknown7: CSC0110 at port 0x538-0x53f on isa0 unknown8: CSC0101 at port 0x200-0x207 on isa0 ... I did have to do a bios upgrade back in November to get the PNPBIOS options to play nice with the hardware, (also had to turn off the fast boot option, (hold down F1 while powering on to get the bios screen)). On Mon, 24 Apr 2000, Kelly Yancey wrote: On Mon, 24 Apr 2000, Kent Hauser wrote: Hi all, I've been unable to get audio (mp3 cdplay) to work on my desktop with a SBLive card or on my laptop (TP 600E). I would *really* like to have IPSec and a working audio cd player on my laptop. I this supposed to work, or am I swimming upstream. Thanks all. Kent Search the mailing list archives for "emu10k1" and you'll find a HOWTO for using the (experimental) emu10k1 drivers, which provide support for the SBLive card and others, with 4.0. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ 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
Errors from the ata disk driver
I've got a striped vinum partition that is occasionally going stale when I get spurrious errors from the ata driver. I can setstate the drives and the volume back up and an fsck of the partition doesn't show any obvious corruption. What do these errors indicate? ad5: status=51 error=84 ad_interrupt: hard error vinum0.p0.s3: fatal read I/O error ad6: status=51 error=84 ad_interrupt: hard error vinum0.p0.s4: fatal read I/O error These drives are hanging off this controller; ata-pci1: Promise Ultra/33 IDE controller irq 9 at device 9.0 on pci0 ata-pci1: Busmastering DMA supported Thanks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Errors from the ata disk driver
Will the backdown to PIO mode be permanent till the next reboot of the machine, or will the driver be able to attempt to return to DMA mode after a timeout period. I'm only seeing these errors under really heavy disk activity (mutlitple nfs readers and writers plus rsync/mirror jobs to the vinum volume in question). On the vinum front, does vinum have the ability to retry writing a block (or whatever the correct abstration is) to the same device if an error like this comes up from the underlying device? Thanks, keep up the great work (Yes, I know I should be using scsi for something like this, but the price of a 200GB raid0 unit built out of IDE equipment compared to the same built out of SCSI hardware is quite shocking. Especially for a non-mission critical role.) On Sat, 11 Dec 1999, Andrew Gallatin wrote: These are UDMA CRC errors. Whatever you do, DO NOT upgrade to a recent current without reading the ata driver's commit logs very carefully. The ata-driver has recently grown recovery code where it will try to back down to PIO mode to fetch such blocks. As recently as last week, the ata driver would lock a machine solid (unpingable, reset or power-cycle required) when attempting to back down to PIO mode when the drive in question was attached to a Promise Ultra controller. Soren knows about the problem is going to fix it. -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email:[EMAIL PROTECTED] Department of Computer SciencePhone: (919) 660-6590 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PNPBIOS vs cs423B codec
Managed to get the sound stuff working on this thinkpad 600e, for anyone who cares... Had to update to the most recent bios, and made sure "quick boot" was disabled (hold down F1 while powering on to get into bios). I removed the "csa0" device from the kernel config, despite having a CS4610 probed during boot. Also set up a pcm0 config line of the sort... device pcm0 at isa? port ? irq 5 drq 1 flags 0x10 % cat /dev/sndstat FreeBSD Audio Driver (newpcm) Dec 9 1999 17:28:08 Installed devices: pcm0: SoundBlaster Pro 3.2 at io 0x220 irq 5 drq 0:1 (1/1 channels duplex) the relevant PNP boot messages without pcm enabled... CSC0100: adding io range 0x530-0x537, size=0x8, align=0 CSC0100: adding io range 0x388-0x38b, size=0x4, align=0 CSC0100: adding io range 0x220-0x233, size=0x14, align=0x20 CSC0100: adding irq mask 0x20 CSC0100: adding dma mask 0x2 CSC0100: adding dma mask 0x1 CSC0100: start dependant pnpbios: handle 14 device ID CSC0100 (0001630e) ... unknown6: CSC0100 at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq 1,0 on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PNPBIOS vs cs423B codec
I've been trying to get my laptop sound to work with recent kernels. It's a thinkpad 600e with a cs4610 on board. I contacted the author of the newpcm code and he mentioned that instead of using the ac97 codec it most likely uses a cs423x in association with the cs4610. This actually jives with behavior I'd seen under openbsd and the older pnp code, where a sound blaster was probed under freebsd, while openbsd and win95 both see a window sound system lookalike. I'll note that I've never been able to get anything but static out of the older freebsd and openbsd sound drivers on this machine. Anyways, the boot messages indicate that the pnp code for some reason isn't getting any usefull info out of the 423x part (other than the midi or synth part) on bootup (most of the other hardware looks like it correctly responds to th PNPBIOS stuff)... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 . Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0x, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0x, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0x, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0x, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 . Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0x, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0x, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0x, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0x, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found:
PNPBIOS vs cs423B codec (fwd)
I've edited the boot messages from my previous mail (the result of fighting with pine over a slow link with a little too much coffee thrown in), sorry to clog up the lines... (fwd) I've been trying to get my laptop sound to work with recent kernels. It's a thinkpad 600e with a cs4610 on board. I contacted the author of the newpcm code and he mentioned that instead of using the ac97 codec it most likely uses a cs423x in association with the cs4610. This actually jives with behavior I'd seen under openbsd and the older pnp code, where a sound blaster was probed under freebsd, while openbsd and win95 both see a window sound system lookalike. I'll note that I've never been able to get anything but static out of the older freebsd and openbsd sound drivers on this machine. Anyways, the boot messages indicate that the pnp code for some reason isn't getting any usefull info out of the 423x part (other than the midi or synth part) on bootup (most of the other hardware looks like it correctly responds to th PNPBIOS stuff)... 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 ... csa0: Crystal Semiconductor CS4610/4611 Audio accelerator irq 11 at device 6.0 on pci0 device_probe_and_attach: csa0 attach returned 6 ... pnpbios: handle 13 device ID PNP0501 (0105d041) CSC0100: adding io range 0-0x, size=0, align=0 CSC0100: adding io range 0-0x, size=0, align=0 CSC0100: adding io range 0-0x, size=0, align=0x20 CSC0100: adding irq mask CSC0100: adding dma mask 00 CSC0100: adding dma mask 00 CSC0100: start dependant pnpbios: handle 14 device ID CSC0100 (0001630e) CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 CSC0110: start dependant pnpbios: handle 15 device ID CSC0110 (1001630e) CSC0101: adding io range 0-0x, size=0, align=0 CSC0101: start dependant pnpbios: handle 16 device ID CSC0101 (0101630e) CSC0103: adding io range 0-0x, size=0, align=0x10 CSC0103: adding irq mask CSC0103: start dependant pnpbios: handle 17 device ID CSC0103 (0301630e) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
