Though casper/initrd are certainly loaded as part of every booting, I’ve never seen a countdown to them loading, i.e. they are near instantaneous. I can only imagine you have a machine limited in resources.WIthout more details, it’s hard to say anything definitive.
CPU: AMD Athlon™ 64 X2 Dual Core Processor 5200+
RAM: 4 GB
Did the integrity check pass?
yes, every time. The user should be able to choose if he/she want to run it or not and not that it’s started every run
And you have this exact same problem with both 20.04 and 20.10? Have you tried other flavors like Xubuntu to see if they have the same situation?
Furthermore, given you suggest elsewhere that this machine has hardware problems, are you sure your issue isn’t somehow related to similar problems? Linux can do wonderful things but it can’t fix broken.
1 Like
I didn’t tryed any else, except the server version, with has the same issue with missing wifi drivers and not installed required packages, so I think it may be a Ubuntu (and any derivatives) related issue, but it need to become checked by more people to become confirmed as a bug
The wifi drivers is no surprise because there’s a long history of closed sourced software being needed to run them and that runs against the whole notion of most Linux distros. I’m not talking about that.
I’m talking about the delay before the integrity check. Did you see that anywhere else?
I haven’t paid much attention to the screen whole time, just some quick looks in the mean time and when I did that, I saw only counting up the loading of as first of a strange bz-image with given info and size of 13 M and after it the counting up of the casper/intrd with the size of 91 M.
What you saw is something I have never seen, even on the slowest of machines I’ve used. I’m becoming increasingly convinced your issue is related directly to your hardware failing to function as it should.
1 Like
Just an FYI:
The defaulting to verify the image integrity before installing is the same for Ubuntu and all flavors.
It was introduced roughly a year ago, but that is not Lubuntu specific. Issues with that should be taken up at the Ubuntu discourse, or via bug report (the skip does work, but if you’re not ready to hit it at the correct time, it is easily missed, as once the scan has reached a certain point it won’t skip)
3 Likes
I was just recently playing with Lubuntu on a more-ancient computer, a generation previous. From inxi:
Dual core AMD Athlon 64 X2 3800+
It ran like a champ. I’m used to modern hardware and was so impressed by the performance that I remarked on it, with great verbosity, on linux.org just a couple of days ago. It was even more impressive when I swapped in an SSD and added RAM, but it was perfectly usable before that.
So, my guess is that there’s a hardware issue or maybe some sort of disk issue. Is the USB device old, maybe only supporting USB 1.1? Check those things, because Lubuntu runs just fine on that ancient computer.
3 Likes
Output results from Terminal:
systemd-analyzeThis topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
Is this still a problem?
it has self fixed after re-download of fresh iso
2 Likes
need manualy edit every time the grub cmd line when running from a live USB and add:
fsck.mode=skip fastboot
before “quiet”
This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.
More likely you were looking at a download and/or copy error with the ISO. These are horribly common.
I’d suggest just installing and then you can make it permanent. It will also boot a lot faster.
2 Likes