| 13 Jun 2025 |
 @magic_rb:numtide.com | will open a bug report in ifstate | 14:41:30 |
 K900 | Yeah that depends on the MAC I think | 14:46:19 |
| @magic_rb:numtide.com | okay so ifstate bug then | 14:47:20 |
| @magic_rb:numtide.com | on a related note, my wifi broke | 14:47:25 |
| @magic_rb:numtide.com | [ 11.874819] mt7996e 0000:01:00.0: vgaarb: pci_notify
[ 11.874869] mt7996e 0000:01:00.0: assign IRQ: got 120
[ 11.874886] mt7996e 0000:01:00.0: enabling device (0000 -> 0002)
[ 11.874930] mt7996e 0000:01:00.0: enabling bus mastering
[ 11.952294] mtk-pcie-gen3 11300000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11300c00 data 1
[ 11.973753] mt7996e 0000:01:00.0: Direct firmware load for mediatek/mt7996/mt7996_rom_patch_233.bin failed with error -2
[ 11.973773] mt7996e 0000:01:00.0: Falling back to sysfs fallback for: mediatek/mt7996/mt7996_rom_patch_233.bin
| 14:47:43 |
| @magic_rb:numtide.com | main@hela:~$ ls /run/current-system/firmware/mediatek/mt7996/mt7996_rom_patch.bin.zst
/run/current-system/firmware/mediatek/mt7996/mt7996_rom_patch.bin.zst
```3
| 14:47:58 |
| @magic_rb:numtide.com | * main@hela:~$ ls /run/current-system/firmware/mediatek/mt7996/mt7996_rom_patch.bin.zst
/run/current-system/firmware/mediatek/mt7996/mt7996_rom_patch.bin.zst
| 14:48:01 |
| @magic_rb:numtide.com | * main@hela:~$ ls /run/current-system/firmware/mediatek/mt7996/mt7996_rom_patch_233.bin.zst
/run/current-system/firmware/mediatek/mt7996/mt7996_rom_patch_233.bin.zst
| 14:48:21 |
| K900 | Probably need to reboot it | 14:50:22 |
| K900 | Sometimes it gets stuck in a weird state after a soft reboot | 14:50:45 |
| K900 | Cutting the power helps | 14:50:45 |
| @magic_rb:numtide.com | ah yeah i have been doing a lot of soft reboots | 14:51:07 |
| @magic_rb:numtide.com | will try cutting | 14:51:11 |
| @magic_rb:numtide.com | also | 14:51:14 |
 emily | the more I investigate this PPP stuff the less sense it makes | 14:51:32 |
| @magic_rb:numtide.com | https://gitlab.com/K900/nix/-/blob/master/shared/platform/bpi-r4.nix#L70 what does this do? | 14:51:39 |
| @magic_rb:numtide.com | why is it there, i copied it but i have no clue why its there | 14:51:47 |
| emily | OpenWrt:
Fri Jun 13 14:22:09 2025 daemon.debug pppd[3465]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xa3c5f758>]
Fri Jun 13 14:22:09 2025 daemon.debug pppd[3465]: rcvd [LCP ConfReq id=0x49 <auth chap MD5> <magic 0x45a13285>]
Fri Jun 13 14:22:09 2025 daemon.debug pppd[3465]: sent [LCP ConfAck id=0x49 <auth chap MD5> <magic 0x45a13285>]
Fri Jun 13 14:22:09 2025 daemon.debug pppd[3465]: rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0xa3c5f758>]
Fri Jun 13 14:22:09 2025 daemon.debug pppd[3465]: sent [LCP EchoReq id=0x0 magic=0xa3c5f758]
NixOS with the exact same MTU/MRU configuration:
Jun 13 14:47:09 bpi-r4 pppd[1784]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x549f006a>]
Jun 13 14:47:12 bpi-r4 pppd[1784]: rcvd [LCP ConfReq id=0x80 <auth chap MD5> <magic 0x40db49af>]
Jun 13 14:47:12 bpi-r4 pppd[1784]: sent [LCP ConfAck id=0x80 <auth chap MD5> <magic 0x40db49af>]
Jun 13 14:47:12 bpi-r4 pppd[1784]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x549f006a>]
Jun 13 14:47:15 bpi-r4 pppd[1784]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x549f006a>]
Jun 13 14:47:16 bpi-r4 pppd[1784]: rcvd [LCP ConfReq id=0x81 <auth chap MD5> <magic 0x40db49af>]
Jun 13 14:47:16 bpi-r4 pppd[1784]: sent [LCP ConfAck id=0x81 <auth chap MD5> <magic 0x40db49af>]
Jun 13 14:47:18 bpi-r4 pppd[1784]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x549f006a>]
[gets stuck forever]
| 14:52:04 |
| K900 | In reply to @magic_rb:numtide.com
https://gitlab.com/K900/nix/-/blob/master/shared/platform/bpi-r4.nix#L70 what does this do? What, the runCommand? | 14:52:19 |
| emily | how come NixOS sends the exact same requests as OpenWrt, but the ISP acks it when OpenWrt does it and ignores NixOS??? | 14:52:23 |
| @magic_rb:numtide.com | yeah | 14:52:33 |
| K900 | Saves me from uploading 700MB of linux-firmware to the thing every other week is what | 14:52:34 |
| @magic_rb:numtide.com | oh so you build a firmware which contains only firmware you actually need? | 14:52:55 |
| K900 | Less relevant now that it's on a non-shit drive | 14:53:02 |
| @magic_rb:numtide.com | so i shouldnt need that, got it | 14:53:13 |
| K900 | But copying that to the eMMC fucking suuuuuuuucked | 14:53:22 |
| K900 | In reply to @magic_rb:numtide.com
oh so you build a firmware which contains only firmware you actually need? Well, "build", as in I just yoink the one directory I care about from nixpkgs linux-firmware | 14:53:43 |
| @magic_rb:numtide.com | last time i had that, it was due to the hardware of the bpi not being able to handle sub 40 byte packets properly, but that fixed made it into franks tree (courtesy of yours truly) and then i assume into k900's tree and maybe mainline? | 14:54:03 |
| @magic_rb:numtide.com | yeah i just was confused what youre doing there, because it seemed like you were doing exactly what you were doing, but i failed to consider the why | 14:54:23 |
| @magic_rb:numtide.com | now it makes sense :) | 14:54:27 |
