Re: PCI 802.11b w/NetBSD 1.6
Jasper Wallace <[email protected]> Fri, 31 Jan 2003 16:18:45 +0000 (GMT)
| Newsgroups | gmane.network.wireless.bsd.general |
|---|---|
| Message-ID | <Pine.NEB.4.51.0301311614440.314@jellycat> |
On Fri, 31 Jan 2003, Shingo WATANABE / [ISO-2022-JP] ÅÏÊÕ ¿¸ã wrote: > At Wed, 29 Jan 2003 13:58:34 +0000 (GMT), > Jasper Wallace <[email protected]> wrote: > > > > On Wed, 29 Jan 2003, Shingo WATANABE / [ISO-2022-JP] ÅÏÊÕ ¿¸ã wrote: > > > > > At Mon, 27 Jan 2003 10:18:29 -0600, > > > David Young <[email protected]> wrote: > > > > > > > A lot of people report this problem. I am not able to reproduce it, > > > > myself. Maybe it is because I test on much slower computers. > > > > > > > > Be sure that you are using the latest ic/wi.c (1.109) and pci/if_wi_pci.c > > > > (1.16), since I have recently fixed bugs in both. > > > > It is not pcmcia card. It is a internal wireless network interface in > IBM ThinkPad X30 (2672-4EJ). > The dmesg says: > wi0 at pci1 dev 2 function 0: Intersil Prism2.5 Wireless Lan > wi0: interrupting at irq 11 > wi0: 802.11 address 00:05:3c:06:32:c9 > wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) > wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) > wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > > Do you have the PCIBIOS options enabled in your kernel? > > YES, I use. including PCIBIOS_ADDR_FIXUP (see pcibios(4) for details). It would probably help to post your kernel config and complete dmesg. > > you could try increasing the size of the kernel message buffer (options > > MSGBUFSIZE) and then enabling PCI_CONFIG_DUMP and PCIVERBOSE to dump the pci > > space info for your wi device. > > > > or you can use pcictl to do the same thing... (pcictl is probably eaiser). > > > > I wouldn't be able to interpret the output, but you could compare it to > > someone who has a working version of this card. > > I would like to know someone use the wirelss card (Intersil Prism2.5 > w/ PCI interface) without problem... I have no more PCI wireless card. > Is the problem related to PCI configuration? That was my guess, it might be that areas of memory that the card/driver use are setup wrong so that the driver is writing commands to somewhere that isn't mapped to the card. -- [http://pointless.net/] [0x2ECA0975] -- *bsd wireless list, a bawug thing <http://www.bawug.org/> [un]subscribe: http://lists.bawug.org/mailman/listinfo/bsd-wireless/