ghost commented 10 months ago

I have the fwupd 1.9.5 and flashrom 1.2-4 installed. Do I need to have those manjaro packages of starlabs?

Sean-StarLabs commented 10 months ago

Shouldn't make too much difference when you get it from , you just need something newer than 1.2 - https://support.starlabs.systems/kb/firmware/lvfs-requirements

ghost commented 9 months ago

I see, I asked because I wanted to test if switching branch works, not working: $ fwupdmgr switch-branch no devices Always with more than 30% battery, and power cord inside.

Sean-StarLabs commented 9 months ago

Which model and which way?

ghost commented 9 months ago

lite mkIII, and ami>coreboot. I know it's beta yet, just want to make sure it works on arch when ready to make the switch

Sean-StarLabs commented 9 months ago

Most likely:

testing remote isn't enabled
flashrom is too old (1.2 definitely is for GLK)
BIOS Lock is enabled

ghost commented 9 months ago

I have testing enabled, flashrom 1.2-4 and BIOS unlocked Should I try with this version of flashrom: https://aur.archlinux.org/packages/flashrom-git?

Sean-StarLabs commented 9 months ago

What does sudo flashrom -p internal say?

ghost commented 9 months ago

flashrom v1.2 on Linux 6.5.5-arch1-1 (x86_64) flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). No DMI table found. WARNING: No chipset found. Flash detection will most likely fail.

You may be running flashrom on an unknown laptop. We could not detect this for sure because your vendor has not set up the SMBIOS tables correctly. Some internal buses have been disabled for safety reasons. You can enforce using all buses by adding -p internal:laptop=this_is_not_a_laptop to the command line, but please read the following warning if you are not sure.

Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details.

If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned.

No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.

Sean-StarLabs commented 9 months ago

That's too old - need a newer version

ghost commented 9 months ago

not sure why the text got disconfigure like that...what version should I use? that one from aur? flashrom-git 1.2.1353.gebda447a-2

Sean-StarLabs commented 9 months ago

1.3 would definately work, you can try the one from AUR - I don't know how they work in terms of what commit it'll use, so don't know if it'll work or not

ghost commented 9 months ago

with flashrom 1.3 installed: `$ sudo flashrom -p internal flashrom unknown on Linux 6.5.5-arch1-1 (x86_64) flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). No DMI table found. Found chipset "Intel Gemini Lake". Enabling flash write... SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only. FREG1: BIOS region (0x00001000-0x0067efff) is read-write. FREG5: Device Expansion region (0x0067f000-0x0077ffff) is locked. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME for details. At least some flash regions are read protected. You have to use a flash layout and include only accessible regions. For write operations, you'll additionally need the --noverify-all switch. See manpage for more details. Enabling hardware sequencing because some important opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific) on internal. No operations were specified.`

ghost commented 9 months ago

But still: $ fwupdmgr switch-branch no devices

ghost commented 9 months ago

No, it needed a reboot: $ fwupdmgr switch-branch Dispositivo selezionato: Lite (bios) ╔══════════════════════════════════════════════════════════════════════════════╗ ║ Passare dal ramo predefinito a coreboot? ║ ╠══════════════════════════════════════════════════════════════════════════════╣ ║ This stable release includes the following features: ║ ║ ║ ║ • Fix the inconsistant memory map in edk2 ║ ║ • Disable DPST to fix a flicker with recent kernels ║ ║ • Dont let coreboot try to change EC values ║ ╚══════════════════════════════════════════════════════════════════════════════╝ Le conseguenze del cambio di ramo del firmware sono state comprese? [y|N]:

StarLabsLtd / firmware

How to make fwupd to work on arch linux? #129

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). No DMI table found. WARNING: No chipset found. Flash detection will most likely fail.

If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned.