Standalone mode means that you use board without the battery and panel.
1 Like
So, since upgrading to 3.22, I consistently canāt get any video (even on the internal display) after the GRUB screen and disk-decryption display when booting with one of my Thunderbolt docks connected unless I disconnect the battery in the BIOS first. I had various weird video problems before, but this is different: I consistently do get video (to all connected displays) until the OS is up, and consistently do not get video once X starts. (And BTW, this is under X, not Wayland ā but I canāt switch to a text VT and get video that way, either.)
Holding down the power button until the laptop reboots, going into UEFI settings and disconnecting the battery, unplugging the dock, and plugging it back in consistently fixes things, but thatās pretty tedious. Since I almost always use the laptop docked, Iām considering just removing the battery as a workaround, but at that point itās not useful if an emergency comes up while Iām on the train or otherwise away from a desk.
(And I suppose I could sleep it instead of shutting all the way down, but I often donāt know how long itās going to be before I use it again, and a couple times in the past Iāve run the battery all the way down that way. I presume hibernating to disk would just make my issues worse.)
BTW, this is with a Cable Matters USB-C/Thunderbolt 3 docking station. (And booting without the docking station plugged in works, and gives me video on the internal display, without problems.)
Framework, how about a status report on 11th Gen BIOS 3.22? Iām not sure if itās ready for release or not.
Updated from BIOS 3.20 to 3.22 with no issues thus far, running Windows 11 Pro.
2 Likes
Upgraded from 3.20 to 3.22 using Framework_Laptop_13_11th_Gen_Intel_Core_BIOS_3.22.zip (sha256 6a37e[...]c8e74) on a laptop that had two EFI entries: an old ubuntu/grub entry (with nothing behind it, as the ubuntu install is long deleted) and a current nixos/systemd-boot entry.
The BIOS update applied cleanly but on reboot only the ubuntu/grub EFI target was present (the nixos/systemd-boot one was gone). I ended up having to boot a NixOS installation USB drive, drop to a terminal, decrypt+mount partitions, sudo nixos-enter, and re-run nixos-rebuild switch --install-bootloader to recover a working /boot/EFI/nixos entry.
Reporting this in case future firmware updates can be made more robust to losing EFI entries like this, and in case the above description is helpful for others to unwedge their systems.
Could anyone whoās staying current on 11th gen BIOSes comment on what the sleep situationās like on Linux? Iām still on 3.19 since, last I heard, that was the only way to have reliably functioning sleep that consumed on the order of 1% of battery per hour.
Iām getting 0.81W with S0 suspend on BIOS 3.20, so thatās more like 1.5% per hour (from a 55Wh battery). I think I got the same on 3.19.
Iām using S3 sleep, so thatās good to know. Thanks. Iād be happier with around 0.5% per hour overnight, but that seems way out of reach right now. In the past when Iāve tried S0, itās been around what youāre saying, as far as I remember, but occasionally a much higher wattage was consumed, like 3W or something.
I updated to BIOS 3.22 and deep sleep on Linux still seems to work for me (power light goes off, resumes ok).
Iāve seen people saying their deep sleep was broken already by 3.19. Maybe some distros do it differently, or something?
2 Likes
Same here, with the setup Iāve posted before and the latest Fedora 42 kernel (6.15.3 IIRC?).
1 Like
Same here. Emboldened by you two, I tried installing 3.22, and deep sleep still works. I can get by on around .5 watts/hour overnight. Whaddya know.
1 Like
May I ask the OS/Distro you use?
1 Like
Iām currently on Fedora 42, just upgraded to an AMD board, but I was on an Intel i7-1165G7 until yesterday.
The Intel board consistently used 0.5 to 0.6 watts per hour in S3 / deep sleep overnight, about 1% per hour. The only relevant kernel parameter I set was mem_sleep_default=deep.
I do run all four ports as USB-C, entirely for battery life reasons.
1 Like
Thanks for the info.
I have nixos on my 11th gen intel machine. I stick to 3.19 and experiment with S0/s2idle. Sometimes (usually when I plug my laptop), it warms quite a lot during suspend. I wonder if 3.22 will resolve this issue. Currently, I always have the option to switch back to S3/deep. I am reluctant to update as I worry I may lose S3 option all together.
Edit: fixed some typos
I have just updated to 3.22 and both s2idle and deep sleep modes are still available.
āÆ cat /sys/power/mem_sleep
[s2idle] deep
2 Likes
Just wanted to report that since the 3.22 BIOS upgrade my 11th-gen i7 Framework Laptop 13 with Xubuntu 24.04 has been effectively unusable for my purposes.
I almost always use my Framework with a Thunderbolt dock and two monitors, both at work and at home. (Using the laptop standalone almost always works, although sometimes the USB ports donāt work until I disconnect the battery.)
I was excited about the suggestion to disconnect the battery, since that let it boot with working video to the internal and external displays once after the first time I tried it, but since then itās clear that thatās not at all consistent. Iāve tried lots of things, and since the laptop boots more-or-less usably about one out of every four or five boots, itās really hard to tell if anything is making a difference, but Iām pretty sure at this point itās just random, and sometimes things work on a reboot but usually they donāt. (I think there may be times when disconnecting the battery is required, but there are also times when it doesnāt seem to have been sufficient, even when leaving the machine powered off with the battery disconnected for ~5min.)
I have not yet tried downgrading; fwupdmgr downgrade tells me No downgrades for System Firmware: No releases found, but I plan on trying to downgrade from Windows. I thought it might be a good idea to report here first, though.
Windows 10 seems to work more-or-less reliably, so clearly thereās something the OS can do to reset the Thunderbolt controller or the BIOSās understanding of peripheral state, but I upgraded to 24.04 before upgrading the BIOS, and was consistently able to get video through the dock once the OS was up (although not to get BIOS/GRUB video through the dock) until the 3.22 upgrade.
Here are some of the typical sequences:
- Boot with dock connected: I see BIOS and GRUB video on the external (and internal) monitors. When the kernel starts, there is no video to any display (including the laptopās internal display). (The keyboard backlight and power light are on.) Usually I can wait indefinitely and no video appears, but sometimes after ~10min or so video comes on and I get kernel errors mentioning BIOS bugs. Iāll attach some screenshots.
- Boot with dock connected: Everything works fine. I see BIOS and GRUB video on the external (and internal, if the laptop is open) monitors, Iām prompted to decrypt the boot drive, and I end up with a graphical login screen and can log in and all displays are seen. This is the rarest case, but it does happen from time to time.
- Boot with dock connected: I see no video on the external monitors. The laptop comes up as if the dock was not there (except that usually, not always, I can use USB HID devices connected through the dock). When the OS comes up, Linux thinks the only monitor connected is the laptopās internal monitor. The light on the dock indicates it thinks the laptop is connected.
- Boot with dock disconnected, unlock boot drive, and log in, then connect dock: Often, the internal monitor goes blank when I connect the dock (and I havenāt found a way to get it back other than leaning on the power button to force the laptop to shut down).
- Boot with dock disconnected, unlock boot drive, and log in, then connect dock: Sometimes, the laptop then sees the external monitors (and the internal one doesnāt go black). This is my most common more-or-less successful case, and happens a lot more often than everything working when I boot the laptop connected to the dock from the start, but less than half the time when I connect the dock after the OS is up.
- Boot with no dock connected, never connect dock: This generally gives me working video on the internal display, and at least some of the time the USB ports work
- Boot with no dock connected, never connect dock: Sometimes, the USB ports donāt work (confirmed by plugging things into them, like a keyboard or mouse, and noting that not only donāt they work, but
dmesgshows no record of a device being attached).
As I mentioned back in May, this is with a Cable Matters USB-C/Thunderbolt 3 docking station. (Several identical ones, actually. And at one point I thought a flaky dock might be the problem and bought a new one, but that didnāt help.)
I have lightly tested this with a borrowed Lenovo Thunderbolt docking station, and seen similar results, but I didnāt have access to that for very long.
And as mentioned Windows seems to work consistently, so thereās clearly something the OS can do about this. I havenāt had time to try switching to Debian or newer-than-24.04 Xubuntu, or booting from a Fedora USB drive or something.
Iāve attached two (camera-taken) screenshots of kernel errors.
The shorter one, that ends with ā[ā¦] ACPI Error: Aborting method \_SB.EITM._OSC due to previous error [ā¦]ā shows up almost all the time (but if Iām remembering correctly, not 100% of the time), regardless of whether a dock is attached or not, and regardless of whether video is going to work or not. (If video is not going to work, that pops up on the screen for about a second before all displays go blank, including the internal display. If video is going to work, I then get the login screen.)
The longer one is what sometimes shows up after 10-15min when video is not working normally. (Most of the time the displays, including the internal one, will all just stay blank forever.) When this happens the first batch of kernel messages (with ā[drm]ā in them) are all on the screen when it eventually turns on, but the following batch of ā[FAILED]ā messages, with a few kernel messages interspersed with them then show up very slowly. I waited for a while after the bottommost (cut off) line appeared and nothing else appeared to show up (the display never scrolled). In that screenshot note the weird video artifacts, although those donāt usually show up.
Anyway, given the complicated intersection between dock, OS, and BIOS, I feel like Iām probably on my own on this, but I wanted to report what I was experiencing in case it was useful for anybody else. Framework folks, I have a spare one of these docks if youād like me to send it to you to experiment with.
(And if anybody has instructions for downgrading live from within Linux rather than rebooting into Windows or from a USB stick that could be handy, although Iām sure I can downgrade in Windows.)
Thanks,
Jay
So I thought after an upgrade to Xubuntu 25.04 that things were better. They do seem improved. The first three times I booted the system connected to the dock (or attached it to the dock after it was up) it worked, albeit with a long (~2min) pause followed by a different āACPI BIOS Error (bug)ā from the kernel before the X login screen appeared (attached). But the fourth time I again got no video (either through the dock or on the internal display). And that time I waited about 15min; still nothing.
So things might be somewhat improved (three out of four boots succeeded, which is much better than I was averaging before), but since this has all been pretty unpredictable I canāt be sure. (Since I need the laptop for work I havenāt been able to do too many test reboots once I get it up and running.)
For reference:
Kernel messages (photo also attached):
[ 54.239382] ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 55.034608] ACPI BIOS Error (bug): Could not resolve symbol [_TZ.ETMD], AE_NOT_FOUND (20240827/psargs-332)
[ 55.034722] ACPI Error: Aborting method _SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[ 82.453066] ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
$ cat /proc/version
Linux version 6.14.0-29-generic (buildd@lcy02-amd64-033) (x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-19ubuntu2) 14.2.0, GNU ld (GNU Binutils for Ubuntu) 2.44) #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 7 18:32:38 UTC 2025
$ lsmod
Module Size Used by
snd_usb_audio 561152 1
snd_usbmidi_lib 57344 1 snd_usb_audio
snd_ump 45056 1 snd_usb_audio
usbhid 77824 0
r8153_ecm 12288 0
cdc_ether 24576 1 r8153_ecm
usbnet 61440 2 r8153_ecm,cdc_ether
uas 32768 0
r8152 143360 1 r8153_ecm
usb_storage 86016 1 uas
mii 20480 2 usbnet,r8152
snd_seq_dummy 12288 0
snd_hrtimer 12288 1
vboxnetadp 28672 0
vboxnetflt 36864 0
vboxdrv 700416 2 vboxnetadp,vboxnetflt
openafs 3010560 2
ccm 20480 6
rfcomm 102400 6
cmac 12288 4
algif_hash 16384 1
algif_skcipher 16384 1
af_alg 32768 6 algif_hash,algif_skcipher
qrtr 53248 2
bnep 32768 2
binfmt_misc 24576 1
nls_iso8859_1 12288 1
xe 3452928 0
drm_gpuvm 45056 1 xe
gpu_sched 61440 1 xe
drm_ttm_helper 16384 1 xe
drm_exec 12288 2 drm_gpuvm,xe
drm_suballoc_helper 16384 1 xe
snd_sof_pci_intel_tgl 12288 0
snd_sof_pci_intel_cnl 20480 1 snd_sof_pci_intel_tgl
snd_sof_intel_hda_generic 36864 2 snd_sof_pci_intel_tgl,snd_sof_pci_intel_cnl
soundwire_intel 77824 1 snd_sof_intel_hda_generic
soundwire_cadence 45056 1 soundwire_intel
snd_hda_codec_idt 73728 1
snd_sof_intel_hda_common 192512 3 snd_sof_intel_hda_generic,snd_sof_pci_intel_tgl,snd_sof_pci_intel_cnl
snd_hda_codec_generic 122880 1 snd_hda_codec_idt
snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common
snd_sof_intel_hda_mlink 45056 3 soundwire_intel,snd_sof_intel_hda_common,snd_sof_intel_hda_generic
snd_sof_intel_hda 24576 2 snd_sof_intel_hda_common,snd_sof_intel_hda_generic
snd_hda_codec_hdmi 98304 1
snd_sof_pci 24576 3 snd_sof_intel_hda_generic,snd_sof_pci_intel_tgl,snd_sof_pci_intel_cnl
snd_sof_xtensa_dsp 12288 1 snd_sof_intel_hda_generic
snd_sof 401408 5 snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_hda_generic,snd_sof_intel_hda,snd_sof_pci_intel_cnl
snd_sof_utils 16384 1 snd_sof
snd_soc_acpi_intel_match 131072 3 snd_sof_intel_hda_generic,snd_sof_pci_intel_tgl,snd_sof_pci_intel_cnl
snd_soc_acpi_intel_sdca_quirks 12288 1 snd_soc_acpi_intel_match
soundwire_generic_allocation 24576 1 soundwire_intel
snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_generic
soundwire_bus 126976 3 soundwire_intel,soundwire_generic_allocation,soundwire_cadence
snd_soc_sdca 12288 2 snd_soc_acpi_intel_sdca_quirks,soundwire_bus
snd_soc_avs 204800 0
snd_soc_hda_codec 24576 1 snd_soc_avs
snd_hda_ext_core 32768 6 snd_soc_avs,snd_soc_hda_codec,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda_mlink,snd_sof_intel_hda
intel_uncore_frequency 16384 0
intel_uncore_frequency_common 16384 1 intel_uncore_frequency
snd_soc_core 434176 6 snd_soc_avs,snd_soc_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda
snd_compress 36864 2 snd_soc_avs,snd_soc_core
ac97_bus 12288 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_hda_intel 65536 1
x86_pkg_temp_thermal 20480 0
snd_intel_dspcfg 45056 5 snd_soc_avs,snd_hda_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_hda_generic
iwlmvm 913408 0
snd_intel_sdw_acpi 16384 2 snd_intel_dspcfg,snd_sof_intel_hda_generic
intel_powerclamp 24576 0
cros_usbpd_charger 24576 0
gpio_cros_ec 12288 0
cros_ec_hwmon 12288 0
cros_ec_chardev 12288 0
cros_ec_debugfs 16384 0
cros_ec_sysfs 16384 0
cros_kbd_led_backlight 12288 0
coretemp 24576 0
snd_hda_codec 204800 8 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_soc_hda_codec,snd_hda_intel,snd_soc_hdac_hda,snd_sof_intel_hda,snd_hda_codec_idt
cros_usbpd_notify 20480 1 cros_usbpd_charger
leds_cros_ec 12288 0
cros_usbpd_logger 16384 0
mac80211 1818624 1 iwlmvm
cros_charge_control 16384 0
led_class_multicolor 16384 1 leds_cros_ec
snd_hda_core 147456 11 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_soc_hda_codec,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda,snd_hda_codec_idt
cmdlinepart 16384 0
kvm_intel 483328 0
spi_nor 163840 0
snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec
uvcvideo 147456 0
libarc4 12288 1 mac80211
cros_ec_dev 12288 0
i915 4743168 43
mei_hdcp 28672 0
mei_pxp 16384 0
mtd 102400 3 spi_nor,cmdlinepart
intel_rapl_msr 20480 0
snd_pcm 196608 14 snd_soc_avs,snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_compress,snd_sof_intel_hda_generic,snd_soc_core,snd_sof_utils,snd_hda_core,snd_pcm_dmaengine
videobuf2_vmalloc 20480 1 uvcvideo
uvc 12288 1 uvcvideo
kvm 1429504 1 kvm_intel
btusb 73728 0
videobuf2_memops 16384 1 videobuf2_vmalloc
btrtl 36864 1 btusb
videobuf2_v4l2 36864 1 uvcvideo
snd_seq_midi 24576 0
snd_seq_midi_event 16384 1 snd_seq_midi
btintel 69632 1 btusb
videobuf2_common 90112 4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
btbcm 24576 1 btusb
irqbypass 12288 1 kvm
drm_buddy 24576 2 xe,i915
hid_sensor_als 16384 0
iwlwifi 659456 1 iwlmvm
snd_rawmidi 57344 3 snd_seq_midi,snd_usbmidi_lib,snd_ump
btmtk 36864 1 btusb
cros_ec_lpcs 20480 0
videodev 364544 2 videobuf2_v4l2,uvcvideo
hid_sensor_trigger 20480 2 hid_sensor_als
rapl 20480 0
ttm 118784 3 drm_ttm_helper,xe,i915
industrialio_triggered_buffer 12288 1 hid_sensor_trigger
cros_ec 20480 1 cros_ec_lpcs
snd_seq 122880 9 snd_seq_midi,snd_seq_midi_event,snd_seq_dummy
bluetooth 1015808 34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
mc 86016 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common
wmi_bmof 12288 0
processor_thermal_device_pci_legacy 12288 0
snd_seq_device 16384 4 snd_seq,snd_seq_midi,snd_ump,snd_rawmidi
kfifo_buf 12288 1 industrialio_triggered_buffer
processor_thermal_device 20480 1 processor_thermal_device_pci_legacy
i2c_i801 36864 0
cfg80211 1437696 3 iwlmvm,iwlwifi,mac80211
drm_display_helper 282624 2 xe,i915
intel_cstate 20480 0
snd_timer 53248 3 snd_seq,snd_hrtimer,snd_pcm
mei_me 57344 2
processor_thermal_wt_hint 16384 1 processor_thermal_device
processor_thermal_rfim 40960 1 processor_thermal_device
hid_sensor_iio_common 24576 2 hid_sensor_trigger,hid_sensor_als
cec 94208 3 drm_display_helper,xe,i915
i2c_smbus 20480 1 i2c_i801
spi_intel_pci 12288 0
processor_thermal_rapl 16384 1 processor_thermal_device
mei 176128 5 mei_hdcp,mei_pxp,mei_me
snd 143360 23 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_sof,snd_timer,snd_compress,snd_soc_core,snd_ump,snd_pcm,snd_hda_codec_idt,snd_rawmidi
i2c_mux 16384 1 i2c_i801
industrialio 143360 4 industrialio_triggered_buffer,hid_sensor_trigger,kfifo_buf,hid_sensor_als
spi_intel 36864 1 spi_intel_pci
intel_rapl_common 53248 2 intel_rapl_msr,processor_thermal_rapl
soundcore 16384 1 snd
rc_core 73728 1 cec
processor_thermal_wt_req 12288 1 processor_thermal_device
processor_thermal_power_floor 12288 1 processor_thermal_device
i2c_algo_bit 20480 2 xe,i915
processor_thermal_mbox 12288 4 processor_thermal_power_floor,processor_thermal_wt_req,processor_thermal_rfim,processor_thermal_wt_hint
intel_soc_dts_iosf 16384 1 processor_thermal_device_pci_legacy
igen6_edac 28672 0
intel_pmc_core 126976 0
int3403_thermal 16384 0
int340x_thermal_zone 16384 2 int3403_thermal,processor_thermal_device
pmt_telemetry 16384 1 intel_pmc_core
int3400_thermal 24576 0
pmt_class 16384 1 pmt_telemetry
acpi_thermal_rel 20480 1 int3400_thermal
intel_vsec 20480 2 intel_pmc_core,xe
acpi_pad 184320 0
joydev 32768 0
input_leds 12288 0
mac_hid 12288 0
sch_fq_codel 24576 2
msr 12288 0
parport_pc 53248 0
ppdev 24576 0
lp 28672 0
parport 73728 3 parport_pc,lp,ppdev
efi_pstore 12288 0
nfnetlink 20480 1
dmi_sysfs 24576 0
ip_tables 36864 0
x_tables 65536 1 ip_tables
autofs4 57344 2
dm_crypt 69632 1
hid_sensor_custom 28672 0
hid_sensor_hub 28672 4 hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_als,hid_sensor_custom
intel_ishtp_hid 32768 0
hid_multitouch 36864 0
hid_generic 12288 0
polyval_clmulni 12288 0
polyval_generic 12288 1 polyval_clmulni
ghash_clmulni_intel 16384 0
nvme 61440 3
sha256_ssse3 32768 0
sha1_ssse3 32768 0
serio_raw 20480 0
intel_ish_ipc 36864 0
thunderbolt 544768 0
nvme_core 229376 4 nvme
intel_ishtp 73728 2 intel_ishtp_hid,intel_ish_ipc
ucsi_acpi 12288 0
intel_lpss_pci 28672 0
typec_ucsi 65536 1 ucsi_acpi
nvme_auth 28672 1 nvme_core
i2c_hid_acpi 12288 0
intel_lpss 12288 1 intel_lpss_pci
i2c_hid 40960 1 i2c_hid_acpi
idma64 20480 0
typec 118784 1 typec_ucsi
hid 266240 6 i2c_hid,usbhid,hid_multitouch,hid_sensor_hub,intel_ishtp_hid,hid_generic
video 77824 2 xe,i915
wmi 28672 2 video,wmi_bmof
pinctrl_tigerlake 28672 2
aesni_intel 122880 11
crypto_simd 16384 1 aesni_intel
cryptd 24576 4 crypto_simd,ghash_clmulni_intel
I wonder if youāre experiencing something thatās distro / distro-update specific.
Have you tried booting with other Framework-Supported live USB / environments?
1 Like
Itās clearly something an OS can do something about, since Windows boots reliably. But it also seems like itās BIOS-related, given the kernel errors about (alleged) BIOS bugs. I have not yet tried other Linux distros while docked, but that is on my list of things to try.
Instructions are unclear.
I have a motherboard in a cooler master case, without a battery so I guess I have to do that:
Updating a Mainboard outside of a laptop
This release supports standalone updates without a battery attached only when updating using the EFI shell method only. After rebooting, please follow the onscreen instructions to update your BIOS when in standalone mode, which will require moving the power source between both sides of the Mainboard to allow PD firmware to update correctly.
Please note that the power and display output must be connected to the same side during standalone updates. Failure to do this may result in no display output during the update process.
We recommend the following update flow for standalone updates:
Part 1
Ensure that standalone operation is enabled in the bios advanced setup menu.
Display connected to upper left port.
Power connected to the lower left port.
Run the updater from EFI shell. Please follow the āInstructions for EFI shell updateā to run the updater.Select the EFI USB Boot Device.
How do I know what is left and what is right side of the motherboard is left the same side as the jack port ?
Then it seems I have to do that:
Instructions for EFI shell update:
Extract contents of zip folder to a FAT32 formatted USB drive. Cleanly unmount the drive before physically removing it, otherwise the BIOS update may not function correctly.
Boot your system while pressing F12 and boot from the thumb drive.
Let startup.nsh run automatically.
Follow the instructions to install the update.
Is the thumb drive the same device as the FAT32 formatted USB drive ? Then I have to remove it ? And then I have to press F12 to boot from it while it is disconnected ? That doesnāt make any sense!
And when I press F12 while I start my computer nothing happens? Am I supposed to get into the BIOs ? Then how ?