If the integrity check succeeded, then it may be an issue of not enough resources. Otherwise, if it froze during or even near the end of the check, that may indicate a problem. Making use of zsync and/or manually checking the hashes on the ISO can confirm the integrity.
zsync worked. I ended up with a ~2 GB file. I tried first with Rufus, twice. I tried with uNetbootin - which only got me to a blinking cursor. I am now trying mkusb. I’ll try dd next. Hmm… mkusb uses dd, so that’s out of the question.
So far, no luck. I get even less far. This is now on bare metal. It’s an older dual-core AMD w/16 GB of RAM and an SSD. I know Lubuntu 18.04 works on it, as that’s installed on it at this moment in time. It installed with nary a hitch - and runs surprisingly well on that hardware.
Before I make any claims, I want to eliminate me as the problem.
I am going to give it a clean download one more time. I’ll also try it on different hardware.
LOL I may need some hand-holding until I’m fully onboard.
I have played with Groovy, but not tested it in any significant capacity. Groovy works just fine on that hardware. It’s not even slow. It’s surprisingly snappy, considering the age of the hardware.
It’s just this particular ISO that’s causing me issues.
You know what’s weird is that I can’t seem to get zsync to behave. It’s as if there’s some sort of network issue. Using HTTP rather than HTTPS, it’s a little more cranky but works as expected. Something is strange.
I am not sure. In some instances, it was stopping at just saying GRUB in the upper left on boot. That was with the rsync file. I downloaded it fresh, from the web using my browser, and then booted and it went to a blinking cursor - after the grub menu.
I ended up waiting about five minutes with the blinking cursor and then it turned into the 8 bit graphics type of thing where it didn’t look like the normal file checking screen. I let that complete and then a couple of minutes the screen popped up. Those times are rough estimates and not exaggerated.
It was much, much longer booting than it should be - even for booting from USB.
It never worked in VirtualBox, but I haven’t tried VBox with this newly downloaded ISO.
For some reason, I think the rsync’ed file was corrupt, but I was under the impression that shouldn’t happen.
Yeah one of the steps to zsync is actually checking the hashes. It’s like a necessary part of the protocol, just as error checking is a necessary part of torrents.
It works now. It also made me make a few changes. I can dedicate an entire desktop to testing, so can do so consistently. It’s an i5 with maybe 16 gigs of RAM and an SSD. It’ll be suitable. I don’t use it for anything. In fact, I just got rid of one just like it.
All that and I have nothing to report!
Also, I’m subscribed to all the mailing lists already. I’ve been there for years. I don’t normally post. I’m the ‘uninvolved@outlook.com’ (David) on the lists. I must have been subscribed for five years now, somewhere in that area.
The mailing lists are largely pretty quiet unless we’re doing announcements, calls for testing, etc. Most of the regular coordination and stuff happens in chat. We’ve got folks on there via IRC, Telegram, and Matrix, so there’s lots of options.
