Re: wi troubles, error

by setting my pccard_mem to 0xd8000, it finally read the cis data from my card correctly.  It dumped:

Configuration data for card in slot 
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: 03 d9 01 ff
    (MWAIT) (3V card)
Tuple #3, Code = 0x20 (Manufacturer ID), length = 4
  000: bf 01 02 33
   PCMCIA ID = 0x1bf, OEM ID = 03302
Tuple #4, code 0x21 (Functional ID), length = 2
  000: 06 00
    Network/LAN adapter
Tuple #5, code = 0x15 (Version 1 info), length = 51
  (hex)
  Version = 5.0, Manf = [Belkin], card vers = [11Mbps-Wireless-Notebook-Network-Adapter]
Tuple #6, code=0x1a (Configuration map), length = 6
  000: 01 02 00 08 01 ff
  Reg len = 2, config register addr = 0x800, last config - 0x2
  Registers: X------- 1 bytes in subtubles
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
   (more power current information)...
   Wait scale Speed = 1.2 x 10 us
   Card decodes 5 addresses lines, limited 8/16 Bit I/O
     IRQ modes:
     IRQs: 3 4 5 8  9 10 11 12 13 14 15
    Max twin cards = 0
    Misc attr: (Power down suipported)
Tuple #8, code = 0xff (Terminator), length = 0
2 slots found.


I configured the following (using the dumped data as my resource) into /etc/pccard.conf:

card "Belkin" "11Mbps-Wireless-Notebook-Network-Adapter"
  config auto "wi" ?
  insert /etc/pccard_ether $device start
  remove /etc/pccard_ether $device stop

..does that look right?  when I insert the card, I get a rather odd error, which is:

pccard: card inserted, slot 1
wi0 at port 0x240-0x27f irq 10 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 attached returned 5

what am I doing wrong?
Thanks, 
Mark





>-----Original Message-----
>From: Vince Vielhaber [mailto:[email protected]]
>Sent: Tuesday, January 14, 2003 07:14 PM
>To: 'mark'
>Cc: [email protected]
>Subject: Re:  wi ultimate crisis
>
>On Tue, 14 Jan 2003, mark wrote:
>
>> I had those two lines in my rc.conf (pccard_enable="YES" and pccard_beep="1")
>> #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 0
>> 2 slots found
>>
>>
>> if I add the line "pccard_mem=0x10000" and reboot I get this for pccardc dumpcis. note: i had the card inserted in the 2nd pcmcia slot:
>
>I recently ran into something similar.  man pccardc told me this (after
>I tried a few other addresses and finally looked it up):
>
>
>     5.   pccardmem addr
>
>          Specifies the host address using PC-CARD controller(PCIC) will use
>          to map cards to.  Because the PCIC needs a contiguous 16KB memory,
>          you can only use the following four addresses:
>
>          0xd0000  0xd0000-0xd3fff (default)
>          0xd4000  0xd4000-0xd7fff
>          0xd8000  0xd8000-0xdbfff
>          0xdc000  0xdc000-0xdffff
>
>          You can use "DEFAULT" instead of 0xd0000.  This subcommand corre-
>          sponds to pccard_mem in rc.conf(5).
>
>So one of those four addresses in the pccard_mem= should get you a bit
>further.
>
>Vince.
>-- 
> Fast, inexpensive internet service 56k and beyond!  http://www.pop4.net/
>   http://www.meanstreamradio.com       http://www.unknown-artists.com
>         Internet radio: It's not file sharing, it's just radio.
>
>



To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message