Closed sim31 closed 1 year ago
You need to set iomem to relaxed
Just tried that. Now I get a slightly different error in journal:
ar 09 16:16:04 sbook systemd[1]: Starting Firmware update daemon...
Mar 09 16:16:04 sbook fwupd[1654]: 14:16:04.137 FuPluginUefiCapsule SMBIOS BIOS Characteristics Extension Byte 2 is invalid -- >
Mar 09 16:16:05 sbook systemd[1]: Started Firmware update daemon.
Mar 09 16:16:37 sbook fwupd[1654]: 14:16:37.640 FuPluginFlashrom Error accessing Opaque flash chip, 0x2000000 bytes at 0x000>
Mar 09 16:16:37 sbook fwupd[1654]: 14:16:37.640 FuPluginFlashrom /dev/mem mmap failed: Resource temporarily unavailable
Mar 09 16:16:37 sbook fwupd[1654]: 14:16:37.640 FuPluginFlashrom Could not map flash chip Opaque flash chip at 0x00000000fe0>
Mar 09 16:17:18 sbook fwupd[1654]: 14:17:18.621 FuPluginUpower failed to query lid state
Mar 09 16:17:18 sbook fwupd[1654]: 14:17:18.621 FuPluginUpower failed to query lid state
Mar 09 16:17:19 sbook systemd[1]: Stopping Firmware update daemon...
Mar 09 16:17:19 sbook fwupd[1654]: 14:17:19.425 FuMain Received SIGTERM
Mar 09 16:17:19 sbook systemd[1]: fwupd.service: Deactivated successfully.
Mar 09 16:17:19 sbook systemd[1]: Stopped Firmware update daemon.
Mar 09 16:17:19 sbook systemd[1]: fwupd.service: Consumed 1.122s CPU time.
Then I tried the suggestion I found here to set nopat kernel parameter. Then the computer does not boot. It gets stuck at: Triggerring uevents...
. Normally I see this in the beginning of the boot.
You don't need nopat
but that does suggest an old version of flashrom - what version do you have installed?
1.2-4. Just saw that it is flagged as out of date in arch linux repos. Do you think 1.3 would fix this?
Yes it would
Built and installed 1.3.0 flashrom version. Weird - now it does even start the update - says: "no updateable devices".
This is the output from fwupdmgr refresh --force
:
Reading… [ - ]
Updating lvfs
Downloading… [ \ ]
Successfully downloaded new metadata: 0 local devices supported
This is the output from fwupdmgr update
:
Reading… [ - ]
Devices with no available firmware updates:
• 0000:00:1f.5
• Star Drive PCIe SSD
• SuperIO FuSuperioIt89Device
No updatable devices
Output from fwupdmgr get-devices
:
Reading… [ - ]Star Labs StarBook
│
├─0000:00:1f.5:
│ Device ID: b04e387fb80d2b91f37a4d0c7b21461c451775e1
│ Summary: Memory Technology Device
│ Vendor: DMI:Star Labs
│ GUIDs: 5f93d7e7-e282-59b9-b663-0146e382f8f6 ← MTD\NAME_0000:00:1f.5
│ 8332559d-efc1-5670-9baa-e06a25556a96 ← MTD\VENDOR_Star-Labs&NAME_0000:00:1f.5
│ ca2344e2-00a1-509a-9062-031db63bb375 ← MTD\VENDOR_Star-Labs&PRODUCT_StarBook&NAME_0000:00:1f.5
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│ • Cryptographic hash verification is available
│
├─12th Gen Intel Core™ i7-1260P:
│ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ Current version: 0x00000429
│ Vendor: Intel
│ GUIDs: b9a2dd81-159e-5537-a7db-e7101d164d3f ← cpu
│ 30249f37-d140-5d3e-9319-186b1bd5cac3 ← CPUID\PRO_0&FAM_06
│ ab855c04-4ff6-54af-8a8a-d8193daa0cd8 ← CPUID\PRO_0&FAM_06&MOD_9A
│ 3ebbde86-d03e-549a-a8fd-02ebf9aa537a ← CPUID\PRO_0&FAM_06&MOD_9A&STP_3
│ Device Flags: • Internal device
│
├─Alder Lake-P Integrated Graphics Controller:
│ Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a
│ Current version: 0c
│ Vendor: Intel Corporation (PCI:0x8086)
│ GUIDs: eaad9970-8e4d-56da-88ab-41a8c1e2811f ← PCI\VEN_8086&DEV_46A6
│ ed0b9458-c2f1-54c5-9063-dea8f75b4039 ← PCI\VEN_8086&DEV_46A6&REV_0C
│ 226cbe0a-2ccd-5e12-8a5a-60aa1e438894 ← PCI\VEN_8086&DEV_46A6&SUBSYS_808646A6
│ c78c6be8-ff08-5945-bb0b-92f25dca2b68 ← PCI\VEN_8086&DEV_46A6&SUBSYS_808646A6&REV_0C
│ c4625510-a985-517c-8800-0ecfc6f68c8f ← PCI\VEN_8086&DEV_46A6&REV_00
│ 25449cf0-7ce3-5bdd-a343-e9f719a164d2 ← PCI\VEN_8086&DEV_46A6&SUBSYS_808646A6&REV_00
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─Star Drive PCIe SSD:
│ Device ID: 03281da317dccd2b18de2bd1cc70a782df40ed7e
│ Summary: NVM Express solid state drive
│ Current version: EIFM31.4
│ Vendor: Phison Electronics Corporation (NVME:0x1987)
│ Serial Number: 1348072C06C700242034
│ GUIDs: 59639c7d-1b5d-5b7f-82da-9fd6b369a461 ← NVME\VEN_1987&DEV_5018
│ fcc92585-8e8e-52a3-90cc-6c022b7f3843 ← NVME\VEN_1987&DEV_5018&REV_01
│ b1fcba59-6797-58bd-af77-5ccb9be2493c ← NVME\VEN_1987&DEV_5018&SUBSYS_19875018
│ c9465066-32bb-50c5-8338-6a750cae2a44 ← NVME\VEN_1987&DEV_5018&SUBSYS_19875018&REV_01
│ 12d61493-5ac4-57f7-a2c5-96878d115455 ← Star Drive PCIe SSD
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs shutdown after installation
│ • Device is usable for the duration of the update
│
├─SuperIO FuSuperioIt89Device:
│ Device ID: 3ecf3fbe07ed8933226b294c8c19f4f9c8ebd71a
│ Summary: Embedded controller
│ Current version: 01.01
│ Vendor: DMI:Star Labs
│ Install Duration: 20 seconds
│ GUIDs: 55a8a029-ca9f-5b54-b68d-412281a2a84c ← SUPERIO\GUID_5c917039-d938-5c9a-b22a-9c392b1534f3
│ d83a4cd0-fce6-58a8-93c7-bcee89b41dcf ← SuperIO-FuSuperioIt89Device
│ Device Flags: • Internal device
│ • Updatable
│ • Update requires a reboot
│ • System requires external power source
│ • Needs a reboot after installation
│ • Cryptographic hash verification is available
│ • Signed Payload
│
└─TPM:
Device ID: c6a80ac3a22083423992a3cb15018989f37834d6
Current version: 7.85.17.51968
Vendor: Infineon (TPM:IFX)
GUIDs: ff71992e-52f7-5eea-94ef-883e56e034c6 ← system-tpm
5eebb112-75ad-5536-b173-a11eb3399402 ← TPM\VEN_IFX&DEV_0000
ddf995da-1b32-5a8a-bc1b-8d5af4b38b51 ← TPM\VEN_IFX&MOD_SLB9670
6d81ab63-db2e-50ac-934f-6be9accf5e02 ← TPM\VEN_IFX&DEV_0000&VER_2.0
301555de-680d-5ddc-b995-7553fc9138f1 ← TPM\VEN_IFX&MOD_SLB9670&VER_2.0
Device Flags: • Internal device
It sounds like you've installed flashrom in a different place; I've never tried it on Arch (PKGBUILD has always sufficed) but I think it should be meson build --prefix=/usr
I used this PKGBUILD from AUR to install, with a modification to take v1.3.0 tag instead of master (later tried to take master as well, but did not help). This PKGBUILD uses arch-meson wrapper, which adds --prefix=/usr
by default.
I even installed the flashrom 1.2 from main repos again, just to see if it instals to the same place. From pacman I can tell that both installations own the same filenames in the same locations.
Not sure - using a Live USB would be the best bet until the Arch packages get sorted out (shouldn't be long given that it's Arch!)
Output from
fwupdmgr report-history
:Relevant journal entries (
journalctl -u fwupd
):I run arch linux and installed fwupd using gnome-firmware package.
Not sure if this is the best place to report it, so let me know.