change format strings in error messages to reasonable values more likely

to be understood by people who don't program in C.
ok everyone

52 files changed, 319 insertions, 319 deletions

diff --git a/share/man/man4/an.4 b/share/man/man4/an.4
index b488b389f7d..5005f7b7ec6 100644
--- a/share/man/man4/an.4
+++ b/share/man/man4/an.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: an.4,v 1.38 2013/02/14 07:40:42 jmc Exp $
+.\"	$OpenBSD: an.4,v 1.39 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ee.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/an.4,v 1.5 2000/03/02 14:53:45 sheldonh Exp $
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt AN 4
 .Os
 .Sh NAME
@@ -139,10 +139,10 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "an%d: failed to allocate %d bytes on NIC"
+.It "an0: failed to allocate N bytes on NIC"
 The driver was unable to allocate memory for transmit frames in the
 NIC's on-board RAM.
-.It "an%d: device timeout"
+.It "an0: device timeout"
 The Aironet card failed to generate an interrupt to acknowledge a transmit
 command.
 .El
diff --git a/share/man/man4/art.4 b/share/man/man4/art.4
index 6a03997082f..ee70a2e3355 100644
--- a/share/man/man4/art.4
+++ b/share/man/man4/art.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: art.4,v 1.7 2009/11/16 17:53:29 sobrado Exp $
+.\"	$OpenBSD: art.4,v 1.8 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 2005  Internet Business Solutions AG, Zurich, Switzerland
 .\" Written by: Claudio Jeker <jeker@accoom.net>
@@ -16,7 +16,7 @@
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
 .\"
-.Dd $Mdocdate: November 16 2009 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt ART 4
 .Os
 .Sh NAME
@@ -122,15 +122,15 @@ For example:
 .Dl # ifconfig art0 media E1-G.704 mode autoselect
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "art%d: device timeout"
+.It "art0: device timeout"
 The device has stopped responding to the network
-.It "art%d: internal FIFO underflow"
+.It "art0: internal FIFO underflow"
 The internal FIFO got empty while transmitting a packet.
 This may indicate a PCI bus congestion.
-.It "art%d: internal FIFO overflow"
+.It "art0: internal FIFO overflow"
 The internal FIFO overflowed while receiving a packet.
 This may indicate a PCI bus congestion.
-.It "art%d: Failed to malloc memory"
+.It "art0: Failed to malloc memory"
 There are not enough mbufs available for allocation.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/ath.4 b/share/man/man4/ath.4
index f2933541748..4f16a56f5fa 100644
--- a/share/man/man4/ath.4
+++ b/share/man/man4/ath.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ath.4,v 1.55 2013/02/14 07:40:42 jmc Exp $
+.\"	$OpenBSD: ath.4,v 1.56 2013/06/02 20:23:33 tedu Exp $
 .\"     $NetBSD: ath.4,v 1.5 2004/07/03 16:58:18 mycroft Exp $
 .\"
 .\" Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting
@@ -42,7 +42,7 @@
 .\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath.4,v 1.16 2004/02/18 08:30:08 maxim Exp $
 .\" parts from $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath_hal.4,v 1.7 2004/01/07 20:49:51 blackend Exp $
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt ATH 4
 .Os
 .Sh NAME
@@ -222,77 +222,77 @@ wpakey mywpakey
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "ath%d: unable to attach hardware; HAL status %u"
+.It "ath0: unable to attach hardware; HAL status %u"
 The Hardware Access Layer was unable to configure the hardware
 as requested.
 The status code is explained in the HAL include file
 .Pa sys/dev/ic/ar5xxx.h .
-.It "ath%d: failed to allocate descriptors: %d"
+.It "ath0: failed to allocate descriptors: N"
 The driver was unable to allocate contiguous memory for the transmit
 and receive descriptors.
 This usually indicates system memory is scarce and/or fragmented.
-.It "ath%d: unable to setup a data xmit queue!"
+.It "ath0: unable to setup a data xmit queue!"
 The request to the HAL to set up the transmit queue for normal
 data frames failed.
 This should not happen.
-.It "ath%d: unable to setup a beacon xmit queue!"
+.It "ath0: unable to setup a beacon xmit queue!"
 The request to the HAL to set up the transmit queue for 802.11 beacon frames
 failed.
 This should not happen.
-.It "ath%d: hardware error; resetting"
+.It "ath0: hardware error; resetting"
 An unrecoverable error in the hardware occurred.
 Errors of this sort include unrecoverable DMA errors.
 The driver will reset the hardware and continue.
-.It "ath%d: rx FIFO overrun; resetting"
+.It "ath0: rx FIFO overrun; resetting"
 The receive FIFO in the hardware overflowed before the data could be
 transferred to the host.
 This typically occurs because the hardware ran short of receive
 descriptors and had no place to transfer received data.
 The driver will reset the hardware and continue.
-.It "ath%d: unable to reset hardware; hal status %u"
+.It "ath0: unable to reset hardware; hal status N"
 The Hardware Access Layer was unable to reset the hardware
 as requested.
 The status code is explained in the HAL include file
 .Pa /sys/dev/ic/ar5xxx.h .
 This should not happen.
-.It "ath%d: unable to initialize the key cache"
+.It "ath0: unable to initialize the key cache"
 The driver was unable to initialize the hardware key cache.
 This should not happen.
-.It "ath%d: unable to start recv logic"
+.It "ath0: unable to start recv logic"
 The driver was unable to restart frame reception.
 This should not happen.
-.It "ath%d: device timeout"
+.It "ath0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware and continue.
 This should not happen.
-.It "ath%d: bogus xmit rate 0x%x"
+.It "ath0: bogus xmit rate 0xNNNN"
 An invalid transmit rate was specified for an outgoing frame.
 The frame is discarded.
 This should not happen.
-.It "ath%d: ath_chan_set: unable to reset channel %u (%u MHz)"
+.It "ath0: ath_chan_set: unable to reset channel N (X MHz)"
 The Hardware Access Layer was unable to reset the hardware
 when switching channels during scanning.
 This should not happen.
-.It "ath%d: unable to allocate channel table"
+.It "ath0: unable to allocate channel table"
 The driver was unable to allocate memory for the table used to hold
 the set of available channels.
-.It "ath%d: unable to collect channel list from hal"
+.It "ath0: unable to collect channel list from hal"
 A problem occurred while querying the HAL to find the set of available
 channels for the device.
 This should not happen.
-.It "ath%d: failed to enable memory mapping"
+.It "ath0: failed to enable memory mapping"
 The driver was unable to enable memory-mapped I/O to the PCI device registers.
 This should not happen.
-.It "ath%d: failed to enable bus mastering"
+.It "ath0: failed to enable bus mastering"
 The driver was unable to enable the device as a PCI bus master for doing DMA.
 This should not happen.
-.It "ath%d: cannot map register space"
+.It "ath0: cannot map register space"
 The driver was unable to map the device registers into the host address space.
 This should not happen.
-.It "ath%d: could not map interrupt"
+.It "ath0: could not map interrupt"
 The driver was unable to allocate an IRQ for the device interrupt.
 This should not happen.
-.It "ath%d: could not establish interrupt"
+.It "ath0: could not establish interrupt"
 The driver was unable to install the device interrupt handler.
 This should not happen.
 .El
diff --git a/share/man/man4/athn.4 b/share/man/man4/athn.4
index 4b83baa1616..be7d6874a03 100644
--- a/share/man/man4/athn.4
+++ b/share/man/man4/athn.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: athn.4,v 1.22 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: athn.4,v 1.23 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 2009 Damien Bergamini <damien.bergamini@free.fr>.
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt ATHN 4
 .Os
 .Sh NAME
@@ -201,18 +201,18 @@ wpakey mywpakey
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "athn%d: device timeout"
+.It "athn0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
-.It "athn%d: radio is disabled by hardware switch"
+.It "athn0: radio is disabled by hardware switch"
 The radio transmitter is off and thus no packet can go out.
 The driver will reset the hardware.
 Make sure the laptop radio switch is on.
-.It "athn%d: radio switch turned off"
+.It "athn0: radio switch turned off"
 The radio switch has been turned off while the interface was up and running.
 The driver will turn the interface down.
-.It "athn%d: error %d, could not read firmware %s"
+.It "athn0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the firmware file from the
 filesystem.
 The file might be missing or corrupted.
diff --git a/share/man/man4/atw.4 b/share/man/man4/atw.4
index fca9fadb977..8384e8ebd0a 100644
--- a/share/man/man4/atw.4
+++ b/share/man/man4/atw.4
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: atw.4,v 1.32 2013/02/14 07:40:42 jmc Exp $
+.\"     $OpenBSD: atw.4,v 1.33 2013/06/02 20:23:33 tedu Exp $
 .\"	$NetBSD: atw.4,v 1.8 2004/06/06 04:05:49 wiz Exp $
 .\"
 .\" Copyright (c) 2003
@@ -28,7 +28,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt ATW 4
 .Os
 .Sh NAME
@@ -151,10 +151,10 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "atw0: failed to tune channel %d"
+.It "atw0: failed to tune channel N"
 The driver failed to tune the radio to a new channel.
 The radio remains tuned to the old channel.
-.It "atw0: atw_si4136_write wrote %08x, SYNCTL still busy"
+.It "atw0: atw_si4136_write wrote XXXX, SYNCTL still busy"
 The driver waited 100ms without seeing an indication that the
 ADM8211 had finished writing a register on the Si4126 RF/IF
 synthesizer.
diff --git a/share/man/man4/aue.4 b/share/man/man4/aue.4
index 0addc7c6cc6..c960e2c861d 100644
--- a/share/man/man4/aue.4
+++ b/share/man/man4/aue.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: aue.4,v 1.34 2012/08/18 08:44:25 jmc Exp $
+.\"	$OpenBSD: aue.4,v 1.35 2013/06/02 20:23:33 tedu Exp $
 .\"	$NetBSD: aue.4,v 1.9 2002/07/11 00:23:31 rh Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
@@ -33,7 +33,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/aue.4,v 1.2 2000/01/07 22:18:47 wpaul Exp $
 .\"
-.Dd $Mdocdate: August 18 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt AUE 4
 .Os
 .Sh NAME
@@ -170,11 +170,11 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "aue%d: watchdog timeout"
+.It "aue0: watchdog timeout"
 A packet was queued for transmission and a transmit command was
 issued, however the device failed to acknowledge the transmission
 before a timeout expired.
-.It "aue%d: no memory for rx list"
+.It "aue0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/axe.4 b/share/man/man4/axe.4
index 54b6fc5e703..415cac963a3 100644
--- a/share/man/man4/axe.4
+++ b/share/man/man4/axe.4
@@ -29,9 +29,9 @@
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/axe.4,v 1.3 2003/05/29 21:28:35 ru Exp $
-.\" $OpenBSD: axe.4,v 1.41 2012/11/14 17:00:23 jcs Exp $
+.\" $OpenBSD: axe.4,v 1.42 2013/06/02 20:23:33 tedu Exp $
 .\"
-.Dd $Mdocdate: November 14 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt AXE 4
 .Os
 .Sh NAME
@@ -134,11 +134,11 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "axe%d: watchdog timeout"
+.It "axe0: watchdog timeout"
 A packet was queued for transmission and a transmit command was
 issued, however the device failed to acknowledge the transmission
 before a timeout expired.
-.It "axe%d: no memory for rx list"
+.It "axe0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/bge.4 b/share/man/man4/bge.4
index eddce0baa14..d2d862f7887 100644
--- a/share/man/man4/bge.4
+++ b/share/man/man4/bge.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: bge.4,v 1.57 2013/03/30 05:34:53 brad Exp $
+.\" $OpenBSD: bge.4,v 1.58 2013/06/02 20:23:33 tedu Exp $
 .\" Copyright (c) 2001 Wind River Systems
 .\" Copyright (c) 1997, 1998, 1999, 2000, 2001
 .\"	Bill Paul <wpaul@windriver.com>. All rights reserved.
@@ -30,7 +30,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: March 30 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt BGE 4
 .Os
 .Sh NAME
@@ -175,11 +175,11 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "bge%d: can't find mem space"
+.It "bge0: can't find mem space"
 A fatal initialization error has occurred.
-.It "bge%d: couldn't map interrupt"
+.It "bge0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "bge%d: watchdog timeout -- resetting"
+.It "bge0: watchdog timeout -- resetting"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
 .El
diff --git a/share/man/man4/cdce.4 b/share/man/man4/cdce.4
index 92dbd0314d1..74d3461d089 100644
--- a/share/man/man4/cdce.4
+++ b/share/man/man4/cdce.4
@@ -25,9 +25,9 @@
 .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.\" $OpenBSD: cdce.4,v 1.16 2012/08/18 08:44:25 jmc Exp $
+.\" $OpenBSD: cdce.4,v 1.17 2013/06/02 20:23:33 tedu Exp $
 .\"
-.Dd $Mdocdate: August 18 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt CDCE 4
 .Os
 .Sh NAME
@@ -83,27 +83,27 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "cdce%d: extra ethernet descriptor"
+.It "cdce0: extra ethernet descriptor"
 There is more than one Ethernet descriptor.
-.It "cdce%d: no data interface"
+.It "cdce0: no data interface"
 The data interface announced by the union descriptor cannot be found.
-.It "cdce%d: no descriptor for interrupt endpoint %d"
-.It "cdce%d: interface alternate setting %d failed"
-.It "cdce%d: no descriptor for bulk endpoint %d"
-.It "cdce%d: could not find data bulk in/out"
+.It "cdce0: no descriptor for interrupt endpoint N"
+.It "cdce0: interface alternate setting N failed"
+.It "cdce0: no descriptor for bulk endpoint N"
+.It "cdce0: could not find data bulk in/out"
 For a manually added USB vendor/product, these errors indicate
 that the bridge is not compatible with the driver.
-.It "cdce%d: watchdog timeout"
+.It "cdce0: watchdog timeout"
 A packet was queued for transmission and a transmit command was
 issued, however the device failed to acknowledge the transmission
 before a timeout expired.
-.It "cdce%d: no memory for rx list -- packet dropped!"
+.It "cdce0: no memory for rx list -- packet dropped!"
 Memory allocation through MGETHDR or MCLGET failed, the system
 is running low on mbufs.
-.It "cdce%d: abort/close rx/tx/interrupt pipe failed"
-.It "cdce%d: rx/tx list init failed"
-.It "cdce%d: open rx/tx/interrupt pipe failed"
-.It "cdce%d: usb error on rx/tx"
+.It "cdce0: abort/close rx/tx/interrupt pipe failed"
+.It "cdce0: rx/tx list init failed"
+.It "cdce0: open rx/tx/interrupt pipe failed"
+.It "cdce0: usb error on rx/tx"
 .El
 .Sh SEE ALSO
 .Xr arp 4 ,
diff --git a/share/man/man4/com.4 b/share/man/man4/com.4
index 7acd905ebc9..8a580c8e6f5 100644
--- a/share/man/man4/com.4
+++ b/share/man/man4/com.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: com.4,v 1.34 2009/05/17 22:08:32 miod Exp $
+.\"	$OpenBSD: com.4,v 1.35 2013/06/02 20:23:33 tedu Exp $
 .\"	$NetBSD: com.4,v 1.5 1996/03/16 00:07:08 thorpej Exp $
 .\"
 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
@@ -33,7 +33,7 @@
 .\"
 .\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
 .\"
-.Dd $Mdocdate: May 17 2009 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt COM 4
 .Os
 .Sh NAME
@@ -133,11 +133,11 @@ of 115200.
 .El
 .Sh DIAGNOSTICS
 .Bl -diag
-.It com%d: %d silo overflows
+.It com0: N silo overflows
 The input
 .Dq silo
 has overflowed and incoming data has been lost.
-.It com%d: weird interrupt: iir=%x
+.It com0: weird interrupt: iir=XXXX
 The device has generated an unexpected interrupt
 with the code listed.
 .El
diff --git a/share/man/man4/cue.4 b/share/man/man4/cue.4
index ac66d57645c..70b3475a932 100644
--- a/share/man/man4/cue.4
+++ b/share/man/man4/cue.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: cue.4,v 1.13 2007/05/31 19:19:49 jmc Exp $
+.\" $OpenBSD: cue.4,v 1.14 2013/06/02 20:23:33 tedu Exp $
 .\" $NetBSD: cue.4,v 1.2 2000/01/16 13:54:39 augustss Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999, 2000
@@ -33,7 +33,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/cue.4,v 1.1 2000/01/14 03:14:47 wpaul Exp $
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt CUE 4
 .Os
 .Sh NAME
@@ -68,11 +68,11 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "cue%d: watchdog timeout"
+.It "cue0: watchdog timeout"
 A packet was queued for transmission and a transmit command was
 issued, however the device failed to acknowledge the transmission
 before a timeout expired.
-.It "cue%d: no memory for rx list"
+.It "cue0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/cy.4 b/share/man/man4/cy.4
index 84c0958b758..4bc4ae9bdec 100644
--- a/share/man/man4/cy.4
+++ b/share/man/man4/cy.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: cy.4,v 1.14 2007/05/31 19:19:49 jmc Exp $
+.\"	$OpenBSD: cy.4,v 1.15 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1993 Andrew Herbert.
 .\" All rights reserved.
@@ -25,7 +25,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt CY 4
 .Os
 .Sh NAME
@@ -54,12 +54,12 @@ The device minor numbers for this driver are encoded as follows:
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "cy%d: tty input queue overflow"
+.It "cy0: tty input queue overflow"
 Incoming characters have been discarded due to a buffer overflow.
 This is caused by the process in control of the device not
 .Xr read 2 Ns 'ing
 characters fast enough.
-.It "cy%d: receive fifo overrun"
+.It "cy0: receive fifo overrun"
 Incoming characters have been discarded due to a CD1400 channel overrun.
 This is caused by interrupts not being serviced sufficiently quickly to prevent
 the 12 byte receive FIFO on a serial channel from overflowing.
diff --git a/share/man/man4/dc.4 b/share/man/man4/dc.4
index 7e65667ec0f..e1b3874261e 100644
--- a/share/man/man4/dc.4
+++ b/share/man/man4/dc.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: dc.4,v 1.48 2012/08/18 08:44:25 jmc Exp $
+.\"	$OpenBSD: dc.4,v 1.49 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ee.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/dc.4,v 1.1 1999/12/04 17:41:24 wpaul Exp $
 .\"
-.Dd $Mdocdate: August 18 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt DC 4
 .Os
 .Sh NAME
@@ -227,19 +227,19 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "dc%d: couldn't map ports/memory"
+.It "dc0: couldn't map ports/memory"
 A fatal initialization error has occurred.
-.It "dc%d: couldn't map interrupt"
+.It "dc0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "dc%d: watchdog timeout"
+.It "dc0: watchdog timeout"
 A packet was queued for transmission and a transmit command was
 issued, however the device failed to acknowledge the transmission
 before a timeout expired.
 This can happen if the device is unable to deliver interrupts for some
 reason, or if there is a problem with the network connection (cable).
-.It "dc%d: no memory for rx list"
+.It "dc0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
-.It "dc%d: TX underrun -- increasing TX threshold"
+.It "dc0: TX underrun -- increasing TX threshold"
 The device generated a transmit underrun error while attempting to
 DMA and transmit a packet.
 This happens if the host is not able to DMA the packet data into the NIC's
@@ -247,13 +247,13 @@ FIFO fast enough.
 The driver will dynamically increase the transmit start threshold so that
 more data must be DMAed into the FIFO before the NIC will start
 transmitting it onto the wire.
-.It "dc%d: TX underrun -- using store and forward mode"
+.It "dc0: TX underrun -- using store and forward mode"
 The device continued to generate transmit underruns even after all
 possible transmit start threshold settings had been tried, so the
 driver programmed the chip for store and forward mode.
 In this mode, the NIC will not begin transmission until the entire packet
 has been transferred into its FIFO memory.
-.It "dc%d: chip is in D3 power state -- setting to D0"
+.It "dc0: chip is in D3 power state -- setting to D0"
 This message applies only to adapters which support power management.
 Some operating systems place the controller in low power
 mode when shutting down, and some PCI BIOSes fail to bring the chip
diff --git a/share/man/man4/de.4 b/share/man/man4/de.4
index 8e734353327..0bc37723e34 100644
--- a/share/man/man4/de.4
+++ b/share/man/man4/de.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: de.4,v 1.22 2008/09/07 06:55:34 jmc Exp $
+.\"	$OpenBSD: de.4,v 1.23 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1997 David E. O'Brien
 .\"
@@ -24,7 +24,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: September 7 2008 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt DE 4
 .Os
 .Sh NAME
@@ -97,17 +97,17 @@ The old
 method of configuration is not supported.
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "de%d: waking device from sleep/snooze mode"
+.It "de0: waking device from sleep/snooze mode"
 The 21041 and 21140A chips support suspending the operation of the card.
-.It "de%d: error: desired IRQ of %d does not match device's actual IRQ of %d"
+.It "de0: error: desired IRQ of X does not match device's actual IRQ of Y"
 The device probe detected that the board is configured for a different
 interrupt than the one specified in the kernel configuration file.
-.It "de%d: not configured; limit of %d reached or exceeded"
+.It "de0: not configured; limit of N reached or exceeded"
 There is a limit of 32
 .Nm
 devices allowed in a single machine.
-.It "de%d: not configured; 21040 pass 2.0 required (%d.%d found)"
-.It "de%d: not configured; 21140 pass 1.1 required (%d.%d found)"
+.It "de0: not configured; 21040 pass 2.0 required (X.Y found)"
+.It "de0: not configured; 21140 pass 1.1 required (X.Y found)"
 Certain revisions of the chipset are not supported by this driver.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/ef.4 b/share/man/man4/ef.4
index 3f341ef22b5..2bdf7841e14 100644
--- a/share/man/man4/ef.4
+++ b/share/man/man4/ef.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ef.4,v 1.16 2007/05/31 19:19:50 jmc Exp $
+.\"	$OpenBSD: ef.4,v 1.17 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1998 Jason L. Wright (jason@thought.net)
 .\" All rights reserved.
@@ -24,7 +24,7 @@
 .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt EF 4
 .Os
 .Sh NAME
@@ -65,12 +65,12 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "ef%d: adapter failure (%x)"
+.It "ef0: adapter failure (XXXX)"
 A fatal error during receive or transmit has occurred.
-.It "ef%d: eeprom failed to come ready"
+.It "ef0: eeprom failed to come ready"
 When reading/writing the EEPROM, the busy bit failed to clear.
 This may indicate a hardware problem.
-.It "ef%d: device timeout"
+.It "ef0: device timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
 .El
diff --git a/share/man/man4/eg.4 b/share/man/man4/eg.4
index 545be4e5d1d..19e053b18cd 100644
--- a/share/man/man4/eg.4
+++ b/share/man/man4/eg.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: eg.4,v 1.9 2008/09/07 06:55:34 jmc Exp $
+.\"	$OpenBSD: eg.4,v 1.10 2013/06/02 20:23:33 tedu Exp $
 .\"     $NetBSD: ec.4,v 1.4 1998/08/09 00:39:02 thorpej Exp $
 .\"
 .\" Copyright (c) 1997 The NetBSD Foundation, Inc.
@@ -29,7 +29,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: September 7 2008 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt EG 4
 .Os
 .Sh NAME
@@ -50,10 +50,10 @@ For example,
 .Dq ifconfig eg0 media .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "eg%d: device timeout"
+.It "eg0: device timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "eg%d: invalid packet size %d; dropping"
+.It "eg0: invalid packet size N; dropping"
 A packet of an invalid length (less than size of Ethernet header or greater
 than maximum size of Ethernet frame) was received and dropped.
 .El
diff --git a/share/man/man4/el.4 b/share/man/man4/el.4
index cf54a360b81..7e4d8edc82c 100644
--- a/share/man/man4/el.4
+++ b/share/man/man4/el.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: el.4,v 1.9 2008/09/07 06:55:34 jmc Exp $
+.\"	$OpenBSD: el.4,v 1.10 2013/06/02 20:23:33 tedu Exp $
 .\"     $NetBSD: ec.4,v 1.4 1998/08/09 00:39:02 thorpej Exp $
 .\"
 .\" Copyright (c) 1997 The NetBSD Foundation, Inc.
@@ -29,7 +29,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: September 7 2008 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt EL 4
 .Os
 .Sh NAME
@@ -50,10 +50,10 @@ For example,
 .Dq ifconfig el0 media .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "el%d: device timeout"
+.It "el0: device timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "el%d: invalid packet size %d; dropping"
+.It "el0: invalid packet size N; dropping"
 A packet of an invalid length (less than size of Ethernet header or greater
 than maximum size of Ethernet frame) was received and dropped.
 .El
diff --git a/share/man/man4/fpa.4 b/share/man/man4/fpa.4
index 042fcbe4065..41b4079f6e8 100644
--- a/share/man/man4/fpa.4
+++ b/share/man/man4/fpa.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: fpa.4,v 1.25 2009/12/13 16:01:51 sobrado Exp $
+.\"	$OpenBSD: fpa.4,v 1.26 2013/06/02 20:23:33 tedu Exp $
 .\"	$NetBSD: fpa.4,v 1.2 1997/02/18 01:07:46 jonathan Exp $
 .\"
 .\" Copyright (c) 1995 The NetBSD Foundation, Inc.
@@ -28,7 +28,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: December 13 2009 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt FPA 4
 .Os
 .Sh NAME
@@ -52,10 +52,10 @@ All variants of either controller are supported including the DAS and
 SAS configurations.
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "fea%d: error: desired IRQ of %d does not match device's actual IRQ (%d)"
+.It "fea0: error: desired IRQ of X does not match device's actual IRQ (Y)"
 The device probe detected that the DEFEA board is configured for a different
 interrupt than the one specified in the kernel configuration file.
-.It "fea%d: error: memory not enabled! ECU reconfiguration required"
+.It "fea0: error: memory not enabled! ECU reconfiguration required"
 The device probe found that no device memory had been configured on the
 DEFEA.
 The DEFEA can be configured with no device memory, this driver
diff --git a/share/man/man4/fxp.4 b/share/man/man4/fxp.4
index 45e454cdded..f588ad74593 100644
--- a/share/man/man4/fxp.4
+++ b/share/man/man4/fxp.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: fxp.4,v 1.43 2013/03/30 05:30:57 brad Exp $
+.\"	$OpenBSD: fxp.4,v 1.44 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1997 David E. O'Brien
 .\"
@@ -24,7 +24,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: March 30 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt FXP 4
 .Os
 .Sh NAME
@@ -103,16 +103,16 @@ interface is brought up:
 If a file is missing, the driver attempts to operate anyway.
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "fxp%d: couldn't map memory"
+.It "fxp0: couldn't map memory"
 A fatal initialization error has occurred.
-.It "fxp%d: couldn't map interrupt"
+.It "fxp0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "fxp%d: Failed to malloc memory"
+.It "fxp0: Failed to malloc memory"
 There are not enough mbufs available for allocation.
-.It "fxp%d: device timeout"
+.It "fxp0: device timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "fxp%d: error %d, could not read firmware %s"
+.It "fxp0: error N, could not read firmware ..."
 The device is able to do interrupt coalescing but required firmware file
 is missing.
 .El
diff --git a/share/man/man4/ipw.4 b/share/man/man4/ipw.4
index 54ed39e4526..8846c95bfd5 100644
--- a/share/man/man4/ipw.4
+++ b/share/man/man4/ipw.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ipw.4,v 1.38 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: ipw.4,v 1.39 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 2004
 .\"	Damien Bergamini <damien.bergamini@free.fr>. All rights reserved.
@@ -25,7 +25,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt IPW 4
 .Os
 .Sh NAME
@@ -129,10 +129,10 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "ipw%d: device timeout"
+.It "ipw0: device timeout"
 The driver will reset the hardware.
 This should not happen.
-.It "ipw%d: error %d, could not read firmware %s"
+.It "ipw0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the firmware image from the
 filesystem.
 The file might be missing or corrupted.
diff --git a/share/man/man4/iwi.4 b/share/man/man4/iwi.4
index 442554c6977..bb6a475d8ac 100644
--- a/share/man/man4/iwi.4
+++ b/share/man/man4/iwi.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: iwi.4,v 1.44 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: iwi.4,v 1.45 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 2004
 .\"	Damien Bergamini <damien.bergamini@free.fr>. All rights reserved.
@@ -25,7 +25,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt IWI 4
 .Os
 .Sh NAME
@@ -128,10 +128,10 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "iwi%d: device timeout"
+.It "iwi0: device timeout"
 The driver will reset the hardware.
 This should not happen.
-.It "iwi%d: error %d, could not read firmware %s"
+.It "iwi0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the firmware image from the
 filesystem.
 The file might be missing or corrupted.
diff --git a/share/man/man4/iwn.4 b/share/man/man4/iwn.4
index 727b8195fa4..a66cdbe4ae1 100644
--- a/share/man/man4/iwn.4
+++ b/share/man/man4/iwn.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: iwn.4,v 1.36 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: iwn.4,v 1.37 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 2007,2008
 .\"	Damien Bergamini <damien.bergamini@free.fr>. All rights reserved.
@@ -15,7 +15,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt IWN 4
 .Os
 .Sh NAME
@@ -150,25 +150,25 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "iwn%d: device timeout"
+.It "iwn0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
-.It "iwn%d: fatal firmware error"
+.It "iwn0: fatal firmware error"
 For some reason, the firmware crashed.
 The driver will reset the hardware.
 This should not happen.
-.It "iwn%d: radio is disabled by hardware switch"
+.It "iwn0: radio is disabled by hardware switch"
 The radio transmitter is off and thus no packet can go out.
 The driver will reset the hardware.
 Make sure the laptop radio switch is on.
-.It "iwn%d: error %d, could not read firmware %s"
+.It "iwn0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the firmware image from the
 filesystem.
 The file might be missing or corrupted.
-.It "iwn%d: firmware file too short: %d bytes"
+.It "iwn0: firmware file too short: N bytes"
 The firmware image is corrupted and can't be loaded into the adapter.
-.It "iwn%d: could not load firmware"
+.It "iwn0: could not load firmware"
 An attempt to load the firmware into the adapter failed.
 The driver will reset the hardware.
 .El
diff --git a/share/man/man4/kue.4 b/share/man/man4/kue.4
index 351cd657dc3..e8588d6e1e8 100644
--- a/share/man/man4/kue.4
+++ b/share/man/man4/kue.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: kue.4,v 1.19 2007/05/31 19:19:50 jmc Exp $
+.\" $OpenBSD: kue.4,v 1.20 2013/06/02 20:23:33 tedu Exp $
 .\" $NetBSD: kue.4,v 1.5 2000/03/20 01:34:22 augustss Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999, 2000
@@ -33,7 +33,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/kue.4,v 1.2 2000/01/07 22:18:48 wpaul Exp $
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt KUE 4
 .Os
 .Sh NAME
@@ -98,11 +98,11 @@ which is loaded on demand when the device is attached:
 .El
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "kue%d: watchdog timeout"
+.It "kue0: watchdog timeout"
 A packet was queued for transmission and a transmit command was
 issued, however the device failed to acknowledge the transmission
 before a timeout expired.
-.It "kue%d: no memory for rx list"
+.It "kue0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/lge.4 b/share/man/man4/lge.4
index 7563d5607bf..1b44f168b7e 100644
--- a/share/man/man4/lge.4
+++ b/share/man/man4/lge.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: lge.4,v 1.23 2012/09/17 21:17:06 sthen Exp $
+.\" $OpenBSD: lge.4,v 1.24 2013/06/02 20:23:33 tedu Exp $
 .\" Copyright (c) 2001 Wind River Systems
 .\" Copyright (c) 1997, 1998, 1999, 2000, 2001
 .\"	Bill Paul <william.paul@windriver.com>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/lge.4,v 1.3 2001/07/06 08:34:13 ru Exp $
 .\"
-.Dd $Mdocdate: September 17 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt LGE 4
 .Os
 .Sh NAME
@@ -103,14 +103,14 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "lge%d: can't map i/o space"
+.It "lge0: can't map i/o space"
 A fatal initialization error has occurred.
-.It "lge%d: couldn't map interrupt"
+.It "lge0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "lge%d: no memory for jumbo buffer queue!"
+.It "lge0: no memory for jumbo buffer queue!"
 The driver failed to allocate memory for jumbo frames during
 initialization.
-.It "lge%d: watchdog timeout"
+.It "lge0: watchdog timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
 .El
diff --git a/share/man/man4/lmc.4 b/share/man/man4/lmc.4
index 848776b1adc..1ca6a03cd6a 100644
--- a/share/man/man4/lmc.4
+++ b/share/man/man4/lmc.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: lmc.4,v 1.25 2011/07/25 07:54:41 jmc Exp $
+.\" $OpenBSD: lmc.4,v 1.26 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1999 Chris Cappuccio
 .\"
@@ -24,7 +24,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: July 25 2011 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt LMC 4
 .Os
 .Sh NAME
@@ -63,28 +63,28 @@ interface should be configured as a point-to-point
 link.
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "lmc%d: couldn't map interrupt"
+.It "lmc0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "lmc%d: couldn't establish interrupt"
+.It "lmc0: couldn't establish interrupt"
 A fatal initialization error has occurred.
-.It "lmc%d: enabling keepalive"
+.It "lmc0: enabling keepalive"
 Cisco HDLC keepalive packets will be transmitted.
-.It "lmc%d: disabling keepalive"
+.It "lmc0: disabling keepalive"
 Cisco HDLC keepalive packets will not be transmitted.
-.It "lmc%d: clock internal"
+.It "lmc0: clock internal"
 The card is using internal clocking for the line.
-.It "lmc%d: clock external"
+.It "lmc0: clock external"
 The card is using external clocking for the line.
-.It "lmc%d: asserting DTR and RTS"
+.It "lmc0: asserting DTR and RTS"
 The card is sending DTR and RTS signals on the line.
-.It "lmc%d: deasserting DTR and RTS"
+.It "lmc0: deasserting DTR and RTS"
 The card is not sending DTR and RTS signals on the line.
-.It "lmc%d: Abnormal interrupt"
+.It "lmc0: Abnormal interrupt"
 The card received an incomplete request.
 This may be a sign of a hardware fault.
-.It "lmc%d: tx_intr: failed to dequeue mbuf?!?"
+.It "lmc0: tx_intr: failed to dequeue mbuf?!?"
 Only available if compiled with LMC_DEBUG.
-.It "lmc%d: txput: tx not running"
+.It "lmc0: txput: tx not running"
 Problem from tulip.
 Only available if compiled with LMC_DEBUG.
 .El
diff --git a/share/man/man4/lo.4 b/share/man/man4/lo.4
index efde1b8343d..8ef0363fcc3 100644
--- a/share/man/man4/lo.4
+++ b/share/man/man4/lo.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: lo.4,v 1.27 2011/04/02 14:38:09 henning Exp $
+.\"	$OpenBSD: lo.4,v 1.28 2013/06/02 20:23:33 tedu Exp $
 .\"	$NetBSD: lo.4,v 1.3 1994/11/30 16:22:23 jtc Exp $
 .\"
 .\" Copyright (c) 1983, 1991, 1993
@@ -30,7 +30,7 @@
 .\"
 .\"     @(#)lo.4	8.1 (Berkeley) 6/5/93
 .\"
-.Dd $Mdocdate: April 2 2011 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt LO 4
 .Os
 .Sh NAME
@@ -72,7 +72,7 @@ be configured first unless no hardware
 interfaces exist.
 .Sh DIAGNOSTICS
 .Bl -diag
-.It lo%d: can't handle af%d.
+.It lo0: can't handle afX.
 The interface was handed
 a message with addresses formatted in an unsuitable address
 family; the packet was dropped.
diff --git a/share/man/man4/mos.4 b/share/man/man4/mos.4
index 411b3406a6f..ee416e95056 100644
--- a/share/man/man4/mos.4
+++ b/share/man/man4/mos.4
@@ -29,9 +29,9 @@
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/axe.4,v 1.3 2003/05/29 21:28:35 ru Exp $
-.\" $OpenBSD: mos.4,v 1.8 2012/08/18 08:44:25 jmc Exp $
+.\" $OpenBSD: mos.4,v 1.9 2013/06/02 20:23:33 tedu Exp $
 .\"
-.Dd $Mdocdate: August 18 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt MOS 4
 .Os
 .Sh NAME
@@ -95,11 +95,11 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "mos%d: watchdog timeout"
+.It "mos0: watchdog timeout"
 A packet was queued for transmission and a transmit command was
 issued, however the device failed to acknowledge the transmission
 before a timeout expired.
-.It "mos%d: no memory for rx list"
+.It "mos0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/otus.4 b/share/man/man4/otus.4
index 428ee8f0ada..b361502d8fa 100644
--- a/share/man/man4/otus.4
+++ b/share/man/man4/otus.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: otus.4,v 1.22 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: otus.4,v 1.23 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 2009 Damien Bergamini <damien.bergamini@free.fr>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt OTUS 4
 .Os
 .Sh NAME
@@ -123,11 +123,11 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "otus%d: error %d, could not read firmware %s"
+.It "otus0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the microcode file from the
 filesystem.
 The file might be missing or corrupted.
-.It "otus%d: device timeout"
+.It "otus0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
diff --git a/share/man/man4/ppp.4 b/share/man/man4/ppp.4
index dc2ebd225cb..8477d875391 100644
--- a/share/man/man4/ppp.4
+++ b/share/man/man4/ppp.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ppp.4,v 1.13 2012/09/26 17:34:38 jmc Exp $
+.\"	$OpenBSD: ppp.4,v 1.14 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1983, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
@@ -29,7 +29,7 @@
 .\"
 .\"     From:	@(#)lo.4	8.1 (Berkeley) 6/5/93
 .\"
-.Dd $Mdocdate: September 26 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt PPP 4
 .Os
 .Sh NAME
@@ -61,7 +61,7 @@ over the SLIP protocol used by the
 interface.
 .Sh DIAGNOSTICS
 .Bl -diag
-.It ppp%d: af%d not supported
+.It ppp0: afX not supported
 The interface was handed
 a message with addresses formatted in an unsuitable address
 family; the packet was dropped.
diff --git a/share/man/man4/rl.4 b/share/man/man4/rl.4
index a0a450d045f..2520cb1681f 100644
--- a/share/man/man4/rl.4
+++ b/share/man/man4/rl.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: rl.4,v 1.34 2013/01/29 01:45:05 brad Exp $
+.\"	$OpenBSD: rl.4,v 1.35 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\"	$FreeBSD: rl.4,v 1.7 1998/12/24 18:52:47 wpaul Exp $
 .\"
-.Dd $Mdocdate: January 29 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt RL 4
 .Os
 .Sh NAME
@@ -148,19 +148,19 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "rl%d: couldn't map memory"
+.It "rl0: couldn't map memory"
 A fatal initialization error has occurred.
-.It "rl%d: couldn't map interrupt"
+.It "rl0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "rl%d: watchdog timeout"
+.It "rl0: watchdog timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "rl%d: no memory for rx list"
+.It "rl0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
-.It "rl%d: no memory for tx list"
+.It "rl0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "rl%d: chip is in D3 power state -- setting to D0"
+.It "rl0: chip is in D3 power state -- setting to D0"
 This message applies only to adapters which support power
 management.
 Some operating systems place the controller in low power
diff --git a/share/man/man4/rsu.4 b/share/man/man4/rsu.4
index d88203cc5f2..3fbb50186c4 100644
--- a/share/man/man4/rsu.4
+++ b/share/man/man4/rsu.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: rsu.4,v 1.12 2013/05/11 22:04:21 jmc Exp $
+.\" $OpenBSD: rsu.4,v 1.13 2013/06/02 20:23:33 tedu Exp $
 .\"
 .\" Copyright (c) 2010 Damien Bergamini <damien.bergamini@free.fr>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: May 11 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt RSU 4
 .Os
 .Sh NAME
@@ -116,11 +116,11 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "rsu%d: error %d, could not read firmware %s"
+.It "rsu0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the microcode file from the
 filesystem.
 The file might be missing or corrupted.
-.It "rsu%d: device timeout"
+.It "rsu0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
diff --git a/share/man/man4/rum.4 b/share/man/man4/rum.4
index 77dd1af7637..75bcffe7311 100644
--- a/share/man/man4/rum.4
+++ b/share/man/man4/rum.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: rum.4,v 1.51 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: rum.4,v 1.52 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2005-2007
 .\"	Damien Bergamini <damien.bergamini@free.fr>
@@ -15,7 +15,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt RUM 4
 .Os
 .Sh NAME
@@ -178,14 +178,14 @@ wpakey mywpakey
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "rum%d: error %d, could not read firmware %s"
+.It "rum0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the microcode file from the
 filesystem.
 The file might be missing or corrupted.
-.It "rum%d: could not load 8051 microcode"
+.It "rum0: could not load 8051 microcode"
 An error occurred while attempting to upload the microcode to the onboard 8051
 microcontroller unit.
-.It "rum%d: device timeout"
+.It "rum0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
diff --git a/share/man/man4/run.4 b/share/man/man4/run.4
index eecc40586ad..d4ca1820e3f 100644
--- a/share/man/man4/run.4
+++ b/share/man/man4/run.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: run.4,v 1.38 2013/05/15 20:49:10 jmc Exp $
+.\" $OpenBSD: run.4,v 1.39 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2008 Damien Bergamini <damien.bergamini@free.fr>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: May 15 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt RUN 4
 .Os
 .Sh NAME
@@ -175,14 +175,14 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "run%d: error %d, could not read firmware %s"
+.It "run0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the microcode file from the
 filesystem.
 The file might be missing or corrupted.
-.It "run%d: could not load 8051 microcode"
+.It "run0: could not load 8051 microcode"
 An error occurred while attempting to upload the microcode to the onboard 8051
 microcontroller unit.
-.It "run%d: device timeout"
+.It "run0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
diff --git a/share/man/man4/safe.4 b/share/man/man4/safe.4
index 455e70da8a1..65cd6f22f48 100644
--- a/share/man/man4/safe.4
+++ b/share/man/man4/safe.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: safe.4,v 1.7 2007/05/31 19:19:51 jmc Exp $
+.\"	$OpenBSD: safe.4,v 1.8 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2003	Sam Leffler, Errno Consulting
 .\" All rights reserved.
@@ -26,7 +26,7 @@
 .\"
 .\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/safe.4,v 1.1 2003/07/21 21:52:14 sam Exp $
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt SAFE 4
 .Os
 .Sh NAME
@@ -63,7 +63,7 @@ input to the
 subsystem.
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "safe%d: Reduce max DMA size to %u words for rev %u.%u"
+.It "safe0: Reduce max DMA size to N words for rev X.Y"
 The 1.0 silicon has major
 .Xr pci 4
 bugs and may lock the bus completely.
diff --git a/share/man/man4/san.4 b/share/man/man4/san.4
index 7635e72fd61..f80e2bd15ef 100644
--- a/share/man/man4/san.4
+++ b/share/man/man4/san.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: san.4,v 1.8 2009/11/16 17:33:31 sobrado Exp $
+.\"	$OpenBSD: san.4,v 1.9 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2001-2004 Sangoma Technologies (SAN)
 .\" All rights reserved.  www.sangoma.com
@@ -31,7 +31,7 @@
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\"
-.Dd $Mdocdate: November 16 2009 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt SAN 4
 .Os
 .Sh NAME
@@ -90,13 +90,13 @@ If the timeslot option is not present, the
 driver configures the card to use all the channels.
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "san%d: couldn't map memory"
+.It "san0: couldn't map memory"
 A fatal initialization error has occurred.
-.It "san%d: No PCI memory allocated for CPU #B"
+.It "san0: No PCI memory allocated for CPU #B"
 A fatal initialization error has occurred.
-.It "san%d: couldn't map interrupt"
+.It "san0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "san%d: IRQ not allocated"
+.It "san0: IRQ not allocated"
 A fatal initialization error has occurred.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/se.4 b/share/man/man4/se.4
index 7df9fe7ce86..c9b5599fdf9 100644
--- a/share/man/man4/se.4
+++ b/share/man/man4/se.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: se.4,v 1.6 2012/02/28 08:18:48 jsg Exp $
+.\"	$OpenBSD: se.4,v 1.7 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2010
 .\"	Christopher Zimmermann <madroach@zakweb.de>. All rights reserved.
@@ -34,7 +34,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/sis.4,v 1.2 1999/11/15 23:14:27 phantom Exp $
 .\"
-.Dd $Mdocdate: February 28 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt SE 4
 .Os
 .Sh NAME
@@ -110,19 +110,19 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "se%d: EEPROM read timeout"
+.It "se0: EEPROM read timeout"
 The driver could not read the controller's MAC address from its EEPROM.
-.It "se%d: invalid EEPROM signature"
+.It "se0: invalid EEPROM signature"
 The driver could not find the expected EEPROM signature and could not read
 the controller's MAC address.
-.It "se%d: Could not find PCI-ISA bridge"
+.It "se0: Could not find PCI-ISA bridge"
 The driver could not read the controller's MAC address from the CMOS memory
 connected to the PCI-ISA bridge.
-.It "se%d: PHY read timeout"
+.It "se0: PHY read timeout"
 The driver could not read data from the PHY.
-.It "se%d: PHY write timeout"
+.It "se0: PHY write timeout"
 The driver could not write data to the PHY.
-.It "se%d: watchdog timeout"
+.It "se0: watchdog timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
 .El
diff --git a/share/man/man4/sis.4 b/share/man/man4/sis.4
index 808155d8686..8e63072194a 100644
--- a/share/man/man4/sis.4
+++ b/share/man/man4/sis.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: sis.4,v 1.29 2013/03/30 05:34:53 brad Exp $
+.\"	$OpenBSD: sis.4,v 1.30 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ee.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/sis.4,v 1.2 1999/11/15 23:14:27 phantom Exp $
 .\"
-.Dd $Mdocdate: March 30 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt SIS 4
 .Os
 .Sh NAME
@@ -121,19 +121,19 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "sis%d: couldn't map ports/memory"
+.It "sis0: couldn't map ports/memory"
 A fatal initialization error has occurred.
-.It "sis%d: couldn't map interrupt"
+.It "sis0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "sis%d: watchdog timeout"
+.It "sis0: watchdog timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "sis%d: no memory for rx list"
+.It "sis0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
-.It "sis%d: no memory for tx list"
+.It "sis0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "sis%d: chip is in D3 power state -- setting to D0"
+.It "sis0: chip is in D3 power state -- setting to D0"
 This message applies only to adapters which support power management.
 Some operating systems place the controller in low power
 mode when shutting down, and some PCI BIOSes fail to bring the chip
diff --git a/share/man/man4/sl.4 b/share/man/man4/sl.4
index dc88241dc23..62f2fe37ac3 100644
--- a/share/man/man4/sl.4
+++ b/share/man/man4/sl.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: sl.4,v 1.16 2008/01/06 09:53:17 mbalmer Exp $
+.\"	$OpenBSD: sl.4,v 1.17 2013/06/02 20:23:34 tedu Exp $
 .\"	$NetBSD: sl.4,v 1.1 1996/08/10 21:26:14 explorer Exp $
 .\"
 .\" Copyright (c) 1983, 1991, 1993
@@ -30,7 +30,7 @@
 .\"
 .\"     From:	@(#)lo.4	8.1 (Berkeley) 6/5/93
 .\"
-.Dd $Mdocdate: January 6 2008 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt SL 4
 .Os
 .Sh NAME
@@ -68,7 +68,7 @@ Auto-enable Van Jacobsen TCP header compression
 .El
 .Sh DIAGNOSTICS
 .Bl -diag
-.It sl%d: af%d not supported.
+.It sl0: afX not supported.
 The interface was handed
 a message with addresses formatted in an unsuitable address
 family; the packet was dropped.
diff --git a/share/man/man4/ste.4 b/share/man/man4/ste.4
index 60940aee54b..89b194c7a2a 100644
--- a/share/man/man4/ste.4
+++ b/share/man/man4/ste.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ste.4,v 1.23 2012/08/18 08:44:25 jmc Exp $
+.\"	$OpenBSD: ste.4,v 1.24 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/ste.4,v 1.3 1999/11/15 23:14:27 phantom Exp $
 .\"
-.Dd $Mdocdate: August 18 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt STE 4
 .Os
 .Sh NAME
@@ -110,19 +110,19 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "ste%d: couldn't map ports/memory"
+.It "ste0: couldn't map ports/memory"
 A fatal initialization error has occurred.
-.It "ste%d: couldn't map interrupt"
+.It "ste0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "ste%d: watchdog timeout"
+.It "ste0: watchdog timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "ste%d: no memory for rx list"
+.It "ste0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
-.It "ste%d: no memory for tx list"
+.It "ste0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "ste%d: chip is in D3 power state -- setting to D0"
+.It "ste0: chip is in D3 power state -- setting to D0"
 This message applies only to adapters which support power
 management.
 Some operating systems place the controller in low power
diff --git a/share/man/man4/ti.4 b/share/man/man4/ti.4
index 2c7a51c8459..3dbdee200fb 100644
--- a/share/man/man4/ti.4
+++ b/share/man/man4/ti.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ti.4,v 1.40 2012/09/17 21:17:06 sthen Exp $
+.\"	$OpenBSD: ti.4,v 1.41 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\"	$FreeBSD: src/share/man/man4/ti.4,v 1.11 2000/08/10 19:47:32 billf Exp $
 .\"
-.Dd $Mdocdate: September 17 2012 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt TI 4
 .Os
 .Sh NAME
@@ -155,35 +155,35 @@ when the device is attached:
 .El
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "ti%d: couldn't map memory"
+.It "ti0: couldn't map memory"
 A fatal initialization error has occurred.
-.It "ti%d: couldn't map interrupt"
+.It "ti0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "ti%d: no memory for softc struct!"
+.It "ti0: no memory for softc struct!"
 The driver failed to allocate memory for per-device instance information
 during initialization.
-.It "ti%d: failed to enable memory mapping!"
+.It "ti0: failed to enable memory mapping!"
 The driver failed to initialize PCI shared memory mapping.
 This might happen if the card is not in a bus-master slot.
-.It "ti%d: no memory for jumbo buffers!"
+.It "ti0: no memory for jumbo buffers!"
 The driver failed to allocate memory for Jumbo frames during
 initialization.
-.It "ti%d: bios thinks we're in a 64 bit slot, but we aren't"
+.It "ti0: bios thinks we're in a 64 bit slot, but we aren't"
 The BIOS has programmed the NIC as though it had been installed in
 a 64-bit PCI slot, but in fact the NIC is in a 32-bit slot.
 This happens as a result of a bug in some BIOSes.
 This can be worked around on the Tigon II, but
 on the Tigon I initialization will fail.
-.It "ti%d: board self-diagnostics failed!"
+.It "ti0: board self-diagnostics failed!"
 The ROMFAIL bit in the CPU state register was set after system
 startup, indicating that the on-board NIC diagnostics failed.
-.It "ti%d: unknown hwrev"
+.It "ti0: unknown hwrev"
 The driver detected a board with an unsupported hardware revision.
 The
 .Nm
 driver supports revision 4 (Tigon 1) and revision 6 (Tigon 2) chips
 and has firmware only for those devices.
-.It "ti%d: watchdog timeout -- resetting"
+.It "ti0: watchdog timeout -- resetting"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
 .El
diff --git a/share/man/man4/tl.4 b/share/man/man4/tl.4
index 732cf3d37d1..e3a6715c248 100644
--- a/share/man/man4/tl.4
+++ b/share/man/man4/tl.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: tl.4,v 1.20 2011/03/28 15:25:37 claudio Exp $
+.\"	$OpenBSD: tl.4,v 1.21 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -30,9 +30,9 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.\"	$Id: tl.4,v 1.20 2011/03/28 15:25:37 claudio Exp $
+.\"	$Id: tl.4,v 1.21 2013/06/02 20:23:34 tedu Exp $
 .\"
-.Dd $Mdocdate: March 28 2011 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt TL 4
 .Os
 .Sh NAME
@@ -102,16 +102,16 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "tl%d: couldn't map memory"
+.It "tl0: couldn't map memory"
 A fatal initialization error has occurred.
-.It "tl%d: couldn't map interrupt"
+.It "tl0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "tl%d: device timeout"
+.It "tl0: device timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "tl%d: no memory for rx list"
+.It "tl0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
-.It "tl%d: no memory for tx list"
+.It "tl0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
 .El
diff --git a/share/man/man4/uath.4 b/share/man/man4/uath.4
index 7fc741d8411..d4a3fc1fafc 100644
--- a/share/man/man4/uath.4
+++ b/share/man/man4/uath.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: uath.4,v 1.28 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: uath.4,v 1.29 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2006
 .\"     Damien Bergamini <damien.bergamini@free.fr>
@@ -15,7 +15,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt UATH 4
 .Os
 .Sh NAME
@@ -140,22 +140,22 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "uath%d: error %d, could not read firmware %s"
+.It "uath0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the firmware image from the
 filesystem.
 The file might be missing or corrupted.
-.It "uath%d: could not load firmware (error=%s)"
+.It "uath0: could not load firmware (error=%s)"
 An error occurred while attempting to upload the firmware to the onboard
 MIPS R4000 processor.
-.It "uath%d: could not initialize adapter (error=%d)"
+.It "uath0: could not initialize adapter (error=N)"
 The firmware was uploaded successfully but did not initialize properly or
 in time.
-.It "uath%d: could not send command (error=%s)"
+.It "uath0: could not send command (error=%s)"
 An attempt to send a command to the firmware failed.
-.It "uath%d: timeout waiting for command reply"
+.It "uath0: timeout waiting for command reply"
 A read command was sent to the firmware but the firmware failed to reply in
 time.
-.It "uath%d: device timeout"
+.It "uath0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
diff --git a/share/man/man4/ural.4 b/share/man/man4/ural.4
index 1d549ef6021..b40b523c61d 100644
--- a/share/man/man4/ural.4
+++ b/share/man/man4/ural.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ural.4,v 1.15 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: ural.4,v 1.16 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2005-2007
 .\"	Damien Bergamini <damien.bergamini@free.fr>
@@ -15,7 +15,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt URAL 4
 .Os
 .Sh NAME
@@ -156,7 +156,7 @@ wpakey mywpakey
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "ural%d: device timeout"
+.It "ural0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
diff --git a/share/man/man4/url.4 b/share/man/man4/url.4
index 63093dd580f..be66c215667 100644
--- a/share/man/man4/url.4
+++ b/share/man/man4/url.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: url.4,v 1.19 2008/06/26 05:42:07 ray Exp $
+.\"	$OpenBSD: url.4,v 1.20 2013/06/02 20:23:34 tedu Exp $
 .\"	$NetBSD: url.4,v 1.4 2002/04/02 20:45:40 augustss Exp $
 .\"
 .\" Copyright (c) 2002 The NetBSD Foundation, Inc.
@@ -25,7 +25,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: June 26 2008 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt URL 4
 .Os
 .Sh NAME
@@ -71,11 +71,11 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "url%d: watchdog timeout"
+.It "url0: watchdog timeout"
 A packet was queued for transmission and a transmit command was
 issued, however the device failed to acknowledge the transmission
 before a timeout expired.
-.It "url%d: no memory for rx list"
+.It "url0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
 .El
 .Sh SEE ALSO
diff --git a/share/man/man4/urtwn.4 b/share/man/man4/urtwn.4
index 093f426bed2..b81f2fd2af6 100644
--- a/share/man/man4/urtwn.4
+++ b/share/man/man4/urtwn.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: urtwn.4,v 1.20 2013/05/16 10:02:59 sthen Exp $
+.\" $OpenBSD: urtwn.4,v 1.21 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2010 Damien Bergamini <damien.bergamini@free.fr>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: May 16 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt URTWN 4
 .Os
 .Sh NAME
@@ -133,11 +133,11 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "urtwn%d: error %d, could not read firmware %s"
+.It "urtwn0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the microcode file from the
 filesystem.
 The file might be missing or corrupted.
-.It "urtwn%d: device timeout"
+.It "urtwn0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
diff --git a/share/man/man4/vlan.4 b/share/man/man4/vlan.4
index e5e8defab92..7942a1a92ca 100644
--- a/share/man/man4/vlan.4
+++ b/share/man/man4/vlan.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: vlan.4,v 1.36 2013/01/17 21:54:18 jmc Exp $
+.\" $OpenBSD: vlan.4,v 1.37 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -27,7 +27,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: January 17 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt VLAN 4
 .Os
 .Sh NAME
@@ -127,7 +127,7 @@ interfaces.)
 .El
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "vlan%d: initialized with non-standard mtu %d (parent %s)"
+.It "vlan0: initialized with non-standard mtu N (parent ...)"
 The IFCAP_VLAN_MTU capability was not set on the parent interface.
 We assume in this event that the parent interface is not capable of handling
 frames larger than its MTU.
diff --git a/share/man/man4/vr.4 b/share/man/man4/vr.4
index ce6fdf02376..2d8adc77346 100644
--- a/share/man/man4/vr.4
+++ b/share/man/man4/vr.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: vr.4,v 1.32 2013/03/30 05:34:53 brad Exp $
+.\"	$OpenBSD: vr.4,v 1.33 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\"	$FreeBSD: vr.4,v 1.3 1999/03/25 00:52:44 wpaul Exp $
 .\"
-.Dd $Mdocdate: March 30 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt VR 4
 .Os
 .Sh NAME
@@ -132,19 +132,19 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "vr%d: couldn't map memory"
+.It "vr0: couldn't map memory"
 A fatal initialization error has occurred.
-.It "vr%d: couldn't map interrupt"
+.It "vr0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "vr%d: watchdog timeout"
+.It "vr0: watchdog timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "vr%d: no memory for rx list"
+.It "vr0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
-.It "vr%d: no memory for tx list"
+.It "vr0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "vr%d: chip is in D3 power state -- setting to D0"
+.It "vr0: chip is in D3 power state -- setting to D0"
 This message applies only to adapters which support power management.
 Some operating systems place the controller in low power
 mode when shutting down, and some PCI BIOSes fail to bring the chip
diff --git a/share/man/man4/wb.4 b/share/man/man4/wb.4
index b558114bf98..731d746e533 100644
--- a/share/man/man4/wb.4
+++ b/share/man/man4/wb.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: wb.4,v 1.18 2008/05/08 03:30:17 brad Exp $
+.\"	$OpenBSD: wb.4,v 1.19 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\"	$FreeBSD: wb.4,v 1.2 1998/12/05 09:31:25 rnordier Exp $
 .\"
-.Dd $Mdocdate: May 8 2008 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt WB 4
 .Os
 .Sh NAME
@@ -108,19 +108,19 @@ For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "wb%d: couldn't map memory"
+.It "wb0: couldn't map memory"
 A fatal initialization error has occurred.
-.It "wb%d: couldn't map interrupt"
+.It "wb0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "wb%d: watchdog timeout"
+.It "wb0: watchdog timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "wb%d: no memory for rx list"
+.It "wb0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
-.It "wb%d: no memory for tx list"
+.It "wb0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "wb%d: chip is in D3 power state -- setting to D0"
+.It "wb0: chip is in D3 power state -- setting to D0"
 This message applies only to adapters which support power management.
 Some operating systems place the controller in low power
 mode when shutting down, and some PCI BIOSes fail to bring the chip
diff --git a/share/man/man4/wi.4tbl b/share/man/man4/wi.4tbl
index 715473310f5..70939e75e28 100644
--- a/share/man/man4/wi.4tbl
+++ b/share/man/man4/wi.4tbl
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: wi.4tbl,v 1.93 2013/02/14 07:40:42 jmc Exp $
+.\"	$OpenBSD: wi.4tbl,v 1.94 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\"	$FreeBSD: wi.4,v 1.3 1999/05/22 16:12:43 wpaul Exp $
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt WI 4
 .Os
 .Sh NAME
@@ -322,13 +322,13 @@ nwkey mywepkey
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "wi%d: init failed"
+.It "wi0: init failed"
 The WaveLAN card failed to come ready after an initialization command
 was issued.
-.It "wi%d: failed to allocate %d bytes on NIC"
+.It "wi0: failed to allocate N bytes on NIC"
 The driver was unable to allocate memory for transmit frames in the
 NIC's on-board RAM.
-.It "wi%d: device timeout"
+.It "wi0: device timeout"
 The WaveLAN failed to generate an interrupt to acknowledge a transmit
 command.
 .El
diff --git a/share/man/man4/wpi.4 b/share/man/man4/wpi.4
index e6e016cf612..ed7e4fdd001 100644
--- a/share/man/man4/wpi.4
+++ b/share/man/man4/wpi.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: wpi.4,v 1.33 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: wpi.4,v 1.34 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 2006, 2007
 .\"	Damien Bergamini <damien.bergamini@free.fr>. All rights reserved.
@@ -25,7 +25,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt WPI 4
 .Os
 .Sh NAME
@@ -115,25 +115,25 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "wpi%d: device timeout"
+.It "wpi0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.
-.It "wpi%d: fatal firmware error"
+.It "wpi0: fatal firmware error"
 For some reason, the firmware crashed.
 The driver will reset the hardware.
 This should not happen.
-.It "wpi%d: Radio transmitter is off"
+.It "wpi0: Radio transmitter is off"
 The radio transmitter is off and thus no packet can go out.
 The driver will reset the hardware.
 Make sure the laptop radio switch is on.
-.It "wpi%d: error %d, could not read firmware %s"
+.It "wpi0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the firmware image from the
 filesystem.
 The file might be missing or corrupted.
-.It "wpi%d: firmware file too short: %d bytes"
+.It "wpi0: firmware file too short: N bytes"
 The firmware image is corrupted and can't be loaded into the adapter.
-.It "wpi%d: could not load firmware"
+.It "wpi0: could not load firmware"
 An attempt to load the firmware into the adapter failed.
 The driver will reset the hardware.
 .El
diff --git a/share/man/man4/xl.4 b/share/man/man4/xl.4
index e74c6359ea9..66514766d2e 100644
--- a/share/man/man4/xl.4
+++ b/share/man/man4/xl.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: xl.4,v 1.44 2013/03/30 05:34:53 brad Exp $
+.\"	$OpenBSD: xl.4,v 1.45 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998
 .\"     Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\"     $FreeBSD: xl.4,v 1.1 1998/08/16 17:19:58 wpaul Exp $
 .\"
-.Dd $Mdocdate: March 30 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt XL 4
 .Os
 .Sh NAME
@@ -144,19 +144,19 @@ For example,
 .Ic ifconfig xl0 media .
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "xl%d: couldn't map memory"
+.It "xl0: couldn't map memory"
 A fatal initialization error has occurred.
-.It "xl%d: couldn't map interrupt"
+.It "xl0: couldn't map interrupt"
 A fatal initialization error has occurred.
-.It "xl%d: device timeout"
+.It "xl0: device timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
-.It "xl%d: no memory for rx list"
+.It "xl0: no memory for rx list"
 The driver failed to allocate an mbuf for the receiver ring.
-.It "xl%d: no memory for tx list"
+.It "xl0: no memory for tx list"
 The driver failed to allocate an mbuf for the transmitter ring when
 allocating a pad buffer or collapsing an mbuf chain into a cluster.
-.It "xl%d: command never completed!"
+.It "xl0: command never completed!"
 Some commands issued to the 3C90x ASIC take time to complete: the
 driver is supposed to wait until the
 .Dq command in progress
@@ -168,7 +168,7 @@ giving up, at which point it issues this message.
 This message may be printed during driver initialization on slower machines.
 If this message appears but the driver continues to function normally, the
 message can probably be ignored.
-.It "xl%d: chip is in D3 power state -- setting to D0"
+.It "xl0: chip is in D3 power state -- setting to D0"
 This message applies only to 3C905B adapters, which support power management.
 Some operating systems place the 3C905B in low power
 mode when shutting down, and some PCI BIOSes fail to bring the chip
@@ -188,7 +188,7 @@ operating system.
 If the system is powered down prior to booting
 .Ox ,
 the card should be configured correctly.
-.It "xl%d: WARNING: no media options bits set in the media options register!"
+.It "xl0: WARNING: no media options bits set in the media options register!"
 This warning may appear when using the driver on some Dell Latitude
 docking stations with built-in 3C905-TX adapters.
 For whatever the reason, the
diff --git a/share/man/man4/zyd.4 b/share/man/man4/zyd.4
index f21284c037e..f0c2db1e38c 100644
--- a/share/man/man4/zyd.4
+++ b/share/man/man4/zyd.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: zyd.4,v 1.37 2013/02/14 07:40:42 jmc Exp $
+.\" $OpenBSD: zyd.4,v 1.38 2013/06/02 20:23:34 tedu Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -30,7 +30,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: February 14 2013 $
+.Dd $Mdocdate: June 2 2013 $
 .Dt ZYD 4
 .Os
 .Sh NAME
@@ -161,22 +161,22 @@ dhcp
 .Ed
 .Sh DIAGNOSTICS
 .Bl -diag
-.It "zyd%d: error %d, could not read firmware %s"
+.It "zyd0: error N, could not read firmware ..."
 For some reason, the driver was unable to read the firmware image from the
 filesystem.
 The file might be missing or corrupted.
-.It "zyd%d: could not load firmware (error=%d)"
+.It "zyd0: could not load firmware (error=N)"
 An error occurred while attempting to upload the firmware to the onboard
 microcontroller unit.
-.It "zyd%d: could not send command (error=%s)"
+.It "zyd0: could not send command (error=...)"
 An attempt to send a command to the firmware failed.
-.It "zyd%d: sorry, radio %s is not supported yet"
+.It "zyd0: sorry, radio ... is not supported yet"
 Support for the specified radio chip is not yet implemented in the driver.
 The device will not attach.
-.It "zyd%d: device version mismatch: 0x%x (only >= 43.30 supported)"
+.It "zyd0: device version mismatch: 0xXXXX (only >= 43.30 supported)"
 Early revisions of the ZD1211 chipset are not supported by this driver.
 The device will not attach.
-.It "zyd%d: device timeout"
+.It "zyd0: device timeout"
 A frame dispatched to the hardware for transmission did not complete in time.
 The driver will reset the hardware.
 This should not happen.