Changes between Version 1 and Version 2 of GoogleCodeInTaskTestHardware


Ignore:
Timestamp:
Nov 24, 2015 5:58:51 PM (4 years ago)
Author:
humdinger
Comment:

Use BeSlySAT to gather info

Legend:

Unmodified
Added
Removed
Modified
  • GoogleCodeInTaskTestHardware

    v1 v2  
    1111   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].
    1212
    13 == Make note of the Hardware you are running on ==
     13== Gathering hardware information ==
    1414
    15 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... 
     15If you can boot successfully, install the [http://software.besly.de/ BeSly System Analysis Tool]:
     16* Open a Terminal.
     17* Add the BeSly repo by entering: {{{ pkgman add-repo http://software.besly.de/repo }}}
     18* Install the tool with {{{ pkgman install beslysat }}}
    1619
    17 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).
     20Start 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.
    1821
    19 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.
     22If 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.
     23
     24Discuss the results of your findings with a mentor.  If there are issues found you may end up opening new trac tickets.