XBMC crash after selecting “play”. Ubuntu 14.04 and 13.0 gotham. Link to crashlog

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

2

I have a brand new machine with fresh install of Ubuntu 14.04 and I’m trying to run Gotham 13.0 on it. I’ve already added the restricted multimedia codecs (just in case) to Ubuntu.

 sudo apt-get install ubuntu-restricted-extras

As well as Unrestricted LibavCodec

sudo apt-get install libavcodec-extra

My graphics is AMD/ATI Tahiti (Radeon HD 7970) with a core i7.

Here’s the XBMC crashlog: http://xbmclogs.com/show.php?id=209365

Here’s what’s happening: I just download the appropriate PPA’s etc. through the XBMC wiki.

sudo add-apt-repository ppa:team-xbmc

sudo apt-get update

sudo apt-get install xbmc

The first time I installed it on this machine, I went through installed Fusion and ran the Hub wizard Template/Setup. Everythings seems good,
but when I select Al Jazeera, for example, I click “watch live”, and then I get the “working” scroll in the bottom right for few seconds, and then the entire program force closes. The same happens with ” The Daily Show” “Youtube” “UsTv Now” etc.
I completly uninstalled XBMC

sudo apt-get purge xbmc xbmc-standalone

and started over. This time only installing one add on and trying it out. Still I get the same results. The music add-ons work though. I have this posted a few days on XBMC forums, and no replies yet. I’m not sure if this is an Ubuntu or XBMC issue ,at this point.
enter image description here

share|improve this question

  • Did you look out if there are bugs about this?

    – Braiam
    May 26 ’14 at 15:48

  • I’m finding bug reports for screen tearing, but I haven’t gotten to that point yet. I can’t find any reports for crash on streaming start up.

    – 5th Wheel
    May 26 ’14 at 17:45

2

I have a brand new machine with fresh install of Ubuntu 14.04 and I’m trying to run Gotham 13.0 on it. I’ve already added the restricted multimedia codecs (just in case) to Ubuntu.

 sudo apt-get install ubuntu-restricted-extras

As well as Unrestricted LibavCodec

sudo apt-get install libavcodec-extra

My graphics is AMD/ATI Tahiti (Radeon HD 7970) with a core i7.

Here’s the XBMC crashlog: http://xbmclogs.com/show.php?id=209365

Here’s what’s happening: I just download the appropriate PPA’s etc. through the XBMC wiki.

sudo add-apt-repository ppa:team-xbmc

sudo apt-get update

sudo apt-get install xbmc

The first time I installed it on this machine, I went through installed Fusion and ran the Hub wizard Template/Setup. Everythings seems good,
but when I select Al Jazeera, for example, I click “watch live”, and then I get the “working” scroll in the bottom right for few seconds, and then the entire program force closes. The same happens with ” The Daily Show” “Youtube” “UsTv Now” etc.
I completly uninstalled XBMC

sudo apt-get purge xbmc xbmc-standalone

and started over. This time only installing one add on and trying it out. Still I get the same results. The music add-ons work though. I have this posted a few days on XBMC forums, and no replies yet. I’m not sure if this is an Ubuntu or XBMC issue ,at this point.
enter image description here

share|improve this question

  • Did you look out if there are bugs about this?

    – Braiam
    May 26 ’14 at 15:48

  • I’m finding bug reports for screen tearing, but I haven’t gotten to that point yet. I can’t find any reports for crash on streaming start up.

    – 5th Wheel
    May 26 ’14 at 17:45

2

2

2

I have a brand new machine with fresh install of Ubuntu 14.04 and I’m trying to run Gotham 13.0 on it. I’ve already added the restricted multimedia codecs (just in case) to Ubuntu.

 sudo apt-get install ubuntu-restricted-extras

As well as Unrestricted LibavCodec

sudo apt-get install libavcodec-extra

My graphics is AMD/ATI Tahiti (Radeon HD 7970) with a core i7.

Here’s the XBMC crashlog: http://xbmclogs.com/show.php?id=209365

Here’s what’s happening: I just download the appropriate PPA’s etc. through the XBMC wiki.

sudo add-apt-repository ppa:team-xbmc

sudo apt-get update

sudo apt-get install xbmc

The first time I installed it on this machine, I went through installed Fusion and ran the Hub wizard Template/Setup. Everythings seems good,
but when I select Al Jazeera, for example, I click “watch live”, and then I get the “working” scroll in the bottom right for few seconds, and then the entire program force closes. The same happens with ” The Daily Show” “Youtube” “UsTv Now” etc.
I completly uninstalled XBMC

sudo apt-get purge xbmc xbmc-standalone

and started over. This time only installing one add on and trying it out. Still I get the same results. The music add-ons work though. I have this posted a few days on XBMC forums, and no replies yet. I’m not sure if this is an Ubuntu or XBMC issue ,at this point.
enter image description here

share|improve this question

I have a brand new machine with fresh install of Ubuntu 14.04 and I’m trying to run Gotham 13.0 on it. I’ve already added the restricted multimedia codecs (just in case) to Ubuntu.

 sudo apt-get install ubuntu-restricted-extras

As well as Unrestricted LibavCodec

sudo apt-get install libavcodec-extra

My graphics is AMD/ATI Tahiti (Radeon HD 7970) with a core i7.

Here’s the XBMC crashlog: http://xbmclogs.com/show.php?id=209365

Here’s what’s happening: I just download the appropriate PPA’s etc. through the XBMC wiki.

sudo add-apt-repository ppa:team-xbmc

sudo apt-get update

sudo apt-get install xbmc

The first time I installed it on this machine, I went through installed Fusion and ran the Hub wizard Template/Setup. Everythings seems good,
but when I select Al Jazeera, for example, I click “watch live”, and then I get the “working” scroll in the bottom right for few seconds, and then the entire program force closes. The same happens with ” The Daily Show” “Youtube” “UsTv Now” etc.
I completly uninstalled XBMC

sudo apt-get purge xbmc xbmc-standalone

and started over. This time only installing one add on and trying it out. Still I get the same results. The music add-ons work though. I have this posted a few days on XBMC forums, and no replies yet. I’m not sure if this is an Ubuntu or XBMC issue ,at this point.
enter image description here

ubuntu drivers radeon amd xbmc

share|improve this question

share|improve this question

share|improve this question

share|improve this question

asked May 26 ’14 at 15:43

5th Wheel5th Wheel

13317

13317

  • Did you look out if there are bugs about this?

    – Braiam
    May 26 ’14 at 15:48

  • I’m finding bug reports for screen tearing, but I haven’t gotten to that point yet. I can’t find any reports for crash on streaming start up.

    – 5th Wheel
    May 26 ’14 at 17:45

  • Did you look out if there are bugs about this?

    – Braiam
    May 26 ’14 at 15:48

  • I’m finding bug reports for screen tearing, but I haven’t gotten to that point yet. I can’t find any reports for crash on streaming start up.

    – 5th Wheel
    May 26 ’14 at 17:45

Did you look out if there are bugs about this?

– Braiam
May 26 ’14 at 15:48

Did you look out if there are bugs about this?

– Braiam
May 26 ’14 at 15:48

I’m finding bug reports for screen tearing, but I haven’t gotten to that point yet. I can’t find any reports for crash on streaming start up.

– 5th Wheel
May 26 ’14 at 17:45

I’m finding bug reports for screen tearing, but I haven’t gotten to that point yet. I can’t find any reports for crash on streaming start up.

– 5th Wheel
May 26 ’14 at 17:45

1 Answer
1

active

oldest

votes

0

It’s a driver issue, install the new omega drivers, that solved the problem for me and I run a dual hd7970 and had the same issue until the driver update, so its the ability of the driver not the card its self and trust me this will solve the issue and will also allow you to do more with your card.

share|improve this answer

    Your Answer

    StackExchange.ready(function() {
    var channelOptions = {
    tags: “”.split(” “),
    id: “106”
    };
    initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

    StackExchange.using(“externalEditor”, function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using(“snippets”, function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: ‘answer’,
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: “”,
    imageUploader: {
    brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
    contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
    allowUrls: true
    },
    onDemand: true,
    discardSelector: “.discard-answer”
    ,immediatelyShowMarkdownHelp:true
    });

    }
    });

    draft saved
    draft discarded

    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f132050%2fxbmc-crash-after-selecting-play-ubuntu-14-04-and-13-0-gotham-link-to-crashlo%23new-answer’, ‘question_page’);
    }
    );

    Post as a guest

    Required, but never shown

    1 Answer
    1

    active

    oldest

    votes

    1 Answer
    1

    active

    oldest

    votes

    active

    oldest

    votes

    active

    oldest

    votes

    0

    It’s a driver issue, install the new omega drivers, that solved the problem for me and I run a dual hd7970 and had the same issue until the driver update, so its the ability of the driver not the card its self and trust me this will solve the issue and will also allow you to do more with your card.

    share|improve this answer

      0

      It’s a driver issue, install the new omega drivers, that solved the problem for me and I run a dual hd7970 and had the same issue until the driver update, so its the ability of the driver not the card its self and trust me this will solve the issue and will also allow you to do more with your card.

      share|improve this answer

        0

        0

        0

        It’s a driver issue, install the new omega drivers, that solved the problem for me and I run a dual hd7970 and had the same issue until the driver update, so its the ability of the driver not the card its self and trust me this will solve the issue and will also allow you to do more with your card.

        share|improve this answer

        It’s a driver issue, install the new omega drivers, that solved the problem for me and I run a dual hd7970 and had the same issue until the driver update, so its the ability of the driver not the card its self and trust me this will solve the issue and will also allow you to do more with your card.

        share|improve this answer

        share|improve this answer

        share|improve this answer

        edited Dec 17 ’14 at 12:11

        Raphael Ahrens

        7,01152846

        7,01152846

        answered Dec 17 ’14 at 11:44

        jasonjason

        1

        1

            draft saved
            draft discarded

            Thanks for contributing an answer to Unix & Linux Stack Exchange!

            • Please be sure to answer the question. Provide details and share your research!

            But avoid

            • Asking for help, clarification, or responding to other answers.
            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.

            draft saved

            draft discarded

            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f132050%2fxbmc-crash-after-selecting-play-ubuntu-14-04-and-13-0-gotham-link-to-crashlo%23new-answer’, ‘question_page’);
            }
            );

            Post as a guest

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            How to enable Virtualization AMD-V Aspire one AO725 from BIOS or otherwise

            The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

            2

            I’m try to use the virtualbox to virtualize a 64-bit system but the error that I get is:

            La aceleración VT-x/AMD-V ha sido habilitada, pero no es funcional. Su sistema invitado de 64-bit fallára al detectar una CPU de 64-bit y no podrá arrancar.
            Compruebe que VT-x/AMD-V están habilitadas en la BIOS de su computadora anfitrión.
            

            For the ones not knowing Spanish, google translate gives:

            VT-x/AMD-V acceleration has been enabled but is not functional. 
            Its system of 64-bit guest will fail to detect a 64-bit CPU and will not boot.
            Check VT-x/AMD-V are enabled in the BIOS of your host computer.
            

            I’ve checked the AMD V CPU Virtualization Extensions with the following command:

            grep --color svm /proc/cpuinfo
            

            The output is:

            flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
                     pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
                     rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid perfmperf
                     pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic
                     cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt arat cpb
                     hw_pstate npt lbrv svm_lock nrip_save pausefilter
            flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
                     pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
                     rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
                     aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm
                     extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt
                     arat cpb hw_pstate npt lbrv svm_lock nrip_save pausefilter
            

            Running the command lscpu

            Architecture:          x86_64
            CPU op-mode(s):        32-bit, 64-bit
            Byte Order:            Little Endian
            CPU(s):                2
            On-line CPU(s) list:   0,1
            Thread(s) per core:    1
            Core(s) per socket:    2
            Socket(s):             1
            NUMA node(s):          1
            Vendor ID:             AuthenticAMD
            CPU family:            20
            Model:                 2
            Stepping:              0
            CPU MHz:               800.000
            BogoMIPS:              1996.36
            Virtualization:        AMD-V
            L1d cache:             32K
            L1i cache:             32K
            L2 cache:              512K
            NUMA node0 CPU(s):     0,1
            

            Update

            Run the command:

            grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
            

            the output is:

            flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm 
            flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm 
            

            so, It’s possible fixed it’s from the bios or otherwise.

            How to fix the mistake? Is it possible at all?

            share|improve this question

              2

              I’m try to use the virtualbox to virtualize a 64-bit system but the error that I get is:

              La aceleración VT-x/AMD-V ha sido habilitada, pero no es funcional. Su sistema invitado de 64-bit fallára al detectar una CPU de 64-bit y no podrá arrancar.
              Compruebe que VT-x/AMD-V están habilitadas en la BIOS de su computadora anfitrión.
              

              For the ones not knowing Spanish, google translate gives:

              VT-x/AMD-V acceleration has been enabled but is not functional. 
              Its system of 64-bit guest will fail to detect a 64-bit CPU and will not boot.
              Check VT-x/AMD-V are enabled in the BIOS of your host computer.
              

              I’ve checked the AMD V CPU Virtualization Extensions with the following command:

              grep --color svm /proc/cpuinfo
              

              The output is:

              flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
                       pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
                       rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid perfmperf
                       pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic
                       cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt arat cpb
                       hw_pstate npt lbrv svm_lock nrip_save pausefilter
              flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
                       pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
                       rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
                       aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm
                       extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt
                       arat cpb hw_pstate npt lbrv svm_lock nrip_save pausefilter
              

              Running the command lscpu

              Architecture:          x86_64
              CPU op-mode(s):        32-bit, 64-bit
              Byte Order:            Little Endian
              CPU(s):                2
              On-line CPU(s) list:   0,1
              Thread(s) per core:    1
              Core(s) per socket:    2
              Socket(s):             1
              NUMA node(s):          1
              Vendor ID:             AuthenticAMD
              CPU family:            20
              Model:                 2
              Stepping:              0
              CPU MHz:               800.000
              BogoMIPS:              1996.36
              Virtualization:        AMD-V
              L1d cache:             32K
              L1i cache:             32K
              L2 cache:              512K
              NUMA node0 CPU(s):     0,1
              

              Update

              Run the command:

              grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
              

              the output is:

              flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm 
              flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm 
              

              so, It’s possible fixed it’s from the bios or otherwise.

              How to fix the mistake? Is it possible at all?

              share|improve this question

                2

                2

                2

                1

                I’m try to use the virtualbox to virtualize a 64-bit system but the error that I get is:

                La aceleración VT-x/AMD-V ha sido habilitada, pero no es funcional. Su sistema invitado de 64-bit fallára al detectar una CPU de 64-bit y no podrá arrancar.
                Compruebe que VT-x/AMD-V están habilitadas en la BIOS de su computadora anfitrión.
                

                For the ones not knowing Spanish, google translate gives:

                VT-x/AMD-V acceleration has been enabled but is not functional. 
                Its system of 64-bit guest will fail to detect a 64-bit CPU and will not boot.
                Check VT-x/AMD-V are enabled in the BIOS of your host computer.
                

                I’ve checked the AMD V CPU Virtualization Extensions with the following command:

                grep --color svm /proc/cpuinfo
                

                The output is:

                flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
                         pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
                         rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid perfmperf
                         pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic
                         cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt arat cpb
                         hw_pstate npt lbrv svm_lock nrip_save pausefilter
                flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
                         pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
                         rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
                         aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm
                         extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt
                         arat cpb hw_pstate npt lbrv svm_lock nrip_save pausefilter
                

                Running the command lscpu

                Architecture:          x86_64
                CPU op-mode(s):        32-bit, 64-bit
                Byte Order:            Little Endian
                CPU(s):                2
                On-line CPU(s) list:   0,1
                Thread(s) per core:    1
                Core(s) per socket:    2
                Socket(s):             1
                NUMA node(s):          1
                Vendor ID:             AuthenticAMD
                CPU family:            20
                Model:                 2
                Stepping:              0
                CPU MHz:               800.000
                BogoMIPS:              1996.36
                Virtualization:        AMD-V
                L1d cache:             32K
                L1i cache:             32K
                L2 cache:              512K
                NUMA node0 CPU(s):     0,1
                

                Update

                Run the command:

                grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
                

                the output is:

                flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm 
                flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm 
                

                so, It’s possible fixed it’s from the bios or otherwise.

                How to fix the mistake? Is it possible at all?

                share|improve this question

                I’m try to use the virtualbox to virtualize a 64-bit system but the error that I get is:

                La aceleración VT-x/AMD-V ha sido habilitada, pero no es funcional. Su sistema invitado de 64-bit fallára al detectar una CPU de 64-bit y no podrá arrancar.
                Compruebe que VT-x/AMD-V están habilitadas en la BIOS de su computadora anfitrión.
                

                For the ones not knowing Spanish, google translate gives:

                VT-x/AMD-V acceleration has been enabled but is not functional. 
                Its system of 64-bit guest will fail to detect a 64-bit CPU and will not boot.
                Check VT-x/AMD-V are enabled in the BIOS of your host computer.
                

                I’ve checked the AMD V CPU Virtualization Extensions with the following command:

                grep --color svm /proc/cpuinfo
                

                The output is:

                flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
                         pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
                         rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid perfmperf
                         pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic
                         cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt arat cpb
                         hw_pstate npt lbrv svm_lock nrip_save pausefilter
                flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
                         pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
                         rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
                         aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm
                         extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt
                         arat cpb hw_pstate npt lbrv svm_lock nrip_save pausefilter
                

                Running the command lscpu

                Architecture:          x86_64
                CPU op-mode(s):        32-bit, 64-bit
                Byte Order:            Little Endian
                CPU(s):                2
                On-line CPU(s) list:   0,1
                Thread(s) per core:    1
                Core(s) per socket:    2
                Socket(s):             1
                NUMA node(s):          1
                Vendor ID:             AuthenticAMD
                CPU family:            20
                Model:                 2
                Stepping:              0
                CPU MHz:               800.000
                BogoMIPS:              1996.36
                Virtualization:        AMD-V
                L1d cache:             32K
                L1i cache:             32K
                L2 cache:              512K
                NUMA node0 CPU(s):     0,1
                

                Update

                Run the command:

                grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
                

                the output is:

                flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm 
                flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm 
                

                so, It’s possible fixed it’s from the bios or otherwise.

                How to fix the mistake? Is it possible at all?

                virtualbox virtual-machine bios amd

                share|improve this question

                share|improve this question

                share|improve this question

                share|improve this question

                edited Jan 17 at 15:33

                Dzamo Norton

                1488

                1488

                asked May 2 ’13 at 1:13

                Cristian Chaparro A.Cristian Chaparro A.

                2061410

                2061410

                    2 Answers
                    2

                    active

                    oldest

                    votes

                    1

                    The output from lscpu indicates what the CPU is capable of doing, not necessarily that this is enabled in the BIOS or that you go into the BIOS and can configure it.

                    The bios manual of the machine does not have any indication that you can set this, but normally browsing through the limited number of CPU options in your BIOS will show you if you can.

                    If you cannot find it and you probably have to go for the UEFI capable upgrade of your BIOS provided by Acer which enables (in UEFI mode) the AMD-V. That most likely will require a reinstallation of your host system.

                    An alternative is try and install ZHGBIOS.FD from BIOS version 1.05 download at the ACER website, there is supposedly an option to set ZSM under Power -> Advanced CPU Control.

                    If you have not done BIOS upgrades before and/or if this is the only machine you have to get to the Internet in case things go wrong, I cannot recommend either of these options.

                    share|improve this answer

                      1

                      Included procedure for both Intel and AMD as if anyone is on either. Also included some information that you know like grep for svm – for completeness sake.

                      Checking support

                      Check if visualization is available

                      • Intel check if vmx is found (VT-x)

                        grep -o "^flagss*:.*svmx(s|$)" /proc/cpuinfo
                        
                      • AMD check if svm is found (AMD-V)

                        grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
                        

                      If not found, one are most likely out of luck.

                      One can also check flags from BIOS by dmidecode

                      dmidecode --type 4 | grep -i virt
                      VME (Virtual mode extension)        # On a specific i386
                      

                      Checking status – require root privileges

                      Read the machine/model specific registers (MSR), (man msr), using msr-tools
                      if not enabled (read fails) load msr by:

                      modprobe msr
                      

                      Then use rdmsr, (quick intoduction) to read processor MSR’s.


                      Intel

                      For Intel processors one can check current status by reading IA32_FEATURE_CONTROL(1) from the processor.

                      The IA32_FEATURE_CONTROL MSR (at address 03AH) provides feature control bits
                      that configure operation of VMX and SMX.

                      Execute commands:

                      rdmsr -f 0:0 0x3a # Read bit-field 0 (Lock-bit)
                      rdmsr -f 2:2 0x3a # Read bit-field 2 (Enable VMX outside SMX operation)
                      

                      These commands should give:

                      0:0 2:2
                        0      ENABLED  (Not 100% sure about this one, `kvm-ok` reports VMX
                                         as enabled when 0 – perhaps meant as modifiable.)
                        1   1  ENABLED
                        1   0  DISABLED 
                      

                      Bit 2 enables VMX outside SMX operation. If this bit is clear, an attempt to execute VMXON will cause a general-
                      protection exception if executed outside SMX operation. Attempts to set this bit on logical processors that do
                      not support VMX operation cause general-protection exceptions.

                      (1) Intel® 64 and IA-32 Architectures Software Developer’s Manual Vol. 2C 5-1 pp 1072.


                      AMD

                      Read Extended Feature Enable Register (EFER)(2) pp. 55, 103 in PDF
                      where bit 12 is “Secure Virtual Machine Enable” (SVME) which indicate whether
                      hardware virtualization is enabled.

                      Execute command:

                      rdmsr -f 12:12 0xc0000080 # If set (1), SVME is enabled.
                      

                      Secure Virtual Machine Enable (SVME) Bit. Bit 12, read/write. Enables the SVM extensions.
                      When this bit is zero, the SVM instructions cause #UD exceptions. EFER.SVME defaults to a reset
                      value of zero. The effect of turning off EFER.SVME while a guest is running is undefined; therefore,
                      the VMM should always prevent guests from writing EFER. SVM extensions can be disabled by
                      setting VM_CR.SVME_DISABLE.

                      To check if it is disabled for session check VM_CR.SVME_DISABLE(2) pp 57, 504 (105, 552 in PDF)

                      Execute command:

                      rdmsr -f 4:4 0xc0010114 # If set (1), it is disabled.
                      

                      as in: you would have to enable in BIOS.

                      SVMDIS — Bit 4. When this bit is set, writes to EFER treat the SVME bit as MBZ. When this bit is
                      clear, EFER.SVME can be written normally. This bit does not prevent CPUID from reporting that
                      SVM is available. Setting SVMDIS while EFER.SVME is 1 generates a #GP fault, regardless of
                      the current state of VM_CR.LOCK. This bit is not affected by SKINIT. It is cleared by INIT when
                      LOCK is cleared to 0; otherwise, it is not affected.

                      (2)AMD64 Architecture Programmer’s Manual, Volume 2: System Programming.


                      KVM

                      If KVM modules are loaded you’ll need to remove them by:

                      sudo modprobe -r kvm_intel
                      sudo modprobe -r kvm_amd 
                      

                      for Intel and AMD respectively as they clash with Virtual Box. Ref.


                      Enabling

                      For your specific model I guess @Anthon has said plenty.

                      As he mention, by using UEFI you most likely would have to reinstall your host system. Other risks by upgrading BIOS is a lot of things where a few
                      could be:

                      • New BIOS could trigger latent bugs in hardware.
                      • The flash of BIOS could crash due to software corruption etc.
                      • One could have downloaded wrong BIOS (for a different model).
                      • Computer could crash, loose power in the mids of flash. (AKA freak accident).
                      • N^x unknown factors could play in.
                      • etc.

                      If flash crashes it could render your PC completely unbootable and a fix could
                      prove to be hard. (You can’t i.e. boot and fix BIOS.)

                      You should have a backup of current BIOS and a USB rescue stick.

                      Search the web, e.g. look at this. Check if your model has “built-in BIOS recovery routine” as mentioned in last post on that page. (As you can see
                      even that can give trouble).

                      And yes, again as mentioned by Anthon. If you do not have any other PC easily
                      accessible for web-search in case of failure, it is far from recommended.


                      If you are willing to hack, risk unknown repercussions etc. you can try to use
                      a “unofficial BIOS version”. This thread at BOIS-Mods have both
                      software and a general discussion. Would read entire thread thoroughly and
                      ask if any questions.

                      Depending on your level of interest, time, and knowledge you could also try
                      to hack this on your own 😉

                      SVM enable

                      share|improve this answer

                      • so, run the command grep -wo "^flagss*:.*(vmx|svm)" /proc/cpuinfo not found nothing, So definitely not possible, right @Sukminder. But if I try to do the hack the way that @Anthon says, What is the worst that can happen?.

                        – Cristian Chaparro A.
                        May 3 ’13 at 1:42

                      • @CristianChaparroA.: Ah. no, extremely sorry. Forgot to update the grep line. Was meaning to update it. From the output you posted you have svm. Else I have updated the answer with some more bla bla. 😉

                        – Runium
                        May 3 ’13 at 5:32

                      Your Answer

                      StackExchange.ready(function() {
                      var channelOptions = {
                      tags: “”.split(” “),
                      id: “106”
                      };
                      initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                      StackExchange.using(“externalEditor”, function() {
                      // Have to fire editor after snippets, if snippets enabled
                      if (StackExchange.settings.snippets.snippetsEnabled) {
                      StackExchange.using(“snippets”, function() {
                      createEditor();
                      });
                      }
                      else {
                      createEditor();
                      }
                      });

                      function createEditor() {
                      StackExchange.prepareEditor({
                      heartbeatType: ‘answer’,
                      autoActivateHeartbeat: false,
                      convertImagesToLinks: false,
                      noModals: true,
                      showLowRepImageUploadWarning: true,
                      reputationToPostImages: null,
                      bindNavPrevention: true,
                      postfix: “”,
                      imageUploader: {
                      brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                      contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                      allowUrls: true
                      },
                      onDemand: true,
                      discardSelector: “.discard-answer”
                      ,immediatelyShowMarkdownHelp:true
                      });

                      }
                      });

                      draft saved
                      draft discarded

                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f74376%2fhow-to-enable-virtualization-amd-v-aspire-one-ao725-from-bios-or-otherwise%23new-answer’, ‘question_page’);
                      }
                      );

                      Post as a guest

                      Required, but never shown

                      2 Answers
                      2

                      active

                      oldest

                      votes

                      2 Answers
                      2

                      active

                      oldest

                      votes

                      active

                      oldest

                      votes

                      active

                      oldest

                      votes

                      1

                      The output from lscpu indicates what the CPU is capable of doing, not necessarily that this is enabled in the BIOS or that you go into the BIOS and can configure it.

                      The bios manual of the machine does not have any indication that you can set this, but normally browsing through the limited number of CPU options in your BIOS will show you if you can.

                      If you cannot find it and you probably have to go for the UEFI capable upgrade of your BIOS provided by Acer which enables (in UEFI mode) the AMD-V. That most likely will require a reinstallation of your host system.

                      An alternative is try and install ZHGBIOS.FD from BIOS version 1.05 download at the ACER website, there is supposedly an option to set ZSM under Power -> Advanced CPU Control.

                      If you have not done BIOS upgrades before and/or if this is the only machine you have to get to the Internet in case things go wrong, I cannot recommend either of these options.

                      share|improve this answer

                        1

                        The output from lscpu indicates what the CPU is capable of doing, not necessarily that this is enabled in the BIOS or that you go into the BIOS and can configure it.

                        The bios manual of the machine does not have any indication that you can set this, but normally browsing through the limited number of CPU options in your BIOS will show you if you can.

                        If you cannot find it and you probably have to go for the UEFI capable upgrade of your BIOS provided by Acer which enables (in UEFI mode) the AMD-V. That most likely will require a reinstallation of your host system.

                        An alternative is try and install ZHGBIOS.FD from BIOS version 1.05 download at the ACER website, there is supposedly an option to set ZSM under Power -> Advanced CPU Control.

                        If you have not done BIOS upgrades before and/or if this is the only machine you have to get to the Internet in case things go wrong, I cannot recommend either of these options.

                        share|improve this answer

                          1

                          1

                          1

                          The output from lscpu indicates what the CPU is capable of doing, not necessarily that this is enabled in the BIOS or that you go into the BIOS and can configure it.

                          The bios manual of the machine does not have any indication that you can set this, but normally browsing through the limited number of CPU options in your BIOS will show you if you can.

                          If you cannot find it and you probably have to go for the UEFI capable upgrade of your BIOS provided by Acer which enables (in UEFI mode) the AMD-V. That most likely will require a reinstallation of your host system.

                          An alternative is try and install ZHGBIOS.FD from BIOS version 1.05 download at the ACER website, there is supposedly an option to set ZSM under Power -> Advanced CPU Control.

                          If you have not done BIOS upgrades before and/or if this is the only machine you have to get to the Internet in case things go wrong, I cannot recommend either of these options.

                          share|improve this answer

                          The output from lscpu indicates what the CPU is capable of doing, not necessarily that this is enabled in the BIOS or that you go into the BIOS and can configure it.

                          The bios manual of the machine does not have any indication that you can set this, but normally browsing through the limited number of CPU options in your BIOS will show you if you can.

                          If you cannot find it and you probably have to go for the UEFI capable upgrade of your BIOS provided by Acer which enables (in UEFI mode) the AMD-V. That most likely will require a reinstallation of your host system.

                          An alternative is try and install ZHGBIOS.FD from BIOS version 1.05 download at the ACER website, there is supposedly an option to set ZSM under Power -> Advanced CPU Control.

                          If you have not done BIOS upgrades before and/or if this is the only machine you have to get to the Internet in case things go wrong, I cannot recommend either of these options.

                          share|improve this answer

                          share|improve this answer

                          share|improve this answer

                          answered May 2 ’13 at 2:55

                          AnthonAnthon

                          60.7k17102166

                          60.7k17102166

                              1

                              Included procedure for both Intel and AMD as if anyone is on either. Also included some information that you know like grep for svm – for completeness sake.

                              Checking support

                              Check if visualization is available

                              • Intel check if vmx is found (VT-x)

                                grep -o "^flagss*:.*svmx(s|$)" /proc/cpuinfo
                                
                              • AMD check if svm is found (AMD-V)

                                grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
                                

                              If not found, one are most likely out of luck.

                              One can also check flags from BIOS by dmidecode

                              dmidecode --type 4 | grep -i virt
                              VME (Virtual mode extension)        # On a specific i386
                              

                              Checking status – require root privileges

                              Read the machine/model specific registers (MSR), (man msr), using msr-tools
                              if not enabled (read fails) load msr by:

                              modprobe msr
                              

                              Then use rdmsr, (quick intoduction) to read processor MSR’s.


                              Intel

                              For Intel processors one can check current status by reading IA32_FEATURE_CONTROL(1) from the processor.

                              The IA32_FEATURE_CONTROL MSR (at address 03AH) provides feature control bits
                              that configure operation of VMX and SMX.

                              Execute commands:

                              rdmsr -f 0:0 0x3a # Read bit-field 0 (Lock-bit)
                              rdmsr -f 2:2 0x3a # Read bit-field 2 (Enable VMX outside SMX operation)
                              

                              These commands should give:

                              0:0 2:2
                                0      ENABLED  (Not 100% sure about this one, `kvm-ok` reports VMX
                                                 as enabled when 0 – perhaps meant as modifiable.)
                                1   1  ENABLED
                                1   0  DISABLED 
                              

                              Bit 2 enables VMX outside SMX operation. If this bit is clear, an attempt to execute VMXON will cause a general-
                              protection exception if executed outside SMX operation. Attempts to set this bit on logical processors that do
                              not support VMX operation cause general-protection exceptions.

                              (1) Intel® 64 and IA-32 Architectures Software Developer’s Manual Vol. 2C 5-1 pp 1072.


                              AMD

                              Read Extended Feature Enable Register (EFER)(2) pp. 55, 103 in PDF
                              where bit 12 is “Secure Virtual Machine Enable” (SVME) which indicate whether
                              hardware virtualization is enabled.

                              Execute command:

                              rdmsr -f 12:12 0xc0000080 # If set (1), SVME is enabled.
                              

                              Secure Virtual Machine Enable (SVME) Bit. Bit 12, read/write. Enables the SVM extensions.
                              When this bit is zero, the SVM instructions cause #UD exceptions. EFER.SVME defaults to a reset
                              value of zero. The effect of turning off EFER.SVME while a guest is running is undefined; therefore,
                              the VMM should always prevent guests from writing EFER. SVM extensions can be disabled by
                              setting VM_CR.SVME_DISABLE.

                              To check if it is disabled for session check VM_CR.SVME_DISABLE(2) pp 57, 504 (105, 552 in PDF)

                              Execute command:

                              rdmsr -f 4:4 0xc0010114 # If set (1), it is disabled.
                              

                              as in: you would have to enable in BIOS.

                              SVMDIS — Bit 4. When this bit is set, writes to EFER treat the SVME bit as MBZ. When this bit is
                              clear, EFER.SVME can be written normally. This bit does not prevent CPUID from reporting that
                              SVM is available. Setting SVMDIS while EFER.SVME is 1 generates a #GP fault, regardless of
                              the current state of VM_CR.LOCK. This bit is not affected by SKINIT. It is cleared by INIT when
                              LOCK is cleared to 0; otherwise, it is not affected.

                              (2)AMD64 Architecture Programmer’s Manual, Volume 2: System Programming.


                              KVM

                              If KVM modules are loaded you’ll need to remove them by:

                              sudo modprobe -r kvm_intel
                              sudo modprobe -r kvm_amd 
                              

                              for Intel and AMD respectively as they clash with Virtual Box. Ref.


                              Enabling

                              For your specific model I guess @Anthon has said plenty.

                              As he mention, by using UEFI you most likely would have to reinstall your host system. Other risks by upgrading BIOS is a lot of things where a few
                              could be:

                              • New BIOS could trigger latent bugs in hardware.
                              • The flash of BIOS could crash due to software corruption etc.
                              • One could have downloaded wrong BIOS (for a different model).
                              • Computer could crash, loose power in the mids of flash. (AKA freak accident).
                              • N^x unknown factors could play in.
                              • etc.

                              If flash crashes it could render your PC completely unbootable and a fix could
                              prove to be hard. (You can’t i.e. boot and fix BIOS.)

                              You should have a backup of current BIOS and a USB rescue stick.

                              Search the web, e.g. look at this. Check if your model has “built-in BIOS recovery routine” as mentioned in last post on that page. (As you can see
                              even that can give trouble).

                              And yes, again as mentioned by Anthon. If you do not have any other PC easily
                              accessible for web-search in case of failure, it is far from recommended.


                              If you are willing to hack, risk unknown repercussions etc. you can try to use
                              a “unofficial BIOS version”. This thread at BOIS-Mods have both
                              software and a general discussion. Would read entire thread thoroughly and
                              ask if any questions.

                              Depending on your level of interest, time, and knowledge you could also try
                              to hack this on your own 😉

                              SVM enable

                              share|improve this answer

                              • so, run the command grep -wo "^flagss*:.*(vmx|svm)" /proc/cpuinfo not found nothing, So definitely not possible, right @Sukminder. But if I try to do the hack the way that @Anthon says, What is the worst that can happen?.

                                – Cristian Chaparro A.
                                May 3 ’13 at 1:42

                              • @CristianChaparroA.: Ah. no, extremely sorry. Forgot to update the grep line. Was meaning to update it. From the output you posted you have svm. Else I have updated the answer with some more bla bla. 😉

                                – Runium
                                May 3 ’13 at 5:32

                              1

                              Included procedure for both Intel and AMD as if anyone is on either. Also included some information that you know like grep for svm – for completeness sake.

                              Checking support

                              Check if visualization is available

                              • Intel check if vmx is found (VT-x)

                                grep -o "^flagss*:.*svmx(s|$)" /proc/cpuinfo
                                
                              • AMD check if svm is found (AMD-V)

                                grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
                                

                              If not found, one are most likely out of luck.

                              One can also check flags from BIOS by dmidecode

                              dmidecode --type 4 | grep -i virt
                              VME (Virtual mode extension)        # On a specific i386
                              

                              Checking status – require root privileges

                              Read the machine/model specific registers (MSR), (man msr), using msr-tools
                              if not enabled (read fails) load msr by:

                              modprobe msr
                              

                              Then use rdmsr, (quick intoduction) to read processor MSR’s.


                              Intel

                              For Intel processors one can check current status by reading IA32_FEATURE_CONTROL(1) from the processor.

                              The IA32_FEATURE_CONTROL MSR (at address 03AH) provides feature control bits
                              that configure operation of VMX and SMX.

                              Execute commands:

                              rdmsr -f 0:0 0x3a # Read bit-field 0 (Lock-bit)
                              rdmsr -f 2:2 0x3a # Read bit-field 2 (Enable VMX outside SMX operation)
                              

                              These commands should give:

                              0:0 2:2
                                0      ENABLED  (Not 100% sure about this one, `kvm-ok` reports VMX
                                                 as enabled when 0 – perhaps meant as modifiable.)
                                1   1  ENABLED
                                1   0  DISABLED 
                              

                              Bit 2 enables VMX outside SMX operation. If this bit is clear, an attempt to execute VMXON will cause a general-
                              protection exception if executed outside SMX operation. Attempts to set this bit on logical processors that do
                              not support VMX operation cause general-protection exceptions.

                              (1) Intel® 64 and IA-32 Architectures Software Developer’s Manual Vol. 2C 5-1 pp 1072.


                              AMD

                              Read Extended Feature Enable Register (EFER)(2) pp. 55, 103 in PDF
                              where bit 12 is “Secure Virtual Machine Enable” (SVME) which indicate whether
                              hardware virtualization is enabled.

                              Execute command:

                              rdmsr -f 12:12 0xc0000080 # If set (1), SVME is enabled.
                              

                              Secure Virtual Machine Enable (SVME) Bit. Bit 12, read/write. Enables the SVM extensions.
                              When this bit is zero, the SVM instructions cause #UD exceptions. EFER.SVME defaults to a reset
                              value of zero. The effect of turning off EFER.SVME while a guest is running is undefined; therefore,
                              the VMM should always prevent guests from writing EFER. SVM extensions can be disabled by
                              setting VM_CR.SVME_DISABLE.

                              To check if it is disabled for session check VM_CR.SVME_DISABLE(2) pp 57, 504 (105, 552 in PDF)

                              Execute command:

                              rdmsr -f 4:4 0xc0010114 # If set (1), it is disabled.
                              

                              as in: you would have to enable in BIOS.

                              SVMDIS — Bit 4. When this bit is set, writes to EFER treat the SVME bit as MBZ. When this bit is
                              clear, EFER.SVME can be written normally. This bit does not prevent CPUID from reporting that
                              SVM is available. Setting SVMDIS while EFER.SVME is 1 generates a #GP fault, regardless of
                              the current state of VM_CR.LOCK. This bit is not affected by SKINIT. It is cleared by INIT when
                              LOCK is cleared to 0; otherwise, it is not affected.

                              (2)AMD64 Architecture Programmer’s Manual, Volume 2: System Programming.


                              KVM

                              If KVM modules are loaded you’ll need to remove them by:

                              sudo modprobe -r kvm_intel
                              sudo modprobe -r kvm_amd 
                              

                              for Intel and AMD respectively as they clash with Virtual Box. Ref.


                              Enabling

                              For your specific model I guess @Anthon has said plenty.

                              As he mention, by using UEFI you most likely would have to reinstall your host system. Other risks by upgrading BIOS is a lot of things where a few
                              could be:

                              • New BIOS could trigger latent bugs in hardware.
                              • The flash of BIOS could crash due to software corruption etc.
                              • One could have downloaded wrong BIOS (for a different model).
                              • Computer could crash, loose power in the mids of flash. (AKA freak accident).
                              • N^x unknown factors could play in.
                              • etc.

                              If flash crashes it could render your PC completely unbootable and a fix could
                              prove to be hard. (You can’t i.e. boot and fix BIOS.)

                              You should have a backup of current BIOS and a USB rescue stick.

                              Search the web, e.g. look at this. Check if your model has “built-in BIOS recovery routine” as mentioned in last post on that page. (As you can see
                              even that can give trouble).

                              And yes, again as mentioned by Anthon. If you do not have any other PC easily
                              accessible for web-search in case of failure, it is far from recommended.


                              If you are willing to hack, risk unknown repercussions etc. you can try to use
                              a “unofficial BIOS version”. This thread at BOIS-Mods have both
                              software and a general discussion. Would read entire thread thoroughly and
                              ask if any questions.

                              Depending on your level of interest, time, and knowledge you could also try
                              to hack this on your own 😉

                              SVM enable

                              share|improve this answer

                              • so, run the command grep -wo "^flagss*:.*(vmx|svm)" /proc/cpuinfo not found nothing, So definitely not possible, right @Sukminder. But if I try to do the hack the way that @Anthon says, What is the worst that can happen?.

                                – Cristian Chaparro A.
                                May 3 ’13 at 1:42

                              • @CristianChaparroA.: Ah. no, extremely sorry. Forgot to update the grep line. Was meaning to update it. From the output you posted you have svm. Else I have updated the answer with some more bla bla. 😉

                                – Runium
                                May 3 ’13 at 5:32

                              1

                              1

                              1

                              Included procedure for both Intel and AMD as if anyone is on either. Also included some information that you know like grep for svm – for completeness sake.

                              Checking support

                              Check if visualization is available

                              • Intel check if vmx is found (VT-x)

                                grep -o "^flagss*:.*svmx(s|$)" /proc/cpuinfo
                                
                              • AMD check if svm is found (AMD-V)

                                grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
                                

                              If not found, one are most likely out of luck.

                              One can also check flags from BIOS by dmidecode

                              dmidecode --type 4 | grep -i virt
                              VME (Virtual mode extension)        # On a specific i386
                              

                              Checking status – require root privileges

                              Read the machine/model specific registers (MSR), (man msr), using msr-tools
                              if not enabled (read fails) load msr by:

                              modprobe msr
                              

                              Then use rdmsr, (quick intoduction) to read processor MSR’s.


                              Intel

                              For Intel processors one can check current status by reading IA32_FEATURE_CONTROL(1) from the processor.

                              The IA32_FEATURE_CONTROL MSR (at address 03AH) provides feature control bits
                              that configure operation of VMX and SMX.

                              Execute commands:

                              rdmsr -f 0:0 0x3a # Read bit-field 0 (Lock-bit)
                              rdmsr -f 2:2 0x3a # Read bit-field 2 (Enable VMX outside SMX operation)
                              

                              These commands should give:

                              0:0 2:2
                                0      ENABLED  (Not 100% sure about this one, `kvm-ok` reports VMX
                                                 as enabled when 0 – perhaps meant as modifiable.)
                                1   1  ENABLED
                                1   0  DISABLED 
                              

                              Bit 2 enables VMX outside SMX operation. If this bit is clear, an attempt to execute VMXON will cause a general-
                              protection exception if executed outside SMX operation. Attempts to set this bit on logical processors that do
                              not support VMX operation cause general-protection exceptions.

                              (1) Intel® 64 and IA-32 Architectures Software Developer’s Manual Vol. 2C 5-1 pp 1072.


                              AMD

                              Read Extended Feature Enable Register (EFER)(2) pp. 55, 103 in PDF
                              where bit 12 is “Secure Virtual Machine Enable” (SVME) which indicate whether
                              hardware virtualization is enabled.

                              Execute command:

                              rdmsr -f 12:12 0xc0000080 # If set (1), SVME is enabled.
                              

                              Secure Virtual Machine Enable (SVME) Bit. Bit 12, read/write. Enables the SVM extensions.
                              When this bit is zero, the SVM instructions cause #UD exceptions. EFER.SVME defaults to a reset
                              value of zero. The effect of turning off EFER.SVME while a guest is running is undefined; therefore,
                              the VMM should always prevent guests from writing EFER. SVM extensions can be disabled by
                              setting VM_CR.SVME_DISABLE.

                              To check if it is disabled for session check VM_CR.SVME_DISABLE(2) pp 57, 504 (105, 552 in PDF)

                              Execute command:

                              rdmsr -f 4:4 0xc0010114 # If set (1), it is disabled.
                              

                              as in: you would have to enable in BIOS.

                              SVMDIS — Bit 4. When this bit is set, writes to EFER treat the SVME bit as MBZ. When this bit is
                              clear, EFER.SVME can be written normally. This bit does not prevent CPUID from reporting that
                              SVM is available. Setting SVMDIS while EFER.SVME is 1 generates a #GP fault, regardless of
                              the current state of VM_CR.LOCK. This bit is not affected by SKINIT. It is cleared by INIT when
                              LOCK is cleared to 0; otherwise, it is not affected.

                              (2)AMD64 Architecture Programmer’s Manual, Volume 2: System Programming.


                              KVM

                              If KVM modules are loaded you’ll need to remove them by:

                              sudo modprobe -r kvm_intel
                              sudo modprobe -r kvm_amd 
                              

                              for Intel and AMD respectively as they clash with Virtual Box. Ref.


                              Enabling

                              For your specific model I guess @Anthon has said plenty.

                              As he mention, by using UEFI you most likely would have to reinstall your host system. Other risks by upgrading BIOS is a lot of things where a few
                              could be:

                              • New BIOS could trigger latent bugs in hardware.
                              • The flash of BIOS could crash due to software corruption etc.
                              • One could have downloaded wrong BIOS (for a different model).
                              • Computer could crash, loose power in the mids of flash. (AKA freak accident).
                              • N^x unknown factors could play in.
                              • etc.

                              If flash crashes it could render your PC completely unbootable and a fix could
                              prove to be hard. (You can’t i.e. boot and fix BIOS.)

                              You should have a backup of current BIOS and a USB rescue stick.

                              Search the web, e.g. look at this. Check if your model has “built-in BIOS recovery routine” as mentioned in last post on that page. (As you can see
                              even that can give trouble).

                              And yes, again as mentioned by Anthon. If you do not have any other PC easily
                              accessible for web-search in case of failure, it is far from recommended.


                              If you are willing to hack, risk unknown repercussions etc. you can try to use
                              a “unofficial BIOS version”. This thread at BOIS-Mods have both
                              software and a general discussion. Would read entire thread thoroughly and
                              ask if any questions.

                              Depending on your level of interest, time, and knowledge you could also try
                              to hack this on your own 😉

                              SVM enable

                              share|improve this answer

                              Included procedure for both Intel and AMD as if anyone is on either. Also included some information that you know like grep for svm – for completeness sake.

                              Checking support

                              Check if visualization is available

                              • Intel check if vmx is found (VT-x)

                                grep -o "^flagss*:.*svmx(s|$)" /proc/cpuinfo
                                
                              • AMD check if svm is found (AMD-V)

                                grep -o "^flagss*:.*ssvm(s|$)" /proc/cpuinfo
                                

                              If not found, one are most likely out of luck.

                              One can also check flags from BIOS by dmidecode

                              dmidecode --type 4 | grep -i virt
                              VME (Virtual mode extension)        # On a specific i386
                              

                              Checking status – require root privileges

                              Read the machine/model specific registers (MSR), (man msr), using msr-tools
                              if not enabled (read fails) load msr by:

                              modprobe msr
                              

                              Then use rdmsr, (quick intoduction) to read processor MSR’s.


                              Intel

                              For Intel processors one can check current status by reading IA32_FEATURE_CONTROL(1) from the processor.

                              The IA32_FEATURE_CONTROL MSR (at address 03AH) provides feature control bits
                              that configure operation of VMX and SMX.

                              Execute commands:

                              rdmsr -f 0:0 0x3a # Read bit-field 0 (Lock-bit)
                              rdmsr -f 2:2 0x3a # Read bit-field 2 (Enable VMX outside SMX operation)
                              

                              These commands should give:

                              0:0 2:2
                                0      ENABLED  (Not 100% sure about this one, `kvm-ok` reports VMX
                                                 as enabled when 0 – perhaps meant as modifiable.)
                                1   1  ENABLED
                                1   0  DISABLED 
                              

                              Bit 2 enables VMX outside SMX operation. If this bit is clear, an attempt to execute VMXON will cause a general-
                              protection exception if executed outside SMX operation. Attempts to set this bit on logical processors that do
                              not support VMX operation cause general-protection exceptions.

                              (1) Intel® 64 and IA-32 Architectures Software Developer’s Manual Vol. 2C 5-1 pp 1072.


                              AMD

                              Read Extended Feature Enable Register (EFER)(2) pp. 55, 103 in PDF
                              where bit 12 is “Secure Virtual Machine Enable” (SVME) which indicate whether
                              hardware virtualization is enabled.

                              Execute command:

                              rdmsr -f 12:12 0xc0000080 # If set (1), SVME is enabled.
                              

                              Secure Virtual Machine Enable (SVME) Bit. Bit 12, read/write. Enables the SVM extensions.
                              When this bit is zero, the SVM instructions cause #UD exceptions. EFER.SVME defaults to a reset
                              value of zero. The effect of turning off EFER.SVME while a guest is running is undefined; therefore,
                              the VMM should always prevent guests from writing EFER. SVM extensions can be disabled by
                              setting VM_CR.SVME_DISABLE.

                              To check if it is disabled for session check VM_CR.SVME_DISABLE(2) pp 57, 504 (105, 552 in PDF)

                              Execute command:

                              rdmsr -f 4:4 0xc0010114 # If set (1), it is disabled.
                              

                              as in: you would have to enable in BIOS.

                              SVMDIS — Bit 4. When this bit is set, writes to EFER treat the SVME bit as MBZ. When this bit is
                              clear, EFER.SVME can be written normally. This bit does not prevent CPUID from reporting that
                              SVM is available. Setting SVMDIS while EFER.SVME is 1 generates a #GP fault, regardless of
                              the current state of VM_CR.LOCK. This bit is not affected by SKINIT. It is cleared by INIT when
                              LOCK is cleared to 0; otherwise, it is not affected.

                              (2)AMD64 Architecture Programmer’s Manual, Volume 2: System Programming.


                              KVM

                              If KVM modules are loaded you’ll need to remove them by:

                              sudo modprobe -r kvm_intel
                              sudo modprobe -r kvm_amd 
                              

                              for Intel and AMD respectively as they clash with Virtual Box. Ref.


                              Enabling

                              For your specific model I guess @Anthon has said plenty.

                              As he mention, by using UEFI you most likely would have to reinstall your host system. Other risks by upgrading BIOS is a lot of things where a few
                              could be:

                              • New BIOS could trigger latent bugs in hardware.
                              • The flash of BIOS could crash due to software corruption etc.
                              • One could have downloaded wrong BIOS (for a different model).
                              • Computer could crash, loose power in the mids of flash. (AKA freak accident).
                              • N^x unknown factors could play in.
                              • etc.

                              If flash crashes it could render your PC completely unbootable and a fix could
                              prove to be hard. (You can’t i.e. boot and fix BIOS.)

                              You should have a backup of current BIOS and a USB rescue stick.

                              Search the web, e.g. look at this. Check if your model has “built-in BIOS recovery routine” as mentioned in last post on that page. (As you can see
                              even that can give trouble).

                              And yes, again as mentioned by Anthon. If you do not have any other PC easily
                              accessible for web-search in case of failure, it is far from recommended.


                              If you are willing to hack, risk unknown repercussions etc. you can try to use
                              a “unofficial BIOS version”. This thread at BOIS-Mods have both
                              software and a general discussion. Would read entire thread thoroughly and
                              ask if any questions.

                              Depending on your level of interest, time, and knowledge you could also try
                              to hack this on your own 😉

                              SVM enable

                              share|improve this answer

                              share|improve this answer

                              share|improve this answer

                              edited Apr 13 ’17 at 12:36

                              Community

                              1

                              1

                              answered May 2 ’13 at 7:44

                              RuniumRunium

                              18.4k43060

                              18.4k43060

                              • so, run the command grep -wo "^flagss*:.*(vmx|svm)" /proc/cpuinfo not found nothing, So definitely not possible, right @Sukminder. But if I try to do the hack the way that @Anthon says, What is the worst that can happen?.

                                – Cristian Chaparro A.
                                May 3 ’13 at 1:42

                              • @CristianChaparroA.: Ah. no, extremely sorry. Forgot to update the grep line. Was meaning to update it. From the output you posted you have svm. Else I have updated the answer with some more bla bla. 😉

                                – Runium
                                May 3 ’13 at 5:32

                              • so, run the command grep -wo "^flagss*:.*(vmx|svm)" /proc/cpuinfo not found nothing, So definitely not possible, right @Sukminder. But if I try to do the hack the way that @Anthon says, What is the worst that can happen?.

                                – Cristian Chaparro A.
                                May 3 ’13 at 1:42

                              • @CristianChaparroA.: Ah. no, extremely sorry. Forgot to update the grep line. Was meaning to update it. From the output you posted you have svm. Else I have updated the answer with some more bla bla. 😉

                                – Runium
                                May 3 ’13 at 5:32

                              so, run the command grep -wo "^flagss*:.*(vmx|svm)" /proc/cpuinfo not found nothing, So definitely not possible, right @Sukminder. But if I try to do the hack the way that @Anthon says, What is the worst that can happen?.

                              – Cristian Chaparro A.
                              May 3 ’13 at 1:42

                              so, run the command grep -wo "^flagss*:.*(vmx|svm)" /proc/cpuinfo not found nothing, So definitely not possible, right @Sukminder. But if I try to do the hack the way that @Anthon says, What is the worst that can happen?.

                              – Cristian Chaparro A.
                              May 3 ’13 at 1:42

                              @CristianChaparroA.: Ah. no, extremely sorry. Forgot to update the grep line. Was meaning to update it. From the output you posted you have svm. Else I have updated the answer with some more bla bla. 😉

                              – Runium
                              May 3 ’13 at 5:32

                              @CristianChaparroA.: Ah. no, extremely sorry. Forgot to update the grep line. Was meaning to update it. From the output you posted you have svm. Else I have updated the answer with some more bla bla. 😉

                              – Runium
                              May 3 ’13 at 5:32

                              draft saved
                              draft discarded

                              Thanks for contributing an answer to Unix & Linux Stack Exchange!

                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid

                              • Asking for help, clarification, or responding to other answers.
                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.

                              draft saved

                              draft discarded

                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f74376%2fhow-to-enable-virtualization-amd-v-aspire-one-ao725-from-bios-or-otherwise%23new-answer’, ‘question_page’);
                              }
                              );

                              Post as a guest

                              Required, but never shown

                              Required, but never shown

                              Required, but never shown

                              Required, but never shown

                              Required, but never shown

                              Required, but never shown

                              Required, but never shown

                              Required, but never shown

                              Required, but never shown

                              Cannot overclock AMD GPU on Ubuntu 18.04 LTS

                              The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                              0

                              I am trying to overclock the memory on my GPU with AMDGPU Pro 18.40 driver.

                              Nonetheless, /sys/class/drm/card0/device/pp_od_clk_voltage is an empty file and I cannot write to it.

                              When I try

                              echo "m 2 1600 950" > /sys/class/drm/card0/device/pp_od_clk_voltage
                              

                              as root it produces the following error:

                              -bash: echo: write error: Invalid argument
                              

                              I have amdgpu.ppfeaturemask=0xffffffff in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

                              I have also tried running:

                              echo manual | sudo tee /sys/class/drm/card0/device/power_dpm_force_performance_level
                              

                              My question is based on the answer to the following question: Can’t overclock GPU using amdgpu driver on archlinux
                              The author claims that this method works, however it obviously does not.

                              share|improve this question

                                0

                                I am trying to overclock the memory on my GPU with AMDGPU Pro 18.40 driver.

                                Nonetheless, /sys/class/drm/card0/device/pp_od_clk_voltage is an empty file and I cannot write to it.

                                When I try

                                echo "m 2 1600 950" > /sys/class/drm/card0/device/pp_od_clk_voltage
                                

                                as root it produces the following error:

                                -bash: echo: write error: Invalid argument
                                

                                I have amdgpu.ppfeaturemask=0xffffffff in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

                                I have also tried running:

                                echo manual | sudo tee /sys/class/drm/card0/device/power_dpm_force_performance_level
                                

                                My question is based on the answer to the following question: Can’t overclock GPU using amdgpu driver on archlinux
                                The author claims that this method works, however it obviously does not.

                                share|improve this question

                                  0

                                  0

                                  0

                                  I am trying to overclock the memory on my GPU with AMDGPU Pro 18.40 driver.

                                  Nonetheless, /sys/class/drm/card0/device/pp_od_clk_voltage is an empty file and I cannot write to it.

                                  When I try

                                  echo "m 2 1600 950" > /sys/class/drm/card0/device/pp_od_clk_voltage
                                  

                                  as root it produces the following error:

                                  -bash: echo: write error: Invalid argument
                                  

                                  I have amdgpu.ppfeaturemask=0xffffffff in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

                                  I have also tried running:

                                  echo manual | sudo tee /sys/class/drm/card0/device/power_dpm_force_performance_level
                                  

                                  My question is based on the answer to the following question: Can’t overclock GPU using amdgpu driver on archlinux
                                  The author claims that this method works, however it obviously does not.

                                  share|improve this question

                                  I am trying to overclock the memory on my GPU with AMDGPU Pro 18.40 driver.

                                  Nonetheless, /sys/class/drm/card0/device/pp_od_clk_voltage is an empty file and I cannot write to it.

                                  When I try

                                  echo "m 2 1600 950" > /sys/class/drm/card0/device/pp_od_clk_voltage
                                  

                                  as root it produces the following error:

                                  -bash: echo: write error: Invalid argument
                                  

                                  I have amdgpu.ppfeaturemask=0xffffffff in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

                                  I have also tried running:

                                  echo manual | sudo tee /sys/class/drm/card0/device/power_dpm_force_performance_level
                                  

                                  My question is based on the answer to the following question: Can’t overclock GPU using amdgpu driver on archlinux
                                  The author claims that this method works, however it obviously does not.

                                  ubuntu amd-graphics amd

                                  share|improve this question

                                  share|improve this question

                                  share|improve this question

                                  share|improve this question

                                  edited Dec 12 at 16:25

                                  asked Dec 12 at 16:17

                                  Stefan Wirtz

                                  12

                                  12

                                      active

                                      oldest

                                      votes

                                      Your Answer

                                      StackExchange.ready(function() {
                                      var channelOptions = {
                                      tags: “”.split(” “),
                                      id: “106”
                                      };
                                      initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                      StackExchange.using(“externalEditor”, function() {
                                      // Have to fire editor after snippets, if snippets enabled
                                      if (StackExchange.settings.snippets.snippetsEnabled) {
                                      StackExchange.using(“snippets”, function() {
                                      createEditor();
                                      });
                                      }
                                      else {
                                      createEditor();
                                      }
                                      });

                                      function createEditor() {
                                      StackExchange.prepareEditor({
                                      heartbeatType: ‘answer’,
                                      autoActivateHeartbeat: false,
                                      convertImagesToLinks: false,
                                      noModals: true,
                                      showLowRepImageUploadWarning: true,
                                      reputationToPostImages: null,
                                      bindNavPrevention: true,
                                      postfix: “”,
                                      imageUploader: {
                                      brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                      contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                      allowUrls: true
                                      },
                                      onDemand: true,
                                      discardSelector: “.discard-answer”
                                      ,immediatelyShowMarkdownHelp:true
                                      });

                                      }
                                      });

                                      draft saved
                                      draft discarded

                                      StackExchange.ready(
                                      function () {
                                      StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f487606%2fcannot-overclock-amd-gpu-on-ubuntu-18-04-lts%23new-answer’, ‘question_page’);
                                      }
                                      );

                                      Post as a guest

                                      Required, but never shown

                                      active

                                      oldest

                                      votes

                                      active

                                      oldest

                                      votes

                                      active

                                      oldest

                                      votes

                                      active

                                      oldest

                                      votes

                                      draft saved
                                      draft discarded

                                      Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                      • Please be sure to answer the question. Provide details and share your research!

                                      But avoid

                                      • Asking for help, clarification, or responding to other answers.
                                      • Making statements based on opinion; back them up with references or personal experience.

                                      To learn more, see our tips on writing great answers.

                                      Some of your past answers have not been well-received, and you’re in danger of being blocked from answering.

                                      Please pay close attention to the following guidance:

                                      • Please be sure to answer the question. Provide details and share your research!

                                      But avoid

                                      • Asking for help, clarification, or responding to other answers.
                                      • Making statements based on opinion; back them up with references or personal experience.

                                      To learn more, see our tips on writing great answers.

                                      draft saved

                                      draft discarded

                                      StackExchange.ready(
                                      function () {
                                      StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f487606%2fcannot-overclock-amd-gpu-on-ubuntu-18-04-lts%23new-answer’, ‘question_page’);
                                      }
                                      );

                                      Post as a guest

                                      Required, but never shown

                                      Required, but never shown

                                      Required, but never shown

                                      Required, but never shown

                                      Required, but never shown

                                      Required, but never shown

                                      Required, but never shown

                                      Required, but never shown

                                      Required, but never shown

                                      How do I compile my Gentoo kernel for AMD IOMMU?

                                      The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                      up vote
                                      1
                                      down vote

                                      favorite

                                      I have an AMD A4-5300 CPU with a motherboard that supports IOMMU and I am trying to enable IOMMU on my Gentoo Hardened 4.3.3-r4 kernel with the intention of using a graphics card on a KVM VM. According to this guide here, I’m supposed to recompile my kernel with a few provided options (“Support for DMA Remapping Devices”, “Enable DMA Remapping Devices” and “PCI Stub driver”). However, “Support for DMA Remapping Devices” and “Enable DMA Remapping Devices” are absent from my kernel configuration.

                                      I then searched the configuration for “remap” and tried enabling a number of options, which were CONFIG_IRQ_REMAP, CONFIG_DMAR_TABLE, CONFIG_IOMMU_SUPPORT, CONFIG_SWIOTLB and CONFIG_PCI_IOV. Then I recompiled my kernel with these options enabled, started my system with amd_iommu=fullflush iommu=force on the kernel command line, and according to the aforementioned guide I checked if IOMMU was running on my system by looking for “AMD-Vi” on my kernel messages:

                                      dmesg | grep AMD-Vi
                                      

                                      Nothing shows up on my kernel log about AMD-Vi.

                                      In addition, when I try to start a VM on virt-manager with an attached PCI device, I get a message that says “Error starting domain: unsupported configuration: host doesn’t support passthrough of host PCI devices”.

                                      Pretty much everything I find is for Fedora, Ubuntu and Debian where IOMMU apparently Just Works out of the box. I don’t believe it’s a matter of my motherboard and CPU not supporting it, because my BIOS has an option for it, and because I remember being able a few years ago to run a VirtualBox VM with IOMMU on Debian (though I didn’t follow up on it because I never thought at the moment that I required two graphic cards to use a GPU on a VM through IOMMU).

                                      Here’s what I have already tried but didn’t work:

                                      1. Using the standard kernel instead of hardened.
                                      2. Enabling Device Drivers >> IOMMU Hardware Support, AMD IOMMU support, Support for Intel IOMMU using DMA Remapping Devices, Support for Interrupt Remapping and Bus options (PCI etc.) >> PCI Stub.
                                      3. Using the latest kernel, currently just upgraded to 4.4.8-hardened-r1.

                                      This is the command line I’m using to start my kernel, with each parameter on a separate line for convenience:

                                      root=/dev/ram0 
                                      crypt_root=/dev/disk/by-uuid/c1ce6456-4c6a-4a64-8027-5ec4fdc0f344 
                                      dolvm 
                                      real_root=/dev/mapper/cryptgentoo-raiz 
                                      rootfstype=jfs 
                                      real_init=/sbin/init 
                                      root_keydev=/dev/disk/by-partuuid/086194de-e476-4abb-82da-9744e6fb0257 
                                      root_key=luks-key.gpg 
                                      keymap=la 
                                      amd_iommu=on 
                                      iommu=on
                                      

                                      Am I still missing a kernel configuration option?


                                      Update: Out of absent-mindedness I mistakenly issued ps -ef | grep -i iommu, and look what I just found…

                                      rockshooter ~ # ps -ef | grep iommu
                                      root        66     2  0 02:57 ?        00:00:00 [amd_iommu_v2]
                                      

                                      If I see a kernel thread, I guess there might be a chance that I can get IOMMU running, it’s just that my kernel isn’t saying anything about it. It’s just a wild guess… but I’m going to go ahead and try using it.

                                      share|improve this question

                                        up vote
                                        1
                                        down vote

                                        favorite

                                        I have an AMD A4-5300 CPU with a motherboard that supports IOMMU and I am trying to enable IOMMU on my Gentoo Hardened 4.3.3-r4 kernel with the intention of using a graphics card on a KVM VM. According to this guide here, I’m supposed to recompile my kernel with a few provided options (“Support for DMA Remapping Devices”, “Enable DMA Remapping Devices” and “PCI Stub driver”). However, “Support for DMA Remapping Devices” and “Enable DMA Remapping Devices” are absent from my kernel configuration.

                                        I then searched the configuration for “remap” and tried enabling a number of options, which were CONFIG_IRQ_REMAP, CONFIG_DMAR_TABLE, CONFIG_IOMMU_SUPPORT, CONFIG_SWIOTLB and CONFIG_PCI_IOV. Then I recompiled my kernel with these options enabled, started my system with amd_iommu=fullflush iommu=force on the kernel command line, and according to the aforementioned guide I checked if IOMMU was running on my system by looking for “AMD-Vi” on my kernel messages:

                                        dmesg | grep AMD-Vi
                                        

                                        Nothing shows up on my kernel log about AMD-Vi.

                                        In addition, when I try to start a VM on virt-manager with an attached PCI device, I get a message that says “Error starting domain: unsupported configuration: host doesn’t support passthrough of host PCI devices”.

                                        Pretty much everything I find is for Fedora, Ubuntu and Debian where IOMMU apparently Just Works out of the box. I don’t believe it’s a matter of my motherboard and CPU not supporting it, because my BIOS has an option for it, and because I remember being able a few years ago to run a VirtualBox VM with IOMMU on Debian (though I didn’t follow up on it because I never thought at the moment that I required two graphic cards to use a GPU on a VM through IOMMU).

                                        Here’s what I have already tried but didn’t work:

                                        1. Using the standard kernel instead of hardened.
                                        2. Enabling Device Drivers >> IOMMU Hardware Support, AMD IOMMU support, Support for Intel IOMMU using DMA Remapping Devices, Support for Interrupt Remapping and Bus options (PCI etc.) >> PCI Stub.
                                        3. Using the latest kernel, currently just upgraded to 4.4.8-hardened-r1.

                                        This is the command line I’m using to start my kernel, with each parameter on a separate line for convenience:

                                        root=/dev/ram0 
                                        crypt_root=/dev/disk/by-uuid/c1ce6456-4c6a-4a64-8027-5ec4fdc0f344 
                                        dolvm 
                                        real_root=/dev/mapper/cryptgentoo-raiz 
                                        rootfstype=jfs 
                                        real_init=/sbin/init 
                                        root_keydev=/dev/disk/by-partuuid/086194de-e476-4abb-82da-9744e6fb0257 
                                        root_key=luks-key.gpg 
                                        keymap=la 
                                        amd_iommu=on 
                                        iommu=on
                                        

                                        Am I still missing a kernel configuration option?


                                        Update: Out of absent-mindedness I mistakenly issued ps -ef | grep -i iommu, and look what I just found…

                                        rockshooter ~ # ps -ef | grep iommu
                                        root        66     2  0 02:57 ?        00:00:00 [amd_iommu_v2]
                                        

                                        If I see a kernel thread, I guess there might be a chance that I can get IOMMU running, it’s just that my kernel isn’t saying anything about it. It’s just a wild guess… but I’m going to go ahead and try using it.

                                        share|improve this question

                                          up vote
                                          1
                                          down vote

                                          favorite

                                          up vote
                                          1
                                          down vote

                                          favorite

                                          I have an AMD A4-5300 CPU with a motherboard that supports IOMMU and I am trying to enable IOMMU on my Gentoo Hardened 4.3.3-r4 kernel with the intention of using a graphics card on a KVM VM. According to this guide here, I’m supposed to recompile my kernel with a few provided options (“Support for DMA Remapping Devices”, “Enable DMA Remapping Devices” and “PCI Stub driver”). However, “Support for DMA Remapping Devices” and “Enable DMA Remapping Devices” are absent from my kernel configuration.

                                          I then searched the configuration for “remap” and tried enabling a number of options, which were CONFIG_IRQ_REMAP, CONFIG_DMAR_TABLE, CONFIG_IOMMU_SUPPORT, CONFIG_SWIOTLB and CONFIG_PCI_IOV. Then I recompiled my kernel with these options enabled, started my system with amd_iommu=fullflush iommu=force on the kernel command line, and according to the aforementioned guide I checked if IOMMU was running on my system by looking for “AMD-Vi” on my kernel messages:

                                          dmesg | grep AMD-Vi
                                          

                                          Nothing shows up on my kernel log about AMD-Vi.

                                          In addition, when I try to start a VM on virt-manager with an attached PCI device, I get a message that says “Error starting domain: unsupported configuration: host doesn’t support passthrough of host PCI devices”.

                                          Pretty much everything I find is for Fedora, Ubuntu and Debian where IOMMU apparently Just Works out of the box. I don’t believe it’s a matter of my motherboard and CPU not supporting it, because my BIOS has an option for it, and because I remember being able a few years ago to run a VirtualBox VM with IOMMU on Debian (though I didn’t follow up on it because I never thought at the moment that I required two graphic cards to use a GPU on a VM through IOMMU).

                                          Here’s what I have already tried but didn’t work:

                                          1. Using the standard kernel instead of hardened.
                                          2. Enabling Device Drivers >> IOMMU Hardware Support, AMD IOMMU support, Support for Intel IOMMU using DMA Remapping Devices, Support for Interrupt Remapping and Bus options (PCI etc.) >> PCI Stub.
                                          3. Using the latest kernel, currently just upgraded to 4.4.8-hardened-r1.

                                          This is the command line I’m using to start my kernel, with each parameter on a separate line for convenience:

                                          root=/dev/ram0 
                                          crypt_root=/dev/disk/by-uuid/c1ce6456-4c6a-4a64-8027-5ec4fdc0f344 
                                          dolvm 
                                          real_root=/dev/mapper/cryptgentoo-raiz 
                                          rootfstype=jfs 
                                          real_init=/sbin/init 
                                          root_keydev=/dev/disk/by-partuuid/086194de-e476-4abb-82da-9744e6fb0257 
                                          root_key=luks-key.gpg 
                                          keymap=la 
                                          amd_iommu=on 
                                          iommu=on
                                          

                                          Am I still missing a kernel configuration option?


                                          Update: Out of absent-mindedness I mistakenly issued ps -ef | grep -i iommu, and look what I just found…

                                          rockshooter ~ # ps -ef | grep iommu
                                          root        66     2  0 02:57 ?        00:00:00 [amd_iommu_v2]
                                          

                                          If I see a kernel thread, I guess there might be a chance that I can get IOMMU running, it’s just that my kernel isn’t saying anything about it. It’s just a wild guess… but I’m going to go ahead and try using it.

                                          share|improve this question

                                          I have an AMD A4-5300 CPU with a motherboard that supports IOMMU and I am trying to enable IOMMU on my Gentoo Hardened 4.3.3-r4 kernel with the intention of using a graphics card on a KVM VM. According to this guide here, I’m supposed to recompile my kernel with a few provided options (“Support for DMA Remapping Devices”, “Enable DMA Remapping Devices” and “PCI Stub driver”). However, “Support for DMA Remapping Devices” and “Enable DMA Remapping Devices” are absent from my kernel configuration.

                                          I then searched the configuration for “remap” and tried enabling a number of options, which were CONFIG_IRQ_REMAP, CONFIG_DMAR_TABLE, CONFIG_IOMMU_SUPPORT, CONFIG_SWIOTLB and CONFIG_PCI_IOV. Then I recompiled my kernel with these options enabled, started my system with amd_iommu=fullflush iommu=force on the kernel command line, and according to the aforementioned guide I checked if IOMMU was running on my system by looking for “AMD-Vi” on my kernel messages:

                                          dmesg | grep AMD-Vi
                                          

                                          Nothing shows up on my kernel log about AMD-Vi.

                                          In addition, when I try to start a VM on virt-manager with an attached PCI device, I get a message that says “Error starting domain: unsupported configuration: host doesn’t support passthrough of host PCI devices”.

                                          Pretty much everything I find is for Fedora, Ubuntu and Debian where IOMMU apparently Just Works out of the box. I don’t believe it’s a matter of my motherboard and CPU not supporting it, because my BIOS has an option for it, and because I remember being able a few years ago to run a VirtualBox VM with IOMMU on Debian (though I didn’t follow up on it because I never thought at the moment that I required two graphic cards to use a GPU on a VM through IOMMU).

                                          Here’s what I have already tried but didn’t work:

                                          1. Using the standard kernel instead of hardened.
                                          2. Enabling Device Drivers >> IOMMU Hardware Support, AMD IOMMU support, Support for Intel IOMMU using DMA Remapping Devices, Support for Interrupt Remapping and Bus options (PCI etc.) >> PCI Stub.
                                          3. Using the latest kernel, currently just upgraded to 4.4.8-hardened-r1.

                                          This is the command line I’m using to start my kernel, with each parameter on a separate line for convenience:

                                          root=/dev/ram0 
                                          crypt_root=/dev/disk/by-uuid/c1ce6456-4c6a-4a64-8027-5ec4fdc0f344 
                                          dolvm 
                                          real_root=/dev/mapper/cryptgentoo-raiz 
                                          rootfstype=jfs 
                                          real_init=/sbin/init 
                                          root_keydev=/dev/disk/by-partuuid/086194de-e476-4abb-82da-9744e6fb0257 
                                          root_key=luks-key.gpg 
                                          keymap=la 
                                          amd_iommu=on 
                                          iommu=on
                                          

                                          Am I still missing a kernel configuration option?


                                          Update: Out of absent-mindedness I mistakenly issued ps -ef | grep -i iommu, and look what I just found…

                                          rockshooter ~ # ps -ef | grep iommu
                                          root        66     2  0 02:57 ?        00:00:00 [amd_iommu_v2]
                                          

                                          If I see a kernel thread, I guess there might be a chance that I can get IOMMU running, it’s just that my kernel isn’t saying anything about it. It’s just a wild guess… but I’m going to go ahead and try using it.

                                          virtual-machine gentoo pci amd

                                          share|improve this question

                                          share|improve this question

                                          share|improve this question

                                          share|improve this question

                                          edited Dec 8 at 15:03

                                          Rui F Ribeiro

                                          38.7k1479128

                                          38.7k1479128

                                          asked Jun 22 ’16 at 6:21

                                          RAKK

                                          4491626

                                          4491626

                                              2 Answers
                                              2

                                              active

                                              oldest

                                              votes

                                              up vote
                                              1
                                              down vote

                                              +50

                                              IOMMU Main Options

                                              Try Device Drivers >> IOMMU Hardware Support:

                                              IOMMU Options

                                              AMD IOMMU

                                              Then enable AMD IOMMU support.

                                              DMA Remapping

                                              Enable Support for Intel IOMMU using DMA Remapping Devices

                                              Optional: IRQ Remapping

                                              Enable Support for Interrupt Remapping

                                              Optional: Enable Version 2 Support

                                              AMD IOMMU Version 2 driver


                                              PCI Option

                                              Bus Options

                                              Bus options (PCI etc.) >> PCI Stub


                                              Never grep the config file, always use menuconfig and the / key to search for the required options. There are three issues with the guide you linked:

                                              1. It’s tailored for Fedora/Redhat users.
                                              2. Because of #1, the kernel version is different, therefore the options are in a different place.
                                              3. Gentoo’s kernel is newer than the kernel used in the guide.

                                              Update

                                              My motherboard is too old to support PCI Passthrough, but I wanted you to see that the options are now properly enabled.Using the exact options I instructed you to use:

                                              IOMMU Main Options

                                              AGP: Checking aperture...
                                              [    0.000000] AGP: No AGP bridge found
                                              [    0.000000] AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB)
                                              [    0.000000] Aperture pointing to e820 RAM. Ignoring.
                                              [    0.000000] AGP: Your BIOS doesn't leave an aperture memory hole
                                              [    0.000000] AGP: Please enable the IOMMU option in the BIOS setup
                                              [    0.000000] AGP: This costs you 64MB of RAM
                                              [    0.000000] AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB)
                                              ...
                                              [    0.959270] PCI-DMA: Disabling AGP.
                                              [    0.959337] PCI-DMA: aperture base @ c4000000 size 65536 KB
                                              [    0.959338] PCI-DMA: using GART IOMMU.
                                              [    0.959340] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
                                              ...
                                              [    1.375277] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
                                              [    1.375277] AMD IOMMUv2 functionality not available on this system
                                              

                                              share|improve this answer

                                              • I just tried enabling these options. It didn’t work. I also tried with the standard kernel and it didn’t work, then I tried upgrading to kernel 4.4.8-hardened-r1 and it didn’t work.
                                                – RAKK
                                                Jun 30 ’16 at 6:03

                                              • What errors did you recurve when trying these? Did you remember to add the kernel to your boot loader configuration? Have you rebooted?
                                                – eyoung100
                                                Jun 30 ’16 at 6:14

                                              • Yep, I have rebooted. I don’t get any error message, I just don’t get any kernel log message saying AMD-Vi was picked up.
                                                – RAKK
                                                Jun 30 ’16 at 6:21

                                              • To give yourself an idea, on the same computer where I have Gentoo I managed to get PCI passthrough working on Debian Stretch. I even used the steps I took to piece together this guide here: wiki.installgentoo.com/index.php/PCI_passthrough
                                                – RAKK
                                                Jun 30 ’16 at 6:22

                                              • Let me follow that guide myself tomorrow. I’ll report back with my findings. If I get the same results as you, we’ll solve this together.
                                                – eyoung100
                                                Jun 30 ’16 at 6:31

                                              up vote
                                              0
                                              down vote

                                              accepted

                                              Finally, after much wailing, complaining and head bashing, I finally figured out what was going on.

                                              As it turns out, IOMMU was working all along, it’s just that the kernel logs weren’t showing it. But the IOMMU driver was there, it was working, and I serendipiously found out when I mistakenly typed ps -ef instead of dmesg like this:

                                              rockshooter ~ # ps -ef | grep -i iommu
                                              root        66     2  0 04:19 ?        00:00:00 [amd_iommu_v2]  
                                              

                                              When I saw that kernel thread running I thought, maybe my IOMMU is actually working? So I performed the same configuration steps I did previously for Debian, and one hour later, lo and behold, I was on my virtual machine hooked up to my graphics card playing some games.

                                              Please save this thread for future reference, because it took me some good 3 weeks to figure this out. I still gave the other poster some well-deserved +50 reputation for bothering with setting up and testing this issue.

                                              share|improve this answer

                                                Your Answer

                                                StackExchange.ready(function() {
                                                var channelOptions = {
                                                tags: “”.split(” “),
                                                id: “106”
                                                };
                                                initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                                StackExchange.using(“externalEditor”, function() {
                                                // Have to fire editor after snippets, if snippets enabled
                                                if (StackExchange.settings.snippets.snippetsEnabled) {
                                                StackExchange.using(“snippets”, function() {
                                                createEditor();
                                                });
                                                }
                                                else {
                                                createEditor();
                                                }
                                                });

                                                function createEditor() {
                                                StackExchange.prepareEditor({
                                                heartbeatType: ‘answer’,
                                                convertImagesToLinks: false,
                                                noModals: true,
                                                showLowRepImageUploadWarning: true,
                                                reputationToPostImages: null,
                                                bindNavPrevention: true,
                                                postfix: “”,
                                                imageUploader: {
                                                brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                                contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                                allowUrls: true
                                                },
                                                onDemand: true,
                                                discardSelector: “.discard-answer”
                                                ,immediatelyShowMarkdownHelp:true
                                                });

                                                }
                                                });

                                                draft saved
                                                draft discarded

                                                StackExchange.ready(
                                                function () {
                                                StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f291297%2fhow-do-i-compile-my-gentoo-kernel-for-amd-iommu%23new-answer’, ‘question_page’);
                                                }
                                                );

                                                Post as a guest

                                                Required, but never shown

                                                2 Answers
                                                2

                                                active

                                                oldest

                                                votes

                                                2 Answers
                                                2

                                                active

                                                oldest

                                                votes

                                                active

                                                oldest

                                                votes

                                                active

                                                oldest

                                                votes

                                                up vote
                                                1
                                                down vote

                                                +50

                                                IOMMU Main Options

                                                Try Device Drivers >> IOMMU Hardware Support:

                                                IOMMU Options

                                                AMD IOMMU

                                                Then enable AMD IOMMU support.

                                                DMA Remapping

                                                Enable Support for Intel IOMMU using DMA Remapping Devices

                                                Optional: IRQ Remapping

                                                Enable Support for Interrupt Remapping

                                                Optional: Enable Version 2 Support

                                                AMD IOMMU Version 2 driver


                                                PCI Option

                                                Bus Options

                                                Bus options (PCI etc.) >> PCI Stub


                                                Never grep the config file, always use menuconfig and the / key to search for the required options. There are three issues with the guide you linked:

                                                1. It’s tailored for Fedora/Redhat users.
                                                2. Because of #1, the kernel version is different, therefore the options are in a different place.
                                                3. Gentoo’s kernel is newer than the kernel used in the guide.

                                                Update

                                                My motherboard is too old to support PCI Passthrough, but I wanted you to see that the options are now properly enabled.Using the exact options I instructed you to use:

                                                IOMMU Main Options

                                                AGP: Checking aperture...
                                                [    0.000000] AGP: No AGP bridge found
                                                [    0.000000] AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB)
                                                [    0.000000] Aperture pointing to e820 RAM. Ignoring.
                                                [    0.000000] AGP: Your BIOS doesn't leave an aperture memory hole
                                                [    0.000000] AGP: Please enable the IOMMU option in the BIOS setup
                                                [    0.000000] AGP: This costs you 64MB of RAM
                                                [    0.000000] AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB)
                                                ...
                                                [    0.959270] PCI-DMA: Disabling AGP.
                                                [    0.959337] PCI-DMA: aperture base @ c4000000 size 65536 KB
                                                [    0.959338] PCI-DMA: using GART IOMMU.
                                                [    0.959340] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
                                                ...
                                                [    1.375277] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
                                                [    1.375277] AMD IOMMUv2 functionality not available on this system
                                                

                                                share|improve this answer

                                                • I just tried enabling these options. It didn’t work. I also tried with the standard kernel and it didn’t work, then I tried upgrading to kernel 4.4.8-hardened-r1 and it didn’t work.
                                                  – RAKK
                                                  Jun 30 ’16 at 6:03

                                                • What errors did you recurve when trying these? Did you remember to add the kernel to your boot loader configuration? Have you rebooted?
                                                  – eyoung100
                                                  Jun 30 ’16 at 6:14

                                                • Yep, I have rebooted. I don’t get any error message, I just don’t get any kernel log message saying AMD-Vi was picked up.
                                                  – RAKK
                                                  Jun 30 ’16 at 6:21

                                                • To give yourself an idea, on the same computer where I have Gentoo I managed to get PCI passthrough working on Debian Stretch. I even used the steps I took to piece together this guide here: wiki.installgentoo.com/index.php/PCI_passthrough
                                                  – RAKK
                                                  Jun 30 ’16 at 6:22

                                                • Let me follow that guide myself tomorrow. I’ll report back with my findings. If I get the same results as you, we’ll solve this together.
                                                  – eyoung100
                                                  Jun 30 ’16 at 6:31

                                                up vote
                                                1
                                                down vote

                                                +50

                                                IOMMU Main Options

                                                Try Device Drivers >> IOMMU Hardware Support:

                                                IOMMU Options

                                                AMD IOMMU

                                                Then enable AMD IOMMU support.

                                                DMA Remapping

                                                Enable Support for Intel IOMMU using DMA Remapping Devices

                                                Optional: IRQ Remapping

                                                Enable Support for Interrupt Remapping

                                                Optional: Enable Version 2 Support

                                                AMD IOMMU Version 2 driver


                                                PCI Option

                                                Bus Options

                                                Bus options (PCI etc.) >> PCI Stub


                                                Never grep the config file, always use menuconfig and the / key to search for the required options. There are three issues with the guide you linked:

                                                1. It’s tailored for Fedora/Redhat users.
                                                2. Because of #1, the kernel version is different, therefore the options are in a different place.
                                                3. Gentoo’s kernel is newer than the kernel used in the guide.

                                                Update

                                                My motherboard is too old to support PCI Passthrough, but I wanted you to see that the options are now properly enabled.Using the exact options I instructed you to use:

                                                IOMMU Main Options

                                                AGP: Checking aperture...
                                                [    0.000000] AGP: No AGP bridge found
                                                [    0.000000] AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB)
                                                [    0.000000] Aperture pointing to e820 RAM. Ignoring.
                                                [    0.000000] AGP: Your BIOS doesn't leave an aperture memory hole
                                                [    0.000000] AGP: Please enable the IOMMU option in the BIOS setup
                                                [    0.000000] AGP: This costs you 64MB of RAM
                                                [    0.000000] AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB)
                                                ...
                                                [    0.959270] PCI-DMA: Disabling AGP.
                                                [    0.959337] PCI-DMA: aperture base @ c4000000 size 65536 KB
                                                [    0.959338] PCI-DMA: using GART IOMMU.
                                                [    0.959340] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
                                                ...
                                                [    1.375277] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
                                                [    1.375277] AMD IOMMUv2 functionality not available on this system
                                                

                                                share|improve this answer

                                                • I just tried enabling these options. It didn’t work. I also tried with the standard kernel and it didn’t work, then I tried upgrading to kernel 4.4.8-hardened-r1 and it didn’t work.
                                                  – RAKK
                                                  Jun 30 ’16 at 6:03

                                                • What errors did you recurve when trying these? Did you remember to add the kernel to your boot loader configuration? Have you rebooted?
                                                  – eyoung100
                                                  Jun 30 ’16 at 6:14

                                                • Yep, I have rebooted. I don’t get any error message, I just don’t get any kernel log message saying AMD-Vi was picked up.
                                                  – RAKK
                                                  Jun 30 ’16 at 6:21

                                                • To give yourself an idea, on the same computer where I have Gentoo I managed to get PCI passthrough working on Debian Stretch. I even used the steps I took to piece together this guide here: wiki.installgentoo.com/index.php/PCI_passthrough
                                                  – RAKK
                                                  Jun 30 ’16 at 6:22

                                                • Let me follow that guide myself tomorrow. I’ll report back with my findings. If I get the same results as you, we’ll solve this together.
                                                  – eyoung100
                                                  Jun 30 ’16 at 6:31

                                                up vote
                                                1
                                                down vote

                                                +50

                                                up vote
                                                1
                                                down vote

                                                +50
                                                +50

                                                IOMMU Main Options

                                                Try Device Drivers >> IOMMU Hardware Support:

                                                IOMMU Options

                                                AMD IOMMU

                                                Then enable AMD IOMMU support.

                                                DMA Remapping

                                                Enable Support for Intel IOMMU using DMA Remapping Devices

                                                Optional: IRQ Remapping

                                                Enable Support for Interrupt Remapping

                                                Optional: Enable Version 2 Support

                                                AMD IOMMU Version 2 driver


                                                PCI Option

                                                Bus Options

                                                Bus options (PCI etc.) >> PCI Stub


                                                Never grep the config file, always use menuconfig and the / key to search for the required options. There are three issues with the guide you linked:

                                                1. It’s tailored for Fedora/Redhat users.
                                                2. Because of #1, the kernel version is different, therefore the options are in a different place.
                                                3. Gentoo’s kernel is newer than the kernel used in the guide.

                                                Update

                                                My motherboard is too old to support PCI Passthrough, but I wanted you to see that the options are now properly enabled.Using the exact options I instructed you to use:

                                                IOMMU Main Options

                                                AGP: Checking aperture...
                                                [    0.000000] AGP: No AGP bridge found
                                                [    0.000000] AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB)
                                                [    0.000000] Aperture pointing to e820 RAM. Ignoring.
                                                [    0.000000] AGP: Your BIOS doesn't leave an aperture memory hole
                                                [    0.000000] AGP: Please enable the IOMMU option in the BIOS setup
                                                [    0.000000] AGP: This costs you 64MB of RAM
                                                [    0.000000] AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB)
                                                ...
                                                [    0.959270] PCI-DMA: Disabling AGP.
                                                [    0.959337] PCI-DMA: aperture base @ c4000000 size 65536 KB
                                                [    0.959338] PCI-DMA: using GART IOMMU.
                                                [    0.959340] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
                                                ...
                                                [    1.375277] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
                                                [    1.375277] AMD IOMMUv2 functionality not available on this system
                                                

                                                share|improve this answer

                                                IOMMU Main Options

                                                Try Device Drivers >> IOMMU Hardware Support:

                                                IOMMU Options

                                                AMD IOMMU

                                                Then enable AMD IOMMU support.

                                                DMA Remapping

                                                Enable Support for Intel IOMMU using DMA Remapping Devices

                                                Optional: IRQ Remapping

                                                Enable Support for Interrupt Remapping

                                                Optional: Enable Version 2 Support

                                                AMD IOMMU Version 2 driver


                                                PCI Option

                                                Bus Options

                                                Bus options (PCI etc.) >> PCI Stub


                                                Never grep the config file, always use menuconfig and the / key to search for the required options. There are three issues with the guide you linked:

                                                1. It’s tailored for Fedora/Redhat users.
                                                2. Because of #1, the kernel version is different, therefore the options are in a different place.
                                                3. Gentoo’s kernel is newer than the kernel used in the guide.

                                                Update

                                                My motherboard is too old to support PCI Passthrough, but I wanted you to see that the options are now properly enabled.Using the exact options I instructed you to use:

                                                IOMMU Main Options

                                                AGP: Checking aperture...
                                                [    0.000000] AGP: No AGP bridge found
                                                [    0.000000] AGP: Node 0: aperture [bus addr 0xc4000000-0xc5ffffff] (32MB)
                                                [    0.000000] Aperture pointing to e820 RAM. Ignoring.
                                                [    0.000000] AGP: Your BIOS doesn't leave an aperture memory hole
                                                [    0.000000] AGP: Please enable the IOMMU option in the BIOS setup
                                                [    0.000000] AGP: This costs you 64MB of RAM
                                                [    0.000000] AGP: Mapping aperture over RAM [mem 0xc4000000-0xc7ffffff] (65536KB)
                                                ...
                                                [    0.959270] PCI-DMA: Disabling AGP.
                                                [    0.959337] PCI-DMA: aperture base @ c4000000 size 65536 KB
                                                [    0.959338] PCI-DMA: using GART IOMMU.
                                                [    0.959340] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
                                                ...
                                                [    1.375277] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
                                                [    1.375277] AMD IOMMUv2 functionality not available on this system
                                                

                                                share|improve this answer

                                                share|improve this answer

                                                share|improve this answer

                                                edited Jul 5 ’16 at 20:10

                                                answered Jun 23 ’16 at 20:46

                                                eyoung100

                                                4,7701441

                                                4,7701441

                                                • I just tried enabling these options. It didn’t work. I also tried with the standard kernel and it didn’t work, then I tried upgrading to kernel 4.4.8-hardened-r1 and it didn’t work.
                                                  – RAKK
                                                  Jun 30 ’16 at 6:03

                                                • What errors did you recurve when trying these? Did you remember to add the kernel to your boot loader configuration? Have you rebooted?
                                                  – eyoung100
                                                  Jun 30 ’16 at 6:14

                                                • Yep, I have rebooted. I don’t get any error message, I just don’t get any kernel log message saying AMD-Vi was picked up.
                                                  – RAKK
                                                  Jun 30 ’16 at 6:21

                                                • To give yourself an idea, on the same computer where I have Gentoo I managed to get PCI passthrough working on Debian Stretch. I even used the steps I took to piece together this guide here: wiki.installgentoo.com/index.php/PCI_passthrough
                                                  – RAKK
                                                  Jun 30 ’16 at 6:22

                                                • Let me follow that guide myself tomorrow. I’ll report back with my findings. If I get the same results as you, we’ll solve this together.
                                                  – eyoung100
                                                  Jun 30 ’16 at 6:31

                                                • I just tried enabling these options. It didn’t work. I also tried with the standard kernel and it didn’t work, then I tried upgrading to kernel 4.4.8-hardened-r1 and it didn’t work.
                                                  – RAKK
                                                  Jun 30 ’16 at 6:03

                                                • What errors did you recurve when trying these? Did you remember to add the kernel to your boot loader configuration? Have you rebooted?
                                                  – eyoung100
                                                  Jun 30 ’16 at 6:14

                                                • Yep, I have rebooted. I don’t get any error message, I just don’t get any kernel log message saying AMD-Vi was picked up.
                                                  – RAKK
                                                  Jun 30 ’16 at 6:21

                                                • To give yourself an idea, on the same computer where I have Gentoo I managed to get PCI passthrough working on Debian Stretch. I even used the steps I took to piece together this guide here: wiki.installgentoo.com/index.php/PCI_passthrough
                                                  – RAKK
                                                  Jun 30 ’16 at 6:22

                                                • Let me follow that guide myself tomorrow. I’ll report back with my findings. If I get the same results as you, we’ll solve this together.
                                                  – eyoung100
                                                  Jun 30 ’16 at 6:31

                                                I just tried enabling these options. It didn’t work. I also tried with the standard kernel and it didn’t work, then I tried upgrading to kernel 4.4.8-hardened-r1 and it didn’t work.
                                                – RAKK
                                                Jun 30 ’16 at 6:03

                                                I just tried enabling these options. It didn’t work. I also tried with the standard kernel and it didn’t work, then I tried upgrading to kernel 4.4.8-hardened-r1 and it didn’t work.
                                                – RAKK
                                                Jun 30 ’16 at 6:03

                                                What errors did you recurve when trying these? Did you remember to add the kernel to your boot loader configuration? Have you rebooted?
                                                – eyoung100
                                                Jun 30 ’16 at 6:14

                                                What errors did you recurve when trying these? Did you remember to add the kernel to your boot loader configuration? Have you rebooted?
                                                – eyoung100
                                                Jun 30 ’16 at 6:14

                                                Yep, I have rebooted. I don’t get any error message, I just don’t get any kernel log message saying AMD-Vi was picked up.
                                                – RAKK
                                                Jun 30 ’16 at 6:21

                                                Yep, I have rebooted. I don’t get any error message, I just don’t get any kernel log message saying AMD-Vi was picked up.
                                                – RAKK
                                                Jun 30 ’16 at 6:21

                                                To give yourself an idea, on the same computer where I have Gentoo I managed to get PCI passthrough working on Debian Stretch. I even used the steps I took to piece together this guide here: wiki.installgentoo.com/index.php/PCI_passthrough
                                                – RAKK
                                                Jun 30 ’16 at 6:22

                                                To give yourself an idea, on the same computer where I have Gentoo I managed to get PCI passthrough working on Debian Stretch. I even used the steps I took to piece together this guide here: wiki.installgentoo.com/index.php/PCI_passthrough
                                                – RAKK
                                                Jun 30 ’16 at 6:22

                                                Let me follow that guide myself tomorrow. I’ll report back with my findings. If I get the same results as you, we’ll solve this together.
                                                – eyoung100
                                                Jun 30 ’16 at 6:31

                                                Let me follow that guide myself tomorrow. I’ll report back with my findings. If I get the same results as you, we’ll solve this together.
                                                – eyoung100
                                                Jun 30 ’16 at 6:31

                                                up vote
                                                0
                                                down vote

                                                accepted

                                                Finally, after much wailing, complaining and head bashing, I finally figured out what was going on.

                                                As it turns out, IOMMU was working all along, it’s just that the kernel logs weren’t showing it. But the IOMMU driver was there, it was working, and I serendipiously found out when I mistakenly typed ps -ef instead of dmesg like this:

                                                rockshooter ~ # ps -ef | grep -i iommu
                                                root        66     2  0 04:19 ?        00:00:00 [amd_iommu_v2]  
                                                

                                                When I saw that kernel thread running I thought, maybe my IOMMU is actually working? So I performed the same configuration steps I did previously for Debian, and one hour later, lo and behold, I was on my virtual machine hooked up to my graphics card playing some games.

                                                Please save this thread for future reference, because it took me some good 3 weeks to figure this out. I still gave the other poster some well-deserved +50 reputation for bothering with setting up and testing this issue.

                                                share|improve this answer

                                                  up vote
                                                  0
                                                  down vote

                                                  accepted

                                                  Finally, after much wailing, complaining and head bashing, I finally figured out what was going on.

                                                  As it turns out, IOMMU was working all along, it’s just that the kernel logs weren’t showing it. But the IOMMU driver was there, it was working, and I serendipiously found out when I mistakenly typed ps -ef instead of dmesg like this:

                                                  rockshooter ~ # ps -ef | grep -i iommu
                                                  root        66     2  0 04:19 ?        00:00:00 [amd_iommu_v2]  
                                                  

                                                  When I saw that kernel thread running I thought, maybe my IOMMU is actually working? So I performed the same configuration steps I did previously for Debian, and one hour later, lo and behold, I was on my virtual machine hooked up to my graphics card playing some games.

                                                  Please save this thread for future reference, because it took me some good 3 weeks to figure this out. I still gave the other poster some well-deserved +50 reputation for bothering with setting up and testing this issue.

                                                  share|improve this answer

                                                    up vote
                                                    0
                                                    down vote

                                                    accepted

                                                    up vote
                                                    0
                                                    down vote

                                                    accepted

                                                    Finally, after much wailing, complaining and head bashing, I finally figured out what was going on.

                                                    As it turns out, IOMMU was working all along, it’s just that the kernel logs weren’t showing it. But the IOMMU driver was there, it was working, and I serendipiously found out when I mistakenly typed ps -ef instead of dmesg like this:

                                                    rockshooter ~ # ps -ef | grep -i iommu
                                                    root        66     2  0 04:19 ?        00:00:00 [amd_iommu_v2]  
                                                    

                                                    When I saw that kernel thread running I thought, maybe my IOMMU is actually working? So I performed the same configuration steps I did previously for Debian, and one hour later, lo and behold, I was on my virtual machine hooked up to my graphics card playing some games.

                                                    Please save this thread for future reference, because it took me some good 3 weeks to figure this out. I still gave the other poster some well-deserved +50 reputation for bothering with setting up and testing this issue.

                                                    share|improve this answer

                                                    Finally, after much wailing, complaining and head bashing, I finally figured out what was going on.

                                                    As it turns out, IOMMU was working all along, it’s just that the kernel logs weren’t showing it. But the IOMMU driver was there, it was working, and I serendipiously found out when I mistakenly typed ps -ef instead of dmesg like this:

                                                    rockshooter ~ # ps -ef | grep -i iommu
                                                    root        66     2  0 04:19 ?        00:00:00 [amd_iommu_v2]  
                                                    

                                                    When I saw that kernel thread running I thought, maybe my IOMMU is actually working? So I performed the same configuration steps I did previously for Debian, and one hour later, lo and behold, I was on my virtual machine hooked up to my graphics card playing some games.

                                                    Please save this thread for future reference, because it took me some good 3 weeks to figure this out. I still gave the other poster some well-deserved +50 reputation for bothering with setting up and testing this issue.

                                                    share|improve this answer

                                                    share|improve this answer

                                                    share|improve this answer

                                                    answered Jul 9 ’16 at 11:06

                                                    RAKK

                                                    4491626

                                                    4491626

                                                        draft saved
                                                        draft discarded

                                                        Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                                        • Please be sure to answer the question. Provide details and share your research!

                                                        But avoid

                                                        • Asking for help, clarification, or responding to other answers.
                                                        • Making statements based on opinion; back them up with references or personal experience.

                                                        To learn more, see our tips on writing great answers.

                                                        Some of your past answers have not been well-received, and you’re in danger of being blocked from answering.

                                                        Please pay close attention to the following guidance:

                                                        • Please be sure to answer the question. Provide details and share your research!

                                                        But avoid

                                                        • Asking for help, clarification, or responding to other answers.
                                                        • Making statements based on opinion; back them up with references or personal experience.

                                                        To learn more, see our tips on writing great answers.

                                                        draft saved

                                                        draft discarded

                                                        StackExchange.ready(
                                                        function () {
                                                        StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f291297%2fhow-do-i-compile-my-gentoo-kernel-for-amd-iommu%23new-answer’, ‘question_page’);
                                                        }
                                                        );

                                                        Post as a guest

                                                        Required, but never shown

                                                        Required, but never shown

                                                        Required, but never shown

                                                        Required, but never shown

                                                        Required, but never shown

                                                        Required, but never shown

                                                        Required, but never shown

                                                        Required, but never shown

                                                        Required, but never shown

                                                        Ryzen/Threadripper temperature sensors: Which senors are related to which kernel modules and how to enable them

                                                        The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                                        up vote
                                                        1
                                                        down vote

                                                        favorite

                                                        What sensors I can monitor on my AMD Threadripper 1950x on an ASRock x399 Taichi mobo under Linux. It was announced last year that temperature monitoring was working for Ryzen processors and that was supposedly included in the 4.15 kernel, according to this:https://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-Temps-Hwmon-Next. However, it seems the temperatures are offset, which was fixed in kernel 4.18.6 according to this: https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.18.6-k10temp-Correct

                                                        As far as I can tell there is absolutely no talk of per-core temperature monitoring under Linux as is available with Windows.

                                                        However, other sources suggest that I might need to build modules specifically based on my motherboard. These instructions seem to suggest that I can build the appropriate kernel drivers based on the output of sensors-detect: https://linuxconfig.org/monitor-amd-ryzen-temperatures-in-linux-with-latest-kernel-modules

                                                        Accoding to sensors-detect I have nct6775, but I can’t find any sign that that I have the appropriate kernel module (not shown with lsmod, is there someplace else I should look?). Unfortunately, I cannot build from the repository because it is no longer on github.

                                                        So these are my questions:

                                                        1. What drivers and kernel modules give what information? Specifically, which ones give the per-core readings that are available under Windows?

                                                        2. What is the status of temperature drivers for Ryzen under linux: complete, incomplete, hacked together and never-to-be-reliable?

                                                        3. If I can get nct6775 built, what will that give me in addition to the K10 that I already have? Where else might I go to get the source to build them from?

                                                        4. Why is this so poorly documented? Is not having clear info about this a year and a half after release par for the course, are is AMD being unusually unhelpful by industry standards?

                                                        share|improve this question

                                                          up vote
                                                          1
                                                          down vote

                                                          favorite

                                                          What sensors I can monitor on my AMD Threadripper 1950x on an ASRock x399 Taichi mobo under Linux. It was announced last year that temperature monitoring was working for Ryzen processors and that was supposedly included in the 4.15 kernel, according to this:https://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-Temps-Hwmon-Next. However, it seems the temperatures are offset, which was fixed in kernel 4.18.6 according to this: https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.18.6-k10temp-Correct

                                                          As far as I can tell there is absolutely no talk of per-core temperature monitoring under Linux as is available with Windows.

                                                          However, other sources suggest that I might need to build modules specifically based on my motherboard. These instructions seem to suggest that I can build the appropriate kernel drivers based on the output of sensors-detect: https://linuxconfig.org/monitor-amd-ryzen-temperatures-in-linux-with-latest-kernel-modules

                                                          Accoding to sensors-detect I have nct6775, but I can’t find any sign that that I have the appropriate kernel module (not shown with lsmod, is there someplace else I should look?). Unfortunately, I cannot build from the repository because it is no longer on github.

                                                          So these are my questions:

                                                          1. What drivers and kernel modules give what information? Specifically, which ones give the per-core readings that are available under Windows?

                                                          2. What is the status of temperature drivers for Ryzen under linux: complete, incomplete, hacked together and never-to-be-reliable?

                                                          3. If I can get nct6775 built, what will that give me in addition to the K10 that I already have? Where else might I go to get the source to build them from?

                                                          4. Why is this so poorly documented? Is not having clear info about this a year and a half after release par for the course, are is AMD being unusually unhelpful by industry standards?

                                                          share|improve this question

                                                            up vote
                                                            1
                                                            down vote

                                                            favorite

                                                            up vote
                                                            1
                                                            down vote

                                                            favorite

                                                            What sensors I can monitor on my AMD Threadripper 1950x on an ASRock x399 Taichi mobo under Linux. It was announced last year that temperature monitoring was working for Ryzen processors and that was supposedly included in the 4.15 kernel, according to this:https://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-Temps-Hwmon-Next. However, it seems the temperatures are offset, which was fixed in kernel 4.18.6 according to this: https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.18.6-k10temp-Correct

                                                            As far as I can tell there is absolutely no talk of per-core temperature monitoring under Linux as is available with Windows.

                                                            However, other sources suggest that I might need to build modules specifically based on my motherboard. These instructions seem to suggest that I can build the appropriate kernel drivers based on the output of sensors-detect: https://linuxconfig.org/monitor-amd-ryzen-temperatures-in-linux-with-latest-kernel-modules

                                                            Accoding to sensors-detect I have nct6775, but I can’t find any sign that that I have the appropriate kernel module (not shown with lsmod, is there someplace else I should look?). Unfortunately, I cannot build from the repository because it is no longer on github.

                                                            So these are my questions:

                                                            1. What drivers and kernel modules give what information? Specifically, which ones give the per-core readings that are available under Windows?

                                                            2. What is the status of temperature drivers for Ryzen under linux: complete, incomplete, hacked together and never-to-be-reliable?

                                                            3. If I can get nct6775 built, what will that give me in addition to the K10 that I already have? Where else might I go to get the source to build them from?

                                                            4. Why is this so poorly documented? Is not having clear info about this a year and a half after release par for the course, are is AMD being unusually unhelpful by industry standards?

                                                            share|improve this question

                                                            What sensors I can monitor on my AMD Threadripper 1950x on an ASRock x399 Taichi mobo under Linux. It was announced last year that temperature monitoring was working for Ryzen processors and that was supposedly included in the 4.15 kernel, according to this:https://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-Temps-Hwmon-Next. However, it seems the temperatures are offset, which was fixed in kernel 4.18.6 according to this: https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.18.6-k10temp-Correct

                                                            As far as I can tell there is absolutely no talk of per-core temperature monitoring under Linux as is available with Windows.

                                                            However, other sources suggest that I might need to build modules specifically based on my motherboard. These instructions seem to suggest that I can build the appropriate kernel drivers based on the output of sensors-detect: https://linuxconfig.org/monitor-amd-ryzen-temperatures-in-linux-with-latest-kernel-modules

                                                            Accoding to sensors-detect I have nct6775, but I can’t find any sign that that I have the appropriate kernel module (not shown with lsmod, is there someplace else I should look?). Unfortunately, I cannot build from the repository because it is no longer on github.

                                                            So these are my questions:

                                                            1. What drivers and kernel modules give what information? Specifically, which ones give the per-core readings that are available under Windows?

                                                            2. What is the status of temperature drivers for Ryzen under linux: complete, incomplete, hacked together and never-to-be-reliable?

                                                            3. If I can get nct6775 built, what will that give me in addition to the K10 that I already have? Where else might I go to get the source to build them from?

                                                            4. Why is this so poorly documented? Is not having clear info about this a year and a half after release par for the course, are is AMD being unusually unhelpful by industry standards?

                                                            kernel-modules hardware amd temperature sensors

                                                            share|improve this question

                                                            share|improve this question

                                                            share|improve this question

                                                            share|improve this question

                                                            edited Dec 2 at 14:58

                                                            Rui F Ribeiro

                                                            38.5k1479128

                                                            38.5k1479128

                                                            asked Dec 2 at 11:33

                                                            Thoughtcraft

                                                            1619

                                                            1619

                                                                1 Answer
                                                                1

                                                                active

                                                                oldest

                                                                votes

                                                                up vote
                                                                1
                                                                down vote

                                                                accepted

                                                                [deleted answer by OP:] I would still like to know: what exactly is making nct6775 available now?

                                                                There are a lot of attempts at answering the general question in the following link. Unfortunately none of them are comprehensive, so I will try to improve on them. Linux: How to find the device driver used for a device?

                                                                In your case, the sensor device can be found as one of the links shown in ls -l /sys/class/hwmon/*. You could try to extend that command, and find your kernel module immediately:

                                                                ls -l /sys/class/hwmon/*/device/driver/module
                                                                

                                                                However, this command makes some assumptions. It will not work in every case. If the command does not work, narrow it down by checking each individual link in the chain. There are three possible cases.

                                                                1. You have a driver link, but no module link.

                                                                  This means the driver is built in to the kernel! Which would kind of answer your question :-).

                                                                  It is equally possible to ls -l on the driver link. I.e. to see the name of the driver, change the above command to remove the /module part. Often the driver name is the same as the name of the loadable module, but sometimes they are different.

                                                                2. The driver link is not immediately under device, but…

                                                                  If the above command does not work, you might need to replace device with device/device, or so on.

                                                                  The device link takes you to the parent device. But sometimes the driver is on the grandparent device instead, or even further :-).

                                                                3. None of the parent device(s) have a driver link, or there is no parent device link at all.

                                                                  The device link takes you to the parent device. For example, you might have a network device /sys/class/wlan0, and /sys/class/wlan0/device might point to a PCI card which provides wlan0.

                                                                  In your case, I can imagine it not having anything like a device on the standard pci bus. In this case the driver is supposed to define its own custom device, in /sys/devices/platform/. This is exactly what the coretemp driver for my Intel CPU does.

                                                                  But if your driver got this wrong, it would create a device with no parent, and hence no device link. Sensors (hwmon devices) are one of the more obscure child devices; I’ve seen this happen several times before. Looking in ls /sys/devices/virtual/*, I seem to have three devices that get this wrong, and all of them are hwmon devices.

                                                                  If there is no “physical” / parent device – then there can be no driver. This is expected behaviour for genuinely virtual devices, like loopback (lo) or bridge networking devices. It reflects the device model of the Linux kernel. On a physical device, you can remove the driver that is bound to a it, and potentially bind a different driver. It wouldn’t make sense to support this without having a physical device. It’s just unfortunate because there is no equivalent method like this, to find the module that implements a virtual device.


                                                                Contents:

                                                                1. Example results looking in /sys
                                                                2. I found the module name, now…

                                                                1. Example results looking in /sys

                                                                $ cd /sys/class/hwmon/
                                                                $ ls -l *
                                                                total 0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon1 -> ../../devices/virtual/hwmon/hwmon1
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon2 -> ../../devices/virtual/thermal/thermal_zone8/hwmon2
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon3 -> ../../devices/platform/coretemp.0/hwmon/hwmon3
                                                                
                                                                $ ls -l hwmon3/device/driver/module
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:32 /sys/class/hwmon/hwmon3/device/driver/module -> ../../../../module/coretemp
                                                                

                                                                But the other results did not look so helpful :-). What is virtual/thermal/thermal_zone0/hwmon0?

                                                                hwmon devices (and some other types) also have a name. E.g. the iwlwifi sensor, which is really provided by my Intel Wi-Fi card. But the driver is buggy and declared it as a virtual device.

                                                                $ head */name
                                                                ==> hwmon0/name <==
                                                                acpitz
                                                                
                                                                ==> hwmon1/name <==
                                                                dell_smm
                                                                
                                                                ==> hwmon2/name <==
                                                                iwlwifi
                                                                
                                                                ==> hwmon3/name <==
                                                                coretemp
                                                                

                                                                Here’s a different device, where the driver is on the “grandparent”:

                                                                $ ls -l */device/device/driver
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:33 /sys/class/hwmon/hwmon0/device/device/driver -> ../../../../bus/acpi/drivers/thermal
                                                                

                                                                Also there is no module for this driver, because this one is built-in to the kernel. You can confirm this if you can find the corresponding option in the kernel build configuration. This is not necessarily named the same as the module though.

                                                                $ ls -l */device/device/driver/module
                                                                ls: cannot access '*/device/device/driver/module': No such file or directory
                                                                
                                                                $ grep CORETEMP= /boot/config-$(uname -r)
                                                                CONFIG_SENSORS_CORETEMP=m
                                                                $ grep ACPI_THERMAL= /boot/config-$(uname -r)
                                                                CONFIG_ACPI_THERMAL=y
                                                                

                                                                2. I found the module name, now…

                                                                You said you’re not 100% sure what you’ve done. If you’ve found the module name, but you were worried because you can’t remember if you installed it from an unknown website, here are some things you could look at.

                                                                You can reload a module and check the path your module was reloaded from:

                                                                $ modprobe --remove coretemp
                                                                
                                                                $ modprobe -v coretemp
                                                                insmod /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                

                                                                Then you can query your package manager to confirm the module file came from the distribution kernel package. E.g. for RPM:

                                                                $ rpm -q --whatprovides /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                
                                                                $ rpm -q --whatprovides /boot/vmlinuz-$(uname -r)
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                

                                                                Your package manager should also let you verify the installed package files have not been modified.

                                                                It’s not so simple to confirm where the package came from :-). Usually you look at the package name and guess :-). You can get a list of available packages and where they come from e.g. with dnf info kernel, but I don’t think dnf can show the checksum of the RPM file that was installed or of the available RPMs.

                                                                share|improve this answer

                                                                • Thanks… this has also led me to ask another question: unix.stackexchange.com/questions/485548/…
                                                                  – Thoughtcraft
                                                                  Dec 2 at 20:11

                                                                • It seems I have my work cut out for me :/
                                                                  – Thoughtcraft
                                                                  Dec 2 at 21:26

                                                                • @Thoughtcraft did you find a module to tell you what provides the nct6775 sensor device on your system? Please, we’re in suspense now :-). Ah, the hwmon devices are just numbered, you might be wondering which hwmon device is the one you wanted, I kind of skipped that step. I edited my answer , I hope this is clearer, and maybe it helps you.
                                                                  – sourcejedi
                                                                  Dec 2 at 21:41

                                                                Your Answer

                                                                StackExchange.ready(function() {
                                                                var channelOptions = {
                                                                tags: “”.split(” “),
                                                                id: “106”
                                                                };
                                                                initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                                                StackExchange.using(“externalEditor”, function() {
                                                                // Have to fire editor after snippets, if snippets enabled
                                                                if (StackExchange.settings.snippets.snippetsEnabled) {
                                                                StackExchange.using(“snippets”, function() {
                                                                createEditor();
                                                                });
                                                                }
                                                                else {
                                                                createEditor();
                                                                }
                                                                });

                                                                function createEditor() {
                                                                StackExchange.prepareEditor({
                                                                heartbeatType: ‘answer’,
                                                                convertImagesToLinks: false,
                                                                noModals: true,
                                                                showLowRepImageUploadWarning: true,
                                                                reputationToPostImages: null,
                                                                bindNavPrevention: true,
                                                                postfix: “”,
                                                                imageUploader: {
                                                                brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                                                contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                                                allowUrls: true
                                                                },
                                                                onDemand: true,
                                                                discardSelector: “.discard-answer”
                                                                ,immediatelyShowMarkdownHelp:true
                                                                });

                                                                }
                                                                });

                                                                draft saved
                                                                draft discarded

                                                                StackExchange.ready(
                                                                function () {
                                                                StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f485472%2fryzen-threadripper-temperature-sensors-which-senors-are-related-to-which-kernel%23new-answer’, ‘question_page’);
                                                                }
                                                                );

                                                                Post as a guest

                                                                Required, but never shown

                                                                1 Answer
                                                                1

                                                                active

                                                                oldest

                                                                votes

                                                                1 Answer
                                                                1

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                up vote
                                                                1
                                                                down vote

                                                                accepted

                                                                [deleted answer by OP:] I would still like to know: what exactly is making nct6775 available now?

                                                                There are a lot of attempts at answering the general question in the following link. Unfortunately none of them are comprehensive, so I will try to improve on them. Linux: How to find the device driver used for a device?

                                                                In your case, the sensor device can be found as one of the links shown in ls -l /sys/class/hwmon/*. You could try to extend that command, and find your kernel module immediately:

                                                                ls -l /sys/class/hwmon/*/device/driver/module
                                                                

                                                                However, this command makes some assumptions. It will not work in every case. If the command does not work, narrow it down by checking each individual link in the chain. There are three possible cases.

                                                                1. You have a driver link, but no module link.

                                                                  This means the driver is built in to the kernel! Which would kind of answer your question :-).

                                                                  It is equally possible to ls -l on the driver link. I.e. to see the name of the driver, change the above command to remove the /module part. Often the driver name is the same as the name of the loadable module, but sometimes they are different.

                                                                2. The driver link is not immediately under device, but…

                                                                  If the above command does not work, you might need to replace device with device/device, or so on.

                                                                  The device link takes you to the parent device. But sometimes the driver is on the grandparent device instead, or even further :-).

                                                                3. None of the parent device(s) have a driver link, or there is no parent device link at all.

                                                                  The device link takes you to the parent device. For example, you might have a network device /sys/class/wlan0, and /sys/class/wlan0/device might point to a PCI card which provides wlan0.

                                                                  In your case, I can imagine it not having anything like a device on the standard pci bus. In this case the driver is supposed to define its own custom device, in /sys/devices/platform/. This is exactly what the coretemp driver for my Intel CPU does.

                                                                  But if your driver got this wrong, it would create a device with no parent, and hence no device link. Sensors (hwmon devices) are one of the more obscure child devices; I’ve seen this happen several times before. Looking in ls /sys/devices/virtual/*, I seem to have three devices that get this wrong, and all of them are hwmon devices.

                                                                  If there is no “physical” / parent device – then there can be no driver. This is expected behaviour for genuinely virtual devices, like loopback (lo) or bridge networking devices. It reflects the device model of the Linux kernel. On a physical device, you can remove the driver that is bound to a it, and potentially bind a different driver. It wouldn’t make sense to support this without having a physical device. It’s just unfortunate because there is no equivalent method like this, to find the module that implements a virtual device.


                                                                Contents:

                                                                1. Example results looking in /sys
                                                                2. I found the module name, now…

                                                                1. Example results looking in /sys

                                                                $ cd /sys/class/hwmon/
                                                                $ ls -l *
                                                                total 0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon1 -> ../../devices/virtual/hwmon/hwmon1
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon2 -> ../../devices/virtual/thermal/thermal_zone8/hwmon2
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon3 -> ../../devices/platform/coretemp.0/hwmon/hwmon3
                                                                
                                                                $ ls -l hwmon3/device/driver/module
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:32 /sys/class/hwmon/hwmon3/device/driver/module -> ../../../../module/coretemp
                                                                

                                                                But the other results did not look so helpful :-). What is virtual/thermal/thermal_zone0/hwmon0?

                                                                hwmon devices (and some other types) also have a name. E.g. the iwlwifi sensor, which is really provided by my Intel Wi-Fi card. But the driver is buggy and declared it as a virtual device.

                                                                $ head */name
                                                                ==> hwmon0/name <==
                                                                acpitz
                                                                
                                                                ==> hwmon1/name <==
                                                                dell_smm
                                                                
                                                                ==> hwmon2/name <==
                                                                iwlwifi
                                                                
                                                                ==> hwmon3/name <==
                                                                coretemp
                                                                

                                                                Here’s a different device, where the driver is on the “grandparent”:

                                                                $ ls -l */device/device/driver
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:33 /sys/class/hwmon/hwmon0/device/device/driver -> ../../../../bus/acpi/drivers/thermal
                                                                

                                                                Also there is no module for this driver, because this one is built-in to the kernel. You can confirm this if you can find the corresponding option in the kernel build configuration. This is not necessarily named the same as the module though.

                                                                $ ls -l */device/device/driver/module
                                                                ls: cannot access '*/device/device/driver/module': No such file or directory
                                                                
                                                                $ grep CORETEMP= /boot/config-$(uname -r)
                                                                CONFIG_SENSORS_CORETEMP=m
                                                                $ grep ACPI_THERMAL= /boot/config-$(uname -r)
                                                                CONFIG_ACPI_THERMAL=y
                                                                

                                                                2. I found the module name, now…

                                                                You said you’re not 100% sure what you’ve done. If you’ve found the module name, but you were worried because you can’t remember if you installed it from an unknown website, here are some things you could look at.

                                                                You can reload a module and check the path your module was reloaded from:

                                                                $ modprobe --remove coretemp
                                                                
                                                                $ modprobe -v coretemp
                                                                insmod /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                

                                                                Then you can query your package manager to confirm the module file came from the distribution kernel package. E.g. for RPM:

                                                                $ rpm -q --whatprovides /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                
                                                                $ rpm -q --whatprovides /boot/vmlinuz-$(uname -r)
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                

                                                                Your package manager should also let you verify the installed package files have not been modified.

                                                                It’s not so simple to confirm where the package came from :-). Usually you look at the package name and guess :-). You can get a list of available packages and where they come from e.g. with dnf info kernel, but I don’t think dnf can show the checksum of the RPM file that was installed or of the available RPMs.

                                                                share|improve this answer

                                                                • Thanks… this has also led me to ask another question: unix.stackexchange.com/questions/485548/…
                                                                  – Thoughtcraft
                                                                  Dec 2 at 20:11

                                                                • It seems I have my work cut out for me :/
                                                                  – Thoughtcraft
                                                                  Dec 2 at 21:26

                                                                • @Thoughtcraft did you find a module to tell you what provides the nct6775 sensor device on your system? Please, we’re in suspense now :-). Ah, the hwmon devices are just numbered, you might be wondering which hwmon device is the one you wanted, I kind of skipped that step. I edited my answer , I hope this is clearer, and maybe it helps you.
                                                                  – sourcejedi
                                                                  Dec 2 at 21:41

                                                                up vote
                                                                1
                                                                down vote

                                                                accepted

                                                                [deleted answer by OP:] I would still like to know: what exactly is making nct6775 available now?

                                                                There are a lot of attempts at answering the general question in the following link. Unfortunately none of them are comprehensive, so I will try to improve on them. Linux: How to find the device driver used for a device?

                                                                In your case, the sensor device can be found as one of the links shown in ls -l /sys/class/hwmon/*. You could try to extend that command, and find your kernel module immediately:

                                                                ls -l /sys/class/hwmon/*/device/driver/module
                                                                

                                                                However, this command makes some assumptions. It will not work in every case. If the command does not work, narrow it down by checking each individual link in the chain. There are three possible cases.

                                                                1. You have a driver link, but no module link.

                                                                  This means the driver is built in to the kernel! Which would kind of answer your question :-).

                                                                  It is equally possible to ls -l on the driver link. I.e. to see the name of the driver, change the above command to remove the /module part. Often the driver name is the same as the name of the loadable module, but sometimes they are different.

                                                                2. The driver link is not immediately under device, but…

                                                                  If the above command does not work, you might need to replace device with device/device, or so on.

                                                                  The device link takes you to the parent device. But sometimes the driver is on the grandparent device instead, or even further :-).

                                                                3. None of the parent device(s) have a driver link, or there is no parent device link at all.

                                                                  The device link takes you to the parent device. For example, you might have a network device /sys/class/wlan0, and /sys/class/wlan0/device might point to a PCI card which provides wlan0.

                                                                  In your case, I can imagine it not having anything like a device on the standard pci bus. In this case the driver is supposed to define its own custom device, in /sys/devices/platform/. This is exactly what the coretemp driver for my Intel CPU does.

                                                                  But if your driver got this wrong, it would create a device with no parent, and hence no device link. Sensors (hwmon devices) are one of the more obscure child devices; I’ve seen this happen several times before. Looking in ls /sys/devices/virtual/*, I seem to have three devices that get this wrong, and all of them are hwmon devices.

                                                                  If there is no “physical” / parent device – then there can be no driver. This is expected behaviour for genuinely virtual devices, like loopback (lo) or bridge networking devices. It reflects the device model of the Linux kernel. On a physical device, you can remove the driver that is bound to a it, and potentially bind a different driver. It wouldn’t make sense to support this without having a physical device. It’s just unfortunate because there is no equivalent method like this, to find the module that implements a virtual device.


                                                                Contents:

                                                                1. Example results looking in /sys
                                                                2. I found the module name, now…

                                                                1. Example results looking in /sys

                                                                $ cd /sys/class/hwmon/
                                                                $ ls -l *
                                                                total 0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon1 -> ../../devices/virtual/hwmon/hwmon1
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon2 -> ../../devices/virtual/thermal/thermal_zone8/hwmon2
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon3 -> ../../devices/platform/coretemp.0/hwmon/hwmon3
                                                                
                                                                $ ls -l hwmon3/device/driver/module
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:32 /sys/class/hwmon/hwmon3/device/driver/module -> ../../../../module/coretemp
                                                                

                                                                But the other results did not look so helpful :-). What is virtual/thermal/thermal_zone0/hwmon0?

                                                                hwmon devices (and some other types) also have a name. E.g. the iwlwifi sensor, which is really provided by my Intel Wi-Fi card. But the driver is buggy and declared it as a virtual device.

                                                                $ head */name
                                                                ==> hwmon0/name <==
                                                                acpitz
                                                                
                                                                ==> hwmon1/name <==
                                                                dell_smm
                                                                
                                                                ==> hwmon2/name <==
                                                                iwlwifi
                                                                
                                                                ==> hwmon3/name <==
                                                                coretemp
                                                                

                                                                Here’s a different device, where the driver is on the “grandparent”:

                                                                $ ls -l */device/device/driver
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:33 /sys/class/hwmon/hwmon0/device/device/driver -> ../../../../bus/acpi/drivers/thermal
                                                                

                                                                Also there is no module for this driver, because this one is built-in to the kernel. You can confirm this if you can find the corresponding option in the kernel build configuration. This is not necessarily named the same as the module though.

                                                                $ ls -l */device/device/driver/module
                                                                ls: cannot access '*/device/device/driver/module': No such file or directory
                                                                
                                                                $ grep CORETEMP= /boot/config-$(uname -r)
                                                                CONFIG_SENSORS_CORETEMP=m
                                                                $ grep ACPI_THERMAL= /boot/config-$(uname -r)
                                                                CONFIG_ACPI_THERMAL=y
                                                                

                                                                2. I found the module name, now…

                                                                You said you’re not 100% sure what you’ve done. If you’ve found the module name, but you were worried because you can’t remember if you installed it from an unknown website, here are some things you could look at.

                                                                You can reload a module and check the path your module was reloaded from:

                                                                $ modprobe --remove coretemp
                                                                
                                                                $ modprobe -v coretemp
                                                                insmod /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                

                                                                Then you can query your package manager to confirm the module file came from the distribution kernel package. E.g. for RPM:

                                                                $ rpm -q --whatprovides /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                
                                                                $ rpm -q --whatprovides /boot/vmlinuz-$(uname -r)
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                

                                                                Your package manager should also let you verify the installed package files have not been modified.

                                                                It’s not so simple to confirm where the package came from :-). Usually you look at the package name and guess :-). You can get a list of available packages and where they come from e.g. with dnf info kernel, but I don’t think dnf can show the checksum of the RPM file that was installed or of the available RPMs.

                                                                share|improve this answer

                                                                • Thanks… this has also led me to ask another question: unix.stackexchange.com/questions/485548/…
                                                                  – Thoughtcraft
                                                                  Dec 2 at 20:11

                                                                • It seems I have my work cut out for me :/
                                                                  – Thoughtcraft
                                                                  Dec 2 at 21:26

                                                                • @Thoughtcraft did you find a module to tell you what provides the nct6775 sensor device on your system? Please, we’re in suspense now :-). Ah, the hwmon devices are just numbered, you might be wondering which hwmon device is the one you wanted, I kind of skipped that step. I edited my answer , I hope this is clearer, and maybe it helps you.
                                                                  – sourcejedi
                                                                  Dec 2 at 21:41

                                                                up vote
                                                                1
                                                                down vote

                                                                accepted

                                                                up vote
                                                                1
                                                                down vote

                                                                accepted

                                                                [deleted answer by OP:] I would still like to know: what exactly is making nct6775 available now?

                                                                There are a lot of attempts at answering the general question in the following link. Unfortunately none of them are comprehensive, so I will try to improve on them. Linux: How to find the device driver used for a device?

                                                                In your case, the sensor device can be found as one of the links shown in ls -l /sys/class/hwmon/*. You could try to extend that command, and find your kernel module immediately:

                                                                ls -l /sys/class/hwmon/*/device/driver/module
                                                                

                                                                However, this command makes some assumptions. It will not work in every case. If the command does not work, narrow it down by checking each individual link in the chain. There are three possible cases.

                                                                1. You have a driver link, but no module link.

                                                                  This means the driver is built in to the kernel! Which would kind of answer your question :-).

                                                                  It is equally possible to ls -l on the driver link. I.e. to see the name of the driver, change the above command to remove the /module part. Often the driver name is the same as the name of the loadable module, but sometimes they are different.

                                                                2. The driver link is not immediately under device, but…

                                                                  If the above command does not work, you might need to replace device with device/device, or so on.

                                                                  The device link takes you to the parent device. But sometimes the driver is on the grandparent device instead, or even further :-).

                                                                3. None of the parent device(s) have a driver link, or there is no parent device link at all.

                                                                  The device link takes you to the parent device. For example, you might have a network device /sys/class/wlan0, and /sys/class/wlan0/device might point to a PCI card which provides wlan0.

                                                                  In your case, I can imagine it not having anything like a device on the standard pci bus. In this case the driver is supposed to define its own custom device, in /sys/devices/platform/. This is exactly what the coretemp driver for my Intel CPU does.

                                                                  But if your driver got this wrong, it would create a device with no parent, and hence no device link. Sensors (hwmon devices) are one of the more obscure child devices; I’ve seen this happen several times before. Looking in ls /sys/devices/virtual/*, I seem to have three devices that get this wrong, and all of them are hwmon devices.

                                                                  If there is no “physical” / parent device – then there can be no driver. This is expected behaviour for genuinely virtual devices, like loopback (lo) or bridge networking devices. It reflects the device model of the Linux kernel. On a physical device, you can remove the driver that is bound to a it, and potentially bind a different driver. It wouldn’t make sense to support this without having a physical device. It’s just unfortunate because there is no equivalent method like this, to find the module that implements a virtual device.


                                                                Contents:

                                                                1. Example results looking in /sys
                                                                2. I found the module name, now…

                                                                1. Example results looking in /sys

                                                                $ cd /sys/class/hwmon/
                                                                $ ls -l *
                                                                total 0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon1 -> ../../devices/virtual/hwmon/hwmon1
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon2 -> ../../devices/virtual/thermal/thermal_zone8/hwmon2
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon3 -> ../../devices/platform/coretemp.0/hwmon/hwmon3
                                                                
                                                                $ ls -l hwmon3/device/driver/module
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:32 /sys/class/hwmon/hwmon3/device/driver/module -> ../../../../module/coretemp
                                                                

                                                                But the other results did not look so helpful :-). What is virtual/thermal/thermal_zone0/hwmon0?

                                                                hwmon devices (and some other types) also have a name. E.g. the iwlwifi sensor, which is really provided by my Intel Wi-Fi card. But the driver is buggy and declared it as a virtual device.

                                                                $ head */name
                                                                ==> hwmon0/name <==
                                                                acpitz
                                                                
                                                                ==> hwmon1/name <==
                                                                dell_smm
                                                                
                                                                ==> hwmon2/name <==
                                                                iwlwifi
                                                                
                                                                ==> hwmon3/name <==
                                                                coretemp
                                                                

                                                                Here’s a different device, where the driver is on the “grandparent”:

                                                                $ ls -l */device/device/driver
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:33 /sys/class/hwmon/hwmon0/device/device/driver -> ../../../../bus/acpi/drivers/thermal
                                                                

                                                                Also there is no module for this driver, because this one is built-in to the kernel. You can confirm this if you can find the corresponding option in the kernel build configuration. This is not necessarily named the same as the module though.

                                                                $ ls -l */device/device/driver/module
                                                                ls: cannot access '*/device/device/driver/module': No such file or directory
                                                                
                                                                $ grep CORETEMP= /boot/config-$(uname -r)
                                                                CONFIG_SENSORS_CORETEMP=m
                                                                $ grep ACPI_THERMAL= /boot/config-$(uname -r)
                                                                CONFIG_ACPI_THERMAL=y
                                                                

                                                                2. I found the module name, now…

                                                                You said you’re not 100% sure what you’ve done. If you’ve found the module name, but you were worried because you can’t remember if you installed it from an unknown website, here are some things you could look at.

                                                                You can reload a module and check the path your module was reloaded from:

                                                                $ modprobe --remove coretemp
                                                                
                                                                $ modprobe -v coretemp
                                                                insmod /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                

                                                                Then you can query your package manager to confirm the module file came from the distribution kernel package. E.g. for RPM:

                                                                $ rpm -q --whatprovides /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                
                                                                $ rpm -q --whatprovides /boot/vmlinuz-$(uname -r)
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                

                                                                Your package manager should also let you verify the installed package files have not been modified.

                                                                It’s not so simple to confirm where the package came from :-). Usually you look at the package name and guess :-). You can get a list of available packages and where they come from e.g. with dnf info kernel, but I don’t think dnf can show the checksum of the RPM file that was installed or of the available RPMs.

                                                                share|improve this answer

                                                                [deleted answer by OP:] I would still like to know: what exactly is making nct6775 available now?

                                                                There are a lot of attempts at answering the general question in the following link. Unfortunately none of them are comprehensive, so I will try to improve on them. Linux: How to find the device driver used for a device?

                                                                In your case, the sensor device can be found as one of the links shown in ls -l /sys/class/hwmon/*. You could try to extend that command, and find your kernel module immediately:

                                                                ls -l /sys/class/hwmon/*/device/driver/module
                                                                

                                                                However, this command makes some assumptions. It will not work in every case. If the command does not work, narrow it down by checking each individual link in the chain. There are three possible cases.

                                                                1. You have a driver link, but no module link.

                                                                  This means the driver is built in to the kernel! Which would kind of answer your question :-).

                                                                  It is equally possible to ls -l on the driver link. I.e. to see the name of the driver, change the above command to remove the /module part. Often the driver name is the same as the name of the loadable module, but sometimes they are different.

                                                                2. The driver link is not immediately under device, but…

                                                                  If the above command does not work, you might need to replace device with device/device, or so on.

                                                                  The device link takes you to the parent device. But sometimes the driver is on the grandparent device instead, or even further :-).

                                                                3. None of the parent device(s) have a driver link, or there is no parent device link at all.

                                                                  The device link takes you to the parent device. For example, you might have a network device /sys/class/wlan0, and /sys/class/wlan0/device might point to a PCI card which provides wlan0.

                                                                  In your case, I can imagine it not having anything like a device on the standard pci bus. In this case the driver is supposed to define its own custom device, in /sys/devices/platform/. This is exactly what the coretemp driver for my Intel CPU does.

                                                                  But if your driver got this wrong, it would create a device with no parent, and hence no device link. Sensors (hwmon devices) are one of the more obscure child devices; I’ve seen this happen several times before. Looking in ls /sys/devices/virtual/*, I seem to have three devices that get this wrong, and all of them are hwmon devices.

                                                                  If there is no “physical” / parent device – then there can be no driver. This is expected behaviour for genuinely virtual devices, like loopback (lo) or bridge networking devices. It reflects the device model of the Linux kernel. On a physical device, you can remove the driver that is bound to a it, and potentially bind a different driver. It wouldn’t make sense to support this without having a physical device. It’s just unfortunate because there is no equivalent method like this, to find the module that implements a virtual device.


                                                                Contents:

                                                                1. Example results looking in /sys
                                                                2. I found the module name, now…

                                                                1. Example results looking in /sys

                                                                $ cd /sys/class/hwmon/
                                                                $ ls -l *
                                                                total 0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon1 -> ../../devices/virtual/hwmon/hwmon1
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon2 -> ../../devices/virtual/thermal/thermal_zone8/hwmon2
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 17:50 hwmon3 -> ../../devices/platform/coretemp.0/hwmon/hwmon3
                                                                
                                                                $ ls -l hwmon3/device/driver/module
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:32 /sys/class/hwmon/hwmon3/device/driver/module -> ../../../../module/coretemp
                                                                

                                                                But the other results did not look so helpful :-). What is virtual/thermal/thermal_zone0/hwmon0?

                                                                hwmon devices (and some other types) also have a name. E.g. the iwlwifi sensor, which is really provided by my Intel Wi-Fi card. But the driver is buggy and declared it as a virtual device.

                                                                $ head */name
                                                                ==> hwmon0/name <==
                                                                acpitz
                                                                
                                                                ==> hwmon1/name <==
                                                                dell_smm
                                                                
                                                                ==> hwmon2/name <==
                                                                iwlwifi
                                                                
                                                                ==> hwmon3/name <==
                                                                coretemp
                                                                

                                                                Here’s a different device, where the driver is on the “grandparent”:

                                                                $ ls -l */device/device/driver
                                                                lrwxrwxrwx. 1 root root 0 Dec  2 18:33 /sys/class/hwmon/hwmon0/device/device/driver -> ../../../../bus/acpi/drivers/thermal
                                                                

                                                                Also there is no module for this driver, because this one is built-in to the kernel. You can confirm this if you can find the corresponding option in the kernel build configuration. This is not necessarily named the same as the module though.

                                                                $ ls -l */device/device/driver/module
                                                                ls: cannot access '*/device/device/driver/module': No such file or directory
                                                                
                                                                $ grep CORETEMP= /boot/config-$(uname -r)
                                                                CONFIG_SENSORS_CORETEMP=m
                                                                $ grep ACPI_THERMAL= /boot/config-$(uname -r)
                                                                CONFIG_ACPI_THERMAL=y
                                                                

                                                                2. I found the module name, now…

                                                                You said you’re not 100% sure what you’ve done. If you’ve found the module name, but you were worried because you can’t remember if you installed it from an unknown website, here are some things you could look at.

                                                                You can reload a module and check the path your module was reloaded from:

                                                                $ modprobe --remove coretemp
                                                                
                                                                $ modprobe -v coretemp
                                                                insmod /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                

                                                                Then you can query your package manager to confirm the module file came from the distribution kernel package. E.g. for RPM:

                                                                $ rpm -q --whatprovides /lib/modules/4.19.4-200.fc28.x86_64/kernel/drivers/hwmon/coretemp.ko.xz
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                
                                                                $ rpm -q --whatprovides /boot/vmlinuz-$(uname -r)
                                                                kernel-core-4.19.4-200.fc28.x86_64
                                                                

                                                                Your package manager should also let you verify the installed package files have not been modified.

                                                                It’s not so simple to confirm where the package came from :-). Usually you look at the package name and guess :-). You can get a list of available packages and where they come from e.g. with dnf info kernel, but I don’t think dnf can show the checksum of the RPM file that was installed or of the available RPMs.

                                                                share|improve this answer

                                                                share|improve this answer

                                                                share|improve this answer

                                                                edited Dec 3 at 0:03

                                                                answered Dec 2 at 18:38

                                                                sourcejedi

                                                                22.3k43398

                                                                22.3k43398

                                                                • Thanks… this has also led me to ask another question: unix.stackexchange.com/questions/485548/…
                                                                  – Thoughtcraft
                                                                  Dec 2 at 20:11

                                                                • It seems I have my work cut out for me :/
                                                                  – Thoughtcraft
                                                                  Dec 2 at 21:26

                                                                • @Thoughtcraft did you find a module to tell you what provides the nct6775 sensor device on your system? Please, we’re in suspense now :-). Ah, the hwmon devices are just numbered, you might be wondering which hwmon device is the one you wanted, I kind of skipped that step. I edited my answer , I hope this is clearer, and maybe it helps you.
                                                                  – sourcejedi
                                                                  Dec 2 at 21:41

                                                                • Thanks… this has also led me to ask another question: unix.stackexchange.com/questions/485548/…
                                                                  – Thoughtcraft
                                                                  Dec 2 at 20:11

                                                                • It seems I have my work cut out for me :/
                                                                  – Thoughtcraft
                                                                  Dec 2 at 21:26

                                                                • @Thoughtcraft did you find a module to tell you what provides the nct6775 sensor device on your system? Please, we’re in suspense now :-). Ah, the hwmon devices are just numbered, you might be wondering which hwmon device is the one you wanted, I kind of skipped that step. I edited my answer , I hope this is clearer, and maybe it helps you.
                                                                  – sourcejedi
                                                                  Dec 2 at 21:41

                                                                Thanks… this has also led me to ask another question: unix.stackexchange.com/questions/485548/…
                                                                – Thoughtcraft
                                                                Dec 2 at 20:11

                                                                Thanks… this has also led me to ask another question: unix.stackexchange.com/questions/485548/…
                                                                – Thoughtcraft
                                                                Dec 2 at 20:11

                                                                It seems I have my work cut out for me :/
                                                                – Thoughtcraft
                                                                Dec 2 at 21:26

                                                                It seems I have my work cut out for me :/
                                                                – Thoughtcraft
                                                                Dec 2 at 21:26

                                                                @Thoughtcraft did you find a module to tell you what provides the nct6775 sensor device on your system? Please, we’re in suspense now :-). Ah, the hwmon devices are just numbered, you might be wondering which hwmon device is the one you wanted, I kind of skipped that step. I edited my answer , I hope this is clearer, and maybe it helps you.
                                                                – sourcejedi
                                                                Dec 2 at 21:41

                                                                @Thoughtcraft did you find a module to tell you what provides the nct6775 sensor device on your system? Please, we’re in suspense now :-). Ah, the hwmon devices are just numbered, you might be wondering which hwmon device is the one you wanted, I kind of skipped that step. I edited my answer , I hope this is clearer, and maybe it helps you.
                                                                – sourcejedi
                                                                Dec 2 at 21:41

                                                                draft saved
                                                                draft discarded

                                                                Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                                                • Please be sure to answer the question. Provide details and share your research!

                                                                But avoid

                                                                • Asking for help, clarification, or responding to other answers.
                                                                • Making statements based on opinion; back them up with references or personal experience.

                                                                To learn more, see our tips on writing great answers.

                                                                Some of your past answers have not been well-received, and you’re in danger of being blocked from answering.

                                                                Please pay close attention to the following guidance:

                                                                • Please be sure to answer the question. Provide details and share your research!

                                                                But avoid

                                                                • Asking for help, clarification, or responding to other answers.
                                                                • Making statements based on opinion; back them up with references or personal experience.

                                                                To learn more, see our tips on writing great answers.

                                                                draft saved

                                                                draft discarded

                                                                StackExchange.ready(
                                                                function () {
                                                                StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f485472%2fryzen-threadripper-temperature-sensors-which-senors-are-related-to-which-kernel%23new-answer’, ‘question_page’);
                                                                }
                                                                );

                                                                Post as a guest

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Unable to install fglrx

                                                                The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                                                up vote
                                                                -1
                                                                down vote

                                                                favorite

                                                                I’m having a lot of problems installing the package fglrx. This is my system information:

                                                                seraphid@Astrocleyer ~ $ cat /etc/os-release
                                                                NAME="Linux Mint"
                                                                VERSION="18.2 (Sonya)"
                                                                ID=linuxmint
                                                                ID_LIKE=ubuntu
                                                                PRETTY_NAME="Linux Mint 18.2"
                                                                VERSION_ID="18.2"
                                                                HOME_URL="http://www.linuxmint.com/"
                                                                SUPPORT_URL="http://forums.linuxmint.com/"
                                                                BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/"
                                                                VERSION_CODENAME=sonya
                                                                UBUNTU_CODENAME=xenial
                                                                

                                                                and this is my error:

                                                                seraphid@Astrocleyer ~ $ sudo apt-get install fglrx
                                                                Reading package lists... Done
                                                                Building dependency tree       
                                                                Reading state information... Done
                                                                Some packages could not be installed. This may mean that you have
                                                                requested an impossible situation or if you are using the unstable
                                                                distribution that some required packages have not yet been created
                                                                or been moved out of Incoming.
                                                                The following information may help to resolve the situation:
                                                                
                                                                The following packages have unmet dependencies:
                                                                 fglrx : Depends: xorg-video-abi-11 but it is not installable or
                                                                              xorg-video-abi-12 but it is not installable or
                                                                              xorg-video-abi-13 but it is not installable or
                                                                              xorg-video-abi-14 but it is not installable or
                                                                              xorg-video-abi-15 or
                                                                              xorg-video-abi-18 or
                                                                              xorg-video-abi-19
                                                                E: Unable to correct problems, you have held broken packages.
                                                                

                                                                I have tried to clean the broken packages, and installing xserver-xorg-core, but nothing works. The goal of installing fglrx is for installing the catalyst control center from AMD.

                                                                share|improve this question

                                                                • fglrx is not compatible with your xorg version.
                                                                  – Ipor Sircer
                                                                  Nov 29 at 13:50

                                                                • So how can I fix that?
                                                                  – Seraphid
                                                                  Nov 29 at 17:40

                                                                • Send your cv to AMD, wait to being employed, persuade your boss to maintain an abandoned code, work on it, release it.
                                                                  – Ipor Sircer
                                                                  Nov 30 at 13:54

                                                                • So simply I can’t use my graphics card because AMD doesn’t want to? Sounds something marvelous
                                                                  – Seraphid
                                                                  Dec 2 at 14:25

                                                                up vote
                                                                -1
                                                                down vote

                                                                favorite

                                                                I’m having a lot of problems installing the package fglrx. This is my system information:

                                                                seraphid@Astrocleyer ~ $ cat /etc/os-release
                                                                NAME="Linux Mint"
                                                                VERSION="18.2 (Sonya)"
                                                                ID=linuxmint
                                                                ID_LIKE=ubuntu
                                                                PRETTY_NAME="Linux Mint 18.2"
                                                                VERSION_ID="18.2"
                                                                HOME_URL="http://www.linuxmint.com/"
                                                                SUPPORT_URL="http://forums.linuxmint.com/"
                                                                BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/"
                                                                VERSION_CODENAME=sonya
                                                                UBUNTU_CODENAME=xenial
                                                                

                                                                and this is my error:

                                                                seraphid@Astrocleyer ~ $ sudo apt-get install fglrx
                                                                Reading package lists... Done
                                                                Building dependency tree       
                                                                Reading state information... Done
                                                                Some packages could not be installed. This may mean that you have
                                                                requested an impossible situation or if you are using the unstable
                                                                distribution that some required packages have not yet been created
                                                                or been moved out of Incoming.
                                                                The following information may help to resolve the situation:
                                                                
                                                                The following packages have unmet dependencies:
                                                                 fglrx : Depends: xorg-video-abi-11 but it is not installable or
                                                                              xorg-video-abi-12 but it is not installable or
                                                                              xorg-video-abi-13 but it is not installable or
                                                                              xorg-video-abi-14 but it is not installable or
                                                                              xorg-video-abi-15 or
                                                                              xorg-video-abi-18 or
                                                                              xorg-video-abi-19
                                                                E: Unable to correct problems, you have held broken packages.
                                                                

                                                                I have tried to clean the broken packages, and installing xserver-xorg-core, but nothing works. The goal of installing fglrx is for installing the catalyst control center from AMD.

                                                                share|improve this question

                                                                • fglrx is not compatible with your xorg version.
                                                                  – Ipor Sircer
                                                                  Nov 29 at 13:50

                                                                • So how can I fix that?
                                                                  – Seraphid
                                                                  Nov 29 at 17:40

                                                                • Send your cv to AMD, wait to being employed, persuade your boss to maintain an abandoned code, work on it, release it.
                                                                  – Ipor Sircer
                                                                  Nov 30 at 13:54

                                                                • So simply I can’t use my graphics card because AMD doesn’t want to? Sounds something marvelous
                                                                  – Seraphid
                                                                  Dec 2 at 14:25

                                                                up vote
                                                                -1
                                                                down vote

                                                                favorite

                                                                up vote
                                                                -1
                                                                down vote

                                                                favorite

                                                                I’m having a lot of problems installing the package fglrx. This is my system information:

                                                                seraphid@Astrocleyer ~ $ cat /etc/os-release
                                                                NAME="Linux Mint"
                                                                VERSION="18.2 (Sonya)"
                                                                ID=linuxmint
                                                                ID_LIKE=ubuntu
                                                                PRETTY_NAME="Linux Mint 18.2"
                                                                VERSION_ID="18.2"
                                                                HOME_URL="http://www.linuxmint.com/"
                                                                SUPPORT_URL="http://forums.linuxmint.com/"
                                                                BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/"
                                                                VERSION_CODENAME=sonya
                                                                UBUNTU_CODENAME=xenial
                                                                

                                                                and this is my error:

                                                                seraphid@Astrocleyer ~ $ sudo apt-get install fglrx
                                                                Reading package lists... Done
                                                                Building dependency tree       
                                                                Reading state information... Done
                                                                Some packages could not be installed. This may mean that you have
                                                                requested an impossible situation or if you are using the unstable
                                                                distribution that some required packages have not yet been created
                                                                or been moved out of Incoming.
                                                                The following information may help to resolve the situation:
                                                                
                                                                The following packages have unmet dependencies:
                                                                 fglrx : Depends: xorg-video-abi-11 but it is not installable or
                                                                              xorg-video-abi-12 but it is not installable or
                                                                              xorg-video-abi-13 but it is not installable or
                                                                              xorg-video-abi-14 but it is not installable or
                                                                              xorg-video-abi-15 or
                                                                              xorg-video-abi-18 or
                                                                              xorg-video-abi-19
                                                                E: Unable to correct problems, you have held broken packages.
                                                                

                                                                I have tried to clean the broken packages, and installing xserver-xorg-core, but nothing works. The goal of installing fglrx is for installing the catalyst control center from AMD.

                                                                share|improve this question

                                                                I’m having a lot of problems installing the package fglrx. This is my system information:

                                                                seraphid@Astrocleyer ~ $ cat /etc/os-release
                                                                NAME="Linux Mint"
                                                                VERSION="18.2 (Sonya)"
                                                                ID=linuxmint
                                                                ID_LIKE=ubuntu
                                                                PRETTY_NAME="Linux Mint 18.2"
                                                                VERSION_ID="18.2"
                                                                HOME_URL="http://www.linuxmint.com/"
                                                                SUPPORT_URL="http://forums.linuxmint.com/"
                                                                BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/"
                                                                VERSION_CODENAME=sonya
                                                                UBUNTU_CODENAME=xenial
                                                                

                                                                and this is my error:

                                                                seraphid@Astrocleyer ~ $ sudo apt-get install fglrx
                                                                Reading package lists... Done
                                                                Building dependency tree       
                                                                Reading state information... Done
                                                                Some packages could not be installed. This may mean that you have
                                                                requested an impossible situation or if you are using the unstable
                                                                distribution that some required packages have not yet been created
                                                                or been moved out of Incoming.
                                                                The following information may help to resolve the situation:
                                                                
                                                                The following packages have unmet dependencies:
                                                                 fglrx : Depends: xorg-video-abi-11 but it is not installable or
                                                                              xorg-video-abi-12 but it is not installable or
                                                                              xorg-video-abi-13 but it is not installable or
                                                                              xorg-video-abi-14 but it is not installable or
                                                                              xorg-video-abi-15 or
                                                                              xorg-video-abi-18 or
                                                                              xorg-video-abi-19
                                                                E: Unable to correct problems, you have held broken packages.
                                                                

                                                                I have tried to clean the broken packages, and installing xserver-xorg-core, but nothing works. The goal of installing fglrx is for installing the catalyst control center from AMD.

                                                                linux-mint xorg amd fglrx

                                                                share|improve this question

                                                                share|improve this question

                                                                share|improve this question

                                                                share|improve this question

                                                                edited Nov 29 at 13:59

                                                                Rui F Ribeiro

                                                                38.4k1479128

                                                                38.4k1479128

                                                                asked Nov 29 at 13:47

                                                                Seraphid

                                                                4

                                                                4

                                                                • fglrx is not compatible with your xorg version.
                                                                  – Ipor Sircer
                                                                  Nov 29 at 13:50

                                                                • So how can I fix that?
                                                                  – Seraphid
                                                                  Nov 29 at 17:40

                                                                • Send your cv to AMD, wait to being employed, persuade your boss to maintain an abandoned code, work on it, release it.
                                                                  – Ipor Sircer
                                                                  Nov 30 at 13:54

                                                                • So simply I can’t use my graphics card because AMD doesn’t want to? Sounds something marvelous
                                                                  – Seraphid
                                                                  Dec 2 at 14:25

                                                                • fglrx is not compatible with your xorg version.
                                                                  – Ipor Sircer
                                                                  Nov 29 at 13:50

                                                                • So how can I fix that?
                                                                  – Seraphid
                                                                  Nov 29 at 17:40

                                                                • Send your cv to AMD, wait to being employed, persuade your boss to maintain an abandoned code, work on it, release it.
                                                                  – Ipor Sircer
                                                                  Nov 30 at 13:54

                                                                • So simply I can’t use my graphics card because AMD doesn’t want to? Sounds something marvelous
                                                                  – Seraphid
                                                                  Dec 2 at 14:25

                                                                fglrx is not compatible with your xorg version.
                                                                – Ipor Sircer
                                                                Nov 29 at 13:50

                                                                fglrx is not compatible with your xorg version.
                                                                – Ipor Sircer
                                                                Nov 29 at 13:50

                                                                So how can I fix that?
                                                                – Seraphid
                                                                Nov 29 at 17:40

                                                                So how can I fix that?
                                                                – Seraphid
                                                                Nov 29 at 17:40

                                                                Send your cv to AMD, wait to being employed, persuade your boss to maintain an abandoned code, work on it, release it.
                                                                – Ipor Sircer
                                                                Nov 30 at 13:54

                                                                Send your cv to AMD, wait to being employed, persuade your boss to maintain an abandoned code, work on it, release it.
                                                                – Ipor Sircer
                                                                Nov 30 at 13:54

                                                                So simply I can’t use my graphics card because AMD doesn’t want to? Sounds something marvelous
                                                                – Seraphid
                                                                Dec 2 at 14:25

                                                                So simply I can’t use my graphics card because AMD doesn’t want to? Sounds something marvelous
                                                                – Seraphid
                                                                Dec 2 at 14:25

                                                                active

                                                                oldest

                                                                votes

                                                                Your Answer

                                                                StackExchange.ready(function() {
                                                                var channelOptions = {
                                                                tags: “”.split(” “),
                                                                id: “106”
                                                                };
                                                                initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                                                StackExchange.using(“externalEditor”, function() {
                                                                // Have to fire editor after snippets, if snippets enabled
                                                                if (StackExchange.settings.snippets.snippetsEnabled) {
                                                                StackExchange.using(“snippets”, function() {
                                                                createEditor();
                                                                });
                                                                }
                                                                else {
                                                                createEditor();
                                                                }
                                                                });

                                                                function createEditor() {
                                                                StackExchange.prepareEditor({
                                                                heartbeatType: ‘answer’,
                                                                convertImagesToLinks: false,
                                                                noModals: true,
                                                                showLowRepImageUploadWarning: true,
                                                                reputationToPostImages: null,
                                                                bindNavPrevention: true,
                                                                postfix: “”,
                                                                imageUploader: {
                                                                brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                                                contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                                                allowUrls: true
                                                                },
                                                                onDemand: true,
                                                                discardSelector: “.discard-answer”
                                                                ,immediatelyShowMarkdownHelp:true
                                                                });

                                                                }
                                                                });

                                                                draft saved
                                                                draft discarded

                                                                StackExchange.ready(
                                                                function () {
                                                                StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f484919%2funable-to-install-fglrx%23new-answer’, ‘question_page’);
                                                                }
                                                                );

                                                                Post as a guest

                                                                Required, but never shown

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                draft saved
                                                                draft discarded

                                                                Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                                                • Please be sure to answer the question. Provide details and share your research!

                                                                But avoid

                                                                • Asking for help, clarification, or responding to other answers.
                                                                • Making statements based on opinion; back them up with references or personal experience.

                                                                To learn more, see our tips on writing great answers.

                                                                Some of your past answers have not been well-received, and you’re in danger of being blocked from answering.

                                                                Please pay close attention to the following guidance:

                                                                • Please be sure to answer the question. Provide details and share your research!

                                                                But avoid

                                                                • Asking for help, clarification, or responding to other answers.
                                                                • Making statements based on opinion; back them up with references or personal experience.

                                                                To learn more, see our tips on writing great answers.

                                                                draft saved

                                                                draft discarded

                                                                StackExchange.ready(
                                                                function () {
                                                                StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f484919%2funable-to-install-fglrx%23new-answer’, ‘question_page’);
                                                                }
                                                                );

                                                                Post as a guest

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Required, but never shown

                                                                Installing .deb using ‘Ubuntu software center’ vs ‘dpkg’ in terminal [closed]

                                                                The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                                                up vote
                                                                0
                                                                down vote

                                                                favorite

                                                                Installation of .deb file taking too long via Ubuntu software center, it took more than 10 minutes to reach 81% of the installation then I cancelled the installation and used the dpkg -i command to install the same .deb file, measured the time running following command

                                                                time sudo dpkg -i rstudio-xenial-1.1.463-amd64.deb
                                                                
                                                                real    0m12.346s
                                                                user    0m8.122s
                                                                sys     0m1.788s
                                                                

                                                                I tried the same with different .deb files, all of it takes a lot of time in software center but happens in a few seconds in terminal. While installation is happening, I checked gnome-system-monitor, CPU use is barely 20%, so is RAM.

                                                                I am facing a similar issue in Ubuntu 18.04, Ubuntu 16, I checked in two AMD hardware – AMD A10 CPU(desktop) and AMD Ryzen 5 (laptop). Even in terminal, while compiling a code, it takes a lot of time in AMD Ryzen CPU but happens in few seconds in Intel.

                                                                A few specs are mentioned below

                                                                $lspci
                                                                00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Complex
                                                                00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (rev d4)
                                                                00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP Audio Controller
                                                                00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
                                                                00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
                                                                00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40)
                                                                00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
                                                                00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
                                                                00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
                                                                00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
                                                                00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16)
                                                                00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
                                                                00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
                                                                00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
                                                                00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 0)
                                                                00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 2)
                                                                00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 0
                                                                00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 1
                                                                00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 2
                                                                00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 3
                                                                00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 4
                                                                00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 5
                                                                03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
                                                                

                                                                Kernel

                                                                $ uname -a
                                                                Linux k10 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
                                                                

                                                                lshw Video output:

                                                                $sudo lshw -C Video
                                                                *-display                 
                                                                   description: VGA compatible controller
                                                                   product: Kaveri [Radeon R7 Graphics]
                                                                   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
                                                                   physical id: 1
                                                                   bus info: pci@0000:00:01.0
                                                                   version: d4
                                                                   width: 64 bits
                                                                   clock: 33MHz
                                                                   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
                                                                   configuration: driver=amdgpu latency=0
                                                                   resources: irq:36 memory:e0000000-efffffff memory:f0000000-f07fffff ioport:f000(size=256) memory:feb00000-feb3ffff memory:c0000-dffff
                                                                

                                                                In both the hardware and OS (Ubuntu 18 and Ubuntu 16), AMD’s performance is poor.

                                                                Is anyone else facing the similar issue? Is there a good kernel which manages the CPU properly. I see many recommendations to use a kernel >=4.15, I have done that too but performance is still poor.

                                                                share|improve this question

                                                                closed as too broad by Rui F Ribeiro, RalfFriedl, thrig, G-Man, X Tian Nov 30 at 11:25

                                                                Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

                                                                • Fill a bugreport.
                                                                  – Ipor Sircer
                                                                  Nov 29 at 7:58

                                                                • What category it should be filed in?
                                                                  – CCC
                                                                  Nov 29 at 8:45

                                                                up vote
                                                                0
                                                                down vote

                                                                favorite

                                                                Installation of .deb file taking too long via Ubuntu software center, it took more than 10 minutes to reach 81% of the installation then I cancelled the installation and used the dpkg -i command to install the same .deb file, measured the time running following command

                                                                time sudo dpkg -i rstudio-xenial-1.1.463-amd64.deb
                                                                
                                                                real    0m12.346s
                                                                user    0m8.122s
                                                                sys     0m1.788s
                                                                

                                                                I tried the same with different .deb files, all of it takes a lot of time in software center but happens in a few seconds in terminal. While installation is happening, I checked gnome-system-monitor, CPU use is barely 20%, so is RAM.

                                                                I am facing a similar issue in Ubuntu 18.04, Ubuntu 16, I checked in two AMD hardware – AMD A10 CPU(desktop) and AMD Ryzen 5 (laptop). Even in terminal, while compiling a code, it takes a lot of time in AMD Ryzen CPU but happens in few seconds in Intel.

                                                                A few specs are mentioned below

                                                                $lspci
                                                                00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Complex
                                                                00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (rev d4)
                                                                00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP Audio Controller
                                                                00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
                                                                00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
                                                                00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40)
                                                                00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
                                                                00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
                                                                00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
                                                                00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
                                                                00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16)
                                                                00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
                                                                00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
                                                                00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
                                                                00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 0)
                                                                00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 2)
                                                                00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 0
                                                                00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 1
                                                                00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 2
                                                                00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 3
                                                                00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 4
                                                                00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 5
                                                                03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
                                                                

                                                                Kernel

                                                                $ uname -a
                                                                Linux k10 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
                                                                

                                                                lshw Video output:

                                                                $sudo lshw -C Video
                                                                *-display                 
                                                                   description: VGA compatible controller
                                                                   product: Kaveri [Radeon R7 Graphics]
                                                                   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
                                                                   physical id: 1
                                                                   bus info: pci@0000:00:01.0
                                                                   version: d4
                                                                   width: 64 bits
                                                                   clock: 33MHz
                                                                   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
                                                                   configuration: driver=amdgpu latency=0
                                                                   resources: irq:36 memory:e0000000-efffffff memory:f0000000-f07fffff ioport:f000(size=256) memory:feb00000-feb3ffff memory:c0000-dffff
                                                                

                                                                In both the hardware and OS (Ubuntu 18 and Ubuntu 16), AMD’s performance is poor.

                                                                Is anyone else facing the similar issue? Is there a good kernel which manages the CPU properly. I see many recommendations to use a kernel >=4.15, I have done that too but performance is still poor.

                                                                share|improve this question

                                                                closed as too broad by Rui F Ribeiro, RalfFriedl, thrig, G-Man, X Tian Nov 30 at 11:25

                                                                Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

                                                                • Fill a bugreport.
                                                                  – Ipor Sircer
                                                                  Nov 29 at 7:58

                                                                • What category it should be filed in?
                                                                  – CCC
                                                                  Nov 29 at 8:45

                                                                up vote
                                                                0
                                                                down vote

                                                                favorite

                                                                up vote
                                                                0
                                                                down vote

                                                                favorite

                                                                Installation of .deb file taking too long via Ubuntu software center, it took more than 10 minutes to reach 81% of the installation then I cancelled the installation and used the dpkg -i command to install the same .deb file, measured the time running following command

                                                                time sudo dpkg -i rstudio-xenial-1.1.463-amd64.deb
                                                                
                                                                real    0m12.346s
                                                                user    0m8.122s
                                                                sys     0m1.788s
                                                                

                                                                I tried the same with different .deb files, all of it takes a lot of time in software center but happens in a few seconds in terminal. While installation is happening, I checked gnome-system-monitor, CPU use is barely 20%, so is RAM.

                                                                I am facing a similar issue in Ubuntu 18.04, Ubuntu 16, I checked in two AMD hardware – AMD A10 CPU(desktop) and AMD Ryzen 5 (laptop). Even in terminal, while compiling a code, it takes a lot of time in AMD Ryzen CPU but happens in few seconds in Intel.

                                                                A few specs are mentioned below

                                                                $lspci
                                                                00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Complex
                                                                00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (rev d4)
                                                                00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP Audio Controller
                                                                00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
                                                                00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
                                                                00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40)
                                                                00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
                                                                00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
                                                                00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
                                                                00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
                                                                00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16)
                                                                00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
                                                                00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
                                                                00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
                                                                00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 0)
                                                                00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 2)
                                                                00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 0
                                                                00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 1
                                                                00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 2
                                                                00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 3
                                                                00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 4
                                                                00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 5
                                                                03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
                                                                

                                                                Kernel

                                                                $ uname -a
                                                                Linux k10 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
                                                                

                                                                lshw Video output:

                                                                $sudo lshw -C Video
                                                                *-display                 
                                                                   description: VGA compatible controller
                                                                   product: Kaveri [Radeon R7 Graphics]
                                                                   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
                                                                   physical id: 1
                                                                   bus info: pci@0000:00:01.0
                                                                   version: d4
                                                                   width: 64 bits
                                                                   clock: 33MHz
                                                                   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
                                                                   configuration: driver=amdgpu latency=0
                                                                   resources: irq:36 memory:e0000000-efffffff memory:f0000000-f07fffff ioport:f000(size=256) memory:feb00000-feb3ffff memory:c0000-dffff
                                                                

                                                                In both the hardware and OS (Ubuntu 18 and Ubuntu 16), AMD’s performance is poor.

                                                                Is anyone else facing the similar issue? Is there a good kernel which manages the CPU properly. I see many recommendations to use a kernel >=4.15, I have done that too but performance is still poor.

                                                                share|improve this question

                                                                Installation of .deb file taking too long via Ubuntu software center, it took more than 10 minutes to reach 81% of the installation then I cancelled the installation and used the dpkg -i command to install the same .deb file, measured the time running following command

                                                                time sudo dpkg -i rstudio-xenial-1.1.463-amd64.deb
                                                                
                                                                real    0m12.346s
                                                                user    0m8.122s
                                                                sys     0m1.788s
                                                                

                                                                I tried the same with different .deb files, all of it takes a lot of time in software center but happens in a few seconds in terminal. While installation is happening, I checked gnome-system-monitor, CPU use is barely 20%, so is RAM.

                                                                I am facing a similar issue in Ubuntu 18.04, Ubuntu 16, I checked in two AMD hardware – AMD A10 CPU(desktop) and AMD Ryzen 5 (laptop). Even in terminal, while compiling a code, it takes a lot of time in AMD Ryzen CPU but happens in few seconds in Intel.

                                                                A few specs are mentioned below

                                                                $lspci
                                                                00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Complex
                                                                00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (rev d4)
                                                                00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP Audio Controller
                                                                00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Root Port
                                                                00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
                                                                00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
                                                                00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40)
                                                                00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
                                                                00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
                                                                00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
                                                                00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
                                                                00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16)
                                                                00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
                                                                00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
                                                                00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
                                                                00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 0)
                                                                00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 2)
                                                                00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 0
                                                                00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 1
                                                                00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 2
                                                                00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 3
                                                                00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 4
                                                                00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) Processor Function 5
                                                                03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
                                                                

                                                                Kernel

                                                                $ uname -a
                                                                Linux k10 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
                                                                

                                                                lshw Video output:

                                                                $sudo lshw -C Video
                                                                *-display                 
                                                                   description: VGA compatible controller
                                                                   product: Kaveri [Radeon R7 Graphics]
                                                                   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
                                                                   physical id: 1
                                                                   bus info: pci@0000:00:01.0
                                                                   version: d4
                                                                   width: 64 bits
                                                                   clock: 33MHz
                                                                   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
                                                                   configuration: driver=amdgpu latency=0
                                                                   resources: irq:36 memory:e0000000-efffffff memory:f0000000-f07fffff ioport:f000(size=256) memory:feb00000-feb3ffff memory:c0000-dffff
                                                                

                                                                In both the hardware and OS (Ubuntu 18 and Ubuntu 16), AMD’s performance is poor.

                                                                Is anyone else facing the similar issue? Is there a good kernel which manages the CPU properly. I see many recommendations to use a kernel >=4.15, I have done that too but performance is still poor.

                                                                ubuntu linux-kernel kernel-modules amd-graphics amd

                                                                share|improve this question

                                                                share|improve this question

                                                                share|improve this question

                                                                share|improve this question

                                                                asked Nov 29 at 7:55

                                                                CCC

                                                                447

                                                                447

                                                                closed as too broad by Rui F Ribeiro, RalfFriedl, thrig, G-Man, X Tian Nov 30 at 11:25

                                                                Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

                                                                closed as too broad by Rui F Ribeiro, RalfFriedl, thrig, G-Man, X Tian Nov 30 at 11:25

                                                                Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

                                                                • Fill a bugreport.
                                                                  – Ipor Sircer
                                                                  Nov 29 at 7:58

                                                                • What category it should be filed in?
                                                                  – CCC
                                                                  Nov 29 at 8:45

                                                                • Fill a bugreport.
                                                                  – Ipor Sircer
                                                                  Nov 29 at 7:58

                                                                • What category it should be filed in?
                                                                  – CCC
                                                                  Nov 29 at 8:45

                                                                Fill a bugreport.
                                                                – Ipor Sircer
                                                                Nov 29 at 7:58

                                                                Fill a bugreport.
                                                                – Ipor Sircer
                                                                Nov 29 at 7:58

                                                                What category it should be filed in?
                                                                – CCC
                                                                Nov 29 at 8:45

                                                                What category it should be filed in?
                                                                – CCC
                                                                Nov 29 at 8:45

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                virtualisation performance KVM and Boxes on linux host [closed]

                                                                The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                                                up vote
                                                                1
                                                                down vote

                                                                favorite

                                                                I set up a machine with AMD Threadripper 2950 , motherboard GIGABYTE Aorus xtreme and WX7100 GPU. I’m running Fedora 29 at the moment ( tested ubuntu 18.04 and Tumbleweed as well). The machine performance is awesome , However there is very weird system response on virtualisation performance. tried KVM QEMU and Boxes. It it literally impossible to use any graphical work on guest machine.

                                                                Even in very normal workloard, ( I have set 4 cpu cores, 8GB RAM on KVM ), the guest cpu load is nearly %90 in total, and 3.5GB of allocated RAM and used 1.5MB of swap! This makes my virtaul machine very slow and laggy.
                                                                I’m wondering if anyone have experienced such an issue and if you can advise who I can fix this issue?

                                                                share|improve this question

                                                                closed as too broad by Rui F Ribeiro, RalfFriedl, JigglyNaga, Romeo Ninov, schily Nov 21 at 18:17

                                                                Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

                                                                • linux-kvm.org/page/Tuning_KVM – for “graphical work” you should elaborate (what are you trying to do and how is it configured). Virtualization is a wide field (ranges from archaic hardware over server only to full blown gpu-passthrough-gaming) and it’s unclear what you’re asking about specifically…
                                                                  – frostschutz
                                                                  Nov 20 at 22:27

                                                                • Graphical work is not the entire reason for using KVM. I need a specific set of hardware development run on different Linux virtual machine. I did set standard installation of KVM/QEMU. Had some difficulties on spice server and OpenGL setup. However, graphics rendering is not good at all on VM ( Centos 7.5 now ). I’ve been heard that I cannot use GPU passthrough and share GPU RAM between several KVM VMs, if that so, I prefer to have several VMs on a good performance and run all in the same time for my application if I can.
                                                                  – Shahram
                                                                  Nov 20 at 22:57

                                                                up vote
                                                                1
                                                                down vote

                                                                favorite

                                                                I set up a machine with AMD Threadripper 2950 , motherboard GIGABYTE Aorus xtreme and WX7100 GPU. I’m running Fedora 29 at the moment ( tested ubuntu 18.04 and Tumbleweed as well). The machine performance is awesome , However there is very weird system response on virtualisation performance. tried KVM QEMU and Boxes. It it literally impossible to use any graphical work on guest machine.

                                                                Even in very normal workloard, ( I have set 4 cpu cores, 8GB RAM on KVM ), the guest cpu load is nearly %90 in total, and 3.5GB of allocated RAM and used 1.5MB of swap! This makes my virtaul machine very slow and laggy.
                                                                I’m wondering if anyone have experienced such an issue and if you can advise who I can fix this issue?

                                                                share|improve this question

                                                                closed as too broad by Rui F Ribeiro, RalfFriedl, JigglyNaga, Romeo Ninov, schily Nov 21 at 18:17

                                                                Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

                                                                • linux-kvm.org/page/Tuning_KVM – for “graphical work” you should elaborate (what are you trying to do and how is it configured). Virtualization is a wide field (ranges from archaic hardware over server only to full blown gpu-passthrough-gaming) and it’s unclear what you’re asking about specifically…
                                                                  – frostschutz
                                                                  Nov 20 at 22:27

                                                                • Graphical work is not the entire reason for using KVM. I need a specific set of hardware development run on different Linux virtual machine. I did set standard installation of KVM/QEMU. Had some difficulties on spice server and OpenGL setup. However, graphics rendering is not good at all on VM ( Centos 7.5 now ). I’ve been heard that I cannot use GPU passthrough and share GPU RAM between several KVM VMs, if that so, I prefer to have several VMs on a good performance and run all in the same time for my application if I can.
                                                                  – Shahram
                                                                  Nov 20 at 22:57

                                                                up vote
                                                                1
                                                                down vote

                                                                favorite

                                                                up vote
                                                                1
                                                                down vote

                                                                favorite

                                                                I set up a machine with AMD Threadripper 2950 , motherboard GIGABYTE Aorus xtreme and WX7100 GPU. I’m running Fedora 29 at the moment ( tested ubuntu 18.04 and Tumbleweed as well). The machine performance is awesome , However there is very weird system response on virtualisation performance. tried KVM QEMU and Boxes. It it literally impossible to use any graphical work on guest machine.

                                                                Even in very normal workloard, ( I have set 4 cpu cores, 8GB RAM on KVM ), the guest cpu load is nearly %90 in total, and 3.5GB of allocated RAM and used 1.5MB of swap! This makes my virtaul machine very slow and laggy.
                                                                I’m wondering if anyone have experienced such an issue and if you can advise who I can fix this issue?

                                                                share|improve this question

                                                                I set up a machine with AMD Threadripper 2950 , motherboard GIGABYTE Aorus xtreme and WX7100 GPU. I’m running Fedora 29 at the moment ( tested ubuntu 18.04 and Tumbleweed as well). The machine performance is awesome , However there is very weird system response on virtualisation performance. tried KVM QEMU and Boxes. It it literally impossible to use any graphical work on guest machine.

                                                                Even in very normal workloard, ( I have set 4 cpu cores, 8GB RAM on KVM ), the guest cpu load is nearly %90 in total, and 3.5GB of allocated RAM and used 1.5MB of swap! This makes my virtaul machine very slow and laggy.
                                                                I’m wondering if anyone have experienced such an issue and if you can advise who I can fix this issue?

                                                                fedora kvm qemu amd-graphics amd

                                                                share|improve this question

                                                                share|improve this question

                                                                share|improve this question

                                                                share|improve this question

                                                                edited Nov 20 at 22:50

                                                                Rui F Ribeiro

                                                                38.2k1475125

                                                                38.2k1475125

                                                                asked Nov 20 at 22:13

                                                                Shahram

                                                                236

                                                                236

                                                                closed as too broad by Rui F Ribeiro, RalfFriedl, JigglyNaga, Romeo Ninov, schily Nov 21 at 18:17

                                                                Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

                                                                closed as too broad by Rui F Ribeiro, RalfFriedl, JigglyNaga, Romeo Ninov, schily Nov 21 at 18:17

                                                                Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

                                                                • linux-kvm.org/page/Tuning_KVM – for “graphical work” you should elaborate (what are you trying to do and how is it configured). Virtualization is a wide field (ranges from archaic hardware over server only to full blown gpu-passthrough-gaming) and it’s unclear what you’re asking about specifically…
                                                                  – frostschutz
                                                                  Nov 20 at 22:27

                                                                • Graphical work is not the entire reason for using KVM. I need a specific set of hardware development run on different Linux virtual machine. I did set standard installation of KVM/QEMU. Had some difficulties on spice server and OpenGL setup. However, graphics rendering is not good at all on VM ( Centos 7.5 now ). I’ve been heard that I cannot use GPU passthrough and share GPU RAM between several KVM VMs, if that so, I prefer to have several VMs on a good performance and run all in the same time for my application if I can.
                                                                  – Shahram
                                                                  Nov 20 at 22:57

                                                                • linux-kvm.org/page/Tuning_KVM – for “graphical work” you should elaborate (what are you trying to do and how is it configured). Virtualization is a wide field (ranges from archaic hardware over server only to full blown gpu-passthrough-gaming) and it’s unclear what you’re asking about specifically…
                                                                  – frostschutz
                                                                  Nov 20 at 22:27

                                                                • Graphical work is not the entire reason for using KVM. I need a specific set of hardware development run on different Linux virtual machine. I did set standard installation of KVM/QEMU. Had some difficulties on spice server and OpenGL setup. However, graphics rendering is not good at all on VM ( Centos 7.5 now ). I’ve been heard that I cannot use GPU passthrough and share GPU RAM between several KVM VMs, if that so, I prefer to have several VMs on a good performance and run all in the same time for my application if I can.
                                                                  – Shahram
                                                                  Nov 20 at 22:57

                                                                linux-kvm.org/page/Tuning_KVM – for “graphical work” you should elaborate (what are you trying to do and how is it configured). Virtualization is a wide field (ranges from archaic hardware over server only to full blown gpu-passthrough-gaming) and it’s unclear what you’re asking about specifically…
                                                                – frostschutz
                                                                Nov 20 at 22:27

                                                                linux-kvm.org/page/Tuning_KVM – for “graphical work” you should elaborate (what are you trying to do and how is it configured). Virtualization is a wide field (ranges from archaic hardware over server only to full blown gpu-passthrough-gaming) and it’s unclear what you’re asking about specifically…
                                                                – frostschutz
                                                                Nov 20 at 22:27

                                                                Graphical work is not the entire reason for using KVM. I need a specific set of hardware development run on different Linux virtual machine. I did set standard installation of KVM/QEMU. Had some difficulties on spice server and OpenGL setup. However, graphics rendering is not good at all on VM ( Centos 7.5 now ). I’ve been heard that I cannot use GPU passthrough and share GPU RAM between several KVM VMs, if that so, I prefer to have several VMs on a good performance and run all in the same time for my application if I can.
                                                                – Shahram
                                                                Nov 20 at 22:57

                                                                Graphical work is not the entire reason for using KVM. I need a specific set of hardware development run on different Linux virtual machine. I did set standard installation of KVM/QEMU. Had some difficulties on spice server and OpenGL setup. However, graphics rendering is not good at all on VM ( Centos 7.5 now ). I’ve been heard that I cannot use GPU passthrough and share GPU RAM between several KVM VMs, if that so, I prefer to have several VMs on a good performance and run all in the same time for my application if I can.
                                                                – Shahram
                                                                Nov 20 at 22:57

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes

                                                                active

                                                                oldest

                                                                votes