Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ok, it boots fine after install.
So I shut it down, then yanked drive and put into the PC that refuses to install, and it BOOTS FINE.
I am typing in this message on it, using 64 bit.
Went from intel chips to amd chips just fine, like it always has for me.
SO next step do another install with the 2.2 infinity set to off in bios, and see what happens.
Last edited by sdowney717; 06-28-2017 at 09:05 AM.
it's an old mobo that doesn't support EFI, take a look at the BIOS date at the very bottom of the video: Copyright (C) 1985-2005.
There is no any EFI or secure boot related options. In 2005 EFI was not designed yet.
It's a traditional BIOS.
Regarding trusted computing - it's not a secure boot.
The bios date is from 2012, the date your seeing is just the American megatrends header.
You are incorrect about the UEFI unless the linux installer is that buggy it just thinks it is UEFI and forces a UEFI install on a non UEFI board? Do you really think that?? Even with all the UEFI error messages I have posted here????
ok, it boots fine after install.
So I shut it down, then yanked drive and put into the PC that refuses to install, and it BOOTS FINE.
I am typing in this message on it, using 64 bit.
Went from intel chips to amd chips just fine, like it always has for me.
SO next step do another install with the 2.2 infinity set to off in bios, and see what happens.
That's good to hear.
Why another install? Is this using another drive, or are you installing another distro as a dual-boot on the same hard drive?
The standard firmware provided with that motherboard appears not to support EFI. Have you at any point updated the firmware?
Edit: I just found this post - http://reboot.pro/topic/16315-22tb-i...fi-with-winpe/ - which claims that the firmware chip does support an undocumented transitional EFI-like capability called "2.2TB Infinity" that doesn't really work. Try and find that capability in the BIOS and switch it off.
You solved my problem!
Turned it off that dumb 2.2 turbo infinity, set to disabled...
Reinstalled
It boots Ubuntu 64 bit OS.
Perfect, thanks very much.
If it is not a UEFI bios and motherboard, then the Linux installer has a serious bug in to that really should be fixed. I can not be the oly person trying to install linux on such a board which I am sure they made lots of them, maybe millions of them.
Last edited by sdowney717; 06-28-2017 at 09:27 AM.
Why another install? Is this using another drive, or are you installing another distro as a dual-boot on the same hard drive?
Why? Because I needed to prove it can install and work on this 760GM-E51 motherboard with a defective bios transitional chip that fools the Linux installer.
Last edited by sdowney717; 06-28-2017 at 09:28 AM.
My original idea was to install updated Mint on the 760GM-E51, get everything working, install ubuntu, get everything working as a backup OS, then yank drive and put into boat PC without having to take it home.
But with it home now, I just updated the OS and installed motion and I suppose will leave it as is. Having a backup OS on the same drive may not be worth the trouble. they are both SATA II drives so wont be any quicker.
The boat PC is 320 gb, and this other drive is 1TB, but I dont need that much hard drive space at the boat.
Last edited by sdowney717; 06-28-2017 at 09:32 AM.
The bios date is from 2012, the date your seeing is just the American megatrends header.
You are incorrect about the UEFI unless the linux installer is that buggy it just thinks it is UEFI and forces a UEFI install on a non UEFI board? Do you really think that?? Even with all the UEFI error messages I have posted here????
Teufel had good reason to state that the motherboard is non-EFI. Neither the motherboard's documentation nor specifications refer to its transitional EFI-like "2.2TB Infinity" capability and, to all intents and purposes, the motherboard doesn't have conventional EFI support. It's just a pity that this undocumented setting was switched on in the motherboard (it was the fact it was switched on that appears to have caused your problems).
It is a real kludgy firmware effort on that board to be honest, particularly if it dates from 2012 when there was no excuse for not implementing proper UEFI. I hope that there aren't too many other motherboards around with firmware like that.
My original idea was to install updated Mint on the 760GM-E51, get everything working, install ubuntu, get everything working as a backup OS, then yank drive and put into boat PC without having to take it home.
But with it home now, I just updated the OS and installed motion and I suppose will leave it as is. Having a backup OS on the same drive may not be worth the trouble. they are both SATA II drives so wont be any quicker.
The boat PC is 320 gb, and this other drive is 1TB, but I dont need that much hard drive space at the boat.
So, problem solved?
If so, I'm glad. Please mark the thread as "Solved" (see "Thread Tools" at the top of this thread) and Happy Boating!
Yes, working now. No one else could figure it out but you.
For me it is a bug in the linux installer, if it cant properly detect that the board is not a UEFI but the installer thinks it is a UEFI board.
Other people can think what they want, this caused me a lot of trouble.
If the average guy, like me, sees a lot of UEFI installer error messages, they are going to think it is a UEFI problem.
Last edited by sdowney717; 06-28-2017 at 09:36 AM.
Yes, working now. No one else could figure it out but you. For me it is a bug in the linux installer, if it cant properly detect that the board is not a UEFI but the installer thinks it is a UEFI board.
Other people can think what they want, this caused me a lot of trouble.
I'm not so sure. If the firmware is presenting itself to the installer as something it really isn't, as some form of kludge, then it's not surprising that the installer is taking the firmware at its word.
I can imagine the trouble it caused you. This is not your run-of-the-mill problem. In the end I found the information, and hence the solution, by Googling "760GM-E51" bios efi. It could well be that the problem was resolved in later firmware updates, I have no idea, but certainly it exists in the firmware version that you have.
I'm not so sure. If the firmware is presenting itself to the installer as something it really isn't, as some form of kludge, then it's not surprising that the installer is taking the firmware at its word.
I can imagine the trouble it caused you. This is not your run-of-the-mill problem. In the end I found the information, and hence the solution, by Googling "760GM-E51" bios efi. It could well be that the problem was resolved in later firmware updates, I have no idea, but certainly it exists in the firmware version that you have.
I had looked at updating the bios.
I found the MSI bios downloads and downloaded the latest one dated 2011.
BUT, looking at the installed bios date, it says 2012, very suspicious.
So I then tried to use M-flash bios utility and the running bios did not recognize the downloaded bios as a bios file...
But I did save the machines existing bios to the usb thumb drive.
The running bios wants an extension of .360 on the bios saved file was named A7596AMS.360. and the download bios from MSI was named A7596AMS.1A0
Who knows but seems sketchy support.
Last edited by sdowney717; 06-28-2017 at 09:49 AM.
I had looked at updating the bios.
I found the MSI bios downloads and downloaded the latest one dated 2011.
BUT, looking at the installed bios date, it says 2012, very suspicious.
So I then tried to use M-flash bios utility and the running bios did not recognize the downloaded bios as a bios file...
But I did save the machines existing bios to the usb thumb drive.
The running bios wants an extension of .360 on the bios saved file was named A7596AMS.360. and the download bios from MSI was named A7596AMS.1A0
Who knows but seems sketchy support.
Indeed. I don't know the specifics of how M-Flash works and what BIOS file format it requires, but you probably did the right thing in not updating the BIOS. Although there are some who swear that the procedure works with nary a glitch, it can also be the easiest way to brick a machine. Just one example: http://www.tomshardware.co.uk/answer...te-failed.html
Indeed. I don't know the specifics of how M-Flash works and what BIOS file format it requires, but you probably did the right thing in not updating the BIOS. Although there are some who swear that the procedure works with nary a glitch, it can also be the easiest way to brick a machine. Just one example: http://www.tomshardware.co.uk/answer...te-failed.html
I have an Asus P5QC which long ago I updated the bios, and it failed, but board has a backup bios chip? So it always booted but took longer with lots of extra beeps. That board finally stopped booting a few years ago. So yes, risky. I have had to update some bios's to get new CPU to be recognized.
I have it sitting next to me, that P5QC still in the case. Was a decent PC. I have not taken the time to tear it completely apart, but did steal the ram, hard drive, PSU out of it
Last edited by sdowney717; 06-28-2017 at 10:51 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.