index : archiso32 | |
Archlinux32 iso tools | gitolite user |
summaryrefslogtreecommitdiff |
author | Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> | 2012-12-10 12:06:19 -0300 |
---|---|---|
committer | Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> | 2012-12-10 12:06:19 -0300 |
commit | f11f34ce48cc5557870dd716e989a87cd4722589 (patch) | |
tree | 9e7c3f9438f3711c7aedb691afb3f48945ce0de9 /docs | |
parent | 943fc674115a36f0488644fdf5647bfeb297acae (diff) |
-rw-r--r-- | docs/README.knownissues | 13 | ||||
-rw-r--r-- | docs/README.transfer | 1 |
diff --git a/docs/README.knownissues b/docs/README.knownissues index c397afb..2f9cf70 100644 --- a/docs/README.knownissues +++ b/docs/README.knownissues @@ -8,3 +8,16 @@ and device mapper devices made by archiso will be "free" on "shutdown tmpfs" (A.K.A deinitramfs), build at initramfs by [archiso_shutdown] initcpio hook. Proper shutdown is mostly important when persistent is used. + +** (2) ISOHYBRID-MBR does boot on some hardware: + + Some firmwares (BIOS) gets confused about using this hack + (first partition start at offset 0 -> MBR "infinite recursion"). + Solutions: + (a) Do not use this method, instead copy files manually and + setup the bootloader [PC-BIOS (MBR)] (See README.transfer). + (b) Change offset of the partition on the ISO or on the target medium + (if ISO is already dumped): + # isohybrid.pl -offset 1 <ISO-SOURCE> + OR + # isohybrid.pl -offset 1 <DEV-TARGET> diff --git a/docs/README.transfer b/docs/README.transfer index d01259b..0507397 100644 --- a/docs/README.transfer +++ b/docs/README.transfer @@ -98,6 +98,7 @@ Note: COW is not supported on NTFS. Note: This method is the most easily, quick and dirty, but is the most limited if you want to use your target medium for other purposes. + See README.knownissues (2) if using this method does not boot. 1) Dump ISO file to target medium. # dd if=<ISO-SOURCE> of=<DEV-TARGET> |