Re: X220 thinkpad battery issue

2021-07-15 Thread Isak Holmström
15 juli 2021 kl. 17:10 skrev Peter N. M. Hansteen :
> 
> On Thu, Jul 15, 2021 at 04:54:08PM +0200, Isak Holmström wrote:
>> 15 juli 2021 kl. 10:07 skrev Jonathan Drews :
>>>> 
>>>>  According to Wikipedia, The X220 was first manufactured in 2011.
>>>> https://en.wikipedia.org/wiki/ThinkPad_X_series#X220
>>>> Remove the battery and look for the date when it was manufactured. The 
>>>> manufacture date is usually stamped somewhere on the battery. If it is 
>>>> more than 4 years old, then it  may very well be dead. 
>> 
>> The battery is a replacement battery not older than 1 year, bought from 
>> eBay. The text on the battery says:
>> Green Cell replace FRU 42T4861, ASM 42T4862. Li-ion 11.1V 4400mAh.”
> 
> In my web search just now it looked superficially like more local (Norwegian 
> or 
> possibly Swedish) sites had new units in stock. Prices quoted something like
> NOK 350 or thereabouts and up to around 1500 NOKs. That variation is a bit odd
> but I'd think it's worth checking for relatively local sources.

Thanks for your help!
I just bought a replacement battery for 599 SEK. Hoping to get it tomorrow or 
the day after tomorrow for express delivery :-)

-isak 



Re: X220 thinkpad battery issue

2021-07-15 Thread Isak Holmström
15 juli 2021 kl. 17:06 skrev Marcus MERIGHI :
> 
> Hello!
> 
> b...@shoshoni.info (Bryan Linton), 2021.07.15 (Thu) 11:33 (CEST):
>>> On 2021-07-15 08:57:32, Isak Holmström  wrote:
>>> Hello,
>>> I recently discovered that my battery is not charging. I really
>>> can’t find anything when searching the web regarding openbsd and
>> 
>> A couple thoughts.
>> 
>> 1)  The battery may simply be dead.  AFAIUI, modern laptop
>> 
>> 2)  Have you upgraded the laptop's internals, or changed the power
>> charger you use?  I know that newer models of Thinkpads will
>> 
>> 3)  Power sockets get plugged and unplugged a lot, and tend to
>> wear out over time.  Could the socket itself be loose?  Does
> 
> Some more thoughts...
> 
> 4) the X220 has a LED indicator that goes off and back on again if I
>   plug the power cord. What does yours do?
> 5) I've once had luck with simply taking the battery out of the
>   notebook, waiting some time, an re-plugging it. But that did not help
>   for long, see 1) :-)

4) Thanks for your time. My LED indicator for the battery keeps blinking red. 

5) I have tried taking the battery out for hours no luck :/

-isak



Re: X220 thinkpad battery issue

2021-07-15 Thread Isak Holmström
15 juli 2021 kl. 16:55 skrev Peter N. M. Hansteen :
> 
> On Thu, Jul 15, 2021 at 04:38:06PM +0200, Isak Holmström wrote:
>>> Output from "sysctl hw.sensors" might give a clue.
>> 
>> Thanks, the output from hw.sensors:
>> hw.sensors.cpu0.temp0=54.00 degC
>> hw.sensors.acpibtn0.indicator0=On (lid open)
>> hw.sensors.acpibat0.volt0=11.10 VDC (voltage)
>> hw.sensors.acpibat0.volt1=9.27 VDC (current voltage)
>> hw.sensors.acpibat0.power0=0.00 W (rate)
>> hw.sensors.acpibat0.watthour0=48.50 Wh (last full capacity)
>> hw.sensors.acpibat0.watthour1=2.42 Wh (warning capacity)
>> hw.sensors.acpibat0.watthour2=0.20 Wh (low capacity)
>> hw.sensors.acpibat0.watthour3=0.00 Wh (remaining capacity), CRITICAL
> 
> This one -- remaining capacity -- I would go back and check after leaving
> the machine plugged in for a while, some hours at least. 
> 
> It would not surprise me a lot if it stays put at 0.00, in which case
> the conclusion would be that you have a dead battery. 
> 
> Fortunately a simple web search seems to indicate that spares are available
> at a price level that is not totally horrible.

Thanks Peter,
I might be afraid that you are totally right the charger has been in charger 
mode for more than 24 hours without any success. I have even tried a couple of 
tricks from the thinkpad community like plug out the charger, remove battery 
and push the power button for at least 30 sec and then plug everything back - 
no success.

- isak 



Re: X220 thinkpad battery issue

2021-07-15 Thread Isak Holmström
15 juli 2021 kl. 15:30 skrev Jan Stary :
> 
> On Jul 15 08:57:32, i...@prehosp.se wrote:
>> I recently discovered that my battery is not charging.
> 
> Is that a battery that previously was charging?
> In this same machine?
> What does sysct hw say?
> What does apm -v say?

sysctl hw.sensors says:

—— snip
hw.sensors.cpu0.temp0=54.00 degC
hw.sensors.acpibtn0.indicator0=On (lid open)
hw.sensors.acpibat0.volt0=11.10 VDC (voltage)
hw.sensors.acpibat0.volt1=9.27 VDC (current voltage)
hw.sensors.acpibat0.power0=0.00 W (rate)
hw.sensors.acpibat0.watthour0=48.50 Wh (last full capacity)
hw.sensors.acpibat0.watthour1=2.42 Wh (warning capacity)
hw.sensors.acpibat0.watthour2=0.20 Wh (low capacity)
hw.sensors.acpibat0.watthour3=0.00 Wh (remaining capacity), CRITICAL
hw.sensors.acpibat0.watthour4=48.84 Wh (design capacity)
hw.sensors.acpibat0.raw0=6 (battery charging), OK
hw.sensors.acpiac0.indicator0=On (power supply)
hw.sensors.acpithinkpad0.temp0=55.00 degC
hw.sensors.acpithinkpad0.temp1=55.00 degC
hw.sensors.acpithinkpad0.temp2=55.00 degC
hw.sensors.acpithinkpad0.temp3=55.00 degC
hw.sensors.acpithinkpad0.temp4=55.00 degC
hw.sensors.acpithinkpad0.temp5=55.00 degC
hw.sensors.acpithinkpad0.temp6=55.00 degC
hw.sensors.acpithinkpad0.temp7=55.00 degC
hw.sensors.acpithinkpad0.fan0=3496 RPM
hw.sensors.acpithinkpad0.indicator0=Off (port replicator), UNKNOWN
hw.sensors.acpitz0.temp0=55.00 degC (zone temperature)
hw.sensors.acpidock0.indicator0=Off (not docked), UNKNOWN
hw.sensors.aps0.temp0=40.00 degC
hw.sensors.aps0.temp1=40.00 degC
hw.sensors.aps0.indicator0=On (Keyboard Active)
hw.sensors.aps0.indicator1=Off (Mouse Active)
hw.sensors.aps0.indicator2=On (Lid Open)
hw.sensors.aps0.raw0=506 (X_ACCEL)
hw.sensors.aps0.raw1=514 (Y_ACCEL)
hw.sensors.aps0.raw2=506 (X_VAR)
hw.sensors.aps0.raw3=514 (Y_VAR)
hw.sensors.softraid0.drive0=online (sd1), OK
—— snip

amp -v says:
—— 
Battery state: CRITICAL, 0% remaining, unknown life estimate
A/C adapter state: connected
Performance adjustment mode: auto (800 MHz)
——- 



Re: X220 thinkpad battery issue

2021-07-15 Thread Isak Holmström
15 juli 2021 kl. 10:07 skrev Jonathan Drews :
>> 
>>  According to Wikipedia, The X220 was first manufactured in 2011.
>> https://en.wikipedia.org/wiki/ThinkPad_X_series#X220
>> Remove the battery and look for the date when it was manufactured. The 
>> manufacture date is usually stamped somewhere on the battery. If it is more 
>> than 4 years old, then it  may very well be dead. 

The battery is a replacement battery not older than 1 year, bought from eBay. 
The text on the battery says:
Green Cell replace FRU 42T4861, ASM 42T4862. Li-ion 11.1V 4400mAh.”



Re: X220 thinkpad battery issue

2021-07-15 Thread Isak Holmström
15 juli 2021 kl. 11:33 skrev Bryan Linton :
> 
> On 2021-07-15 08:57:32, Isak Holmström  wrote:
>> Hello,
>> I recently discovered that my battery is not charging. I really can’t find 
>> anything when searching the web regarding openbsd and batteries. Please 
>> advice me how to debug this issue. I cannot find anything on 
>> https://marc.info or man sysctl, apm or apmd, sysctl.conf 
>> 
> 
> A couple thoughts.
> 
> 1)  The battery may simply be dead.  AFAIUI, modern laptop
> batteries have internal circuits that disable the battery if they
> detect anything that could be dangerous.  There may be a
> (Windows-only) utility that Lenovo offers to check this.

This might be the case, but it was fully working a week ago.


> 
> 2)  Have you upgraded the laptop's internals, or changed the power
> charger you use?  I know that newer models of Thinkpads will
> refuse to charge if the charger can't put out enough power to do
> so.  Lenovo makes chargers in many different wattage ratings.  Is
> the one you're using rated to power an X220 in the configuration
> it's in?  I.e. Models with faster CPUs/discrete graphics often
> require a higher wattage power supply than those without.

The charger is a 20V. Belonging to the device. Nothing has been changed the 
recent year another than the replacement battery, max one year old.


> 
> 3)  Power sockets get plugged and unplugged a lot, and tend to
> wear out over time.  Could the socket itself be loose?  Does
> "sysctl hw.sensors" show hw.sensors.acpiac0.indicator0 as being
> "on"?  Does wiggling the power cable cause it to
> connect/disconnect?

The power cable is firmly set, not “wiggly”.

> 
> None of these are a definite answer, but hopefully one of them
> will help guide you to a solution to your problem.
> 
> -- 
> Bryan
> 



Re: X220 thinkpad battery issue

2021-07-15 Thread Isak Holmström

> 15 juli 2021 kl. 10:00 skrev Stuart Henderson :
> 
> On 2021-07-15, Isak Holmström  wrote:
>> Hello,
>> I recently discovered that my battery is not charging. I really can’t find 
>> anything when searching the web regarding openbsd and batteries. Please 
>> advice me how to debug this issue. I cannot find anything on 
>> https://marc.info or man sysctl, apm or apmd, sysctl.conf
> 
> OpenBSD doesn't control charging. That's a function of the various parts
> of the laptop (battery, charger, embedded controller etc). The system
> communicates with the firmware on the battery pack and won't charge if
> that fails or it thinks it's unsafe to charge.
> 
>> acpibat0 at acpi0: BAT0 model "42T4861" serial 17065 type LION oem "SANYO"
> 
> There is clearly some comms with the battery because this is reported.
> Output from "sysctl hw.sensors" might give a clue.

Thanks, the output from hw.sensors:
hw.sensors.cpu0.temp0=54.00 degC
hw.sensors.acpibtn0.indicator0=On (lid open)
hw.sensors.acpibat0.volt0=11.10 VDC (voltage)
hw.sensors.acpibat0.volt1=9.27 VDC (current voltage)
hw.sensors.acpibat0.power0=0.00 W (rate)
hw.sensors.acpibat0.watthour0=48.50 Wh (last full capacity)
hw.sensors.acpibat0.watthour1=2.42 Wh (warning capacity)
hw.sensors.acpibat0.watthour2=0.20 Wh (low capacity)
hw.sensors.acpibat0.watthour3=0.00 Wh (remaining capacity), CRITICAL
hw.sensors.acpibat0.watthour4=48.84 Wh (design capacity)
hw.sensors.acpibat0.raw0=6 (battery charging), OK
hw.sensors.acpiac0.indicator0=On (power supply)
hw.sensors.acpithinkpad0.temp0=55.00 degC
hw.sensors.acpithinkpad0.temp1=55.00 degC
hw.sensors.acpithinkpad0.temp2=55.00 degC
hw.sensors.acpithinkpad0.temp3=55.00 degC
hw.sensors.acpithinkpad0.temp4=55.00 degC
hw.sensors.acpithinkpad0.temp5=55.00 degC
hw.sensors.acpithinkpad0.temp6=55.00 degC
hw.sensors.acpithinkpad0.temp7=55.00 degC
hw.sensors.acpithinkpad0.fan0=3496 RPM
hw.sensors.acpithinkpad0.indicator0=Off (port replicator), UNKNOWN
hw.sensors.acpitz0.temp0=55.00 degC (zone temperature)
hw.sensors.acpidock0.indicator0=Off (not docked), UNKNOWN
hw.sensors.aps0.temp0=40.00 degC
hw.sensors.aps0.temp1=40.00 degC
hw.sensors.aps0.indicator0=On (Keyboard Active)
hw.sensors.aps0.indicator1=Off (Mouse Active)
hw.sensors.aps0.indicator2=On (Lid Open)
hw.sensors.aps0.raw0=506 (X_ACCEL)
hw.sensors.aps0.raw1=514 (Y_ACCEL)
hw.sensors.aps0.raw2=506 (X_VAR)
hw.sensors.aps0.raw3=514 (Y_VAR)
hw.sensors.softraid0.drive0=online (sd1), OK
——- snip 

So the charger is charging or at least trying. No errors.

- isak 



X220 thinkpad battery issue

2021-07-15 Thread Isak Holmström
Hello,
I recently discovered that my battery is not charging. I really can’t find 
anything when searching the web regarding openbsd and batteries. Please advice 
me how to debug this issue. I cannot find anything on https://marc.info or man 
sysctl, apm or apmd, sysctl.conf 

dmesg x220:
——- snip

OpenBSD 6.9 (GENERIC.MP) #3: Mon Jun  7 08:21:26 MDT 2021

r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8451125248 (8059MB)
avail mem = 8179625984 (7800MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries)
bios0: vendor LENOVO version "8DET76WW (1.46 )" date 06/21/2018
bios0: LENOVO 4291H77
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT 
SSDT DMAR UEFI UEFI UEFI
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) EHC1(S3) 
EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2492.23 MHz, 06-2a-07
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz, 06-2a-07
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.92 MHz, 06-2a-07
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz, 06-2a-07
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus 5 (EXP4)
acpiprt5 at acpi0: bus 13 (EXP5)
acpiprt6 at acpi0: bus -1 (EXP7)
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
tpm0 at acpi0 TPM_ addr 0xfed4/0x5000, device 0x104a rev 0x4e
acpibat0 at acpi0: BAT0 model "42T4861" serial 17065 type LION oem "SANYO"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0: version 1.0
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2
acpitz0 at acpi0: critical temperature is 99 degC
acpidock0 at acpi0: GDCK not docked (0)
acpivideo0 at acpi0: VID_
acpivout0 at acpivideo0: LCD0
acpivideo1 at acpi0: VID_
cpu0: using VERW MDS workaround (except on vmm entry)
cpu0: Enhanced SpeedStep 2492 MHz: speeds: 2501, 2500, 2200, 2000, 1800, 1600, 
1400, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi, 

Re: @OpenBSD_CVS Twitter 140char limit?

2020-05-10 Thread Isak Holmström

10 maj 2020 23:00:45 Daniel Jakots :

 On Sat, 09 May 2020 19:17:29 +0200, Tommy Nevtelen 

 wrote


> Does anybody on this list manage @OpenBSD_CVS? Would be nice to 

lift

>
> the message truncation from the old 140char limit to the new 280char
>
> limit. Super annoying when I can't read an interesting commit message
>
> that is just a little longer  :)
>

    afresh1@ is pretty busy so your best luck is probably to submit a 

pull


request at https://github.com/afresh1/openbsd-commits-to-twitter



I do believe it's using the "new" limit introduced 2017 :)

my $default_maxlen = 280;

I found this on GitHub. Though there a reference in the code to 140.

:wq isak Sent from mobile device, all error self inflicted.



Keybase team

2020-02-03 Thread Isak Holmström
Hello @misc-readers,
I'm not sure this is the correct forum. But I was wondering if any of you would 
be interested in a keybase team? Using it for discussions, questions and a 
closer contact way than via email.

If I am completely wrong about this I am truly sorry for the inconvenience.

Best regards,
Isak 
-- 
Sent from mobile device, all error self inflicted.



Re: pkg_add -u fails on nonexistant package

2019-08-21 Thread Isak Holmström
Have you tried pkg_check to see failing messages for missing files? 

On August 21, 2019 11:03:06 PM UTC, Jordon  wrote:
>A few years ago I attempted to make a port of obs-studio for openbsd. 
>With help from this mailing list, I got something that ran but wasn’t
>particularly useful, as audio and video sources were not there.  I gave
>up on that project and since then have been using that machine for
>local development on a cgi-based website.
>This system runs current and gets updated about once a week or so.  I
>also try to do a ‘pkg_add -u’ regularly too.  Every time I do that, it
>ends with this:
>Fatal error: can't parse OpenBSD::Requiring: writing
>/var/db/pkg/obs-studio-17.0.0/+REQUIRING: No such file or directory at
>/usr/libdata/perl5/OpenBSD/RequiredBy.pm line 30.
>
>That is the package I was making and it is no longer installed.  How
>does pkg_add even know about it, as it isn't part of the base packages?
>What can I do to get rid of that message?  It has been doing that for a
>while and I am finally annoyed enough to try to fix it!
>
>Jordon

--
Isak - OBSD.xyz