Theonly annoying thing is I cannot navigate the BIOS menu for some tweaking because the BIOS not shown on the external monitor, instead, it only shown on the broken laptop screen, and it only output to my external monitor when Windows/OS is logged-on.
Most laptops detect a closed lid with a magnet and a sensor. There is a small magnet probably somewhere on the top edge of the screen, and a sensor in the area of the body of the laptop that it would be near when closed. You can use a small refrigerator magnet placed on the sensor to trick the laptop into thinking it's always closed, while still having access to keyboard and buttons.
You say you're having problems trying to get the "boot with lid closed" method working; I just want to make sure you're actually trying to boot with the lid closed, and not pressing the power button/quickly closing the lid.
I had a this problem with a 2011 ASUS A53SV laptop which has a broken screen. The laptop was being used like a desktop with an external monitor. It had an old hard drive, and I wanted to upgrade it to an SSD.
After taking the battery out and putting it back in, I followed this by doing the following: got Ubuntu on a DVD and took the hard drive out so only Ubuntu would boot from the DVD drive (afterwards I found out that the BIOS didn't allow booting from USB), then tried pressing F8 to switch display in an HDMI and then DVI connection. Only the DVI-to- monitor connection worked for this laptop, but it was relieving to see the BIOS on the screen for the first time after spamming F2. It may be notable that the laptop motherboard was connected to the broken screen via display cable when this occurred.
Finally, I cloned the OS, Windows 7, from the old hard drive onto the new SSD and put in the new SSD. After putting in the SSD, W7 was bootable right from the start, and I was able to reinstall W7 via DVD.
Had the same problem with my HP laptop. Tried closing the lid, F4, etc, but they did't work for me. It was booting into the Windows login screen, but refused to output anything to HDMI during neither startup nor login.
I connected the HDMI cable before starting up, then repeatedly hit the ESC key during POST (right after power is turned on; this directs you to the page for selecting boot options), which somehow routed the display to the external display, and I was able to navigate into BIOS accordingly on my external display.
I tricked my laptop into thinking it had a closed lid by placing a magnetic strip along the front part (of the bottom half), and it worked! It let me enter BIOS the usual way (depending on your laptop, of course) and automatically showed it on the external monitor.
For right now, in the here and now. We have seen a decent success rate getting this updated using Windows. Obviously, like most of you, I am a full-time Linux users. So I have no desire to install Windows to update my BIOS.
Did the EFI method break laptops? cause it worked fine for me and some others it seemed. I dont like sharing the efi files while the official beta got removed, cause who can trust little ol me? if the windows stick method truly is such a problem, why consider a beta bios at all. just wait.
@Matt_Hartley Can you please share some details. What is the exact problem of the EFI updater? Is it the missing ME update? If people used the EFI updater (and updated the ME), will they need to wait for another update to fix something? If yes, what?
This is pretty much the same behavior and solution I observed when updating my personal 1260p (FRANGACP06) from 3.03 to 3.06 last year (WD SN850 back then, more RAM, all USB-C expansion cards). Even was the same ReTimer that failed to update. Although, while I am not 100%, I believe I had a different charger plugged in and on the left side back then.
So it seems very much that the ReTimers updating is what is problematic and nothing has changed with that since the 3.06 update. Only that my own FW already had up-to-date ReTimers, so that was not an issue this time around.
However, those who do not wish to wait can install Windows and run the MSI which has a solid success rate in testing here in with the community and with us. Ideal, no. But it does mean there BIOS are available now, but for efi we need to get some things sorted as there are some configurations that are not playing ball.
For those of you using Linux that are not thrilled with this. Yes, I get it. Fulltime Linux user here. However the ventoy method of creating a Windows installer USB is sound and works.
Install Windows, run the MSI updater, complete the process. Then once you have confirmed the BIOS update, wipe Windows.
Im pretty confident the general recommendation is not to install this update at all since this is just a beta. There are still no updates for the 12th gen laptops as far as the average user is concerned.
might not even browse these community pages, nor be on discord and be unaware of any bios updates. the average computer user is annoyed when a system reboots multiple times and all scary white characters appear and multiple progressbars.
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
I ordered a Dell laptop recently. About a month after it was delivered, I began receiving notifications from the Dell support tools preinstalled on the computer that a critical BIOS update was required.
I ignored the continual pop-ups reminding me to install the update for about four weeks. Eventually, about two months after I received the laptop, I installed the BIOS update. Immediately after applying the update and rebooting the computer, the computer stopped outputting video on the USB-C port to the monitors connected to my Dell dock.
Christopher Elliott is the founder of Elliott Advocacy, a 501(c)(3) nonprofit organization that empowers consumers to solve their problems and helps those who can't. He's the author of numerous books on consumer advocacy and writes weekly columns for King Features Syndicate, USA Today, Forbes and the Washington Post. He also publishes the Elliott Report, a news site for consumers, and Elliott Confidential, a critically acclaimed newsletter about customer service. If you have a consumer problem you can't solve, contact him directly through his advocacy website. You can also follow him on Twitter, Facebook, and LinkedIn, or sign up for his daily newsletter. This article originally appeared on Chriselliotts.com.
I recently bought an HP Pavilion 15 laptop that identifies itself as HP Pavilion Laptop 15-cc5xx. It runs Windows 10 Home 64. I am very disappointed with it, as it is a 7th Gen Core i5 with 8 gigs RAM but I find it quite slow, and it freezes constantly for no reason I can determine. However, I digress. I am trying to find out how I can access the BIOS on this laptop. All the docs I can find say to press F10 during startup, but that doesn't do anything. I just end up at the Windows screen. I'd appreciate any help. Thanks in advance.
I am not sure exactly what the Dell specific setting does, but here is some info on laptop battery charging rates. If you charge a battery faster (at higher rate) it wear much faster and loose its capacity much faster over time, than it would if you charged it at a slow or standard rate. The slower charging rate is better for the battery and the battery will keep its charge for longer. So if you use the express charge it will charge the battery faster, but will increase the wear on the battery and diminish its capacity over time. It will also cause your a/c adapter to consume more power and run much warmer, causing that to wear faster than it normally would. I recommend sticking with the standard charge rate and only use express, if you really need to charge you battery quickly, say you forgot to charge it for a long trip where you cannot charge it for a while.
We have several hundred Dell laptops and have found that with express charge the batteries do wear out much faster. What the means is that the battery will, at a faster rate, lose the ability to hold a charge and will not stay charged as long as it would if you were to use the standard charge feature.
History of Issue: I did a fresh install and immediately installed the kernel26-bfs kernel image. All went well. I tested a few things and did another fresh install (just because I like having a clean slate when experimenting) and installed the kernel26-bfs kernel image again. All seemed fine. Rebooted, shutdown and power upped a few times. Still good, so I shut down the laptop for the day and went to bed. (changed NO config files) Next morning I woke up and turned on the computer, which took a lot longer than usual. I found that when prompted at Lilo boot screen I couldn't type "bfs" (my kernel image named) but it ended up booting it anyway (after 50 seconds) since it was my default image. During the startup sequence it freaks out and kernel panics, trying to look for "device 802", whatever the heck that is. I don't know where it got that from since I had rebooted, etc, the previous day where it looked for "device /dev/sda2". So it shows a bunch of "kernel panic" lines and comes to a halt.
Anyway, I manually had to power down my laptop and I put in a LiveCD (Knoppix), it still wouldn't let me type with my keyboard, so I had to manually power down again. I tried the Arch LiveUSB image. Still nothing. I tried everything I could think of. I can't even hit the F9, F10, etc, keys during laptop start to enter my BIOS. I noticed a weird delay that I never had before. Usually when I start my laptop it would show the Hewlett-Packard BIOS Help screen immediately, but during that first morning when things went awry, it delays about 10-15 whole seconds before showing the HP screen.
SO, my question is... does it seem like my laptop had a hardware failure? Or do you think my MBR was seriously 'harmed' somehow? I can't access any log files seeing as I can't TYPE anything on that laptop. So, I'm kind of screwed when it comes to providing detail. I've had this laptop about 8 months, new w/o box, or so they say.. I may end up getting a new laptop if I can't fix this.
3a8082e126