Boot stuck on "VTloading....." #1374
Comments
|
You can try text mode |
|
Some old legacy bios machine boot the USB device fine only if the 1st partition of the USB device start from sector 63. |
Nothing to do. I set the cli mode through VentoyPlugson.sh, and in fact on other PCs I see the change, but the hp pavilion always remains blocked on VTloading. |
Thanks for the reply, there is nothing I can attempt then? |
|
Try other PCs/Notebooks? |
As I said, on other notebooks, ventoy works great in both gui and cli modes. It is only on the hp pavilion DV6 that, regardless of gui or cli mode, it gets stuck on VTloading.....? |
|
Sorry, I missed that! |
|
请问 之前进得去 现在死活进不去 百度到几个答案 说是内存太大 之前4+4 现在4+4+2+2 台式机没问题 笔记本死活不行 重做也不行 答案2 可以bios关闭安全启动，老点的电脑建议插USB2.0上。 没有安全这个选项 USB四个口都试过了 最近在学怎么建站 用PHPstudy 的 然后用工具改了IP啥的 然后二天开机就连不到网 转圈很久 |
|
I'm confirming this is still the case with |
|
This is STILL the case with v1.0.77 and the HP dv6 Pavilion 😐😐 |
|
Not everyone has a HP Pavilion dv6 pc on there desk - so we cannot test it to find out what could be the cause. |
|
Is USB drive listed in BIOS as USB Hard Drive (not floppy)? I have also seen on Google that you must use single USB port on right and must set USB as first boot device in BIOS ?? |
|
This might not be the case for this issue, but for me on a legacy BIOS system, disabling "Secure Boot support" in Ventoy fixed it. |
|
@sonic011gamer: Disabling secure boot should have no effect on legacy booting? |
|
same issue on hp pavilion dv7 |
It shouldn't, but it did solve the issue on a HP Pavilion G6. |
|
Some BIOSes do not allow legacy boot if Secure Boot is enabled in the BIOS. |
|
My laptop doesn't have secure boot option. I have hp pavilion dv7 laptop . I tried Ventoy with different configurtions too many times but is still not working for me. |
|
Hi, I have a HP DV6 with an I7 and have the same issue on "VTloading..." stuck, on previous version it worked, but now I does not. Any workaround on this? |
|
我遇到了同样的问题，开机卡在“VTloading”，最后是换了个内存条后恢复正常的。 |
|
I'm also trying to get around this, but only have the machine while I work on it. |
|
I've also recently come into possession of an HP dv7 (specifically the dv7t-6100) with this exact same issue and have to work around it using the old fashioned "Rufus" method of installing ISOs. The one thing I can add to this discussion however is that Ventoy does work when connected via the internal SATA, e.g. installing Ventoy to a SATA disk and then connecting that disk to the laptop's internal SATA connector (the dv7 even has two 2.5" drive bays, but mine only had a single SATA cable and therefore no way to connect a secondary SATA disk...) Also, curiously, I'm in possession of an HP DM1 laptop from around the same year, albeit with an AMD CPU rather than an Intel one (which the dv7 uses), yet the DM1 has no issues with Ventoy... I've also been able to use Ventoy on both much older devices (e.g. laptops from 2006 and 2007) as well as much newer devices (gaming handhelds with Ryzen 4000 and Ryzen 5000, so hardware that isn't even 5 years old) |
|
Another dv7 user here, stuck with the same issue. It's not a big deal, I suppose. I only wanted to use this for testing purposes, playing with Ventoy for the first time. It's just a bummer that it still doesn't work. I have version 1.0.94. Thanks all! |
|
I've the same issue with laptop Dell inspiron 17r-7720 I configured the BIOS to legacy boot. BTW, Ventoy was working fine using the same USB pen and laptop But after updating Ventoy to recent version (1.0.95) I no longer able to making it work! Make a fresh Ventoy installation using Linux Mint 21.2 USB Stick Formater didn't fix the issue! May you please help me to fix this issue. I really need to re-install Linux Mint 21.2 into my laptop EDIT: some screenshots
|
|
I tried another method for creating Ventoy pen by restoring Restore Disk Image... Unfortunately I got a similar message: |
|
IMPORTANT: I could run same USB pen on my friend laptop without any problem. This issue occurs on my laptop only :( My BIOS configurations: |
|
@mbnoimi Even though you're expriencing the same result, the fact that you're describing a regression and that it used to work on your non-HP laptop implies that you're experiencing a different issue. Therefore, I would suggest narrowing down what was the last version of Ventoy to work and what was the first version of Ventoy to not work, and then opening a new issue ticket specifically for your issue. ————————————————————————————————
Is there a particular reason for this? I personally find it better to install the OS itself via UEFI and then add a secondary legacy bootloader so that your hard drive/SSD can be booted on both types. More info:
You could try things the old-fashioned way: writing the Linux Mint 21.2 ISO using Mint's built-in disk image writer, or using Rufus from a Windows PC or VM, and just overwrite the entire USB disk with just the contents of that ISO temporarily, Another derpy workaround would be, If both your laptop and your friend's laptop do NOT have Nvidia graphics, then you can always just put your internal hard drive/SSD into your friend's laptop, install Mint 21.2 onto your hard drive/SSD, and then put your hard drive/SSD back into your laptop (this works with any combination of AMD and Intel CPUs and graphics—just no Nvidia). |
|
Thank you @NintendoManiac64 |
|
|
Well as luck would have it, I received one of these laptops from a customer who upgraded. It seems to have the same issue of not loading any version of ventoy. I tried to load 1.0.95 from an easy2boot drive and that freezes as well. So I don't believe it falls into the realm of the sector 63 issue. I do have a workaround method that works well. If I run duet efi bootloader and then run ventoy from there, it works fine. It would be nice to not have to do that though. Just to add, I cannot run grubfm at all either. It freezes when I try to run it as well. If you need me to run debug builds let me know. |
|
@tech128 What exact laptop do you have? I recently picked up a 2011 HP Pavilion dv6-6057ef that is BIOS-only (v1B if that helps) and gets stuck on |
The trick is to "install" Hiren's BootCD PE via the traditional method of writing an ISO to a USB drive, that being Rufus, Etcher, etc. ...and actually, since you said you used the optical drive, you could just as easily do that for Hiren's BootCD PE since it comes in ISO format and is roughly the same file size as Linux Mint. Once booted into Hiren's BootCD PE, you should be able to access any old USB flash drive or the like in order to access the files for updating the BIOS (while I've been able to successfully do this previously on a different laptop, I do know from experience that ther's a slew of software I've been unable to run on Hiren's BootCD PE, the firmware updater for Western Digital SSDs in particular comes to mind). Regardless, if you happen to have a spare SATA disk drive, you can actually install Ventoy onto that SATA drive and it should be able to boot just fine in your HP. This is key as, if the BIOS update doesn't work from Hiren's BootCD PE, then another option would be MediCat which I find has somewhat better support for running certain software but is a MUCH larger download at 20+GB (also you may want to follow the manual install process instead of using their installer) |
Just checked mine right now. It is a HP Pavilion dv6-6150us. BIOS Revision: 15.27 |
|
@NintendoManiac64 Thanks for trying to help. I did not need your tips eventually, but maybe they’ll help someone else. @tech128 Maybe we could start a "Does not work on"-list? |
Yeah that'd be fine. But in my job I've come across less older systems than I used to. So it might take awhile to find these systems that ventoy doesn't want to work on. I'm more interested in finding the cause of the issues. There has to be some reason it gets stuck. When I get some time, I'd like to try to see if modifying the boot image, so the first partition starts at sector 63 and also disable secure boot support in ventoy and see how that goes. |
It has nothing to do with it being an older system as my own Sandy Bridge-era HP laptop this occurs on is in fact the second newest laptop I own (my newest, a Thinkpad T420, is only half a year newer), yet I've had no issues with Ventoy on the various older laptops (at least as far back as DDR2-era systems) including another HP laptop that's only half a year older but uses AMD instead of Intel. |
|
So did you try disconnecting all usb devices except the Ventoy usb drive? |
I have. |
|
Also experiencing this issue, on an HP Pavilion DV7. |
|
Easy2boot now has Ventoy 1.0.97 so it may be worth trying. Make a new e2b usb drive with agFM and Ventoy added when prompted . |
|
Steve, I tried usin ventoy 1.0.97 right when it first came out hopin it would fix the issue. No dice. Also just tried to use grub4dos usb driver from easy2boot, it always says no usb device detected. I also tried plop boot manager 6 in the hopes that a different usb stack would work. That hangs on tryin to detect ehci for some odd reason. Also another weird thing I noticed. In addition to grubfm not wantin to load, the system locks anytime i try to load an initrd after a kernel memdisk. |
|
I am sure there is some incompatibility problem with the latest versions of grub. |
|
I don't know if this other information is also helpful.. the problem evidently is ALSO the bios. |
and others
Official FAQ
Ventoy Version
1.0.64
What about latest release
Yes. I have tried the latest release, but the bug still exist.
BIOS Mode
Legacy BIOS Mode
Partition Style
MBR
Disk Capacity
32GB
Disk Manufacturer
Kingston
Image file checksum (if applicable)
No response
Image file download link (if applicable)
No response
What happened?
I am trying to use a usb stick with ventoy on a hp pavilion dv6 pc. This has a legacy bios, so ventoy was written simply with
Ventoy2Disk.sh -i /dev/sdc.Now the problem is that when I go to boot from usb, I find myself a black screen stuck indefinitely with only written "VTloading.....".
I have tried various iso images in multiple different formats. I first had fat32 left, then I tried NTFS and finally ext4, but nothing has changed.
Finally I also tried to reformat with the secure boot -s option (even if this is not necessary for my bios), but this too was useless. What else can I try?
The text was updated successfully, but these errors were encountered: