So I’ve been attempting for about a week to try out Linux Mint 17.3 - mostly because I’m completely at my wits end with Windows!
I’m attempting to boot live from a USB, and my laptop is an HP Pavillion running Windows 10, 64 bit (upgraded from Windows 8.1).
I’ve changed BIOS settings to Legacy, disabled Fast Boot and Secure Boot. I’ve tried multiple USB drives, and multiple software to prepare the bootable drives (LiLi, UniversalUSB and Rufus). I’ve even tried using Mint 17.2. Yet for some reason, regardless of what I do, I cannot get Linux Mint to boot as 64 bit edition - I get the notification ‘Unable to find a medium containing a live file’.
I have managed, however to boot the 32 bit version, which is progress! When I run the inxi -Fxz command in Terminal, this is what I get:
Hi Mark, I followed your steps and I get the standard start-up option screen, where I select 'Boot from a USB device (UEFI).
I then get a notification saying ‘Boot Device Failed - select OK to continue’. So I select ‘OK’ and press enter, then get taken to the Boot Option Menu, where there’s no option to boot from the USB device - just ‘OS Boot Manager’ and ‘Boot from EFI File’
I do have Windows 64 bit, and 64 bit Linux Mint 17.3 ISO…
I installed your software and attempted to boot from the USB - same issue. I get the option to select from Linux Mint 17.3, LM 17.3 Compatibility Mode, or to check the integrity of the medium. I select the full version, hit enter, then get a few minutes of the Linux Mint logo on the screen, followed by this:
'Device not accepting address 2 (then 3,4), error -62 ’
Then 'Unable to find a medium containing a live file system ’
Well I have 2 HP 15’s so can assure you that Linux flies onto them, so there MUST be a hardware problem somewhere.
Googling “15-n278sa linux” also return plenty of people who’re discussing which graphics drivers to use and how to overcome dropping wireless … so there’s no problem with that specific model.
The part I was referring to was adding the:-
usbcore.old_scheme_first=1
kernel boot parameter … do you know how to try that ?
Boot the live DVD and as soon as you see anything Mint related, hit the Shift key … to access the GRUB menu
Once at the GRUB menu, hit the ‘Tab’ key to edit the boot command line.
Use the cursor keys to navigate to “quiet splash”, and add usbcore.old_scheme_first=1 after quiet splash … so it now ends:
quiet splash usbcore.old_scheme_first=1
Still no joy with this Mark. I tried it on both USB sticks too.
I’m wondering, since you mentioned a hardware fault - could it be the USB drives I’m using? One is a SanDisk Ultra 3.0, the other an old micro SD USB converter.
I have a standard SD card here and SD slot - could I try booting from that somehow?
Ok, so I’ll get hold of another USB and give it one more try… To be honest though the whole reason I wanted to try LM out was with a view to installing it alongside Windows! From the brief experience I’ve had with the 32 bit version - I really like it So I’ll need to create a bootable DVD first?
Hi, I am a very experienced Windows user but a complete novice for Linux. I want to move to Linux to avoid the ever closer clutches of Microsoft with Windows 10 and later releases. Today I downloaded a Linux Mint ISO file and burnt it to a DVD, intending to try a test-drive before getting serious with re-partitioning my disc etc. When I boot into Mint I get the same issue as Cheiro, which does not seem to have been resolved. I have no idea what any of the suggestions are saying, so I don’t know where to go from here! Think of it like this - I want to learn to drive but I can’t even turn the engine on, so it’s no use telling me about umpteen technical things that could be wrong because I don’t know my head gasket from my water pump! I just need the car to be in working order! No criticism intended folks, honestly, but please could somebody tell me in simple but complete steps, from scratch, how to create a bootable DVD that will take me into the Mint desktop automatically at bootup? I am running Windows 7 on a 64 bit system with two large hard drives.
Thank you.
And did you check the ISO images MD5 checksum before burning it, to make sure the download didn’t become corrupt ?
(if you’re unsure how to do this, just ask)