Unable to boot to some PXE ROM
-
[quote=“Wolfbane8653, post: 40652, member: 3362”]Can you list the devices that are “only UEFI”?[/quote]
The systems are all ACER computers. I have been up and down in the BIOS and I don’t see anything to disable UEFI. I am also getting some Lenovos and it seems that I will be running on the same issue. On the Lenovo I was able to upload the original image but when I download it back to the system well, the system crashed and a repair had to be done. On the last one, the hard drive was wiped and Windows 8.1 was installed manually (less bloated) to customize the system, in this instance the image just locked again.
One point to clarify is that it never fails, it just sit in the very last screen before actually doing the upload. I have to either press enter or shutdown the system to force the system out of the induced coma. Does that help?
I am still trying to figure out if there are any logs that can be pulled to see what is going on. I know it could be an issue with GPT discovery in the code as mention previously. Is it possible to fix the issue with GPT? The only way to create the image was using raw but it will take too long.
Thank you in advance for any assistance.
-
[quote=“DarkEnergy, post: 40703, member: 26785”]The systems are all ACER computers.[/quote]
Can we get some make and models?
Maybe if someone else has the same device or close they would jump in here and help out. I have an Acer desktop here on a side work order but it works well with fog. -
[quote=“Wolfbane8653, post: 40709, member: 3362”]Can we get some make and models?
Maybe if someone else has the same device or close they would jump in here and help out. I have an Acer desktop here on a side work order but it works well with fog.[/quote]You are focusing in the make an model when you should be focusing in the type of BIOS the system is running. Does your ACER is UEFI or just plain old BIOS? Many systems independent of the manufacturer use the same mobo with the same BIOS/UEFI in the board. For instance Many systems comes with AMI or Phoenix BIOS. It would be more beneficial to pain attention at the type of BIOS and file systems. For instance in my case I have to use GPT as part of the UEFI as I cannot disable UEFI. The Acer is a Veriton M275 series. I will provide the UEFI as soon as the system finish creating the image.
Thank you for all your assistance.
-
[quote=“DarkEnergy, post: 40719, member: 26785”]You are focusing in the make an model when you should be focusing in the type of BIOS the system is running. Does your ACER is UEFI or just plain old BIOS? Many systems independent of the manufacturer use the same mobo with the same BIOS/UEFI in the board. For instance Many systems comes with AMI or Phoenix BIOS. It would be more beneficial to pain attention at the type of BIOS and file systems. For instance in my case I have to use GPT as part of the UEFI as I cannot disable UEFI. The Acer is a Veriton M275 series. I will provide the UEFI as soon as the system finish creating the image.
Thank you for all your assistance.[/quote]
DarkEnergy,
We’re trying to get the make and model because we want to see if we have any body with the same make and model so we can replicate the results. Focusing on the make and model is the only way to ensure your system will work and we have a duplicate system. The BIOS is not relevant as a manufacturer (in many cases) can customize the BIOS. This is why some systems use Secureboot and others might use Windows Mode or some description of some sort.
All we’re trying to do is help. I assure you, giving us your exact make or model (even if we don’t have it within ourselves) will go leaps and bounds as we can possibly find an emulator to work off if (hopefully).
-
Hi Tom:
Yes, I understand where you coming from but base on my experience I have seeing many systems using the same mobo with the same BIOS. While, as you mention, companies can customized the BIOS there are minor modifications. The idea was focus on other possible FOG’s users withe different make and model (feel like I am talking about a car…LOL) but they have the same modo with the same BIOS.
BTW:
The BIOS/UEFI is: Version 2.15.1227 AcerThank you.
-
Right, but the if we have the make and model, cause most don’t keep track of the bios and maker of the mobo, they keep track of the make and model of the system.
It’s easier to ask for:
Who has Acer Aspire D255 v. 3.0?
VS.
Who has Motherboard ASUS H81M-A Firmware Revision 1.3.0a1753?
-
Um would this help at all?
“[SIZE=14px][FONT=Trebuchet MS][COLOR=#000000]1. Enter Bios from startscreen (Delete)[/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Trebuchet MS][COLOR=#000000]2. Select “Authentication” (right key)
3. Select “Secure Boot” and set it to Disabled
4. Select “Boot Option” (right key)
5. Select “Launch CSM” and set it to Allways
*1 [6. Select “Boot Menu” and set it to Enabled]
[7. Select DVD, Removable Device or LAN as 1. Boot Device][/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Trebuchet MS][COLOR=#000000] [/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Trebuchet MS][COLOR=#000000]Press F10 and Yes
*1 [Press F12 from startscreen to select Boot Menu][/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Trebuchet MS][COLOR=#000000] [/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Trebuchet MS][COLOR=#000000]NB!! Remember to set back 3 and 5 when you are finished another boot device.[/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Trebuchet MS][COLOR=#000000] [/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Trebuchet MS][COLOR=#000000]Regards[SIZE=14px]” ~[/SIZE][FONT=Tahoma][COLOR=#141414][url]http://community.acer.com/t5/Desktops-All-In-Ones/Aspire-5600U-Bios/td-p/201413[/url][/COLOR][/FONT][/COLOR][/FONT][/SIZE] -
I’m having some similar issues with some Dell Optiplex 740’s. Secure boot doesn’t exist for the BIOS on these pc’s. The error I’m getting is Could not boot: Input/Output error ([url]http://ipxe.org/1d0c6139[/url]). tftp and http go through without any issue. I’m not sure what is causing this issue and why an Optiplex 755 will go though pxe perfectly fine.
Edit: I’m currently on SVN 2873. I know fog 1.2.0 worked with the 740’s.
-
Update:
I gather what you are saying Tom. Many don’t even know what exactly is a BIOS and the differences between a BIOS and CMOS. Most people that build computers just put pieces together but “COMPUTER’S BUILDERS” or “GAMERS” will know more about the hardware than many people that fix computers. That is because they base performance on many low level information. However, I still see your point.
Created and image with RAW and when it was reimage to same machine from which the image was created; the image was corrupted. I am starting to give up on FOG supporting Windows 8. I have invested a week so far in this issue and have not answers to any of my questions. I will be moving forward with a different solution for Window 8. At this point the question rises; will FOG support Windows 10? As it has been noted those operating systems are base on Windows 7 but they are totally different animals.
For now I am done with this post.I want to thanks everyone that tried or try to assists.
-
In my experience “COMPUTER’S BUILDERS” and “GAMERS” know far less about computers then what they think they know. They know the benchmark stats on the latest-and-greatest hardware, but very little about how computers actually work. They base performance assumptions on low level information that they don’t understand.
Fog supports and flawlessly deploys every version of windows to date and has been tested against the windows 10 technical preview.
Fog does have some gaps in it’s support, like UEFI and quirks with the client software, but they are actively being worked on. -
[quote=“Junkhacker, post: 40846, member: 21583”]In my experience “COMPUTER’S BUILDERS” and “GAMERS” know far less about computers then what they think they know. They know the benchmark stats on the latest-and-greatest hardware, but very little about how computers actually work. They base performance assumptions on low level information that they don’t understand.
Fog supports and flawlessly deploys every version of windows to date and has been tested against the windows 10 technical preview.
Fog does have some gaps in it’s support, like UEFI and quirks with the client software, but they are actively being worked on.[/quote]There are all kind of test in the Internet most of them are pay-driven test for sale (advertising). I am not sure what kind of gamers you know but the one I relate and I play with are very savvy on hardware, including chipsets, front and side buss, transfer rate, memory access, CPU cache size (type of memory) direct and indirect buss communication and more. Perhaps they are not real gamers as they say.
I have installed Windows 8 on three different systems and the only one that works was an old HP Compaq DX2400 series that uses old BIOS with limited configuration.The BIOS is an old AMI Ver. 02.61 that when I installed Windows 8 and Windows 10 it works wonderfully. But when I go and install the same OS on newer systems it just don’t work. I even installed in a Lenovo B50 (make and model) and still no go. I have configured the BIOS and disable security and enable legacy and still fails. However, if I do it with Acronis it works just fine. That said, I am not sure at this point what is wrong. I will try Ghost and see if that give any hassle.
-
Look,
Knowing the BIOS and the Motherboard isn’t helpful. One because that motherboard could potentially be on any system which would easily be overlooked.
Based on the image name in your previous posts, my guess for the (simple question I guess that’s just been overlooked here) make and model is:
Acer ventron 2611
See how hard that was?
-
I updated to the latest Kernel that is available and I’m still unable to pxe boot to Dell Optiplex 740’s. It works perfectly fine on models 755 and up but it just won’t work on the 740’s. Besides the kernel update is there anything else I can try?
-
I don’t understand what the Kernel has to do with PXE boot files.
-
I read in other forum posts that updating the kernel fixed pxe booting for certain models of PC’s. I thought I would try it see if it would work for me. Unfortunately it did not.
-
Can you try the undionly.kkpxe boot file instead of the undionly.kpxe?
-
[LEFT]That got it to work. Thank you. My reasoning behind why I thought the kernel’s would help was because the kernels contain the bzImage files that go into the pxe service.[/LEFT]
-
What?
bzImage is loaded by the ipxe file after things are happening.
bzImage is after pxe service and is at the OS layer.
-
[quote=“Tom Elliott, post: 40893, member: 7271”]Can you try the undionly.kkpxe boot file instead of the undionly.kpxe?[/quote]
This is an interesting point. I have a DD-WRT router that directs to the FOG server, however, it doesn’t matter which image I use to try to boot as always redirect to to the default. Is that what has to happen?
-
The default.ipxe file is a generated file that tells the undionly where to get it’s information. All systems will always search for this file based on the proper setup. If some systems are failing with .kpxe, using the .kkpxe should correct that, but I guess I’m at a loss as to what the problem is.
