STE(4)
π STE(4) β the Sundance Technologies ST201 Fast Ethernet device driver π
okay bestie, sit down, hydrate, and let me tell you about ste(4) β a little kernel driver from the Kernel Interfaces Manual section of your fave manual pages. she's niche, she's vintage, she's iconic, and she makes old NICs go brrr. π¦
β¨ NAME β¨
ste β the Sundance Technologies ST201 Fast Ethernet device driver π
β¨ SYNOPSIS β¨
so like, you wanna bake this driver into the kernel? sure babe, drop these lines into your kernel configuration file:
device miibus
device ste
orrrr, if you'd rather load it as a module at boot time (which, honestly, slay), put this one line in loader.conf(5):
if_ste_load="YES"
pick your fighter, both are valid. π«Ά
β¨ DESCRIPTION β¨
the ste driver is out here providing support for PCI Ethernet adapters and embedded controllers based on the Sundance Technologies ST201 PCI Fast Ethernet controller chip. it's giving retro-tech main character energy fr fr.
the Sundance ST201 uses bus master DMA and was literally designed to be a 3Com Etherlink XL workalike. same DMA descriptor structure, very similar in operation β but bestie, its register layout is different. so close, yet so not the same. π
the ST201 has a 64-bit multicast hash filter and a single perfect filter entry for the station address. she supports both 10 and 100Mbps speeds in either full or half duplex using an MII transceiver. versatile queen. π
the ste driver supports the following media types:
autoselectβ turns on autoselection of the media type and options. and here's the tea: you can manually override the autoselected mode by adding media options to the/etc/rc.conffile. no cap. β¨10baseT/UTPβ sets 10Mbps operation. themediaoptoption can also be used to select eitherfull-duplexorhalf-duplexmodes.100baseTXβ sets 100Mbps (Fast Ethernet) operation. themediaoptoption can also be used to select eitherfull-duplexorhalf-duplexmodes.
and the following media options:
full-duplexβ force full duplex operation. πͺhalf-duplexβ force half duplex operation. π
for more info on configuring this device, go see ifconfig(8). she has the details, iykyk.
β¨ HARDWARE β¨
the ste driver supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded controllers, including these icons:
- D-Link DFE-530TXS
- D-Link DFE-550TX
- D-Link DFE-580TX
D-Link really said "we're gonna make three of them" and honestly? respect. π
β¨ SYSCTL VARIABLES β¨
the following variables are available as both sysctl(8) variables and loader(8) tunables:
dev.ste.%d.int_rx_modβ maximum number of time to delay RX interrupts. the valid range is 0 to 209712 in units of 1us, and the default is 150 (150us). the value 0 effectively disables the RX interrupt moderation. heads up: the resolution of the timer is about 3.2us, so finer tuning than 3.2us wouldn't be available. and the best part? the interface does not need to be brought down and up again before a change takes effect. we love a live-edit queen. π
β¨ DIAGNOSTICS β¨
here's the drama, message by message:
ste%d: couldn't map ports/memoryβ a fatal initialization error has occurred. πste%d: couldn't map interruptβ a fatal initialization error has occurred. π (yes, same energy, different mapping)ste%d: watchdog timeoutβ the device has stopped responding to the network, or there is a problem with the network connection (cable). check ur cable bestie.ste%d: no memory for rx listβ the driver failed to allocate an mbuf for the receiver ring.ste%d: 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.ste%d: chip is in D3 power state -- setting to D0β okay so 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 out of this state before configuring it. the controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. the driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. if you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform a second warm boot to have the device properly configured. π
ngl, note that this condition only occurs when warm booting from another operating system. if you power down your system prior to booting FreeBSD, the card should be configured correctly. so like... cold boot and chill. πΈ
β¨ SEE ALSO β¨
altq(4), arp(4), miibus(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8)
also: Sundance ST201 data sheet, http://www.sundanceti.com. π
β¨ HISTORY β¨
the ste device driver first appeared in FreeBSD 3.0. a true OG. π
β¨ AUTHORS β¨
the ste driver was written by Bill Paul <wpaul@ee.columbia.edu>. thank you king, we owe you everything. π«Ά
and that's the whole page, bestie!! π this lil Debian edition of STE(4) is dated December 24, 2009 β a certified vintage, a holiday-season drop, an absolute classic. go forth and configure ur NIC, you've got this. periodt. π
β¨
π¦ where this page comes from
- debian bookworm: freebsd-manpages 12.2-1 Β· BSD-2-Clause-FreeBSD AND BSD-4-Clause
- debian trixie: freebsd-manpages 12.2-2 Β· BSD-2-Clause-FreeBSD AND BSD-4-Clause
- ubuntu jammy: freebsd-manpages 12.2-1 Β· BSD-2-Clause-FreeBSD AND BSD-4-Clause
- ubuntu noble: freebsd-manpages 12.2-1 Β· BSD-2-Clause-FreeBSD AND BSD-4-Clause
- ubuntu questing: freebsd-manpages 12.2-2
- ubuntu resolute: freebsd-manpages 12.2-2build1 Β· BSD-2-Clause-FreeBSD AND BSD-4-Clause
- ubuntu stonking: freebsd-manpages 12.2-2build1 Β· BSD-2-Clause-FreeBSD AND BSD-4-Clause
- Copyright (c) 1997, 1998, 1999 Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms