blob: e4fc98aac2fbb9a22ac3ef74776ff44dafb892b3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
<?xml version='1.0' encoding='utf-8'?><section
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:ns5="http://www.w3.org/1998/Math/MathML"
xmlns:ns4="http://www.w3.org/2000/svg"
xmlns:ns3="http://www.w3.org/1999/xhtml"
xmlns:ns="http://docbook.org/ns/docbook"
xml:id="drakbug_report" version="5.0">
<info>
<title xml:id="drakbug_report-ti1">Collect Logs and System Information
for Bug Reports</title><subtitle>drakbug_report</subtitle>
</info>
<para>This tool<footnote><para>You can start this tool from the command
line, by typing <emphasis role="bold">drakbug_report</emphasis> as
root.</para></footnote> can only be started and used on the command
line.</para>
<para>It is advised to write the output of this command to a file, for
instance by doing <emphasis role="bold">drakbug_report >
drakbugreport.txt</emphasis>, but make sure you have enough disk space
first: the file can easily be several GBs large.</para>
<note><para>The output is far too large to attach to a bug report without
first removing the unneeded parts.</para></note>
<para>This command collects the following information on your system:</para>
<itemizedlist>
<listitem><para> lspci</para></listitem>
<listitem><para> pci_devices</para></listitem>
<listitem><para> dmidecode</para></listitem>
<listitem><para> fdisk</para></listitem>
<listitem><para> scsi</para></listitem>
<listitem><para> /sys/bus/scsi/devices</para></listitem>
<listitem><para> lsmod</para></listitem>
<listitem><para> cmdline</para></listitem>
<listitem><para> pcmcia: stab</para></listitem>
<listitem><para> usb</para></listitem>
<listitem><para> partitions</para></listitem>
<listitem><para> cpuinfo</para></listitem>
<listitem><para> syslog</para></listitem>
<listitem><para> Xorg.log</para></listitem>
<listitem><para> monitor_full_edid</para></listitem>
<listitem><para> stage1.log</para></listitem>
<listitem><para> ddebug.log</para></listitem>
<listitem><para> install.log</para></listitem>
<listitem><para> fstab</para></listitem>
<listitem><para> modprobe.conf</para></listitem>
<listitem><para> lilo.conf</para></listitem>
<listitem><para> grub: menu.lst</para></listitem>
<listitem><para> grub: install.sh</para></listitem>
<listitem><para> grub: device.map</para></listitem>
<listitem><para> xorg.conf</para></listitem>
<listitem><para> urpmi.cfg</para></listitem>
<listitem><para> modprobe.preload</para></listitem>
<listitem><para> sysconfig/i18n</para></listitem>
<listitem><para> /proc/iomem</para></listitem>
<listitem><para> /proc/ioport</para></listitem>
<listitem><para> mageia version</para></listitem>
<listitem><para> rpm -qa</para></listitem>
<listitem><para> df</para></listitem>
</itemizedlist>
<note><para>At the time this help page was written, the "syslog" part of
this command's output was empty, because this tool had not yet been
adjusted to our switch to systemd. If it is still empty, you can
retrieve the "syslog" by doing (as root) <emphasis role="bold">
journalctl -a > journalctl.txt</emphasis>. If you don't have a lot of
diskspace, you can, for instance, take the last 5000 lines of the log
instead with: <emphasis role="bold">journalctl -a | tail -n5000 >
journalctl5000.txt</emphasis>.</para></note>
</section>
|
