Linux Lite 5.0 RC1 Released

[minesheep]

Lite software was probably non functional due to bad network connection.

VirtualBox and Audacity installs fine from Lite Software here on RC1.

FYI - I just successfully installed Virtualbox with Lite Software. Works fine on my system.

[Valtam]

[member=9185]minesheep[/member] and my libblockdev-crypto2 fix?

[minesheep]

[member=9185]minesheep[/member] and my libblockdev-crypto2 fix?

[member=9185]minesheep[/member] please do:

Code:

sudo apt install libblockdev-crypto2
systemctl restart udisks2.service

and report back if that fixes it, I'll put it in the Final is it does.

Yes your fix is working. I also noticed the wrong passphrase is finally "incorrect passphrase" the old was "operation not permitted". For some reason trying with wrong password now takes nearly forever. Not sure if it was taking long previously. However entering correct passphrase in graphical LL5.0RC1 with your fix only takes normal amount of time.

[WytWun]

[quote author=WytWun link=topic=7231.msg51697#msg51697 date=1588172543]
I attempted to install this RC on my 32bit UEFI Lenovo 100S which has been problematic with previous versions.

I've done some more testing with this obstreperous device so an update...[/quote]
Yet another update...

The failure during the install turns out to be during writing the Grub configuration file to the ESP.  Because Grub can't find a configuration file during boot, but is able to determine the root device and everything else it needs it displays the grub> prompt.

After finding this Grub 2 rescue how-to, I was able to find the information required to use the linux, initrd and boot commands (see the Booting From grub> section of the how-to) to boot the installed OS.  Once booted, I opened a terminal and used sudo update-grub to create the missing Grub configuration file, and the subsequent reboot was completely normal.  In fact I'm posting this from 5.0rc1...

NB: because this machine has an eMMC drive rather than HD or SSD, I had to use /dev/mmcblk1p? rather than /dev/sda? for the root option to the linux command.

Observations:
- the Grub boot menu still says "Ubuntu" instead of "Linux Lite" (did you say this should be fixed for the final Jerry?)
- changing from the light to the dark theme from the welcome system didn't appear to give any feedback that the change had been applied, though when I opened an application it had.
- in the course of resolving this I tried booting a few other EFI capable distros - some could be booted from a dd style USB flash but others would only boot with a Rufus "file copy" flash.  I've not been able to determine what this machine's firmware doesn't like about the dd flashed images that it won't boot though.

[Valtam]

Observations:
- the Grub boot menu still says "Ubuntu" instead of "Linux Lite" (did you say this should be fixed for the final Jerry?)

No, I gave instructions for how to alter.

How did you burn the ISO, with Etcher?

[iAnART]

hi! sorry for my question. still noob here.

is it possible to use the Linux Lite 5.0 RC1 kernel 5.x to the previous version?

[WytWun]

How did you burn the ISO, with Etcher?

As noted here this machine doesn't recognise any Etcher flashed 5.0rc1 USB stick as bootable.

[Valtam]

As noted here this machine doesn't recognise any Etcher flashed 5.0rc1 USB stick as bootable.

I did read that originally. It's extremely hard to accept that one machine cannot recognise any Etcher flashed drive. I'm not saying it's not true, understand that. It should not be showing up as 'ubuntu' in your boot-from-device menu, I also have an entry called 'ubuntu' but I select the actual name of the USB drive to boot from it ie. 'External USB Hard Drive'. That works no problem.

[WytWun]

[quote author=WytWun link=topic=7231.msg51940#msg51940 date=1589892446]

As noted here this machine doesn't recognise any Etcher flashed 5.0rc1 USB stick as bootable.

I did read that originally. It's extremely hard to accept that one machine cannot recognise any Etcher flashed drive. I'm not saying it's not true, understand that. It should not be showing up as 'ubuntu' in your boot-from-device menu, I also have an entry called 'ubuntu' but I select the actual name of the USB drive to boot from it ie. 'External USB Hard Drive'. That works no problem.
[/quote]
The 100S F12 boot menu with no USB drive present or with a USB drive that is not recognised as UEFI bootable (there's a single Linux Lite installation on this machine, nothing else - don't know why "ubuntu" is appearing twice):


The 100S F12 boot menu with a UEFI bootable USB drive present:


I checked a few 64 bit Linux distro ISO's from my collection to see whether Etcher could create USB installers for them bootable on this machine - sadly only a few have 32bit UEFI support .

The ones that would boot from Etcher flashed USB sticks:
- Mageia 7.1 Live XFce x86_64
- MX 19.1 x64
- a Linuxium Intel Atom specific re-spin of Ubuntu 20.04
- Rescatux 0.73

The ones that weren't recognised (in addition to Lite 5.0rc1):
- Clonezilla Live 2.6.6-15 amd64
- GParted 1.1.0-1 amd64

Clonezilla and GParted both boot when flashed with Rufus in "file copy" mode, same as Lite 5.0rc1.

The 100S has Insyde H2O™ UEFI firmware.  There are later firmware packages available than it's running which might improve the behaviour, but the available packages seem to be only installable from Windows which isn't something I'd consider re-installing at this point.  If I find a way to update the firmware from Linux I might attempt it but at the moment I'm not bothered as I can deal with the issues I've encountered.

BTW: While it would be great if the issues I've reported were fixed - if you can work out solutions - my posts about the installation headaches with this machine have been to document them and any solutions or workarounds I've found for the benefit of others who might encounter similar problems.  These sorts of issues will hopefully be pretty uncommon except for similar machines.

[Valtam]

my posts about the installation headaches with this machine have been to document them and any solutions or workarounds I've found for the benefit of others who might encounter similar problems.  These sorts of issues will hopefully be pretty uncommon except for similar machines.

Agreed.