NetBSD Problem Report #10284
Received: (qmail 25226 invoked from network); 5 Jun 2000 12:43:48 -0000
Message-Id: <200006051242.e55CgXn00537@bobafett.localhost.fi>
Date: Mon, 5 Jun 2000 14:42:33 +0200 (CEST)
From: Antti Kantee <pooka@iki.fi>
Reply-To: pooka@iki.fi
To: gnats-bugs@gnats.netbsd.org
Subject: wiconfig(8) doesn't work with awi driver
X-Send-Pr-Version: 3.95
>Number: 10284
>Category: kern
>Synopsis: wiconfig(8) doesn't work with awi driver
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Jun 05 12:44:00 +0000 2000
>Closed-Date: Fri Jun 09 07:05:06 +0000 2000
>Last-Modified: Fri Jun 09 07:05:06 +0000 2000
>Originator: Antti Kantee
>Release: cvs updated the 2nd June
>Organization:
>Environment:
System: NetBSD bobafett.localhost.fi 1.4Z NetBSD 1.4Z (BOBAFETT) #13: Fri Jun 2 14:55:55 CEST 2000 pooka@bobafett.localhost.fi:/usr/src/sys/arch/i386/compile/BOBAFETT i386
>Description:
wiconfig awi0
wiconfig: SIOCGWAVELAN: Invalid argument
dmesg:
NetBSD 1.4Z (BOBAFETT) #13: Fri Jun 2 14:55:55 CEST 2000
pooka@bobafett.localhost.fi:/usr/src/sys/arch/i386/compile/BOBAFETT
cpu0: family 6 model 8 step 1
cpu0: Intel Pentium III (E) (686-class)
total memory = 97856 KB
avail memory = 77860 KB
using 3660 buffers containing 14640 KB of memory
BIOS32 rev. 0 found at 0xfd7d2
PCI BIOS rev. 2.1 found at 0xfd9e6
pcibios: config mechanism [1][x], special cycles [x][x], last bus 1
PCI IRQ Routing Table rev. 1.0 found at 0xfdf50, size 144 bytes (7 entries)
PCI Interrupt Router at 000:07:0 (Intel 82371FB PCI-to-ISA Bridge (PIIX))
--------------------------------------------
device vendor product pin PIRQ IRQ stage
--------------------------------------------
000:07:2 0x8086 0x7112 D 0x03 10 0
000:10:0 0x104c 0xac1c A 0x00 10 0
000:10:1 0x104c 0xac1c B 0x01 10 0
000:13:0 0x125d 0x1998 A 0x02 05 0
000:13:1 0x125d 0x1999 A 0x02 05 0
--------------------------------------------
PCI bridge 0: primary 0, secondary 1, subordinate 1
PCI bridge 1: primary 0, secondary 2, subordinate 2
PCI bridge 2: primary 0, secondary 3, subordinate 3
PCI bus #3 is the last bus
mainbus0 (root)
pnpbios0 at mainbus0: code f0000, data 400, entry a81b, control 0 eventp 400
pnpbios0: nodes 14, max len 224
PNP0C02 (mem fffe0000-ffffffff, io 4d0-4d1 8000-803f 2180-218f 3800-381f 3820-383f 398-399) at pnpbios0 index 0 ignored
PNP0C01 (mem 0-9ffff dc000-fffff 100000-5ffffff) at pnpbios0 index 1 ignored
PNP0200 (io 0-f 81-8f c0-df, dma 4) at pnpbios0 index 2 ignored
PNP0000 (io 20-21 a0-a1, irq 2) at pnpbios0 index 3 ignored
PNP0100 (io 40-43, irq 0) at pnpbios0 index 4 ignored
PNP0B00 (io 70-71, irq 8) at pnpbios0 index 5 ignored
PNP0303 (io 60 64, irq 1) at pnpbios0 index 6 ignored
PNP0C04 (io f0-ff, irq 13) at pnpbios0 index 7 ignored
PNP0800 (io 61) at pnpbios0 index 8 ignored
PNP0A03 (io cf8-cff) at pnpbios0 index 9 ignored
PNP0F13 (irq 12) at pnpbios0 index 10 ignored
com0 at pnpbios0 index 11 (PNP0501)
com0: io 3f8-3ff, irq 4
com0: ns16550a, working fifo
lpt0 at pnpbios0 index 17 (PNP0401)
lpt0: io 378-37f 778-77f, irq 7, dma 0
PNP0700 (io 3f0-3f5 3f7, irq 6, dma 2) at pnpbios0 index 18 ignored
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82443BX Host Bridge/Controller (rev. 0x03)
ppb0 at pci0 dev 1 function 0: Intel 82443BX AGP Interface (rev. 0x03)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga1 at pci1 dev 0 function 0: Silicon Motion product 0x0710 (rev. 0xa3)
wsdisplay0 at vga1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0
pcib0: Intel 82371AB PCI-to-ISA Bridge (PIIX4) (rev. 0x02)
pciide0 at pci0 dev 7 function 1: Intel 82371AB IDE controller (PIIX4) (rev. 0x01)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
wd0 at pciide0 channel 0 drive 0: <IBM-DARA-212000>
wd0: drive supports 16-sector pio transfers, lba addressing
wd0: 11513 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 23579136 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
pciide0: secondary channel wired to compatibility mode
atapibus0 at pciide0 channel 1
cd0 at atapibus0 drive 0: <CD-224E, , 1.5A> type 5 cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2
pciide0: secondary channel interrupting at irq 15
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
uhci0 at pci0 dev 7 function 2: Intel 82371AB USB Host Controller (PIIX4) (rev. 0x01)
uhci0: interrupting at irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
Intel 82371AB Power Management Controller (PIIX4) (miscellaneous bridge, revision 0x03) at pci0 dev 7 function 3 not configured
cbb0 at pci0 dev 10 function 0: Texas Instruments PCI1225 PCI-CardBus Bridge (rev. 0x01)
cbb1 at pci0 dev 10 function 1: Texas Instruments PCI1225 PCI-CardBus Bridge (rev. 0x01)
ESS Technology Inc product 0x1998 (audio multimedia) at pci0 dev 13 function 0 not configured
ESS Technology Inc product 0x1999 (miscellaneous communications) at pci0 dev 13 function 1 not configured
isa0 at pcib0
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
isapnp0: no ISA Plug 'n Play devices found
cbb0: interrupting at irq 10
cbb0: cacheline 0x8 lattimer 0x20
cbb0: bhlc 0x824008 lscp 0x20020200
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer 0x20
pcmcia0 at cardslot0
cbb1: interrupting at irq 10
cbb1: cacheline 0x8 lattimer 0x20
cbb1: bhlc 0x828008 lscp 0x20030300
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cardslot1: bus 3 device 0 cacheline 0x8, lattimer 0x20
pcmcia1 at cardslot1
apm0 at mainbus0: Power Management spec V1.2
biomask ef6d netmask ef6d ttymask ffef
IPsec: Initialized Security Association Processing.
ex0 at cardbus1 dev 0 function 0: 3Com 3c575B-TX Ethernet
ex0: interrupting at 10
ex0: MAC address 00:50:04:ca:0e:db
tqphy0 at ex0 phy 0: 78Q2120 10/100 media interface, rev. 11
tqphy0: 10baseT, 100baseTX, auto
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
wsdisplay0: screen 5 added (80x25, vt100 emulation)
wsdisplay0: screen 6 added (80x25, vt100 emulation)
wsdisplay0: screen 7 added (80x25, vt100 emulation)
pcmcia0: CIS version PC Card Standard 5.0
pcmcia0: CIS info: Nokia, C020 WLAN Card, ,
pcmcia0: Manufacturer code 0x23d, product 0x20c0
pcmcia0: function 0: network adapter, ccr addr 800 mask 3
pcmcia0: function 0, config table entry 1: I/O card; irq mask ffff; iomask 6, iospace 0-3f; io8 powerdown
awi0 at pcmcia0 function 0: Nokia C020 WLAN Card
awi0: IEEE802.11 (DS 2Mbps) address 00:e0:03:04:3b:1c
>How-To-Repeat:
run wiconfig awi0
>Fix:
.
>Release-Note:
>Audit-Trail:
From: Jason R Thorpe <thorpej@zembu.com>
To: Antti Kantee <pooka@iki.fi>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10284: wiconfig(8) doesn't work with awi driver
Date: Mon, 5 Jun 2000 06:46:03 -0700
On Mon, Jun 05, 2000 at 02:42:33PM +0200, Antti Kantee wrote:
> >Synopsis: wiconfig(8) doesn't work with awi driver
Um, of course it doens't. wiconfig(8) is for the wi driver, not
the awi driver.
All the things they do, of course, should be put into ifconfig(8).
--
-- Jason R. Thorpe <thorpej@zembu.com>
From: Antti Kantee <pooka@iki.fi>
To: Jason R Thorpe <thorpej@zembu.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10284: wiconfig(8) doesn't work with awi driver
Date: Mon, 5 Jun 2000 16:59:13 +0300
On Mon Jun 05 2000 at 06:46:03 -0700, Jason R Thorpe wrote:
> > >Synopsis: wiconfig(8) doesn't work with awi driver
>
> Um, of course it doens't. wiconfig(8) is for the wi driver, not
> the awi driver.
>
> All the things they do, of course, should be put into ifconfig(8).
talk about deceptive man pages then (wiconfig.8):
The wiconfig command controls the operation of WaveLAN/IEEE wireless net-
working devices via the wi(4) and awi(4) drivers.
--
Antti Kantee <pooka@iki.fi> Of course he runs NetBSD.
From: Jason R Thorpe <thorpej@zembu.com>
To: Antti Kantee <pooka@iki.fi>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10284: wiconfig(8) doesn't work with awi driver
Date: Mon, 5 Jun 2000 07:05:20 -0700
On Mon, Jun 05, 2000 at 04:59:13PM +0300, Antti Kantee wrote:
> talk about deceptive man pages then (wiconfig.8):
> The wiconfig command controls the operation of WaveLAN/IEEE wireless net-
> working devices via the wi(4) and awi(4) drivers.
Well, then the manpage is incorrect.
--
-- Jason R. Thorpe <thorpej@zembu.com>
From: Antti Kantee <pooka@iki.fi>
To: Jason R Thorpe <thorpej@zembu.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10284: wiconfig(8) doesn't work with awi driver
Date: Mon, 5 Jun 2000 17:43:17 +0300
On Mon Jun 05 2000 at 07:05:20 -0700, Jason R Thorpe wrote:
> > talk about deceptive man pages then (wiconfig.8):
> > The wiconfig command controls the operation of WaveLAN/IEEE
> > wireless net- working devices via the wi(4) and awi(4)
> > drivers.
>
> Well, then the manpage is incorrect.
Well, it should be corrected then ;)
I can't quite figure out how to configure the network name etc. with the
awi driver in that case.
--
Antti Kantee <pooka@iki.fi> Of course he runs NetBSD.
State-Changed-From-To: open->closed
State-Changed-By: onoe
State-Changed-When: Thu Jun 8 23:53:50 PDT 2000
State-Changed-Why:
Now awi(4) driver accepts most of ioctls from wiconfig(8).
I've proposed changes to ifconfig(8) to configure wireless LAN cards
this April on tech-net, but which parameters should be configured via
ifconfig(8) is still unclear and needs more experience.
We should gather implementations to configure wireless LAN and
define which part are common and should be set via general network
configuration utility -- ifconfig(8).
For now, I decided to support wiconfig(8) as a start point of
wireless LAN configuration utility and will make sure what parameters
should be configured both for DS and FH radio types.
I'm not sure why my thought already be put into wiconfig(8) man page.
I've just committed the support for wiconfig(8) into awi(4) and
this is the reason I'd like to close this PR by fixing driver instead
of modifying the man page.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.