02-03-2020, 04:25 PM
(This post was last modified: 05-24-2020, 02:50 AM by firenice03.)
Hi, I've been distro "speed dating" for a year. (ha). About a year ago I installed 15 distros to compare memory use. I just did it again, with about 25 distros.
My impression has consistently been that there's something odd about Linux Lite's iso. The reason I say that: I've had virtually no trouble "burning" the other distros to USB flash (and booting them. I might have trouble with drivers loading, reaching a desktop. But, the flash drives are recognized and at least *start* to boot.). I've burned them using unetbootin, MX USB Maker, the dd command. They don't seem to care.
But, every time I try Linux Lite... it seems very particular. Either the USB flash drive isn't recognized by the BIOS as even available to boot from. Or, it is recognized -- but when I choose to boot it, it does nothing and hands-off to the hard disk (i.e., the USB flash drive will be accessed for 5-10 seconds, and then the hard drive boots as if that's what I choose.).
This has been on two different computers (an older Toshiba Satellite C55-B, and a new Acer Aspire 5 A515-43-R19L).
Yesterday I was able to boot Linux Lite 4.8 in a Virtual Box for the first time. (I love what I see. I definitely would like to "hop" to it sometime.). This morning I thought I would pursue the bootable "burning" problem further.
I see on your web page that it's only supposed to be burned with Etcher or the DD command. I tried both, but the resulting USB flash drive won't begin to boot (in the way I described above). When I try to open that device in gparted, I get an error: "Invalid partition table - recursive partition on /dev/sdb"
I'm raising this topic not so much as "how can I get this to work," but "why is it this way?" As I said, I have not had this experience with 20 other distros (maybe I've had it with Antix 19). And, I had this experience last April when I "speed dated" some distros. I'm having it again this time.
Linux is known to be frustrating migrating to it (from Windows). It seems like something's wrong with the Linux Lite iso in a way that would make that even a higher-friction experience. So, I'm raising this topic to try to help in some way. It's hard to believe it's just me (or, is it just me? I've tried two computers, different USB devices, burning it different ways -- including the Linux Lite-supported ways).
I'm willing to try things, and provide more info to track down what's happening.
My impression has consistently been that there's something odd about Linux Lite's iso. The reason I say that: I've had virtually no trouble "burning" the other distros to USB flash (and booting them. I might have trouble with drivers loading, reaching a desktop. But, the flash drives are recognized and at least *start* to boot.). I've burned them using unetbootin, MX USB Maker, the dd command. They don't seem to care.
But, every time I try Linux Lite... it seems very particular. Either the USB flash drive isn't recognized by the BIOS as even available to boot from. Or, it is recognized -- but when I choose to boot it, it does nothing and hands-off to the hard disk (i.e., the USB flash drive will be accessed for 5-10 seconds, and then the hard drive boots as if that's what I choose.).
This has been on two different computers (an older Toshiba Satellite C55-B, and a new Acer Aspire 5 A515-43-R19L).
Yesterday I was able to boot Linux Lite 4.8 in a Virtual Box for the first time. (I love what I see. I definitely would like to "hop" to it sometime.). This morning I thought I would pursue the bootable "burning" problem further.
I see on your web page that it's only supposed to be burned with Etcher or the DD command. I tried both, but the resulting USB flash drive won't begin to boot (in the way I described above). When I try to open that device in gparted, I get an error: "Invalid partition table - recursive partition on /dev/sdb"
I'm raising this topic not so much as "how can I get this to work," but "why is it this way?" As I said, I have not had this experience with 20 other distros (maybe I've had it with Antix 19). And, I had this experience last April when I "speed dated" some distros. I'm having it again this time.
Linux is known to be frustrating migrating to it (from Windows). It seems like something's wrong with the Linux Lite iso in a way that would make that even a higher-friction experience. So, I'm raising this topic to try to help in some way. It's hard to believe it's just me (or, is it just me? I've tried two computers, different USB devices, burning it different ways -- including the Linux Lite-supported ways).
I'm willing to try things, and provide more info to track down what's happening.