From owner-freebsd-hardware Tue Oct 19 17: 9:21 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 25A851823C for ; Tue, 19 Oct 1999 17:09:18 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id CAA29668 for freebsd-hardware@FreeBSD.ORG; Wed, 20 Oct 1999 02:09:17 +0200 (CEST) (envelope-from olli) Date: Wed, 20 Oct 1999 02:09:17 +0200 (CEST) From: Oliver Fromme Message-Id: <199910200009.CAA29668@dorifer.heim3.tu-clausthal.de> To: freebsd-hardware@FreeBSD.ORG Subject: Yamaha YMF744 (soundchip) support? Organization: Administration Heim 3 Reply-To: freebsd-hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've bought a "Guillemot Maxi Sound Fortissimo" sound card, based on a Yamaha YMF744 (YMF744B) chip. Unfortunately, it doesn't look like FreeBSD supports it. Is there someone working on supporting it...? Well, at least I have the ability to return the card (until next Monday) if I can't get it to work at all... Regards Oliver PS: The nice thing about this inexpensive card is that it has a digital optical output (standard connector, like those on CD players). Would be really nice if I could digitally record some mp3s to MD... -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 20 0:38:36 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from relay.rinet.ru (relay.rinet.ru [195.54.192.35]) by hub.freebsd.org (Postfix) with ESMTP id 6D87B1AF92 for ; Wed, 20 Oct 1999 00:37:59 -0700 (PDT) (envelope-from gvs@rinet.ru) Received: from diggy.rinet.ru (diggy.rinet.ru [195.54.192.50]) by relay.rinet.ru (8.9.3/8.9.3) with ESMTP id LAA15826 for ; Wed, 20 Oct 1999 11:37:50 +0400 (MSD) X-Envelope-To: Date: Wed, 20 Oct 1999 11:37:50 +0400 (MSD) From: Seva Gluschenko To: freebsd-hardware@freebsd.org Subject: Winbond 83977EF high-speed async ports Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello folks! Does anybody knows how to get from the Winbond WB83977EF chip serial (async) ports the speed higher than 115200? This hardware pretends to run much higher speeds, but it seems like FreeBSD doesn't know that or I just don't know how to flip the switch. Any ideas will be much appreciated. SY, Seva Gluschenko, just stranger at the Road. | http://gvs.rinet.ru/ Cronyx Plus / RiNet network administrator. | GVS-RIPE | GVS3-RIPN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 21 12:51:16 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with ESMTP id 19DB614DB7 for ; Thu, 21 Oct 1999 12:51:02 -0700 (PDT) (envelope-from paulo@nlink.com.br) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.9.3/8.9.1) with SMTP id RAA10991 for ; Thu, 21 Oct 1999 17:51:01 -0200 (EDT) Date: Thu, 21 Oct 1999 17:51:00 -0200 (EDT) From: Paulo Fragoso To: freebsd-hardware@freebsd.org Subject: DAVICOM Ethernet Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm making little routers using motherboards with video and ethernet on board. This motherbard has one Davicom Ethernet and Davicom's sites there is a driver for Linux: http://www.davicom8.com/drivers/dm9102/LinuxOS2.zip Is possible to port this driver to freebsd? Or are there any plans to include support for that in kernel? I'm thinking use this motherboard because its size and price. I will make very slim routers using small cases with small powers suplly (75W). This router will use serial ports at 230400bps to access external ISDN adapter. Thanks, Paulo Fragoso. ------ " ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else" -David Filo, Yahoo! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 21 19:43:50 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 06AE714E5C for ; Thu, 21 Oct 1999 19:43:41 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id JAA93553; Fri, 22 Oct 1999 09:42:53 +0700 (NOVST) (envelope-from nnd) Date: Fri, 22 Oct 1999 09:42:53 +0700 (NOVST) Message-Id: <199910220242.JAA93553@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: hardware@freebsd.org Subject: Re: DAVICOM Ethernet In-Reply-To: User-Agent: tin/pre-1.4-19990927 ("Nine While Nine") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In Paulo Fragoso wrote: > Hi, > > I'm making little routers using motherboards with video and ethernet on > board. This motherbard has one Davicom Ethernet and Davicom's sites there > is a driver for Linux: > http://www.davicom8.com/drivers/dm9102/LinuxOS2.zip > > Is possible to port this driver to freebsd? Or are there any plans to > include support for that in kernel? > > I'm thinking use this motherboard because its size and price. I will > make very slim routers using small cases with small powers suplly (75W). > This router will use serial ports at 230400bps to access external ISDN > adapter. See the 'dm' device driver in FreeBSD-current. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 21 23:18:46 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 21F5F14F30 for ; Thu, 21 Oct 1999 23:18:43 -0700 (PDT) (envelope-from kozowski@svjava.com) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id XAA26637 for freebsd-hardware@FreeBSD.ORG; Thu, 21 Oct 1999 23:18:42 -0700 (PDT) Date: Thu, 21 Oct 1999 23:18:42 -0700 From: Eric Kozowski To: freebsd-hardware@FreeBSD.ORG Subject: problems installing 3.3 Message-ID: <19991021231842.D25786@schooner.svjava.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i'm having difficulty installing 3.3 on the following system: amptron 3100B motherboard intel p2-400 128m ram buslogic bt-958 scsi controller 2 ibm 4.5g scsi drives diamond mm pro1000gl video keyboard, mouse scsi controller recognizes both disks. disks low level formatted. i can boot off the 3.3 install disks and get through the full screen config. i remove everything but the scsi controller, keyboard, mouse and syscon from the config. system boots w/o errors until it gets to "npx0: INT 16 interface", which is the last line displayed. the system then freezes up. i've played with various combinations of settings in the bios, none of which seem to have any effect. there are no irq conflicts. anyone have any ideas as to what the problem could be? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 22 1: 0: 3 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from rz5.rz.fh-wilhelmshaven.de (rz5.rz.fh-wilhelmshaven.de [139.13.57.132]) by hub.freebsd.org (Postfix) with ESMTP id A1AC314C43 for ; Fri, 22 Oct 1999 00:59:59 -0700 (PDT) (envelope-from ohoyer@fbwi.fh-wilhelmshaven.de) Received: from fettesau.stuwo.fh-wilhelmshaven.de (stuwopc5.stuwo.fh-wilhelmshaven.de [139.13.209.5]) by rz5.rz.fh-wilhelmshaven.de (8.8.7/8.8.5) with SMTP id JAA17229 for ; Fri, 22 Oct 1999 09:59:55 +0200 Message-Id: <4.1.19991022095543.00baf850@mailserv.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mailserv.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 22 Oct 1999 09:59:06 +0200 To: freebsd-hardware@FreeBSD.ORG From: Olaf Hoyer Subject: Re: problems installing 3.3 In-Reply-To: <19991021231842.D25786@schooner.svjava.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 23:18 21.10.99 -0700, you wrote: > >i'm having difficulty installing 3.3 on the following system: > >amptron 3100B motherboard >intel p2-400 >128m ram >buslogic bt-958 scsi controller >2 ibm 4.5g scsi drives >diamond mm pro1000gl video >keyboard, mouse > >scsi controller recognizes both disks. disks low level formatted. > >i can boot off the 3.3 install disks and get through the full >screen config. i remove everything but the scsi controller, keyboard, >mouse and syscon from the config. system boots w/o errors until it >gets to "npx0: INT 16 interface", which is the last line displayed. >the system then freezes up. > Hi! Well, npx0 is the numerical co-processor. In this case it seems that some kind of routing mishappens. Amptron is another name for PCCHips mainboards, like Alton, Eurone, Hsing Tech... IMO, based on some bitter experiences, they range from cheap to crap. In field service, seen lots of them making stress... Well, just a theory. will be happy seeing other guys pointing other= solution. Regards Olaf Hoyer - - - - - - - -=20 Olaf Hoyer ICQ: 22838075 mailto: Olaf.Hoyer@nightfire.de home: www.nightfire.de (The home of the burning CPU) Wer mit Ungeheuern k=E4mpft, mag zusehn,=20 da=DF er nicht dabei zum Ungeheuer wird. Und wenn du lange in einen Abgrund blickst, blickt der Abgrund=20 auch in dich hinein. (Friedrich Nietzsche, Jenseits von Gut und B=F6se) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 22 10:12:42 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C35F514C26 for ; Fri, 22 Oct 1999 10:12:37 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA93529; Fri, 22 Oct 1999 11:12:00 -0600 (MDT) (envelope-from ken) Message-Id: <199910221712.LAA93529@panzer.kdm.org> Subject: Re: Adaptech AHA 1520 support In-Reply-To: <004401bf172d$4cfed700$4d01190a@fw> from Richard Cotrina at "Oct 15, 1999 11:48:17 am" To: rcc@demo.telefonica.com.pe (Richard Cotrina) Date: Fri, 22 Oct 1999 11:12:00 -0600 (MDT) Cc: freebsd-hardware@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Richard Cotrina wrote... > Hi all, > > Is there any way to enable Adaptec AHA 1520 SCSI Host Adapter in FreeBSD > 3.3-CURRENT ? > > Is there any driver, patch o new kernel available ? A driver for the Adaptec 6260/6360 chips just went in the tree a couple of days ago. You'll need a very recent snapshot of -current or -stable to try it out. If you have questions about it, contact Luoqi Chen . Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 23 1: 9: 1 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E43B214D24; Sat, 23 Oct 1999 01:08:51 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA22519; Sat, 23 Oct 1999 02:08:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA28033; Sat, 23 Oct 1999 02:09:07 -0600 (MDT) Message-Id: <199910230809.CAA28033@harmony.village.org> To: Donald Burr Subject: Re: Is VIA VT83C469 PCMCIA controller supported? Cc: FreeBSD Hardware , FreeBSD Mobile In-reply-to: Your message of "Sun, 03 Oct 1999 15:30:55 PDT." References: Date: Sat, 23 Oct 1999 02:09:06 -0600 From: Warner Losh Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Donald Burr writes: : I just picked up a PCMCIA-to-ISA connectivity kit (a card that lets me : plug PCMCIA cards into my desktop computer). It uses the VIA VT83C469 : PCMCIA controller. Is this chipset supported by the PCMCIA drivers in : 3.3-STABLE and/or PAO? (I'd rather not have to move to PAO, though) : : Thanks! (ps: please CC: your replies to me in e-mail, if possible) Don't know. Likely it will probe as a Intel 82365, although it may probe as a Vadem 469. Give it a shot. 3.3 Stable should work. Stay away from -current for a little while with this one... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 23 6: 2:30 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from va.com.au (va.com.au [203.15.106.1]) by hub.freebsd.org (Postfix) with ESMTP id 88BBA14C91; Sat, 23 Oct 1999 06:02:15 -0700 (PDT) (envelope-from jesse@va.com.au) Received: from [1.1.1.3] (203.108.18.244) by va.com.au with ESMTP (Eudora Internet Mail Server 2.2); Sat, 23 Oct 1999 22:32:10 +0930 Mime-Version: 1.0 X-Sender: jesse@mail.va.com.au Message-Id: In-Reply-To: <199910230809.CAA28033@harmony.village.org> References: <199910230809.CAA28033@harmony.village.org> Date: Sat, 23 Oct 1999 23:02:02 +1000 To: FreeBSD Hardware , FreeBSD Mobile From: jesse reynolds Subject: zircom pc-card's on a Fujitsu Lifebook 735Dx Laptop... Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Folx I've recently installed 3.3-RELEASE on this Fujitsu Lifebook 735Dx laptop. I reconfigured and recompiled the kernel with various pc-card components turned on, including the xe driver which is necessary for the zircom cards. The two cards I have are an ethernet only PS-CE2-10, and an ethernet and modem CEM33. I'd be happy to get either of these cards working. I believe I have a CardBus system, not a standard PCMCIA system. I have not yet added the file /etc/pccard.conf because it's here that I am stuck. I don't know what strings to use in this file because pccarcd doesn't work. Output of pccardc is: # pccardc dumpcis Read return -1 bytes (expected 2) pccardc: CIS code read: Cannot allocate memory Read return -1 bytes (expected 10) Configuration data for card in slot 1 2 slots found # So yes, what's happening here? I'm not sure what sort of pccard system is in this Fujitsu, but the following entries from an earlier boot may help: (from dmesg) probing pci bus... (etc) ... chip3: rev 0x01 int a irq 9 on pci0.19.0 chip4: rev 0x01 int b irq 9 on pci0.19.1 ... I've also noticed that in /var/log/messages the kernel is writing messages when I insert and remove cards, as follows: Oct 19 06:47:24 /kernel: Card inserted, slot 1 So it knows when cards are inserted and removed, which is good. Is it the PCI to CardBus bridge that might be a problem? I see in the XE readme that FreeBSD has no support for CardBus systems? I'm including a few files here... /etc/rc.conf output of dmesg /usr/src/sys/i386/conf/FUZZY (my kernel config file) I have posted this to the XE driver list, but Scott Mitchell said I should fire this at freebsd-mobile to see how support for CardBus is going. Cheers Jesse -----------------------/etc/rc.conf : -------------------------- # This file now contains just the overrides from /etc/defaults/rc.conf # please make all changes to this file. # -- sysinstall generated deltas -- # moused_port="/dev/psm0" moused_type="auto" moused_enable="NO" gateway_enable="YES" # -- sysinstall generated deltas -- # moused_enable="YES" ----------------------- dmesg output : -------------------------- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-RELEASE #1: Mon Oct 18 23:58:00 EST 1999 root@fuzzy.syd.va.com.au:/usr/src/sys/compile/FUZZY Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (133.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 33554432 (32768K bytes) config> di sio1 config> di sio0 config> di ppc0 config> di zp0 No such device: zp0 Invalid command or syntax. Type `?' for help. config> di ze0 No such device: ze0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ex0 No such device: ex0 Invalid command or syntax. Type `?' for help. config> di ep0 No such device: ep0 Invalid command or syntax. Type `?' for help. config> di ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> q avail memory = 29978624 (29276K bytes) Preloaded elf kernel "kernel" at 0xc02c2000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02c209c. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 ide_pci0: rev 0x01 on pci0.1.1 chip2: rev 0x01 on pci0.1.3 pcic0: rev 0x01 int a irq 9 on pci0.19.0 pcic1: rev 0x01 int b irq 9 on pci0.19.1 vga0: rev 0xd3 int a irq 255 on pci0.20.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1556MB (3187296 sectors), 3162 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordy acd0: drive speed 2416KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 xe0: probe xe0 not found vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 Initializing PC-card drivers: xe sio Intel Pentium detected, installing workaround for F00F bug IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default BRIDGE 981214, have 4 interfaces DUMMYNET initialized (990504) IP Filter: initialized. Default = pass all, Logging = enabled changing root device to wd0s2a Card inserted, slot 0 Card inserted, slot 1 ------------ /usr/src/sys/i386/conf/FUZZY : -------------------------- # # FUZZY - attempt to build a kernel that supports the # Zircom PS-CE2-10 PCCard Ethernet Card # # Jesse Reynolds 1999.10.18 # # PCCARD -- Generic machine with WD/AHx/NCR/BTx family disks and PCMCIA # hardware support # # 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/PCCARD,v 1.15.2.4 1999/08/29 17:05:59 iwasaki Exp $ machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident FUZZY maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # Jesse's adding the following: options MROUTING # multicast routing options IPFIREWALL # firewall options IPFIREWALL_VERBOSE # print info about dropped packets options IPFIREWALL_FORWARD # enable transparent proxy support options "IPFIREWALL_VERBOSE_LIMIT=100" # limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT # allow all by default options IPDIVERT # divert sockets options IPFILTER # kernel ipfilter support options IPFILTER_LOG # ipfilter logging options "ICMP_BANDLIM" options DUMMYNET options BRIDGE options NETATALK #Appletalk comms protocols config kernel root on wd0 # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 controller pnp0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. # controller ncr0 # controller ahb0 # controller ahc0 # controller isp0 # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. # controller dpt0 # controller adv0 at isa? port ? cam irq ? # controller adw0 # controller bt0 at isa? port ? cam irq ? # controller aha0 at isa? port ? cam irq ? # controller scbus0 # device da0 # device sa0 # device pass0 # device cd0 #Only need one of these, the code dynamically grows device wt0 at isa? port 0x300 bio irq 5 drq 1 device mcd0 at isa? port 0x300 bio irq 10 controller matcd0 at isa? port 0x230 bio # device scd0 at isa? port 0x230 bio # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #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 device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? #controller vpo0 at ppbus? # # The following Ethernet NICs are all PCI devices. # # device al0 # ADMtek AL981 (``Comet'') # device ax0 # ASIX AX88140A #device de0 # DEC/Intel DC21x4x (``Tulip'') #device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device rl0 # RealTek 8129/8139 #device sf0 # Adaptec AIC-6915 DuraLAN (``Starfire'') #device tl0 # Texas Instruments ThunderLAN #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vr0 # VIA Rhine, Rhine II #device vx0 # 3Com 3c590, 3c595 (``Vortex'') #device wb0 # Winbond W89C840F #device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. # device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 # device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 # device ep0 at isa? port 0x300 net irq 10 # device ex0 at isa? port? net irq? # device fe0 at isa? port 0x300 net irq ? # device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 # device lnc0 at isa? port 0x280 net irq 10 drq 0 device xe0 at isa? port? net irq ? #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 # device cs0 at isa? port 0x300 net irq ? pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 1 #Berkeley packet filter -------------------------------------------------------------------------- -- Jesse Reynolds - Virtual Artists Pty Ltd - http://www.va.com.au Email: jesse (at) va.com.au - http://virtual.artists To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 23 11:36:24 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from logatome.micronet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id BCD1114C2C; Sat, 23 Oct 1999 11:36:19 -0700 (PDT) (envelope-from e-masson@kisoft-services.com) Received: from kisoft-services.com (Nantes4.francenet.net [193.149.110.68]) by logatome.micronet.fr (8.8.8/8.8.8) with ESMTP id UAA21619; Sat, 23 Oct 1999 20:36:09 +0200 (CEST) Message-ID: <38120042.D8F1BE5D@kisoft-services.com> Date: Sat, 23 Oct 1999 20:36:50 +0200 From: Eric MASSON Organization: Kisoft Services X-Mailer: Mozilla 4.6 [fr] (WinNT; I) X-Accept-Language: fr MIME-Version: 1.0 To: jesse reynolds Cc: FreeBSD Hardware , FreeBSD Mobile Subject: Re: zircom pc-card's on a Fujitsu Lifebook 735Dx Laptop... References: <199910230809.CAA28033@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi > # pccardc dumpcis > Read return -1 bytes (expected 2) > pccardc: CIS code read: Cannot allocate memory > Read return -1 bytes (expected 10) > Configuration data for card in slot 1 > 2 slots found Enable pccardd start in /etc/rc.conf and then pccardc dumpcis will work properly. Regards Eric -- Any opinions expressed above | Murphy's Law Corollary : are my own, not Kisoft's | Murphy was an optimist. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 23 22:17:41 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from va.com.au (va.com.au [203.15.106.1]) by hub.freebsd.org (Postfix) with ESMTP id 59C8C14C94; Sat, 23 Oct 1999 22:17:35 -0700 (PDT) (envelope-from jesse@va.com.au) Received: from [1.1.1.3] (203.108.19.84) by va.com.au with ESMTP (Eudora Internet Mail Server 2.2); Sun, 24 Oct 1999 14:47:31 +0930 Mime-Version: 1.0 X-Sender: jesse@mail.va.com.au Message-Id: In-Reply-To: <38120042.D8F1BE5D@kisoft-services.com> References: <199910230809.CAA28033@harmony.village.org> <38120042.D8F1BE5D@kisoft-services.com> Date: Sun, 24 Oct 1999 15:17:25 +1000 To: Eric MASSON From: jesse reynolds Subject: Re: zircom pc-card's on a Fujitsu Lifebook 735Dx Laptop... Cc: FreeBSD Hardware , FreeBSD Mobile Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 8:36 PM +0200 23/10/1999, Eric MASSON wrote: >Hi > >> # pccardc dumpcis >> Read return -1 bytes (expected 2) >> pccardc: CIS code read: Cannot allocate memory >> Read return -1 bytes (expected 10) >> Configuration data for card in slot 1 >> 2 slots found >Enable pccardd start in /etc/rc.conf and then pccardc dumpcis will work >properly. How should I do this? eg: pccardd_start="YES" is this what you mean? It's not working. I get the same output as above, only doubled, as I have both the cards installed (two of them). I'm not sure of the syntax to use here. I also tried the following with no success: pccardd_enable="YES" I actually thought it might be more to do with the order of the drivers starting up in the kernel, as it tries to probe for xe before it's loaded the PC-Card driver, and initialises xe and sio: xe0: probe xe0 not found . . . PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 Initializing PC-card drivers: xe sio then again I'm probably barking up the wrong tree. Anyone? cheers jesse -- Jesse Reynolds - Virtual Artists Pty Ltd - http://www.va.com.au Faxmail: +61 2 9776 3594 Virtual Community Engine Email: jesse (at) va.com.au http://www.vce.net ?: http://jesse.va.com.au huh?: Community Server for ICQ: 4766684 MacOS Servers (W*API) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message