USB key detection problem at boot time - live USB use impossible

Hello from France,

I purchased in October 2019 a Proteus laptop, and am facing the following problem with USB key detection by the BIOS.
First of all, my final goal is to set a dual boot Windows/linux ; I have to boot on a live USB key built from a .iso image file, but at boot, the BIOS doesn't always detect the plugged in USB key ! (But... sometimes it does however...).
(By "not detecting the USB key", I mean the BIOS does NOT propose the option of booting on the USB key, as it does for all the SSD and HDD present devices, PXE environments, etc.)

So, the final goal is to set a dual boot, but the real point of this post is to stress that the BIOS (I noticed it's a BIOS, not an (U)EFI ?) often does not detect plugged USB keys.

To install another OS, I have to resize the existing partitions, so, to do that, I downloaded .iso files from Gparted (about 400 kbytes), and then, Fedora (about 1.6 Mbytes) internet sites.
The iso are burnt on the USB keys with the "Rufus" tool which allows create live USB keys from hybrid ISO files.

What I noticed :
1/ I burnt the x86_64 .iso of Gparted (400 kbytes) on an Attaché PNY 1Gbytes USB 2.0 key : the USB key is not detected at boot (after choosing the right option in the BIOS, of course !)
2/ I burnt the i686 .iso of Gparted on the same key : the USB key IS detected at boot (it's the only case of detection)
(2.1 : once started, the display is not usable because the letters appear like "compressed Morse code" ; I imagine that the embedded distribution, an old Debian, doesn't support the graphical card... but this is another problem)
3/ Fedora only delivers x86_64 .iso files ; I burnt it on a Survivor Stealth USB 3.0 key 16 Gbytes ; the key is not detected at boot
4/ I burnt the Gparted i686 on the same 16 Gbytes USB key, the key is not detected

I repeated the same tests a few number of times each, and always had the same results.

So, my conclusion is, at first sight :
* the BIOS (Quanta QP161, build of May, 27th 2019) detects small USB keys, and only with i686-architecture burnt iso,
* the BIOS doesn't detect x86_64-architecture files on USB keys,
* the BIOS doesn't detect "big capacity" USB keys (or... USB 3.0 keys).

(Less and less .iso are created for i686, or older, architectures ; this will become a problem if x86_64 iso files are not supported...)

... and of course, both keys insertions work perfectly at normal operation (i.e, once W10 started), so I would say the BIOS is under suspicion.
I have of course ever successfully used this procedure to set a dual boot on another, older laptop.

Has anybody else, ever heard about, or experimented something like this ?

Is there a way to fix this ?

Thanks in advance for your help, and please forgive my poor level in English 😉.
 

Stephen M

Author Level
What is your main drive, if it is a NVMe SSD there are problems with Intel, automatically setting a RAID mode which makes it impossible to use Linux on the drive. If you have a standard HDD or SSD that should not be a problem.
 
Thank you Stephen, for such a quick answer.

My point is not (for the moment), to install linux but to detect the live USB keys which will allow (later) install linux (or do anything else...) ; for the moment, I can't even achieve this. Installing linux will come later...

1st storage drive : DISQUE DUR SEAGATE 1 To SERIAL ATA III 2,5 pouces AVEC 128 Mo DE CACHE (7 200 t/min)
1st M.2 SSD drive : 256 Go ADATA SX6000 Pro PCIe M.2 2280 (2100 Mo/R, 1200 Mo/W)
 

ubuysa

The BSOD Doctor
If you bought the laptop in 2019 then it's using UEFI for certain. I suspect that the tool you're using to make the Linux distro bootable is not able to make them UEFI bootable. Try using the Rufus tool instead, that can.
 
I did many experiments with the Rufus parameters combinations :), (MBR/BIOS or UEFI), (GPT/UEFI), with many types of formatting, and tried to boot with.

Nothing works, except the combination I indicated in my first post.

In between, I received a private email from PCS, indicating that, once the technicians asked, the USB keys were, indeed, not detected by the laptop during boot, and that I would be warned if PCS receives a fix for this.
 
Hello,

Just to end here, and help those who would face the same kind of problems... Note that the problem is related to my (new, recent) PCS laptop.

I finally achieved installing Fedora 32 as a dual boot on my laptop BUT, it was impossible with a live USB key, for at least two reasons :
- First, the only format detected by the uefi/boot of my PC is NTFS, and most of the tools for live USBs building don't let the choice for the format (and I imagine the one used, is NOT NTFS), except Rufus but I don't know any other ones (I tried UNetBootIn, Fedora Media Writer, another Fedora command line tool...). And it took me a while to understand this.
Second parameter to be taken into account : generate a live USB key to boot on a native UEFI system ("GPT" / "UEFI with no CSM" for Rufus ; other tools do not allow this being chosen/configured).
- Secondly, I came to the conclusion that most of the live USBs are NOT designed (yet ?) to run with native UEFI (which is also the case of my laptop, and slowly becomes the standard), that is to say, UEFI with no Compatibility Support Module (CSM) : even generated with the right parameters combination (NTFS/GPT with no CSM), something prevents the images from correctly booting till the end, with this type of boot (GPT/native UEFI) architecture.

(A noteworthy exception with Ubuntu which provides "out of the box" an iso image which, once generated as NTFS/native UEFI, allows to boot correctly until the end ! ... but I wanted Fedora :confused: ; also tried Linux Mint, Debian... with no more success)

My solution was to build a complete PXE environment, and boot from it : no problem of format anymore of course, but another one with the non support of the NVidia (recent, also) GPU driver (Fedora's installer is built with the free driver "nouveau", which does not support this GPU yet ; the solution was a use of a graphical option during installation in order to use a degraded, but sufficient graphic mode). Once installed, the suitable driver could be installed with the usual packages repositories.
... but this is another story.
 

ubuysa

The BSOD Doctor
Thanks for taking the time to post this. :)

It might be an idea to start a thread in the Linux forum with this information in it. I suspect that's where most Linux users will go for help. :)
 

truca

New member
I purchased in April 2020 a Proteus laptop, and I am facing the same problem.

I can boot without problems Windows 10, Acronis disk director / Acronis true image.

I have tried Rufus, balena etcher, easy 2 boot - all combinations (MBR/GPT, iso/dd ) with Ubuntu, Debian, Fedora - nothing works.

I was able to load superGrub2 beta from EFI but couldn't find the USB sticks.


1 USB stick 2.0 8GB + 1 USB stick 3.0 16GB - bootable in VMware and QEMU!


Very strange I was able to boot and install from USB 3.0 16GB KDE Manjaro; - also, live Linux...

same problem https://www.pcspecialist.co.uk/forums/threads/dual-boot.62540/#post-436831

same problem https://www.pcspecialist.co.uk/forums/threads/ubuntu-on-proteus-vi.62170/
 

ubuysa

The BSOD Doctor
I purchased in April 2020 a Proteus laptop, and I am facing the same problem.

I can boot without problems Windows 10, Acronis disk director / Acronis true image.

I have tried Rufus, balena etcher, easy 2 boot - all combinations (MBR/GPT, iso/dd ) with Ubuntu, Debian, Fedora - nothing works.

I was able to load superGrub2 beta from EFI but couldn't find the USB sticks.


1 USB stick 2.0 8GB + 1 USB stick 3.0 16GB - bootable in VMware and QEMU!


Very strange I was able to boot and install from USB 3.0 16GB KDE Manjaro; - also, live Linux...

same problem https://www.pcspecialist.co.uk/forums/threads/dual-boot.62540/#post-436831

same problem https://www.pcspecialist.co.uk/forums/threads/ubuntu-on-proteus-vi.62170/
I suggest you start a new thread in the Linux forum.
 
Top