Nightly builds

Important informations about SolydXK including releases notes, forum rules and other anouncements
User avatar
patzy
Posts: 410
Joined: 15 Dec 2013 08:32
Location: Australia

Re: Nightly builds

Postby patzy » 19 Dec 2014 01:26

Schoelje wrote:
tuxic wrote:I personally think that with systemd the need of Plymouth is none. With the boot time so reduced, you don't have time to display it. Last time I saw it , disappeared in half a second! :cry:
That's my experience also, but I doubt that's the case with older systems.
As you probably know I have an 'older system". I don't run Plymouth, having had a lot of trouble with it over the past year.
Systemd is faster but with an old system there is anything up to 8 secs delay, with a completely blank black screen, before the desktop comes up. :o
The first time it happened I thought I'd lost everthing, but I'm used to it now.
If this happens to anyone new they would have a big fright.

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: Nightly builds

Postby Snap » 19 Dec 2014 06:40

Good point.
This likely means that your installation is broken. -Mr Pixbuf.

Image

kurotsugi
Posts: 2240
Joined: 09 Jan 2014 00:17

Re: Nightly builds

Postby kurotsugi » 19 Dec 2014 07:14

when I said plymouth is broke I refer to zz's post here http://forums.solydxk.nl/viewtopic.php?f=34&t=5025 it was the #2 breakage. you can't directly upgrade to jessie if you have plymouth.

Code: Select all

update-initramfs: Generating /boot/initrd.img-3.16-2-amd64
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.16-2-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
you need a certain trick to safely upgrade to jessie.

as for the plymouth logs,

Code: Select all

# systemctl status plymouth-start.service
● plymouth-start.service - Show Plymouth Boot Screen
   Loaded: loaded (/lib/systemd/system/plymouth-start.service; static)
   Active: inactive (dead) since Mon 2014-12-15 07:05:45 CET; 7h ago
  Process: 571 ExecStartPost=/bin/plymouth show-splash (code=exited, status=0/SUCCESS)
  Process: 568 ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS)
 Main PID: 379 (code=exited, status=0/SUCCESS)
it means that plymouth is fine (at least as a boot logger). I might be wrong but AFAIK we need plymouth-drm to make the splash work. we can try to install it then rebuild the initramfs by using 'sudo update-initramfs -U'

User avatar
Arjen Balfoort
Site Admin
Posts: 9333
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Nightly builds

Postby Arjen Balfoort » 19 Dec 2014 08:05

As far as I know plymouth-drm is now integrated into plymouth and is no longer available in the repositories (only the previous version in Wheezy).

I haven't found any problems upgrading the HE isos and the BE isos as long as I followed my own instructions:
http://forums.solydxk.nl/viewtopic.php?f=33&t=5095
http://forums.solydxk.nl/viewtopic.php?f=33&t=5092

On metal Plymouth seems to work but my new system just flashes Plymouth. During shutdown it shows perfectly (it takes 90 seconds until the NAS throws a time-out on my wireless connection - still haven't found a solution for that).

In VB Plymouth doesn't work but it doesn't throw any errors either. Systemd says it's running fine.


SolydXK needs you!
Development | Testing | Translations

kurotsugi
Posts: 2240
Joined: 09 Jan 2014 00:17

Re: Nightly builds

Postby kurotsugi » 19 Dec 2014 09:04

I'd like to know solydxk content of this file.

Code: Select all

cat /etc/initramfs-tools/modules

User avatar
Arjen Balfoort
Site Admin
Posts: 9333
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Nightly builds

Postby Arjen Balfoort » 19 Dec 2014 09:40

Thanks for helping me out with this.

This is default for all SolydXK ISOs:

/etc/initramfs-tools/modules:

Code: Select all

uvesafb mode_option=1024x768-24 mtrr=3 scroll=ywrap
/etc/initramfs-tools/conf.d/splash:

Code: Select all

FRAMEBUFFER=y
/etc/default/grub:

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Theme is set with:

Code: Select all

sudo plymouth-set-default-theme solydk-logo
update-grub
update-initramfs -t -u -k all
This has always worked. Even better than using this: https://wiki.debian.org/plymouth

Now it works on metal, but not in VB.

However, my system is not the average system (fanless i7 quadcore with sdd):

Code: Select all

$ inxi -Fxx
System:    Host: solydk64 Kernel: 3.16.0-4-amd64 x86_64 (64 bit gcc: 4.8.3) 
           Desktop: KDE 4.14.2 (Qt 4.8.6) dm: lightdm Distro: SolydXK 1 solydxk 
Machine:   System: ASUS product: All Series
           Mobo: ASUSTeK model: Q87T v: Rev X.0x Bios: American Megatrends v: 0907 date: 06/27/2014
CPU:       Quad core Intel Core i7-4785T (-HT-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 17561 
           Clock Speeds: 1: 2263 MHz 2: 2212 MHz 3: 2200 MHz 4: 2665 MHz 5: 2200 MHz 6: 2196 MHz 7: 2200 MHz
           8: 2200 MHz
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
           bus-ID: 00:02.0 chip-ID: 8086:0412
           Display Server: X.Org 1.16.1.901 driver: intel Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel Haswell Desktop GLX Version: 3.0 Mesa 10.3.2 Direct Rendering: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Definition Audio Controller 
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:8c20 
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller 
           driver: snd_hda_intel bus-ID: 00:03.0 chip-ID: 8086:0c0c 
           Sound: Advanced Linux Sound Architecture v: k3.16.0-4-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168
           IF: eth1 state: down mac: 38:2c:4a:6c:c0:17
           Card-2: Intel Wireless 7260 driver: iwlwifi v: in-tree: bus-ID: 04:00.0 chip-ID: 8086:08b1
           IF: wlan0 state: up mac: f8:16:54:db:c4:19
           Card-3: Intel Ethernet Connection I217-LM
           driver: e1000e v: 2.3.2-k port: f080 bus-ID: 00:19.0 chip-ID: 8086:153a
           IF: eth2 state: down mac: 38:2c:4a:6c:c2:6e
Drives:    HDD Total Size: 250.1GB (47.2% used)                                                                
           ID-1: /dev/sda model: Samsung_SSD_840 size: 250.1GB serial: S1DBNSAF939332Z temp: 0C                
Partition: ID-1: / size: 32G used: 13G (41%) fs: ext4 dev: /dev/sda3                                           
           ID-2: /home size: 190G used: 91G (51%) fs: ext4 dev: /dev/sda4 
           ID-3: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 259 Uptime: 3:14 Memory: 3586.5/7875.0MB 
           Init: systemd v: 215 runlevel: 5 default: 2 Gcc sys: 4.9.1 alt: 4.8 
           Client: Shell (bash 4.3.301 running in konsole) inxi: 2.1.28 


SolydXK needs you!
Development | Testing | Translations

kurotsugi
Posts: 2240
Joined: 09 Jan 2014 00:17

Re: Nightly builds

Postby kurotsugi » 19 Dec 2014 16:19

plymouth need drm for best result so we need to add drm into /etc/initramfs-tools/modules. intel seems doesn't need it but when I was using ATI, I need to specify it or my boot splash will looks ugly.

Code: Select all

uvesafb mode_option=1024x768-24 mtrr=3 scroll=ywrap
drm
as for a system with a super fast boot we can do this trick on /etc/plymouth/plymouthd.conf

Code: Select all

[Daemon]
Theme=joy
ShowDelay=7
common system with HDD takes ~18 seconds to boot while on SSD we need ~8 seconds so IMO best value would be between 5 to 10. both tested and work quite well on metal and VB. however, I should note that my VB is an X less system (boot splash work but it's very simple. a moving dot) and I didn't use plymouth-X11 on both system.

User avatar
Arjen Balfoort
Site Admin
Posts: 9333
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Nightly builds

Postby Arjen Balfoort » 19 Dec 2014 18:47

Okay, I'm building a SolydK64 ISO now with those changes.
Let's see if it works when running live.

If so, I'll have to adapt the Debian Plymouth Manager as well (a note to myself).

I'll post back with the results as soon as I can.


SolydXK needs you!
Development | Testing | Translations

kurotsugi
Posts: 2240
Joined: 09 Jan 2014 00:17

Re: Nightly builds

Postby kurotsugi » 19 Dec 2014 19:39

since you mentioned it, I got two problem with our plymouth manager
1. it delete my boot parameter. the best idea would be to not delete user boot parameter. if we can't do that at least we need to backup user's grub config and notify the user that his grub config is modified. OTOH "quite splash" is our default setting and user rarely delete "splash" so I believe plymouth manager actually don't have to modify grub config at all.
2. it takes too long to rebuild the initramfs. "update-initramfs -u -k all" usually fast because we only modify small part on our initramfs. can we do something about this?

User avatar
Arjen Balfoort
Site Admin
Posts: 9333
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Nightly builds

Postby Arjen Balfoort » 19 Dec 2014 20:13

Unfortunately, even with your changes, I see no difference.
I'm going to upload new nightly builds with these changes so you can see it for yourself.
It'll take a while before they're uploaded. I'll post here when I'm done.

Regarding Debian Plymouth Manager. If you know a bit of Python, you could take a look at the source: https://github.com/SolydXK/debian-plymouth-manager


SolydXK needs you!
Development | Testing | Translations

User avatar
Arjen Balfoort
Site Admin
Posts: 9333
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Nightly builds

Postby Arjen Balfoort » 20 Dec 2014 00:35

The nightly builds with kurotsugi's changes are ready for download: http://downloads.solydxk.nl/nightly/


SolydXK needs you!
Development | Testing | Translations

User avatar
tuxic
Posts: 39
Joined: 24 Sep 2013 10:31

Re: Nightly builds

Postby tuxic » 24 Dec 2014 06:49

Just a warm advice against the use of Plymouth in Debian (specially in sid):
http://forum.siduction.org/index.php?topic=5244.0
You've been warned...

User avatar
Arjen Balfoort
Site Admin
Posts: 9333
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Nightly builds

Postby Arjen Balfoort » 24 Dec 2014 08:14

It's not a warning it's just a rant against Plymouth and Ubuntu in general.


SolydXK needs you!
Development | Testing | Translations

User avatar
tuktuk22
Posts: 105
Joined: 20 Mar 2013 08:54

Re: Nightly builds

Postby tuktuk22 » 25 Dec 2014 18:27

this nightly build is simply beautiful. :D
- solydk64
- debian testing

User avatar
grizzler
Posts: 2180
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Nightly builds

Postby grizzler » 25 Dec 2014 20:28

This may not be just about the nightly builds, but they're the most recent isos, so...

I've been playing with installing them in a VirtualBox VM with EFI. Actually, I've only managed to install SolydX isos so far, as trying to get the nightly SolydK64 to run Live in an EFI VM simply doesn't work (the November SolydK64 iso does work of sorts, but everything is running so excruciatingly slow it would probably take a day to install, so I aborted the attempt).

After installing SolydX64 I noticed it has grub-pc installed, which causes this error whenever you want to install or remove anything:

Code: Select all

You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 grub-efi : Depends: grub-common (= 2.02~beta2-17)
 grub-efi-amd64 : Depends: grub-common (= 2.02~beta2-17)
                  Depends: grub2-common (= 2.02~beta2-17)
 grub-efi-amd64-bin : Depends: grub-common (= 2.02~beta2-17)
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
solydx64-efi@vbox-efi ~ $
After doing that, you can of course purge grub-pc without issues, but it shouldn't be there in the first place (SolydX32 doesn't have it).
I've seen this reported before and that was an install on metal, so this is not a VM peculiarity.
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
Arjen Balfoort
Site Admin
Posts: 9333
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Nightly builds

Postby Arjen Balfoort » 25 Dec 2014 20:38

So, correct me if I'm wrong. The live-installer should purge grub-pc when grub-efi is being installed?
Does non-efi systems rely on grub-pc?


SolydXK needs you!
Development | Testing | Translations

User avatar
grizzler
Posts: 2180
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Nightly builds

Postby grizzler » 25 Dec 2014 20:46

Non-efi systems require grub-pc, yes.
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
just
Posts: 297
Joined: 07 Nov 2013 08:06
Location: Rovaniemi, Finland

Re: Nightly builds

Postby just » 26 Dec 2014 19:31

just a quick note about Plymouth. it continues to run smoothly (fading in-and-out SolydXK logo in default config) on the following hardware here:
  • pure Intel GPU integrated controller, on Acer S3-951 ultrabook
  • pure AMD Radeon HD 6650M, on Acer 7750G notebook
  • hybrid Intel+NVIDIA GeForce GT 555M (nvidia-optimus), on Dell L702X 17 eXtreme Power Station (XPS) notebook
  • hybrid Intel+NVIDIA GeForce GT 750M (nvidia-optimus), on Acer V5-573G ultrabook
it runs equally well starting from the earlier 2013.03 ISOs and ending up with the recently available solydk64_201412.iso 2014-12-19 nightly builds.

it works without a problem on all that hardware, in both Live session and installed system, making a nice power up and shut down effect. with extreme ease it may be disabled/enabled from the kernel's boot parameters. inability to control the Plymouth doesn't seem to be a good reason to remove it completely.

if it is still possible, please, don't remove it.

Happy New Year to all!
Image

User avatar
Arjen Balfoort
Site Admin
Posts: 9333
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Nightly builds

Postby Arjen Balfoort » 27 Dec 2014 09:06

@grizzler
Strange, if I install grub-efi, grub-pc is removed. I haven't got it installed on either of my EFI systems.

@just
I'm not planning on removing Plymouth and a happy new year to you too!


SolydXK needs you!
Development | Testing | Translations

User avatar
grizzler
Posts: 2180
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Nightly builds

Postby grizzler » 27 Dec 2014 11:04

Schoelje wrote:Strange, if I install grub-efi, grub-pc is removed. I haven't got it installed on either of my EFI systems.
Yes, grub-efi and grub-pc conflict with each other, so this is expected. However, if I install SolydX64 in an EFI environment, grub-pc is fully installed and grub-efi, grub-efi-amd64 and grub-efi-amd64-bin aren't (which causes apt-get to come up with the error I mentioned in my first message of 25-12).

Just to be sure this wasn't a one off glitch, I performed the installation twice, using a newly created VM each time. Same result both times. So I have to assume the SolydX64 iso's installer is responsible for putting grub-pc in the install.
Frank

SolydX EE 64 - tracking Debian Testing


Return to “News & Anouncements”

Who is online

Users browsing this forum: No registered users and 4 guests