: 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
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 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:
: dstumbler breaks; on startup it reports
: unable to ioctl device socket: Input/output error.
As root or no?
As root, with interface up and configured.
Magnus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
to be resolved or documented before MFC. (copied maintainer)
Why, did they not work/build after the commit? I didn't try all the ports
that depend on the driver but the API (ioctls) should be unchanged except
for the
: dstumbler breaks; on startup it reports
: unable to ioctl device socket: Input/output error.
As root or no?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Sorry, for the new wi driver you need to add:
device wlan
to your config files. This probably belongs in UPDATING.
Sam
- Original Message -
From: Matt Haught [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 15, 2003 9:59 PM
Subject: Re: HEADS UP: new wi driver
I
On Thu, 16 Jan 2003, Sam Leffler wrote:
...
to your config files. This probably belongs in UPDATING.
NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
to be resolved or documented before MFC. (copied maintainer)
Magnus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Thu, 16 Jan 2003, Sam Leffler wrote:
...
to your config files. This probably belongs in UPDATING.
NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
to be resolved or documented before MFC. (copied maintainer)
Why, did they not work/build after the commit? I
Hi Sam,
The new device wlan option is pushing the kern.flp over the limit
during make release. Maybe it can be moved to mfsroot.flp?
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the
I just committed a new version of the wi driver. This driver is very
different in that it depends on a common core implementation of the 802.11
state machine and mgmt protocols. There should be no visible differences
(for now) between the old driver and the new but beware. If you encounter
11 matches
Mail list logo
