From owner-freebsd-current Sat Jan 25 9:47:28 2003 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 F249F37B401 for ; Sat, 25 Jan 2003 09:47:26 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0545643F13 for ; Sat, 25 Jan 2003 09:47:26 -0800 (PST) (envelope-from sam@errno.com) Received: from melange (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.5/8.12.1) with ESMTP id h0PHlJnN098012 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 25 Jan 2003 09:47:19 -0800 (PST)?g (envelope-from sam@errno.com)œ X-Authentication-Warning: ebb.errno.com: Host melange.errno.com [66.127.85.82] claimed to be melange Message-ID: <1cd401c2c499$ceec0590$52557f42@errno.com> From: "Sam Leffler" To: "Sean Chittenden" , "M. Warner Losh" Cc: , References: <1e4301c2bd82$03de8cb0$5a557f42@errno.com> <20030117.102821.89423323.imp@bsdimp.com> <20030124215212.GB1224@perrin.int.nxad.com> Subject: Re: HEADS UP: new wi driver Date: Sat, 25 Jan 2003 09:47:18 -0800 Organization: Errno Consulting MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 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 > > : dstumbler breaks; on startup it reports > > : "unable to ioctl device socket: Input/output error". > > > > As root or no? > > I have a rebuilt system finally that I could test this against and I'm > actually getting a different error message on startup of dstumbler: > > error: unable to ioctl device socket: Invalid argument > > From ktrace: > > 43042 dstumbler CALL sigaction(0x12,0x280b5850,0) > 43042 dstumbler RET sigaction 0 > 43042 dstumbler CALL socket(0x2,0x2,0) > 43042 dstumbler RET socket 3 > 43042 dstumbler CALL ioctl(0x3,SIOCGIFGENERIC,0xbfbff4b0) > 43042 dstumbler RET ioctl 0 > 43042 dstumbler CALL ioctl(0x3,SIOCSIFGENERIC,0xbfbff4c0) > 43042 dstumbler RET ioctl 0 > 43042 dstumbler CALL ioctl(0x3,SIOCGIFGENERIC,0xbfbff4b0) > 43042 dstumbler RET ioctl 0 > 43042 dstumbler CALL ioctl(0x3,SIOCSIFGENERIC,0xbfbff4c0) > 43042 dstumbler RET ioctl -1 errno 22 Invalid argument > 43042 dstumbler CALL sigaction(0x12,0x280b5838,0x280b5850) > 43042 dstumbler RET sigaction 0 > 43042 dstumbler CALL poll(0xbfbff3e8,0x1,0) > 43042 dstumbler RET poll 0 > 43042 dstumbler CALL poll(0xbfbff3e8,0x1,0) > 43042 dstumbler RET poll 0 > 43042 dstumbler CALL write(0x1,0x8060000,0x5e) > 43042 dstumbler GIO fd 1 wrote 94 bytes > "\^[[52;22H\^[[34m\^[[1m[\^[[31m error: unable to ioctl device socket: \ > Invalid argument \^[[C\^[[39;49m\^[[m\^O" > dstumbler uses WI_RID_SCAN_REQ to initiate a scan for AP's. This required the application know whether it was talking to a prims/wavelan/symbol card so was replaced by WI_RID_SCAN_APS which provides a device-independent interface. I changed wicontrol to deal with this; it would be good if dstumbler did likewise. Otherwise I can look at adding a backwards compatibility entry for WI_RID_SCAN_REQ. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message