Framework 13 AMD BIOS update [Solved]

[DeM]

Hello everyone,

I have a Framework 13, AMD Ryzen 7 laptop, running the latest MX KDE.

The BIOS needs to be updated, and after following the instructions on Frameworks website, I am wondering if the process didn't work because MX doesn't use systemd? The USB with the BIOS update files wasn't visible upon an f12 boot.

I haven't been able to find anything that specifically says either way, as this is still a relatively recent update. Framework only officially support Fedora and Ubuntu just now, so I thought I'd ask here first. I was wondering if switching over to systemd briefly to do the update might work, and then switching back to sysvinit. Any thoughts would be greatly appreciated. Thanks

Best wishes

[j2mcgreg]

From the Framework site:
https://knowledgebase.frame.work/en_us/ ... -BkQBvKWr3

Download: No New BIOS at this time. The Factory-Installed BIOS (3.03) is the latest version

Extract contents of zip folder to a FAT32 formatted USB drive.
Disable secure boot in BIOS (tap F2 while booting, navigate to Security -> Secure Boot, and set Enforce Secure Boot to Disabled. Press F10 to save and exit.)
With power plugged in, boot your system while tapping F12, and select the USB drive. NOTE: The F12 setup menu will only show devices that have a valid EFI boot partitions.
Let startup.nsh run automatically.
System will reboot, and you can unplug the USB drive.

You can see that SystemD / OS is immaterial. Also once you post your Quick System Info (QSI), we will have more information to help you. QSI is located in MX Tools. Run it, click Copy for Forum at the bottom, and just paste it here in your thread.

[Stevo]

Since it's easy and safe to boot with systemd on installed MX, you could try the experiment yourself.

What UEFI does your QSI show the machine using?

[DeM]

Hi, thanks for your help. Here is my QSI:

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
    resume=UUID=<filter> resume_offset=5320704
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.2_KDE_x64 Libretto
    October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: Framework product: Laptop 13 (AMD Ryzen 7040Series) v: A7
    serial: <superuser required>
  Mobo: Framework model: FRANMDCP07 v: A7 serial: <superuser required> UEFI: INSYDE v: 03.03
    date: 10/17/2023
Battery:
  ID-1: BAT1 charge: 48.1 Wh (77.8%) condition: 61.8/60.7 Wh (101.9%) volts: 16.0 min: 15.5
    model: N/A type: Unknown serial: <filter> status: discharging cycles: 29
CPU:
  Info: model: AMD Ryzen 7 7840U w/ Radeon 780M Graphics bits: 64 type: MT MCP arch: Zen 4 gen: 5
    level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x74 (116)
    stepping: 1 microcode: 0xA704103
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1816 high: 5065 min/max: 1600/6677 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1600 2: 1600 3: 1600 4: 1600 5: 1600 6: 1600
    7: 1600 8: 5065 9: 1600 10: 1600 11: 1600 12: 1600 13: 1600 14: 1600 15: 1600 16: 1600
    bogomips: 105405
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: safe RET, no microcode
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Phoenix1 driver: amdgpu v: kernel arch: RDNA-3 code: Phoenix process: TSMC n4 (4nm)
    built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3,
    DP-4, DP-5, DP-6, DP-7, DP-8 bus-ID: c1:00.0 chip-ID: 1002:15bf class-ID: 0300 temp: 28.0 C
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 2256x1504 s-dpi: 96 s-size: 596x397mm (23.46x15.63") s-diag: 716mm (28.19")
  Monitor-1: eDP-1 mapped: eDP model: BOE Display 0x0bca built: 2022 res: 2256x1504 hz: 60
    dpi: 201 gamma: 1.2 size: 285x190mm (11.22x7.48") diag: 343mm (13.5") ratio: 3:2 modes:
    max: 2256x1504 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Graphics (gfx1103_r1 LLVM 15.0.6
    DRM 3.49 6.1.0-13-amd64) direct-render: Yes
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: c1:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A alternate: snd_pci_acp3x,
    snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: c1:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: c1:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e v: kernel
    modules: wl pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 14c3:0616 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  IF-ID-1: pvpnksintrf1 state: unknown speed: N/A duplex: N/A mac: <filter>
  IF-ID-2: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
  Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-5:5
    chip-ID: 0e8d:e616 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2305 hci-v: 5.2 rev: 3012
  Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 1.82 TiB used: 404.28 GiB (21.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD BLACK SN850X 2000GB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 620331WD temp: 20.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 204.78 GiB size: 200.51 GiB (97.91%) used: 52.41 GiB (26.1%) fs: ext4
    dev: /dev/dm-0 maj-min: 253:0 mapped: luks-<filter>
  ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 106.4 MiB (10.9%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-3: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-4: /home raw-size: 1.62 TiB size: 1.59 TiB (98.37%) used: 351.76 GiB (21.6%) fs: ext4
    dev: /dev/dm-1 maj-min: 253:1 mapped: luks-<filter>
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 36.54 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 47.2 C mobo: N/A gpu: amdgpu temp: 27.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2608 pm: dpkg pkgs: 2589 libs: 1405 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 19
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net bookworm main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
    2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
    1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
Info:
  Processes: 406 Uptime: 3h 4m wakeups: 347 Memory: 30.54 GiB used: 3.06 GiB (10.0%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

The link you posted was for the Intel 13th gen chip. Whereas I have the Ryzen 7 chip, and there is an update for the BIOS to version 3.05:
https://knowledgebase.frame.work/en_us/ ... -r1rXGVL16

Thanks

[j2mcgreg]

They were the only bios update instructions I could find, but the methodology should apply to either CPU. A computer's bios is independent of the OS, and the utility to update the bios would have been created by its author (not the computer manufacturer). You haven't said why you need to update the bios. Are there fixes in the latest version that may help you with a current problem?

[DeM]

That's what I thought, and the instructions are basically the same. But, when I press f12 after booting, the USB that I extracted the contents of the zip file to isn't available.

There are various security fixes in the update, as the hardware is all still quite new.

Thanks

[DeM]

So, the fix turned out to be pretty easy. When I extracted the files to the USB, a folder was created on the USB with the files in it. It turns out that was why I couldn't see the USB on the f12 boot. Taking the files out of the folder fixed the issue. Everything is updated now.

Thanks

[j2mcgreg]

Please mark this topic as Solved by clicking on the check mark beside the post that contains the solution.