VSIDO Community

VSIDO Controls => VSIDO Discussions => Topic started by: filip on March 29, 2017, 10:32:13 PM

Title: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on March 29, 2017, 10:32:13 PM
Hello VSIDO community,

It took a while, but better late then ever, trios-installer 7.0.7 has landed in master.  ???

In short, new/fixed stuff:
  1. Support for NVMe drives
  2. Workaround for issue #5 (https://gitlab.com/Cofi/trios-installer/issues/5) ( root pass was not set if it existed on live system ( as it does on VSIDO ))
  3. Fixed "bug" in automatic partitioning by explicitly depending on "os-prober". Bug was that auto partitioning quetly only ever offered
      a complete disk wipe, instead of additionaly finding ( using "os-prober" ) existing distributions to replace.

Merged from upstream:
  1. GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX are now preseedable ( important for VSIDO, see bellow )
  2. User groups are now preseedable ( both default and additional ones )
  3. Improved support for Mac's

For full changes list, please take a look here. (https://gitlab.com/Cofi/trios-installer/compare/f664f4792052738640534c6a28d898913db8e1bd...7.0.7-fd2)  :)



@NVMe:

Since I don't have the actual hardware to test properly, support for NMVe is fully tested on VBox only.
Even with that, it should be in good shape because it didn't require masive changes/additions, however usual caution
( backups/double checking summary before hiting "Forward" to begin install etc ) when installing on real hardware is still advised!

One known issue so far is that installer doesn't warn the user that, on legacy BIOS systems, booting from NVMe will fail!
Instead, it will happily perform the installation, but the system won't be bootable, 'cause AFAIK, no legacy BIOS supports booting
from NVMe devices.
This also applies to some older UEFI systems, however I don't think that there is a way to check this from installer or linux itself.

So, if you're about to buy NVMe SSD, and use it as the only drive in the system, be sure to verify that your BIOS can boot from it!
Otherwise, make sure that besides NVMe drive, you have:
- A regular hard drive/usb flash/SD card --> For legacy BIOS to boot from, if MBR partitioning scheme is employed
- A "/boot" partition on a regular hard drive/usb flash/SD card -- For legacy BIOS to boot from, if GPT partitioning scheme is employed
- Or "/boot/efi" partition on a regular hard drive/usb flash/SD card -- For UEFI's

And ofc, feedback on NVMe would be really apreciated!!  :)

@GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX:

In favor of upstream and this better and more granular implementation, I've dropped the "custom_kernel_args" preseed.

If I recall corectly "custom_kernel_args" is used in VSIDO to force persistent network names!?
If so, it needs to be replaced by either "grub_cmdline_linux" or "grub_cmdline_linux_default" ( or both )!

The difference between the two is that parameters in "grub_cmdline_linux" are passed to kernel in both normal and recovery boot modes,
while ones in "grub_cmdline_linux_default" are passed to kernel only for normal (default) boot.



Installer future:

Due to some real life craziness I've been AFK for a while, and as it seems, probably will be again.
"AFK" here means I simply don't have enough free time to actualy think about cool stuff/improvements,
let alone sit down to implement them ( and when I think I finally do, for some ungodly reasons I get proven otherwise ::) ).

So, until that gets sorted, in the nutshell:
- Installer will be in maintanance mode only == timely fixes for serious issues ( please do report (https://gitlab.com/Cofi/trios-installer/issues), if any is encountered! )
- Feature requests are of course welcome, however beware that it might take a while for me to get to them.

Cheers,
Filip
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on March 31, 2017, 09:57:52 PM
Great news Filip...

I started the process to build again but I think the How To Build the VSIDO Trios Installer (http://vsido.org/index.php?topic=1135.0) is now obsolete or files have moved

On any of the git clone commands I run it is wanting a login and password.. Do you know what needs to be used now?

Thanks
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on March 31, 2017, 10:08:38 PM
Logging in with my account shows:

Code: [Select]
fatal: repository 'https://gitlab.com/trios-linux/keeptalking.git/' not found
So everything has moved around it seems
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 01, 2017, 02:01:12 PM
I forgot completely, sorry.  :(
Yes, it has moved from TRIOS group to my own.

I'll update the How-To properly hopefully tonight, but in the mean time, quick fix is to replace "trios-linux" in links for installer, bricks, keeptalking etc with "Cofi".
Thus:
Code: [Select]
git clone https://gitlab.com/trios-linux/trios-installer.gitBecomes:
Code: [Select]
git clone https://gitlab.com/Cofi/trios-installer.git
Also, this time latest version of installer is in the master branch, so:
Code: [Select]
git checkout testingis no longer needed.  :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 01, 2017, 03:50:28 PM
^ No worries Filip ... got it installed with Cofi (and some good coffee too)

Regarding the refind section.. with these changes to add uefi and nvme is it still necessary for me to continue to do this?

Edit these files to take care of eufi refind that is not a part of VSIDO (yet)

Code: [Select]
sudo medit /usr/share/linstaller/linstaller/modules/bootloader/inst/_init_.py
Find and comment out these lines:

Code: [Select]
def refind_install(self):
""" Install REFIND """

if "uefidetect.inst" in self.moduleclass.modules_settings and self.moduleclass.modules_settings["uefidetect.inst"]["uefi"] == True:
verbose("Installing refind...")
m.sexec("/refind-inst.sh")
else:
pass
         
and comment this line in same file:

Code: [Select]
self._refind_inst = {"grub":self.install.refind_install}         
and finally

Code: [Select]
sudo medit /usr/share/linstaller/linstaller/modules/bootloader/inst/glade/_init_.py
Find and comment out these lines (53,54 and 55)

Code: [Select]
                          #Pass 5: Install Refind
        self.parent.progress_set_text(_("Installing REFIND..."))
self.parent.moduleclass._refind_inst[bootloader]()
self.parent.progress_set_percentage(5)

And finally I cannot recall where this is even at.. (my bad memory)

Quote
If I recall corectly "custom_kernel_args" is used in VSIDO to force persistent network names!?
If so, it needs to be replaced by either "grub_cmdline_linux" or "grub_cmdline_linux_default" ( or both )!


Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 01, 2017, 08:37:36 PM
Quote
(and some good coffee too)
...
Quote
Programmer is an organism capable of converting coffee into software
:D
Or, as I sometime like to put it:
Quote
No bug can survive a good dosage of caffeine
;D



Quote
Regarding the refind section.. with these changes to add uefi and nvme is it still necessary for me to continue to do this?

Commenting just these should be enough:

1. Currently line No.355, @/usr/share/linstaller/linstaller/modules/bootloader/inst/_init_.py
Code: [Select]
self._refind_inst = {"grub":self.install.refind_install}
2. Currently lines No.53--55, @/usr/share/linstaller/linstaller/modules/bootloader/inst/glade/_init_.py
Code: [Select]
# PASS 5: Install REFIND
self.parent.progress_set_text(_("Installing REFIND..."))
self.parent.moduleclass._refind_inst[bootloader]()
self.parent.progress_set_percentage(5)

Btw, I'll postpone the How-To update for a little bit, since this^ commenting stuff out should really be dealt with properly, including the additions in "network" module.
In other words, I'll put both behind config options, so no code editing will be needed. Then the How-To will follow.  :)

EDIT:

On the side note, in the existing How-To, you said:
Quote
Edit these files to take care of eufi refind that is not a part of VSIDO (yet)
And looking inside VSIDO ISO I don't see any "efi" images, leading me to think that VSIDO doesn't actually support UEFI!? If so, you don't need to comment REFIND related lines, since they're not gonna be called anyway ( they're called only when booted in UEFI mode ). :)

Also, if you'd like, I can put into git and package VSIDO linstaller config files ( "/etc/linstaller/vsido*" into eg. "linstaller-config-vsido_all.deb )??
The benefit here would be that:
- You would not need to worry about manually updating config when needed, like it was with "custom_kernel_args" preseed and will be with the incoming refind/network stuff,
- I can make code, and when it's necessary, config changes and know I've came full circle with that particular change/improvement.

Quote
And finally I cannot recall where this is even at.. (my bad memory)

Quote

    If I recall corectly "custom_kernel_args" is used in VSIDO to force persistent network names!?
    If so, it needs to be replaced by either "grub_cmdline_linux" or "grub_cmdline_linux_default" ( or both )!

@/etc/linstaller/vsido-base  :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 02, 2017, 12:03:09 AM
Thank you Filip... Regarding eUFI I have a separate build environment just for that... so it is easy enough to implement what is needed on each

I appreciate it.. when I get this done I will send you the vsido base files that I have to edit if you want to include them

Cheers!
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 02, 2017, 05:20:59 PM
Thank you Filip... Regarding eUFI I have a separate build environment just for that... so it is easy enough to implement what is needed on each

I appreciate it.. when I get this done I will send you the vsido base files that I have to edit if you want to include them

Cheers!

You're most welcome!  :)

@VSIDO UEFI:
Cool! Found & downloaded...  :)

@config files:
What I need is:
- /etc/linstaller/vsido
- /etc/linstaller/vsido-base
- /etc/network/interfaces

You can just paste them in a post ( easier to copy ) or don't bother if ones in the current How-To are up to date, I'll use them.  ;)

@Changes:
Done! Network (https://gitlab.com/Cofi/trios-installer/commit/a7fedd9ddcc58244a5e3241c44332b666621a9ca) and Bootloader/rEFInd! (https://gitlab.com/Cofi/trios-installer/commit/bc925be45c8710155290c32d3138de04135e11d3)

Btw, don't bother testing them yet, they don't apply without updated configs!

:)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 02, 2017, 09:35:51 PM
Hello Filip.. I have updated the How to with everything we have discussed including these files that I will include here for you

it is looking good.. Thanks mate!

    /etc/linstaller/vsido


Code: [Select]
## MAIN LINSTALLER CONFIGURATION FILE FOR VSIDO

[linstaller:extends]
source = vsido-base

# Do not ask for language, use the system's one instead.
#[module:language]
#ask = False

# Do not ask for timezone, use the system's one instead.
#[module:timezone]
#ask = False

# Disable root
#[module:userhost]
#root = None

   /etc/linstaller/vsido-base

Code: [Select]
## BASE LINSTALLER CONFIGURATION FILE FOR VSIDO -- END USER WILL NOT (HOPEFULLY) NEED THIS

[linstaller]
distribution = VSIDO
modules = uefidetect.inst welcome.front language.front timezone.front userhost.front partdisks.front bootloader.front summary.front partdisks.inst unsquash.inst virtualpartitions.inst language.inst timezone.inst network.inst supportrepo.inst bootloader.inst userhost.inst debian.inst clean.inst fstab.inst finish.inst end.front
special = partdisks.inst unsquash.inst virtualpartitions.inst

[module:language]
ask = True

[module:timezone]
ask = True
timezone = Etc/GMT

[module:partdisks]
swap_noformat = True

[module:unsquash]
image = /lib/live/mount/medium/live/filesystem.squashfs

[module:debian]
remove = /etc/linstaller/trios.packages-remove
autoremove = True

[module:bootloader]
bootloader = grub
custom_kernel_args = grub_cmdline_linux
should_hide_menu = False

[module:supportrepo]
path = file:///lib/live/mount/medium/support
binarydir = ./
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 02, 2017, 09:58:16 PM
Update:

Installing VSIDO UEFI is, umm, mostly fine.
After working around a couple issues it's installed properly using latest installer and config files from the (old) How-To.  :)

Issues @live:

1. net.ifaces=0 is missing from grub/kernel line, resulting in missing network ( in VBox ). Adding it manually solves the issue.
2. For some weird reason, mkfs is refusing to format any drive when called from installer ( compains that "/dev/xyz" doesn't exist, when it obviously does ). Calling it manualy from terminal works.  ???

Issue booting installed system:
1. local-filesystems.service fails trying to mount some UUID's I haven't actually seen exist at all. However, after it spends it's 1min30sec limit system boots normaly.

Now, I'll assume that atleast the mkfs issue stems from maybe SID being a b*tch at the time of ISO build, @Oct 2016. Unless I missed a newer ISO?

Nitpick:
1. You might wanna associate text files with Medit, since Vim is the current default, and it doesn't run when opening a file from SpaceFM ( Vim's .desktop file issue maybe? ).  :)

All in all, it's looking good, but the mkfs kinda rubbed me the wrong way...
It would be great if you have the time to build a fresh UEFI ISO so that we can, hopefully, learn that it was just a temporary Sid quirk.

EDIT:

Quote
Hello Filip.. I have updated the How to with everything we have discussed including these files that I will include here for you

it is looking good.. Thanks mate!


Awesome, thanks! Will be in git soon. :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 02, 2017, 10:05:20 PM
^ Yes.. that particular uEFI ISO is very old and was designed to help one user with nvme

The tool I use to build (refracta) has been updated with uEFI support so it should go easier

I'll build some new ones later this week

I'll fix the VIM issue

Thanks mate..
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 02, 2017, 10:42:37 PM
^ Yes.. that particular uEFI ISO is very old and was designed to help one user with nvme

The tool I use to build (refracta) has been updated with uEFI support so it should go easier

I'll build some new ones later this week

I'll fix the VIM issue

Thanks mate..

No problem, great! :)

@Installer:

Allright, config is pushed and packaged ( in testing brach atm ).
From now on you should be able to simply do a "clone --> build packages --> install" without editing anything.
That is unless I missed something. Will recheck tomorow hopefully, and if all is ok push to master & release.

Changes are:

1. There's now a "vsido-net-interfaces" file that gets copied to "/etc/network/interfaces" -- no need to mess with network module py files anymore.
2. Updated "grub_cmdline_linux" option ( corectly sets "net.ifaces=0" )
3. rEFInd installation disabled -- no need to mess with bootloader module...

And all of that is neatly packaged into "linstaller-config-vsido" .deb, which btw conflicts with "linstaller-config-trios" ( it's a mutual conflict actualy ), so that only one of them can be installed at a time, for the obvious benefits of all parties involved.

For details, take a look here. (https://gitlab.com/Cofi/trios-installer/compare/bc925be4...testing)  :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 03, 2017, 01:39:26 AM
Excellent work Filip!

I have uploaded the uEFI ISO's that can be downloaded here (http://www.nixnut.com/vsido/test/uefi/)

Anyone with uEFI and/or nvme hardware can use these and both installers should work
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 04, 2017, 08:56:27 PM
Hmm, "mkfs" is still bitching over here.  :-[ Though I'm starting to think it might be related to VBox or current kernel, or either.
The weirdest part is that it works normaly on TRIOS/Jessie and when called manualy from terminal, yet the very same call from installer makes it go blind ( see screens ).  ???

I'd be glad if someone with actual hardware would test and drop a note on how it went, since there's really no (obvious) reason in the installer itself for something like this to ever happen.

Besides that, everything else looks good, including the config package, UEFI/Grub, network conf etc... :)
Though I'll hold back the push to stable for a while, until we can find the cause for the "mkfs" lunacy, or at least rule it out on the real hardware!
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 04, 2017, 09:03:41 PM
I have the same issues with V-Box and it not seeing the installation but it most likely has to do with grub-efi is not being installed correctly to the new installation..  I am pretty sure I can chroot into the new install from the LiveCD and manually install grub-efi and and update-grub everything would be fine

I am like you, I have no real efi hardware and will wait until someone with it reports back
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 04, 2017, 09:25:30 PM
Quote
it not seeing the installation but it most likely has to do with grub-efi is not being installed correctly
I don't have that issue -- Box weirdness galore.  ;D
Though it would be nice if you could post the installation log from it ( boot live -- mount root -- cat /var/log/installation.log ), it should tell us more about what happened.  :)

Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 04, 2017, 09:46:15 PM
working to get that now.. there is no network now on the livecd with the changes made.. getting the enp0s3 instead of eth0 and failing to restart the network

I will have the file up shortly
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 04, 2017, 10:02:01 PM
Here is a pastebin post of the installation log (https://hastebin.com/irihupidap.sql)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 04, 2017, 10:03:18 PM
I also attached it here
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 04, 2017, 10:28:30 PM
@Network:

I can't be of much help here, since besides the usuall stuff, it's exactly the network nonsense that keeps me away from systemd. Random connection drops, changing cable from one LAN port to another breaks the network on both, the famouse "doesn't brings up the net on boot", device name changing....

Anyway, quick workaround for live is to just run "dhclient".  :)
And if I may suggest you to take a look at "connman"... If doesn't have issues with systemd, it might be perfect for VSIDO, given that it has tiny footprint* and a solid Gtk GUI ( not pacakged yet, unfortunately ), and the best off all is that nothing else is needed ( nm, wicd etc... ).

connman-gtk: https://github.com/jgke/connman-gtk (https://github.com/jgke/connman-gtk)
* Along the lines of 5-8MB of RAM for both the daemon and the GUI.

@Installer/GRUB:

Looks like you didn't setup an EFI partition ( fat16, about 30-100MB, mountpoint=/boot/efi ).  ;) :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 04, 2017, 11:15:35 PM
^ thanks for that.. is the creation of the fat16 partition is all that is needed for the installer?

Do I tell grub to install there?  Forgive my ignorance on this.. never had a uEFI hardware and very limited experiences...
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 04, 2017, 11:18:27 PM
I saw the answer to my question in the installation at the partition setup .. it does the boot/efi for us.. nice!
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 04, 2017, 11:30:49 PM
Successfully installed and now seeing the issues you reported clearly... I created the partitions in Gparted before the installation so I did not see the mkfs issue .. I will test that on net test install

1.  net.ifnames=0 is easy to correct.. It will be on the next ISO test.. Since the grub config files are different I need to edit them to be the same

2. I will look at connman and I have a short term fix for the local-filesystems.service issue simply shortening 90 seconds down to 5
is a setting from fstab that is not being passed in this ISO.. will research and figure it out

3. Will fix the Medit issue

Thanks for all the help and feedback!
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: jedi on April 05, 2017, 12:31:10 AM
Successfully installed and now seeing the issues you reported clearly... I created the partitions in Gparted before the installation so I did not see the mkfs issue .. I will test that on net test install

Which ISO? the 02Apr one?  I did see the mkfs error.  Reran and did gparted first solved that.  Tried the install with /boot/efi mounted and not mounted.  Same result both times.  Did not work.  Install worked just didn't do the grub part...

Once I've rebooted into my VSIDO_GoTo and updated grub, then the new install boots from the VSIDO_GoTo grub menu.  Issues with the install.  I get the fstab problem of old where the sys hangs for a minute and a half which is an easy fix on this end. (I can see a new user getting a little frustrated about this)  Though this has probably been resolved here, still getting two speakers on the menu.py volume icon.  After the minute and a half hang, I had to Ctrl-D to continue.  It said that the login password was wrong?  ???

Just updated grub from this new install and a reboot will tell the tale...
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 05, 2017, 12:40:52 AM
Thanks for testing and the feedback Jedi

Yes the April 2nd is the current testing version we are all using

When I Ctrl-D after the 90 seconds I just let it boot and then it gets to a login screen.. is that where you are seeing the PW as wrong, at the normal login screen?

All the issues you saw I am aware of and am now working on resolving them

For me... I am perplexed.. I can successfully install and on the first reboot from the installation V-Box sees grub and efi and all is good... but once I shut the session down and reboot, V-Box no longer sees the efi partition.. Does the efi partition need to be anything special other than fat16? Does it need to be sda or sda1? Does it need to be flagged as a boot device from gparted? I can go into the v-box settings of efi and switch around the boot order but the only thing that seems to consistently boot efi is the ISO and NOT the installed VSIDO with efi
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: jedi on April 05, 2017, 12:47:46 AM
Does the efi partition need to be anything special other than fat16? Does it need to be sda or sda1? Does it need to be flagged as a boot device from gparted? I can go into the v-box settings of efi and switch around the boot order but the only thing that seems to consistently boot efi is the ISO and NOT the installed VSIDO with efi

Just wanted to be sure on the correct ISO to be testing.  It is the one I'm using as well.  A Ctrl-D after the 90 sec's does indeed get me to the login screen...

Yes the /boot/efi partition should be fat32 imo, however if fat16 works thats cool too.  It should also be noted that that partition will need the boot flags 'esp' and 'boot' selected.  Not sure if that'll fix the V-box issues though...

I updated grub after booting into the new install the second time and it was successful.  However on reboot there is no entry for it in the UEFI boot list.  My regular GoTo grub menu got me back here to the new install.  Will keep puzzling for a little while.  Been a while since I had any fun...
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 05, 2017, 12:56:44 AM
OK... I rebooted to a new install and set the partition as a boot drive and ran update-grub and now I am getting a reboot back to the new install

Thanks for that clarity.. Now I need to correct the net.ifnames=0 on the grub line so that there is network on the LiveCD and to add these parameters to the fstab entry to stop the 90 second delay

Code: [Select]
noauto,x-systemd.automount,x-systemd.device-timeout=2 0 2
I will also eventually correct the vim/medit issue

Thanks for testing and helping out, it is greatly appreciated
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 05, 2017, 01:14:43 AM
For those keeping score, these are the changes I had to make to the fstab to eliminate the 90 second timeout crap

My current /etc/fstab

Code: [Select]
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc   /proc   proc   defaults   0   0
# /dev/sda2
UUID=63881c3d-95b7-49b8-986c-f767c13701ae   /   ext4   noauto,x-systemd.automount,x-systemd.device-timeout=2 0 2
# /dev/sda1
UUID=B13B-925B   /boot/efi   vfat   auto,users,rw,quiet,umask=000,shortname=lower,x-systemd.automount,x-systemd.device-timeout=2  0   0
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: jedi on April 05, 2017, 01:39:20 AM
you can probably axe the 'proc' line as well.  I simply deleted the swapfile line in fstab and it solved the 90 sec issue...
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 05, 2017, 02:00:24 AM
I do not have a swap file setting.. the error is coming specifically from the efi boot line

Code: [Select]
vfat   auto,users,rw,quiet,umask=000,shortname=lower
Edit  Adding this to the line above is all that is needed to stop the 90 second timeout (on my end)

Code: [Select]
x-systemd.automount,x-systemd.device-timeout=2
So the line should be:

Code: [Select]
auto,users,rw,quiet,umask=000,shortname=lower,x-systemd.automount,x-systemd.device-timeout=2  0   0
The exact same setup does not have this error on normal VSIDO without uEFI..

And there is nothing I can do to change it during the installation.. it is something that needs to be added or edited after the install
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 05, 2017, 03:19:13 AM
I have finished building and testing a new ISO for testing uEFI hardware and it has been uploaded to the test download page (http://www.nixnut.com/vsido/test/uefi/)

As stated above the 90 second delay can be solved after the install with an edit to fstab

I have corrected the issue with net.ifnames=0 on the grub line so now the LiveCD session does have a correct network setup and internet access

Anyone testing this be sure to remember to create the 30-100 MiB fat16 or fat32 partition and the installer will set it up for you. I am assuming that since Jedi is confirming than nvme is working since he got it to install .. (Did you use the new installer Jedi?  The Trios/VSIDO new one?) ... You must also run an update-grub on your new install as soon as you boot to it (after the vsido-welcome and before a reboot)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 05, 2017, 03:40:55 PM
@Jedi:

Thanks for testing mate! :)

Please do post the installation log for me to take a look at. It's at "/var/log/installation.log".

Quote
you can probably axe the 'proc' line as well.
I think that /proc is actually a must for the "update-grub" to find partitions/mount info.
At least I was never able to restore/reinstall GRUB from a live system without binding it to the mounted root first ( eg mount --bind /proc /path/to/root/partition/proc ).



@VastOne:
Quote
I am perplexed.. I can successfully install and on the first reboot from the installation V-Box sees grub and efi and all is good...
Likewise/confirmed.  ???

Quote
Does the efi partition need to be anything special other than fat16? Does it need to be sda or sda1? Does it need to be flagged as a boot device from gparted?

- AFAIK, it should be (any) FAT, most likely because every BIOS will support it.
- Should be a first one ( sdX1, nvmeXnXp1 etc ), though not a must, however the same "support issue" as above still applies.
- Yes, it needs "esp" flag to be set, which is what Parted/Gparted actually does when you set a "boot" flag.

Installer-wise, it sets the "boot" flag using parted itself, so that's unlikely to be the cause ( see here (https://gitlab.com/Cofi/trios-installer/blob/master/linstaller/core/libmodules/partdisks/library.py#L509), @line 509 )

@fstab
Quote
And there is nothing I can do to change it during the installation.. it is something that needs to be added or edited after the install

That won't be too hard to implement as preseed ( including the entire "options" part of "fstab" for every file system available ).

Quote
I have finished building and testing a new ISO for testing uEFI hardware and it has been uploaded to the test download page

Looking good!  :)
Btw, should another build be required while we're debuging these issues, may I ask you to build with VBox Guest Additions ( I'm sorely missing the shared clipboard when fixing/testing installer stuff on a live system )? :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 05, 2017, 04:56:40 PM
I have a good understanding of the preseed methodology and what it can do but have never used one in the installer to know how to make the changes.. I could use a How To on it if there is one. I did a search and have found very little info on it

Regarding the Guest Additions, can't you just install them on your end with the ISO? they add a huge amount of space to the ISO if I include them
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 05, 2017, 08:07:57 PM
I have a good understanding of the preseed methodology and what it can do but have never used one in the installer to know how to make the changes.. I could use a How To on it if there is one. I did a search and have found very little info on it

Regarding the Guest Additions, can't you just install them on your end with the ISO? they had a huge amount of space to the ISO if I include them

Well, here's a somewhat sparse wiki page @Semplice (http://semplice-linux.org/doku/semplice:users:linstaller:preseeds), however, besides the short documentation of the existing preseeds, there's also the issue of missing ones, which occasionaly popup as needed ( like it's the case with "fstab", or was for rEFInd etc. ).
The only way around second one is to actually code them in, which is not hard per se, but it does requires basic knowledge of Python and installer internals.
I'm certanly willing to write a HowTo if you're up for it. :)

As an example, here you can see what it took to add the "copy specified file to /etc/network/interfaces" functionality I've added for VSIDO ("custom_net_ifaces" preseed):
https://gitlab.com/Cofi/trios-installer/commit/a7fedd9ddcc58244a5e3241c44332b666621a9ca

On the doc side, I will eventualy get to documenting and explaining existing preseeds, however that is not likely to happen soon.

@VBox GA:
Of course I can, however I need them in live mode, since there I'm testing and fixing the installer on-the-fly...
Anyway, it's not a must have, I've basically asked for this one time exception, mostly because it would make the ^work much faster and easier to do.  :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: jedi on April 06, 2017, 02:31:35 AM
@Jedi:

Thanks for testing mate! :)

Please do post the installation log for me to take a look at. It's at "/var/log/installation.log".

Attached is the log file Filip.

To be clear; Using the 02Apr ISO was very "painfully" installed.  The attached log file is from the successful install tonight of the 04Apr ISO.  This time the install went A LOT smoother.  It DID create the new UEFI entry in the NVRAM/BIOS. (vsido_x64 is the name of the uefi entry)  This worked at the first shot tonight on the new install.  Last time not so much.  In short, the install went perfectly (exceptions already mentioned by VastOne, and totally expected) including installing grub-efi-amd64 or grub-efi correctly.  Yes I did setup drives with gparted BEFORE running the installer to avoid the mkfs error.  After reboot, the expected 90 sec delay occurred.  Again, easily fixed.  I noticed a difference this time with the installer when choosing not to specify a swap partition.  On reboot, the 'swapfile' line was NOT in fstab as it was last time on the 02Apr ISO.

Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: jedi on April 06, 2017, 02:41:04 AM
Oh yeah, IT BOOTS INSTANTLY!!!!   8)

So while VSIDO is my default goto OS,  ??? I'm now switching to the "Testing" version of VSIDO! bwahahahahahaha...  :D
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 06, 2017, 02:50:39 AM
@Jedi:

Thanks for testing mate! :)

Please do post the installation log for me to take a look at. It's at "/var/log/installation.log".

Attached is the log file Filip.

To be clear; Using the 02Apr ISO was very "painfully" installed.  The attached log file is from the successful install tonight of the 04Apr ISO.  This time the install went A LOT smoother.  It DID create the new UEFI entry in the NVRAM/BIOS. (vsido_x64 is the name of the uefi entry)  This worked at the first shot tonight on the new install.  Last time not so much.  In short, the install went perfectly (exceptions already mentioned by VastOne, and totally expected) including installing grub-efi-amd64 or grub-efi correctly.  Yes I did setup drives with gparted BEFORE running the installer to avoid the mkfs error.  After reboot, the expected 90 sec delay occurred.  Again, easily fixed.  I noticed a difference this time with the installer when choosing not to specify a swap partition.  On reboot, the 'swapfile' line was NOT in fstab as it was last time on the 02Apr ISO.

The only differences between the April 02 and the April 04 was the changes to make ifnames=0 added so that there was internet access on the LiveCD.. other than that everything was identical.. I know on the 04 I took more time with the partition setup and allowed the Installer to create and partition the /boot/efi drive that I had already created.  As Filip said it did apply the boot flag and all I had to do was an update-grub once I booted into it and all was well

The good thing is we are light years ahead of where we have ever been with uEFI and nvme technologies

Thanks for the assist Jedi it is appreciated
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 06, 2017, 08:16:29 PM
@Jedi:

Thanks!
Log looks perfectly fine. No errors, and most importantly GRUB is corectly installed and updated ( btw, going by the log, there shouldn't be a need to update it manualy on first boot! ):
Code: [Select]
...
Installing for x86_64-efi platform.
Installation finished. No error reported.
...
Found Debian V-SID-O jedi (V-Ger) on /dev/nvme0n1p1
Found Manjaro Linux (17.0) on /dev/nvme0n1p5
Adding boot menu entry for EFI firmware configuration
done

I forgot it last time:
Quote
I simply deleted the swapfile line in fstab and it solved the 90 sec issue...
Installer doesn't support the swapfile at all, so unless we're looking at another "mkfs"-like wierdness, it couldn't have came from installer itself. :)



I've been quite busy in the last couple of days, so the actual fstab/mkfs work/investigation will have to wait for the weekend ( I'll also push a "connman-gtk" with some fixes and packaging to GitLab, so you can take it for a spin if you'd like ).
In the mean time, unrelated, but you might be interested to know that unfortunately Ignorant Guru is no longer developing (https://github.com/IgnorantGuru/spacefm/issues/687) SpaceFM, however there's now a fork and a new version at https://github.com/Teklad/spacefm-ng :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: jedi on April 06, 2017, 08:55:29 PM
@Jedi:

Thanks!
Log looks perfectly fine. No errors, and most importantly GRUB is corectly installed and updated ( btw, going by the log, there shouldn't be a need to update it manualy on first boot! ):

Installer doesn't support the swapfile at all, so unless we're looking at another "mkfs"-like wierdness, it couldn't have came from installer itself. :)


@filip, yes it went perfectly.  As you saw in the log, there was indeed no need of any grub finessing   With the 02Apr ISO it warned me about not choosing a swap file but that it was fine to proceed.  On the 04Apr ISO, this did not happen, and the line in fstab did not show up either. (mkfs? beats me) All in all, a pretty impressive result and jump forward for VSIDO...

My initial testing with the 02Apr ISO should probably be totally disregarded.  I did most of it in the garage.  Never a conducive work environment.  Turns out it's a lonely winter up here!  I really need some Spring...
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 08, 2017, 09:02:51 PM
@Jedi:

Thanks!
Log looks perfectly fine. No errors, and most importantly GRUB is corectly installed and updated ( btw, going by the log, there shouldn't be a need to update it manualy on first boot! ):

Installer doesn't support the swapfile at all, so unless we're looking at another "mkfs"-like wierdness, it couldn't have came from installer itself. :)


@filip, yes it went perfectly.  As you saw in the log, there was indeed no need of any grub finessing   With the 02Apr ISO it warned me about not choosing a swap file but that it was fine to proceed.  On the 04Apr ISO, this did not happen, and the line in fstab did not show up either. (mkfs? beats me) All in all, a pretty impressive result and jump forward for VSIDO...

My initial testing with the 02Apr ISO should probably be totally disregarded.  I did most of it in the garage.  Never a conducive work environment.  Turns out it's a lonely winter up here!  I really need some Spring...

Great!  :)

@garage:
While I certanly understand where you're coming from, I do on the other hand have to differ about it not being a conducive work env. But I guess it depends on the actual garage ( I see mine as a den of sorts )...  :D ;D



fstab preseed for EFI partition is now exposed and preset in "vsido-base" to "x-systemd.automount,x-systemd.device-timeout=2".
Details: https://gitlab.com/Cofi/trios-installer/compare/60e481752253d822c5b2baf67b40c54ae9d20eeb...a9aa560c1e14d08025e21110f496b1dbc04ff588

For now, preseed is applied only if EFI partition is formated with FAT16 or FAT32 (vfat actually)!
Can be easily extended for other FS's if the need be. :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 08, 2017, 10:29:10 PM
HAHA  ... the garage at Jedi's is a definite place for the mind to relax and chill.. to the point of grand illusions   8)  8)  8)  8)  ???

A perfect install .. no delays, a perfect boot

And STILL less than three minutes even with new procedures during the installation


  (http://www.zimagez.com/miniature/screenshot2017-04-0817-18-45.php)
 (http://www.zimagez.com/zimage/screenshot2017-04-0817-18-45.php)

I also attached is the installation log of the install if you wanted to check it out
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 08, 2017, 10:41:32 PM
HAHA  ... the garage at Jedi's is a definite place for the mind to relax and chill.. to the point of grand illusions   8)  8)  8)  8)  ???

Well, that explains it then...  :D :D ;D ;D

A perfect install .. no delays, a perfect boot

And STILL less than three minutes even with new procedures during the installation


  (http://www.zimagez.com/miniature/screenshot2017-04-0817-18-45.php)
 (http://www.zimagez.com/zimage/screenshot2017-04-0817-18-45.php)

I also attached is the installation log of the install if you wanted to check it out

Awesome!  :)

Though you might wanna recreate the partition table on that hdd ( via Gparted or installer ), to avoid potential issues in future testing.  ;)
Code: [Select]
GUID Partition Table Header signature is wrong: be5608740128e852 != 5452415020494645
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: jedi on April 08, 2017, 10:51:47 PM
 ???  Yes my 'garage' is definitely Kush.  My den, man-cave, secret hideout, etc.  It is especially Kush this weekend!  Totally unbelievable!!  ???
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 08, 2017, 11:32:09 PM
Update @mkfs:

I'm perplexed and out of ideas really.   :-[

Been sifting trough the installer for most of the evening --> found nothing obviously wrong. 
Heck, "partprobe" is being executed (https://gitlab.com/Cofi/trios-installer/blob/master/linstaller/core/libmodules/partdisks/library.py#L539) before every call to "mkfs", for the very reason of avoiding the issue we're seeing, which btw shouldn't be even needed, since we're just formating existing partitions, no changes were made to them or the partition table, warranting a need for "partprobe"...
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 09, 2017, 12:06:44 AM
^ You say you do not see this on the Trios side right?  What distro level are they?

My thinking is this could be a SID issue ..
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 09, 2017, 07:24:35 PM
^ You say you do not see this on the Trios side right?  What distro level are they?

My thinking is this could be a SID issue ..

Jessie.

@SID:

Possibly...
I have a feeling it's one of those dumbest ass things that on the "outside" appear perfectly normal and fine, yet silently casue issues and a major pain to detect.  >:(
And when you finally find it, you go like "I don't wanna live on this planet anymore"...  ;D

Anyhow, as they say, it's just a matter of time.... ;)
Will post progress updates as they come.  :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 09, 2017, 07:37:36 PM
Be aware that on the latest SID updates (and on VSIDO installs with the new ISO) there is a delay of about 20 seconds and then a message

Code: [Select]
gave up waiting on suspend/resume device
and then it boots normally

Not sure where the message even comes from as it is immediate .. possibly initramfs update but I am not sure

It is not causing any issues other than a blank 20 second delay.. strange one I have never seen before

Does NOT happen boot of ISO to LiveCD, only after installed..

It could also be an SSD issue since that is what I am running on
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 09, 2017, 07:57:32 PM
Be aware that on the latest SID updates (and on VSIDO installs with the new ISO) there is a delay of about 20 seconds and then a message

Code: [Select]
gave up waiting on suspend/resume device
and then it boots normally

Not sure where the message even comes from as it is immediate .. possibly initramfs update but I am not sure

It is not causing any issues other than a blank 20 second delay.. strange one I have never seen before

Does NOT happen boot of ISO to LiveCD, only after installed..

It could also be an SSD issue since that is what I am running on

Try this:

1. Reboot
2. Remove "resume=/dev/sdxy" from kernel cmdline ( press "e" when grub shows, then find it on the "linux" line and remove ) & hit F10 to boot.

If the error goes away, and you haven't formated/deleted/moved the swap partition, then it's likely some systemd bustage ( though changelog doesn't indicate anything related ).

When you hibernate your machine, RAM content is dumped onto the swap partition for a persistent storage. Then, when you turn back on, "resume=/dev/sdxy" line is used to point the kernel to that partition as the resume device containing the previous state.

So, if you're not using hibernation, it's safe to remove the same line from "GRUB_CMDLINE_LINUX_DEFAULT" in "/etc/default/grub" file, and then run "update-grub", however do keep in mind that if you ever hibernate the machine, it will NOT resume into previous state, but boot normaly instead! :)
Otherwise if you moved your swap, correct the "/dev/sdxy" in the same file & update-grub.
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 10, 2017, 12:01:34 AM
I do not have that on any line, I do not use swap and never ever have used hibernation even when I do use a laptop

This has also started to happen on this my build machine that is also completely up to SID levels..

This is nothing new in SID, just a hiccup that is only a concern if someone boots VSIDO on a new install and does not wait the 20 seconds on the boot and gets frustrated..

Cheers
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: VastOne on April 11, 2017, 02:03:36 AM
@filip

I saw your cofi89 questions on the VSIDO IRC.. I do not always cover that anymore.. Simply, I have been selfless forever and it has gotten me nowhere

To answer your question I did solve the network issue on V-Box with a tweak to a refracta file used in building the ISO

Thanks
 
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 12, 2017, 07:46:31 PM
I do not have that on any line, I do not use swap and never ever have used hibernation even when I do use a laptop

This has also started to happen on this my build machine that is also completely up to SID levels..

This is nothing new in SID, just a hiccup that is only a concern if someone boots VSIDO on a new install and does not wait the 20 seconds on the boot and gets frustrated..

Cheers

Yeah, it's some update ( possibly systemd ) related then. :)


... I do not always cover that anymore.. Simply, I have been selfless forever and it has gotten me nowhere

No problem!
I know that feeling...  ::)

To answer your question I did solve the network issue on V-Box with a tweak to a refracta file used in building the ISO

Great, thanks!  :)
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: hakerdefo on April 14, 2017, 09:03:35 PM
@filip Great work on the installer  8)
Keep it up  :)

Cheers!!!
Title: Re: TRIOS Installer -- shiny new v7.0.7 ( not late at all )...
Post by: filip on April 15, 2017, 08:11:11 PM
@filip Great work on the installer  8)
Keep it up  :)

Cheers!!!

Thank you!  :)



@VastOne:

The "resume device" hang propagated to Stretch as well. And for once it actually has nothing to do with systemd.
You were right, issue was introduced in "initramfs-tools", v128 in order to fix the bug where some NVMe drives were slow to enumerate partitions causing the system to fail to resume from hibernation...

See changelog (https://tracker.debian.org/media/packages/i/initramfs-tools/changelog-0.128) and a bug report. (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854791)

The weird part is the wait time they've set ( ~20sec ). I mean what for, seriously!? Even the guy who reported the bug said that adding a 1sec delay fixed the issue for him...  ::)

Anyway, until they sort it out, the quick fix is to add the "resume=/dev/sdXY" to the "GRUB_CMDLINE_LINUX_DEFAULT" in "/etc/default/grub" file, where "/dev/sdXY" is your swap partition ( worked for me atleast @Stretch ).  :)
You might even get away with any partition ( not just swap ), as long as you don't have any data on it ( untested!!! ).



EDIT:

I've also looked at the actuall shell scripts used, however I'm having a bit of a hard time reading them ( I've never really understood why Debianers always write shell scripts in such obfuscated and "hard to read" way  ::) ).
I'll let you know If I get anywhere with that...