From owner-freebsd-current Sat Nov 2 12: 9: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDF1A37B401 for ; Sat, 2 Nov 2002 12:09:03 -0800 (PST) Received: from mail46.fg.online.no (mail46-s.fg.online.no [148.122.161.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5338F43E42 for ; Sat, 2 Nov 2002 12:08:54 -0800 (PST) (envelope-from frode@nordahl.net) Received: from [10.0.0.100] (ti200720a080-0270.bb.online.no [80.212.245.14]) by mail46.fg.online.no (8.9.3/8.9.3) with ESMTP id VAA01824; Sat, 2 Nov 2002 21:08:42 +0100 (MET) Subject: Re: CNet CNWLC-811 (PRISM2), kernel panic From: Frode Nordahl To: "M. Warner Losh" Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <20021102.111539.102714390.imp@bsdimp.com> References: <1036232462.628.6.camel@samwise.xu.nordahl.net> <20021102.111539.102714390.imp@bsdimp.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 02 Nov 2002 21:07:42 +0100 Message-Id: <1036267664.791.13.camel@samwise.xu.nordahl.net> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, With OLDCARD it does not crash! After crafting a pccard.conf entry for the card, wi does not successfully attach to the card. Do you think it is feasible to add support for this card in the "wi" driver? Please don't hesitate to ask me for more information if you need it, thanks! If there is any dirty work to be done to make it work, tell me. I'll be more than happy to do it for you :) pccard.conf line: # CNet CNWLC-811 card "OEM" "11Mbps Wireless LAN PC Card V-3" config auto "wi" ? insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop I get the following output from the driver: wi0 at port 0x240-0x27f irq 11 slot 1 on pccard1 wi0: timeout in wi_cmd 0x0000; event status 0x0000 wi0: timeout in wi_cmd 0x0000; event status 0x0000 wi0: timeout in wi_cmd 0x0000; event status 0x0000 wi0: init failed wi0: timeout in wi_cmd 0x0021; event status 0x0000 wi0: timeout in wi_cmd 0x0021; event status 0x0000 wi0: mac read failed 5 device_probe_and_attach: wi0 attach returned 5 # pccardc dumpcis Configuration data for card in slot 1 Tuple #1, code = 0x17 (Attribute memory descriptor), length = 3 000: d9 01 ff Attribute memory device information: Device number 1, type Function specific, WPS = ON Speed = 250nS, Memory block size = 2Kb, 1 units Tuple #2, code = 0x1d (Other conditions for attribute memory), length = 4 000: 01 d9 01 ff (MWAIT) Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 00 00 00 PCMCIA ID = 0x0, OEM ID = 0x0 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #5, code = 0x15 (Version 1 info), length = 39 000: 05 00 4f 45 4d 00 31 31 4d 62 70 73 20 57 69 72 010: 65 6c 65 73 73 20 4c 41 4e 20 50 43 20 43 61 72 020: 64 20 56 2d 33 00 ff Version = 5.0, Manuf = [OEM], card vers = [11Mbps Wireless LAN PC Card V-3] Tuple #6, code = 0x1a (Configuration map), length = 6 000: 01 02 00 08 03 ff Reg len = 2, config register addr = 0x800, last config = 0xff Registers: XX------ 1 bytes in subtuples Tuple #7, code = 0x1b (Configuration entry), length = 15 000: c1 81 9d 71 55 2e 2e 2d fc 14 45 10 b8 ff 20 Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2.5 x 100mA Max current average over 10 ms: 2.5 x 100mA Power down supply current: 2.5 x 10mA Wait scale Speed = 1.2 x 10 us Card decodes 5 address lines, limited 8/16 Bit I/O IRQ modes: IRQs: 3 4 5 7 8 9 10 11 12 13 14 15 Max twin cards = 0 Misc attr: (Power down supported) Tuple #8, code = 0xff (Terminator), length = 0 2 slots found Mvh, Frode Nordahl On Sat, 2002-11-02 at 19:15, M. Warner Losh wrote: > Does this happen with OLDCARD? I have a couple of cards that do this, > but haven't been able to track down why this happens. > > Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message