Changes between Version 4 and Version 5 of ReportingBugs

Timestamp:

Aug 3, 2010, 8:10:46 AM (14 years ago)

Author:

humdinger

Comment:

changed path to /boot/common/var/log as that is easily navigatible with Tracker.

ReportingBugs

@@ -51 +51 @@
 === Syslog ===
 '''This is the preferred method for gaining information from a non-booting system.'''[[BR]]
-The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file `/var/log/syslog`. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).
+The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file `/boot/common/var/log/syslog`. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).
 
 The option ''Enable debug syslog'' in the boot loader's ''Debug menu'' makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu, e.g. by holding down the `Shift` key. In the boot loader's ''Debug menu'' you should now find the entries ''Display syslog from previous session'' and ''Save syslog from previous session''. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for writing the file to. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.
@@ -57 +57 @@
 === On Screen Debug Output ===
 '''The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.'''[[BR]]
-This is only relevant when Haiku fails to boot on your machine and the "Debug syslog option" doesn't work for some reason. Before the Haiku boot logo appears, press the `Shift` key to enter the boot loader menu. Select ''Select safe mode options''. Near the bottom, ''[ ] Enable on screen debug output'' will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.) Finally select ''Return to main menu'' and then ''continue booting''. One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. For more information on the [http://www.haiku-os.org/docs/userguide/en/bootloader.html Boot Loader].
+This is only relevant when Haiku fails to boot on your machine and the "Debug syslog option" doesn't work for some reason. Before the Haiku boot logo appears, press the `Shift` key to enter the boot loader menu. Select ''Select safe mode options''. Near the bottom, ''[ ] Enable on screen debug output'' will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.) Finally select ''Return to main menu'' and then ''continue booting''. One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the [http://www.haiku-os.org/docs/userguide/en/bootloader.html Boot Loader].
 
 === Hardware Issues ===