pcic.ko recent changes to sys/pccard/*
Hi, I'm running FreeBSD 4.0-CURRENT on my laptop, a Dell Inspiron 7000. I successfully got my 3Com Megahertz 3C574B Ethernet PC-Card to work under 4.0-CURRENT (sources as of September 29, 1999 @ 10AM EDT, before marcel's infamous signal.h commits). CVSup'ing recently and finally successfully remaking world, I find that the sys/pccard/* has changed somewhat. Looking through the cvsweb changes, I see Warner's message about changing the PCMCIA support lines in the kernel configfile, so I did that. (see cvs log messages for src/sys/pccard/pccard.c,v 1.89) But it doesn't work. I'm assuming that my kernel config file's settings do not affect make world in any way, and thus it seems that pcic.ko is not being built by make world anymore... Thus, /dev/card0 is reported as "Device not configured" upon boot (because kldload can't find pcic.ko in /modules or elsewhere). What's going on here? Is the Makefile in src/sys/modules/pcic borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem likely, as the last time it was changed was for the $Id$ - $FreeBSD$ change, which of course was mostly propagated by Peter Wemm. And it wasn't relevant to pcic anyway. So where is it breaking? It's either breaking in a Makefile I missed somewhere, or the pcic code is broken, or I'm broken (being egotistical, I doubt it ;). --Will Andrews [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
how to allocate a resource at new-bus architecture?
Hi, all. I have a question about a resource allocation at a child device of PCI device. I'm thinking about to write a CardBud device driver. CardBus is attached at PCI bus. So I think CardBus is a child device of PCI device. Before revision 1.122 of @src/sys/pci/pci.c, I can allocate a resouce when I set rid 0 and call bus_alloc_resource(). CardBus driver is a child of PCI driver, so bus_alloc_resource(), called at CardBus driver, call pci_alloc_resource(). When rid == 0, pci_alloc_resource() call an resource allocation method of parent bus. But revision 1.122 or later, pci_alloc_resource() was rewritten very simply. pci_alloc_resource() only call resource_list_alloc() and resource_list_alloc() returns 0 when requested resource is not registered nor reserved. It seems me new PCI driver assume all resources are assigned by BIOS. But a BIOS of my notebood, VAIO 818/Phoenix BIOS, does not assign a resource for a CardBus socket/ExCA base address register. #of cource, I set a BIOS as 'Plug Play O/S: No'. I can't allocate a resource using bus_alloc_resource(). How to allocate a resource for a device which resources are not assigned by BIOS? What is a right way to allocate a resource in a new-bus device driver? Thanks, --- YAMAMOTO ShigeruInternet Initiative Japan Inc. [EMAIL PROTECTED] Network Engineering Div. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Signal 12 during build of -current
I'm installing -current on a FreeBSD-3.3-stable system. I've done the sup (which succeeded with no problems). When I try the "make buildworld" I get "signal 12" crashes during the gcc lib build. In specific: I had the same problem (see my mail from 12th October). One of the present requirements is to build, install and boot the new kernel before doing the make world. Please read src/UPDATING, an excellent reference for major events in the source tree: 19990929: The sigset_t datatype has been changed from an integral type to a compound type and can hold 128 signals. Syscalls directly or indirectly using the new sigset_t have been added as to maintain compatible with existing binaries. A new kernel must be made and installed and booted with before a make world can be done. As you start from a v3 system, the v4 kernel might not work with v3 user land. I would suggest to grab an older v4 tree (e.g. as of September, 14th) and to move your v3 to that older v4 first. If this succeded, grab the latest v4 and try to jump over the sigset_t hurdle as described. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current unable to attach USB, Power Mgmt, sound
pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 This is an Abit BP6 board with two Celeron 366, 256 MByte memory, one Soundblaster PCI 128 (pcm0) and one Hoontech (pcm1) sound card. Below is the complete dmesg from today's current, and the kernel config. I reported the same problem. PCI 128 uses the same ES1370 chip as the Audio PCI. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: QIC ft0 driver support in 4.0-CURRENT gone?
Jacques Vidrine [EMAIL PROTECTED] writes: I have one (colorado thing). I _will not_ adopt it :-) but I'd happily send it to a committer that wanted to support it. I haven't used it in years, but AFAIK it still works. I have an old Conner drive and three 40MB tapes which I will happily donate to any poor S.O.B. who hates life enough to take it upon himself to maintain the ft0 driver. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is it just me or is sys/signal.h just completely screwed up now?
I've got a box running yesterday's -current and it can't compile or install things like XFree86 or ImageMagik due to syntax errors in this file. See the mails from October 15th, esp. the ones from Marcel Moolenaar and Sheldon Hearn. It seems this patch has not been commited yet. Anyone got problems? Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is it just me or is sys/signal.h just completely screwed up now?
See the mails from October 15th, esp. the ones from Marcel Moolenaar and Sheldon Hearn. I did, but they don't fix the XFree86 3.3.5 build problem. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is it just me or is sys/signal.h just completely screwed up now?
On Mon, 18 Oct 1999 01:52:57 MST, "Jordan K. Hubbard" wrote: See the mails from October 15th, esp. the ones from Marcel Moolenaar and Sheldon Hearn. I did, but they don't fix the XFree86 3.3.5 build problem. Hmmm, that's odd, because the patch Marcel sent me was later committed to signal.h as rev 1.22 -- and it did indeed fix the Xfree86 3.3.5 ``make install'' problem for me. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: jumping from 3.1 to 4.0
On Sun, 17 Oct 1999, Daniel C. Sobral wrote: You could do that, and it would load your kernel. Your best option, though, it's to jump first to 3.3-stable. I've got the -currents' snap loader for the 10th of october. It works fine - i've managed to load 3.x and 4.x kernels. But before you do that, could you please give me the error log? Loader should have *not* been affected by the signal changes! I don't know. I think there was some headers include absence. Error log is in attachment. === ficl cc -O -pipe -I/usr/src/sys/boot/ficl -DFICL_TRACE -c /usr/src/sys/boot/ficl/dict.c -o dict.o cc -O -pipe -I/usr/src/sys/boot/ficl -DFICL_TRACE -c /usr/src/sys/boot/ficl/ficl.c -o ficl.o cc -O -pipe -I/usr/src/sys/boot/ficl -DFICL_TRACE -c /usr/src/sys/boot/ficl/math64.c -o math64.o cc -O -pipe -I/usr/src/sys/boot/ficl -DFICL_TRACE -c /usr/src/sys/boot/ficl/stack.c -o stack.o cc -O -pipe -I/usr/src/sys/boot/ficl -DFICL_TRACE -c /usr/src/sys/boot/ficl/sysdep.c -o sysdep.o cc -O -pipe -I/usr/src/sys/boot/ficl -DFICL_TRACE -c /usr/src/sys/boot/ficl/vm.c -o vm.o cc -O -pipe -I/usr/src/sys/boot/ficl -DFICL_TRACE -c /usr/src/sys/boot/ficl/words.c -o words.o (cd /usr/src/sys/boot/ficl/softwords; cat softcore.fr jhlocal.fr marker.fr freebsd.fr ficllocal.fr ifbrack.fr | awk -f softcore.awk) softcore.c cc -O -pipe -I/usr/src/sys/boot/ficl -DFICL_TRACE -c softcore.c -o softcore.o building standard ficl library ranlib libficl.a === i386 === i386/mbr (cd /usr/src/sys/boot/i386/mbr; m4 mbr.m4 mbr.s) | as -o mbr.o ld -N -e start -Ttext 0x600 -o mbr.out mbr.o objcopy -S -O binary mbr.out mbr === i386/boot0 (cd /usr/src/sys/boot/i386/boot0; m4 -DFLAGS=0xf -DTICKS=0xb6 boot0.m4 boot0.s) | as -o boot0.o ld -N -e start -Ttext 0x600 -o boot0.out boot0.o objcopy -S -O binary boot0.out boot0 === i386/kgzldr (cd /usr/src/sys/boot/i386/kgzldr; m4 -DSIOPRT=0x3f8 /usr/src/sys/boot/i386/kgzldr/start.s) | as -o start.o cc -fno-builtin -O -DKZIP -c /usr/src/sys/boot/i386/kgzldr/boot.c cc -fno-builtin -O -DKZIP -c /usr/src/sys/boot/i386/kgzldr/../../../kern/inflate.c cc -fno-builtin -O -DKZIP -c /usr/src/sys/boot/i386/kgzldr/lib.c (cd /usr/src/sys/boot/i386/kgzldr; m4 -DSIOPRT=0x3f8 /usr/src/sys/boot/i386/kgzldr/crt.s) | as -o crt.o (cd /usr/src/sys/boot/i386/kgzldr; m4 -DSIOPRT=0x3f8 /usr/src/sys/boot/i386/kgzldr/sio.s) | as -o sio.o cc -nostdlib -static -r -o kgzldr.o start.o boot.o inflate.o lib.o crt.o sio.o === i386/btx === i386/btx/btx (cd /usr/src/sys/boot/i386/btx/btx; m4 btx.m4 btx.s) | as -o btx.o ld -N -e start -Ttext 0x9000 -o btx.out btx.o objcopy -S -O binary btx.out btx === i386/btx/btxldr cc --assembler-with-cpp -c -o btxldr.o /usr/src/sys/boot/i386/btx/btxldr/btxldr.s ld -N -e start -Ttext 0x10 -o btxldr.out btxldr.o objcopy -S -O binary btxldr.out btxldr === i386/btx/lib as -elf -o btxcsu.o /usr/src/sys/boot/i386/btx/lib/btxcsu.s as -elf -o btxsys.o /usr/src/sys/boot/i386/btx/lib/btxsys.s as -elf -o btxv86.o /usr/src/sys/boot/i386/btx/lib/btxv86.s ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o === i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2/dev/null cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -O -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c /usr/src/sys/boot/i386/boot2/boot2.c (cd /usr/src/sys/boot/i386/boot2; m4 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 sio.s) | as -o sio.o ld -nostdlib -static -N -Ttext 0x1000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x1000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.01 size=700 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=1458 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1d58 text=200 data=1b58 org=0 entry=0 168 bytes available dd if=boot2.ld of=boot2 obs=7680 conv=osync 2/dev/null === i386/libi386 cc -O -pipe -I/usr/src/sys/boot/i386/libi386/../../common -I/usr/src/sys/boot/i386/libi386/../btx/lib -I/usr/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DTERM_EMU -c /usr/src/sys/boot/i386/libi386/aout_freebsd.c -o aout_freebsd.o *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. In file included from /usr/src/sys/boot/i386/libi386/../../../sys/signal.h:236, from /usr/src/sys/boot/i386/libi386/../../../sys/param.h:90, from /usr/src/sys/boot/i386/libi386/aout_freebsd.c:29:
aic driver camified
After the recent signal related changes, the pre-cam kernel I saved a long time ago no longer works with (even statically compiled) user applications, which meant I had no way to access my files on an old disk hanging off an aic6360 card. So I decided to bite the bullet and camify the aic driver myself (I've long given up hope someone else would do it.) The source is at http://www.freebsd.org/~luoqi/aic. Copy the source files into sys/dev/aic, apply the patch files.diff to sys/conf/files. Don't forget to add the controller aic0 line back to your config file. Since I don't have *any* documentation on the chip or card, except for the existing source code (FreeBSD/NetBSD/Linux), and my knowledge of our cam implementation is quite limited, so consider this code extremely experimental and use at your own risk. DMA is not supported, sync transfer is supported but not tested, neither pnp nor pccard is supported. My card doesn't support any of these, so there's not much I could do, I hope sopme of you could fill in the blanks. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Promise Ultra66 IDE adapter
Is the Promise Ultra66 IDE adapter supported? I cannot get 3.3 or 4.0 kernels to see the card at all. The mailing list archive details are sketchy at best. The pci_ide source seems to only do support for the Ultra33. Thanks, Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current unable to attach USB, Power Mgmt, sound
pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 This is an Abit BP6 board with two Celeron 366, 256 MByte memory, one Soundblaster PCI 128 (pcm0) and one Hoontech (pcm1) sound card. Below is the complete dmesg from today's current, and the kernel config. I reported the same problem. PCI 128 uses the same ES1370 chip as the Audio PCI. The following patch from Doug Rabson fixed the USB and sound problem for me. It has already bee committed to -current. It did not fix the power management (intpm0) problem. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] -- RCS file: /home/ncvs/src/sys/pci/pci.c,v retrieving revision 1.122 diff -u -r1.122 pci.c --- pci.c 1999/10/14 21:38:31 1.122 +++ pci.c 1999/10/16 19:11:27 @@ -1032,7 +1032,7 @@ #endif if (type == SYS_RES_IOPORT !pci_porten(cfg)) continue; - if (type == SYS_RES_IOPORT !pci_memen(cfg)) + if (type == SYS_RES_MEMORY !pci_memen(cfg)) continue; resource_list_add(rl, type, reg, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcic.ko recent changes to sys/pccard/*
In message [EMAIL PROTECTED] Will Andrews writes: : But it doesn't work. I'm assuming that my kernel : config file's settings do not affect make world in any way, : and thus it seems that pcic.ko is not being built by make world : anymore... What doesn't work? Can you give some error messages as well as a complete dmesg? : What's going on here? Is the Makefile in src/sys/modules/pcic : borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem : likely, as the last time it was changed was for the $Id$ - : $FreeBSD$ change, which of course was mostly propagated : by Peter Wemm. And it wasn't relevant to pcic anyway. The pcic module is borked and hasn't worked for a long time. I'm off to FreeBSD con here in a few minutes, but will read your reply when I get there. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT `make world` fails.. (ucontext.h?)
[cc'ing Marcel just in case he wants to volunteer any suggestion... :)] [also cc'ing Mike Smith since aout_freebsd.c seems to be his] [and cc'ing Peter too, since he dabbed a lot in that file] Will Andrews wrote: ... Is there any additional information I can provide (I noticed a related thread, but DCS's reply didn't seem to help..)? I'm tracking this now. Well, I'll start tracking as soon as I finish my mail. I suggested first upgrading to 3.3 (or even 3.2), and only then to current. That _will_ work, as it will upgrade the loader. Alas, you need not even go to such pains. Just cvsup to -stable, cd /sys/boot; make depend make all install, and then cvsup to -current, make the kernel, etc, etc. The person who first reported the problem said he succesfully used the loader from a recent snap. That will work. Go to a near FreeBSD ftp site, get the "loader" binary from a snapshot, copy it to /boot, and that will be able to load a -current kernel. Alternatively (I just thought of it), you might want to interrupt the boot at boot2 (press any key while the | is being displayed), and boot the kernel directly from there, avoiding going through loader. I'd be interested in hearing whether this can be used as a work-around or not. As for the problem it goes like this: FreeBSD 3.1's loader was not capable of loading a kernel at a different base address than the one FreeBSD used up to that point. Unfortunately, this resulted in an annoying bug that affected machines with lots of RAM and big maxusers (like, for instance, 256). This was corrected by moving the base address of kernel, which required modifications to loader. Thus, FreeBSD's 3.1 loader is not capable of booting a current kernel. Now, aout_freebsd.c (and possibly other files) in sys/boot/i386/libi386 includes sys/param.h, which, in turn, includes sys/signal.h. The later requires machine/ucontext.h, which is not present. Why the newer signal.h is found but not ucontext.h, I'll find out shortly (I hope :). For now, I'm working with the hypothesis of a "file.h" instead of file.h #include. All things considered, this isn't much of a problem in itself. There is a huge problem here,though. Generally speaking, loader is immune to world troubles, since it uses libstand. But, are we not risking chicken-and-egg problems such as this by including standard sys/*.h? Situations where newer loaders are needed to boot a new kernel (as much as we would like loader to be able to handle all future kernels), but not being able to build them until a newer kernel is booted? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcic.ko recent changes to sys/pccard/*
On 18-Oct-99 Warner Losh wrote: In message [EMAIL PROTECTED] Will Andrews writes: : But it doesn't work. I'm assuming that my kernel : config file's settings do not affect make world in any way, : and thus it seems that pcic.ko is not being built by make world : anymore... What doesn't work? Can you give some error messages as well as a complete dmesg? I could give you a complete dmesg and error messages.. but I'll have to read them off argon (the laptop sitting next to me), since argon's only Internet connection _was_ through that PC-Card Ethernet card. :-) Let me try...: 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 #0: Mon Oct 18 03:13:00 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ARGON Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (300.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT, PSE36,MMX,FXSR real memory = 134217728 (131072K bytes) avail memory = 127410176 (124424K bytes) Preloaded elf kernel "kernel" at 0xc028b000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028b09c. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge 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 vga-pci0: ATI model 4c42 graphics accelerator irq 11 at device 0.0 on pci1 pcic0: TI PCI-1220 PCI-CardBus Bridge at device 4.0 on pci0 pcic1: TI PCI-1220 PCI-CardBus Bridge at device 4.1 on pci0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 devclass_alloc_unit: pcic0 already exists, using next available unit number devclass_alloc_unit: pcic1 already exists, using next available unit number isa0: ISA bus on isab0 ide_pci0: Intel PIIX4 Bus-master IDE controller at device 7.1 on pci0 chip1: UHCI USB controller irq 11 at device 7.2 on pci0 chip2: Intel 82371AB Power management controller at device 7.3 on pci0 pci0: unknown card (vendor=0x125d, dev=0x1968) at 8.0 irq 5 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): IBM-DADA-26480 wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 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 ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) on COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold plip0: PLIP network interface on ppbus 0 pccard: initializing drivers: ep changing root device to wd0s2a --- Here's /usr/src/sys/i386/conf/ARGON: # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.192 1999/09/22 05:07:49 wpaul Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident ARGON maxusers100 makeoptions DEBUG=-g options INET options FFS options FFS_ROOT options MSDOSFS options CD9660 options CD9660_ROOT options PROCFS options COMPAT_43 options SCSI_DELAY=15000 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options SOFTUPDATES options NO_F00F_HACK options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options IDE_DELAY=8000 device pcm0 controller isa0 controller pnp0 controller pci0 controller fdc0at isa? port IO_FD1 irq 6 drq 2 diskfd0 at fdc0 drive 0 controller wdc0at isa? port IO_WD1 irq 14 diskwd0 at wdc0 drive 0 diskwd1 at wdc0 drive 1 device wcd0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? conflicts device sc0 at isa? options XSERVER device npx0at nexus? port IO_NPX irq 13 device apm0at nexus? disable flags 0x31 controller pcic0 at isa? controller pcic1 at isa? controller card0 device sio0at isa? port IO_COM1 flags 0x10 irq 4 device ppc0at isa? port? flags 0x40 irq 7 controller ppbus0 device lpt0 device plip0
Re: -CURRENT `make world` fails.. (ucontext.h?)
On 18-Oct-99 Daniel C. Sobral wrote: I'm tracking this now. Well, I'll start tracking as soon as I finish my mail. I suggested first upgrading to 3.3 (or even 3.2), and only then to current. That _will_ work, as it will upgrade the loader. Alas, you need not even go to such pains. Just cvsup to -stable, cd /sys/boot; make depend make all install, and then cvsup to -current, make the kernel, etc, etc. Yes, that's how I did it. Actually, I had 3.3-RELEASE.. I downloaded the entire -CURRENT CVS repository so I could get sources for September 29, before marcel's changes. Then I burned those sources to a CD-R, and loaded it on my laptop. Made world, rebooted, and I'm in 4.0-CURRENT. Then after several unsuccessful attempts to do a newer world, I finally got it. argon.blackdawn.com (my laptop) is _NOW_ running 4.0-CURRENT as of October 17, 1999 @ 9PM EDT. Only one problem is left - my pccard isn't working. I'm working with Warner Losh on that... (hopefully something good will come out of that.) The person who first reported the problem said he succesfully used the loader from a recent snap. That will work. Go to a near FreeBSD ftp site, get the "loader" binary from a snapshot, copy it to /boot, and that will be able to load a -current kernel. Interesting. All I did was rebuild the kernel again and tried another make world. For some reason, the system wanted me to build the same kernel twice. Or maybe I cvsup'd more than once, and didn't build a new kernel the second or third time. I don't know. :) I didn't try a bootloader off the ftp sites.. that wouldn't have worked for me anyway, since pccard support broke around the time I got to the bootloader in `make world`. I mean, it broke 'cause I lost my old Sept. 29 kernel. I forgot to keep a backup copy of it.. :\ As for the problem it goes like this: FreeBSD 3.1's loader was not capable of loading a kernel at a different base address than the one FreeBSD used up to that point. Unfortunately, this resulted in an annoying bug that affected machines with lots of RAM and big maxusers (like, for instance, 256). This was corrected by moving the base address of kernel, which required modifications to loader. Thus, FreeBSD's 3.1 loader is not capable of booting a current kernel. Perhaps people need to install a new boot loader first (one that is of 4.0-CURRENT lineage), as you suggested. Then perhaps building a -CURRENT kernel, and rebooting. Of course, I dunno if that'd work, given the differing kernel and world.. Now, aout_freebsd.c (and possibly other files) in sys/boot/i386/libi386 includes sys/param.h, which, in turn, includes sys/signal.h. The later requires machine/ucontext.h, which is not present. Why the newer signal.h is found but not ucontext.h, I'll find out shortly (I hope :). For now, I'm working with the hypothesis of a "file.h" instead of file.h #include. Yes, I thought the machine/ucontext.h was the problem. Is "machine/ucontext.h" under /usr/src somewhere? I thought I saw one, but couldn't seem to finger its precise path. All things considered, this isn't much of a problem in itself. There is a huge problem here,though. Generally speaking, loader is immune to world troubles, since it uses libstand. But, are we not risking chicken-and-egg problems such as this by including standard sys/*.h? Situations where newer loaders are needed to boot a new kernel (as much as we would like loader to be able to handle all future kernels), but not being able to build them until a newer kernel is booted? Like I said above, a -CURRENT kernel may have problems with a -STABLE world. I'm honestly not fully aware of the dependencies regarding the signal changes (i.e., ucontext.h), so my thoughts may be completely wrong. :-) Comments? -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Luoqi Chen wrote: DMA is not supported, sync transfer is supported but not tested, neither pnp nor pccard is supported. My card doesn't support any of these, so there's not much I could do, I hope sopme of you could fill in the blanks. Looks pretty good. I'll whip up an MCA front end and try it out when I get home. I suspect someone will want a PCCARD front end as well. I'll write it if someone will work with me on testing. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT `make world` fails.. (ucontext.h?)
[removing cc's, since I addressed them in another message in another
thread in another list :]
Will Andrews wrote:
Yes, that's how I did it. Actually, I had 3.3-RELEASE.. I downloaded the entire
If you had 3.3-RELEASE, you wouldn't need a new loader to load the
-current kernel. That's not true of someone who had 3.1-RELEASE.
Now, aout_freebsd.c (and possibly other files) in
sys/boot/i386/libi386 includes sys/param.h, which, in turn, includes
sys/signal.h. The later requires machine/ucontext.h, which is not
present. Why the newer signal.h is found but not ucontext.h, I'll
find out shortly (I hope :). For now, I'm working with the
hypothesis of a "file.h" instead of file.h #include.
Yes, I thought the machine/ucontext.h was the problem. Is
"machine/ucontext.h" under /usr/src somewhere? I thought I saw one, but
couldn't seem to finger its precise path.
Actually, now that I spent a few minutes witht he code, it's obvious
that I was way short-sighted in this. The analysis above is too
naive, and, to be blunt, dumb. :-) Obviously, /usr/src/sys/machine/*
cannot be found, because it does not exist. /usr/include/machine/*
is generated from /usr/src/sys/${MACHINE_ARCH}/include. The makefile
uses -I so that sys/* files will be found under /usr/src/sys
(well, not exactly -- it uses a relative path, but that's the gist
of it :), but the machine/* files included by those cannot be
found.
Thus, we have a situation in which some of the include files are the
latest (sys/*.h), and some are not (machine/*.h).
The problem is triggered by machine/ucontext.h, but it could have
been triggered by a number of other files. It's just not a simple
problem to solve. :-(
Like I said above, a -CURRENT kernel may have problems with a -STABLE world.
I'm honestly not fully aware of the dependencies regarding the signal changes
(i.e., ucontext.h), so my thoughts may be completely wrong. :-)
Comments?
You ought to say that a -STABLE world will have problems with a
-CURRENT kernel. The kernel ought to be immune to -STABLE world's
problems. :-) In a perfect world, anyway. :-) Anyway, there are
problems a -STABLE world will have with a -CURRENT kernel, but they
are not likely to be crippling (ie, you should be able to make world
after booting the new kernel). One thing that *can* bite is the use
of klds. Bad ju ju may result from the use of old klds with a new
kernel.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Luoqi Chen wrote: After the recent signal related changes, the pre-cam kernel I saved a long time ago no longer works with (even statically compiled) user applications, which meant I had no way to access my files on an old disk hanging off an aic6360 card. So I decided to bite the bullet and camify the aic driver myself (I've long given up hope someone else would do it.) Luoqi, you are a god. I bow to thee. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: workaround for ata driver woes on alpha
On 1999 Oct 18, Andrew Gallatin (aka [EMAIL PROTECTED]) wrote: BTW -- I just talked to a collegue here who's getting screwed by ad_timeout() with a very slow disk on a pc. It sounds like it could be the same problem. Hi- I would be that induhvidual. I have x86 box at home running current as of last night that began to behave this way: FreeBSD bobzilla 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Oct 17 21:45:50 EDT 1999 sto@bobzilla:/usr/src/sys/compile/BOBZILLA i386 ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ad0: WDC AC23200L/09.09M08 ATA-4 disk at ata0 as master ad1: ST5540A/09.09.01 ATA-? disk at ata1 as slave acd0: CD-532E/1.0A CDROM drive at ata1 as master ata1-slave: ad_timeout: lost disk contact - resetting ata1: resetting devices .. done Once this ad_timeout happened, I was hosed. I had to power cycle my way out of a shutdown.. and upon reboot, the file system was completely toast. newfs was my only way out... fortunately, this was just my /usr/obj directory, so I am not too concerned about the lost data. Of course, this could just be a sign of the imminent demise of this drive. Hope this helps. S -- --- Sean O'ConnellEmail: [EMAIL PROTECTED] Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
adv hanging at boot
Current, cvsup'ed daily. My adv is hanging now at "Waiting 5 seconds for SCSI devices to settle" Two weeks or so it then gave 4 messages about "bus timeout" or so (Sorry I can't remember the exact wording; it doesn't say so now.) It has ben non-functional for a month or so. I only have a HP4020i cd-writer on the bus, so it's not that important... It works nicely under windows, and also used to work under Fbsd. I can still boot an older kernel, but it won't run with the current userland. Here is a dmesg with adv disabled in userconfig to get something to send you. 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 #118: Sat Oct 16 04:42:50 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/GINA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (337.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 67096576 (65524K bytes) VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc00c0e38 (ce38) VESA: S3 Incorporated Trio3D. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge 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 vga-pci0: S3 model 8904 graphics accelerator at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 IDE controller at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller irq 9 at device 4.2 on pci0 uhci0: could not map ports device_probe_and_attach: uhci0 attach returned 6 intpm0: Intel 82371AB Power management controller at device 4.3 on pci0 intpm0: Could not allocate Bus space device_probe_and_attach: intpm0 attach returned 6 pcm0: AudioPCI ES1370 irq 5 at device 11.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 ed1: NE2000 PCI Ethernet (RealTek 8029) irq 10 at device 12.0 on pci0 ed1: address 00:80:ad:50:40:cf, type NE2000 (16 bit) 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 adv0: not probed (disabled) 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: model Generic PS/2 mouse, device ID 0 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 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver devclass_alloc_unit: pcf0 already exists, using next available unit number pcf0 at port 0x320 irq 5 on isa0 Gets detected here ---unknown0: ABP5140 at port 0x110-0x11f iomem 0xc8000-0xc807f irq 11 drq 5 on isa0 ad0: ST38641A/3.11 ATA-4 disk at ata0 as master ad0: 8207MB (16809660 sectors), 16676 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ad1: IBM-DTTA-350640/T54OA73A ATA-4 disk at ata0 as slave ad1: 6197MB (12692295 sectors), 13431 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 31 depth queue, UDMA33 Creating DISK ad1 Creating DISK wd1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: BCD-48SB CD-ROM/VER 2.8 CDROM drive at ata1 as slave acd0: read 343KB/s (7562KB/s), 128KB buffer, DMA acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd1s3a My config: machine i386 cpu I686_CPU ident "GINA" maxusers32 options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options NFS #Network Filesystem 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!]
Re: pcic.ko recent changes to sys/pccard/*
On Mon, Oct 18, 1999 at 12:25:48PM -0400, Will Andrews wrote: If you don't believe me when I say that pcic _was_ working for the Sept. 29 sources: The pcic modules is *KNOWN* to have and cause problems. Warner told you this and you still insist on pushing the issue. Why? NO FreeBSD developer uses the pcic *module*, thus it is quite unwise for you to be using it as we no longer test it or keep it in sync with the rest of the kernel. : What's going on here? Is the Makefile in src/sys/modules/pcic : borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem : likely, as the last time it was changed was for the $Id$ - The building of modules/pcic was removed from /sys/modules/Makefile. Check the history on that file. The pcic module is borked and hasn't worked for a long time. Actually, it worked for me in my last world - September 29, 1999 @ 10AM EDT. STOP USING IT!!! I disabled it in -STABLE and -CURRENT quite some time ago. How is it you are even compiling and installing it? Please statically compile it into your kernel so developer's time isn't wasted on this. We have known problems for PCIMCA modems and that is where the pccard developer's time needs to be spent. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
I suspect someone will want a PCCARD front end as well. I'll write it if someone will work with me on testing. You have a guinie pig^W^Wtester. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcic.ko recent changes to sys/pccard/*
On 18-Oct-99 David O'Brien wrote: On Mon, Oct 18, 1999 at 12:25:48PM -0400, Will Andrews wrote: If you don't believe me when I say that pcic _was_ working for the Sept. 29 sources: The pcic modules is *KNOWN* to have and cause problems. Warner told you this and you still insist on pushing the issue. Why? NO FreeBSD developer uses the pcic *module*, thus it is quite unwise for you to be using it as we no longer test it or keep it in sync with the rest of the kernel. No, no... see below. : What's going on here? Is the Makefile in src/sys/modules/pcic : borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem : likely, as the last time it was changed was for the $Id$ - The building of modules/pcic was removed from /sys/modules/Makefile. Check the history on that file. The pcic module is borked and hasn't worked for a long time. Actually, it worked for me in my last world - September 29, 1999 @ 10AM EDT. STOP USING IT!!! I disabled it in -STABLE and -CURRENT quite some time ago. How is it you are even compiling and installing it? Please statically compile it into your kernel so developer's time isn't wasted on this. We have known problems for PCIMCA modems and that is where the pccard developer's time needs to be spent. I apologize for causing undue freaking-out... I am confused. :) First things first. After this message, I'm going to read the -current archives regarding pccard. Second, it should be noted that I don't see how I could ever have used the pcic module.. if you disabled it before September 29, then it must have been kernel support. My old logs show no indication that any module was loaded before, so if the 9/29 kernel worked, why doesn't the current kernel work with my pccard? I made the appropriate changes that Warner mentioned in the cvs logs for src/sys/pccard/pccard.c, v1.89, as I said before. Third, part of my confusion is due to /etc/rc.pccard, which seems to attempt to load the module. Since I received no errors before (in the 9/29 world/kernel) about kldload failing, it seems like there WAS indeed a pcic.ko module (because now, since there is no module, kldload gives an error on booting up: "can't find module pcic".) I would never use any deprecated software. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current unable to attach USB, Power Mgmt, sound
On Mon, 18 Oct 1999, Marc van Woerkom wrote: pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 This is an Abit BP6 board with two Celeron 366, 256 MByte memory, one Soundblaster PCI 128 (pcm0) and one Hoontech (pcm1) sound card. Below is the complete dmesg from today's current, and the kernel config. I reported the same problem. PCI 128 uses the same ES1370 chip as the Audio PCI. The Vibra128 (which is PCI) uses the Ensoniq chip, but I'm not so sure the PCI128 does. I just found this out the hard way on 56 new systems. I wanted the SB16 ISA, couldn't get that, so I was going to get an AWE64 ISA, couldn't get that either (curse you, Creative, for discontinuing those cards). Got what I THOUGHT was the PCI128, which turned out to be the Vibra128, which is a very different animal as far as the Windows drivers are concerned. It hasn't done too bad so far, though we're running Win95, not FreeBSD (yet). The wavetable samples don't appear to exist in any kind of onboard RAM, so I'm not entirely sure just how "hardware" the wavetable is at all. -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI Hardware Modem (Really)
Well, Windows 98 recognizes it as a PCI Serial Controller before I install a driver, is there any way to direct the sio to look at the pci bus? Bill [EMAIL PROTECTED] - Original Message - From: Steve O'Hara-Smith [EMAIL PROTECTED] To: Bill A. K. [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; FreeBSD Questions [EMAIL PROTECTED] Sent: Monday, October 18, 1999 8:03 AM Subject: RE: PCI Hardware Modem (Really) On 15-Oct-99 Bill A. K. wrote: Hi, I've got a Rockwell PCI Modem thats full hardware, and I was wondering if anybody has written a driver for this kind yet. If it really is a full hardware modem then the driver has been around for a while, called sio. If you mean something like the Lucent which has all the signal processing hardware but no serial port or command processing, then there is an alpha work in progress going on. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current unable to attach USB, Power Mgmt, sound
The following patch from Doug Rabson fixed the USB and sound problem for me. It has already bee committed to -current. Thanks for that hint. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Luoqi Chen wrote: After the recent signal related changes, the pre-cam kernel I saved a long time ago no longer works with (even statically compiled) user applications, which meant I had no way to access my files on an old disk hanging off an aic6360 card. So I decided to bite the bullet and camify the aic driver myself (I've long given up hope someone else would do it.) WOOHOO!! I'll be your guinea pig for trying this on -stable if you like. All I have is a ZIP drive to test things with. If it would make any difference, I could also borrow a Yamaha 4260 CD writer and a Sony SDT-S5200 DDS2 drive. The source is at http://www.freebsd.org/~luoqi/aic. Copy the source files into sys/dev/aic, apply the patch files.diff to sys/conf/files. Don't forget to add the controller aic0 line back to your config file. Should this apply cleanly to -stable? If so, I'll give it a shot when I get home. -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BSD Applications database
Good afternoon, Last month we announced the Linux Applications database for BSD Unix systems. This database has been generalized to include ALL Unix applications and has been moved to its own domain http://www.bsdapps.org/ The generalization is especially import for the NetBSD and OpenBSD groups as these platforms are able to run several Unix applications (from Alpha and Sparc systems for instance) as well. An example in the database can be found here: http://www.bsdapps.org/db/owa/bsdapps$apps.queryview?P_BSDAPPS_ID=109Z_CHK=3989 6 This database is open to anybody. This means that anybody is allowed to insert new applications and/or support notes. This will create an Open Internet initiative in order to support BSD systems in general. Thanks for the support, Remco Moolenaar -- Remco Moolenaar mailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.0-19991012-CURRENT
Has anyone tried using the 4.0-19991012-CURRENT snapshot? I need to confirm that this snapshot is a "good one" before I update my 3.3R installation to it in a last ditch effort to compile USB modem support into the kernel. Thanks, -- Brett White [EMAIL PROTECTED] Duty Programmer, CS130 tutor, 4thYr D/Degree SSCC CQAT rep. "Like the naked leads the blind. I know I'm selfish, I'm unkind." -Placebo 'Every You, Every Me' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The Unofficial AudioPCI/PCI64 Support Page
The Vibra128 (which is PCI) uses the Ensoniq chip, but I'm not so sure the PCI128 does. Walter Lord has set up (and still maintains) a home page when the Ensoniq Audio PCI came out: http://www.netexcite.com/audiopci/index.html You find lots of drivers, the 8 MB wave table sets for the Windows driver and other useful information there. Wish we could use that wave tables for a midi device.. To make a long story short. The original Ensoniq Audio PCI card used the ES1370 chip (PCI control) and the AK4531 codec for AD/DA. Later they made Audio PCI cards with the ES1371 chip. This one seems to be able to use lots of different codecs (that is where the driver fun comes in) that comply to some Intel spec (AC 97), among them the AK4540. All this time, Ensoniq also sold their chips to OEMS, who in turn might have used the same codec or even other stuff. Then Creative came up and bought Ensoniq to get some decent PCI card. The PCI 128 seems to be more or less the same like the Audio PCI (I am not 100% sure, because the latest greatest Win drivers do not work for me anymore), the PCI 64 is reported to have at least a lesser quality code. And more fun: recently people reported an ES1374 chip - I have no clue yet where this one is different. Specs for ES1370 and ES1371: http://www.ensoniq.com/multimedia/semi_html/index.htm Specs for Ashai Kasei AK4531 and AK4543: http://www.akm.com/Text/pdflist.html http://www.asahi-kasei.co.jp/akm/english/p_i/pdf/EK4351.pdf http://www.akm.com/pdf/4543.pdf Specs for Audio Codec '97: http://developer.intel.com/pc-supp/platform/ac97 Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-19991012-CURRENT
Date: Tue, 19 Oct 1999 09:56:49 +1000 From: Brett White [EMAIL PROTECTED] Has anyone tried using the 4.0-19991012-CURRENT snapshot? I need to confirm that this snapshot is a "good one" before I update my 3.3R installation to it in a last ditch effort to compile USB modem support into the kernel. I'm currently using 4.0-19991012-CURRENT and trying -- so far, unsuccessfully -- to break it (as I broke(*) 3.2-R 3.3-R) with a script that does some fairly aggressive file creation/deletion. I haven't done much more than that with it, though. (Well, I persuaded it to "play nice" in our Engineering net, NIS and all. And it uses amd OK.) (I'm stress-testing the machine because I'm trying to set up a new amanda server, and I want to do a better job of it than I did last time. The script is kinda dumb, but moderately effective, at simulating the kind of load an active amanda server puts on ts "holding disk".) *"Broke" as in panic. Called Julian over to have a look; he suggested trying 3.3-R, then a recent CURRENT snap. Panic, as I recall, was whimpering about an attempt to free a vnode that was already marked free. Hope that's useful, david -- David Wolfskill [EMAIL PROTECTED] UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current unable to attach USB, Power Mgmt, sound
On 18-Oct-99 Chris Dillon wrote: though we're running Win95, not FreeBSD (yet). The wavetable samples don't appear to exist in any kind of onboard RAM, so I'm not entirely sure just how "hardware" the wavetable is at all. Probably not at all.. Since Vibra 128's are REALLY cheap, then the 'hardware' wavetable would probably mean that it DMA's wavetable samples from physical RAM when it needs them. --- 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
USB Modem??
Hey there, Has anyone managed to get USB modem support compiled into the 4.0 kernel using the patches from the projects site?? Or can it be done another way?? Unfortunately my 33.6K internal has rolled over and died and now I just have a 56.6K external USB modem which I haven't been able to get the support for yet (hence I can't cvsup to 4.0 like most ppl have suggested, but thanks for the responses anyway!!). See Ya! -- Brett White [EMAIL PROTECTED] How many Tux could the Daemon Chuck slay if the Daemon Chuck could slay Tux? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Chris Dillon wrote: Should this apply cleanly to -stable? If so, I'll give it a shot when I get home. I'll answer my own question (which, oddly enough, still hasn't made it to the list after about two hours). I forgot about newbus. It doesn't work, of course, and my Clue Quotient(TM) isn't high enough to backport this to -stable. I think I'll teach myself how to do this next weekend, if nobody else gets to it. :-) -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD CON and laptops
During this week I have two goals here at FreeBSD con. 1 is to kludge up a working sio driver. The second is to help fix those folks I've broken by my latest changes. Please trip me while I'm here if youare seeing problems. I have most of the sio driver mods done, but I'm doing something silly in newbus so need to talk to dfr, et al, about it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
