FAQ - Revision history

Icon: "nico.h@gmx.de: Rename => Supported Hardware"

2023-12-03T17:46:58Z

"nico.h@gmx.de: Rename => Supported *H*ardware"

← Older revision		Revision as of 17:46, 3 December 2023
Line 1:		Line 1:
	== Flashprog doesn't seem to work on my board, what can I do? ==		== Flashprog doesn't seem to work on my board, what can I do? ==

	* First of all, check if your chipset, ROM chip, and mainboard are supported (see [[Supported ~~hardware~~]], or use '''flashprog -L''').		* First of all, check if your chipset, ROM chip, and mainboard are supported (see [[Supported Hardware]], or use '''flashprog -L''').
	* If your board has a jumper for BIOS flash protection (check the manual), disable it.		* If your board has a jumper for BIOS flash protection (check the manual), disable it.
	* Should your BIOS menu have a BIOS flash protection option, disable it.		* Should your BIOS menu have a BIOS flash protection option, disable it.

Icon: "nico.h@gmx.de: Update for flashprog"

2023-12-03T17:46:47Z

"nico.h@gmx.de: Update for flashprog"

Nico@flashrom.org/: "Nico@flashrom.org/: add question about linux_spi and spispeed"

2023-12-03T17:46:46Z

"Nico@flashrom.org/: add question about linux_spi and spispeed"

← Older revision		Revision as of 17:46, 3 December 2023
Line 22:		Line 22:

	* Generally, if your version of flashrom is very old, an update might help. Flashrom has less strict requirements now and works on more systems without having to change the kernel.		* Generally, if your version of flashrom is very old, an update might help. Flashrom has less strict requirements now and works on more systems without having to change the kernel.

			== I'm using flashrom with ''linux_spi'' and it doesn't find the chip. I've double checked all connections, what else can I try? ==

			* In case you haven't set it already: The ''linux_spi'' driver has a '''''spispeed''''' parameter that should always be set to a reasonable speed (100kHz..10,000kHz, try lower frequencies first). Also see the flashrom(8) manpage.

			* Generally, [[Common problems]] and [[ISP]] may apply.

	== How do I use flashrom? ==		== How do I use flashrom? ==

Nico@flashrom.org/: "Nico@flashrom.org/: remove broken link to flashrom.8"

2023-12-03T17:46:46Z

"Nico@flashrom.org/: remove broken link to flashrom.8"

← Older revision		Revision as of 17:46, 3 December 2023
Line 31:		Line 31:
	== How do I use flashrom? ==		== How do I use flashrom? ==

	Please see the ~~[http://~~flashrom.~~org/trac/flashrom/browser/trunk/flashrom~~.8 flashrom(8)~~] manpage~~.		Please see the flashrom(8) manpage (e.g. execute `'''''man flashrom'''''`).

	== Is there a flashrom Live CD? ==		== Is there a flashrom Live CD? ==

	See [[Live CD]].		See [[Live CD]].

Nico@flashrom.org/: "Nico@flashrom.org/: Empty MediaWiki Message"

2023-12-03T17:46:46Z

"Nico@flashrom.org/: *Empty MediaWiki Message*"

← Older revision		Revision as of 17:46, 3 December 2023
Line 12:		Line 12:

	* If flashrom tells you '/dev/mem mmap failed: ''Operation not permitted''':		* If flashrom tells you '/dev/mem mmap failed: ''Operation not permitted''':
	** Most common at the time of writing is a Linux kernel option, CONFIG_IO_STRICT_DEVMEM, that prevents even the root user from accessing hardware from user-space. ~~Try~~ again after rebooting with '''''iomem=relaxed''''' in ~~your~~ kernel command line.		** Most common at the time of writing is a Linux kernel option, CONFIG_IO_STRICT_DEVMEM, that prevents even the root user from accessing hardware from user-space if the resource is unknown to the kernel or a conflicting kernel driver reserved it. On Intel systems, this is most often ''lpc_ich'', so '''''modprobe -r lpc_ich''''' can help. A more invasive solution is to try again after rebooting with '''''iomem=relaxed''''' in the kernel command line.
	** Some systems with incorrect memory reservations (e.g. E820 map) may have the same problem even with CONFIG_STRICT_DEVMEM. In that case '''''iomem=relaxed''''' in the kernel command line may help too.		** Some systems with incorrect memory reservations (e.g. E820 map) may have the same problem even with CONFIG_STRICT_DEVMEM. In that case '''''iomem=relaxed''''' in the kernel command line may help too.

Nico@flashrom.org/: "Nico@flashrom.org/: update reference to /dev/mem question"

2023-12-03T17:46:46Z

"Nico@flashrom.org/: update reference to /dev/mem question"

← Older revision		Revision as of 17:46, 3 December 2023
Line 4:		Line 4:
	* If your board has a jumper for BIOS flash protection (check the manual), disable it.		* If your board has a jumper for BIOS flash protection (check the manual), disable it.
	* Should your BIOS menu have a BIOS flash protection option, disable it.		* Should your BIOS menu have a BIOS flash protection option, disable it.
	* If you run flashrom on a Linux ~~system with kernels >= 2~~.~~6.27 there are two issues you have to check:~~		* If you run flashrom on Linux and see messages about /dev/mem, see next question.
	** TODO: '''X86_PAT''' and '''nopat'''
	** TODO: '''CONFIG_STRICT_DEVMEM'''
	* If you run flashrom on OpenBSD, you might need to obtain raw access permission by setting '''securelevel=-1''' in '''/etc/rc.securelevel''' and rebooting, or rebooting into single user mode.		* If you run flashrom on OpenBSD, you might need to obtain raw access permission by setting '''securelevel=-1''' in '''/etc/rc.securelevel''' and rebooting, or rebooting into single user mode.

Uwe@flashrom.org/: "Uwe@flashrom.org/: OpenBSD securelevel issue."

2023-12-03T17:46:45Z

"Uwe@flashrom.org/: OpenBSD securelevel issue."

← Older revision		Revision as of 17:46, 3 December 2023
Line 7:		Line 7:
	** TODO: '''X86_PAT''' and '''nopat'''		** TODO: '''X86_PAT''' and '''nopat'''
	** TODO: '''CONFIG_STRICT_DEVMEM'''		** TODO: '''CONFIG_STRICT_DEVMEM'''
			* If you run flashrom on OpenBSD, you might need to obtain raw access permission by setting '''securelevel=-1''' in '''/etc/rc.securelevel''' and rebooting, or rebooting into single user mode.

	* See [[Easy projects#Test_flashrom\|this page]] for instructions on how to test flashrom support properly (this may be risky, make sure you have a working backup flash chip).		* See [[Easy projects#Test_flashrom\|this page]] for instructions on how to test flashrom support properly (this may be risky, make sure you have a working backup flash chip).

Hailfinger@flashrom.org/: "Hailfinger@flashrom.org/: /* flashrom doesn't seem to work on my board, what can I do? */ correct link to testing instructions"

2023-12-03T17:46:45Z

"Hailfinger@flashrom.org/: flashrom doesn't seem to work on my board, what can I do?: correct link to testing instructions"

← Older revision		Revision as of 17:46, 3 December 2023
Line 1:		Line 1:
	== flashrom doesn't seem to work on my board, what can I do? ==		== flashrom doesn't seem to work on my board, what can I do? ==

	* First of all, check if your chipset, ROM chip, and mainboard are supported (see ~~tables above~~, or use '''flashrom -L''').		* First of all, check if your chipset, ROM chip, and mainboard are supported (see [[Supported hardware]], or use '''flashrom -L''').
	* If your board has a jumper for BIOS flash protection (check the manual), disable it.		* If your board has a jumper for BIOS flash protection (check the manual), disable it.
	* Should your BIOS menu have a BIOS flash protection option, disable it.		* Should your BIOS menu have a BIOS flash protection option, disable it.
Line 7:		Line 7:
	** TODO: '''X86_PAT''' and '''nopat'''		** TODO: '''X86_PAT''' and '''nopat'''
	** TODO: '''CONFIG_STRICT_DEVMEM'''		** TODO: '''CONFIG_STRICT_DEVMEM'''
	* See [[~~Board Testing HOWTO~~#~~Flashrom~~\|this page]] for instructions on how to test flashrom support properly (this may be risky, make sure you have a working backup flash chip).		* See [[Easy projects#Test_flashrom\|this page]] for instructions on how to test flashrom support properly (this may be risky, make sure you have a working backup flash chip).

	== How do I use flashrom? ==		== How do I use flashrom? ==

Uwe@flashrom.org/: "Uwe@flashrom.org/: Linkfix."

2023-12-03T17:46:45Z

"Uwe@flashrom.org/: Linkfix."

← Older revision		Revision as of 17:46, 3 December 2023
Line 17:		Line 17:
	== Is there a flashrom Live CD? ==		== Is there a flashrom Live CD? ==

	See [[~~Flashrom/~~Live CD]].		See [[Live CD]].

Nico@flashrom.org/: "Nico@flashrom.org/: rewrite /dev/mem trouble section"

2023-12-03T17:46:45Z

"Nico@flashrom.org/: rewrite /dev/mem trouble section"

← Older revision		Revision as of 17:46, 3 December 2023
Line 10:		Line 10:

	* See [[Easy projects#Test_flashrom\|this page]] for instructions on how to test flashrom support properly (this may be risky, make sure you have a working backup flash chip).		* See [[Easy projects#Test_flashrom\|this page]] for instructions on how to test flashrom support properly (this may be risky, make sure you have a working backup flash chip).

			== What can I do about ''/dev/mem'' errors? ==

			* If flashrom tells you '/dev/mem mmap failed: ''Operation not permitted''':
			** Most common at the time of writing is a Linux kernel option, CONFIG_IO_STRICT_DEVMEM, that prevents even the root user from accessing hardware from user-space. Try again after rebooting with '''''iomem=relaxed''''' in your kernel command line.
			** Some systems with incorrect memory reservations (e.g. E820 map) may have the same problem even with CONFIG_STRICT_DEVMEM. In that case '''''iomem=relaxed''''' in the kernel command line may help too.

			* If it tells you '/dev/mem mmap failed: ''Resource temporarily unavailable''':
			** This may be an issue with PAT (e.g. if the memory flashrom tries to map is already mapped in an incompatible mode). Try again after rebooting with '''''nopat''''' in the kernel command line.

			* If you see this message 'Can't mmap memory using /dev/mem: Invalid argument':
			** Your flashrom is very old, better update it. If the issue persists, try the kernel options mentioned above.

			* Generally, if your version of flashrom is very old, an update might help. Flashrom has less strict requirements now and works on more systems without having to change the kernel.

	== How do I use flashrom? ==		== How do I use flashrom? ==

FAQ - Revision history

Icon: "nico.h@gmx.de: Rename => Supported *H*ardware"

Icon: "nico.h@gmx.de: Update for flashprog"

Nico@flashrom.org/: "Nico@flashrom.org/: add question about linux_spi and spispeed"

Nico@flashrom.org/: "Nico@flashrom.org/: remove broken link to flashrom.8"

Nico@flashrom.org/: "Nico@flashrom.org/: *Empty MediaWiki Message*"

Nico@flashrom.org/: "Nico@flashrom.org/: update reference to /dev/mem question"

Uwe@flashrom.org/: "Uwe@flashrom.org/: OpenBSD securelevel issue."

Hailfinger@flashrom.org/: "Hailfinger@flashrom.org/: /* flashrom doesn't seem to work on my board, what can I do? */ correct link to testing instructions"

Uwe@flashrom.org/: "Uwe@flashrom.org/: Linkfix."

Nico@flashrom.org/: "Nico@flashrom.org/: rewrite /dev/mem trouble section"

Icon: "nico.h@gmx.de: Rename => Supported Hardware"

Nico@flashrom.org/: "Nico@flashrom.org/: Empty MediaWiki Message"