u/enterrawolfe

Hey all!

I started yesterday with 11k+ purchasing power. I made a larger furniture purchase for about 9k. Everything went through just fine in store. Later last night I got a rejection email. Plan is showing up in the app as pending. Is this an issue that I need to handle?

UPDATE: Okay… so I talked to Affirm. They’ve assured me that everything is fine and I don’t need to take any action. And yet… why do I doubt them?

I’ll update again when/if there is an issue. Or… if by some miracle it’s actually fine.

I'm grateful to see more VRAM in the 5070xt, but I'd much rather see an AMD product with additional VRAM. While nvidia has improved in their support of Linux, AMD has long been a good steward of the open source community and I trust them more in that respect.

Is there any rumors of a new release of mobile AMD GPU products for Framework 16?

When this occurs, its randomly. Sometimes it doesn't happen for weeks. When it does happen, turning the connection off and on again doesn't help. Setting a static IP, subnet & DNS doesn't help. Restarting the network service doesn't either.

Systemctl status shows "<warn>  [1777302716.3795] device (p2p-dev-wlp5s0): error setting IPv4 forwarding to '0': Success"

··• sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
   Drop-In: /usr/lib/systemd/system/service.d
            └─10-timeout-abort.conf
    Active: active (running) since Mon 2026-04-27 11:11:56 EDT; 10s ago
Invocation: 5db2e8805c0d4bf9bbfd1a46045d5a22
      Docs: man:NetworkManager(8)
  Main PID: 245264 (NetworkManager)
     Tasks: 5 (limit: 115306)
    Memory: 4.2M (peak: 6.1M)
       CPU: 39ms
    CGroup: /system.slice/NetworkManager.service
            └─245264 /usr/bin/NetworkManager --no-daemon

Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3757] device (enp14s0): Activation: successful, device activated.
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3758] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3793] device (wlp5s0): supplicant interface state: internal-starting -> disconnected
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3794] Wi-Fi P2P device controlled by interface wlp5s0 created
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3794] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5)
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3795] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <warn>  [1777302716.3795] device (p2p-dev-wlp5s0): error setting IPv4 forwarding to '0': Success
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3796] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3797] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Apr 27 11:11:56 Destroyer NetworkManager[245264]: <info>  [1777302716.3948] agent-manager: agent[1a14a2b63e7bbaee,:1.63/org.kde.plasma.networkmanagement/1000]: agent registered

IP link show shows the connection is up

··• ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
   link/ether 3a:51:49:cf:3d:84 brd ff:ff:ff:ff:ff:ff permaddr 10:5f:ad:d8:07:7a
   altname wlx105fadd8077a
3: enp15s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
   link/ether 60:cf:84:8a:63:9f brd ff:ff:ff:ff:ff:ff
   altname enx60cf848a639f
4: enp14s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
   link/ether 60:cf:84:ae:4f:ab brd ff:ff:ff:ff:ff:ff
   altname enx60cf84ae4fab

Restarting the computer is the only way I've found to resolve. Any ideas as to where I go from here?