BFE(4)
π BFE(4) β the Broadcom BCM4401 Ethernet tea π
okay so bestie, welcome to BFE(4), from the Kernel Interfaces Manual. yes we're reading a manpage together, it's giving study date energy, grab a snack π
β¨ NAME β¨
bfe β the Broadcom BCM4401 Ethernet Device Driver. that's it, that's the girl π
π SYNOPSIS π
so like, there's two ways to get her in the building. option one: compile the driver straight into your kernel. put these lines in your kernel configuration file:
device miibus
device bfe
or, alternatively, if you wanna be lazy in a cute way (no judgment, it's literally me), load the driver as a module at boot time instead. drop this line in loader.conf(5):
if_bfe_load="YES"
boom. loaded. β¨
π¦ DESCRIPTION π¦
okay so the bfe driver is out here providing support for Broadcom BCM4401 based Fast Ethernet adapters. that's her whole job and she's doing it π«Ά
now, the bfe driver supports the following media types:
autoselectβ turns on autoselection of the media type and options. let her pick, she knows what she's doing π10baseT/UTPβ sets 10Mbps operation. slow era, retro vibes π100baseTXβ sets 100Mbps (Fast Ethernet) operation. the fast one. main character energy π₯
and she also supports the following media options:
full-duplexβ sets full duplex operation β¨
for further info on configuring this device, go peek at ifconfig(8). iykyk π
π DIAGNOSTICS π
these are the messages she might hit you with. read them, love them, fear them a little:
bfe%d: couldn't map memoryβ a fatal initialization error has occurred π like, truly fatal. she's not okay.bfe%d: couldn't map interruptβ also a fatal initialization error has occurred. two different ways to be not okay, iconic honestly πbfe%d: failed to allocate DMA resourcesβ there are not enough mbufs available for allocation. she's hungry and the fridge is empty πbfe%d: watchdog timeout -- resettingβ the device has stopped responding to the network, or there is a problem with the network connection (cable). check the cable bestie, it's always the cable π
not me getting emotional over a watchdog timeout. but fr, if you see any of these, something is actually wrong. don't just vibe through it.
π SEE ALSO π
go read these too, they're all part of the friend group:
altq(4), arp(4), miibus(4), netintro(4), ng_ether(4), ifconfig(8)
π HISTORY π
the bfe device driver first appeared in FreeBSD 5.1. vintage, but make it fast β¨
π§ AUTHORS π§
the bfe device driver was written by Stuart Walsh and Duncan Barclay. and this manual page was written by Stuart Walsh. kings, honestly, thank you for your service π«Ά
and that's the whole page bestie!! this one's from the Debian crew, dated July 16, 2005 (yes she's an elder, respect her), filed under BFE(4). mwah, go configure something cute π π
π¦ 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) 2003 Stuart Walsh
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms