Re: new-bus, pcm, and matcd (was Re: new-bus breaks both sound drivers)
On Sat, 24 Apr 1999, Chris Csanady wrote: Ugh. This also has the same effect on captured audio using fxtv. It seems that everything audio related is messed up now. (Or perhaps real time?) I will try to find the exact day where things broke I guses. I don't have much time right now though.. FWIW, I can still play audio CDs... perhaps its time to shake the dust off some CDs? ;) - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus, pcm, and matcd (was Re: new-bus breaks both sound drivers)
mp3s aren't playing quite right with x11amp though, little skips here and there, they work fine with the old kernel. mpg123 seems fine, as does the sound in FXTV. I'll try making the world again. Was there ever any resolution/further inspection of this? Not as far I know; its still happening here. cmp3 (mpg123) also skips in the same way, but its much less noticeable. I've been updating and recompiling almost daily. Ugh. This also has the same effect on captured audio using fxtv. It seems that everything audio related is messed up now. (Or perhaps real time?) I will try to find the exact day where things broke I guses. I don't have much time right now though.. Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
Hmm, you might like to try this patch and see what happens, there is a missing old driver wrapper for the pcm stuff. As a result, it's not getting run from the isa probe. Regarding the other driver, I'm not sure what's going on there as the hooks appear to be present. Right on, that patch does it for me. pcm0 at port 0x220 irq 5 drq 1 flags 0x15 on isa0 pcm0: interrupting at irq 5 I've got an old SB16 Value, non-pnp. mp3s aren't playing quite right with x11amp though, little skips here and there, they work fine with the old kernel. mpg123 seems fine, as does the sound in FXTV. I'll try making the world again. Was there ever any resolution/further inspection of this? x11amp behaves similarly for me. Actually, under considerable load, it is *really* bad. Have there been any notable scheduling changes recently? I remember people were seeing overflows on their serial ports after the new-bus integration since the driver was no longer using fast interrupts or something. Could there be something similar with the pcm driver? Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
new-bus, pcm, and matcd (was Re: new-bus breaks both sound drivers)
mp3s aren't playing quite right with x11amp though, little skips here and there, they work fine with the old kernel. mpg123 seems fine, as does the sound in FXTV. I'll try making the world again. Was there ever any resolution/further inspection of this? Not as far I know; its still happening here. cmp3 (mpg123) also skips in the same way, but its much less noticeable. I've been updating and recompiling almost daily. also, is it known that the matcd driver is now non-functional? It doesn't get probed at all, but it does show up in the visual kernel config screen. Its a 2x cdrom drive that plugs into my sb16; proprietary interface, not IDE. grep matcd /sys/i386/conf/JAKE controller matcd0 at isa? port 0x230 bio dmesg | grep matcd Thank you. Jake -- we are but packets in the internet of life To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
Chris Piazza wrote: On 17-Apr-99 Brian Feldman wrote: Both sound drivers are broken with the new-bus code. My SB16, in the old driver, now gets recognized but sbxvi is never looked for. pcm0, the new driver, never initializes with the new code :( device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 The pcm0 sounddriver works for me. In fact, the only problem I had with new bus was it is now pcm0 instead of pcm1 ;-). es0: AudioPCI ES1370 at device 9.0 on pci0 pcm0: using I/O space register mapping at 0xd800 es0: interrupting at irq 4 device pcm0 On two different systems it works for me using pcm0.. This is an ESS clone card: Probing for PnP devices: CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0x Comp ID: PNPb02f [0x2fb0 d041] ESS1868 (rev 11) pcm1 (ESS1868 ESS1868 sn 0x) at 0x220-0x22f irq 5 drq 1 on isa This is an on-board Crystal SB-like PnP device: Probing for PnP devices: CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0x Comp ID: @@@ [0x ] mss_attach CS42361 at 0x530 irq 5 dma 1:0 flags 0x10 pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 fl ags 0x10 on isa For what it's worth, PnP has for the most part not been changed under new-bus and is using the old mechanisms. The only significant risk is that the attach code doesn't like what I've done with the emulation of isa_device-id_id for unit numbers. I'm sorry, you're going to need to have a bit of a look around and turning on or inserting some debug code to see what's happening. Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
Chris Piazza wrote: On 17-Apr-99 Brian Feldman wrote: Both sound drivers are broken with the new-bus code. My SB16, in the old driver, now gets recognized but sbxvi is never looked for. pcm0, the new driver, never initializes with the new code :( device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 The pcm0 sounddriver works for me. In fact, the only problem I had with new bus was it is now pcm0 instead of pcm1 ;-). es0: AudioPCI ES1370 at device 9.0 on pci0 pcm0: using I/O space register mapping at 0xd800 es0: interrupting at irq 4 device pcm0 On two different systems it works for me using pcm0.. This is an ESS clone card: Probing for PnP devices: CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0x Comp ID: PNPb02f [0x2f b0 d041] ESS1868 (rev 11) pcm1 (ESS1868 ESS1868 sn 0x) at 0x220-0x22f irq 5 drq 1 on isa This is an on-board Crystal SB-like PnP device: Probing for PnP devices: CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0x Comp ID: @@@ [0x00 00 ] mss_attach CS42361 at 0x530 irq 5 dma 1:0 flags 0x10 pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 fl ags 0x10 on isa For what it's worth, PnP has for the most part not been changed under new-bus and is using the old mechanisms. The only significant risk is that the attach code doesn't like what I've done with the emulation of isa_device-id_id for unit numbers. I thought PnP was not even using new-bus yet?! I haven't used PnP in a long time, but the pcm driver is broke for me too. I have used the following successfully with just the plain isa0 for quite some time.. device pcm0 at isa? port? tty irq 5 drq 1 flags 0x10 I'm sorry, you're going to need to have a bit of a look around and turning on or inserting some debug code to see what's happening. Where should I start? It doesn't print out anything upon boot.. Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
On Sat, 17 Apr 1999, Peter Wemm wrote: Chris Piazza wrote: On 17-Apr-99 Brian Feldman wrote: Both sound drivers are broken with the new-bus code. My SB16, in the old driver, now gets recognized but sbxvi is never looked for. pcm0, the new driver, never initializes with the new code :( device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 The pcm0 sounddriver works for me. In fact, the only problem I had with new bus was it is now pcm0 instead of pcm1 ;-). es0: AudioPCI ES1370 at device 9.0 on pci0 pcm0: using I/O space register mapping at 0xd800 es0: interrupting at irq 4 device pcm0 On two different systems it works for me using pcm0.. This is an ESS clone card: Probing for PnP devices: CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0x Comp ID: PNPb02f [0x2fb0 d041] ESS1868 (rev 11) pcm1 (ESS1868 ESS1868 sn 0x) at 0x220-0x22f irq 5 drq 1 on isa This is an on-board Crystal SB-like PnP device: Probing for PnP devices: CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0x Comp ID: @@@ [0x ] mss_attach CS42361 at 0x530 irq 5 dma 1:0 flags 0x10 pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 fl ags 0x10 on isa For what it's worth, PnP has for the most part not been changed under new-bus and is using the old mechanisms. The only significant risk is that the attach code doesn't like what I've done with the emulation of isa_device-id_id for unit numbers. I'm sorry, you're going to need to have a bit of a look around and turning on or inserting some debug code to see what's happening. Cheers, -Peter Here's what's going on with the pcm code. I've got an on-board audio device that should probably eventually be supported, is PnP and detected, but not recognized by the pcm driver. However, my SB16 ALSO fails to be attached. My SB16 is a nice pre-PnP one, which used to work fine with either audio driver. I'll paste my current config and dmesg. # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration - # Configuring the FreeBSD Kernel - The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # URL:http://www.FreeBSD.ORG/ # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.102 1998/01/11 02:16:38 jkh Exp $ machine i386 cpu I586_CPU ident CUSTOM maxusers128 makeoptions DEBUG=-g 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 CD9660#ISO 9660 Filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG#boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options NO_F00F_HACK options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_FORWARD #enable xparent proxy support options IPDIVERT options IPSTEALTH options DUMMYNET options DDB options DDB_UNATTENDED options VM86 options SOFTUPDATES options PQ_HUGECACHE # color for 1024k cache options ICMP_BANDLIM options MSGBUF_SIZE=16384 options VESA options INVARIANTS options INVARIANT_SUPPORT options CLK_USE_TSC_CALIBRATION #optionsICMP_BANDLIM_SILENT #optionsCPU_WT_ALLOC #optionsNO_MEMORY_HOLE config kernel root on wd0 controller pci0at nexus? controller isa0at nexus? controller pnp0 # Luigi's snd code. # You may also wish to enable the pnp controller with this, for pnp # sound cards. # device pcm0 device pcm1 at isa? port? tty irq 5 drq 1 flags 0x16 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 6 #device sbmidi0 at isa? port 0x330 #device opl0 at isa? port 0x388 device joy0at isa? port IO_GAME #controller fdc0at isa? port IO_FD1 bio irq 6 drq 2 #disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # for a PCI only system (most modern machines) #controller ata0 #device atadisk0# ATA disks #device
Re: new-bus breaks both sound drivers
On Sat, 17 Apr 1999, Brian Feldman wrote: On Sat, 17 Apr 1999, Peter Wemm wrote: Chris Piazza wrote: On 17-Apr-99 Brian Feldman wrote: Both sound drivers are broken with the new-bus code. My SB16, in the old driver, now gets recognized but sbxvi is never looked for. pcm0, the new driver, never initializes with the new code :( device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 [bunch of dmesg delete] [here from Peter] For what it's worth, PnP has for the most part not been changed under new-bus and is using the old mechanisms. The only significant risk is that the attach code doesn't like what I've done with the emulation of isa_device-id_id for unit numbers. I'm sorry, you're going to need to have a bit of a look around and turning on or inserting some debug code to see what's happening. Here's what's going on with the pcm code. I've got an on-board audio device that should probably eventually be supported, is PnP and detected, but not recognized by the pcm driver. However, my SB16 ALSO fails to be attached. My SB16 is a nice pre-PnP one, which used to work fine with either audio driver. I'll paste my current config and dmesg. FWIW, using a 2 hour old kernel, my Turtle Beach Malibu PCI PnP card works just fine: [from my config file] device pcm0 at isa? port ? tty irq 15 drq 1 [from my dmesg] Probing for PnP devices: Trying Read_Port at 203 CSN 1 Vendor ID: CSC7537 [0x3775630e] Serial 0x Comp ID: @@@ [0x ] PnP: override config for CSN 1 LDN 0 vend_id 0x3775630e port 0x 0x 0x 0x irq 0:0 drq 4:4 en 0 Called nullpnp_probe with tag 0x0001, type 0x3775630e port 0x0534 0x 0x0220 0x irq 15:0 drq 1:0 en 1 port 0x0534 0x 0x0220 0x irq 15:0 drq 1:0 en 1 mss_attach CS42371 at 0x530 irq 15 dma 1:0 flags 0x10 pcm1 (CS423x/Yamaha/AD1816 CS4237 sn 0x) at 0x530-0x537 irq 15 drq 1 f lags 0x10 on isa Notice that the line beginning port shows twice, which is an odditity. I use a line in my kernel.conf of: pnp 1 0 os enable port0 0x534 port2 0x220 irq0 15 drq0 1 drq1 0 I'm not saying Brian doesn't have a real problem, but I *am* saying that not all PCI PnP sound is broken. +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
Brian Feldman wrote:
On Sat, 17 Apr 1999, Peter Wemm wrote:
Chris Piazza wrote:
On 17-Apr-99 Brian Feldman wrote:
Both sound drivers are broken with the new-bus code. My SB16, in the ol
d
driver, now gets recognized but sbxvi is never looked for. pcm0, the ne
w
driver, never initializes with the new code :(
device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16
The pcm0 sounddriver works for me. In fact, the only problem I had with
new
bus was it is now pcm0 instead of pcm1 ;-).
es0: AudioPCI ES1370 at device 9.0 on pci0
pcm0: using I/O space register mapping at 0xd800
es0: interrupting at irq 4
device pcm0
On two different systems it works for me using pcm0..
Here's what's going on with the pcm code. I've got an on-board audio device
that should probably eventually be supported, is PnP and detected, but
not recognized by the pcm driver. However, my SB16 ALSO fails to be attached.
My SB16 is a nice pre-PnP one, which used to work fine with either audio
driver. I'll paste my current config and dmesg.
[..]
# Luigi's snd code.
# You may also wish to enable the pnp controller with this, for pnp
# sound cards.
#
device pcm0
device pcm1 at isa? port? tty irq 5 drq 1 flags 0x16
[..]
Hmm, you might like to try this patch and see what happens, there is
a missing old driver wrapper for the pcm stuff. As a result, it's not
getting run from the isa probe. Regarding the other driver, I'm not
sure what's going on there as the hooks appear to be present.
Index: i386/isa/isa_compat.h
===
RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v
retrieving revision 1.1
diff -u -r1.1 isa_compat.h
--- isa_compat.h1999/04/16 21:22:23 1.1
+++ isa_compat.h1999/04/17 17:30:34
@@ -49,6 +49,7 @@
#include ze.h
#include zp.h
#include oltr.h
+#include pcm.h
#include pas.h
#include sb.h
#include sbxvi.h
@@ -117,6 +118,7 @@
extern struct isa_driver zedriver;
extern struct isa_driver zpdriver;
extern struct isa_driver oltrdriver;
+extern struct isa_driver pcmdriver;
extern struct isa_driver pasdriver;
extern struct isa_driver sbdriver;
extern struct isa_driver sbxvidriver;
@@ -320,6 +322,9 @@
#if NOLTR 0
{ DRIVER_TYPE_MISC, oltrdriver },
+#endif
+#if NPCM 0
+ { DRIVER_TYPE_MISC, pcmdriver },
#endif
#if NPAS 0
{ DRIVER_TYPE_MISC, pasdriver },
Cheers,
-Peter
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
On Sat, 17 Apr 1999, Peter Wemm wrote: For what it's worth, PnP has for the most part not been changed under new-bus and is using the old mechanisms. The only significant risk is that the attach code doesn't like what I've done with the emulation of isa_device-id_id for unit numbers. Well, something appears to have changed. My internal PnP modem is no longer detected. I just checked sio.c, and it appears as if the PnP id is still there. I've got: controller pnp0 device sio0at isa? port IO_COM1 flags 0x10 tty irq 4 in my config file. Previously dmesg|grep sio would return: sio1: irq maps: 0x1 0x9 0x1 0x1 sio1: type 16550A sio1 (siopnp Cardinal MVP288IV sn 0x00416288) at 0x3e8-0x3ef irq 3 on isa sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A apm: found APM BIOS version 1.2 Now it returns: apm: found APM BIOS version 1.2 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 I'm sorry, you're going to need to have a bit of a look around and turning on or inserting some debug code to see what's happening. Cheers, -Peter - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
On Sun, 18 Apr 1999, Peter Wemm wrote:
Brian Feldman wrote:
On Sat, 17 Apr 1999, Peter Wemm wrote:
Chris Piazza wrote:
On 17-Apr-99 Brian Feldman wrote:
Both sound drivers are broken with the new-bus code. My SB16, in the
ol
d
driver, now gets recognized but sbxvi is never looked for. pcm0, the
ne
w
driver, never initializes with the new code :(
device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16
The pcm0 sounddriver works for me. In fact, the only problem I had
with
new
bus was it is now pcm0 instead of pcm1 ;-).
es0: AudioPCI ES1370 at device 9.0 on pci0
pcm0: using I/O space register mapping at 0xd800
es0: interrupting at irq 4
device pcm0
On two different systems it works for me using pcm0..
Here's what's going on with the pcm code. I've got an on-board audio device
that should probably eventually be supported, is PnP and detected, but
not recognized by the pcm driver. However, my SB16 ALSO fails to be
attached.
My SB16 is a nice pre-PnP one, which used to work fine with either audio
driver. I'll paste my current config and dmesg.
[..]
# Luigi's snd code.
# You may also wish to enable the pnp controller with this, for pnp
# sound cards.
#
device pcm0
device pcm1 at isa? port? tty irq 5 drq 1 flags 0x16
[..]
Hmm, you might like to try this patch and see what happens, there is
a missing old driver wrapper for the pcm stuff. As a result, it's not
getting run from the isa probe. Regarding the other driver, I'm not
sure what's going on there as the hooks appear to be present.
Thank you, that did work :) Now if someone could tell me why I need to
keep seeing
sorry, read DMA channel unavailable
let me know. This seems to be something that I do NOT need to see
from sb_dsp.c :P Other than that, everything's nice and peachy.
No, wait, I forgot. IPFW is _not_ being recognized in the kernel, and
the module is getting loaded instead (ipfw not being initialized?).
Index: i386/isa/isa_compat.h
===
RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v
retrieving revision 1.1
diff -u -r1.1 isa_compat.h
--- isa_compat.h 1999/04/16 21:22:23 1.1
+++ isa_compat.h 1999/04/17 17:30:34
@@ -49,6 +49,7 @@
#include ze.h
#include zp.h
#include oltr.h
+#include pcm.h
#include pas.h
#include sb.h
#include sbxvi.h
@@ -117,6 +118,7 @@
extern struct isa_driver zedriver;
extern struct isa_driver zpdriver;
extern struct isa_driver oltrdriver;
+extern struct isa_driver pcmdriver;
extern struct isa_driver pasdriver;
extern struct isa_driver sbdriver;
extern struct isa_driver sbxvidriver;
@@ -320,6 +322,9 @@
#if NOLTR 0
{ DRIVER_TYPE_MISC, oltrdriver },
+#endif
+#if NPCM 0
+ { DRIVER_TYPE_MISC, pcmdriver },
#endif
#if NPAS 0
{ DRIVER_TYPE_MISC, pasdriver },
Cheers,
-Peter
Brian Feldman_ __ ___ ___ ___ ___
gr...@unixhelp.org_ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ __ \ |) |
http://www.freebsd.org _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
Hmm, you might like to try this patch and see what happens, there is a missing old driver wrapper for the pcm stuff. As a result, it's not getting run from the isa probe. Regarding the other driver, I'm not sure what's going on there as the hooks appear to be present. Right on, that patch does it for me. pcm0 at port 0x220 irq 5 drq 1 flags 0x15 on isa0 pcm0: interrupting at irq 5 I've got an old SB16 Value, non-pnp. mp3s aren't playing quite right with x11amp though, little skips here and there, they work fine with the old kernel. mpg123 seems fine, as does the sound in FXTV. I'll try making the world again. IPFW works for me...but I'm loading the KLD. my panasonic cdrom is no longer probed, it uses the matcd driver. doesn't show up in dmesg at all, but it does in the visual kernel config thing. It's so old, I'm not surprised :) great work! Jake -- we are but packets in the internet of life To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
Oh, btw, you did break sbxvi. Look carefully at the #if which surrounds it ;) Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
On Sat, 17 Apr 1999, Jake Burkholder wrote: Hmm, you might like to try this patch and see what happens, there is a missing old driver wrapper for the pcm stuff. As a result, it's not getting run from the isa probe. Regarding the other driver, I'm not sure what's going on there as the hooks appear to be present. Right on, that patch does it for me. pcm0 at port 0x220 irq 5 drq 1 flags 0x15 on isa0 pcm0: interrupting at irq 5 I've got an old SB16 Value, non-pnp. mp3s aren't playing quite right with x11amp though, little skips here and there, they work fine with the old kernel. mpg123 seems fine, as does the sound in FXTV. I'll try making the world again. I suggest using the old VoxWare with an old SB16, like I do. I was only trying to use pcm temporarily because sbxvi is broken (fix isa_compat.h). IPFW works for me...but I'm loading the KLD. I like having my ipfw rules there BEFORE anything happens, hence before rc(5). my panasonic cdrom is no longer probed, it uses the matcd driver. doesn't show up in dmesg at all, but it does in the visual kernel config thing. It's so old, I'm not surprised :) great work! Jake -- we are but packets in the internet of life To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
Brian Feldman wrote: IPFW works for me...but I'm loading the KLD. I like having my ipfw rules there BEFORE anything happens, hence before rc(5). klds can be loaded by the loader. Hence, before /kernel. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, Windows works, using a loose definition of 'works'... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus breaks both sound drivers
On Sun, 18 Apr 1999, Daniel C. Sobral wrote: Brian Feldman wrote: IPFW works for me...but I'm loading the KLD. I like having my ipfw rules there BEFORE anything happens, hence before rc(5). klds can be loaded by the loader. Hence, before /kernel. Thanks for ruining my logic ;) But I really do hate overstuffing Makefile.inc in sys/modules so I can get the options I want. That's why for most things I use the kernel itself and not modules, really. -- Daniel C. Sobral (8-DCS) d...@newsguy.com d...@freebsd.org Well, Windows works, using a loose definition of 'works'... Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
new-bus breaks both sound drivers
Both sound drivers are broken with the new-bus code. My SB16, in the old driver, now gets recognized but sbxvi is never looked for. pcm0, the new driver, never initializes with the new code :( device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 6 #device sbmidi0 at isa? port 0x330 #device opl0 at isa? port 0x388 Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \\__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: new-bus breaks both sound drivers
On 17-Apr-99 Brian Feldman wrote: Both sound drivers are broken with the new-bus code. My SB16, in the old driver, now gets recognized but sbxvi is never looked for. pcm0, the new driver, never initializes with the new code :( device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 The pcm0 sounddriver works for me. In fact, the only problem I had with new bus was it is now pcm0 instead of pcm1 ;-). es0: AudioPCI ES1370 at device 9.0 on pci0 pcm0: using I/O space register mapping at 0xd800 es0: interrupting at irq 4 device pcm0 I'm using it right now, actually. Of course, this is a PCI card so there could be/is a difference. --- Chris PiazzaAbbotsford, BC, Canada cpia...@home.net finger n...@norn.ca.eu.org for PGP key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
