There is also the VISUAL param which overrides what is inferred from EDITOR.
On Fri, May 31, 2024, at 2:23 PM, Stuart Henderson wrote:
> On 2024-05-31, 04-psyche.tot...@icloud.com <04-psyche.tot...@icloud.com>
> wrote:
> > Hi all,
> >
> > I use the following terminal:
> >
> > echo $TERM
> > xterm
> From your dmesg:
>
> iwx0 at pci6 dev 0 function 0 "Intel Wi-Fi 6 AX210" rev 0x1a, msix
>
> if you read the end of man page for iwx you'll see:
>
> This driver does not support powersave mode.
Ah.
I guess that’s a failure to read man page. Thank you.
I’ve tested disabling the port in BI
> 1. Snapshot's kernel:
>
> Apr 28 13:32:23 matebook apmd: battery status: CRITICAL. external power
> status: not connected. estimated battery life 14% (11 minutes life time
> estimate)
>
> 2. Solene's patch:
>
> May 1 11:52:28 matebook apmd: battery status: CRITICAL. external power
> s
>
> I tried disabling cores in my bios down to 3 CPUs and did comparisons and i
> didn't really notice a savings.
That was for idle usage, though. This may help out with an actual workload
> Linux has drivers for devices shutdown when not used and idle power
> states, pretty much like Windows has. Android, who is Linux derived,
> took this concept to a much higher level.
> Think of a wireless card and you can see on man ath(4): " The driver
> does not fully enable power-save operat
> It is extention of powersave mode which disabling / enabling CPUs.
Interesting, maybe i'll test on it.
> Regarding estimated life time:
>
> Battery state: high, 66% remaining, 152 minutes life estimate
> AC adapter state: not connected
> Performance adjustment mode: powersaving (400 MHz
> I am conducting my tests with manual hw.setperf=0
I think maybe it’s the drivers not powering down like you said
On Tue, Apr 30, 2024, at 3:13 PM, Mihai Popescu wrote:
> https://marc.info/?l=openbsd-misc&m=165231418528297&w=2
>
>
I am conducting my tests with manual hw.setperf=0
Kirill thanks for the patch, but i am still worried about the power usage. Even
if i put apmd in manual mode and setperf=0, my system sucks 9-9.5W, which means
the patch will not do much in my situation since any benefit from the patch
comes from setperf=0.
What could be taking so much power? C
On Sun, Apr 28, 2024, at 4:17 PM, Mihai Popescu wrote:
> > Any ideas if it's remediable or where to start digging?
>
> Linux has drivers for devices shutdown when not used and idle power
> states, pretty much like Windows has. Android, who is Linux derived,
> took this concept to a much higher l
On Tue, Apr 30, 2024, at 7:52 AM, Nathaniel Griswold wrote:
> For this reason, I’m not sure it’s doing straight pass through — it must be
> some kind of hybrid design or something I don’t understand.
For anyone interested, I guess I was wrong it stays at zero current even under
high l
> Well, I haven't tried it but I've read documentation [1] and it seems a bit
> differently, isn't it?
Um, obsdfreqd sets a cpu frequency “percentage” which I thought might just be
setperf. One difference is it sets a range based on a usage algorithm while
solene’s patch seems to setperf 100 or
> is it an genuine (really in strict sense of the term) brand battery or a
> compatible replacement (even if they call it "genuine", always puzzles me).
> Since I keep alive a lot of vintage laptops and am the author of
> GNUstep's BatteryMonitor I share the experience that non-original
> batte
> I had near the same question sometime ago but on different machine, and I've
> discovered a patch which I've inlinded into this email.
>
Hm, ok, i'll try it. Do you have any insight into whether obsdfreqd has similar
power saving to this patch? It seems to set the perf similarly. I wasn't hav
On Mon, Apr 29, 2024, at 5:06 AM, Polarian wrote:
> Hello,
>
> Just a quick thing I wanted to point out.
>
> > I have no idea why my charge cycles is so low. It's at 5 now. And i
> > tested that on Linux, too, so it's not just OpenBSD.
>
> Having low charge cycles is good, that isn't the issue
> So you are running on battery, not AC.
Yes, i am testing the power usage on battery
> > hw.sensors.acpibat0.raw1=4 (discharge cycles)
>
> Probably not related, but your battery has dropped full charge
> from 3.57 Ah to 3.01 in four cycles?
>
>
> > hw.sensors.acpitz0.temp0=42.80 degC (zone t
I trimmed the dmesg.boot to be just the last boot
On Sun, Apr 28, 2024 at 08:01:58PM +0200, Jan Stary wrote:
> > > hw.sensors.acpibat0.volt0=15.40 VDC (voltage)
> > > hw.sensors.acpibat0.volt1=14.29 VDC (current voltage)
> > > hw.sensors.acpibat0.current0=0.69 A (rate)
>
> I think he got it from
I forgot to mention that I have apmd running in automatic mode. I've also tried
obsdfreqd but it does not seem to have much of an effect on or off. Here is my
`sysctl hw.sensors' output (with obsdfreqd on)
```sysctl hw.sensors
hw.sensors.cpu0.temp0=47.00 degC
hw.sensors.cpu0.frequency0=6
I am seeing a lot of power drawn even when nothing is going on on the system
(top shows everything at zero, load average is 0.01). This is even if the
backlight is dim.
On an Ubuntu Linxu system, i was getting about 3.5-4W when nothing much was
going on.
Any ideas if it's remediable or where t
19 matches
Mail list logo
