DebuggingRemovableDevices

Differences between revisions 11 and 12
⇤ ← Revision 11 as of 2006-01-17 14:47:44 →
Size: 1720
Editor: 195
Comment: udpate g-v-m debugging for current dapper
← Revision 12 as of 2006-04-10 23:54:59 → ⇥
Size: 1842
Editor: syndicate
Comment: add udevmonitor output
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
  `sudo udevmonitor -e | tee udev.log`
Line 14: Line 15:
 0. In Dapper press Control-C to stop the udevmonitor
Line 17: Line 19:
 0. attach `gvm.log`, `lshal.txt`, `devices.txt`, and `dmesg.txt` to the bug report  0. attach `gvm.log`, `lshal.txt`, `devices.txt`, `dmesg.txt` and `udev.log` (dapper only)
to the bug report

DebuggingRemovableDevices

When reporting a problem with removable devices, such as USB storage devices ("keys", hard drives, card readers, music players, digital cameras, etc.), please do the following steps:

  1. disconnect the device

  2. killall gnome-volume-manager

  3. In Warty, Hoary, Breezy:

    • gnome-volume-manager 2>&1 | tee gvm.log

    In Dapper:

    • gnome-volume-manager -n 2>&1 | tee gvm.log sudo udevmonitor -e | tee udev.log

  4. connect the device
  5. wait a few seconds
  6. Press Control-C to stop the foreground gnome-volume-manager
  7. In Dapper press Control-C to stop the udevmonitor

  8. lshal > lshal.txt

  9. dmesg > dmesg.txt

  10. ls -l /dev/sd* > devices.txt

  11. attach gvm.log, lshal.txt, devices.txt, dmesg.txt and udev.log (dapper only)

to the bug report

  1. restart your Gnome session to get a proper background g-v-m back

  2. paste the output of id into the bug report

  3. paste the output of id hal into the bug report

  4. paste the output of uname -a into the bug report

In easy cases this is everything that is needed. However, you might be asked for a "hal debug output"; please do the following steps to get it:

  1. disconnect the device

  2. sudo killall hald

  3. In Warty and Hoary:

    • sudo hald --drop-privileges --daemon=no --verbose=yes 2>&1 | tee hal.log

    In Breezy and Dapper:

    • sudo hald --daemon=no --verbose=yes 2>&1 | tee hal.log

  4. wait until the flood of messages settled
  5. connect the device
  6. wait again until no messages appear any more
  7. press Control-C to stop the foreground hal
  8. Restore the background hal:

    • sudo /etc/init.d/dbus-1 restart (in Warty and Hoary)

    • sudo /etc/dbus-1/event.d/20hal start (in Breezy and Dapper)

  9. attach hal.log to the bug report
  10. Restart your desktop session

DebuggingRemovableDevices (last edited 2011-01-07 14:06:15 by 67-42-160-182)