Opened 11 years ago

Closed 9 years ago

#31 closed problem (wontfix)

Create bug report wi(4) driver under RELENG_8 scan mode

Reported by: rick Owned by: rick
Keywords: Cc:
Location: Generiek

Description

When the wi(4) driver has an ssid set which is not available -thus not connected- initiating a scan is not showing results and stalls forever.

XXX: Output with CNodeZwet# sysctl hw.wi.debug=10 needed

Quick and dirty:

CNodeZwet# ifconfig wlan0 create wlandev wi0 wlanmode sta 10.18.0.1/24

CNodeZwet# ifconfig wlan0 scan

[ok_results]
CNodeZwet# ifconfig wlan0 ssid connected.ssid

CNodeZwet# ifconfig wlan0 scan

[ok_results]
CNodeZwet# ifconfig wlan0 ssid non.connected.ssid

CNodeZwet# ifconfig wlan0 scan

[wail_till_ctrl_c_is_pressed]
[no_results]
CNodeZwet# ifconfig wlan0 ssid -

CNodeZwet# ifconfig wlan0 scan

[ok_results]

CNodeZwet# dmesg | grep wi1: <INTERSIL HFA384x/IEEE> at port 0x180-0x1bf irq 11 function 0 config 1 on pccard0

CNodeZwet# uname -a

FreeBSD CNodeZwet.wLeiden.NET 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Wed Jan 27 20:54:10 UTC 2010 root@….:/usr/obj/nanobsd.wleiden/usr/src/sys/kernel.wleiden i386

Change History (3)

comment:1 Changed 10 years ago by richardvm

Is dit een iris probleem?

comment:2 Changed 10 years ago by rick

Is dit een iris probleem?

Nee, maar moet wel gedaan worden vandaar een reminder ticket :-)

comment:3 Changed 9 years ago by rick

Resolution: wontfix
Status: newclosed

wi(4) not used/needed anymore, neither does this function.

Note: See TracTickets for help on using tickets.