igb_phy_forc...d_duplex_igp(9)

📦 version 7.3.1, in nixpkgs unstable

💅 igb_phy_forc...d_duplex_igp(9) 💅

okay so this is from the Kernel API Manual bestie, and the vibes are immaculate but the name is LONG so they had to squish it. let's get into it 🫶

✨ NAME ✨

igb_phy_force_speed_duplex_igp — it forces speed/duplex for the igp PHY. that's the whole thing. it's giving "no thoughts, just force" and honestly? iconic 💅

🌸 SYNOPSIS 🌸

s32 igb_phy_force_speed_duplex_igp (struct e1000_hw *hw );

like yes we return an s32 and yes she takes exactly one argument, so clean, so minimal, main character energy fr fr ✨

🎀 ARGUMENTS 🎀

  • hw — pointer to the HW structure. that's it. that's the whole argument list. she walks in with her struct e1000_hw * and gets to work 💖

🦋 DESCRIPTION 🦋

so what she actually DOES is — she calls the PHY setup function to force speed and duplex. like, forcing it. not asking nicely. no negotiations. periodt 🔥

then she clears the auto-crossover to force MDI manually, because sometimes you just gotta take the wheel and pick the thing yourself, y'know? no cap 🙈

after that she waits for link, and returns successful if link up is successful. otherwise? it's -E1000_ERR_PHY which is literally (-2). so if you see a -2 come back, that's your girl saying "nope, no link" 😭💀

lowkey the ordering matters here — the wait comes after the forcing, and the error only shows up when link-up didn't work. don't @ me, that's just what the page says 🧚

💜 SEE ALSO 💜

she runs with a whole squad, okay, like a full group chat of igb functions — here's everyone invited bestie:

Kernel file ./drivers/net/ethernet/intel/igb/e1000_phy.c

okay that's the whole entire page and yes i read all of them so you don't have to 💖

she lives at ./drivers/net/ethernet/intel/igb, dated October 2026, and this little manual moment was brought to you by the igb_phy_forc...d_duplex_igp(9) girlies. slay, stay connected, and may your link always come up 🎀✨🦋

📦 where this page comes from