Changes between Version 1 and Version 2 of GoogleCodeInTaskTestHardware

Timestamp:

Nov 24, 2015, 5:58:51 PM (9 years ago)

Author:

humdinger

Comment:

Use BeSlySAT to gather info

GoogleCodeInTaskTestHardware

@@ -11 +11 @@
    2. Pick an "Anyboot" from the list of [http://download.haiku-os.org/nightly-images/x86_gcc2_hybrid/ Nightly Images] and create a Haiku USB stick or Haiku CD and boot from it. Select to "Install" and follow the [https://www.haiku-os.org/get-haiku/installation-guide Installation Guide].
 
-== Make note of the Hardware you are running on ==
+== Gathering hardware information ==
 
-For this testing you should take note of what hardware you are running it on, and keep track of any issues you find.  Check that Haiku boots, or doesn't.  If not, where did it get stuck.  What video chipset does it have?  Audio chipset, etc...  
+If you can boot successfully, install the [http://software.besly.de/ BeSly System Analysis Tool]:
+* Open a Terminal.
+* Add the BeSly repo by entering: {{{ pkgman add-repo http://software.besly.de/repo }}}
+* Install the tool with {{{ pkgman install beslysat }}}
 
-Discuss the results of your findings with a mentor.  If there are issues found you may end up opening new trac tickets.  We will want your syslog file and the output of listdev run in a terminal (listdev > myhardwarelist.txt).
+Start BeSlySAT and fill out the questionaire. Invoke "Database | Add Hardwaredata" and also "Database | Export As..." and attach the exported ZIP file to the GCI task.
 
-If it fails to boot, we may need screenshots or photos of your screen.  Try out the various boot menu options to see if turning off some features allows it to boot further than others.  To get to the boot menu, press and hold <LEFT SHIFT> during the boot process.
+If Haiku fails to boot, we may need screenshots or photos of your screen.  Try out the various boot menu options to see if turning off some features allows it to boot further than others.  To get to the boot menu, press and hold <LEFT SHIFT> during the boot process.
+
+Discuss the results of your findings with a mentor.  If there are issues found you may end up opening new trac tickets.