[openbeos] Some old tickets need someone to test on real hardware

I'm reading through many of the older tickets and have found a few
where the original reporter no longer has access to the equipment that
was used when the problem occurred.
If you have access to a Dell Latitude D810 maybe you can check up on
http://dev.haiku-os.org/ticket/1150, and provide a more detailed
feedback.
Do you have a PC with an intel extreme 855 chipset?  Maybe you can
followup on http://dev.haiku-os.org/ticket/1299.
If you have reported any troubles be sure to check back on them and
see if there's been any progress on them.
It's easy to search through them, check here: http://dev.haiku-os.org/query
I see kaoutsis rechecked 1135 and it's been fixed.

I see the wiki is back and has some notes on reporting bugs,
From: http://dev.haiku-os.org/wiki

Reporting bugs

Since our developers are unable to test every hardware combination,
nor every different way of interacting with the operating system, we
are relying on you to give us some input on how things work at your
end. Since this is a very early product, it is very likely that you
will encounter bugs. We thank you for taking the time to report these.
Since our time is limited, we need accurate information. Follow these
guidelines to create helpful bug reports:

   1. Before reporting a bug please make sure that it does not yet
exist. You can also use the search function for this.
   2. After you have established this is a unique bug, make your
information as accurate as possible:
         1. Include basic information such as how you are testing
Haiku (on real hardware, on VMWare, on QEMU, etc.).
         2. Mention which revision from SVN you are running. You can
find this out in the 'About Haiku' application, in the Deskbar menu.
         3. Describe the problem you are experiencing. Try to be as
accurate as you can: describe the actual behavior, and the behavior
you expected.
         4. Describe what steps to you need to perform in order to
expose the bug. This will help developers reproduce the bug.
         5. Attach as much information as you have. If it is a GUI
bug, or a bug in one of the applications, try to make a screen shot.
If it is a hardware problem, include a copy of the syslog file.
   3. After the bug has been reported, a developer will look at your
bug and try to classify it. Remember, we are all volunteers, and as
such, sometimes a bug report might go unanswered for a while. Adding
new information when it becomes available usually helps getting a bug
picked up quicker, but do not try to 'bump' the bug up by adding
non-descriptive comments.
   4. Remember, reporting a bug is not something you do spend a little
time on and then you are done. If you reported a bug, then you are
part of the Haiku development process. Developers might come up with
questions while they are trying to fix your bug. Stay around to answer
these. Consider your participation 'done' when the bug is marked as
'fixed'. Together we can improve Haiku, bit by bit.

--------------------------------------------------------------------------
Maybe we can add a page to the wiki for debugging tips, such as using
listdev and sysinfo to get system details.  How to setup serial debug
for those who have an extra PC and both systems have serial ports.
And I'm sure others have more tips they could add.
-scottmc

Other related posts: