summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkarolherbst <karolherbst@web>2017-04-18 16:22:32 +0000
committernouveau <iki-nouveau@freedesktop.org>2017-04-18 16:22:32 +0000
commitee497ba3f6cbf634fa6f7ff4321bbc23c15d768f (patch)
treef983b96b8ce60dde871e5646e8e15dbe35a6a50a
parentbae1e7540ac98c84a7b1731878fbce5a7d3f5117 (diff)
remove outdated ways to retrieve it
-rw-r--r--DumpingVideoBios.mdwn6
1 files changed, 0 insertions, 6 deletions
diff --git a/DumpingVideoBios.mdwn b/DumpingVideoBios.mdwn
index 20217c7..18a3740 100644
--- a/DumpingVideoBios.mdwn
+++ b/DumpingVideoBios.mdwn
@@ -10,12 +10,6 @@ A video BIOS may contain x86 binary code, binary scripts and several data tables
There are several options on how to dump the BIOS:
-* vbtracetool: [[http://cgit.freedesktop.org/~stuart/vbtracetool/|http://cgit.freedesktop.org/~stuart/vbtracetool/]]
- * Vbtracetool can do more than just dump the BIOS, and is the recommended method. You can get it with git: `git clone git://people.freedesktop.org/~stuart/vbtracetool` and then follow the QUICKSTART.
-* using /sys: `echo 1 > /sys/bus/pci/devices/<pciid>/rom; cat /sys/bus/pci/devices/<pciid>/rom > vbios.rom; echo 0 > /sys/bus/pci/devices/<pciid>/rom`
-* using a dd incantation: `dd if=/dev/mem of=vbios.rom bs=1k skip=768 count=64`
- * This can result in a damaged BIOS dump unfortunately, due to possible mangling when the system BIOS copies the video BIOS in shadow RAM.
-* nvclock: [[http://www.linuxhardware.org/nvclock/|http://www.linuxhardware.org/nvclock/]]
* nvagetbios: [[https://github.com/envytools/envytools/blob/master/nva/nvagetbios.c]]
* using any nouveau module after 2.6.34 ([[commit|http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=b42861f40f5ea3261d9fa1d5533496bf1fc812cf]]):
* `cat /sys/kernel/debug/dri/0/vbios.rom > vbios.rom` `Note: assuming that you have debugfs mounted on "/sys/kernel/debug"`