Date: Fri, 19 Apr 2002 07:59:33 +0100 From: Jean-Mark Dupoux <jmdupoux@lineone.net> To: John Utz <john@utzweb.net> Cc: questions@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG Subject: Re: Kernel config parameters for soundcard - 4.4 release Message-ID: <3CBFC055.B8D12949@lineone.net> References: <Pine.LNX.4.44.0204190120180.12819-100000@jupiter.linuxengine.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------DD7FE1464D07CA410EF55C74 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ok, here's the file - I havnt changed much from generic yet since the soundcard was pretty much the only sticking point jmdupoux_@_lineone.net John Utz wrote: > > On Fri, 19 Apr 2002 jmdupoux@lineone.net wrote: > > > nope, this one doesn't want to be fixed so soon ! > > remarkable. i am stumped. > > could you send your kernel config to the list for review? > > tnx! > > > I tried adding make clean in the run of commands but get the exact same failure at > > make. I suspected it would happen, since I already ran rm -r on the > > compile/KERNEL directory with the same intention on a couple of attempts to > > build with device pcm before that, again with no difference in the result > > > > what im trying to figure now is whether there is already an attempt to probe the > > hardware when the compile is running into the problem code, or is this "just > > software" reacting badly on my machine ? > > > > Jean-Mark Dupoux > > jmdupoux_@_lineone.net > > > > > > > > > > > > > > On 18 Apr 2002 at 17:22, John Utz wrote: > > > > > On Thu, 18 Apr 2002 jmdupoux@lineone.net wrote: > > > > > > > hmmm, I really should have mentioned this in my last mail as it is the > > > > obvious thing to suggest (how often do we overlook things like that when > > > > we get too wrapped up in a problem), but I already tried compiling with > > > > just: > > > > > > > > device pcm > > > > device sb0 at isa? port 0x220 irq 5 drq 0 flags 0x11 > > > > > > > > and none of the other devices, but make still falls over with the exact > > > > same errors. I think I tried more or less every possible combination of > > > > inclusion/exclusion of the other devices combined with pcm and sb0, but > > > > nothing ever got past make ( so long as I had pcm and not snd as the > > > > first device) > > > > > > did you do a config, make clean, make depend, then make? once you sucked > > > in the midi stuff, it's gonna try and build it unless you change the > > > makefile. > > > > > > so, i'd first make sure that i had blown that stuff away. cause there is > > > know reason why you shouldnt be able to make a kernel. > > > > > > > Since you're working on the code for this I'll be more specific about > > > > the exact card and chipsets involved here as it might be useful for > > > > reference: > > > > > > :-) > > > > > > tnx. but lets save it till i have some working code for you to try :-) > > > > > > > > > > Aztech Sound Galaxy pro II (often referred to as Sound Galaxy Washington > > > > or sometimes Nova) main chipset is AZT2316r and the card also has a > > > > Crystal 4231a-kl > > > > > > > > obviously the card has DOS/Windows drivers, which basically set the card > > > > up with SB pro emulation, combined with MSS sound system, opl3, joystick > > > > and midi, all at the "standard" addresses (software adjustable) I think > > > > I also tried to install Crystal drivers on the card once in DOS but > > > > definitely without very good results. Other non-specific DOS programs > > > > can get audio produced using basic SB-pro settings without the specific > > > > Aztech driver (eg a DOS general hardware diagnostics utility I use to > > > > check IRQ's ) > > > > > > > > From what I can tell the card is not truly plug-n-play, but uses an > > > > EEPROM chip where the settings get written to when options get changed > > > > through the driver interface > > > > > > > > > > > > I'm not desparate to get this working although it would be very useful, > > > > but still very confused why the __SGNXPRO__ option doesn't get > > > > recognised - this is where practical experience from someone else's > > > > machine might really pay off. > > > > > > > > > > > > Jean-Mark Dupoux > > > > jmdupoux_@_lineone.net > > > > > > > > > > > > > > > > On 18 Apr 2002 at 14:55, John Utz wrote: > > > > > > > > > midi is utterly unimplemented with the new sound code. > > > > > > > > > > so putting the midi devices into the config file will generate the errors > > > > > you are getting, because the old midi code is based on 'oldbus' for want > > > > > of a better term, whereas the device structure in 4.X is based on > > > > > 'newbus'. > > > > > > > > > > so that stuff aint gonna compile. > > > > > > > > > > i am *actively* working on merging the tanimura code into 4.5-RELEASE. i > > > > > spend 2+ hours a day on it, 5 days a week ( assuming that i take the bus > > > > > to work all week, if i drive to work, then i dont work on it that day, eh! > > > > > :-) ). > > > > > > > > > > i've been thinking about making a public announcement that i was going to > > > > > tackle this, and i'd rather have waited until i had working code ( which > > > > > i am guessing is 2 months off ), but your mail seemed like a good segue. > > > > > > > > > > the patches that tanimura generated in 1999 are pretty big, and so i have > > > > > been basically wading thru the code trying to understand the > > > > > relationships. > > > > > > > > > > my intent is to turn the midi bits into a kld. that makes it a lot harder > > > > > in the beginning ( because the code *appears* to be implemented as > > > > > compiled in only...but i could be mistaken ), but makes development easier > > > > > in the long run because the build/try cycle is much shorter ( i usually > > > > > refer to this as 'compile, fiddle, compile' :-) ). > > > > > > > > > > streamlining the process is *very* important to me because i am doing this > > > > > on an HP 800CT laptop with a p166MMX and 80M of ram. we ain't talkin' big > > > > > iron here..... > > > > > > > > > > so, the good news for you is that the 800CT has an ESS AudioDrive ISA OEM > > > > > in it, so it too makes use of the sbc bridge. so any work that i do should > > > > > be immediately available to you. > > > > > > > > > > after i get it to work reliably on my laptop, i'll work on the other > > > > > hardware that i have at home, including my real live mpu-401 card. > > > > > > > > > > it's important to note that i make no predictions as to when i will > > > > > finish or if i will even be successful....midi has a long sad story with > > > > > freebsd because it's *never* been finished! i've been running freebsd > > > > > since pre 1.0 and i have seen various bits of midi code thru the years. > > > > > individuals take up the cause, and then they stop, and are never heard > > > > > from again! lord knows that i have sent tanimura-san an email or two since > > > > > 1999 and i have never heard bit0 from him. or her. > > > > > > > > > > i *do* get lots of mail that sez 'gee, it would make me really happy if i > > > > > could use midi with freebsd'. > > > > > > > > > > but the code is pretty dense, and FreeBSD kernel-hackery seems to have an > > > > > awfully steep learning curve, it's certainly kicked *my* ass more than > > > > > once. > > > > > > > > > > as soon as i get something to compile, i'll post to -multimedia. then we > > > > > can go from there..... > > > > > > > > > > have a nice day! > > > > > > > > > > johnu > > > > > > > > > > > > > > > On Thu, 18 Apr 2002, Jean-Mark Dupoux wrote: > > > > > > > > > > > The first thing I tried was running the compile with pcm instead of > > > > > > snd, as per all the docs but then I got different errors come up, this > > > > > > time during the make. That's the only reason I compiled with snd > > > > > > instead. > > > > > > > > > > > > Specifically, I get a screenful of errors similar to the 2 or 3 lines > > > > > > i've quoted below, and then the build stops: > > > > > > > > > > > > midi_synth.o: In function 'midi_synth_xxxxx': > > > > > > midi_synth.o(.text+0xNNN): undefined reference to 'synth_devs' > > > > > > /* (similar error definitions complaining about other midi.synth.o > > > > > > function calls and undefined references repeated for several lines) */ > > > > > > > > > > > > ending with the line: > > > > > > > > > > > > *** Error code 1 > > > > > > > > > > > > and an abrupt stop to the make. > > > > > > > > > > > > > > > > > > But in any case, it wasnt until I had a "successful" build that I > > > > > > realised no mixer was being created, so then I went back and tried to > > > > > > compile with pcm again instead of snd and this time include the line > > > > > > with options __SGNXPRO__ added for the mixer, but then the build falls > > > > > > over when I run /usr/sbin/config MYKERNELFILE with the exact same error > > > > > > "Unknown option __SGNXPRO__" > > > > > > > > > > > > still cant make sense of this one, all the other documented options > > > > > > i've read about for the sb device dont kick up any errors (but they're > > > > > > not relevant to my card !) > > > > > > > > > > > > > > > > > > thanks in advance > > > > > > > > > > > > John Utz wrote: > > > > > > > > > > > > > > why are you using snd instead of pcm? > > > > > > > > > > > > > > snd is pretty deprecated.... > > > > > > > > > > > > > > i think you will get immediately better results using sbc ( the sb bridge > > > > > > > driver for pcm ) and pcm > > > > > > > > > > > > > > man pcm and man sbc can be your new best friends! > > > > > > > > > > > > > > On Thu, 18 Apr 2002, Jean-Mark Dupoux wrote: > > > > > > > > > > > > > > > Im having problems with an option for soundcard support to put in a > > > > > > > > kernel config file. To begin with I added the following lines into the > > > > > > > > config file: > > > > > > > > > > > > > > > > device snd > > > > > > > > device sb0 at isa? port 0x220 irq 5 drq 0 flags 0x11 > > > > > > > > device sbmidi0 at isa? port 0x330 irq 9 > > > > > > > > device opl0 at isa? port 0x388 > > > > > > > > device joy0 at isa? port 0x200 > > > > > > > > > > > > > > > > The kernel compiled properly and successfully loaded the soundblaster > > > > > > > > pro 3.1 driver. But I still got no sound out of the card, using cat > > > > > > > > /filename > /dev/audio or > /dev/dsp and got the same no sound > > > > > > > > result using play /filename > > > > > > > > > > > > > > > > when I checked cat /dev/sndstat it showed that no mixer was loaded, > > > > > > > > which seemed like a fair explanation for the silence, so I dug deeper > > > > > > > > in man sb(4). This turned up an extra option for the Sound Galaxy pro > > > > > > > > card that I am using which should specifically add mixer support - the > > > > > > > > SG card apparently has a slightly different mixer from a basic SB pro > > > > > > > > which includes bass/treble adjustment, and I hoped the problem would be > > > > > > > > solved. > > > > > > > > So I went ahead and added the suggestion from man sb > > > > > > > > > > > > > > > > options __SGNXPRO__ > > > > > > > > > > > > > > > > into the config file, right after the sound devices section, but now > > > > > > > > the kernel doesnt compile any more. After running > > > > > > > > ln -s /usr/local/kernels/MYKERNELFILE > > > > > > > > I then enter as usual: > > > > > > > > /usr/sbin/config MYKERNELFILE > > > > > > > > > > > > > > > > but that's as far as the process gets. The output on the screen is: > > > > > > > > Error > > > > > > > > Unknown option __SGNXPRO__ (line xxx) > > > > > > > > > > > > > > > > I've checked and double-checked the relevant documentation and im sure > > > > > > > > I havnt made a typo or syntax error. > > > > > > > > What's more that specific option seems to have been present going back > > > > > > > > quite a few releases, so I'm truly puzzled why config wont accept it > > > > > > > > > > > > > > > > Has anyone else got experience with this kind of card, or with > > > > > > > > options parameters for soundcards generally, or should I be thinking > > > > > > > > about reporting this to bugs ? > > > > > > > > > > > > > > > > thanks in advance > > > > > > > > Jean-Mark Dupoux > > > > > > > > jmdupoux_@_lineone.net > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-multimedia" in the body of the message > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > John L. Utz III > > > > > > > john@utzweb.net > > > > > > > > > > > > > > Idiocy is the Impulse Function in the Convolution of Life > > > > > > > > > > > > > > > > -- > > > > > > > > > > John L. Utz III > > > > > john@utzweb.net > > > > > > > > > > Idiocy is the Impulse Function in the Convolution of Life > > > > > > > > > > > > > > > > > > > -- > > > > > > John L. Utz III > > > john@utzweb.net > > > > > > Idiocy is the Impulse Function in the Convolution of Life > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-multimedia" in the body of the message > > > > -- > > John L. Utz III > john@utzweb.net > > Idiocy is the Impulse Function in the Convolution of Life --------------DD7FE1464D07CA410EF55C74 Content-Type: text/plain; charset=us-ascii; name="JM5X86" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="JM5X86" # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.34 2001/08/12 13:13:46 joerg Exp $ machine i386 #cpu I386_CPU cpu I486_CPU #cpu I586_CPU #cpu I686_CPU ident JM5X86 maxusers 8 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=6000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers #device aac # Adaptec FSA RAID, Dell PERC2/PERC3 #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family #device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 #device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card #device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 #device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports #device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') #device txp # 3Com 3cR990 (``Typhoon'') #device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device pcn # AMD Am79C97x PCI 10/100 NICs #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device wx # Intel Gigabit Ethernet Card (``Wiseman'') #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # 'device ed' requires 'device miibus' device ed0 at isa? port 0x300 irq 15 iomem 0xC8000 #device ex #device ep #device fe0 at isa? port 0x300 # Xircom Ethernet #device xe # PRISM I IEEE 802.11b wireless NIC. #device awi # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attachment needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. #device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # Multimedia support # Sound card - aztech audio galaxy pro II cs4231 device pcm device sb0 at isa? port 0x220 irq 5 drq 0 flags 0x11 # commented trash .... # device snd0 # device sbmidi0 at isa? port 0x330 irq 9 # device mss0 at isa? port 0x530 irq 7 drq 5 # flags 0x11 # device sbmidi0 at isa? port 0x330 irq 9 # device opl0 at isa? port 0x388 # device joy0 at isa? port 0x200 # options CONFIG_SBPRO # options __SGNXPRO__ # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet --------------DD7FE1464D07CA410EF55C74-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CBFC055.B8D12949>