From owner-freebsd-questions Sun Nov 4 15:59:34 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.utexas.edu (wb3-a.mail.utexas.edu [128.83.126.138]) by hub.freebsd.org (Postfix) with SMTP id 0F0FC37B405 for ; Sun, 4 Nov 2001 15:59:29 -0800 (PST) Received: (qmail 17719 invoked by uid 0); 4 Nov 2001 23:59:22 -0000 Received: from dhcp-199-210.dsl.utexas.edu (HELO osilva.mail.utexas.edu) (128.83.199.210) by umbs-smtp-3 with SMTP; 4 Nov 2001 23:59:22 -0000 Message-Id: <5.1.0.14.2.20011104174808.00a2ab80@mail.utexas.edu> X-Sender: oscars@mail.utexas.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 04 Nov 2001 18:07:49 -0600 To: questions@freebsd.org From: Oscar Ricardo Silva Subject: Xircom CEM56 with FreeBSD 4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm attempting to load FreeBSD 4.4 on my Compaq Armada 6500 with a built-in Xircom 10/100 + 56K modem CEM56 card. Just want to make clear that this card is built-in so I can't pull it out and look at any information that may be written on it. I found a site with drivers for the Xircom cards under FreeBSD: But I'm having some problems compiling it into the kernel. For one, if_xe.c has a reference to bpfilter.h which I believe is something from the FreeBSD 3.x days. I do have pccard services being loaded at startup and it does try to load the driver. Here is what I see: Nov 4 13:49:53 drfate pccardd[85]: Card "Xircom"("CreditCard Ethernet 10/100 + Modem 56") [CEM56] [1.00] matched "Xircom" ("CreditCard Ethernet 10/100 + Modem 56") [(null)] [(null)] Nov 4 13:49:53 drfate pccardd[85]: Using I/O addr 0x2e8, size 8 Nov 4 13:49:53 drfate pccardd[85]: Setting config reg at offs 0xff80 to 0x67, Reset time = 50 ms Nov 4 13:49:58 drfate pccardd[85]: Assigning I/O window 0, start 0x2e8, size 0x8 flags 0x7 Nov 4 13:49:58 drfate pccardd[85]: Assign xe0, io 0x2e8-0x2ef, mem 0x0, 0 bytes, irq 11, flags 0 Nov 4 13:49:58 drfate pccardd[85]: driver allocation failed for Xircom(CreditCard Ethernet 10/100 + Modem 56): Device not configured Nov 4 13:49:58 drfate pccardd[85]: pccardd started I had Linux installed on this machine and the card was detected and worked: cs: memory probe 0xa0000000-0xa0ffffff: clean. xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh) cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 0x3c0-0x3df cs: IO port probe 0x0178-0x036f: clean. cs: IO port probe 0x0380-0x03bf: clean. cs: IO port probe 0x03e0-0x04ff: clean. cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0a00-0x0aff: clean. cs: IO port probe 0x0c00-0x0cff: clean. eth0: MII link partner: 0021 eth0: MII selected eth0: media 10BaseT, silicon revision 5 eth0: Xircom: port 0x300, irq 3, hwaddr 00:80:C7:05:3B:A1 ttyS03 at port 0x02e8 (irq = 3) is a 16550A eth0: MII link partner: 0021 eth0: MII selected eth0: media 10BaseT, silicon revision 5 From looking at the dmesg output on the linux side I see that it was using IRQ 3 and IO 0x300. I've tried to force pccard services to see the card on these settings by creating /etc/pccard.conf and entering these values but each time I see that IRQ 11 is selected. Here is my pccard.conf: # Xircom CreditCard Ethernet 10/100 + modem (Ethernet part) (CEM56) card "Xircom" "CreditCard Ethernet 10/100 + Modem 56" config 0x27 "xe" 3 # config auto "sio" ? insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop I have noticed that the IO port values reported on the FreeBSD match the modem (ttyS03) values on the Linux side. Maybe I'm only loading part of the driver for the card? At this point, I've tried different values in pccard.conf and each time I boot, pccard services tries to load the Xircom card at the same values. Not even sure which way to turn right now. Any information or suggestions would be appreciated. Oscar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message