saturnian Posted October 8, 2018 Share Posted October 8, 2018 (edited) Okay, as I was saying in another thread, I have two newer notebooks that don't seemed to want to boot my flash drives that have MX-17 or GParted Live on them. The other distros that I have on flash drives boot fine, but when I try to boot with either the MX-17 flash drive or the GParted Live flash drive, I get taken to the boot screen of the installed system rather than to the ones I'm trying to boot from the flash drives. Looking at one of the computers now, HP 15-ba015wm. From GParted on an installed system, I go to View > Device Information and I see "Partition table: gpt". Here's what I'm seeing in the setup utility: InsydeH20 Setup Utility Rev. 5.0 System Configuration > Boot Options POST Hotkey Delay (sec) - <0> CD-ROM Boot <Enabled> USB Boot <Enabled> Network Boot <Disabled> Network Boot Protocol <IPv4+ IPv6 (UEFI)> Legacy Support <Disabled> Secure Boot <Disabled> Platform Key Not Enrolled Pending Action None Clear All Secure Boot Keys Load HP Factory Default Keys UEFI Boot Order Internal CD/DVD ROM Drive USB Diskette on Key/USB Hard Diskette OS Boot Manager USB CD/DVD ROM Drive ! Network Adapter Legacy Boot Order (this part is grayed out) From inxi -Fxxx, the "Machine" section: Machine: Type: Laptop System: HP product: HP Notebook v: Type1ProductConfigId serial: <root required> Chassis: type: 10 serial: <root required> Mobo: HP model: 82F6 v: 40.42 serial: <root required> UEFI: Insyde v: F.25 date: 08/10/2017 And, from inxi -f: CPU: Topology: Quad Core model: AMD E2-7110 APU with AMD Radeon R2 Graphics bits: 64 type: MCP L2 cache: 2048 KiB Speed: 998 MHz min/max: 1000/1800 MHz Core speeds (MHz): 1: 1044 2: 1023 3: 1141 4: 1013 Flags: 3dnowprefetch abm acc_power aes aperfmperf apic arat avx bmi1 bpext clflush cmov cmp_legacy constant_tsc cpuid cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid fpu fxsr fxsr_opt ht hw_pstate ibs lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor movbe msr mtrr nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 ptsc rdrand rdtscp rep_good sep skinit ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 svm svm_lock syscall topoext tsc tsc_scale vme vmmcall wdt xsave xsaveopt What am I missing here? Edited October 8, 2018 by saturnian Quote Link to comment Share on other sites More sharing options...
securitybreach Posted October 8, 2018 Share Posted October 8, 2018 Well unless your flash drives are GPT partition tabled, they will not be able to boot because of Legacy Support Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 8, 2018 Author Share Posted October 8, 2018 Hm. I've been following the same steps to prepare a flash drive for every iso I try. I clear the flash drive with: $ sudo dd if=/dev/zero of=/dev/sdb count=100 Then, from GParted, I create a new partition table (msdos) and a new partition (FAT32). Then I copy the iso to the flash drive. I have my Kubuntu 18.04 flash drive plugged in right now. GParted shows the flash drive's partition table as msdos. Yet this flash drive boots both UEFI notebooks, as do all of my other flash drives, except for the ones with MX-17 and GParted Live isos copied to them. So perhaps you can understand my confusion here. So, for MX-17 and for GParted Live, I'd have to make the flash drive's partition table gpt, even though I haven't had to do that for Kubuntu and the other distros??? I mean, that's cool and everything, maybe things are different with MX and GParted Live. Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 8, 2018 Author Share Posted October 8, 2018 OK, regardless of why the other distros boot those notebooks even with msdos partitions on the flash drives, I'll go ahead and download the GParted Live iso again, then make a gpt partition table on the flash drive and copy the iso the flash drive, and that should take care of it. Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 8, 2018 Author Share Posted October 8, 2018 No luck so far. I downloaded gparted-live-0.32.0-1-amd64.iso. Checked the md5sum. Cleared my flash drive as noted above. From Debian Stretch, I opened GParted, created a new partition table (gpt) and a new FAT32 partition. Checked the partition table again with GParted to make sure it was still gpt. Then I copied the iso to the flash drive. After that, I again used GParted in Debian Stretch to check the flash drive's partition table, but now it says it's a msdos partition table!!! I have no idea why that happened. So, the flash drive won't boot either UEFI notebook, and it boots the older notebooks with no problem. I did all of this twice, same results. Lol, this is all very interesting but I'm gonna have to let it go for now, got other things to attend to. securitybreach, thanks very much for trying to help me out. 1 Quote Link to comment Share on other sites More sharing options...
securitybreach Posted October 8, 2018 Share Posted October 8, 2018 Not a problem Quote Link to comment Share on other sites More sharing options...
raymac46 Posted October 8, 2018 Share Posted October 8, 2018 Anything useful here? https://mxlinux.org/wiki/system/uefi Quote Link to comment Share on other sites More sharing options...
sunrat Posted October 8, 2018 Share Posted October 8, 2018 You don't need a partition on your flash drive, the iso should overwrite the whole drive. Try this: Make sure you get the correct device name. Insert it and immediately do: dmesg |tail Write the .iso making sure you specify the correct device and use the whole device, not a partition ie. sdX not sdX1. Replace the X with the drive letter you found with dmesg: dd if=MX-17.1_<insert_exact_name_of>.iso of=/dev/sdX bs=4k ;sync This is the exact command I use and it has always worked. Note the device needs to be not mounted for dd to run! It's highly recommended to install from the latest snapshot which is currently MX-17.1_September_x64.iso IIRC there were updates including installer updates which may help. Latest snapshots are always available from here: http://mxrepo.com/snapshots/ Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 9, 2018 Author Share Posted October 9, 2018 sunrat, I didn't have a problem writing MX-17.1 to the flash drive. I wrote the iso to the flash drive only a few weeks ago (Sept 19, according to my notes) with the following command: $ sudo dd if=MX-17.1_August_x64.iso of=/dev/sdb bs=4m; sync That flash drive boots my older notebooks with no problem; it's only the two UEFI notebooks that it fails on. I've successfully used quite a few different flash drives to boot those two UEFI notebooks, with several different distros. The only ones so far that won't boot either UEFI notebook are MX-17 and GParted Live 0.32.0-1. I may try the lastest MX-17 snapshot if/when I get around to it. One notebook is currently running Arch and the other one is currently home to Debian Stretch, and I won't be replacing either of those installations any time soon. In the past, I've actually booted both notebooks into live sessions of of MX-15 and earlier versions of GParted Live (GParted Live 0.29.0-1-amd64 is one example -- I used that one to partition the hard drive on one of those notebooks!). FWIW, I was a Mepis user, back in the day -- I could always count on that distro. And I've always been able to count on MX and GParted Live, until now. Quote Link to comment Share on other sites More sharing options...
sunrat Posted October 9, 2018 Share Posted October 9, 2018 There was one other setting in UEFI setup I had to change to get it to boot. I had to change "Windows 8/10 Features" to "Other OS". It's a Gigabyte H170 <something> mobo. Quote Link to comment Share on other sites More sharing options...
abarbarian Posted October 9, 2018 Share Posted October 9, 2018 I use a MX-17 usb live in a legacy laptop and also on my UEFI desktop with no problems. The desktop has "secure boot and fast boot" disabled. if that helps to muddy the waters at all. Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 10, 2018 Author Share Posted October 10, 2018 I use a MX-17 usb live in a legacy laptop and also on my UEFI desktop with no problems. The desktop has "secure boot and fast boot" disabled. if that helps to muddy the waters at all. Ha-ha! Yeah, if there's one thing I've learned over the past few days, it's that when it comes to UEFI/Secure Boot and all that, the waters can definitely be muddy! Thanks for all the help, folks! Y'all are great and I really think that more people should come here for help. I'll keeping putting the good word out about these forums, for sure! Well unless your flash drives are GPT partition tabled, they will not be able to boot because of Legacy Support <Disabled> I do have several flash drives that have msdos partition tables (according to GParted) that for some reason will boot my UEFI notebooks, even though (as I'm understanding things) they shouldn't, not with legacy support disabled. I also have one (which I've used to install Kubuntu 18.04) that GParted shows as having a mac partition table! I didn't create that partition table! Check this out, this is from parted: Model: SanDisk Cruzer Blade (scsi) Disk /dev/sdb: 32.0GB Sector size (logical/physical): 2048B/512B Partition Table: mac Disk Flags: Number Start End Size File system Name Flags 1 2048B 6143B 4096B Apple 2 1840MB 1842MB 2392kB EFI Anyway, that one also boots the UEFI notebooks. I've been digging through my notes, looking back on what I've done in the past with these two notebooks, and also looking stuff up online. I'm learning a lot but also finding lots of confusing info. Kinda fun, in a way. Quote Link to comment Share on other sites More sharing options...
raymac46 Posted October 10, 2018 Share Posted October 10, 2018 Have you tried a new 3.0 compatible USB drive? If the one you have will boot on one machine and not another, that sounds to me like hardware. 1 Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 11, 2018 Author Share Posted October 11, 2018 Nope, I don't have a USB 3.0 flash drive (yet). A friend of mine sent me a link to some interesting stuff: http://www.rodsbooks.com/efi-bootloaders/csm-good-bad-ugly.html I've been very busy with other things and I'll have to get back to this topic later. Quote Link to comment Share on other sites More sharing options...
raymac46 Posted October 11, 2018 Share Posted October 11, 2018 A bit more data. I have MX-17.1 installed on an old HP laptop from 2012. I downloaded the latest MX 17 snapshot ISO and burned it using MX-17's excellent Live USB maker. This thumb drive ISO booted on the old laptop, and also on my Lenovo Flex2-15D laptop which has UEFI enabled and also runs Windows 10. The MX-17 USB maker does set up the drive to use UEFI. 1 Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 15, 2018 Author Share Posted October 15, 2018 Finally, I have some time to take a look at all this again, but I'm very close to giving up. I'm reading the info here: http://www.rodsbooks...d-bad-ugly.html It's just that my installed systems (Debian Stretch on one notebook and Arch on the other) are booting fine, and I don't want to mess around with the Setup Utility on either of these two notebooks just to try to boot the MX-17 and GParted Live flash drives, especially since I don't really need either distro at this point, and especially after reading what was written at the page linked above. It's becoming quite clear that what works on one computer won't necessarily work on another computer, even if they seem to be quite similar. Also, various distros are doing things differently. And there's a lot of incorrect info out there on the web. One thing, though, kinda unrelated, regarding something I mentioned earlier, about the flash drive with Kubuntu 18.04 on it: Why does parted show that one as having a mac partition table? I certainly didn't specify "mac" when I created that partition table! Does anyone here know anything about this? I haven't had any problems booting either of these two notebooks with that flash drive, and earlier I installed Kubuntu 18.04 on one of the notebooks, using that flash drive (later, I wiped Kubuntu and put that distro on an older notebook, for reasons that have nothing to do with this discussion). Quote Link to comment Share on other sites More sharing options...
raymac46 Posted October 15, 2018 Share Posted October 15, 2018 One further data point. The USB drive with MX-17 I created boots fine on an Acer desktop which is an all-Intel system. The thumbdrive is a 16GB Verbatim and shows up as (UEFI) Verbatim in the boot order. I did not use any sort of partition editor prior to letting the MX-17 Live USB creator do its thing. Just went with defaults. The other two laptops I tried with the thumbdrive were AMD APU machines so the source of technology isn't an issue. Quote Link to comment Share on other sites More sharing options...
raymac46 Posted October 15, 2018 Share Posted October 15, 2018 AND one last final machine. I booted the thumbdrive successfully on my main Linux desktop - AMD A8-5600 APU with R7 360 video card. This machine has a Gigabyte BIOS that supports both Legacy and UEFI. Posting from it now. So my bottom line is that the MX-17 Live USB creator has done a good job and I can get the drive to boot on a variety of laptops and desktops. This probably doesn't do much to help saturnian though. Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 16, 2018 Author Share Posted October 16, 2018 (edited) So for MX I could try the MX-17 Live USB Creator, on an older notebook, from a live session. I'm guessing that this would be a good way to go. My approach has been to use dd to clear the flash drive, then GParted to create the partition table and to do the partitioning, then dd to write the iso to the flash drive, all from an installed system. It's been a very reliable approach, except in this case, I can't get the MX-17 and GParted Live flash drives to boot these two newer notebooks. I'm assuming that I would not be able to use MX-17 Live USB Creator to put GParted Live on a flash drive. I prefer to stay with the command line approach as much as possible. The GParted Live documentation (https://gparted.org/liveusb.php) mentions four approaches -- Tuxboot, "Manual" (using a zip file and makeboot.sh), Unetbootin, and "Manual - Overwrite" (using an iso file and dd). I'm gonna pass on trying Tuxboot and Unetbootin (I've gone with Unetbootin in the past, with mixed results). I have a flash drive that has KNOPPIX 7.7.1 on it. I did that one about two years ago, using flash-knoppix from a live session, which I was running from DVD. That flash drive boots both newer notebooks beautifully! Edited October 16, 2018 by saturnian Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 16, 2018 Author Share Posted October 16, 2018 Success with GParted Live 0.32.0-1, using the zip file approach as shown at the GParted Live site! Booted both newer notebooks. I followed the steps there and found that it was not necessary to run makeboot.sh at the end, because that's "for making a bootable disk with MBR partition table" and I'd created a gpt partition table. Before trying with the zip file, I made another attempt with dd and the iso file. What keeps happening is that each time I write the iso to the flash drive with dd, the partition table changes from gpt to msdos (!!!). So then the flash drive won't boot my newer notebooks. When I used the unzip command with the zip file, the partition table remained gpt, and the flash drive worked for me. OK, so maybe I'll try a different approach for MX-17 later, but for now I'm happy about being able to boot GParted Live on both of these notebooks! 1 Quote Link to comment Share on other sites More sharing options...
raymac46 Posted October 16, 2018 Share Posted October 16, 2018 I don't think the MX-17 live USB creator is all that much different from a CLI approach. You see the commands being executed in a window, that's all. It does have a few tricks to get the stick formatted correctly for UEFI. I don't see why a live version on USB could not format another USB stick as long as you can plug in two thumbdrives and know which one to format. Personally, I never bother with trying to set up partitions on a USB drive. I just get a USB installer that works for me. Linux Mint has a good one, and if I try it with Windows there is Rufus or LI-Li USB Creator. Quote Link to comment Share on other sites More sharing options...
saturnian Posted October 16, 2018 Author Share Posted October 16, 2018 I don't see why a live version on USB could not format another USB stick as long as you can plug in two thumbdrives and know which one to format. Yeah, that should work. Not sure if/when I'll get around to trying it for MX-17; I'm finding that I'm losing interest in that distro, sorta like how I lost interest in Linux Mint. I've used Unetbootin in the past, but since it didn't always work, I kinda got turned off by GUI approaches. And there are definitely some advantages to going the CLI route. Also, I tend to prefer approaches that work with lots of different distros rather relying upon any one distro's special tools. But that's just me, different strokes for different folks. Quote Link to comment Share on other sites More sharing options...
raymac46 Posted October 16, 2018 Share Posted October 16, 2018 I've had mixed results with Unetbootin as well. The Linux Mint USB image creator has always worked for me though. Quote Link to comment Share on other sites More sharing options...
securitybreach Posted October 16, 2018 Share Posted October 16, 2018 I only use dd. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.