Installing Neon on Ideapad s205 - Some issues & questions with boot loader

Thomas Weissel valueerror at gmail.com
Mon Apr 8 08:58:22 BST 2019


i thought kde neon moved away fron the buggy ubiquity installer to
calamares??

if you want a fully configured image with all applications you will ever
need preinstalled and a preconfigured calamares installer (and patched
casper) that circumvents most ubiquity problems with uefi grub
installations try

http://life-edu.eu/download.html

i've run and installed this w/o problems on so many systems i lost count

also i've investigated a similar problem .. i had to specify the location
of the boot files on every boot..
in my case a specific part of the grub efi file seemed to be hardcoded to a
directory called "ubuntu" while my installation put the efi files in a
folder called "life"  - (kde neon puts those files in a folder called
"neon" and has implemented a specific switch in a capser file to copy the
files to the ubuntu folder in case of "neon"...  i therefore also patched
those files in the image to copy the efi files to the "ubuntu" folder
instead of the "life" folder and ignore the casper and hostname settings
for this part
could be related ..

cheers
thomas



David Hurka <david.hurka at mailbox.org> schrieb am Mo., 8. Apr. 2019, 00:20:

> Hi everyone,
>
> I “successfully” installed KDE Neon on a Lenovo Ideapad s205. This
> computer is known for its insane BIOS problems, which make installation of
> Linux painful.
>
> I have attached a file about my experiences.
>
> Now I have two issues remaining, can anyone here help?
>
> 1. I could generate grub.cfg, but Grub does not load it automatically. I
> have to load it everytime from the grub command line. Is it possible to fix
> that? (Probably only from within the grub command line itself?)
>
> 2. The installer (ubiquity kde_ui) always crashes when it tries to install
> the boot loader. It says that it was not possible to access something or
> so, but in fact, the boot loader is installed now. The problem is, that the
> resulting OS is somewhat broken, probably because the installation didn’t
> complete. I will fix some hardware problems now, and then try to install
> Neon again using ubiquity --no-bootloader kde_ui. Will this solve all
> problems regarding the broken OS installation?
>
> Nevertheless, thanks for providing Neon!
>
> Cheers,
> David Hurka
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/neon/attachments/20190408/81ef5f2a/attachment.html>


More information about the neon mailing list