Advertisement
Guest User

Untitled

a guest
Dec 11th, 2024
38
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.68 KB | None | 0 0
  1. $ sudo ./flashrom -p internal --noverify-all --wp-enable -V
  2. flashrom v1.5.0-devel on Linux 6.8.0-38-generic (x86_64)
  3. flashrom is free software, get the source code at https://flashrom.org
  4.  
  5. flashrom was built with GCC 13.2.0, little endian
  6. Command line (5 args): ./flashrom -p internal --noverify-all --wp-enable -V
  7. Acquiring lock (timeout=180 sec)...
  8. Opened file lock "/run/lock/firmware_utility_lock"
  9. Lock acquired.
  10. Initializing internal programmer
  11. get_mtd_info: device_name: "BIOS", is_writeable: 0, numeraseregions: 0, total_size: 16777216, erasesize: 4096
  12. Cannot open file stream for /dev/mtd0
  13. Found candidate at: 00000500-00000528
  14. Found coreboot table at 0x00000500.
  15. Found candidate at: 00000000-00000548
  16. Found coreboot table at 0x00000000.
  17. coreboot table found at 0x7aa9c000.
  18. coreboot header(24) checksum: 89a2 table(1328) checksum: df52 entries: 45
  19. Vendor ID: Google, part ID: Caroline
  20. Using Internal DMI decoder.
  21. DMI string chassis-type: "Laptop"
  22. Laptop detected via DMI.
  23. DMI string system-manufacturer: "Google"
  24. DMI string system-product-name: "Caroline"
  25. DMI string system-version: "1.0"
  26. DMI string baseboard-manufacturer: "Google"
  27. DMI string baseboard-product-name: "Caroline"
  28. DMI string baseboard-version: "1.0"
  29. Found chipset "Intel Skylake Y Premium" with PCI ID 8086:9d46.
  30. This chipset is marked as untested. If you are using an up-to-date version
  31. of flashrom *and* were (not) able to successfully update your firmware with it,
  32. then please email a report to [email protected] including a verbose (-V) log.
  33. Thank you!
  34. Enabling flash write... Using libpci PCI_ACCESS_I386_TYPE1
  35. BIOS_SPI_BC = 0x8b: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x0 (SPI)
  36. Top Swap: not enabled
  37. SPI Read Configuration: prefetching enabled, caching enabled,
  38. BIOS_CNTL = 0x8b: BIOS Lock Enable: enabled, BIOS Write Enable: enabled
  39. Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed.
  40. New value is 0x8b.
  41. SPIBAR = 0x000070a6566a9000 (phys = 0xfe010000)
  42. 0x04: 0xf800 (HSFS)
  43. HSFS: FDONE=0, FCERR=0, AEL=0, SCIP=0, PRR34_LOCKDN=1, WRSDIS=1, FDOPSS=1, FDV=1, FLOCKDN=1
  44. SPI Configuration is locked down.
  45. Reading OPCODES... done
  46. 0x06: 0x020c (HSFC)
  47. HSFC: FGO=0, FCYCLE=6, WET=0, FDBC=2, SME=0
  48. 0x0c: 0x00001f00 (DLOCK)
  49. DLOCK: BMWAG_LOCKDN=0, BMRAG_LOCKDN=0, SBMWAG_LOCKDN=0, SBMRAG_LOCKDN=0,
  50. PR0_LOCKDN=1, PR1_LOCKDN=1, PR2_LOCKDN=1, PR3_LOCKDN=1, PR4_LOCKDN=1,
  51. SSEQ_LOCKDN=0
  52. 0x50: 0x00004acb (FRAP)
  53. BMWAG 0x00, BMRAG 0x00, BRWA 0x4a, BRRA 0xcb
  54. 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
  55. 0x58: 0x0fff0200 FREG1: BIOS region (0x00200000-0x00ffffff) is read-write.
  56. 0x5C: 0x01ff0001 FREG2: Management Engine region (0x00001000-0x001fffff) is locked.
  57. Not all flash regions are freely accessible by flashrom. This is most likely
  58. due to an active ME. Please see https://flashrom.org/ME for details.
  59. At least some flash regions are read protected. You have to use a flash
  60. layout and include only accessible regions. For write operations, you'll
  61. additionally need the --noverify-all switch. See manpage for more details.
  62. 0xa0: 0x80 (SSFS)
  63. SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0
  64. 0xa1: 0xfe0000 (SSFC)
  65. SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=6
  66. 0xa4: 0x5006 (PREOP)
  67. 0xa6: 0xb32d (OPTYPE)
  68. 0xa8: 0x05030201 (OPMENU)
  69. 0xac: 0x0bd89f20 (OPMENU+4)
  70. 0xc4: 0xf3d82004 (LVSCC)
  71. LVSCC: BES=0x0, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1
  72. 0xc8: 0x00002000 (UVSCC)
  73. UVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x20
  74. Enabling hardware sequencing by default for 100+ series PCH.
  75. OK.
  76. The following protocols are supported: Programmer-specific.
  77. Probing for Programmer Opaque flash chip, 0 kB: Hardware sequencing reports 1 attached SPI flash chip with a density of 16384 kB.
  78. HSFC: FGO=1, FCYCLE=6, WET=0, FDBC=2, SME=0
  79. Chip identified: GD25Q127C/GD25Q128E
  80. Added layout entry 00000000 - 00ffffff named complete flash
  81. Found GigaDevice flash chip "GD25Q127C/GD25Q128E" (16384 kB, Programmer-specific) on internal.
  82. Found GigaDevice flash chip "GD25Q127C/GD25Q128E" (16384 kB, Programmer-specific).
  83. This chip may contain one-time programmable memory. flashrom cannot read
  84. and may never be able to write it, hence it may not be able to completely
  85. clone the contents of this chip (see man page for details).
  86. Reading Status register
  87. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  88. Reading Status register
  89. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  90. ich_hwseq_read_status: only supports STATUS1
  91. wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00.
  92. Reading Status register
  93. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  94. ich_hwseq_read_status: only supports STATUS1
  95. wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00.
  96. Reading Status register
  97. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  98. Reading Status register
  99. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  100. Reading Status register
  101. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  102. Reading Status register
  103. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  104. Reading Status register
  105. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  106. ich_hwseq_read_status: only supports STATUS1
  107. wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00.
  108. Reading Status register
  109. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  110. ich_hwseq_read_status: only supports STATUS1
  111. wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00.
  112. Reading Status register
  113. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  114. Reading Status register
  115. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  116. Reading Status register
  117. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  118. Reading Status register
  119. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  120. ich_hwseq_read_status: only supports STATUS1
  121. wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00.
  122. Reading Status register
  123. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  124. ich_hwseq_read_status: only supports STATUS1
  125. wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00.
  126. Reading Status register
  127. HSFC: FGO=1, FCYCLE=8, WET=0, FDBC=0, SME=0
  128. Writing status register
  129. HSFC: FGO=1, FCYCLE=7, WET=0, FDBC=0, SME=0
  130. Transaction error between offset 0x00000001 and 0x00000001 (= 0x00000001 + 0)!
  131. HSFS: FDONE=1, FCERR=1, AEL=0, SCIP=0, PRR34_LOCKDN=1, WRSDIS=1, FDOPSS=1, FDV=1, FLOCKDN=1
  132. HSFC: FGO=0, FCYCLE=7, WET=0, FDBC=0, SME=0
  133. Writing Status register failed
  134. !!Failed to apply new WP settings: failed to write the new WP configuration
  135. Restoring PCI config space for 00:1f:5 reg 0xdc
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement