- This topic has 6 replies, 4 voices, and was last updated Dec 27-10:14 am by Currock.
-
Posts
-
Currock
Antix funktioniert so weit.
Jetzt habe ich noch ein paar Frage:
Der CPU-Takt scheint festgelegt zu sein: 800 MHz bei Akkubetrieb, 1600 MHz bei Netzbetrieb.
Kann man da nicht Einstellungen benutzen, die z.B. Lastabhängig die Frequenz einstellen oder z.B. abhängig von der Akkuladung?Hier mal ein inxi -Fx (MAC-Adressen gelöscht)
System: Host: Arrow Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: IceWM 2.0.0 Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Laptop System: ASUSTeK product: 901 v: x.x serial: <root required> Mobo: ASUSTeK model: 901 v: x.xx serial: <root required> BIOS: American Megatrends v: 2103 date: 06/11/2009 Battery: ID-1: BAT0 charge: 23.5 Wh condition: 43.8/55.3 Wh (79%) model: ASUS 901 status: Charging CPU: Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell rev: 2 L2 cache: 512 KiB flags: nx pae sse sse2 sse3 ssse3 bogomips: 6400 Speed: 1333 MHz max: 1333 MHz Core speeds (MHz): 1: 1333 2: 1333 Graphics: Device-1: Intel Mobile 945GSE Express Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1024x600~60Hz OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6 direct render: Yes Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.9.235-antix.1-486-smp Network: Device-1: Ralink RT2790 Wireless 802.11n 1T/2R PCIe driver: rt2800pci v: 2.3.0 port: 0400 bus ID: 01:00.0 IF: wlan1 state: up mac: Device-2: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet vendor: ASUSTeK driver: ATL1E v: N/A port: ec80 bus ID: 04:00.0 IF: eth0 state: down mac: Drives: Local Storage: total: 266.54 GiB used: 82.41 GiB (30.9%) ID-1: /dev/sda vendor: Super Talent model: STT FPM32GLSE size: 29.82 GiB ID-2: /dev/sdb vendor: ASUS model: PHISON SSD size: 3.76 GiB ID-3: /dev/sdc type: USB model: Single Flash Reader size: 232.96 GiB Partition: ID-1: / size: 27.22 GiB used: 16.38 GiB (60.2%) fs: ext4 dev: /dev/sda1 ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 61.0 C mobo: N/A Fan Speeds (RPM): cpu: 1430 Info: Processes: 161 Uptime: 45m Memory: 1.96 GiB used: 1019.1 MiB (50.8%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36
Xecure
Sorry for answering in English.
I think the CPU limit when on battery mode is related to a tlp setting.
Could you also give us the output of:
sudo tlp-stat -p
when connected to power and then the same output when connected to battery?Probably one of the Processor scaling options in /etc/tlp.conf needs to be changed, so it can use a greater frequency when on battery mode.
Here is a link related to TLP Processor options in case someone else cannot give any advice, so we can study it after performing different tests:
https://linrunner.de/tlp/settings/processor.htmlantiX Live system enthusiast.
General Live Boot Parameters for antiX.Hi,Englisch lesen ist kein Problem. Aber wenn ich versuche, englisch zu schreiben könnte es lustige neue Kreationen geben.
Hier ist die tlp-stat mit Netzteil:
--- TLP 1.3.1 -------------------------------------------- +++ Processor CPU model = Intel(R) Atom(TM) CPU N270 @ 1.60GHz /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver = acpi-cpufreq /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor = performance /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors = conservative userspace powersave ondemand performance schedutil /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies = 1600000 1333000 1067000 800000 [kHz] /sys/devices/system/cpu/cpu1/cpufreq/scaling_driver = acpi-cpufreq /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor = performance /sys/devices/system/cpu/cpu1/cpufreq/scaling_available_governors = conservative userspace powersave ondemand performance schedutil /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu1/cpufreq/scaling_available_frequencies = 1600000 1333000 1067000 800000 [kHz] /sys/devices/system/cpu/cpufreq/boost = (not available) Intel EPB: unsupported CPU. /sys/module/workqueue/parameters/power_efficient = Y /proc/sys/kernel/nmi_watchdog = (not available)Und hier die mit Batterie:
--- TLP 1.3.1 -------------------------------------------- +++ Processor CPU model = Intel(R) Atom(TM) CPU N270 @ 1.60GHz /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver = acpi-cpufreq /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor = performance /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors = conservative userspace powersave ondemand performance schedutil /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies = 1600000 1333000 1067000 800000 [kHz] /sys/devices/system/cpu/cpu1/cpufreq/scaling_driver = acpi-cpufreq /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor = performance /sys/devices/system/cpu/cpu1/cpufreq/scaling_available_governors = conservative userspace powersave ondemand performance schedutil /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu1/cpufreq/scaling_available_frequencies = 1600000 1333000 1067000 800000 [kHz] /sys/devices/system/cpu/cpufreq/boost = (not available) Intel EPB: unsupported CPU. /sys/module/workqueue/parameters/power_efficient = Y /proc/sys/kernel/nmi_watchdog = (not available)In der /etc/tlp.conf sind alle Zeilen auskommentiert.
Xecure
No problem. A few other users also post in their language and the translator helps us figure out what each of us are trying to say.
There is no change at all between both outputs, so there doesn’t seem to be anything overwriting the CPU scaling options. I would even say they are not working properly. It should state:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq = 800000 [kHz] /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq = 1600000 [kHz]but instead it states:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq = 1333000 [kHz] /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq = 1333000 [kHz]If you get any output using tlp-stat means that the tlp service is running. Just in case, run:
sudo tlp-stat -s
+++ TLP STATUS should say State = enabled. This will confirm that it is running./sys/devices/system/cpu/cpu0/cpufreq/scaling_driver = acpi-cpufreqacpi-cpufreq seems to be the driver.
My guess is that the CPU behavior in battery mode is determined by the BIOS and tlp cannot override it. If possible, see if you can enter the BIOS and find any energy related option (maybe in CPU configuration).
Based on search results for atom CPUs of the similar specs, jumping to 800MHz on battery mode is the “power saving mode” (ideal for longer battery life).Based on this post in ubuntuforums, the eee pc 901 powermodes can be changed between 4 modes, but the (at the time) driver didn’t support clock-speed change, so maybe a newer (4.19) kernel has that option or maybe it is locked in the BIOS.
Sorry I couldn’t find much else. Maybe someone with more practical experience with eee pc 901 can give us a hint in the right direction.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
rokytnji
Made a mistake on the welcome thread.
My eeepc was a 900 . Not a 901.
I never tried over clocking mine from 800Mhz.Been years since I messed with one. Good luck with it.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsModdIt
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor = performance
Looks like in both cases the cpu is already running in Performance mode.
If my memory is correct you can not run in turbo, ie 1600 for prolonged periods
without risking processor overheating.Best info possibly here #https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling
The debian wiki is harder to understand, for me anyway.Ich kann die Frequenzeinstellungen mit cpufreq-info abfragen und mit cpufreq-set einstellen, z.B.
cpufreq -c 0 -d 800000
cpufreq -c 0 -u 1600000wird die untere Frequenz für cpu 0 auf 800 MHz und die obere auf 1,6 GHz gestellt.
Conky läuft ja auch und zeigt den aktuellen Wert für die CPU 0 an.Mit cpufreq-info werden die Grenzen und die aktuellen Werte angezeigt.
Die Frequenz wechselt bei 80% Akku von 1,6 GHz auf 1,333 GHz, wenn ich das Netzteil abziehe.tlp-stat -p zeigt mir in dem Fall immer die aktuelle Frequenz als obere und untere grenzfrequenz an.
Vielleicht kann ich es ja mit einem Startscript anpassen.
Soweit meine Erkenntnisse dazu, werde mal noch ein wenig weiter experimentieren. Aber wenn noch jemand Infos dazu hat, immer her damit!
Vielen Dank für die bisherigen Infos!
- This reply was modified 2 years, 4 months ago by Currock.
- You must be logged in to reply to this topic.
