No sound in -current?
Hello, I just updated my system last night around 8 PM PST and today I have no sound. XMMS says it's playing music and I can see that it thinks it's playing something, but I am hearing nothing. Same deal with RealPlayer and every other app I try. No crackles, pops or *anything*. Just dead silence. Is this a known issue? Sound was working fine with my previous system from a couple of weeks ago. I'm running: FreeBSD 5.0-CURRENT #0: Thu Mar 27 20:24:08 PST 2003 and 'cat /dev/sndstat' yields: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT82C686A at io 0xdc00 irq 5 (1p/1r/0v channels duplex default) Any ideas? Thanks in advance, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
No sound in -current?
Hello, I just updated my system last night around 8 PM PST and today I have no sound. XMMS says it's playing music and I can see that it thinks it's playing something, but I am hearing nothing. Same deal with RealPlayer and every other app I try. No crackles, pops or *anything*. Just dead silence. Is this a known issue? Sound was working fine with my previous system from a couple of weeks ago. I'm running: FreeBSD 5.0-CURRENT #0: Thu Mar 27 20:24:08 PST 2003 and 'cat /dev/sndstat' yields: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT82C686A at io 0xdc00 irq 5 (1p/1r/0v channels duplex default) Any ideas? Thanks in advance, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re:No sound in -current?
Scott R. writes: | I just updated my system last night around 8 PM PST and today I have no | sound. XMMS says it's playing music and I can see that it thinks it's | playing something, but I am hearing nothing. Same deal with RealPlayer | and every other app I try. No crackles, pops or *anything*. Just dead | silence. Is this a known issue? Sound was working fine with my | previous system from a couple of weeks ago. Scott A fix for this was committed this morning (PST). Please let me know if you experience any audio problems after the next update. Thanks - Orion ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trying to play sound in -current
On 04-Sep-01 David W. Chapman Jr. wrote: On Mon, Sep 03, 2001 at 08:44:58PM -0700, John Baldwin wrote: On 02-Sep-01 Julian Elischer wrote: David W. Chapman Jr. wrote: I get this a lot recently when I try to play anything echo test /dev/dsp0 /dev/dsp0: Device busy. even when it shouldn't be busy, after atbout 10 mins it usually becomes not busy sure your window manager isn't using it? (e.g. 'enlighten' does, as does kde in some configurations) Shouldnt' matter in -current since the sound driver does software mixing of multiple input channels (meaning that multiple processes can open /dev/dsp at the same time and it all Just Works (tm)). I was instructed to set snd.hw.vchan=4 I believe and it has appeared to fix this, by default its at 1 and they aren't mixed. Really? I've run multiple mpg123's before and had it mix the output appropriately w/o needing to set any sysctl's. In fact, am doing so right now inside of KDE (with arts or whatever their sound daemon is called also running). Granted, it sounds rather weird. :-P 915 john -80 5236K 900K pcmwr0:01 1.66% 1.51% mpg123 914 john -80 4336K 912K pcmwr0:01 1.64% 1.51% mpg123 sysctl hw.snd hw.snd.verbose: 0 hw.snd.unit: 0 hw.snd.autovchans: 0 hw.snd.maxvchans: 0 hw.snd.pcm0.vchans: 0 hw.snd.pcm0.hwvol_step: 5 hw.snd.pcm0.hwvol_mixer: vol -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trying to play sound in -current
On Tue, Sep 04, 2001 at 09:40:44AM -0700, John Baldwin wrote: In fact, am doing so right now inside of KDE (with arts or whatever their sound daemon is called also running). Granted, it sounds rather weird. :-P 915 john -80 5236K 900K pcmwr0:01 1.66% 1.51% mpg123 914 john -80 4336K 912K pcmwr0:01 1.64% 1.51% mpg123 sysctl hw.snd hw.snd.verbose: 0 hw.snd.unit: 0 hw.snd.autovchans: 0 hw.snd.maxvchans: 0 hw.snd.pcm0.vchans: 0 hw.snd.pcm0.hwvol_step: 5 hw.snd.pcm0.hwvol_mixer: vol If everything is using artsd then that may be the reason. My problem was I had apps using esound, artsd and them vmware directly talking to dsp. But this is only from what I gather, not from knowledge. -- 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: trying to play sound in -current
John Baldwin wrote: On 04-Sep-01 David W. Chapman Jr. wrote: On Tue, Sep 04, 2001 at 09:40:44AM -0700, John Baldwin wrote: In fact, am doing so right now inside of KDE (with arts or whatever their sound daemon is called also running). Granted, it sounds rather weird. :-P 915 john -80 5236K 900K pcmwr0:01 1.66% 1.51% mpg123 914 john -80 4336K 912K pcmwr0:01 1.64% 1.51% mpg123 sysctl hw.snd hw.snd.verbose: 0 hw.snd.unit: 0 hw.snd.autovchans: 0 hw.snd.maxvchans: 0 hw.snd.pcm0.vchans: 0 hw.snd.pcm0.hwvol_step: 5 hw.snd.pcm0.hwvol_mixer: vol If everything is using artsd then that may be the reason. My problem was I had apps using esound, artsd and them vmware directly talking to dsp. But this is only from what I gather, not from knowledge. Note the mpg123 processes. They are in pcmwr, i.e. writing to /dev/dsp directly and not going through artsd. I haven't looked at the code, but does a value of 0 for vchans mean infinite, I know this is a standard use for the value of zero in some instances... The other guy's was set to 1, raising it fixed his problem. Yours works with multiple opens with a value of zero. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trying to play sound in -current
I haven't looked at the code, but does a value of 0 for vchans mean infinite, I know this is a standard use for the value of zero in some instances... What what I gather, 0 means none, only use how many channels the sound card has. I'm assuming that John has multiple hardware channels. -- 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: trying to play sound in -current
David W. Chapman Jr. wrote: I haven't looked at the code, but does a value of 0 for vchans mean infinite, I know this is a standard use for the value of zero in some instances... What what I gather, 0 means none, only use how many channels the sound card has. I'm assuming that John has multiple hardware channels. Okay, that makes sense. I was wondering, because mine also shows a value of zero and works with multiple opens, but then I'm using a SB-Live!, and it has a lot of hardware channels, so if I switched to the Yamaha POS on the motherboard, I would have locks. This makes sense. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trying to play sound in -current
On 04-Sep-01 David W. Chapman Jr. wrote: On Tue, Sep 04, 2001 at 09:40:44AM -0700, John Baldwin wrote: In fact, am doing so right now inside of KDE (with arts or whatever their sound daemon is called also running). Granted, it sounds rather weird. :-P 915 john -80 5236K 900K pcmwr0:01 1.66% 1.51% mpg123 914 john -80 4336K 912K pcmwr0:01 1.64% 1.51% mpg123 sysctl hw.snd hw.snd.verbose: 0 hw.snd.unit: 0 hw.snd.autovchans: 0 hw.snd.maxvchans: 0 hw.snd.pcm0.vchans: 0 hw.snd.pcm0.hwvol_step: 5 hw.snd.pcm0.hwvol_mixer: vol If everything is using artsd then that may be the reason. My problem was I had apps using esound, artsd and them vmware directly talking to dsp. But this is only from what I gather, not from knowledge. Note the mpg123 processes. They are in pcmwr, i.e. writing to /dev/dsp directly and not going through artsd. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trying to play sound in -current
On 02-Sep-01 Julian Elischer wrote: David W. Chapman Jr. wrote: I get this a lot recently when I try to play anything echo test /dev/dsp0 /dev/dsp0: Device busy. even when it shouldn't be busy, after atbout 10 mins it usually becomes not busy sure your window manager isn't using it? (e.g. 'enlighten' does, as does kde in some configurations) Shouldnt' matter in -current since the sound driver does software mixing of multiple input channels (meaning that multiple processes can open /dev/dsp at the same time and it all Just Works (tm)). -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trying to play sound in -current
On Mon, Sep 03, 2001 at 08:44:58PM -0700, John Baldwin wrote: On 02-Sep-01 Julian Elischer wrote: David W. Chapman Jr. wrote: I get this a lot recently when I try to play anything echo test /dev/dsp0 /dev/dsp0: Device busy. even when it shouldn't be busy, after atbout 10 mins it usually becomes not busy sure your window manager isn't using it? (e.g. 'enlighten' does, as does kde in some configurations) Shouldnt' matter in -current since the sound driver does software mixing of multiple input channels (meaning that multiple processes can open /dev/dsp at the same time and it all Just Works (tm)). I was instructed to set snd.hw.vchan=4 I believe and it has appeared to fix this, by default its at 1 and they aren't mixed. -- 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
trying to play sound in -current
I get this a lot recently when I try to play anything echo test /dev/dsp0 /dev/dsp0: Device busy. even when it shouldn't be busy, after atbout 10 mins it usually becomes not busy pcm0: Creative CT5880-A port 0xd000-0xd03f irq 5 at device 14.0 on pci0 -- 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: trying to play sound in -current
"David W. Chapman Jr." wrote: I get this a lot recently when I try to play anything echo test /dev/dsp0 /dev/dsp0: Device busy. even when it shouldn't be busy, after atbout 10 mins it usually becomes not busy sure your window manager isn't using it? (e.g. 'enlighten' does, as does kde in some configurations) pcm0: Creative CT5880-A port 0xd000-0xd03f irq 5 at device 14.0 on pci0 -- 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 -- ++ __ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ [EMAIL PROTECTED] +--x USA\ a very strange | ( OZ)\___ ___ | country ! +- X_.---._/presently in San Francisco \_/ \\ v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trying to play sound in -current
I suppose it uses it, but why does it lock it for extended periods of time. KDE can't even use the sound driver while this is happening. - Original Message - From: Julian Elischer [EMAIL PROTECTED] To: David W. Chapman Jr. [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, September 02, 2001 2:46 PM Subject: Re: trying to play sound in -current David W. Chapman Jr. wrote: I get this a lot recently when I try to play anything echo test /dev/dsp0 /dev/dsp0: Device busy. even when it shouldn't be busy, after atbout 10 mins it usually becomes not busy sure your window manager isn't using it? (e.g. 'enlighten' does, as does kde in some configurations) pcm0: Creative CT5880-A port 0xd000-0xd03f irq 5 at device 14.0 on pci0 -- 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 -- ++ __ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ [EMAIL PROTECTED] +--x USA\ a very strange | ( OZ)\___ ___ | country ! +- X_.---._/presently in San Francisco \_/ \\ v To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trying to play sound in -current
I suppose it uses it, but why does it lock it for extended periods of time. KDE can't even use the sound driver while this is happening. set sysctl hw.snd.verbose as high as it'll go (3, with the latest code) and cat /dev/sndstat. it'll tell you the pid of the process using each channel. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trying to play sound in -current
On Sun, Sep 02, 2001 at 09:43:28PM +0100, Cameron Grant wrote:
I suppose it uses it, but why does it lock it for extended periods of
time. KDE can't even use the sound driver while this is happening.
set sysctl hw.snd.verbose as high as it'll go (3, with the latest code) and
cat /dev/sndstat. it'll tell you the pid of the process using each channel.
Now that I know how to debug it I can't seem to reproduce it for a
length of time that will provide me with the pid of the process
that's taking it, but thank you for the info. Just curious, how many
channels do I have, I don't quite understand the output.
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0: Creative CT5880-A at io 0xd000 irq 5 (1p/1r/0v channels
duplex default)
[pcm0:0:record]: speed 0, format , flags
interrupts 0, overruns 0, hfree 4096, sfree 0
{hardware} - feeder_root() - {userland}
[pcm0:1:play]: speed 44100, format 1010, flags 7030, pid 581
interrupts 124, underruns 0, ready 40960
{hardware} - feeder_root(1010) - {userland}
--
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: trying to play sound in -current
I recall reading the explanation somewhere on the KDE site on why artsd will hold a lock on the sound device, but as I recall the lock is like for 30 or 60 seconds... Reading the explanation I seem to recall thinking it was a lame hack solution to the problem of dealing with multiple opens on older sound hardware that can't handle multiple opens. I forget where this was but it was related to artsd. Julian Elischer wrote: "David W. Chapman Jr." wrote: I get this a lot recently when I try to play anything echo test /dev/dsp0 /dev/dsp0: Device busy. even when it shouldn't be busy, after atbout 10 mins it usually becomes not busy sure your window manager isn't using it? (e.g. 'enlighten' does, as does kde in some configurations) pcm0: Creative CT5880-A port 0xd000-0xd03f irq 5 at device 14.0 on pci0 -- 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 -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trying to play sound in -current
That seems to confirm the results of my research. artsd is the sound server and apparently it defaults to a 60 second lock. - Original Message - From: "Jim Bryant" [EMAIL PROTECTED] To: "Julian Elischer" [EMAIL PROTECTED] Cc: "David W. Chapman Jr." [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, September 02, 2001 9:13 PM Subject: Re: trying to play sound in -current I recall reading the explanation somewhere on the KDE site on why artsd will hold a lock on the sound device, but as I recall the lock is like for 30 or 60 seconds... Reading the explanation I seem to recall thinking it was a lame hack solution to the problem of dealing with multiple opens on older sound hardware that can't handle multiple opens. I forget where this was but it was related to artsd. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No sound in current from ES1370
Hello, recent 5.0-current versions do not generate sound any more on my Soundblaster PCI128 (Ensoniq 1370-Chip). On a kernel build from sources from Oct. 17th everything was o.k. So I guess it must be the changes that went in on Oct. 26th. I will try to backout these. Anyways if someone wants to look into this, I have enclosed the kernel-config-file and the dmesg output. TIA Michael - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - 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: Sun Oct 29 10:35:44 MET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/MCSMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (349.07-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 268369920 (262080K bytes) avail memory = 256327680 (250320K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc04a5000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 7 entries at 0xc00fde10 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xd000-0xd01f irq 11 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: Intel 82371AB Power management controller port 0x5000-0x500f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped 4000 pci0: Matrox MGA Millennium II 2164W graphics accelerator at 8.0 irq 16 pcm0: AudioPCI ES1370 port 0xd400-0xd43f irq 17 at device 9.0 on pci0 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xd800-0xd87f mem 0xe2003000-0xe200307f irq 18 at device 10.0 on pci0 xl0: Ethernet address: 00:10:5a:d7:dd:9c miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bktr0: BrookTree 878 mem 0xe200-0xe2000fff irq 19 at device 11.0 on pci0 bti2c0: bt848 Hard/Soft I2C controller iicbb0: I2C generic bit-banging driver on bti2c0 iicbus0: Philips I2C bus on iicbb0 master-only smbus1: System Management Bus on bti2c0 smb1: SMBus general purpose I/O on smbus1 bktr0: Hauppauge Model 61344 D121 bktr0: Detected a MSP3410D-B4 at 0x80 bktr0: Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, remote control. pci0: unknown card (vendor=0x109e, dev=0x0878) at 11.1 irq 19 ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xdc00-0xdcff mem 0xe2002000-0xe2002fff irq 16 at device 12.0 on pci0 aic7895C: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xe000-0xe0ff mem 0xe2004000-0xe2004fff irq 16 at device 12.1 on pci0 aic7895C: Wide Channel B, SCSI Id=7, 32/255 SCBs fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,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 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port unknown: PNP0303 can't assign
Re: Sound and -current.
That's the hint I was looking for.. I had the pcm0 but didn't know we now had to add a special sbc entry.. THANKS! Now I know what I'm looking for i'll ge an dlook at LINT to see what else is in that vicinty. I guess I stopped reading at: # For pnp sound cards: #device pcm0 On Sun, 19 Dec 1999, Devin Butterfield wrote: Julian Elischer wrote: So is there any chance that my Vibra16 Soundblaster will ever be recognised again? I was surprised because I had imagined that the soundblaster would be the first card supported under the new code. unknown0: Audio at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 7 drq 0,5 on isa0 unknown1: IDE at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown2: Game at port 0x200-0x207 on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Silly question but...do you have: devicepcm0 devicesbc0 in your kernel config? I have the ViBRA16X and I got the same messages during boot until I compiled support into the kernel. Now it looks like: sbc0: Creative ViBRA16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq1,3 on isa0 pcm0: SB DSP 4.16 on sbc0 unknown0: Game at port 0x201 on isa0r Of course I'm not using the game port. :) -- Regards, Devin. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound and -current.
On Sun, Dec 19, 1999, Julian Elischer wrote: So is there any chance that my Vibra16 Soundblaster will ever be recognised again? Did you add the sbc0 bridge driver to your kernel configuration file? (I managed to miss that heads-up the first time around too.) -- |Chris Costello [EMAIL PROTECTED] |Computers are a more fun way to do the same |work you'd have to do without them. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound and -current.
On 19 Dec, Devin Butterfield wrote: sbc0: Creative ViBRA16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq1,3 on isa0 pcm0: SB DSP 4.16 on sbc0 unknown0: Game at port 0x201 on isa0r Of course I'm not using the game port. :) Just add "device joy0" to your config. sbc0: Creative ViBRA16C at port 0x220-0x22f,0x330-0x331,0x388-0x38b ... pcm0: SB DSP 4.13 on sbc0 joy0: Generic PnP Joystick at port 0x200-0x207 on isa0 The only use for it (for me) is to allow to move the mousecursor with the joystick (X11). It´s nice to look into the face of WinXX-users while you present the possibilities of a highly configurable system to them. Bye, Alexander. -- This message guarded by an attack llama. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
