Re: Fixed sound card problem.
+[ Arthur H. Johnson II ]- | I fixed the sound card problem I was having. I just commented out the pnp | driver. I know I will run into problems later if I ever get pnp devices, | but its a temporary fix. Pcm doesn't work for me anymore with or without a pnp controller defined. It's not even probed. I've got a genuine Sound Blaster 16 with on board SCSI (unused). -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]|Specialist To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fixed sound card problem.
+[ Doug Rabson ]- | On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote: | | +[ Arthur H. Johnson II ]- | | I fixed the sound card problem I was having. I just commented out the pnp | | driver. I know I will run into problems later if I ever get pnp devices, | | but its a temporary fix. | | Pcm doesn't work for me anymore with or without a pnp controller defined. | It's not even probed. | | I've got a genuine Sound Blaster 16 with on board SCSI (unused). | | Can I see your kernel config and dmesg lines both from an old (working) | kernel and from the new kernel. I would have attached the dmesg originally but it didn't even show the pcm probe at all... and there was nothing strange in it (I did look for errors). My current kernel has got voxware in unfortunately... and I'm currently building world (again) d8/ I can rebuild a kernel afterwards with pcm compiled in and send that, but, that won't be for a few hours yet... It's 1:30 am here right now and my kids will be waking me up for fathers day nice and early so I can't pull a dawner tonight. Here's my kernel config and dmesg from a working kernel. The changes I've made other than to comment out the pnp controller, is to add the options CPU_FASTER_5X86_FPU I'm going to remove that next kernel build as well to see if that makes a difference. I'll forward you a non-working dmesg tomorrow my time I guess unless something comes to light before then. -[pcm working]--- FreeBSD 4.0-CURRENT #39: Fri Aug 13 18:41:33 GMT 1999 [EMAIL PROTECTED]:/export/src/sys/compile/work.on Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199681339 Hz CPU: Pentium/P55C (199.68-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 67108864 (65536K bytes) avail memory = 61059072 (59628K bytes) Preloaded elf kernel "kernel" at 0xc03b4000. Preloaded splash_image_data "/newlogo.bmp" at 0xc03b409c. Preloaded elf module "vesa.ko" at 0xc03b40e8. Preloaded elf module "splash_bmp.ko" at 0xc03b4184. Intel Pentium detected, installing workaround for F00F bug VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc00c0d16 (cd16) VESA: S3 Incorporated. ViRGE /DX /GX Probing for PnP devices: npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 ide_pci0: Intel PIIX4 Bus-master IDE controller at device 7.1 on pci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller irq 0 at device 7.2 on pci0 uhci0: could not map ports device_probe_and_attach: uhci0 attach returned 6 chip1: Intel 82371AB Power management controller at device 7.3 on pci0 vga-pci0: S3 ViRGE DX/GX graphics accelerator irq 11 at device 10.0 on pci0 ahc0: Adaptec 2940 Ultra SCSI adapter irq 10 at device 11.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs isa0: ISA bus on motherboard ed0 at port 0x300-0x31f irq 12 on isa0 ed0: address 00:00:01:19:99:84, type NE2000 (16 bit) 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 4 virtual consoles, flags=0x200 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (atapi): ASUS CD-S400/V1.10, removable, accel, dma, iordy wcd0: drive speed 0 - 6875KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA, packet track wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked fdc0: NEC 765 or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fd0: 1440-KB 3.5" drive on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A pcm0 at port 0x220 irq 5 drq 1 flags 0x15 on isa0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver joy0 at port 0x201 on isa0 joy0: joystick ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode 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 lppps0: Pulse per second Timing Interface on ppbus 0 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default ds0 XXX: driver didn't set ifq_maxlen Waiting 2 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 2 lun 0 sa0: SONY SDT-5000 3.30 Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 8) changing root device to da0s1a da1 at ahc0 bus 0 target 3 lun 0 da1: IBM DORS-32160W !# WA1A Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz,
Re: Fixed sound card problem.
Crap, the old kernel is gone. I was going to save the old working kernel but its gone now. I attached the old config file thou. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Sat, 4 Sep 1999, Doug Rabson wrote: On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote: +[ Arthur H. Johnson II ]- | I fixed the sound card problem I was having. I just commented out the pnp | driver. I know I will run into problems later if I ever get pnp devices, | but its a temporary fix. Pcm doesn't work for me anymore with or without a pnp controller defined. It's not even probed. I've got a genuine Sound Blaster 16 with on board SCSI (unused). Can I see your kernel config and dmesg lines both from an old (working) kernel and from the new kernel. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd.Phone: +44 181 442 9037 # # ARTHUR -- Customized kernel for arthur (starwars.linuxberg.org) # # $Id: ARTHUR,v 1.182 1999/08/15 09:54:56 phk Exp $ machine i386 cpu I586_CPU ident ARTHUR maxusers32 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options MATH_EMULATE#Support for x87 emulation options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT#MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores # To make an SMP kernel, the next two are needed #optionsSMP # Symmetric MultiProcessor Kernel #optionsAPIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #optionsNCPU=2 # number of CPUs #optionsNBUS=4 # number of busses #optionsNAPIC=1 # number of IO APICs #optionsNINTR=24# number of INTs controller isa0 controller pnp0# PnP support for ISA controller eisa0 controller pci0 # Floppy drives controller fdc0at isa? port IO_FD1 irq 6 drq 2 diskfd0 at fdc0 drive 0 diskfd1 at fdc0 drive 1 # IDE controller and disks controller wdc0at isa? port IO_WD1 irq 14 diskwd0 at wdc0 drive 0 diskwd1 at wdc0 drive 1 controller wdc1at isa? port IO_WD2 irq 15 diskwd2 at wdc1 drive 0 diskwd3 at wdc1 drive 1 # ATAPI devices on wdc? device wcd0#IDE CD-ROM device wfd0#IDE Floppy (e.g. LS-120) device wst0#IDE Tape (e.g. Travan) # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0# NCR/Symbios Logic #controller ahb0# EISA AHA1742 family #controller ahc0# AHA2940 and onboard AIC7xxx devices #controller isp0# Qlogic family #controller dpt0 # DPT Smartcache - See LINT for options! #controller adv0at isa? port ? irq ? #controller adw0 #controller bt0 at isa? port ? irq ? #controller aha0at isa? port ? irq ? # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. #controller scbus0 # SCSI bus (required) #device da0 # Direct Access (disks) #device sa0 # Sequential Access (tape etc) #device cd0 # CD #device pass0 # Passthrough device (direct SCSI
Re: Fixed sound card problem.
Done, and I have pci.c 1.117. When did it get broken then fixed? I ran make update and make world just thursday. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Sat, 4 Sep 1999, Doug Rabson wrote: On Sun, 5 Sep 1999, Andrew Kenneth Milton wrote: +[ Doug Rabson ]- | On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote: | | +[ Arthur H. Johnson II ]- | | I fixed the sound card problem I was having. I just commented out the pnp | | driver. I know I will run into problems later if I ever get pnp devices, | | but its a temporary fix. | | Pcm doesn't work for me anymore with or without a pnp controller defined. | It's not even probed. | | I've got a genuine Sound Blaster 16 with on board SCSI (unused). | | Can I see your kernel config and dmesg lines both from an old (working) | kernel and from the new kernel. I would have attached the dmesg originally but it didn't even show the pcm probe at all... and there was nothing strange in it (I did look for errors). My current kernel has got voxware in unfortunately... and I'm currently building world (again) d8/ I can rebuild a kernel afterwards with pcm compiled in and send that, but, that won't be for a few hours yet... It's 1:30 am here right now and my kids will be waking me up for fathers day nice and early so I can't pull a dawner tonight. Here's my kernel config and dmesg from a working kernel. The changes I've made other than to comment out the pnp controller, is to add the options CPU_FASTER_5X86_FPU I'm going to remove that next kernel build as well to see if that makes a difference. I'll forward you a non-working dmesg tomorrow my time I guess unless something comes to light before then. Make sure that you have the latest version of pci.c before you test again. Also, when you change back to using pnp, change the pcm declaration from: device pcm0 at isa? ... to device pcm0 -- 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: Fixed sound card problem.
After i got 1.117 everything went back to normal. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Sat, 4 Sep 1999, Doug Rabson wrote: On Sat, 4 Sep 1999, Arthur H. Johnson II wrote: Done, and I have pci.c 1.117. When did it get broken then fixed? I ran make update and make world just thursday. The bug in pci.c 1.116 only affected pnp cards so perhaps you have another problem. If so, you need to try to work with Cameron Grant ([EMAIL PROTECTED]) who is the main force behind the new sound driver. -- 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
Fixed sound card problem.
I fixed the sound card problem I was having. I just commented out the pnp driver. I know I will run into problems later if I ever get pnp devices, but its a temporary fix. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fixed sound card problem.
I tried using snd1. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Ollivier Robert wrote: According to Arthur H. Johnson II: I fixed the sound card problem I was having. I just commented out the pnp driver. I know I will run into problems later if I ever get pnp devices, but its a temporary fix. Something to remember: if you have both pcm0 and pnp, then it will be probed as pcm0 BUT the device you must use is pcm1. That means that you need to do "sh MAKEDEV snd1" and not "sh MAKEDEV snd0". pcm0: MAKEDEV snd0 pcm0 + pnp: MAKEDEV snd1 Luigi gave a good explanation a while when he wrote pcm but I don't remember it now :) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 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: Fixed sound card problem.
On Fri, 3 Sep 1999, Ollivier Robert wrote: According to Arthur H. Johnson II: I fixed the sound card problem I was having. I just commented out the pnp driver. I know I will run into problems later if I ever get pnp devices, but its a temporary fix. Something to remember: if you have both pcm0 and pnp, then it will be probed as pcm0 BUT the device you must use is pcm1. That means that you need to do "sh MAKEDEV snd1" and not "sh MAKEDEV snd0". pcm0: MAKEDEV snd0 pcm0 + pnp: MAKEDEV snd1 Luigi gave a good explanation a while when he wrote pcm but I don't remember it now :) This is no longer necessary (in fact it causes much confusion for the driver). The correct declaration for a pnp soundcard is 'device pcm0'. -- 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: Fixed sound card problem.
On Fri, Sep 03, 1999 at 09:08:59PM +0100, Doug Rabson wrote: This is no longer necessary (in fact it causes much confusion for the driver). The correct declaration for a pnp soundcard is 'device pcm0'. How do you set flags for particular cards, now? I used to have to use the flags option to tell the pcm driver which second DMA channel to use (5: flags 0x15). I haven't had the opportunity to do any full-duplex stuff since that change, so I don't know whether it has figured it out for itself or not. I assume that it has? The boot message now says: pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa So, is 0 a useful 2nd DMA channel, or does the driver make do with one channel now? This is on a -stable system cvsupped on 2nd September. -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fixed sound card problem.
"Andrew Reilly" wrote: On Fri, Sep 03, 1999 at 09:08:59PM +0100, Doug Rabson wrote: This is no longer necessary (in fact it causes much confusion for the driver). The correct declaration for a pnp soundcard is 'device pcm0'. How do you set flags for particular cards, now? I used to have to use the flags option to tell the pcm driver which second DMA channel to use (5: flags 0x15). I haven't had the opportunity to do any full-duplex stuff since that change, so I don't know whether it has figured it out for itself or not. I assume that it has? The boot message now says: pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa So, is 0 a useful 2nd DMA channel, or does the driver make do with one channel now? I'm not sure, dma 0 works here, but it's specifically detected automatically (without flags) and is reported as such. # dmesg | grep pcm pcm0: AudioPCI ES1370 irq 11 at device 10.0 on pci0 pcm1: ESS1868 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 \ on isa0 On another box, I see: # dmesg | grep pcm pcm0: CS4236 at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 \ on isa0 I suspect this is the same device you have. Are you sure you are up to date with your source? The probe message looks a bit odd and looks more like the old pnp messages. Did you rerun config and do a 'make depend'? Also, the new pnp/pcm code will start at pcm0, rather than pcm1 unless there is a pcm0 already in use. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
