> : 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"
wistat.c, line 225 seems to be the offending line that is no longer
working. Does dstumbler need to be updated or is this a bug in the
new wlan code? -sc
--
Sean Chittenden
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
