true image 2017 -no Intel 7 generation support: invalid video frame buffer parameter - kernel error video setup mode 0x1480006
Dear support.
I'm a disapontend user. New version ATI2017 but no new hardware support. Again!
Device Notebook HP Probook 470 G4 i5-7200U/8GB/SSD m.2 256GB/1TB/FHD IPS/930MX/W10Pro (Y8B64EA#BED)
Processor Graphics: Intel HD Graphics 620!
Goal: Preinstall image backup
I've tried:
A. New Acronis ATI 2017 64BIT UEFI version 5554 Bootable image on CD
B. Old: Acronis ATI 2016 64BIT UEFI version 6581 Bootable USB.
I got The same error !!!!
For me this mean that: you have not updated the drivers of boot core of ATI 2017 its the same as ATI2016!
Procedure:
HP Boot F9 - boot option Boot from above A or B:
Screen result is the same:
>1
Please wait...
Loading protected mode kernel ... (ATI2017 loading 1 minute, ATI2016 loading 10 seconds and then I got)
Press <e> to edit kernel command line
Video mode setup error: Error 0x1480006: Invalid video frame buffer parameters.
| line info: 0xac98503a7af41d1
| $module: bootwiz_ef1a64_42
Kernel console may work incorrectly.
You have nicely updated the page of the products, with large photos and bare description what the product should does.
But there is no hardware supported list of manufacturer of chipset and CPU support.
Intel is the biggest on the market at lest them:
Like we support Intel Cpu Gen 1, 2, 3, 4, 5, 6,
Chipset Intel 110 170 ...
Des this mean that for you the Intel 7 generation product does not exsist yet?
If we want to use your product on new hardware I must use Win PE with custom embeded drivers for Intel 7 generation product!
Why?
Intel is a mainstream standard product!
Basicaly You sell and I buy a product which does not support new hardware.
When it will be available in a standard product as it should be already as intel pushed Gen 7 products?
Best Regards
Marko Gorenjc
I would contact support as well. However, your issue is that the default recovery media is Linux based and does not have drivers for your system. I don't think this has anything to do with the Intel chipset as I have an i5 6600K and the default linux media works just fine.. it even works with the latest NVME PCIE hard drives as long as the SATA mode in the bios is set to AHCI. However, there are instances where Linux does not have very good driver support...
1) if you are using NVIDIA optimus (or whatever AMD's version of it is), turn that off in the bios - this causes issues with the Linux bootable media as Linux doesn't have drivers for the fast switching of embedded to dedicated graphics. I suspect this is the real culprit here based on the specific error, but it's just a guess. Unfortunately, if your system cannot disable Optimus or if you can't pick a specific graphics card in the bios (embedded or dedicated only), the default linux recovery media does you no good on systems that use Optimus technology (or any technology that uses fast graphcis switching).
Or
2) Your system is usiing RAID in the bios as the SATA mode, which requires RAID controller drivers. Linux RAID support is not very good. Actually, WinPE doesnt' have Intel RAID support by default either so has to be injected seperately as well.
But there is a solution that simplifies this for you now... please see the sticky: https://forum.acronis.com/forum/127281
In your case, you need to build the WinPE bootable and using our MVP .bat script to start the process, this is very simple and allows for easy driver injection - it already includes the IRST drivers as well. Regardless of what OS you are running (7, 8, 8.1. or 10), download the Windows 10 ADK 1511 and install the 1st 3 components (roughly 3.4Gb though!). Once installed, you can either use the embedded rescue media builder in Acronis to build WinPE automatically, but won't allow you to inject any additional drivers that don't already come with the Windows 10 ADK. Or, use the .bat tool in the sticky and put your drivers in the correct folder (x86 or x64 - don't mix and match versions in the folders).
Dear Bobbo,
Thanks for Your reply.
I've used your WinPE bootable and using Yur MVP on a Win10-64bit PC.
1. HP 470 G4 i5-7200U (7 generation CPU and 7 generation graphic HD 620)
The default grahic is Intel HD 620 secondary Nvidia GT930.
I've tried changes in bios too.
But got the same error as in original post for: ATI2016 or ATI2017!
2. Thanks Ive used Your MVP and tryed to embed the driver for Intel HD 620:
link: https://downloadcenter.intel.com/product/96551/Intel-HD-Graphics-620
Made first: ATI2017 Linux Boot.
But got the same error in ATI2017. I dont know if maybe the graphic driver cant embed well in MVP Linux CD.
Made second: WinPE with ATI2017 and tryed to embed the driver for Intel HD 620:
Then Ive made a MVP WinPE but the system doesent boot from the DVD media - it remains stuck.
Probably' Ive made something wrong, or the driver in:
link: https://downloadcenter.intel.com/product/96551/Intel-HD-Graphics-620
wasent named formated correctly for embeding.
Your help regarding this would be apreciated.
I have systems with Intel 6 generation technology and the ATI2016 and ATI2017 linux works BOOTs OK.
Acronis has the problem supporting New Intel network cards - ATI boots but has no network.
This problem solution is described in Your MVP inject WinPE - as again newer network drivers from Intel are not supported in Linux.
I use Acronis products for 10 years. I vas a satisfied user which has recomanded the product.
But from september 2015 I'm a disapointed user.
I post here becouse user must know that NEW Equipement developed by Intel:
embeded graphic
Storage boot IRST (Raid, nvme)
network cards
are NOT supported from Acronis default Linux boot, or default Acronis USB linux products:
ATI 2016
or
ATI 2017!
User buys a product which doesnt work for him!
Acronis doesnt provide us with a time line to let us know when it would be supported!
Regards, Marko
A couple of things...
1) Please do a full format of your USB flash drive that you want to build the recovery media with. This takes longer, but will ensure the system volumen inforamtion with the boot information is wiped out - just in case. Do this before you build the media again.
2) What version of the Windows ADK do you have installed presently? If you have Windows 10 ADK 1511 or the latest, that should work for building WinPE in this case.
3) The intel embedded graphics of the HD620 should not be an issue with the Linux or the WinPE media, but let's focus on the WinPE media for now to ensure that you have good NIC driver support. I looked up your system specs and there is no secondary graphics which is good.
That said, HP does have their own WinPE driver packs: https://ftp.hp.com/pub/caps-softpaq/cmit/HP_WinPE_DriverPack.html I would suggest you delete the drivers from the graphics from the MVP tool driver folder. Download the Win10 PE driver pack from HP. Use 7zip (it's free) to rextract the content of the sp77392.exe that you'll be downloading from HP. This will have the NIC drivers you need/want as well as any storage drivers that may be necessary for yoru system.
sp77392.exe (open archive with 7zip) >>> blank folder >>> WinPE10.1.20 >>> x64_winpe10 ... copy the x64_winpe10 folder into the x64 folder of the MVP tool driver\x64 directory. Now launch the too and make sure that you are building the 64-bit media builder and not the 32-bit one.
-------------------------
As to the other comments about recovery media support. Acronis only uses Linux as the default because it is open-source and a fully built recovery media (.iso) can be distributed. They're the only backup software I know that provides this and it can be very handy to be able to download a prebuilt .iso from another machine and burn it so you can use it if need be on a failed system. This does not prevent you from building WinPE media though and it is offered as a secondary option. Personally, I also feel that this area can be improved and I have been providing feedback to Acronis to try and get this considered since the newer hardware is limited with the Linux media. In the meantime, the MVP's (Acronis volunteers - we built the tool in our spare time for fun to try and help others) built the tool to try and help others like yourself.
I have no doubt that the media itself, the WinPE created by the MVP .bat tool, is completely usable on your machine. Acronis aside, WinPE is Microsoft Windows under the hood (the same you would use to boot a Windows installer disk or a Windows system repair disk). If you can't boot this, there are other issues at play.
For now, go through the steps mentioned above in this post and resport back if you still get the error or not. If you do get the error, we need to look at your bios settings...
- Perhaps safeboot needs to be disabled in the bios first.
- Or, perhaps it's possible that Windows 10 Fastboot is the problem. Fastboot is enabled by default. When you "shutdown" your pc, it's really only going into hibernation and that hibernation file locks the hard drive so that other third party tools can't access it. You can either turn off hibernation in Windows (which turns off fastboot in the process). Or, when you "restart" instead of "shutdwown" that forces a full shutdown before starting up again. Alternatively, if you shutdown using command prompt and "shutdown /s /t 3" it will force a full shutdown instead of a fastboot shtudown (with a 3 second delay instead of the default 60 second delay)
- Or, perhaps this system is trying to boot in legacy mode, but you need to ensure that you're booting the USB flash drive in UEFI mode, by using the one-time boot override menu.
I'm sure we'll get to the bottom of this.
Dear Bobbo,
Thanks For your reply and valuable help.
1. I've made a WinPE DVD image not a USB one.
2. Downloaded nd installed Win 10 ADK 1607 on OS Win 10 pro 64bit ver 1607
3. Ive tried with Intel driver download not HP WinPE 1.20. I will build again WinPE based on your suggestions.
Setup in treported mode: Bios: Disabled fast boot, disabled protected mode, UEFI boot
Ill try legacy boot
Started ATI boot only after a restart procedure from Win 10 (not shut down - eg. disk hibernation for fast boot).
I'm not able to test your suggestions until next friday.
I will reply as I try your suggestions and have the results.
Then we may have a solution for all users.
My problems started with Acronis when new Intel products roled out (ewerything worked great unitl september 2015).
The Acronis Linux Boot CD ATI2016 - New Intel nic problem:
119944: Intel nic no detection I219LM GbE LOM - again you helped for a workaround!
There is no acronis linux solution (as I know) Yet. The problem is Wide is not only for Acronis True Image other Acronis product are affected with tihis problem too - as writen in forum and knowledge base.
I understood they are working ti solve problems.
But on Acronis page there is no information on New hardware limitaitons / problems for Linux Boot *
*You must build your own WinPE as a workaround to be used on New eqipement which uses thelatest Intel solutions.
People would not buy such a product .
Personaly If something desn't work correctly with Acronis Linux boot I use Linux Mint 18 cinnamon Live (version I used when I post this) to see if Linux does already support the devices as default (not custom implementation).
I understood that Linux Mint is a wide community and for this reason in front and leading in linux enviroment - but solutions for the drivers are there.
Sure they need implemention from Acronis teamwhich works on Linux.
A long lasting success for Acronis was its Linux boot media - The implementation of Linux with HW drivers was great worked for me.
And I hope Linux boot media - included with new driver implementation is still one of Acronis high priority task.
I'm awaiting any result from Acronis.
Still waiting.
But time goes by and we still need to talk and test how to build WinPE for major HW brand Intel.
I've paid for a product and now You, the community and Me have to invest our people, resources and time for the workaround.
I've already payed for the product, developement and support to Acronis.
Regards Marko
Hey Bobbo,
I had a similar issue when attempting to boot from the rescue media on new HP Probook 440 G4's making image deployment with Acronis 2017 impossible. Instead of using MVP and building a Win-PE (beyond my ability at present) I disabled fast boot which was one of your suggestions and it worked slick! Thank you for that. I would like to learn how to build recovery images with injected drivers but time is always working against me. I do appreciate the efforts of folks like you whose unpaid work helps us all.
Best,
Shrewless
Thanks for the feedback and glad that turning of fastboot did the trick! I have it off by default on all of my machines with SSD's as the fastboot speed at bootup really isn't that much (if anything at all) and I've had issues with "locked" disks from fastboot hibernation or even hibernation files that fail to load properly which require a hard reboot anyway. Overall, not having fastboot enabled has had no negative impact and has made backups easier as well.
If you do find the time to make WinPE rescue media, I think you'll find the tool pretty easy to use - it's menu driven and the choices are basic with notes along the way. The hardest part is downloading and installing the Windows ADK in advance of using the tool, but that's basic too... just download, install, select only the top 3 options (3.4GB) and let it run its course. Then you're ready to use the MVP winpe builder tool to build yourself some custom winpe rescue media and you don't really have to worry about injecting any special drivers - just say yes to the "custom" option and it will inject the ones we provided already - those will be good for about 99% of most home systems.
First time I had to use Acronis 2014 on this as I need to get an image off it. And this machine won't allow Acronis to boot. I have done the following and nothing worked:
1. Disable fast boot
2. Made sure the USB/DVD are first before the m.2 SSD
3. disable secure boot (enabling legacy boot),
4. Tried VGA=ASK
Not sure what else to try. Any one have any ideas? This computer is only using it's internal video card. Which I believe is a Intel 620. It's an i7 7th gen processor.
Hey nizmoz,
There are a couple of things I had to do to get Acronis to boot on various systems. I'll list them for you but which might solve your issue will likely be trial and error.
1.) In the Secure Boot Configuration in the "BIOS" I had to select Legacy Support Enable And Secure Boot Disable.
2.) When using a USB3 flash drive to boot into Acronis I had to make sure it was plugged into a USB2 port otherwise it wouldn't see it as bootable - I don't have this issue any longer as switched to old USB2 flash drives for this purpose. I have no idea why this is but I suspect it is a driver issue.
I hope this helps with your issue but if not there are a good number of bright well-informed people on this site so I am sure someone will be able to help.
I've done #1. Didn't help. I've also been booting from my good old CD that I created with Acronis.
:(
Hey nizmoz,
There are a couple of things I had to do to get Acronis to boot on various systems. I'll list them for you but which might solve your issue will likely be trial and error.
1.) In the Secure Boot Configuration in the "BIOS" I had to select Legacy Support Enable And Secure Boot Disable.
2.) When using a USB3 flash drive to boot into Acronis I had to make sure it was plugged into a USB2 port otherwise it wouldn't see it as bootable - I don't have this issue any longer as switched to old USB2 flash drives for this purpose. I have no idea why this is but I suspect it is a driver issue.
I hope this helps with your issue but if not there are a good number of bright well-informed people on this site so I am sure someone will be able to help.
Nizmoz, what kind of m.2 drive do you have? Is it an AHCI SSD m.2 or a PCIE NVME m.2. M.2 is just a form factor, and if it's SATA, then should "just work" as long as the drive is not in RAID. If it's a PCIE NVME m.2, the technology is newer than 2014. NVME and eMMC flash hard drive support didn't get added to default rescue media until late 2016. For most current OEM systems coming from the factory with m.2 PCIE NVME drives, they are also setting the bios to RAID instead of AHCI which also requires Intel Rapid Storage Technology (IRST) drivers which aren't available in even the most current default Linux rescue media. WinPE rescue media built with current ADK and the added injection of IRST is needed. Our MVP tool helps with this, but only works with 2016 and 2017.