Update TODO file

[grml2usb.git] / grml2usb.8.txt

diff --git a/grml2usb.8.txt b/grml2usb.8.txt
index 995c8a5..4e5860e 100644 (file)
--- a/grml2usb.8.txt
+++ b/grml2usb.8.txt
@@ -340,16 +340,26 @@ Where can I get grml2usb?
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
 grml2usb is available as Debian package via link:http://deb.grml.org/[the
-grml-testing Debian repository]. Please make sure you really have the Debian
-package installed as having just the grml2usb script available is definitely
-*NOT* enough!
+grml-testing Debian repository].
 
-If you do NOT have a Debian based system but still want to be able to use
-grml2usb you can use the provided
+If you do not want to (or can't) use the grml2usb Debian package you can either
+use the grml2usb git tree running:
+
+  git clone git://git.grml.org/grml2usb.git
+  cd grml2usb
+  make -C mbr
+  sudo ./grml2usb ...
+
+or download the provided
 link:http://grml.org/grml2usb/grml2usb.tgz[http://grml.org/grml2usb/grml2usb.tgz]
 (link:http://grml.org/grml2usb/grml2usb.tgz.md5.asc[gpg signed md5 hash]).
 Download and extract the tarball and execute the provided script 'install.sh'.
 
+[NOTE]
+It is *NOT* enough to have just the grml2usb script itself without the according
+files provided either via the Debian package, the git tree or the file
+grml2usb.tgz.
+
 [[grml2hd-vs-grml2usb]]
 What's the difference between grml2hd and grml2usb?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -460,7 +470,47 @@ The following message:
 
   '/usr/sbin/grub-install: line 374: [: =: unary operator expected'
 
-This is "normal". Just ignore it.
+This is "normal". Just ignore it. (It usually doesn't appear
+on the second invocation on the same device.)
+
+[[unknown-filesystem]]
+grub-install fails with grub-probe: error: unknown filesystem?!
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following message:
+
+  grub-probe: error: unknown filesystem
+  Auto-detection of a filesystem module failed.
+  Please specify the module with the option `--modules' explicitly.
+
+usually means that the device partition table says something else than the
+filesystem on the device. For example using FAT16 as filesystem type and
+using FAT32 as filesystem on the partition will not work. Either set filesystem
+type to FAT32 or format the partition using FAT16. It is essential that
+device partition table and filesystem use the same filesystem type.
+
+[[mbr-vs-pbr]]
+grub-setup fails after Attempting to install GRUB to a partition instead of the MBR?!
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following message:
+
+  grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR.  This is a BAD idea.
+  grub-setup: warn: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and its use is discouraged.
+  grub-setup: error: Cannot read `/grub/core.img' correctly
+
+appears because recent grub2 versions introduced a regression which avoids that
+grub is being installed into a partition (instead of MBR). We (the grml2usb
+developers) are evaluating the current situation (thinking about installing grub
+into the MBR). To fix this issue in the meanwhile either manually execute
+(adjust '/dev/sdx' to your device of course):
+
+  mount /dev/sdx1 /mnt/test
+  grub-install --force --recheck --no-floppy --root-directory=/mnt/test /dev/sdx
+
+after execution of grml2usb failed (this will will install grub into the MBR of
+the specified device) or consider using the '--syslinux' option until this issue
+is resolved.  Sorry about that.
 
 [[splash-xpm]]
 I'm getting something like "Error: /usr/share/grml2usb/grub/splash.xpm.gz can not be read"!?