From owner-freebsd-stable Wed May 31 0: 4:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id A907D37BE50 for ; Wed, 31 May 2000 00:04:03 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id DAA05283 for ; Wed, 31 May 2000 03:04:43 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Wed, 31 May 2000 03:04:43 -0400 (EDT) From: "Brandon D. Valentine" To: FreeBSD-STABLE Subject: Problems with xe driver under 4.0-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I'm having trouble getting the xe driver to load for my Intel EtherExpress PRO/100 16 bit PCMCIA card. I know next to nothing about PCMCIA as a technology and don't know what to make of "Can't map in cis". I gathered from the manpages that cis is card information services, but I am not sure what it is that the driver is failing on. Perhaps someone with a better understanding of the lower level process of inserting a pccard and the code internals of the xe driver can lend some insight. Warner perhaps? I'd appreciate any insight you guys can offer. I can take diffs over on a floppy disk and try to repair it that way, but sneakernet is my only option at this point until I get that PCMCIA NIC working. Here are the relevant system messages: # uname -sr FreeBSD 4.0-RELEASE # tail -n 4 /var/log/messages May 31 01:33:15 hostname /kernel: pccard: card inserted, slot 0 May 31 01:33:25 hostname /kernel: xe1: xe: Probing May 31 01:33:25 hostname /kernel: xe1: Can't map in cis May 31 01:33:25 hostname pccardd[50]: driver allocation failed for Intel(EtherExpress(TM) PRO/100 PC Card Mobile Adapter16): Device not configured # pccardc dumpcis 0 Code 136 not found Code 136 not found code Unknown ignored code Manufacturer ID ignored Code 138 not found Code 138 not found code Unknown ignored Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 2 000: 00 ff Attribute memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #3, code = 0x15 (Version 1 info), length = 77 000: 05 00 49 6e 74 65 6c 00 45 74 68 65 72 45 78 70 010: 72 65 73 73 28 54 4d 29 20 50 52 4f 2f 31 30 30 020: 20 50 43 20 43 61 72 64 20 4d 6f 62 69 6c 65 20 030: 41 64 61 70 74 65 72 31 36 00 50 52 4f 2f 31 30 040: 30 20 4d 31 36 41 00 31 2e 30 30 00 ff Version = 5.0, Manuf = [Intel],card vers = [EtherExpress(TM) PRO/100 PC Card Mobile Adapter16] Addit. info = [PRO/100 M16A],[1.00] Tuple #4, code = 0x0 (Null tuple), length = 8 000: 00 e3 7a 00 00 00 00 00 Tuple #5, code = 0x0 (Null tuple), length = 5 000: 89 00 0a 01 43 Tuple #6, code = 0x44 (Card init date), length = 4 000: 6e 90 64 25 Tuple #7, code = 0x1a (Configuration map), length = 5 000: 01 01 00 08 03 Reg len = 2, config register addr = 0x800, last config = 0x1 Registers: XX------ Tuple #8, code = 0x1b (Configuration entry), length = 25 000: c1 c1 bd 7f 55 4d 5d 3e 46 46 06 e0 17 17 e4 60 010: 00 00 0f 70 bc 8e 10 00 20 Config index = 0x1(default) Interface byte = 0xc1 (I/O) +RDY/-BSY active, wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Minimum operating supply voltage: 4.5 x 1V Maximum operating supply voltage: 5.5 x 1V Continuous supply current: 3.5 x 100mA Max current average over 1 second: 4 x 100mA Max current average over 10 ms: 4 x 100mA Power down supply current: 1 x 100mA Wait scale Speed = 1.2 x 10 ms RDY/BSY scale Speed = 1.2 x 10 ms Card decodes 23 address lines IRQ modes: IRQs: NMI IOCK BERR 0 1 2 4 8 9 10 12 Memory space length = 0x60 Max twin cards = 0 Misc attr: Tuple #9, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #10, code = 0x22 (Functional EXT), length = 8 000: 04 06 00 a0 c9 7a e3 28 Voice services available: Tuple #11, code = 0x22 (Functional EXT), length = 2 000: 01 02 Modem interface capabilities: Tuple #12, code = 0x22 (Functional EXT), length = 5 000: 02 80 96 98 00 Data modem services available: Tuple #13, code = 0x22 (Functional EXT), length = 5 000: 02 00 e1 f5 05 Data modem services available: Tuple #14, code = 0x22 (Functional EXT), length = 2 000: 03 01 Tuple #15, code = 0x22 (Functional EXT), length = 2 000: 03 03 Tuple #16, code = 0x22 (Functional EXT), length = 2 000: 05 00 Modem interface capabilities: Tuple #17, code = 0x0 (Null tuple), length = 12 000: 34 30 30 32 36 46 37 41 45 33 32 38 Tuple #18, code = 0xff (Terminator), length = 0 2 slots found Brandon D. Valentine -- "You should believe in death, taxes, Larry Ellison's loathing of Bill Gates and Intel's inability to ship a working chipset." - Dr Spinola, The Register, 05/13/2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message