!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

883 Members
Declaratively manage your switching, routing, wireless, tunneling and more. | Don't rely on `networking.*` for interface and routing setup, use systemd-networkd, ifstate or NetworkManager instead. | Set `SYSTEMD_LOG_LEVEL=debug` to debug networking issues with networkd | No bad nft puns, please. | Room recommendations: #sysops:nixos.org251 Servers

Load older messages


SenderMessageTime
13 Jun 2025
@k900:0upti.meK900https://github.com/frank-w/BPI-Router-Linux/commit/1a6d1e12425127e5f9fe3012581d75650034285614:58:21
@emilazy:matrix.orgemilyis the password actually 1234 lol14:58:23
@k900:0upti.meK900 This is the change I think 14:58:21
@emilazy:matrix.orgemilyuh wow federation lag14:58:30
@magic_rb:numtide.com@magic_rb:numtide.comit doesnt matter, they do it based on the port14:58:50
@emilazy:matrix.orgemilyhow the hell did they release this hardware14:59:08
@magic_rb:numtide.com@magic_rb:numtide.comyeah thats the patch14:59:17
@magic_rb:numtide.com@magic_rb:numtide.comexactly as any other hardware, you just dont notice bugs on other things because they've been already worked around14:59:40
@emilazy:matrix.orgemily hmm I see you're using upstream rp-ppoe.so whereas I'm using the pppoe.so fork that ships as part of pppd 14:59:48
@magic_rb:numtide.com@magic_rb:numtide.com50% on Linux's job is workarounds, which is why osdev is so fucking hard14:59:58
@emilazy:matrix.orgemilynot sure if that will be making any difference or which is een better14:59:59
@k900:0upti.meK900
In reply to @emilazy:matrix.org
how the hell did they release this hardware
Honestly for networking hardware that's not even that cursed
15:00:01
@magic_rb:numtide.com@magic_rb:numtide.comokay, im off15:00:16
@magic_rb:numtide.com@magic_rb:numtide.comill try the proper reboot15:00:23
@magic_rb:numtide.com@magic_rb:numtide.com👋15:00:27
@emilazy:matrix.orgemilyif I can ping 8.8.8.8 successfully with 1-byte packets does that mean my kernel isn't affected?15:01:21
@emilazy:matrix.orgemilyhmm15:01:31
@emilazy:matrix.orgemilyI guess those packets would be bigger :)15:01:34
@emilazy:matrix.orgemilybecause of headers15:01:35
@emilazy:matrix.orgemilyI see no evidence of this patch in your tree, so if it went mainline, it must have changed significantly15:02:20
@k900:0upti.meK900 Yeah maybe try it 15:02:32
@magic_rb:numtide.com@magic_rb:numtide.comim back15:02:41
@magic_rb:numtide.com@magic_rb:numtide.comyay15:02:43
@emilazy:matrix.orgemilyalright time to build another kernel15:02:53
@emilazy:matrix.orgemilycan you include this in the next rebase :P15:03:00
@magic_rb:numtide.com@magic_rb:numtide.comno wifi still15:03:10
@magic_rb:numtide.com@magic_rb:numtide.comffs15:03:13
@magic_rb:numtide.com@magic_rb:numtide.com
[   11.721941] mt7996e 0000:01:00.0: vgaarb: pci_notify
[   11.721996] mt7996e 0000:01:00.0: assign IRQ: got 103
[   11.722014] mt7996e 0000:01:00.0: enabling device (0000 -> 0002)
[   11.722063] mt7996e 0000:01:00.0: enabling bus mastering
[   11.814596] mt7996e 0000:01:00.0: Direct firmware load for mediatek/mt7996/mt7996_rom_patch_233.bin failed with error -2
[   11.814617] mt7996e 0000:01:00.0: Falling back to sysfs fallback for: mediatek/mt7996/mt7996_rom_patch_233.bin
[   74.444141] mt7996e 0000:01:00.0: probe with driver mt7996e failed with error -110
[   74.451725] mt7996e 0000:01:00.0: vgaarb: pci_notify
15:03:29
@k900:0upti.meK900
In reply to @emilazy:matrix.org
can you include this in the next rebase :P
If you confirm it helps, sure
15:04:24
@emilazy:matrix.orgemilyyeah working on it15:04:34

Show newer messages


Back to Room ListRoom Version: 6