Re: Sound card troubles
On Mon, 22 Sep 2003 17:02:29 -0700 (PDT) Doug White [EMAIL PROTECTED] wrote: On Mon, 22 Sep 2003, Bruce Mackay wrote: Most BIOSen with PnP support have an option to clear the device config and force a PCI/PnP resource reconfiguration on next boot. snip Laugh, it's actually a toshiba POS. I wish I had realised that the BIOS was so feeble. One of the reasons I'm checking out FreeBSD is so that I can tinker with different stuff. Oh well... Tinkering with BIOS options isn't a feature of most operating systems :) That's too bad... It might solve my problem :) Is this something that FreeBSD team has considered or is considering supporting PnP enforced BIOSes systems? Or am I SOL? There is a PNPBIOS kernel option in -stable you might try, but no guarantees. I wonder if Toshiba has a program floating around to toggle the PnP bit anyway since it would preclude anything but Windows from running on the machine. -- I could try that only problem is that I had to migrate to -current to get my wireless nic card working. I may give it a try just to see if I can get my sound card working though... I have searched for a program that can change settings in the BIOS. The only thing I've found is Toshiba's Hardware Setting Program, but all it basically lets you do is change your bootup order. I'll keep looking though... Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound card troubles
On Sun, 21 Sep 2003 12:56:53 -0700 (PDT) Doug White [EMAIL PROTECTED] wrote: On Sun, 21 Sep 2003, Bruce Mackay wrote: I actually tried hw.pci.allow_unsupported_io_range = 1 to no avail. I've tried building pcm into my kernel, I've tried loading them as modules with no success. I was reading somewhere that I may need hw.pci.enable_io_modes = 1 to use my sound card. However I cannot boot unless I set hw.pci.enable_io_modes = 0. Any ideas on how I can get around this? Or if this will even help... You might check that your BIOS has PnP OS set to No, and try wiping the device configuration. You may just be screwed :( -- snip Yeah the only thing I can change in this stupid BIOS is the time. PnP cannot be turned off through the BIOS apparently. What do you mean by wiping the device configuration? Maybe I'll try doing that anyway and see what happens. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound card troubles
On Mon, 22 Sep 2003, Bruce Mackay wrote: Yeah the only thing I can change in this stupid BIOS is the time. PnP cannot be turned off through the BIOS apparently. What do you mean by wiping the device configuration? Maybe I'll try doing that anyway and see what happens. Is this some dell POS? You might check for a BIOS update. Most BIOSen with PnP support have an option to clear the device config and force a PCI/PnP resource reconfiguration on next boot. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound card troubles
On Mon, 22 Sep 2003 09:27:52 -0700 (PDT) Doug White [EMAIL PROTECTED] wrote: On Mon, 22 Sep 2003, Bruce Mackay wrote: Yeah the only thing I can change in this stupid BIOS is the time. PnP cannot be turned off through the BIOS apparently. What do you mean by wiping the device configuration? Maybe I'll try doing that anyway and see what happens. Is this some dell POS? You might check for a BIOS update. Most BIOSen with PnP support have an option to clear the device config and force a PCI/PnP resource reconfiguration on next boot. snip Laugh, it's actually a toshiba POS. I wish I had realised that the BIOS was so feeble. One of the reasons I'm checking out FreeBSD is so that I can tinker with different stuff. Oh well... Is this something that FreeBSD team has considered or is considering supporting PnP enforced BIOSes systems? Or am I SOL? Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound card troubles
On Mon, 22 Sep 2003, Bruce Mackay wrote: Most BIOSen with PnP support have an option to clear the device config and force a PCI/PnP resource reconfiguration on next boot. snip Laugh, it's actually a toshiba POS. I wish I had realised that the BIOS was so feeble. One of the reasons I'm checking out FreeBSD is so that I can tinker with different stuff. Oh well... Tinkering with BIOS options isn't a feature of most operating systems :) Is this something that FreeBSD team has considered or is considering supporting PnP enforced BIOSes systems? Or am I SOL? There is a PNPBIOS kernel option in -stable you might try, but no guarantees. I wonder if Toshiba has a program floating around to toggle the PnP bit anyway since it would preclude anything but Windows from running on the machine. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound card troubles
On Sat, 20 Sep 2003, Bruce Mackay wrote: Hey all, I get the following hang up when I try booting up, here's the problem area... pcm0: Intel ICH3 (82801CA) at device 31.5 on pci0 pcm0: unable to map IO port space device_probe_and_attach: pcm0 attach returned 6 I'm running a CVSUP -current from Thu Sep 18 12:34:00 EDT 2003, I have a Yamaha YMF753 Codex Chip and it's Sound Blaster Pro compatible card, anyone have any suggestions? Try setting the tunable hw.pci.allow_unsupported_io_range to 1 in loader.conf and booting. Your machine appears to need special consideration; most ICH3 chips don't need this option. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound card troubles
On Sat, 20 Sep 2003 23:07:10 -0700 (PDT) Doug White [EMAIL PROTECTED] wrote: On Sat, 20 Sep 2003, Bruce Mackay wrote: Hey all, I get the following hang up when I try booting up, here's the problem area... pcm0: Intel ICH3 (82801CA) at device 31.5 on pci0 pcm0: unable to map IO port space device_probe_and_attach: pcm0 attach returned 6 I'm running a CVSUP -current from Thu Sep 18 12:34:00 EDT 2003, I have a Yamaha YMF753 Codex Chip and it's Sound Blaster Pro compatible card, anyone have any suggestions? Try setting the tunable hw.pci.allow_unsupported_io_range to 1 in loader.conf and booting. Your machine appears to need special consideration; most ICH3 chips don't need this option. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org snip I actually tried hw.pci.allow_unsupported_io_range = 1 to no avail. I've tried building pcm into my kernel, I've tried loading them as modules with no success. I was reading somewhere that I may need hw.pci.enable_io_modes = 1 to use my sound card. However I cannot boot unless I set hw.pci.enable_io_modes = 0. Any ideas on how I can get around this? Or if this will even help... Thanks, Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound card troubles
On Sun, 21 Sep 2003, Bruce Mackay wrote: I actually tried hw.pci.allow_unsupported_io_range = 1 to no avail. I've tried building pcm into my kernel, I've tried loading them as modules with no success. I was reading somewhere that I may need hw.pci.enable_io_modes = 1 to use my sound card. However I cannot boot unless I set hw.pci.enable_io_modes = 0. Any ideas on how I can get around this? Or if this will even help... You might check that your BIOS has PnP OS set to No, and try wiping the device configuration. You may just be screwed :( -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Sound card troubles
Hey all, I get the following hang up when I try booting up, here's the problem area... pcm0: Intel ICH3 (82801CA) at device 31.5 on pci0 pcm0: unable to map IO port space device_probe_and_attach: pcm0 attach returned 6 I'm running a CVSUP -current from Thu Sep 18 12:34:00 EDT 2003, I have a Yamaha YMF753 Codex Chip and it's Sound Blaster Pro compatible card, anyone have any suggestions? Thanks, Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound card woes
Hello, On Fri, Aug 22, 2003 at 11:30:45AM -0400, Matt Gostick wrote: On Wed, 2003-08-20 at 17:04, Szilveszter Adam wrote: What does 'cat /dev/sndstat' say? # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: SB16 DSP 4.16 (ViBRA16X) at io 0x220 irq 7 drq 0 bufsz 4096d (1p/1r/0v channels duplex default) So it's a Vibra. It seems to be detected mostly ok. cat test.wav /dev/dsp makes a sound... but it isn't exactly what test.wav should sound like. You mean the sound is distorted? The issue is probably some resource conflict. Since you have an SB 16, I'll have to ask: is it ISA? Or ISAPnP? Or PCI? PCI should just work but if it is ISA, you will need some tweaking. It is an ISA card... very old. Should I try and dig up a PCI card, or is it going to fairly 'painless' tweaking? Where should I start tweaking? My previous assumption seems to be reinforced, it is probably a resource conflict. If the card is ISAPnP (I think it is) you could try to extract a correct configuration from it using the pnpinfo command. Do not be very surprised if you will see many possible configs. (My old SB 64 AWE card had at least 6 or something) Pick one that is marked best or similar and check that the kernel uses that. You should also try and avoid IRQ sharing for the slot that the card is in if possible. If the card does not find the proper setting by itself, you may need to use hints. See them in /usr/src/sys/conf/NOTES, like this: hints.sbc.0.at=isa hints.sbc.0.port=0x220 hints.sbc.0.irq=5 hints.sbc.0.drq=1 hints.sbc.0.flags=0x15 Please do not copy these simply, but find the settings that your card supports and use those! If the card is not even ISAPnP, then you need its docs to find the real config. Possibly there is also a DOS program to set them on the card or jumpers. For your first question, yes, it should be easier to get a PCI card to work (even an SB 16) and it will cause less problems in any case. ISA cards can impact the system performance very badly. Hope this helps somewhat. -- Regards: Szilveszter ADAM Budapest Hungary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound card woes
On Wed, 2003-08-20 at 17:04, Szilveszter Adam wrote: Hello, On Wed, Aug 20, 2003 at 03:20:55PM -0400, Matt Gostick wrote: I have a SND Blaster 16 in my computer. I was using FreeBSD 4.8 and 'device pcm' in my kernel config file, worked great. I've completely re-installed with 5.1R and recompiled my kernel with 'device pcm'. Unfortunately sound doesn't work. You also could add 'device sbc' to your kernel config since that is the SB bridge driver. But the card should work with PCM only. What does 'cat /dev/sndstat' say? # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: SB16 DSP 4.16 (ViBRA16X) at io 0x220 irq 7 drq 0 bufsz 4096d (1p/1r/0v channels duplex default) cat test.wav /dev/dsp makes a sound... but it isn't exactly what test.wav should sound like. The issue is probably some resource conflict. Since you have an SB 16, I'll have to ask: is it ISA? Or ISAPnP? Or PCI? PCI should just work but if it is ISA, you will need some tweaking. It is an ISA card... very old. Should I try and dig up a PCI card, or is it going to fairly 'painless' tweaking? Where should I start tweaking? Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
sound card woes
I have a SND Blaster 16 in my computer. I was using FreeBSD 4.8 and 'device pcm' in my kernel config file, worked great. I've completely re-installed with 5.1R and recompiled my kernel with 'device pcm'. Unfortunately sound doesn't work. I no longer have a /dev/snd0 device - I think I had one before... how do I make devices in 5.1R??? MAKEDEV is no longer available... and section 9.5 of the FreeBSD manual says: If you are running FreeBSD 5.0 or later you can safely skip this section. These versions use devfs(5) to allocate device nodes transparently for the user I've written the -questions list and they told me to try wrinting here. What do I do? Thanks, Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound card woes
Hello, On Wed, Aug 20, 2003 at 03:20:55PM -0400, Matt Gostick wrote: I have a SND Blaster 16 in my computer. I was using FreeBSD 4.8 and 'device pcm' in my kernel config file, worked great. I've completely re-installed with 5.1R and recompiled my kernel with 'device pcm'. Unfortunately sound doesn't work. You also could add 'device sbc' to your kernel config since that is the SB bridge driver. But the card should work with PCM only. What does 'cat /dev/sndstat' say? The issue is probably some resource conflict. Since you have an SB 16, I'll have to ask: is it ISA? Or ISAPnP? Or PCI? PCI should just work but if it is ISA, you will need some tweaking. I no longer have a /dev/snd0 device - I think I had one before... how do I make devices in 5.1R??? MAKEDEV is no longer available... and section 9.5 of the FreeBSD manual says: If you are running FreeBSD 5.0 or later you can safely skip this section. These versions use devfs(5) to allocate device nodes transparently for the user You do not need this, devfs will create the device for you when needed. -- Regards: Szilveszter ADAM Budapest Hungary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ESS sound card support on laptop
From: David W. Chapman Jr. [EMAIL PROTECTED] Subject: Re: ESS sound card support on laptop Date: Sat, 15 Jun 2002 18:11:35 -0500 Message-ID: [EMAIL PROTECTED] dwcjr The rumor I heard is that their english isn't that good so that I dwcjr might not be able to communicate with them, english being the only dwcjr language I know. I would be glad to contact them if this isn't the dwcjr case, but Im not sure exactly who they are. It is rumor truly, I think. :-) -- [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ESS sound card support on laptop
I have the following sound card on my laptop, does anyone know how hard it would be to add this card to the pcm driver. none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x10 hdr=0x00 vendor = 'ESS Technology' device = 'ES1978 Maestro-2E Audiodrive, ES1970 Canyon3D' class= multimedia subclass = audio -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
On Sat, Jun 15, 2002 at 02:52:33PM -0500, David W. Chapman Jr. wrote: I have the following sound card on my laptop, does anyone know how hard it would be to add this card to the pcm driver. none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x10 hdr=0x00 vendor = 'ESS Technology' device = 'ES1978 Maestro-2E Audiodrive, ES1970 Canyon3D' class= multimedia subclass = audio -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org Does it not work with the maestro driver? Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
On Sat, Jun 15, 2002 at 01:52:16PM -0600, Scott Long wrote: On Sat, Jun 15, 2002 at 02:52:33PM -0500, David W. Chapman Jr. wrote: I have the following sound card on my laptop, does anyone know how hard it would be to add this card to the pcm driver. none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x10 hdr=0x00 vendor = 'ESS Technology' device = 'ES1978 Maestro-2E Audiodrive, ES1970 Canyon3D' class= multimedia subclass = audio Does it not work with the maestro driver? It does. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : pcm0: ESS Technology Maestro-2E irq 5 at device 14.0 on pci0 : pcm0: unable to map register space : device_probe_and_attach: pcm0 attach returned 6 FreeBSD should, but isn't, assign resources to PCI devices. In the past, the BIOS has done this, but MS has migrated this functionality into the OS. That's why you see a lot of these sorts of failures with various kludges in the FreeBSD tree. That's part of what I was talking about in the developers conference when I said we needed to make PCI work again :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
M. Warner Losh wrote: In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : pcm0: ESS Technology Maestro-2E irq 5 at device 14.0 on pci0 : pcm0: unable to map register space : device_probe_and_attach: pcm0 attach returned 6 FreeBSD should, but isn't, assign resources to PCI devices. In the past, the BIOS has done this, but MS has migrated this functionality into the OS. That's why you see a lot of these sorts of failures with various kludges in the FreeBSD tree. That's part of what I was talking about in the developers conference when I said we needed to make PCI work again :-) So if you have a machine without any MS software installed, and have thereby denied the opportunity for MS to migrate this functionality into the OS, how does it get migrated? -- TErry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
past, the BIOS has done this, but MS has migrated this functionality into the OS. That's why you see a lot of these sorts of failures with various kludges in the FreeBSD tree. That's part of what I was talking about in the developers conference when I said we needed to make PCI work again :-) Wel I look forward to this if it fixes my sound and linksys card :) -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
In message: [EMAIL PROTECTED] Terry Lambert [EMAIL PROTECTED] writes: : M. Warner Losh wrote: : In message: [EMAIL PROTECTED] : David W. Chapman Jr. [EMAIL PROTECTED] writes: : : pcm0: ESS Technology Maestro-2E irq 5 at device 14.0 on pci0 : : pcm0: unable to map register space : : device_probe_and_attach: pcm0 attach returned 6 : : FreeBSD should, but isn't, assign resources to PCI devices. In the : past, the BIOS has done this, but MS has migrated this functionality : into the OS. That's why you see a lot of these sorts of failures with : various kludges in the FreeBSD tree. That's part of what I was : talking about in the developers conference when I said we needed to : make PCI work again :-) : : So if you have a machine without any MS software installed, and : have thereby denied the opportunity for MS to migrate this : functionality into the OS, how does it get migrated? We write it. It isn't in the BIOS anymore. Usually with ACPI. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
We write it. It isn't in the BIOS anymore. Usually with ACPI. Now that msmith left, do we have any acpi gurus? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
M. Warner Losh wrote: : FreeBSD should, but isn't, assign resources to PCI devices. In the : past, the BIOS has done this, but MS has migrated this functionality : into the OS. That's why you see a lot of these sorts of failures with : various kludges in the FreeBSD tree. That's part of what I was : talking about in the developers conference when I said we needed to : make PCI work again :-) : : So if you have a machine without any MS software installed, and : have thereby denied the opportunity for MS to migrate this : functionality into the OS, how does it get migrated? We write it. It isn't in the BIOS anymore. Usually with ACPI. That was kind of my point to David: blaming MS doesn't make FreeBSD work. At some point, you have to accept that the problem is yours, rather than being caused by some outside agency. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
That was kind of my point to David: blaming MS doesn't make FreeBSD work. At some point, you have to accept that the problem is yours, rather than being caused by some outside agency. I'm not sure I understand if you're referring to me. I haven't blamed MS or even mentioned MS. If I understand warner correctly, it can be solved by working on ACPI. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : We write it. It isn't in the BIOS anymore. Usually with ACPI. : Now that msmith left, do we have any acpi gurus? There are many japanese that are expert at this. I had plans on taking up at least some familiarity with the ACPI code because it directly impacts a usable cardbus subsystem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
In message: [EMAIL PROTECTED] Terry Lambert [EMAIL PROTECTED] writes: : That was kind of my point to David: blaming MS doesn't make FreeBSD : work. At some point, you have to accept that the problem is yours, : rather than being caused by some outside agency. Actually, it was caused by MS moving the BIOS resource assignment into the OS. We have had forever to deal and just haven't. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
On Sat, Jun 15, 2002 at 05:07:53PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : We write it. It isn't in the BIOS anymore. Usually with ACPI. : Now that msmith left, do we have any acpi gurus? There are many japanese that are expert at this. I had plans on taking up at least some familiarity with the ACPI code because it directly impacts a usable cardbus subsystem. The rumor I heard is that their english isn't that good so that I might not be able to communicate with them, english being the only language I know. I would be glad to contact them if this isn't the case, but Im not sure exactly who they are. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
David W. Chapman Jr. wrote: That was kind of my point to David: blaming MS doesn't make FreeBSD work. At some point, you have to accept that the problem is yours, rather than being caused by some outside agency. I'm not sure I understand if you're referring to me. I haven't blamed MS or even mentioned MS. If I understand warner correctly, it can be solved by working on ACPI. It was a point to you, but the statement was Warner's. It was your reaction that I was reacting to... 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
How could I do with my sound card?
Hello, My question is: My sound card is CS423X, FreeBSD supports it. It says: pcm1: CS423x at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 . But my system is FreeBSD-current, the /dev file system I can't write, can't use sh MAKEDEV snd0, and all software to look for /dev/mixer0 .. So how could to now? my dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed Feb 21 19:57:08 GMT 2001 [EMAIL PROTECTED]:/usr/home/src-cur/sys/compile/bigbear Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300685261 Hz CPU: AMD-K6tm w/ multimedia extensions (300.69-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x400b10 real memory = 67108864 (65536K bytes) avail memory = 61530112 (60088K bytes) Preloaded elf kernel "kernel" at 0xc03b5000. seq0-15: Midi sequencers. Using $PIR table, 4 entries at 0xc00fdc10 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at 7.2 (no driver attached) pci0: old, non-VGA display device at 7.3 (no driver attached) ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xe800-0xe81f irq 10 at device 10.0 on pci0 ed0: address 00:e0:4c:dd:a0:ec, type NE2000 (16 bit) pci0: display, VGA at 12.0 (no driver attached) atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 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 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/16 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 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 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0f13 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0401 can't assign resources unknown: PNP0501 can't assign resources pcm1: CS423x at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 ad0: 4112MB WDC AC14300R [8912/15/63] at ata0-master UDMA33 ad1: 2014MB QUANTUM FIREBALL ST2.1A [4092/16/63] at ata0-slave UDMA33 acd0: CDROM LTN341 at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a cd9660: RockRidge Extension my dev: acd0a dsp1.0 ppi0sequencer9 ttyv5 acd0c dsp1.1 psm0sndstat ttyv6 ad0 dspW1.0 random stderr ttyv7 ad0s1a dspW1.1 sequencer0 stdin ttyv8 ad0s1b fd sequencer1 stdout ttyv9 ad0s1e fd0 sequencer10 sysmousettyva ad1 io sequencer11 tty ttyvb audio1.0kbd0sequencer12 ttyd0 ttyvc audio1.1klogsequencer13 ttyd1 ttyvd bpsm0 kmemsequencer14 ttyid0 ttyve console log sequencer15 ttyid1 ttyvf consolectl lpt0sequencer2 ttyld0 urandom cuaa0 lpt0.ctlsequencer3 ttyld1 vga cuaa1 mdctl sequencer4 ttyv0 zero cuaia0 mem sequencer5 ttyv1 cuaia1 mixer1 sequencer6 ttyv2 cuala0 nullsequencer7 ttyv3 cuala1 pci sequencer8 ttyv4 my df: Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a22820798219 11173247%/ devfs 110 100% /dev/ /dev/ad0s1e 3460132 1892196 129112659%/usr procfs 440 100% /proc /dev/acd0a 659010 6590100 100% /cdrom __ Do You Yahoo!? Yahoo! Auctions -
RE: How could I do with my sound card?
On 23-Feb-01 Liu Siwei wrote: Hello, My question is: My sound card is CS423X, FreeBSD supports it. It says: pcm1: CS423x at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 . But my system is FreeBSD-current, the /dev file system I can't write, can't use sh MAKEDEV snd0, and all software to look for /dev/mixer0 .. So how could to now? try MAKEDEV snd1 I'm fairly sure there is a FAQ or handbook entry on this. --- 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: How could I do with my sound card?
On Thu, Feb 22, 2001 at 04:31:30PM -0800, Liu Siwei wrote: Hello, My question is: My sound card is CS423X, FreeBSD supports it. It says: pcm1: CS423x at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 . But my system is FreeBSD-current, the /dev file system I can't write, can't use sh MAKEDEV snd0, and all software to look for /dev/mixer0 .. Are you trying to run MAKEDEV as root? So how could to now? -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How could I do with my sound card?
says: pcm1: CS423x at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 you have a bogus device pcm0. you probably have a mistake in your hints file. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sound card errors in -current ?
This is on a -current system when loading snd_maestro some time after boot. pcm0: ESS Technology Maestro-2E port 0x1400-0x14ff irq 5 at device 8.0 on pci0 pcm0: chn_init() for (play:0) failed pcm0: offset 0xfef7a000 exceeds limit. pcm0: chn_init() for (play:1) failed pcm0: offset 0xfefa9000 exceeds limit. pcm0: chn_init() for (play:2) failed pcm0: offset 0xfefb5000 exceeds limit. pcm0: chn_init() for (play:3) failed -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
How to set AC'97 on Board Sound sound card?
My system can recognize my VIA AC97 on board sound card. I can use cat /dev/sndstat to
see my sound card information. But why i cann't play any sound ?
N
'²æìr¸zǧvf¢Új:+v¨· è® "¶§²æìr¸yúÞy» rêëz{bØ^nr¡ûazg¬±¨
FreeBSD-current problem with my AC97 sound card
System is : FreeBSD -current 11,2000
I compile my system and kernel with device pcm, the system say message
when I run cat /dev/sndstat:
FreeBSD Audio Driver (newpcm) Nov 2 2000 17:31:39
Installed devices:
pcm0: VIA VT82C686A AC'97 Audio at io 0xdc00 irq 5 (1p/1r channels duplex)
but when i play sound, the sound is very ugly, why?
The following is my dmesg message:
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Thu Nov 2 17:34:37 GMT 2000
[EMAIL PROTECTED]:/home/src/sys/compile/amd
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 700029408 Hz
CPU: AMD Athlon(tm) Processor (700.03-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x642 Stepping = 2
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
AMD Features=0xc044b18,AMIE,DSP,3DNow!
real memory = 134152192 (131008K bytes)
config di sn0
config di lnc0
config di le0
config di ie0
config di fe0
config di cs0
config di bt0
config di aic0
config di aha0
config di adv0
config q
avail memory = 126980096 (124004K bytes)
Preloaded elf kernel "kernel" at 0xc038b000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc038b09c.
Preloaded elf module "random.ko" at 0xc038b0ec.
module_register: module random already exists!
Module random failed to register: 17
Pentium Pro MTRR support enabled
WARNING: Driver mistake: repeat make_dev("random")
WARNING: Driver mistake: repeat make_dev("urandom")
md0: Malloc disk
Using $PIR table, 7 entries at 0xc00fdd20
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
pcib1: VIA 8363 (KT133) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: NVidia Riva Ultra Vanta TNT2 graphics accelerator at 0.0 irq 10
isab0: VIA 82C686 PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: VIA 82C686 ATA66 controller port 0xd000-0xd00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: VIA 83C572 USB controller at 7.2 irq 11
pci0: VIA 83C572 USB controller at 7.3 irq 11
pcm0: VIA VT82C686A AC'97 Audio port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 5
at device 7.5 on pci0
ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xe800-0xe81f irq 11 at device 11.0 on
pci0
ed0: address 52:54:ab:1b:c6:05, type NE2000 (16 bit)
atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
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
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
plip0: PLIP network interface on ppbus0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
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
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: PNP0303 can't assign resources
unknown: PNP0f13 can't assign resources
unknown: PNP0700 can't assign resources
unknown: PNP0501 can't assign resources
unknown: PNP0501 can't assign resources
unknown: PNP0400 can't assign resources
ad0: 19574MB WDC WD205BA [39770/16/63] at ata0-master UDMA66
acd0: CDROM SAMSUNG CD-ROM SC-140F at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
new sound card
Alright, this just bit me in the ass... I just bought a card today that says "Creative Ensoniq AudioPCI" on the box. Well, as far as I can tell this card uses the es1371 chip. Well, I did a little digging because apparently the card's pci device id wasn't in the es137x.c file. So what I did was I put it in the file, and tried to make it configure as a 1371 chip. However I got an error when I did this: pcm0: AudioPCI ES1371 port 0xe400-0xe43f irq 11 at device 9.0 on pci0 pcm0: ac97 codec invalid or not present (id == 0) The mixer would not configure with this, and the driver wouldn't attach, so I went to ac97.c and found the error message, and commented out the "return ENODEV" statement so that I could make it attach the driver and see what would happen. Well, when I did that, I got another error in addition to the 2 above: pcm0: ac97 codec reports dac not ready however, the driver attaached, and I can use the mixer devices, and I can play CD's, but pcm audio still won't play, and there are no errors on the console when I try to play mp3's or any other kind of sounds. So I guess my question is: is anyone working on getting the device with id 0x58801274 (the closest card originally listed in the file was: 0x50001274) to work? Or does anyone already have this card working? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
more info on sound card
I managed to find a little more info on this chip in my new soundcard. It is slightly different from a regular es1371... and in linux it even get's some of its own #defines: CT5880REV_CT5880_C is it's revision. (or 0x02) and the chip says CT5880 on it. I'm assuming it's not much different, but so far in the linux driver, there are a couple of little differences between this chip and the regular 1371. If I get this working, I'll submit whatever I did to the driver to make it work, but I may need a little help here. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound Card
Ron 'The InSaNe One' Rosson wrote: On Sun, 13 Feb 2000, MIHIRA Yoshiro was heard blurting out: [EMAIL PROTECTED] wrote: Ron 'The InSaNe One' Rosson wrote: Under 3.3-RELEASE with PAO the sound card work with this entry in the config file: device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 Here is what the dmesg output looked like with that entry: pcm0 at 0x220 irq 5 drq 1 on isa ESS1879 (rev 11, native mode) Now under current I have tried both of these entries to get sound working to no avail. device pcm0 at isa? port? irq 5 drq 1 flags 0x0 device pcm0 at isa? port? irq 5 drq 1 flags 0x15 Any assistance in this matter would be greatly appreciated. device pcm0 device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x0 The above worked.. here is the dmesg output of it: sbc0: ESS 688 at port 0x220-0x22f irq 5 drq 1 on isa0 pcm0: SB DSP 3.01 (ESS mode) on sbc0 and insane-mental cat /dev/sndstat FreeBSD Audio Driver (newpcm) Feb 12 2000 16:45:04 Installed devices: pcm0: SB DSP 3.01 (ESS mode) at io 0x220 irq 5 drq 1 (1p/1r channels) The only issue I have left is that when a sound is played everuything is find till the end and it sounds like a fading echo. Did you actually try: options PNPBIOS device pcm device sbc It is important that you do this please, at least so we have a datapoint. Also, what version of -current? (if it's fairly new, you can even leave out 'device sbc' if you are running in PnP or PNPBIOS mode) I presume this is for a laptop, right? (you mentioned PAO but otherwise gave no clues). Does 'pnpinfo' report a pnp device? or is it a bios configured non-pnp chip on the motherboard? (in which case PNPBIOS should find it) Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound Card
On Tue, 15 Feb 2000, Peter Wemm was heard blurting out: Ron 'The InSaNe One' Rosson wrote: On Sun, 13 Feb 2000, MIHIRA Yoshiro was heard blurting out: [EMAIL PROTECTED] wrote: Ron 'The InSaNe One' Rosson wrote: Under 3.3-RELEASE with PAO the sound card work with this entry in the config file: device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 Here is what the dmesg output looked like with that entry: pcm0 at 0x220 irq 5 drq 1 on isa ESS1879 (rev 11, native mode) Now under current I have tried both of these entries to get sound working to no avail. device pcm0 at isa? port? irq 5 drq 1 flags 0x0 device pcm0 at isa? port? irq 5 drq 1 flags 0x15 Any assistance in this matter would be greatly appreciated. devicepcm0 devicesbc0at isa? port 0x220 irq 5 drq 1 flags 0x0 The above worked.. here is the dmesg output of it: sbc0: ESS 688 at port 0x220-0x22f irq 5 drq 1 on isa0 pcm0: SB DSP 3.01 (ESS mode) on sbc0 and insane-mental cat /dev/sndstat FreeBSD Audio Driver (newpcm) Feb 12 2000 16:45:04 Installed devices: pcm0: SB DSP 3.01 (ESS mode) at io 0x220 irq 5 drq 1 (1p/1r channels) The only issue I have left is that when a sound is played everuything is find till the end and it sounds like a fading echo. Did you actually try: options PNPBIOS device pcm device sbc It is important that you do this please, at least so we have a datapoint. Also, what version of -current? (if it's fairly new, you can even leave out 'device sbc' if you are running in PnP or PNPBIOS mode) I presume this is for a laptop, right? (you mentioned PAO but otherwise gave no clues). Does 'pnpinfo' report a pnp device? or is it a bios configured non-pnp chip on the motherboard? (in which case PNPBIOS should find it) Peter, Everyone, I did the recommendations Peter requested. It finds the sound card. The sound card still has the fading echo problem. I apologize for not mentioning this sooner but this is on a Fujitsu E360 Lifebook. I håve also attacthed the dmesg for it now with its current kernel. The thing that gets me is al the unknowns listed. TIA -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- Today's Quote: "It's important to pay close attention in schoolfor years I thought that bears masturbated all winter."---Damon R. Milhem 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 4.0-2208-CURRENT #12: Tue Feb 15 09:37:38 PST 2000 root@mental:/usr/src/sys/compile/MENTAL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (331.83-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 67018752 (65448K bytes) config en pcic0 config po pcic0 0x3e0 config ir pcic0 11 config iom pcic0 0xd config f pcic0 0 config q avail memory = 61784064 (60336K bytes) Preloaded elf kernel "kernel" at 0xc0305000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc030509c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX host to PCI bridge (AGP disabled) on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 ATA-33 controller port 0xf4f0-0xf4ff at device 7.1 on pci0 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 7.2 irq 9 chip1: Intel 82371AB Power management controller port 0xff80-0xff8f at device 7.3 on pci0 pci0: unknown card (vendor=0x11c1, dev=0x0440) at 16.0 irq 9 pcic-pci0: TI PCI-1221 PCI-CardBus Bridge irq 9 at device 19.0 on pci0 pcic-pci1: TI PCI-1221 PCI-CardBus Bridge irq 9 at device 19.1 on pci0 vga-pci0: Trident model 9388 VGA-compatible display device mem 0xfe80-0xfebf,0xfedc-0xfedd,0xfe40-0xfe7f at device 20.0 on pci0 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 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: mode
Re: Sound Card
On Sun, 13 Feb 2000, MIHIRA Yoshiro was heard blurting out: [EMAIL PROTECTED] wrote: Ron 'The InSaNe One' Rosson wrote: Under 3.3-RELEASE with PAO the sound card work with this entry in the config file: device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 Here is what the dmesg output looked like with that entry: pcm0 at 0x220 irq 5 drq 1 on isa ESS1879 (rev 11, native mode) Now under current I have tried both of these entries to get sound working to no avail. device pcm0 at isa? port? irq 5 drq 1 flags 0x0 device pcm0 at isa? port? irq 5 drq 1 flags 0x15 Any assistance in this matter would be greatly appreciated. devicepcm0 devicesbc0at isa? port 0x220 irq 5 drq 1 flags 0x0 The above worked.. here is the dmesg output of it: sbc0: ESS 688 at port 0x220-0x22f irq 5 drq 1 on isa0 pcm0: SB DSP 3.01 (ESS mode) on sbc0 and insane-mental cat /dev/sndstat FreeBSD Audio Driver (newpcm) Feb 12 2000 16:45:04 Installed devices: pcm0: SB DSP 3.01 (ESS mode) at io 0x220 irq 5 drq 1 (1p/1r channels) The only issue I have left is that when a sound is played everuything is find till the end and it sounds like a fading echo. TIA -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- "One of these days, people will be required to take written exams to use computers. I cannot wait for that day." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound Card
[EMAIL PROTECTED] wrote: Ron 'The InSaNe One' Rosson wrote: Under 3.3-RELEASE with PAO the sound card work with this entry in the config file: device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 Here is what the dmesg output looked like with that entry: pcm0 at 0x220 irq 5 drq 1 on isa ESS1879 (rev 11, native mode) Now under current I have tried both of these entries to get sound working to no avail. device pcm0 at isa? port? irq 5 drq 1 flags 0x0 device pcm0 at isa? port? irq 5 drq 1 flags 0x15 Any assistance in this matter would be greatly appreciated. Have you tried the following? device pcm device sbc or device pcm0 device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x0 Cheers MIHIRA Yoshiro Yokohama, Japan. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sound Card
Under 3.3-RELEASE with PAO the sound card work with this entry in the config file: device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 Here is what the dmesg output looked like with that entry: pcm0 at 0x220 irq 5 drq 1 on isa ESS1879 (rev 11, native mode) Now under current I have tried both of these entries to get sound working to no avail. device pcm0 at isa? port? irq 5 drq 1 flags 0x0 device pcm0 at isa? port? irq 5 drq 1 flags 0x15 Any assistance in this matter would be greatly appreciated. TIA -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- If computers get too powerful, we can organize them into a committee--that will do them in. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound Card
Ron 'The InSaNe One' Rosson wrote:
Under 3.3-RELEASE with PAO the sound card work with this entry in the
config file:
device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0
Here is what the dmesg output looked like with that entry:
pcm0 at 0x220 irq 5 drq 1 on isa
ESS1879 (rev 11, native mode)
Now under current I have tried both of these entries to get sound
working to no avail.
device pcm0 at isa? port? irq 5 drq 1 flags 0x0
device pcm0 at isa? port? irq 5 drq 1 flags 0x15
Any assistance in this matter would be greatly appreciated.
Have you tried the following?
device pcm
device sbc
(with and without "options PNPBIOS")
sbc.c: {0x78187316, "ESS ES1878"}, /* ESS1878 */
sbc.c: {0x79187316, "ESS ES1879"}, /* ESS1879 */
Cheers,
-Peter
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
Re: Flash (was: Re: Sound card support)
Hi .. Under current the flash plugin works with the linux version of Netscape and the linuxelator ... Sound etc, everything works ok ... except for the odd crash of netscape which is normal :) Hmmm. The developers of mozilla are dying to get bug reports http://www.mozilla.org 8) Someone for berkeley.edu last week reported 36 bugs which made the developers very happy ... -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Flash (was: Re: Sound card support)
Hi, On Thu, Dec 09, 1999 at 11:16:58PM +0300, Dmitrij Tejblum wrote: Good luck using it under current. First site you hit quits netscape without reasons... ... yes. I built the port for the first time just yesterday and made the same experience. ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. If you can hack on the flash plugin's Makefile, try add -fno-exceptions there. ... many thanks for the tip. It's up and running. Regards, Andreas P.S.: ... the port's maintainer is cc-ed ... -- : TSE GmbH Neue Medien : Gsf: Arne Reuter: : : Hovestrasse 14: Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP: :: : Anti-Spam Petition: http://www.politik-digital.de/spam/: : PGP-Key:http://www.tse-online.de/~ab/public-key: : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sound card support
[subject changes and thread hijacked] On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Also, I hope to contribute in some way to broaden FreeBSD's sound card support. I have the ESS 1868. I just made a printout of the data sheets for this particular sound card. If anyone out there needs the pdf version of the ESS 1868 datasheet/specs, just email me and I can send you a copy via email. So far, it looks like the 1868 only does full duplex in mono. ;-( (Is the 1868 even worth worrying about?) Also, how well does the ProAudio Spectrum 16 work at this point right now in -current? Does it work flawlessly? Whatever happened to the company that made the PAS 16? I saw where MediaVision doesn't exist anymore. Has another company taken over PAS development? Anyhow, as far as ISA cards go... how does the PAS 16 compare to the ESS 1868? I think the PAS only gets full duplex when you've got both the PAS and the SB compatibility side working in tandem. Well, I've got a PCI machine (Pentium), so I imagine a PCI sound card would be worlds better. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Flash (was: Re: Sound card support)
[again subject changes] -On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote: On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. I already mailed maintainer about this. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Flash (was: Re: Sound card support)
On Thu, Dec 09, 1999 at 08:32:05PM +0100, Jeroen Ruigrok/Asmodai wrote: [again subject changes] -On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote: On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. I already mailed maintainer about this. I don't even use the FreeBSD Netscape any more. As far as I'm concerned, there might as well NOT be a native binary for FreeBSD, because it's not very stable. I use the Linux netscape with macromedia's flash4 plugin and it works very well. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Flash (was: Re: Sound card support)
Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. If you can hack on the flash plugin's Makefile, try add -fno-exceptions there. Dima To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Flash (was: Re: Sound card support)
Hi .. Under current the flash plugin works with the linux version of Netscape and the linuxelator ... Sound etc, everything works ok ... except for the odd crash of netscape which is normal :) Just get the linux netscape and the linux flash plugin. Reinier [again subject changes] -On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote: On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. I already mailed maintainer about this. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... 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
Opti931 Sound Card
Since the new sound code has been committed, my cheapo Opti931 sound card hasn't been working. Hopefully with the dmesg and pnpinfo output which is attached, somebody can add the proper vendor IDs. Much appreciated. Neal Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID OPT0931 (0x3109143e), Serial Number 0x PnP Version 1.0, Vendor Version 0 Device Description: OPTi Audio 16 Logical Device ID: OPT 0x143e #0 Vendor register funcs 00 Device Description: AUX0 Logical Device ID: OPT9310 0x1093143e #1 Vendor register funcs 00 Device Description: OPTi Audio 16 TAG Start DF I/O Range 0x534 .. 0x608, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x380 .. 0x3f0, alignment 0x10, len 0xc [16-bit addr] I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0xe0c .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 7 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F DMA: channel(s) 0 1 3 5 6 8/16-bit, not a bus master, count by byte, count by word, Type F TAG Start DF I/O Range 0x534 .. 0xff0, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x380 .. 0x3f0, alignment 0x10, len 0xc [16-bit addr] I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0xe0c .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 7 9 10 11 - only one type (true/edge) DMA: channel(s) 0 1 3 5 6 8/16-bit, not a bus master, count by byte, count by word, Type F DMA: channel(s) 0 1 3 5 6 8/16-bit, not a bus master, count by byte, count by word, Type F TAG Start DF I/O Range 0x534 .. 0x608, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x380 .. 0x3f0, alignment 0x10, len 0xc [16-bit addr] I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0xe0c .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 7 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F TAG Start DF I/O Range 0x534 .. 0xff0, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x380 .. 0x3f0, alignment 0x10, len 0xc [16-bit addr] I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0xe0c .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 7 9 10 11 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F TAG Start DF I/O Range 0x534 .. 0xff0, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x380 .. 0x3f0, alignment 0x10, len 0xc [16-bit addr] I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0xe0c .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 7 9 10 11 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F TAG End DF Logical Device ID: OPT0001 0x0100143e #2 Vendor register funcs 00 Device Description: Game Port I/O Range 0x200 .. 0x20f, alignment 0x1, len 0x1 [16-bit addr] Logical Device ID: OPT0002 0x0200143e #3 Vendor register funcs 00 Device Description: MPU401 I/O Range 0x300 .. 0x360, alignment 0x10, len 0x2 [16-bit addr] IRQ: 5 7 9 10 11 - only one type (true/edge) End Tag Successfully got 53 resources, 4 logical fdevs -- card select # 0x0001 CSN OPT0931 (0x3109143e), Serial Number 0x Logical device #0 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0380 0x0380 0x0380 0x0380 0x0380 0x0380 0x0380 0x0380 IRQ 5 0 DMA 0 1 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #3 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 10 0 DMA 4 4 IO range check 0x00 activate 0x01 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 #121: Tue Sep 28 19:34:04 PDT 1999 root@:/usr/src/sys/compile/MILLENNIUM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199310064 Hz CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping = 7 Features=0xf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,
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 !# W
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 # P
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
Re: Problems with the sound card.
On Thu, 2 Sep 1999, Luoqi Chen wrote:
That's exactly what I have. This is just so weird. I am now reading the
debug register chapter of intel's manual, it is virtually impossible to
pinpoint the location by single-stepping through the code...
The debug register trick worked, and the discovery was quite unexpected:
because the isa bus is hanging off the pci bus, bus_release_resource()
call by a isa device, eventually reaches the pci_release_resource(),
where the device is blindly assumed to be a pci device and its isa_device
struct overwritten as if it were a struct pci_devinfo. pci_release_resource()
should check for pass-thru releases.
How about this patch:
Index: pci.c
===
RCS file: /home/ncvs/src/sys/pci/pci.c,v
retrieving revision 1.116
diff -u -r1.116 pci.c
--- pci.c 1999/08/28 00:51:03 1.116
+++ pci.c 1999/09/03 07:59:44
@@ -1375,40 +1375,42 @@
int rv;
struct pci_devinfo *dinfo = device_get_ivars(child);
pcicfgregs *cfg = dinfo-cfg;
+ int passthrough = (device_get_parent(child) != dev);
int map = 0;
- switch (type) {
- case SYS_RES_IRQ:
- if (rid != 0)
- return EINVAL;
- break;
+ if (!passthrough)
+ switch (type) {
+ case SYS_RES_IRQ:
+ if (rid != 0)
+ return EINVAL;
+ break;
- case SYS_RES_DRQ: /* passthru for child isa */
- break;
+ case SYS_RES_DRQ: /* passthru for child isa */
+ break;
#ifdef __alpha__
- case SYS_RES_DENSE:
- case SYS_RES_BWX:
+ case SYS_RES_DENSE:
+ case SYS_RES_BWX:
#endif
- case SYS_RES_MEMORY:
- case SYS_RES_IOPORT:
- /*
+ case SYS_RES_MEMORY:
+ case SYS_RES_IOPORT:
+ /*
* Only check the map registers if this is a direct
* descendant.
*/
- if (device_get_parent(child) == dev)
- map = pci_mapno(cfg, rid);
- else
- map = -1;
- break;
-
- default:
- return (ENOENT);
- }
+ if (device_get_parent(child) == dev)
+ map = pci_mapno(cfg, rid);
+ else
+ map = -1;
+ break;
+
+ default:
+ return (ENOENT);
+ }
rv = BUS_RELEASE_RESOURCE(device_get_parent(dev), child, type, rid, r);
- if (rv == 0) {
+ if (!passthrough rv == 0) {
switch (type) {
case SYS_RES_IRQ:
cfg-irqres = 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: Problems with the sound card.
On Thu, 2 Sep 1999, Ollivier Robert wrote: According to Doug Rabson: changing over to the pcm driver. Since your card is a PnP one, you should be able to put just "device pcm0" in your kernel config. Even for ISA ones ? I though only PCI sound cards let you use the shorter form... The new ISA PnP code uses it too. -- 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: Problems with the sound card.
What about documenting what you do here? It's not quite obvious to me why the dev is not the parent of the child in some cases. Cheers, Nick pcicfgregs *cfg = dinfo-cfg; +int passthrough = (device_get_parent(child) != dev); int map = 0; -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
On Fri, 3 Sep 1999, Nick Hibma wrote: What about documenting what you do here? It's not quite obvious to me why the dev is not the parent of the child in some cases. It may be a great-grandchild. For instance in this case, the child is isab0, the grandchild is isa0 and the great-grandchild is 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
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: Sound card problems with -current.
On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: What does "still nothing" mean? I can't see anything in your e-mail message which indicates what you're doing to test the sound and what you see in the way of error messages. I do see this: pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 That makes it look like your card's available. Are you sure you've created the appropriate devices and symlinks as follows: cd /dev ./MAKEDEV snd0 The pcm(4) manpage says snd1, but if your card's detected as pcm0, then that obviously doesn't apply. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Sheldon Hearn wrote: On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: What does "still nothing" mean? I can't see anything in your e-mail message which indicates what you're doing to test the sound and what you see in the way of error messages. I do see this: pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 That makes it look like your card's available. Are you sure you've created the appropriate devices and symlinks as follows: cd /dev ./MAKEDEV snd0 The pcm(4) manpage says snd1, but if your card's detected as pcm0, then that obviously doesn't apply. Ciao, Sheldon. 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: Sound card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. What are the permissions on /dev/dsp*? Are other deamons running that are attempting to access /dev/dsp? As an example, I ran E once and enabled 'sounds' from within e-conf only to find that while 'esd' is running, gqmpeg will not run (it reports 'Can't access /dev/dsp'). Good luck, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
Well, i recompiled with the Voxware drivers and commented out the pnp0 device, and now it works. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Mike Hoskins wrote: On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. What are the permissions on /dev/dsp*? Are other deamons running that are attempting to access /dev/dsp? As an example, I ran E once and enabled 'sounds' from within e-conf only to find that while 'esd' is running, gqmpeg will not run (it reports 'Can't access /dev/dsp'). Good luck, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: -- pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 unknown0: Game on isa0 unknown1: Audio at port 0x240-0x24f,0x300-0x301,0x388-0x38b irq 9 drq 1,7 on isa0 I'm confused by the unknown1 line. Could you send the output of 'pnpinfo' for this machine. -- 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.
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: Sound card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Okay. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] Now I'm really confused. It looks like you have an explicit line for the soundcard in your config (e.g. "device pcm0 at isa? port ? ...") but the config file which you posted only had a "device pcm0" line. With the new driver, if it is a pnp card, you mustn't specify resources. What appears to have happened is that the probe hints (which must have matched the bios settings) allowed pcm0 to probe and attach the card. After that, the pnp code allocated resources for the Audio logical device, avoiding the resources already allocated by pcm0. This moved the card settings away from what the driver was expecting, effectively disabling pcm0. Since the Audio device didn't probe as pcm1, you may also have the buggy version of pci.c which was overwriting some of the pnp information. Make sure that you have at least version 1.117 of pci.c. -- 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, 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: Sound card problems with -current.
Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Doug Rabson wrote: On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Okay. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] Now I'm really confused. It looks like you have an explicit line for the soundcard in your config (e.g. "device pcm0 at isa? port ? ...") but the config file which you posted only had a "device pcm0" line. With the new driver, if it is a pnp card, you mustn't specify resources. Um, I did try that once, but I tried it the correct way and it still didnt work. What appears to have happened is that the probe hints (which must have matched the bios settings) allowed pcm0 to probe and attach the card. After that, the pnp code allocated resources for the Audio logical device, avoiding the resources already allocated by pcm0. This moved the card settings away from what the driver was expecting, effectively disabling pcm0. Since the Audio device didn't probe as pcm1, you may also have the buggy version of pci.c which was overwriting some of the pnp information. Make sure that you have at least version 1.117 of pci.c. BINGO! I had pci.c version 1.116. It is running off pcm0 now thou. -- 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
Re: Problems with the sound card.
Could you send the output of dmesg. It could be that your BIOS has rearranged the irq settings and has put another card on that IRQ. Is the sound card PNP? If not, could you check that the card's IRQ is marked as legacy in the BIOS? Nick My sound card used to work, and with a backup kernel it still did ( I lost it ) but after doing a make update world yesturday I came to the realization that it no longer works. Did someone break the sb drivers? I get a drq / irq conflict error, but they are set to the sound card's settings. 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 -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
here it is: 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 #4: Thu Sep 2 10:45:54 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ARTHUR Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (167.05-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 = 62173184 (60716K bytes) Preloaded elf kernel "kernel" at 0xc02d1000. 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: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ide_pci0: Intel PIIX3 Bus-master IDE controller at device 7.1 on pci0 vga-pci0: Matrox MGA 1024SG/1064SG/1164SG graphics accelerator irq 10 at device 10.0 on pci0 xl0: 3Com 3c905B-TX Fast Etherlink XL irq 11 at device 11.0 on pci0 xl0: Ethernet address: 00:10:4b:c5:24:df 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-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 on isa0 wdc0: unit 0 (wd0): WDC AC23200L wd0: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): E285XA/1.00, removable, dma, iordis wcd0: drive speed 1377KB/sec, 240KB cache wcd0: supported read types: CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked 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 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: 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 ppi0: generic parallel i/o on ppbus 0 sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: SoundBlaster 16 4.13 sbxvi0 at port 0x drq 5 on isa0 isa_compat: didn't get ports for sbxvi snd0: SoundBlaster 16 4.13 WARNING: "snd" is usurping "snd"'s cdevsw[] unknown0: Game on isa0 unknown1: Audio at port 0x221-0x230,0x300-0x301,0x388-0x38b irq 9 drq 3,7 on isa0 changing root device to wd0s1a Sound: DMA (output) timed out - IRQ/DRQ config error? Sound: DMA (output) timed out - IRQ/DRQ config error? Sound: DMA (output) timed out - IRQ/DRQ config error? thanks. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Thu, 2 Sep 1999, Nick Hibma wrote: Could you send the output of dmesg. It could be that your BIOS has rearranged the irq settings and has put another card on that IRQ. Is the sound card PNP? If not, could you check that the card's IRQ is marked as legacy in the BIOS? Nick My sound card used to work, and with a backup kernel it still did ( I lost it ) but after doing a make update world yesturday I came to the realization that it no longer works. Did someone break the sb drivers? I get a drq / irq conflict error, but they are set to the sound card's settings. 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 -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy 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: Problems with the sound card.
Could you send the output of dmesg. It could be that your BIOS has rearranged the irq settings and has put another card on that IRQ. Is the sound card PNP? If not, could you check that the card's IRQ is marked as legacy in the BIOS? Nick My sound card used to work, and with a backup kernel it still did ( I lost it ) but after doing a make update world yesturday I came to the realization that it no longer works. Did someone break the sb drivers? I get a drq / irq conflict error, but they are set to the sound card's settings. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] I too have problems with my on board CS4236 sound chip and it is of a very strange nature: in the new isa pnp code, function isa_assign_resources() mysteriously overwrites the isa_device structure and sets logical_id to 0, and as a result subsequent probe would not recognize it any more. I have narrowed it down to the bus_release_resource() call at the end of isa_find_irq(). It was so convoluted beyond that point and I gave up. I'd like to see someone more familiar with the code to continue. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
On Thu, 2 Sep 1999, Luoqi Chen wrote: Could you send the output of dmesg. It could be that your BIOS has rearranged the irq settings and has put another card on that IRQ. Is the sound card PNP? If not, could you check that the card's IRQ is marked as legacy in the BIOS? Nick My sound card used to work, and with a backup kernel it still did ( I lost it ) but after doing a make update world yesturday I came to the realization that it no longer works. Did someone break the sb drivers? I get a drq / irq conflict error, but they are set to the sound card's settings. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] I too have problems with my on board CS4236 sound chip and it is of a very strange nature: in the new isa pnp code, function isa_assign_resources() mysteriously overwrites the isa_device structure and sets logical_id to 0, and as a result subsequent probe would not recognize it any more. I have narrowed it down to the bus_release_resource() call at the end of isa_find_irq(). It was so convoluted beyond that point and I gave up. I'd like to see someone more familiar with the code to continue. This sounds pretty strange. What do you have in your kernel config? For PnP cards, you just need: device pcm0 in the config file (i.e. no explicit bus location or resource assignments). -- 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: Problems with the sound card.
I too have problems with my on board CS4236 sound chip and it is of a very strange nature: in the new isa pnp code, function isa_assign_resources() mysteriously overwrites the isa_device structure and sets logical_id to 0, and as a result subsequent probe would not recognize it any more. I have narrowed it down to the bus_release_resource() call at the end of isa_find_irq(). It was so convoluted beyond that point and I gave up. I'd like to see someone more familiar with the code to continue. This sounds pretty strange. What do you have in your kernel config? For PnP cards, you just need: device pcm0 in the config file (i.e. no explicit bus location or resource assignments). That's exactly what I have. This is just so weird. I am now reading the debug register chapter of intel's manual, it is virtually impossible to pinpoint the location by single-stepping through the code... -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
That's exactly what I have. This is just so weird. I am now reading the debug register chapter of intel's manual, it is virtually impossible to pinpoint the location by single-stepping through the code... The debug register trick worked, and the discovery was quite unexpected: because the isa bus is hanging off the pci bus, bus_release_resource() call by a isa device, eventually reaches the pci_release_resource(), where the device is blindly assumed to be a pci device and its isa_device struct overwritten as if it were a struct pci_devinfo. pci_release_resource() should check for pass-thru releases. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Aurel VORTEX Sound Card
Dose anybody install sound card Diamond Monster Sound II (based on Aurel VORTEX chipset) and make it propertly work ? Tell me how you did it, pls! -- Mike Ju. Volkov AKA Commander [EMAIL PROTECTED] tel.: 232-3644 ICQ# 5173328 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: how to play with pci128 sound card
Greetings, I also have a Creative Labs Sound Blaster PCI128 installed, and though I followed your instructions below I am not havine what I would call promising results. At 12:21 PM 1/10/99 +0100, Luigi Rizzo wrote: you need a -current system with the pcm device, then I am running 3.1-STABLE, but since your instructions were dated befoe the split, I assumed this would be OK. I have added the pnp0 controller and the pcm0 device to my kernel. /kernel: es1: AudioPCI ES1370 rev 0x00 int a irq 12 on pci0.10.0 /kernel: pcm1: using I/O space register mapping at 0xb800 cd /dev ./MAKEDEV snd1 I have done this. cat somefile /dev/audio When I cat'd a .au file I had on my system there was a pause before I got my prompt back, but complete silence from the speakers. Since I did not get any errors addressing the device, could this be a volume problem? If so, is there any way to adjust the volume. If not a volume problem, do you have any suggestions? Any help appreciated! -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Which sound card now?
Is the SB PCI 128 supported yet in -current. I new a new sound card and I really would like a 'real' Sound balster. On Fri, 15 Jan 1999, Satoshi Asami wrote: * From: br...@worldcontrol.com * So I am now mostly back the square 1. I'm still using an old GUS MAX, * which at the whim of FreeBSD-core may suddenly stop working. Just one point -- the axing of voxware was *not* approved by FreeBSD-core, and that's why it has been brought back. Satoshi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Jim Joseph Email: j...@phoenix.net Be free and open and breezy! Enjoy! Things won't get any better so get used to it. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Which sound card now?
Some weeks or days ago my GUS MAX (non-PnP) became a relic when Voxware was axed from FreeBSD. Eventhough, Voxware was reinstated, I diligently went about finding a Luigi-Approved sound card. After weeks of research I came to the conclusion that the 'Aopen AW 37 Pro' was the card of choice. I then set about ordering 2. Two different companies have told me that the card is no longer made. So I am now mostly back the square 1. I'm still using an old GUS MAX, which at the whim of FreeBSD-core may suddenly stop working. And I have no idea what modern card will be reasonably well supported under pcm0. Does anyone have any suggestions? -- Brian Litzinger br...@litzinger.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Which sound card now?
* From: br...@worldcontrol.com * So I am now mostly back the square 1. I'm still using an old GUS MAX, * which at the whim of FreeBSD-core may suddenly stop working. Just one point -- the axing of voxware was *not* approved by FreeBSD-core, and that's why it has been brought back. Satoshi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Which sound card now?
Eventhough, Voxware was reinstated, I diligently went about finding a Luigi-Approved sound card. After weeks of research I came to the conclusion that the 'Aopen AW 37 Pro' was the card of choice. ... And I have no idea what modern card will be reasonably well supported under pcm0. I have had good success recently with Yamaha ISA cards, e.g. YMF715 or YMF719. luigi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Which sound card now?
And I have no idea what modern card will be reasonably well supported under pcm0. Does anyone have any suggestions? Followup: Dru Nelson was so kind to post me the details of his research on this subject and told me the following: I just went to Central Computer www.centralcomputer.com. They are close to where I work. AXRA 16 Yamaha 719 3D Sound...$15.95 J-Bond MF-719 Yamaha 3D OPL-3 w Midi..$36 ESS 16 IDE 3D Sound Card..$14 Television:TeleSound EX16 IDE.$68 USSA ASW192 PCI Sound Card$24.95 Yamaha Wave Force 192XG PCI Sound Card oem$32 of the above, i think the first two can work reasonably well; the ESS might work (with the recent patches) for listening to mpeg audio, whereas the Yamaha PCI do not work because Yamaha are not disclosing programming info on them. cheers luigi ---+- Luigi RIZZO . EMAIL: lu...@iet.unipi.it. Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) ---+- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
