- <p>If you find another bug, or consider something a problem not yet
- mentioned <a href="#bugreport">please report it</a>.</p>
-
- <h3><a name="hardware"></a><a href="#toc">I have problems with my hardware!</a></h3>
-
- <p>Take a look at the script grml-hwinfo. This script generates a file
- named info.tar.bz2 which contains important information about your
- hardware. If you think we might help, please run grml-hwinfo and <a
- href="/contact/">send us the file</a> with additional, relevant
- information regarding your problem.</p>
-
- <h3><a name="boot"></a><a href="#toc">grml does not boot on my computer!</a></h3>
-
- <p>Please take a look at <a
- href="http://git.grml.org/?p=grml-live.git;a=blob_plain;f=templates/GRML/grml-cheatcodes.txt;hb=HEAD">the
- available bootparamters and cheatcodes</a> and '<a href="#booting">Which
- ways exist to boot grml?</a>'. Especially booting with 'acpi=off noapm
- noapic' might help. The bootparameter 'failsafe' provides minimal
- hardware detection using some special bootoptions (please do NOT boot
- with 'grml failsafe' but with 'failsafe' as first word of the boot
- commandline) . If booting hangs during stage "Waiting for /dev to
- be fully populated" please try booting with 'grml noudev'. If you
- don't even see the bootsplash of the grml-ISO your BIOS might be broken
- (pretty common especially on old hardware). Please consider using <a
- href="http://btmgr.sourceforge.net/">btmgr</a> then for booting your
- system. Also check out the <a
- href="http://wiki.grml.org/doku.php?id=problems">problems webpage</a> in
- <a href="http://wiki.grml.org/">the grml-wiki</a>. You still have
- problems? Feel free to <a href="/contact/">contact us</a>.</p>
-
- <h3><a name="fbprobs"></a><a href="#toc">I don't see anything when booting grml?!</a></h3>
-
- <p>Likely, this is a problem with the vesafb framebuffer. Try to boot
- with the 'Disable Framebuffer' menuentry (available behind the submenu
- 'Boot options for ...') or manually ad 'vga=normal' to the kernel
- command line (press TAB to edit a menu entry and add 'vga=normal'
- to it then).</p>
-
- <h3><a name="utf8"></a><a href="#toc">I have problems with UTF-8 / Unicode</a></h3>
-
- <p>Check out <a
- href="http://wiki.grml.org/doku.php?id=utf8">UTF8-webpage in the
- grml-wiki</a>.</p>
-
- <h3><a name="cifsshare"></a><a href="#toc">Booting grml-small via PXE using a CIFS share fails</a></h3>
-
- <p>When trying to boot grml-small[64] via PXE (network boot) using a
- CIFS share this will fail because grml-small[64] lacks cifs-utils.
- cifs-utils would consume >14MB of additional disk space - that's why
- it isn't part of the release. But there's a simple workaround: you can
- take the initrd and kernel from the regular grml flavour and use just
- the squashfs from grml-small[64].</p>
-
- <h3><a name="missingfiles"></a><a href="#toc">I noticed some files are missing on grml</a></h3>
-
- <p>Yes, output of 'debsums -a 1>/dev/null' might output some
- failures. The reason is pretty simple: some few modification have been
- done either because they are required for the provided environment or
- because of space limitiations on the ISO. The failures are nothing to
- really care about, but as we don't hide anything we thought it might be
- worth mentioning.</p>
-
- <h3><a name="bugreport"></a><a href="#toc">Bugreport</a></h3>
-
- <p>Searching for a bug? Want to report a bug? Take a look at the <a
- href="/bugs/">bugs webpage</a>.</p>
-
- <h2><a name="system"></a><a href="#toc">System</a></h2>
-
- <h3><a name="isolinux"></a><a href="#toc">Where's the old bootsplash?</a></h3>
-
- <p>Starting with release 2009.10 Grml provides a menu based bootsplash.
- To adjust boot options just press the TAB-key. To directly switch to the
- old-style isolinux cmdline just press the escape key within 30 seconds. If you
- still need access to the old bootsplash layout (including the f2, f3,...
- pages with further information regarding available bootoptions)
- select the entry 'Isolinux prompt' in the menu based bootsplash (just
- press 'i' and ENTER for direct access to it). The timeout until either
- the selected entry is booted (if specified) or until the system will
- restore from the cmdline to the menu based bootsplash is 30 seconds.</p>
-
- <h3><a name="configure"></a><a href="#toc">Which tools exist to configure grml?</a></h3>
-
- <p>Grml provides several scripts and tools which should make life
- easier. See 'dpkg -L grml-scripts' to get an overview of some main
- scripts. Run 'grml-config' to get a dialog interface for the most
- important scripts and tasks. Or just type 'grml-' and press tab-key to
- get a completion menu in the shell.</p>
-
- <h3><a name="password"></a><a href="#toc">What are the passwords of users on grml?</a></h3>
-
- <p>There are no default passwords - all accounts are locked by default
- for security reasons. Even local logins are not possible (unless you set
- a password or create new user accounts as root). You can create valid
- passwords using "sudo passwd [username]" from the shell
- individually.</p>
-
- <h3><a name="version"></a><a href="#toc">How do I find out the version of grml</a></h3>