troubles with recent wireless changes

From: Toxa <postfix_at_sendmail.ru>
Date: Sun, 23 Jan 2005 05:42:02 +0300
Hi.

After january changes in wireless area I've encountered several problems
with my sony vaio laptop.

1. Preloading if_wi (in loader.conf) gives me kernel panic. Sorry I have
no serial console to put here trap info, so I can only say it gets fatal trap. 
I know this is quite useless but that's all I can say. 
Loading if_wi from userland after boot works ok. I didn't try to build
device wi support into kernel because I still hope it will work as usual, someday.

2. After serveral hours of wireless working, I have to reload if_wi due
to the such failures (wi stops transmitting data but still connected to
AP):

wi0: timeout in wi_cmd 0x010b; event status 0x8000
wi0: xmit failed
wi0: timeout in wi_seek to 152/0
wi0: timeout in wi_seek to 152/0
wi0: timeout in wi_seek to 152/0
wi0: timeout in wi_seek to 152/0
wi0: bad alloc 128 != 13d, cur 1 nxt 1

3. dstumbler doesn't work anymore due to the 
"error: unable to ioctl device socket: Invalid argument"


My wireless interface:

wi0: <Intersil Prism2.5> mem 0xf8000000-0xf8000fff irq 9 at device 2.0
on pci2
wi0: [GIANT-LOCKED]
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.3)
wi0: Ethernet address: 00:d0:59:49:12:52


My dmesg can be reached ffrom http://62.89.204.62/dmesg/laptoxa.txt
(I decide not to put it here in order to avoid big message)

Big thanks in advance.
Received on Sun Jan 23 2005 - 01:44:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:26 UTC