From owner-freebsd-mobile@freebsd.org Sun Oct 15 15:58:22 2017 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55E8DE45AB4; Sun, 15 Oct 2017 15:58:22 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9BEFC7E3FF; Sun, 15 Oct 2017 15:58:21 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v9FFwApA094512; Mon, 16 Oct 2017 02:58:10 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 16 Oct 2017 02:58:10 +1100 (EST) From: Ian Smith To: tech-lists cc: freebsd-hardware@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: problems getting AMD C-70 APU working with powerd/cpufreq In-Reply-To: <20171014212602.GB92751@acer.zyxst.net> Message-ID: <20171016013155.I34192@sola.nimnet.asn.au> References: <20171013123721.GA27736@acer.zyxst.net> <20171014215317.K34192@sola.nimnet.asn.au> <20171014212602.GB92751@acer.zyxst.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Oct 2017 15:58:22 -0000 On Sat, 14 Oct 2017 22:26:02 +0100, tech-lists wrote: > On Sat, Oct 14, 2017 at 10:36:02PM +1100, Ian Smith wrote: > > On Fri, 13 Oct 2017 13:37:21 +0100, tech-lists wrote: > > > system: FreeBSD 11.1-STABLE #0 r324342 > > > > > > # sysctl debug.cpufreq.verbose=1 > > > debug.cpufreq.verbose: 0 -> 1 > > > > This shows that cpufreq was alreasy loaded. It's in the GENERIC kernel. > > Have a good browse through cpufreq(4). > > I can't comment about earlier versions of FreeBSD, but this sysctl is present > on 11.1-stable without cpufreq loaded. I'm using a modified kernel - modified > to the extent that superfluous stuff has been removed, because this machine > is hardware-challenged. Without cpufreq loaded, the following sysctls are > present: > > # sysctl -a | grep cpufreq > debug.cpufreq.verbose: 0 > debug.cpufreq.lowest: 0 Right you are; likely all|most of the debug. tunables and sysctls are. > # uname -i > ACER > # cat /sys/amd64/conf/ACER |grep cpufreq > # > # cat /boot/loader.conf amdtemp_load="YES" > # > > I've known this machine has had issues with cpufreq for a while, but > this is the first time I've sat down to try work out why. This is one > of the reasons why cpufreq isn't in my kernel. > > which is why I was able to > > > > # kldload cpufreq > > > # > > no message Indeed, sorry for bad assumption. However, it poses other questions .. > (I set debug.cpufreq.verbose to 1 in order to hopefully see more > output) However, this is after you've booted, right? Might you need to add cpufreq_load="YES" to /boot/loader.conf, so it's loaded before being needed for detection / attachment during boot probing, perhaps? I may again be misinterpreting how your dmesg arose .. you can select verbose boot or add boot_verbose="YES" and maybe verbose_loading="YES" to loader.conf too .. I often run that way and quote /var/run/dmesg.boot > > > dev.acpi_perf.1.%parent: cpu1 > > > dev.acpi_perf.0.%parent: cpu0 > > > > These are interesting. In cpufreq(4) you'll see acpi_perf is one of the > > absolute frequency control drivers, presumably used (see also in dmesg) > > because the expected driver for AMD processors, powernow, did not attach > > - though your verbose dmesg shows nothing about any failure/s to attach. Again, might this be rather because cpufreq wasn't loaded before boot? > > > dev.cpu.1.cx_usage: 11.14% 88.85% last 156us > > > dev.cpu.1.cx_lowest: C2 > > > > At least you're getting plentiful use of C2 state, though I'm not aware > > how much power saving that might buy you on that AMD CPU. > > Not a lot! ;) The APU is only 9W THD anyway, and assuming it's the same or similar to https://www.notebookcheck.net/AMD-C-Series-C-70-Notebook-Processor.82852.0.html and https://www.notebookcheck.net/Review-Acer-Aspire-One-725-C7Xkk-Notebook.89991.0.html then battery life should be ok? Or maybe was, 3-4 years ago? > One of the reasons I'm interested in powerd/cpufreq is that I beleive it > can make turbo kick in. Apparently this chip has a turbo mode @1.333GHz. As far as I know, from following various 'Turbo' mode descriptions on several Intel CPUs (mine is Core2Duo) - the CPU itself chooses to kick a core into turbo mode when conditions such as total thermal load across cores allows, so that one (or more, with enough cores) may run flat-out for a while when others are relatively idle. That's likely a bit too simplistic, but so is my understanding :) powerd can be used to _prevent_ selection of turbo mode, by setting maximum freq (-M) to a lower freq, where turbo mode freq is represented (symbolically) by the maximum freq +1, eg here: dev.cpu.0.freq_levels: 2401/35000 2400/35000 1600/15000 800/12000 dev.cpu.0.freq: 800 and powerd_flags="-a adp -b adp -i 70 -r 90 -M 2400" disables it (on particular advice for my CPU, which otherwise overheats on buildworld) Mind, I did read one article somewhere suggesting powerd was needed to use turbo mode, but I found several aspects of that piece unconvincing. > might be wrong about that though. Moi aussi :) > > So, there's no dev.cpu.0.freq nor dev.cpu.0.freq_levels - therefore > > powerd has nothing to work with. Its (misleading?) message doesn't mean > > cpufreq not loaded, but that the sysctls powerd relies upon don't exist. In this case you manually loaded cpufreq before running powerd, but I'm not sure that'd be enough - see if it differs any if loaded pre-boot? > [...] > > > Nothing in any of those suggests that this cpu has any other frequency > > available than 1000MHz, which seems quite bizarre to me. Of course it's > > possible FreeBSD hasn't been taught to recognise this particular cpu. > > > > You haven't disabled anything in $BIOS related to power or freq control? > > The bios has only a very limited number of options for this machine - > possibly by design as the machine is a netbook. Options for overclocking are > not present at all. > > > The cpuid output has a heading "Advanced Power Management Feature Flags" > > near the bottom, but none are shown. > > yeah, odd that Well unless booting with cpufreq loaded - assuming you didn't before - provides any more info on why powernow(0) (STILL no manpage!) didn't at least try to attach, I'm out of ideas. If you do get any further, sysctl hw.acpi might shed some light too. cheers, Ian From owner-freebsd-mobile@freebsd.org Mon Oct 16 12:17:46 2017 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 532F1E3916F; Mon, 16 Oct 2017 12:17:46 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 22D7D7E352; Mon, 16 Oct 2017 12:17:45 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CFA7B20BC3; Mon, 16 Oct 2017 08:17:38 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 16 Oct 2017 08:17:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=x99O4Htp74kI/s3CRgzg1I1clTze7PvfNI3jQ2vA+8s=; b=YdZQXu3l 2yfe1ZFP5dKazSDyV0WRAXVvaCVWtIFeh7VDlUX3rqzKDQIzaOfxN7YrUchLI/9o 5EI2OoZAVv03OrOECyqeVSuieVZlLfU/E837rltyOMMBsJcBlcFcZYNWsgBiRZiy EARHc60wi4sBKWJehXajTnubK9oUM2EBY0oOlNXUDYUYchipJOacSKKJmR/1ekuB jmzl07IIwe79+RrpTAjXc7Js5MlTY6LFEZpRvR0esA+6w5O1e4hz2T1DTIGNVa2a JOy+GgYmPXnYFnFZudd1ka69N9AwievR+LZtRqetHF0NJDJ/ehXm/WppFzyOkNct lB5OS8n86kW7Yg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=x99O4Htp74kI/s3CRgzg1I1clTze7 PvfNI3jQ2vA+8s=; b=LFDTqmHe/7PrWknQdjTXv9E0+Yyv4sTg86qlo/sHwqIgP ugJNC83Hy/jWRTfD1UwnSiCEEmfoNFylmzNrY8NwH6+ZEtNVeokIj9EXcoRzhgII /fqo3PYr9sIUMhpJF43MyYGzRZndsnbX2SbrBABx8kpxTyHjDnN0bExmmHiHzM6V YZqOjDuy15Fj0uPZ2gysts+2OvcwAvCu+7EKyzomPNiHh99XA0eMnMVK9+PcDFU1 ayMidOh3kpjpWLaArSew6FHhrGeeYlsFcLgYSN/XAgpL/AniuRotYOFzytaB9bDe y9TOdA/gqzslEw4H9cVIGa5QNIGzIrjVC+QiNciyg== X-ME-Sender: Received: from acer.zyxst.net (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 1DB547FA5C; Mon, 16 Oct 2017 08:17:38 -0400 (EDT) Date: Mon, 16 Oct 2017 13:17:36 +0100 From: tech-lists To: freebsd-hardware@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: problems getting AMD C-70 APU working with powerd/cpufreq Message-ID: <20171016121735.GA73795@acer.zyxst.net> Mail-Followup-To: freebsd-hardware@freebsd.org, freebsd-mobile@freebsd.org References: <20171013123721.GA27736@acer.zyxst.net> <20171014215317.K34192@sola.nimnet.asn.au> <20171014212602.GB92751@acer.zyxst.net> <20171016013155.I34192@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20171016013155.I34192@sola.nimnet.asn.au> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 12:17:46 -0000 Hi, On Mon, Oct 16, 2017 at 02:58:10AM +1100, Ian Smith wrote: >On Sat, 14 Oct 2017 22:26:02 +0100, tech-lists wrote: > > On Sat, Oct 14, 2017 at 10:36:02PM +1100, Ian Smith wrote: > > > On Fri, 13 Oct 2017 13:37:21 +0100, tech-lists wrote: >However, this is after you've booted, right? Might you need to add >cpufreq_load="YES" to /boot/loader.conf, so it's loaded before being >needed for detection / attachment during boot probing, perhaps? ok tried that. I get cpufreq.ko loaded in the kernel via /boot/loader.conf but still I get $ sudo powerd -v powerd: no cpufreq(4) support -- aborting: No such file or directory >I may again be misinterpreting how your dmesg arose .. you can select >verbose boot or add boot_verbose="YES" and maybe verbose_loading="YES" >to loader.conf too .. I often run that way and quote /var/run/dmesg.boot selected at boot >Again, might this be rather because cpufreq wasn't loaded before boot? unfortunately, with it loaded in loader.conf seems to not make any difference. >then battery life should be ok? Or maybe was, 3-4 years ago? difficult to say, and there is a story behind that. [0] >Well unless booting with cpufreq loaded - assuming you didn't before - >provides any more info on why powernow(0) (STILL no manpage!) didn't at >least try to attach, I'm out of ideas. > >If you do get any further, sysctl hw.acpi might shed some light too. I have set hw.acpi.verbose=1 in /etc/sysctl.conf for obvious reasons $ sudo sysctl -a | grep hw.acpi hw.acpi.thermal.tz0._TSP: 40 hw.acpi.thermal.tz0._TC2: 3 hw.acpi.thermal.tz0._TC1: 2 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._CRT: 100.1C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._PSV: 94.1C hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0.passive_cooling: 1 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.temperature: 70.1C hw.acpi.thermal.user_override: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.min_runtime: 0 hw.acpi.battery.info_expire: 5 hw.acpi.battery.units: 1 hw.acpi.battery.state: 0 hw.acpi.battery.time: -1 hw.acpi.battery.life: 100 hw.acpi.acline: 1 hw.acpi.cpu.cx_lowest: C2 hw.acpi.reset_video: 0 hw.acpi.handle_reboot: 1 hw.acpi.disable_on_reboot: 0 hw.acpi.verbose: 1 hw.acpi.s4bios: 0 hw.acpi.sleep_delay: 1 hw.acpi.suspend_state: S3 hw.acpi.standby_state: NONE hw.acpi.lid_switch_state: NONE hw.acpi.sleep_button_state: S3 hw.acpi.power_button_state: S5 [0] would you beleive this netbook was set at the factory to load windows 8 installation!! When I saw how it was struggling, I aborted the process and installed linux mint as a stopgap, thinking maybe install freebsd later when there was more time. Leading to this situation [1] So for a while it was used as a mint netbook, then hd errors started happening, so installed freebsd with the then new option of root-on-zfs and used it as a hobby/dev server that came with built-in UPS (ie the netbook battery). While configured like this, it was permanently plugged into AC and wired ethernet. It was set up this way for a couple of years. Then my bigger, more powerful laptop died, so re-purposed the netbook to be a proper netbook, along the way replacing the hd with a SSD, upgrading ram from 4GB to 8GB [1]. It's now running smoothly but the battery needs replacing as the capacity is 70% of what it was. It manages about 2 hrs, longer if the screen is off, but this is another problem [3]. I'm persisting in trying to get this device working as I'd like because the form factor and build quality is excellent and the wireless is well supported (Atheros AR9485) [1] bios upgrades seem to require windows being present. It's a windows executable file [4] [5] [2] somehow the bios acquired a password. I don't know the password. [5] All I can do is to select bootable media, all other functions and access to the bios require a password. [3] there are function keys to turn up and down the brightness. Right now it's at 100% brightness and the function keys don't work under FreeBSD (they may have done under Mint, I can't remember). The screen will automatically turn off after 10 mins of keyboard non-use. [4] I have a windows 8 key but no windows, and I don't own any windows computers, not for a long time. [5] I think swapping out the hardware made it "acquire" a "password" I'll try to get some diagnostics via linux mint, booting from usb3. Have tried via booting to freedos but the executable seems to require actual windows :( ISTR acpi being turned on in the bios. But there's nothing much tunable in there. That and selecting boot media are about it. many thanks, -- J. From owner-freebsd-mobile@freebsd.org Tue Oct 17 22:23:17 2017 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C82E0E49233 for ; Tue, 17 Oct 2017 22:23:17 +0000 (UTC) (envelope-from Scoobi_doo@yahoo.com) Received: from sonic308-3.consmr.mail.bf2.yahoo.com (sonic308-3.consmr.mail.bf2.yahoo.com [74.6.130.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8B5EC147E for ; Tue, 17 Oct 2017 22:23:17 +0000 (UTC) (envelope-from Scoobi_doo@yahoo.com) X-YMail-OSG: yrbReKIVM1mG3dHXMdFj_DB5E2pz8m95_u59mq7aozExSDnQCKIyW1.f0cnSt72 HHWyzjq2sdi5vmrTCS1bUs516mAHlbYjE88DngGYniXcKUt1c0GVxIGHdi3h2kCo9eu0S71d64Vu YicXvs0G2uuZHM56LEa2_HFtSNhY0iEtxDYbzWJA6BhFn_WJ5gLrjQzMO4OKGX3FilugOpEmHeP6 GivBb5Ed8sktNdjtoLtJXcr7gWMXUvQM7.ff6a1TfggzYWHMB_ENusxem.B.zw6e1ngjLz1XeL9J M60Q3AyO_DXHskfiQ003T4iK..4B9xGOcKpkKn21qklK1tnJG65pstm0g8lQDLjfD9GpL7IjPg.n Hy7esfkdVJHIjWfaKaT7HYMpYuFtq5ZZ6iUrvKipKlFMakU89wSrppSrVSe08SK_ZsLpXBbg0GfP mqLrqmOFoSemoW5C7hPbt41zovO2B4_O1_eyAHaBrdNsgaZCZxENA5GC8lF7PL23rBaCEjFU- Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.bf2.yahoo.com with HTTP; Tue, 17 Oct 2017 22:23:10 +0000 Received: from [127.0.0.1] by smtp230.mail.bf1.yahoo.com with NNFMP; 17 Oct 2017 22:23:08 -0000 X-Yahoo-Newman-Id: 426197.40812.bm@smtp230.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: yrbReKIVM1mG3dHXMdFj_DB5E2pz8m95_u59mq7aozExSDn QCKIyW1.f0cnSt72HHWyzjq2sdi5vmrTCS1bUs516mAHlbYjE88DngGYniXc KUt1c0GVxIGHdi3h2kCo9eu0S71d64VuYicXvs0G2uuZHM56LEa2_HFtSNhY 0iEtxDYbzWJA6BhFn_WJ5gLrjQzMO4OKGX3FilugOpEmHeP6GivBb5Ed8skt NdjtoLtJXcr7gWMXUvQM7.ff6a1TfggzYWHMB_ENusxem.B.zw6e1ngjLz1X eL9JM60Q3AyO_DXHskfiQ003T4iK..4B9xGOcKpkKn21qklK1tnJG65pstm0 g8lQDLjfD9GpL7IjPg.nHy7esfkdVJHIjWfaKaT7HYMpYuFtq5ZZ6iUrvKip KlFMakU89wSrppSrVSe08SK_ZsLpXBbg0GfPmqLrqmOFoSemoW5C7hPbt41z ovO2B4_O1_eyAHaBrdNsgaZCZxENA5GC8lF7PL23rBaCEjFU- X-Yahoo-SMTP: 9sPoSQ2swBBlERuQ.0vs8XLc_MeClW0- Subject: Re: problems getting AMD C-70 APU working with powerd/cpufreq To: freebsd-hardware@freebsd.org, freebsd-mobile@freebsd.org, tech-lists References: <20171013123721.GA27736@acer.zyxst.net> <20171014215317.K34192@sola.nimnet.asn.au> <20171014212602.GB92751@acer.zyxst.net> <20171016013155.I34192@sola.nimnet.asn.au> <20171016121735.GA73795@acer.zyxst.net> From: Anthony Jenkins Message-ID: Date: Tue, 17 Oct 2017 18:23:06 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171016121735.GA73795@acer.zyxst.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 22:23:17 -0000 On 10/16/2017 08:17, tech-lists wrote: > Hi, > > On Mon, Oct 16, 2017 at 02:58:10AM +1100, Ian Smith wrote: >> On Sat, 14 Oct 2017 22:26:02 +0100, tech-lists wrote: >> > On Sat, Oct 14, 2017 at 10:36:02PM +1100, Ian Smith wrote: >> > > On Fri, 13 Oct 2017 13:37:21 +0100, tech-lists wrote: > >> However, this is after you've booted, right?  Might you need to add >> cpufreq_load="YES" to /boot/loader.conf, so it's loaded before being >> needed for detection / attachment during boot probing, perhaps? > > ok tried that. I get cpufreq.ko loaded in the kernel via > /boot/loader.conf but still I get > > $ sudo powerd -v > powerd: no cpufreq(4) support -- aborting: No such file or directory > cpufreq(4) does not support AMD processor family 0x14 (20), which I believe your dmesg showed your processor to be. I had added support for controlling the frequency on some later AMD families last year, but the AMD documentation for the 0x14 family is pretty complicated for my tiny brain.  The other families control processor frequency with a single register, but AFACT you use P-states on family 0x14.  You can have up to 8 P-states, each of which specifies a power/frequency configuration.  If someone could point me to a reference for controlling the frequency for this family, I could submit something for review...no idea what Linux does for this family. Anthony From owner-freebsd-mobile@freebsd.org Wed Oct 18 11:42:46 2017 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D21AAE359C1; Wed, 18 Oct 2017 11:42:46 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A06297565A; Wed, 18 Oct 2017 11:42:46 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 988612103B; Wed, 18 Oct 2017 07:42:44 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 18 Oct 2017 07:42:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=sNEw9aFfdtJms6gpR5FM/fSAsfQ3K aaCfuHQeTPPGqY=; b=omQepHV8I+2OdJ5cJ5TOEMsJDXSKVDQaz+AXb8uUOR8dw HRkqkBeAlx+T7dll3otYSwjQxywaT9w+IShIJIYOtLqYp5wQoDYyOlCHA9/F0Cog oY99P/rUI0MjYQxdl4cir/HRgW6WdA5ZcpuBOaw8MxS98uKZUxFk9ov8BiQ6sbN0 gaVl2HthimrkNsjtBpLi+py6QPj/TusHPEeKsc9NjiN5briMDwr+HHwSbG+eV5/C SU/UGj7wvQ+bta+ufj4zObRSAX2GdGO84GtdfkF/StET2PhgwYKcqRbRX3hI+qq1 y8X3ivyxiIyFmAXkzxK0FnaMIsCe59DfLg3eClSZQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=sNEw9a FfdtJms6gpR5FM/fSAsfQ3KaaCfuHQeTPPGqY=; b=OFpdfxrbRoi9h37lFGtMgy qY4j0McjLGSS+kdFActFZAG/Leev8P16omzR1NQbMIkSjxic2YbjDosYIe8U57CA yZEptLtmjqNyR7/TivaeVKw+Gk3vsUdveKyx8cfx8h9kyZJCVn3/LV0j9imTn7zQ cXbg4sfWhbe3y6gliIvW28hlQ4dBeRGeSc0KBQIsbonuSvGddaJm2uGFShkngwz1 HgdHXBVaAYwvBJCmJnIqCaURWkJd9aIeUwvCw7eG+HYfILdN6OR7aNpCVXgIS8ql 2DhjhlosYIARD3rpmPzs05c7HyDEYDgkpTEo57qrvftyhZK2xtvVOR5VzFkc1/Gw == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 1CEC97F3AB; Wed, 18 Oct 2017 07:42:44 -0400 (EDT) Date: Wed, 18 Oct 2017 12:42:42 +0100 From: tech-lists To: freebsd-hardware@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: problems getting AMD C-70 APU working with powerd/cpufreq Message-ID: <20171018114241.GA991@desktop.parsley.growveg.org> Mail-Followup-To: freebsd-hardware@freebsd.org, freebsd-mobile@freebsd.org References: <20171013123721.GA27736@acer.zyxst.net> <20171014215317.K34192@sola.nimnet.asn.au> <20171014212602.GB92751@acer.zyxst.net> <20171016013155.I34192@sola.nimnet.asn.au> <20171016121735.GA73795@acer.zyxst.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 11:42:46 -0000 On Tue, Oct 17, 2017 at 06:23:06PM -0400, Anthony Jenkins wrote: >cpufreq(4) does not support AMD processor family 0x14 (20), which I >believe your dmesg showed your processor to be. aha! >I had added support for controlling the frequency on some later AMD >families last year, but the AMD documentation for the 0x14 family is >pretty complicated for my tiny brain.  The other families control >processor frequency with a single register, but AFACT you use P-states >on family 0x14.  You can have up to 8 P-states, each of which specifies >a power/frequency configuration.  If someone could point me to a >reference for controlling the frequency for this family, I could submit >something for review...no idea what Linux does for this family. Would it help if I were to get hardware output from booting temporarily to linux mint? many thanks, -- J. From owner-freebsd-mobile@freebsd.org Sat Oct 21 13:15:40 2017 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE252E55E23; Sat, 21 Oct 2017 13:15:40 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A10F983E0F; Sat, 21 Oct 2017 13:15:40 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B0AEB20D40; Sat, 21 Oct 2017 09:15:38 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Sat, 21 Oct 2017 09:15:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=kC7zZpwOAkUY0pjXAe1PWVF7fj6bL 5XZkIQio3u7Wx4=; b=slVWqu4JOZ2l6cLzJBUYLK+FdoIPdnJbXecYjcn9jKLRn u1d/HMO9TdwrQruC6dAYX2V40tBuM5/7JE4fL1jRHmh9UZge9PHNmH1Er4lkxh4u 8Uka8cTNzlmqCQt9gn89S3wxlKDmZZN/9ULeMQ9d9miB4ds3EXAKf96cWGBt1UjP wczru/VRgB0qoyludBeodwC2cBPmzFtWXzE4NQMjJlkMHTpQgUAyRVlCQRRzE7fO m+q2Whr+jWvJQyeg8EL50UFnB8tY0kEJZb5KaLu2MUK9rBw27o+S88RnWWZFzfoA HlQuL4autfci/GjwgkLbW+bEjgnzwx4q5T/Sy0D+A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=kC7zZp wOAkUY0pjXAe1PWVF7fj6bL5XZkIQio3u7Wx4=; b=qCtOyzrs7/HHZ5cV1nKzuS DqOypKT2ha6cjyy/D3fSHcSZPJprg2b3xZDiaxoeK2FMrHcntPyhRoaY7/WQ4SXn 7ozCeLP/YlG1e74rgjSfSkat46UCxNsCAyzUvLpVUGvo1Y2sORIciKhaDjOk7NSN JtpvEEKnwAAYUNSHprIz8Vyiob4ZrM90LhpjBpTOexDZWzDEB9Zv17Sm2JxZMarv dgoBc2tSYrFPl0HIOyNCDkYDcvlQXpxOF3GtjCKEmYmJTZl09Ge/jOd4MNWGMlQr RFilnBN1QUZio+9zMLocqJb7NRzMNtBFMqsHpW+TyVVv0xF3L+H3BCuD2pXBSY6Q == X-ME-Sender: Received: from acer (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 193DE2484B; Sat, 21 Oct 2017 09:15:38 -0400 (EDT) Date: Sat, 21 Oct 2017 14:15:36 +0100 From: tech-lists To: freebsd-mobile@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: problems getting AMD C-70 APU working with powerd/cpufreq Message-ID: <20171021131535.GA2771@acer> Mail-Followup-To: freebsd-mobile@freebsd.org, freebsd-hardware@freebsd.org References: <20171013123721.GA27736@acer.zyxst.net> <20171014215317.K34192@sola.nimnet.asn.au> <20171014212602.GB92751@acer.zyxst.net> <20171016013155.I34192@sola.nimnet.asn.au> <20171016121735.GA73795@acer.zyxst.net> <20171018114241.GA991@desktop.parsley.growveg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20171018114241.GA991@desktop.parsley.growveg.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 13:15:41 -0000 On Wed, Oct 18, 2017 at 12:42:42PM +0100, tech-lists wrote: >On Tue, Oct 17, 2017 at 06:23:06PM -0400, Anthony Jenkins wrote: >>cpufreq(4) does not support AMD processor family 0x14 (20), which I >>believe your dmesg showed your processor to be. > >aha! > >>I had added support for controlling the frequency on some later AMD >>families last year, but the AMD documentation for the 0x14 family is >>pretty complicated for my tiny brain.  The other families control >>processor frequency with a single register, but AFACT you use P-states >>on family 0x14.  You can have up to 8 P-states, each of which specifies >>a power/frequency configuration.  If someone could point me to a >>reference for controlling the frequency for this family, I could submit >>something for review...no idea what Linux does for this family. > >Would it help if I were to get hardware output from booting temporarily >to linux mint? [thought I'd try it anyway] Linux info here: https://www.zyxst.net/txt/amd-c70-netbook/linux-dmesg-amdc70.txt https://www.zyxst.net/txt/amd-c70-netbook/linux-cpufreq-info-amdc70.txt cpufreq appears to be working on linux. Because of this and that brightness control works, I've installed linux mint permanently. If you need me to, I can easily boot into freebsd to run tests; equally can run tests from linux. I'd prefer to run freebsd, but the inability to turn down screen brightness was a showstopper. many thanks, -- J.