Psx Eu Bios
Kathleen Denson
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.
I tried to update using ms dos but somebody bumped on the power plug and corrupted the bios. I bought a EEPROM flasher to try to recover it now. Waiting for it to be delivered. Will post an update as soon as I can.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
The update process was executed in DOS environment using the command "iflash2 /pf TC0048P.bio". The system restarted and initiated the update process. It was taking too long though (more than 10 minutes). Having no other choice, I left it to its guns to (hopefully) complete the update, and went away to do something else. Upon returning, a good 30 minutes later, the system's fans were running and the screen was black. At that point no amount of resetting, turning it on/off, clearing the CMOS, etc. could get it to boot.
There are ways to recover but these did not work. I prepared a USB drive with only the BIOS file on it, removed the jumper from the motherboard to initiate recovery process but to no avail. The other option would be flashing the BIOS externally. The problem is that the BIOS chip (MX25L6445E) is 8 megabytes whilst the bios file is near 10 megabytes. I was still able to flash (with a warning) using the CH341a programming tool but, again, that didn't work.
First, let me say that other than swapping out or otherwise upgrading drives and memory cards, I am NOT an expert hardware guy. I have on occasion run the F7 BIOS updates many years ago, but on the whole I've "let sleeping dogs lay".
The problem prompting my post here is that a DVD optical drive recently connected to the SATA 2 port (SSD & HDD in ports 0 and 1) while showing in the BIOS and Device Manager fails to appear along with the drives in Windows Explorer. To the best of my knowledge, the Optical drive is functioning properly, at least Device Manager reports it as such.
So, given all the above, it would seem the first order of business ought to be to get the BIOS up-to-date? If so, will the "TC00P48.bio" file take my current version 37 BIOS through the series of updates in one swoop, or does one have to obtain the intervening updates and do them one at a time? OR, do you recognize the "WE no show" issue and there's a simple solution that doesn't involve the BIOS at all?
Sounds like your issue is a Windows problem. Maybe try assigning a new drive letter to the DVD drive in Windows Drive Management? Failing that you could perform a DISM / SFC or even a re-install of Windows.
That said BIOS updates are fun, and easy. My hobby is buying old computers and seeing if I can turn them into something usable. Once I get something running the next step is BIOS update. It was pretty easy on this Intel board so I recommended it. My most recent purchase was a M83 Lenovo and it actually made me write an ISO to CD and connect a physical optical drive to it before it got going.
.BIN files are not provided for desktop boards because you are basically stealing the identity of another board. Those .BIN files that you do find are from someone who as copied the bios from one board, and sells the .BIN file to people, like you. Now, if you have a damaged board, and copy the bios in .BIN format, that is "acceptible". But, most that you find are clones from good boards and should not be used. Consider, for example, you will have the same MAC address as another board.
By professional I mean someone who has experience with these boards. I have been using Intel desktop boards for a VERY long time. And, Scott has been using them longer than me. I have updated the bios on desktop boards probably three times a year for the past 30 years or so. Do the math. And, I have seen a good number of guys with a chip burner make mistakes and roach/brick their boards, and try to blame it on Intel. And, you could have come this forum BEFORE you tried anything and asked questions.
You are actually mistaken about the working BIOS files. To put matters into perspective, I have a Lenovo Ideacentre Y900 of which the BIOS was password-protected from the previous owner. There was no way to unlock it and used the serial number of that system to download a working BIOS file directly from Lenovo that I used to successfully flash the BIOS on that system, with my external flasher, in order to remove the password. Of course more work was needed later to also add details like serial number UUID, MAC address etc but, the bottomline is, it worked!
About the procedure now for the Intel board now. If you followed this thread closely, you would have read that I followed the conventional procedure first, before resorting to the flasher, and it FAILED. Is that my fault too? Would your 30 years of experience have predicted that by following the standard procedure to update the BIOS would result to a failed BIOS update? I don't think so.
Lenovo's bios belongs to lenovo and they can do what they want. Not relevent here because this is an intel bios and board. So, it is your mistake to assume they are the same. And, to help you further, dell's bios belongs to dell, asus bios belongs to asus, msi bios belongs to msi, etc., etc., etc. They may or may not have the same restrictions as Intel.
Now, it is time for you to move on. Yoiu have bricked your board, because of your lack of experience and knowledge, and tried to blame it on someone else. Take your new-found knowledge, and your chip burner, and go play somewhere else.
"Lenovo's bios belongs to lenovo and they can do what they want. Not relevent here because this is an intel bios and board. So, it is your mistake to assume they are the same. And, to help you further, dell's bios belongs to dell, asus bios belongs to asus, msi bios belongs to msi, etc., etc., etc. They may or may not have the same restrictions as Intel."
So if other big manufacturers do not impose the same "Security" restrictions as Intel does then who's to blame? These "Security" features is another way of destroying equipment and forcing consumers to go and buy the "new stuff".
"Now, it is time for you to move on. Yoiu have bricked your board, because of your lack of experience and knowledge, and tried to blame it on someone else. Take your new-found knowledge, and your chip burner, and go play somewhere else."
Thank you Scott! Your instructions proved to be PERFECT! In effect, my BIOS upgraded from P37 to P48 in one operation without a hitch. I happened to have an old USB 2.0 8GB that formatted easily and I simply copied the .bio file from your earlier post referencing the latest BIOS version to its root.
For anyone that might be interested in what the recovery script looks like when it runs, I've attached a iPhone screenshot herein. I also included a shot of the jumper in case anyone is unfamiliar with its appearance on the board.
For 18 years, more than 4,000 BIOS participants have surpassed their peers in introductory courses, retention within their major, and graduation rates. BIOS is an optional Choose Your Adventure event that takes place during Welcome Week before the beginning of each fall semester. It is a full-day program extending from Thursday August 22nd through Sunday August 25, 2024. Attendance at all events on these four days is mandatory for BIOS participation. Unfortunately, BIOS participation directly conflicts with other Choose Your Adventure Events including Greek Rush and LSU Band. Pre-registration is required and participation is limited to College of Science incoming freshmen. Pre-registration is now open and the deadline is Friday, July 26th. The Choose Your Adventure Pre-Registration Form is found on the Welcome Week website.There is a fee of $275 for the program. See the payment portion below for more details.
c80f0f1006