Gigabyte-GA-AX370-Gaming(rev1.0);Ryzen3_2200G

Since I can’t upload anything I’m pasting the yml file below. I use Qubes-4.0.4-rc1.


layout:
‘hcl’
type:
‘desktop’
hvm:
‘yes’
iommu:
‘yes’
slat:
‘yes’
tpm:
‘unknown’
remap:
‘yes’
brand: |
Gigabyte Technology Co., Ltd.
model: |
AX370-Gaming(rev1.0)
bios: |
F50d
cpu: |
AMD Ryzen 3 2200G with Radeon Vega Graphics
cpu-short: |
Ryzen 3 2200G
chipset: |
Advanced Micro Devices, Inc. [AMD] Device [1022:15d0]
chipset-short: |
AMD X370
gpu: |
Zotac GTX 1060 6GB RAM
gpu-short: |
GTX1060
network: |
Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
memory: |
16332
scsi: |
KINGSTON SA400S3 Rev: 61E1
usb: |
4
versions:

  • works:
    ‘yes’
    qubes: |
    R4.0.4-rc1
    xen: |
    4.8.5-25.fc25
    kernel: |
    5.8.16-1
    remark: |
    Fantastic
    credit: |
    Sagar Acharya
    link: |
    FIXLINK

Hi sagar,

thank you for the HCL, I added it to my next pull request. I’d like to
use your post as an opportunity to give a few pointers for reporters:

cpu-short:
just add the actual model here, e.g. Ryzen 3 2200G in this case

chipset-short:
for Intel chips we are looking for the code name (e.g. “Skylake”), in
case of AMD a simple “AMD” suffices … if you have trouble finding the
code name just leave the FIXME in place and I’ll fill it in before
sending the pull request to Andrew

gpu-short: often the user knows the name (obviously) or it’s already
detected by Linux. In some cases like this one, I have to go and check
devicehunt.com or a similar site to find the name. In this case it is:
GeForce GTX 1060

Filling in the above makes my job a little easier, but it’s not a big
deal if you are not sure or don’t know. I can take care of it. More
important is this…

  • works:
    …in the absence of any information, I am optimistically assuming the
    answer is ‘yes’. However it would really be great for the one submitting
    the report to choose. In case of partial, please provide details in the
    post / email.

remark:
… if you can say what needs to be said (other than “works” or “doesn’t
work at all”) in a sentence, then by all means do it here. Otherwise,
please be more specific in the post / email itself and I will then link
to it.

credit:
if you leave this on FIXME, I’ll use your username / email

link:
this one just leave alone, I’ll always set this to point to the original
post / email (and you can’t know the URL before posting).

Thanks!

Hey Sven, I’ve made the necessary changes. Thanks.

1 Like

Hi, @Sven. This is due to the fact that new users (trust level 0) cannot upload the .yml file. Jumping to trust level 1 is easy but it may be the case that the users have been on the forum for a while and decide to create an account for adding the report. Not sure how to best approach this. My guess is it won’t be very often.

This the template users see when writing their HCL Report post:

<!-- Find instructions on reporting HCL here:
https://www.qubes-os.org/doc/hcl/#generating-and-submitting-new-reports -->

## Remarks

<!-- Please include any useful information about any Qubes features you may have tested (see the legend below), as well as general machine compatibility (video, networking, sleep, etc.).-->


## Attachments

<!--Drag & drop here the generated HCL Info `.yml` file. Please consider attaching the HCL Support Files .cpio.gz file as well.-->


If you write some general tips like these, in a post, I can pin it so users see it always at the top of the category.