Update -m 108x0 -a 3 function calls and update some GitHub issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -8,10 +8,10 @@ assignees: ''
 ---
 
 **GitHub is for bugs and features - not for support**
-For support, please use [the hashcat forums](https://hashcat.net/forum/)
+For support, please use the hashcat forums https://hashcat.net/forum/
 
 **Check the FAQ**
-Some items that might appear to be issues are not issues. Please review [the hashcat FAQ](https://hashcat.net/wiki/doku.php?id=frequently_asked_questions) before submitting a bug report.
+Some items that might appear to be issues are not issues. Please review the hashcat FAQ https://hashcat.net/wiki/doku.php?id=frequently_asked_questions before submitting a bug report.
 
 **Describe the bug**
 A clear and concise description of what the bug is.
@@ -31,7 +31,27 @@ A clear and concise description of what you expected to happen.
 **Hashcat version (please complete the following information):**
  - OS: [e.g. Linux]
  - Distribution: [e.g. Ubuntu 18.04]
- - Version [e.g. 6.2.0]
+ - Version: [e.g. 6.2.0]
+
+**Diagnostic output compute devices:**
+
+
+```
+For NV: Post nvidia-smi output. This tool also exist on Windows
+For AMD ROCm: Post rocm-smi and rocminfo output
+```
+
+```
+Post clinfo output
+```
+
+```
+Post hashcat -I output
+```
+
+```
+On Linux: post lspci output
+```
 
 **Additional context**
-Add any other context about the problem here.
+Add any other context about the problem here. For instance, it was working with hashcat version X.X.X (also please post output from older versions).

.github/ISSUE_TEMPLATE/new-hash-mode.md

@@ -1,6 +1,6 @@
 ---
-name: Add new hash-mode (-m)
-about: Add support for new algorithm
+name: Feature Request: Add new algorithm
+about: Add support for new hash-mode (-m)
 title: ''
 labels: new algorithm
 assignees: ''
@@ -13,9 +13,6 @@ For instance:
 - The password protection for the application XY was made by public by security researcher XY and there's a paper called ...
 - The cryptographic schema used in protocol XY can be found in the OSS code on it's GitHub repository.
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
-
 **Describe alternatives you've considered**
 A clear and concise description of any alternative solutions or features you've considered. For instance, other standalone crackers which already support this algorithm.