Yes, an older one and have had it from new, but it became unusable for a long time after power on and battery not charging problems. Running Mint but was on MX initially.
Kept on resetting the board at first, changed the ML1220 at least twice and eventually resetting did not work any more. Main battery was then ordered (support diagnosed that) but as I had relocated, I had to wait for months before I could return to fetch the new battery…
So, only managed to persuade the device to charge and run on the new battery recently by some “black magic” trial and error of procedures. And finally, BIOS got and update.
However, I am getting a few hints/reminders of symptoms that make me worry. For example, when I plug in the power, the bolt deos not appear and it still runs on battery until I reboot. And there is that charge-pending status.
Read that Windows does not have these issues, but I am not eager to run that and far prefer Linux especially vs 11.
I do still have them: when I unplug and run on battery and then plug in to charge, the bolt does not appear but if I boot up with power cable, it is there until I unplug and reinserting the cable does the same no-bolt.
Head-scratching stuff…
Will try other OS as you suggested. Thanks for that.
Yes:
Plugged in, boot up (normal and expected icon display with bolt)
unplug (on battery, again normal icon with bolt now gone)
run down battery for a little bit
plug in to charge (no bolt in icon, and charge-pending status)
Also, now a new symptom. Powered down device to deal with screw holes. Closed up everything and attempted to boot up but everything was cold and dark, power button did not light up, totally unresponsive. Had to plug in, started up normally but noted that the side LED was orange and battery was 79%. Since it was booted up plugged-in, bolt was showing in the icon and battery status confirmed charging. Then I unplugged and the same repeats …
It refused to power up after a full shut down even with 70% battery unless I plug in power cable! All was cold and dark, the power button did not light up, I tried a long press, multiple presses, nothing worked. Once the power cable went it, the LED was momentarily orange, then green, and the power button lit up and it booted normally.
I am having the same issue with my 11th gen. After the bios update it only turns on if I plug in the cable even if it is fully charged and was off a minute ago!
The BIOS version does not show as updated to 3.20 on the BIOS main page or in the return of dmidecode.
There doesn’t appear to be any 6Ghz bands available on Wifi even when standing right next to the AP (Using the provided Intel AX210). iw phy still shows all 6GHz frequencies as being disabled.
This is the output of the “successful” BIOS update.
I ran the intel provided script to check if the CSME was updated to 15.0.47.2473 and it was.
It appears that some portions of the BIOS update was successful whereas other things were not. I’m not sure what the CapsuleApp errors are at the end of the BIOS update, so may be related to that?
Hello,
i had a problem with this update that grub-boot was gone.
Did anyone else have this?
I have Dualboot Windows / Linux (Debian) with grub, after the UEFI Update the computer direct boots to Windows and grub is gone.
It seems I was wrong. It still needs to be plugged in and then turned on if left off for a couple hours or more. If I turn it off and then immediately turn it on then it works.
I’m seeing an issue with booting as well across two 11th gen 13" laptops after upgrading to 3.20. It seems likely to be related to the RTC battery. Neither will boot normally, the fans just spin and the power button light comes on with the screen off until it turns all the way off and tries again. One just wouldn’t boot at all until I took out the RTC battery and now it’s normalish, just takes a long time to boot. The other I haven’t tried removing the RTC battery yet, but won’t boot unless I plug it into a phone charger (but not a laptop charger). From reading the docs, it seems this is due to the phone charger trickle charging the RTC battery.
The booting issue happens immediately upon suspending or shutting down. I can close the laptop lid then open it right back up and it won’t come back up unless I power it all the way down. It seems unlikely to be an OS issue, but I’m running Linux.
If S3’s been unsupported, but I’ve gotten away with using it, and 3.20 breaks it; you figure I should stay on 3.19? I’ve gotten attached to passable power usage during sleep.
What the heck was Intel smoking, anyways? (Aside from their own CPUs, eh?)
it sounds like if I upgrade to 3.20, (a) I will lose the ability to use suspend to RAM and (b) I won’t be able to downgrade to 3.19 to get it back.
I like suspend to RAM, because it’s the only way I can get sleep power consumption down in the vicinity of half a watt, roughly 1% per hour. Suspend to idle sucks. It uses more power and sometimes it fails mysteriously.
So the “should” part of my question is, are there any 3.20 BIOS changes that are desirable enough for me to lose suspend to RAM?
I’m not having any issues yet, because I haven’t upgraded to 3.20 yet. I’m still running 3.19.
I doubt the OS matters, aside from it being Linux. I’m on Fedora 40. I can’t try 3.20 to see if it works, because downgrading is impossible, so I’m just going by what others have said.
Try selecting your bootloader directly with F3 on startup (rather than F12).
Once you’ve booted your preferred OS, re-run the commands you used to install your bootloader. That will rewrite the UEFI NVRAM entries that inform the firmware about it.
