New ISO build to try.

DeepDayze · 2022-03-11 20:03:55

I took a look at the latest Lilidog and it's pretty sweet and dig the dark themes. This is something I'll consider using as my daily driver and it should really fly on my big rig (which I am rebuilding soon as got new Ryzen 7 5800x CPU and a 1TB SSD.)

Last edited by DeepDayze (2022-03-11 20:05:13)

sleekmason · 2022-03-11 22:56:31

@unklar That Conky is incredible! Sorry you lost your Siduction install:( Never cool when you are in the middle of stuff and have it all fall apart.

@DeepDayze Glad to hear you are enjoying Lilidog, I hope it meets your needs!

I have a decent list of small visual changes for the next Debian point release arriving in a few weeks. These are already committed to github, and are more about getting things right with what is already present, rather than adding anything new to the mix. Optimization time!

It Only takes 20 minutes or so for my computer to build Lilidog, but a nerve wrangling 5 hours or so to upload each version to Sourceforge. Occasionally these get dropped in the middle. Lol. I'll have all builds up within 48 hours of the new release if everything goes smooth.

Sid will be updated whenever they update the installer to use the latest nvidia-modprobe 510.47, or if someone knows how to add /experimental to the INSTALLER itself? I've got the distro covered by pinning and/or adding from experimental, but even the daily version of the installer is still using the earlier version 4.70 of nvidia-modprobe As soon as I can add the installer back into the mix, sid will update as well.

I'll try again in a day or so and it will probably be matched up again. I've decided to keep a sid version for easy transition to the next stable. We'll see how that goes:)

DeepDayze · 2022-03-12 03:31:34

One nitpick: any way to add additional conky's to the conky list?

I may even try out the Sid version too once it's ready.

Last edited by DeepDayze (2022-03-12 03:35:25)

unklar · 2022-03-12 08:07:59

sleekmason wrote:

Sid will be updated whenever they update the installer to use the latest nvidia-modprobe 510.47, or if someone knows how to add /experimental to the INSTALLER itself?

@sleekmason,
I don't think this is a good idea.

Do you really want the inexperienced users to destroy their system because you set the threshold lower?
If you need experimental, you should already know what/how to do it.

DeepDayze wrote:

One nitpick: any way to add additional conky's to the conky list?

How about putting your configuration files in ~/.config/conky ?

sleekmason · 2022-03-12 12:22:25

DeepDayze wrote:

One nitpick: any way to add additional conky's to the conky list?
I may even try out the Sid version too once it's ready.

For conky, The script to control which conkys' can be activated from the menu and keybind is in ~/.config/conky/scripts/conky-chooser Editing this script will allow you to add any number of additional conkys to the yad dialog list, or you can simply replace one of the ones already there.

Any and all conky.confs should go into ~/.config/conky to keep things simple.

You can also edit ~/.config/openbox/autostart to add conkys to autostart, and/or you can also add conky entries to any of the Theme Changer scripts located in ~/.config/Lilidog-themes. (Paw Icon in panel).
here, you can tweak the existing themes or create your own however you want! More info: https://sourceforge.net/p/lilidog/discu … 3fec6a23b/

Everything conky for Lilidog is located in ~/.config/conky. Nothing more required but conky, yad, and a menu entry pointing to the conky-chooser script.

sleekmason · 2022-03-12 12:39:18

unklar wrote:

sleekmason wrote:
Sid will be updated whenever they update the installer to use the latest nvidia-modprobe 510.47, or if someone knows how to add /experimental to the INSTALLER itself?
@sleekmason,
I don't think this is a good idea.
Do you really want the inexperienced users to destroy their system because you set the threshold lower?
If you need experimental, you should already know what/how to do it.

Excellent point. I'll wait. Sid catches me by surprise sometimes. Testing in a VM doesn't cut it. I have to do a full install to a separate partition every time not to miss small items.

Before, I just kept the sid copy private, but it seems such a waste to do so. I'll think more on this as well.

Experimental within the distro build itself isn't the issue, just adjusting the installer. The obvious way is to get rid of non-free and contrib, adding them back in on install, but I haven't had problems in this area until recently. Always something new in sid. Ha!

Thank you much for your input! I need more of this:)

DeepDayze · 2022-03-12 15:36:10

Another thing I encountered is that the splash screen does not start in the installed Lilidog vs the live install. In addition that nice grub background does not show as just get the black background in grub2 screen. Seems there may be customizations that somehow do not make it into the installation. Have you encountered this in your tests?

EDIT: Thanks for the info in how to add conkys to the simple conky manager and where to place the conky configs/scripts.

Last edited by DeepDayze (2022-03-12 15:37:29)

DeepDayze · 2022-03-12 15:40:50

sleekmason wrote:

unklar wrote:
sleekmason wrote:
Sid will be updated whenever they update the installer to use the latest nvidia-modprobe 510.47, or if someone knows how to add /experimental to the INSTALLER itself?
@sleekmason,
I don't think this is a good idea.
Do you really want the inexperienced users to destroy their system because you set the threshold lower?
If you need experimental, you should already know what/how to do it.
Excellent point. I'll wait. Sid catches me by surprise sometimes. Testing in a VM doesn't cut it. I have to do a full install to a separate partition every time not to miss small items.
Before, I just kept the sid copy private, but it seems such a waste to do so. I'll think more on this as well.
Experimental within the distro build itself isn't the issue, just adjusting the installer. The obvious way is to get rid of non-free and contrib, adding them back in on install, but I haven't had problems in this area until recently. Always something new in sid. Ha!
Thank you much for your input! I need more of this:)

Yep, same here as I rather want to test distros on bare metal rather than in a VM. However VMs are maybe a quick and dirty way to try out a distro but to get the actual experience it's better to install to bare metal. That's why I have plenty of scratch SSDs/HDDs lying around to use and swapping them when needed. I use a laptop for this testing as it's easy to swap a drive in the machine I have, rather than mucking around in my big rig to connect/disconnect drives.

DeepDayze · 2022-03-12 15:42:51

Another thing (sorry for all the spam lol), why not maybe write a script similar to the bl-welcome that will let users quickly configure things, if that's not too much effort.

sleekmason · 2022-03-12 17:15:11

Interesting thought, but probably not:)
I like having the user options prevalent in the menus and panel. Install options, theme options, and system options should be pretty easy to get to if possible.

I can always use new ideas for system setup post install, and/or other install scripts that give groovy options though. I keep introducing new ones here and there as I think of them or discover them.

sleekmason · 2022-03-12 18:41:28

@DeepDayze, was there a configuration option in particular you would like to see? It may already exist as well. . .

jeffreyC · 2022-03-12 23:38:07

sleekmason wrote:

Sid will be updated whenever they update the installer to use the latest nvidia-modprobe 510.47, or if someone knows how to add /experimental to the INSTALLER itself? I've got the distro covered by pinning and/or adding from experimental, but even the daily version of the installer is still using the earlier version 4.70 of nvidia-modprobe As soon as I can add the installer back into the mix, sid will update as well.

Could you backport the nvidia-modprobe package and add it to your ISO? That would be safer than including Experimental by default.

DeepDayze · 2022-03-12 23:49:56

jeffreyC wrote:

sleekmason wrote:
Sid will be updated whenever they update the installer to use the latest nvidia-modprobe 510.47, or if someone knows how to add /experimental to the INSTALLER itself? I've got the distro covered by pinning and/or adding from experimental, but even the daily version of the installer is still using the earlier version 4.70 of nvidia-modprobe As soon as I can add the installer back into the mix, sid will update as well.
Could you backport the nvidia-modprobe package and add it to your ISO? That would be safer than including Experimental by default.

Think you can backport from Experimental to Sid...never tried that.

sleekmason · 2022-03-13 01:31:35

jeffreyC wrote:

Could you backport the nvidia-modprobe package and add it to your ISO? That would be safer than including Experimental by default.

Howdy, The problem I ran into stemmed from the Debian installer portion of the build process (not the whole ISO) in Sid.

The installer portion of the build process grabs a complete set of packages necessary for all installation purposes by the new future user. This happens every single build so that only the newest packages are added to the installer. Sometimes things don't quite mesh:)

Most of the time these are worked out fairly quickly. I think my longest wait so far is just a couple of weeks. The simple solution for working with Sid is not to add non-free and contrib to the build process because it drags in Nvidia and maybe some other stuff.

Within the given parameters for the installer, I can control whether non-free and contrib are added, but I don't know of a way to individually pin, or add packages to the installer. (not the Lilidog build environment.)

The installer is a set of separate packages from Lilidog itself, providing all? the possible package combinations we find when we go to install.

No worries though! the pace at which SID moves means that today or tomorrow, surely by next week? things will fall back into place for another good bit of time.

unklar · 2022-03-13 13:46:35

DeepDayze wrote:

Another thing I encountered is that the splash screen does not start in the installed Lilidog vs the live install.

I think that the splash screen of the live ISO has simply taken care of itself in the installed Lilidog.

In addition that nice grub background does not show as just get the black background in grub2 screen. Seems there may be customizations that somehow do not make it into the installation. Have you encountered this in your tests?

I've gotten into the habit of installing the grub from new installs into the / partition because I don't want to change my main boot loader. Then I make in the 40_custom of the main bootloader the entry for the grub of the new installation. Yes, and I can not agree with you on that either. I see here the grub with Lilidog as background.

sleekmason · 2022-03-13 14:24:39

unklar wrote:

DeepDayze wrote:
Another thing I encountered is that the splash screen does not start in the installed Lilidog vs the live install.
I think that the splash screen of the live ISO has simply taken care of itself in the installed Lilidog.

In addition that nice grub background does not show as just get the black background in grub2 screen. Seems there may be customizations that somehow do not make it into the installation. Have you encountered this in your tests?
I've gotten into the habit of installing the grub from new installs into the / partition because I don't want to change my main boot loader. Then I make in the 40_custom of the main bootloader the entry for the grub of the new installation. Yes, and I can not agree with you on that either. I see here the grub with Lilidog as background.

@DeepDayze Sorry I missed these questions!

The splash screen will need to be activated in the installed system by adding 'splash' to the command line in /etc/default/grub https://sourceforge.net/p/lilidog/discu … 75da784fa/
I am wary about messing with the default grub configuration until after installation until I learn a few more things about how it all comes together.

As far as the Grub background, there shouldn't be any issues I am aware of . . .
Which version did you install? The image is a 1920x1080.png and should work without issue.

I would ask if you are able to change the grub background using the grub background changer in the menu?

@unklar, I agree! I've thought about having the splash for just the live session. After install, it just annoys me to no end.

*EDIT Has anybody else been missing their grub screen background after install? It should be a picture of Lilidog in an all black background. The only possibility I can see at the moment is some sort of display issues with the image size?

Last edited by sleekmason (2022-03-13 14:34:25)

DeepDayze · 2022-03-13 14:43:25

sleekmason wrote:

unklar wrote:
DeepDayze wrote:
Another thing I encountered is that the splash screen does not start in the installed Lilidog vs the live install.
I think that the splash screen of the live ISO has simply taken care of itself in the installed Lilidog.

In addition that nice grub background does not show as just get the black background in grub2 screen. Seems there may be customizations that somehow do not make it into the installation. Have you encountered this in your tests?
I've gotten into the habit of installing the grub from new installs into the / partition because I don't want to change my main boot loader. Then I make in the 40_custom of the main bootloader the entry for the grub of the new installation. Yes, and I can not agree with you on that either. I see here the grub with Lilidog as background.
@DeepDayze Sorry I missed these questions!
The splash screen will need to be activated in the installed system by adding 'splash' to the command line in /etc/default/grub https://sourceforge.net/p/lilidog/discu … 75da784fa/
I am wary about messing with the default grub configuration until after installation until I learn a few more things about how it all comes together.
As far as the Grub background, there shouldn't be any issues I am aware of . . .
Which version did you install? The image is a 1920x1080.png and should work without issue.
I would ask if you are able to change the grub background using the grub background changer in the menu?
@unklar, I agree! I've thought about having the splash for just the live session. After install, it just annoys me to no end.
*EDIT Has anybody else been missing their grub screen background after install? It should be a picture of Lilidog in an all black background. The only possibility I can see at the moment is some sort of display issues with the image size?

Thanks for the tip and will add the "splash" to the grub cmdline (if I choose to enable it) and will take a look at the image as the monitor I am using it in is a 1920x1080px.

sleekmason · 2022-03-13 14:57:45

DeepDayze wrote:

Thanks for the tip and will add the "splash" to the grub cmdline (if I choose to enable it) and will take a look at the image as the monitor I am using it in is a 1920x1080px.

Thank you:)

For anybody that may have a good grip on this: Would it mess anything up for different types of installs with nvidia and the like, if I were to use sed to add 'splash' to the grub command line in a script?

I simply don't know enough here yet. I have zero computers with anything other than intel graphics. In any event, I can make a script to add 'splash' to the grub command line, and then give people an option to enable splash in the installed system. Really just need the info from someone who know a bit about this before proceeding.

Easy enough to make another one to remove it as well, but that wouldn't help much if someone can't get into their system.

DeepDayze · 2022-03-13 15:09:24

sleekmason wrote:

DeepDayze wrote:
Thanks for the tip and will add the "splash" to the grub cmdline (if I choose to enable it) and will take a look at the image as the monitor I am using it in is a 1920x1080px.
Thank you:)
For anybody that may have a good grip on this: Would it mess anything up for different types of installs with nvidia and the like, if I were to use sed to add 'splash' to the grub command line in a script?
I simply don't know enough here yet. I have zero computers with anything other than intel graphics. In any event, I can make a script to add 'splash' to the grub command line, and then give people an option to enable splash in the installed system. Really just need the info from someone who know a bit about this before proceeding.
Easy enough to make another one to remove it as well, but that wouldn't help much if someone can't get into their system.

Maybe leave it as it is and perhaps put some notes somewhere with additional information how to enable/disable the splash.

unklar · 2022-03-13 16:15:52

sleekmason wrote:

I would ask if you are able to change the grub background using the grub background changer in the menu?

This works perfectly, even with your own images in the appropriate size, basically preferring .png
-----------
I am not a friend of "splash", because I always want to see the startup process, because already there I notice errors. Therefore it says here in the /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="systemd.show_status=1 quiet resume=UUID=155fec67-8fb0-425e-b474-93a8fe189abc"

Who likes it "colorful", should leave the splash 'in it.

I wouldn't recommend doing it through an additional script either. Whether nvidia or not, you are building in additional error sources. That's my opinion.

#121 2022-03-11 20:03:55

Re: New ISO build to try.

#122 2022-03-11 22:56:31

Re: New ISO build to try.

#123 2022-03-12 03:31:34

Re: New ISO build to try.

#124 2022-03-12 08:07:59

Re: New ISO build to try.

#125 2022-03-12 12:22:25

Re: New ISO build to try.

#126 2022-03-12 12:39:18

Re: New ISO build to try.

#127 2022-03-12 15:36:10

Re: New ISO build to try.

#128 2022-03-12 15:40:50

Re: New ISO build to try.

#129 2022-03-12 15:42:51

Re: New ISO build to try.

#130 2022-03-12 17:15:11

Re: New ISO build to try.

#131 2022-03-12 18:41:28

Re: New ISO build to try.

#132 2022-03-12 23:38:07

Re: New ISO build to try.

#133 2022-03-12 23:49:56

Re: New ISO build to try.

#134 2022-03-13 01:31:35

Re: New ISO build to try.

#135 2022-03-13 13:46:35

Re: New ISO build to try.

#136 2022-03-13 14:24:39

Re: New ISO build to try.

#137 2022-03-13 14:43:25

Re: New ISO build to try.

#138 2022-03-13 14:57:45

Re: New ISO build to try.

#139 2022-03-13 15:09:24

Re: New ISO build to try.

#140 2022-03-13 16:15:52

Re: New ISO build to try.

Board footer