Collect Logs and System Information for Bug Reports

drakbug_report

This tool[51] can only be started and used on the command line.

It is advised to write the output of this command to a file, for instance by doing drakbug_report > drakbugreport.txt, but make sure you have enough disk space first: the file can easily be several GBs large.

Poznámka

The output is far too large to attach to a bug report without first removing the unneeded parts.

Tyto následující příkazy shromažďují informace o vašem systému:

  • lspci

  • pci_devices

  • dmidecode

  • fdisk

  • scsi

  • /sys/bus/scsi/devices

  • lsmod

  • cmdline

  • pcmcia: stab

  • usb

  • partitions

  • cpuinfo

  • syslog

  • Xorg.log

  • monitor_full_edid

  • stage1.log

  • ddebug.log

  • install.log

  • fstab

  • modprobe.conf

  • lilo.conf

  • grub: menu.lst

  • grub: install.sh

  • grub: device.map

  • xorg.conf

  • urpmi.cfg

  • modprobe.preload

  • sysconfig/i18n

  • /proc/iomem

  • /proc/ioport

  • mageia version

  • rpm -qa

  • df

Poznámka

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) journalctl -a > journalctl.txt. If you don't have a lot of diskspace, you can, for instance, take the last 5000 lines of the log instead with: journalctl -a | tail -n5000 > journalctl5000.txt.



[51] You can start this tool from the command line, by typing drakbug_report as root.


CC BY-SA 3.0
loading table of contents...