Need help testing

SolydXK is too quiet for you? SolydXK Enthusiast Editions, based on Debian Testing is for you! Here you can find news about Debian Testing and Unstable too, and also tests on SolydXK programs.
The support for SolydXK EE is provided by the community.
User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Need help testing

Postby zerozero » 24 Jun 2014 11:45

@Dan
for those who have deb-multimedia already enabled in sources.list (all the HE installed systems until now) they should keep using it, otherwise it might break the multimedia stack with future updates.

for the isos released from now on, deb-multimedia will be an optional.
bliss of ignorance

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Need help testing

Postby zerozero » 24 Jun 2014 11:48

kurotsugi wrote:@zz: AFAIK samba didn't work well with systemd yet. that's the reason why it boot twice longer with samba.
yeahh now i remember reading something about that in the mint sid's breakage topic :mrgreen: (from you :lol: )
Schoelje wrote:or even in the welcome screen as suggested by kurotsugi.
this would be the best compromise
bliss of ignorance

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

Re: Need help testing

Postby Arjen Balfoort » 24 Jun 2014 11:55

zerozero wrote:
Schoelje wrote:or even in the welcome screen as suggested by kurotsugi.
this would be the best compromise
...or better even: in the live-installer!
People tend to look better at the instructions of the live-installer than the welcome screen. Furthermore, I'm already working on the live-installer to improve localization for our Japanese friends: http://forums.solydxk.nl/viewtopic.php?p=38293#p38293


SolydXK needs you!
Development | Testing | Translations

User avatar
MAYBL8
Posts: 1487
Joined: 10 Mar 2013 18:41
Location: Maryland Heights, MO USA
Contact:

Re: Need help testing

Postby MAYBL8 » 24 Jun 2014 11:59

@Dan
for those who have deb-multimedia already enabled in sources.list (all the HE installed systems until now) they should keep using it, otherwise it might break the multimedia stack with future updates.

for the isos released from now on, deb-multimedia will be an optional.
Sounds like this is going to get complicated for testing purposes and fixing users problems.

Just an observation.
I know you guys will make it simplified.


User avatar
ane champenois
Posts: 1539
Joined: 24 Feb 2013 08:17
Location: Grands lacs Forêt d'Orient, France

Re: Need help testing

Postby ane champenois » 24 Jun 2014 12:07

Schoelje wrote: @ane
Please clean the pen drive before using Unetbootin.
I cleaned it with Gparted...I suppose that was an artifact, or perhaps my pendrive becoming old.
zerozero wrote: for those who have deb-multimedia already enabled in sources.list (all the HE installed systems until now) they should keep using it, otherwise it might break the multimedia stack with future updates.

for the isos released from now on, deb-multimedia will be an optional.
Hum...something to keep in mind if somebody has a multimedia problem. ;)
Schoelje wrote:
zerozero wrote:
Schoelje wrote:or even in the welcome screen as suggested by kurotsugi.
this would be the best compromise
...or better even: in the live-installer!
People tend to look better at the instructions of the live-installer than the welcome screen. Furthermore, I'm already working on the live-installer to improve localization for our Japanese friends: http://forums.solydxk.nl/viewtopic.php?p=38293#p38293
Nice for Japan community 8-)
You're right: I suppose most of end-users just close the welcome screen to get rid of it...and they can't do that with the live-installer so it's safer to avoid people coming on the forum because of no-OOTB DVD playing (not sure this is real english :lol: )
----
Testing the SolydX 32: everything's fine on the live-installer version. Installing on bare...to be continued...
They did not know it was impossible so they did it.

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

Re: Need help testing

Postby kurotsugi » 24 Jun 2014 13:10

I'm convinced this is going to get solved upstream in time. I suppose there's not much we can do about it?
aside from samba I wonder if we could enhance the boot process. we'll need to further investigate the system by 'systemd-analyze critical-chain' command. I saw some suspicious processes in zz's blame list.

Code: Select all

10.126s clamav-freshclam.service
2.081s dirmngr.service
6.003s timidity.service

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

Re: Need help testing

Postby Arjen Balfoort » 24 Jun 2014 13:23

kurotsugi wrote:
I'm convinced this is going to get solved upstream in time. I suppose there's not much we can do about it?
aside from samba I wonder if we could enhance the boot process. we'll need to further investigate the system by 'systemd-analyze critical-chain' command. I saw some suspicious processes in zz's blame list.

Code: Select all

10.126s clamav-freshclam.service
2.081s dirmngr.service
6.003s timidity.service
Good idea!
Could you create a new topic (in this testing section) for this?


SolydXK needs you!
Development | Testing | Translations

User avatar
ane champenois
Posts: 1539
Joined: 24 Feb 2013 08:17
Location: Grands lacs Forêt d'Orient, France

Re: Need help testing

Postby ane champenois » 24 Jun 2014 13:31

SolydX32 on bare metal: working smootly 8-)
Wainting for the new topic on systemd to provide some infos too ;)
They did not know it was impossible so they did it.

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

Re: Need help testing

Postby kurotsugi » 24 Jun 2014 14:04

we only need the result of these two commands to investigate it.

Code: Select all

systemd-analyze blame
systemd-analyze critical-chain
IMO we don't need a separate thread for it. it should be ended faster than we thought. we can decide what should we do after we got the result of these commands from solydx and solydk.

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

Re: Need help testing

Postby ScottQuier » 24 Jun 2014 14:24

Here's mine on SoldyK-64:

Code: Select all

scott@k64-systemd ~ $ systemd-analyze 
Startup finished in 6.604s (kernel) + 18.005s (userspace) = 24.610s
scott@k64-systemd ~ $ systemd-analyze blame
         11.056s samba.service
         10.591s nmbd.service
          9.835s samba-ad-dc.service
          5.277s ModemManager.service
          5.201s NetworkManager.service
          5.115s clamav-freshclam.service
          4.388s timidity.service
          3.774s lightdm.service
          3.119s systemd-fsck-root.service
          2.946s bootlogs.service
          2.339s ufw.service
          1.944s polkitd.service
          1.882s loadcpufreq.service
          1.759s avahi-daemon.service
          1.707s keyboard-setup.service
          1.429s systemd-logind.service
          1.413s binfmt-support.service
          1.361s dirmngr.service
          1.319s nvidia-kernel.service
          1.258s rsyslog.service
          1.162s virtualbox-guest-utils.service
          1.131s networking.service
          1.020s colord.service
           949ms dns-clean.service
           947ms sys-kernel-debug.mount
           895ms dev-hugepages.mount
           894ms dev-mqueue.mount
           721ms minissdpd.service
           667ms systemd-modules-load.service
           632ms kbd.service
           558ms systemd-udev-trigger.service
           539ms hdparm.service
           536ms virtualbox-guest-x11.service
           471ms lm-sensors.service
           442ms systemd-random-seed-load.service
           442ms systemd-user-sessions.service
           425ms udisks2.service
           385ms winbind.service
           376ms console-kit-log-system-start.service
           376ms alsa-restore.service
           369ms systemd-udevd.service
           332ms motd.service
           325ms systemd-sysctl.service
           302ms smbd.service
           274ms systemd-tmpfiles-setup.service
           208ms sys-fs-fuse-connections.mount
           205ms systemd-tmpfiles-setup-dev.service
           203ms console-setup.service
           179ms console-kit-daemon.service
           116ms openvpn.service
           104ms upower.service
            95ms pulseaudio.service
            69ms systemd-remount-fs.service
            64ms rtkit-daemon.service
            54ms proc-sys-fs-binfmt_misc.mount
            54ms systemd-tmpfiles-clean.service
            49ms rc-local.service
            49ms systemd-update-utmp-runlevel.service
            45ms hddtemp.service
            44ms dev-disk-by\x2duuid-31808665\x2db058\x2d4073\x2d8b03\x2d4c19d83081ee.swap
            23ms pppd-dns.service
             3ms saned.service
             3ms cpufrequtils.service
             2ms systemd-journal-flush.service
             1ms run-lock.mount
             1ms run-user.mount
scott@k64-systemd ~ $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @17.955s
└─multi-user.target @17.955s
  └─winbind.service @17.569s +385ms
    └─samba.service @6.512s +11.056s
      └─basic.target @6.509s
        └─sockets.target @6.509s
          └─dbus.socket @6.508s
            └─sysinit.target @6.465s
              └─ufw.service @4.126s +2.339s
                └─local-fs.target @4.126s
                  └─run-user.mount @4.124s +1ms
                    └─local-fs-pre.target @4.124s
                      └─systemd-remount-fs.service @4.054s +69ms
                        └─keyboard-setup.service @1.481s +1.707s
                          └─systemd-udevd.service @1.111s +369ms
                            └─systemd-tmpfiles-setup-dev.service @905ms +205ms
                              └─systemd-journald.socket @851ms
                                └─-.mount @851ms
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

wayne
Posts: 178
Joined: 25 Feb 2013 14:58

Re: Need help testing

Postby wayne » 24 Jun 2014 14:28

Solydx_32, test iso

Code: Select all

wayne@solydx32:~$ systemd-analyze
Startup finished in 11.621s (kernel) + 26.531s (userspace) = 38.153s
wayne@solydx32:~$ systemd-analyze blame
         14.929s samba.service
         14.195s nmbd.service
         13.962s samba-ad-dc.service
          8.197s solydxk-system.service
          8.097s ModemManager.service
          8.096s NetworkManager.service
          8.093s accounts-daemon.service
          6.611s clamav-freshclam.service
          5.632s exim4.service
          5.606s lightdm.service
          5.426s avahi-daemon.service
          5.424s systemd-logind.service
          4.639s loadcpufreq.service
          4.409s ufw.service
          3.977s systemd-fsck-root.service
          2.755s bootlogs.service
          2.683s keyboard-setup.service
          2.672s networking.service
          2.629s rpcbind.service
          2.411s kbd.service
          2.203s rsyslog.service
          2.195s polkitd.service
          2.050s virtualbox-guest-x11.service
          1.937s lm-sensors.service
          1.898s upower.service
          1.851s ntp.service
          1.767s nfs-common.service
          1.585s console-kit-log-system-start.service
          1.427s hdparm.service
          1.348s binfmt-support.service
          1.280s sys-kernel-debug.mount
          1.275s winbind.service
          1.252s dev-mqueue.mount
          1.217s dev-hugepages.mount
          1.020s systemd-tmpfiles-setup.service
           937ms systemd-modules-load.service
           936ms systemd-random-seed-load.service
           913ms virtualbox-guest-utils.service
           795ms hdapsd.service
           757ms systemd-udev-trigger.service
           623ms rtkit-daemon.service
           602ms smbd.service
           469ms systemd-remount-fs.service
           446ms systemd-user-sessions.service
           417ms systemd-update-utmp-runlevel.service
           374ms systemd-tmpfiles-setup-dev.service
           367ms colord.service
           360ms systemd-udevd.service
           359ms minissdpd.service
           357ms lpd.service
           299ms decnet.service
           277ms systemd-sysctl.service
           232ms console-setup.service
           230ms alsa-restore.service
           212ms motd.service
           211ms hddtemp.service
           172ms udisks2.service
           120ms openvpn.service
           108ms sys-fs-fuse-connections.mount
            97ms console-kit-daemon.service
            92ms pulseaudio.service
            59ms pppd-dns.service
            58ms rc-local.service
            54ms saned.service
            32ms proc-sys-fs-binfmt_misc.mount
            11ms plymouth-quit.service
            11ms plymouth-read-write.service
             6ms cpufrequtils.service
             3ms systemd-journal-flush.service
             2ms plymouth-quit-wait.service
             1ms run-lock.mount
             1ms run-user.mount
wayne@solydx32:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @26.112s
└─multi-user.target @26.112s
  └─winbind.service @24.837s +1.275s
    └─samba.service @9.907s +14.929s
      └─basic.target @9.905s
        └─sockets.target @9.905s
          └─dbus.socket @9.905s
            └─sysinit.target @9.876s
              └─ufw.service @5.466s +4.409s
                └─local-fs.target @5.466s
                  └─run-rpc_pipefs.mount @9.741s
                    └─local-fs-pre.target @5.464s
                      └─systemd-remount-fs.service @4.994s +469ms
                        └─keyboard-setup.service @1.751s +2.683s
                          └─systemd-udevd.service @1.390s +360ms
                            └─systemd-tmpfiles-setup-dev.service @1.015s +374ms
                              └─systemd-journald.socket @951ms
                                └─-.mount @950ms
wayne@solydx32:~$ 


Same computer, another debian-xfce-sid

Code: Select all

Startup finished in 5.422s (kernel) + 12.664s (userspace) = 18.086s
[wayne@trios][~]$ systemd-analyze blame
          6.747s ModemManager.service
          6.093s exim4.service
          6.060s NetworkManager.service
          5.752s bootlogs.service
          5.706s accounts-daemon.service
          5.516s avahi-daemon.service
          5.513s systemd-logind.service
          5.459s lightdm.service
          4.436s alsa-restore.service
          4.189s rsyslog.service
          3.455s minissdpd.service
          2.706s ntp.service
          2.601s networking.service
          1.990s virtualbox-guest-utils.service
          1.894s lm-sensors.service
          1.830s saned.service
          1.668s console-kit-log-system-start.service
          1.386s motd.service
          1.380s hddtemp.service
          1.311s keyboard-setup.service
          1.301s systemd-fsck-root.service
          1.189s kbd.service
          1.182s virtualbox-guest-x11.service
           888ms hdparm.service
           882ms gdomap.service
           853ms systemd-tmpfiles-setup.service
           741ms dev-hugepages.mount
           740ms sys-kernel-debug.mount
           739ms pppd-dns.service
           738ms systemd-user-sessions.service
           712ms dev-mqueue.mount
           545ms keymap.service
           539ms systemd-tmpfiles-setup-dev.service
           495ms rc-local.service
           445ms systemd-modules-load.service
           300ms upower.service
           243ms sys-fs-fuse-connections.mount
           211ms systemd-udev-trigger.service
           199ms lvm2.service
           177ms systemd-sysctl.service
           137ms udisks2.service
           132ms udev-finish.service
           125ms console-setup.service
           108ms systemd-remount-fs.service
           107ms polkitd.service
            81ms console-kit-daemon.service
            72ms pulseaudio.service
            58ms systemd-update-utmp-runlevel.service
            58ms rtkit-daemon.service
            39ms systemd-udevd.service
             2ms systemd-journal-flush.service
             1ms run-user.mount
             1ms run-lock.mount
             1ms live-tools.service
             1ms systemd-random-seed-load.service
[wayne@trios][~]$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @12.604s
└─multi-user.target @12.604s
  └─exim4.service @6.511s +6.093s
    └─nss-lookup.target @6.511s
      └─network.target @5.775s
        └─networking.service @3.166s +2.601s
          └─local-fs.target @2.891s
            └─run-lock.mount @2.890s +1ms
              └─local-fs-pre.target @2.889s
                └─systemd-remount-fs.service @2.780s +108ms
                  └─keyboard-setup.service @1.468s +1.311s
                    └─systemd-udevd.service @1.428s +39ms
                      └─systemd-tmpfiles-setup-dev.service @888ms +539ms
                        └─systemd-journald.socket @821ms
                          └─-.mount @820ms
[wayne@trios][~]$ 

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

Re: Need help testing

Postby kurotsugi » 24 Jun 2014 15:28

KDE: the result overall seems good. our main problem is samba and samba related process. it add 14 seconds for boot process

Code: Select all

samba.service @9.907s +14.929s
winbind.service @24.837s +1.275s
these services took some of my interest

Code: Select all

5.115s clamav-freshclam.service
4.388s timidity.service
1.882s loadcpufreq.service
1.361s dirmngr.service
3ms cpufrequtils.service
I'm not quite sure about timidity and dirmngr (I never saw them on XFCE. they could be KDE specific services) but the other are optional services and can be turned off. it won't decrease the boot time but it lighten the burden in your system. you can turn them off by 'sudo systemctl disable <service name>.service'

XFCE: the result is similar with KDE. the point of interest are

Code: Select all

6.611s clamav-freshclam.service
5.632s exim4.service
4.639s loadcpufreq.service
299ms decnet.service
I don't know about decnet but exim4 isn't needed since we already have thunderbird. we can speed up the boot process up to 6 seconds if we remove exim4 as indicated here "exim4.service @6.511s +6.093s".

as a comparison, my result with a minimalistic installation of XFCE are:

Code: Select all

systemd-analyze     
Startup finished in 2.255s (kernel) + 13.707s (userspace) = 15.962s

systemd-analyze blame
          4.475s systemd-suspend.service
          4.318s systemd-fsck-root.service
          4.046s ModemManager.service
          3.781s NetworkManager.service
          3.316s keyboard-setup.service
          2.790s avahi-daemon.service
          2.784s systemd-logind.service
          2.689s lightdm.service
          1.323s ufw.service
          1.162s rsyslog.service
          1.118s systemd-fsck@dev-disk-by\x2duuid-FC7E\x2d02BD.service
           937ms virtualbox.service
           895ms nfs-common.service
           872ms sys-kernel-debug.mount
           871ms dev-hugepages.mount
           870ms dev-mqueue.mount
           793ms lm-sensors.service
           791ms tlp.service
           754ms bootlogs.service
           723ms systemd-udev-trigger.service
           711ms systemd-tmpfiles-setup-dev.service
           698ms systemd-modules-load.service
           575ms networking.service
           516ms systemd-fsck@dev-disk-by\x2duuid-8e753c67\x2d86fb\x2d480e\x2dbb9a\x2d36b3e44503ee.service
           472ms polkitd.service
           467ms rpcbind.service
           426ms upower.service
           398ms console-kit-log-system-start.service
           387ms wpa_supplicant.service
           330ms kbd.service
           312ms pppd-dns.service
           272ms systemd-tmpfiles-setup.service
           241ms rtkit-daemon.service
           233ms systemd-user-sessions.service
           220ms systemd-sysctl.service
           210ms udisks2.service
           198ms hddtemp.service
           187ms home.mount
           178ms console-setup.service
           126ms dev-disk-by\x2duuid-a980345c\x2dac83\x2d4ec3\x2dbfd6\x2d4e7f2025833b.swap
           126ms boot-efi.mount
           111ms openvpn.service
           109ms systemd-tmpfiles-clean.service
            94ms systemd-random-seed-load.service
            86ms rc-local.service
            78ms saned.service
            67ms console-kit-daemon.service
            56ms alsa-restore.service
            53ms systemd-update-utmp-runlevel.service
            51ms systemd-udevd.service
            46ms pulseaudio.service
            42ms systemd-remount-fs.service
            18ms motd.service
             3ms var-tmp.mount
             3ms run-lock.mount
             3ms systemd-journal-flush.service
             1ms run-user.mount

graphical.target @13.537s
└─multi-user.target @13.537s
  └─ModemManager.service @9.491s +4.046s
    └─basic.target @9.476s
      └─sockets.target @9.476s
        └─dbus.socket @9.476s
          └─sysinit.target @9.438s
            └─nfs-common.service @8.542s +895ms
              └─rpcbind.service @8.074s +467ms
                └─local-fs.target @8.073s
                  └─run-rpc_pipefs.mount @9.193s
                    └─local-fs-pre.target @6.108s
                      └─systemd-remount-fs.service @6.065s +42ms
                        └─keyboard-setup.service @2.486s +3.316s
                          └─systemd-udevd.service @2.434s +51ms
                            └─systemd-tmpfiles-setup-dev.service @1.722s +711ms
                              └─systemd-journald.socket @1.689s
                                └─-.mount @1.687s

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Need help testing

Postby zerozero » 25 Jun 2014 00:10

there's already a lot of info here but i will add from X-64 in VB

Code: Select all

zerozero@x64-d:~$ systemd-analyze
Startup finished in 4.689s (kernel) + 17.719s (userspace) = 22.408s

Code: Select all

zerozero@x64-d:~$ systemd-analyze blame
         11.221s samba.service
         10.776s nmbd.service
         10.367s samba-ad-dc.service
          8.075s clamav-freshclam.service
          6.050s ModemManager.service
          5.910s NetworkManager.service
          5.576s exim4.service
          5.225s solydxk-system.service
          4.841s accounts-daemon.service
          4.530s loadcpufreq.service
          3.189s ntp.service
          3.108s bootlogs.service
          3.087s lightdm.service
          2.836s avahi-daemon.service
          2.522s systemd-logind.service
          2.393s binfmt-support.service
          2.322s console-kit-daemon.service
          2.319s ufw.service
          2.042s polkitd.service
          1.807s colord.service
          1.414s networking.service
          1.376s nfs-common.service
          1.310s keyboard-setup.service
          1.212s rsyslog.service
          1.175s virtualbox-guest-utils.service
          1.041s virtualbox-guest-x11.service
           879ms hdparm.service
           865ms winbind.service
           850ms rpcbind.service
           782ms systemd-udev-trigger.service
           767ms dev-hugepages.mount
           766ms systemd-tmpfiles-setup-dev.service
           766ms sys-kernel-debug.mount
           741ms systemd-modules-load.service
           741ms dev-mqueue.mount
           713ms proc-sys-fs-binfmt_misc.mount
           586ms console-setup.service
           581ms hdapsd.service
           461ms kbd.service
           421ms openvpn.service
           418ms console-kit-log-system-start.service
           416ms lm-sensors.service
           406ms pulseaudio.service
           379ms systemd-user-sessions.service
           376ms decnet.service
           349ms alsa-restore.service
           325ms minissdpd.service
           325ms motd.service
           323ms lpd.service
           323ms hddtemp.service
           321ms pppd-dns.service
           317ms smbd.service
           310ms rc-local.service
           302ms saned.service
           175ms systemd-tmpfiles-setup.service
           166ms systemd-fsck-root.service
           156ms systemd-sysctl.service
           144ms systemd-udevd.service
           127ms systemd-random-seed-load.service
            84ms systemd-update-utmp-runlevel.service
            83ms udisks2.service
            61ms dev-disk-by\x2duuid-9463797b\x2d04ae\x2d4572\x2d9492\x2d95894f8257a3.swap
            57ms systemd-remount-fs.service
            48ms upower.service
            42ms rtkit-daemon.service
            16ms plymouth-read-write.service
            11ms systemd-journal-flush.service
            10ms plymouth-quit.service
             6ms cpufrequtils.service
             4ms sys-fs-fuse-connections.mount
             3ms run-user.mount
             2ms plymouth-quit-wait.service
             2ms run-lock.mount
zerozero@x64-d:~$ 

Code: Select all

zerozero@x64-d:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @17.633s
└─multi-user.target @17.633s
  └─winbind.service @16.767s +865ms
    └─samba.service @5.545s +11.221s
      └─basic.target @5.539s
        └─sockets.target @5.539s
          └─dbus.socket @5.539s
            └─sysinit.target @5.518s
              └─ufw.service @3.198s +2.319s
                └─local-fs.target @3.197s
                  └─run-rpc_pipefs.mount @5.260s
                    └─local-fs-pre.target @3.193s
                      └─systemd-remount-fs.service @3.135s +57ms
                        └─keyboard-setup.service @1.824s +1.310s
                          └─systemd-udevd.service @1.678s +144ms
                            └─systemd-tmpfiles-setup-dev.service @909ms +766ms
                              └─systemd-journald.socket @896ms
                                └─-.mount @894ms
zerozero@x64-d:~$ 
bliss of ignorance

User avatar
jsalpha2
Posts: 296
Joined: 28 May 2013 12:28

Re: Need help testing

Postby jsalpha2 » 25 Jun 2014 01:44

From SolydX64 real install

Code: Select all

joe@xfce:~$ systemd-analyze blame
         15.517s samba.service
         15.002s nmbd.service
         14.789s samba-ad-dc.service
          8.695s ModemManager.service
          8.120s solydxk-system.service
          7.626s NetworkManager.service
          6.867s lightdm.service
          6.839s accounts-daemon.service
          6.330s clamav-freshclam.service
          5.993s exim4.service
          4.566s ufw.service
          4.008s systemd-fsck-root.service
          3.825s rsyslog.service
          3.799s keyboard-setup.service
          3.659s avahi-daemon.service
          3.649s systemd-logind.service
          3.286s loadcpufreq.service
          3.131s bootlogs.service
          2.926s rpcbind.service
          2.677s polkitd.service
          2.469s systemd-tmpfiles-setup.service
          2.239s networking.service
          2.195s ntp.service
          2.048s binfmt-support.service
          2.017s kbd.service
          2.017s virtualbox-guest-x11.service
          1.761s nfs-common.service
          1.567s winbind.service
          1.388s systemd-random-seed-load.service
          1.166s lm-sensors.service
           975ms hdparm.service
           975ms dev-hugepages.mount
           974ms dev-mqueue.mount
           973ms sys-kernel-debug.mount
           809ms systemd-tmpfiles-clean.service
           795ms console-setup.service
           793ms colord.service
           731ms systemd-remount-fs.service
           703ms decnet.service
           593ms hdapsd.service
           581ms systemd-user-sessions.service
           574ms systemd-udev-trigger.service
           565ms systemd-modules-load.service
           560ms proc-sys-fs-binfmt_misc.mount
           540ms systemd-tmpfiles-setup-dev.service
           500ms openvpn.service
           493ms pulseaudio.service
           488ms upower.service
           462ms lpd.service
           440ms minissdpd.service
           431ms sys-fs-fuse-connections.mount
           429ms cpufrequtils.service
           420ms udisks2.service
           376ms smbd.service
           332ms virtualbox-guest-utils.service
           324ms dev-disk-by\x2duuid-f3a434b5\x2d3989\x2d4fc9\x2dbefd\x2dae574cd48cc3.swap
           218ms console-kit-log-system-start.service
           175ms systemd-sysctl.service
           123ms alsa-restore.service
            88ms console-kit-daemon.service
            78ms rtkit-daemon.service
            75ms hddtemp.service
            66ms rc-local.service
            61ms systemd-udevd.service
            44ms saned.service
            42ms motd.service
            41ms pppd-dns.service
            29ms systemd-update-utmp-runlevel.service
            13ms plymouth-read-write.service
            11ms plymouth-quit.service
             2ms run-lock.mount
             2ms systemd-journal-flush.service
             2ms plymouth-quit-wait.service
             1ms run-user.mount
joe@xfce:~$ 
joe@xfce:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @27.715s
└─multi-user.target @27.715s
  └─winbind.service @26.147s +1.567s
    └─samba.service @10.629s +15.517s
      └─basic.target @10.596s
        └─sockets.target @10.596s
          └─dbus.socket @10.596s
            └─sysinit.target @10.579s
              └─nfs-common.service @8.817s +1.761s
                └─rpcbind.service @5.891s +2.926s
                  └─local-fs.target @5.889s
                    └─run-rpc_pipefs.mount @10.471s
                      └─local-fs-pre.target @5.885s
                        └─systemd-remount-fs.service @5.154s +731ms
                          └─keyboard-setup.service @1.354s +3.799s
                            └─systemd-udevd.service @1.291s +61ms
                              └─systemd-tmpfiles-setup-dev.service @749ms +540ms
                                └─systemd-journald.socket @698ms
                                  └─-.mount @697ms

User avatar
patzy
Posts: 410
Joined: 15 Dec 2013 08:32
Location: Australia

Re: Need help testing

Postby patzy » 25 Jun 2014 04:03

Schoelje wrote:Tha's probably because these ISOs are now deb-multimedia fee, and that includes libdvdcss.
The question is: how should we handle this?
I can't live without running commercial DVDs on my computer! - Really!!

I suggest either putting the libdvdcss from VLC into the Solyd repos, or having an obvious note (maybe during or after install) about how to get it and make the install as simple as possible.

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Need help testing

Postby zerozero » 25 Jun 2014 10:47

patzy
http://forums.solydxk.nl/viewtopic.php? ... =80#p38308
being resolved (but anyway this question only affects new installs)
bliss of ignorance

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

Re: Need help testing

Postby Arjen Balfoort » 25 Jun 2014 21:10

I've just uploaded a new SolydK32 ISO for testing purposes only: http://downloads.solydxk.nl/dev/solydk32_201406.iso

This one has a new live-installer.
The live-installer can now be extended with a configuration file to install additional packages for a certain language. It contains a list for the Japanese language only, but I'll start a new topic soon to ask the community to create those lists for other languages as well.
It also has the possibility to install additional multimedia packages (libdvdcss2, w32codecs/w64codecs). It is pre-selected for installation.


SolydXK needs you!
Development | Testing | Translations

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Need help testing

Postby zerozero » 26 Jun 2014 10:56

if (as it seems) systemd is a solved issue we have 3 open questions regarding shipping the next isos without deb-multimedia
  • how to deal with (and communicate) the different sources.list?
  • identify possible regressions in multimedia support (local and online)
  • dropping deb-multimedia means as well that some app won't be available in the standard repo. what to do about that?
bliss of ignorance

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

Re: Need help testing

Postby kurotsugi » 26 Jun 2014 18:05

1. how to deal with (and communicate) the different sources.list?
2. identify possible regressions in multimedia support (local and online)
3. dropping deb-multimedia means as well that some app won't be available in the standard repo. what to do about that?
I'd like to change the 1st problem with

Code: Select all

what will we do with existing user which still using DMO? 
my proposal are:
1. announce it on UP note, forcefully 'purify' the system during UP upgrade.
2. announce it on UP note, suggest for clean install.
3. announce it, let user choose what to do with DMO. we can help them by creating a script to 'purify' solydxk if they want to do it.

the option 2 and 3 isn't a separated solution. we can combine it as a 1 option. there are also some another ideas in my mind but I think the easiest ones are three mentioned above. as for the second question, up until now our test give us possitive result and I'm quite optimistic that there won't be any problem with multimedia stuffs aside from dvd encoding and windows propietary codecs :3

the last question is a tricky one. not every software in DMO is essential. IMO first of all we need to decide which one should remain on solydxk. I'm thinking about creating a poll but it might require more works for us. my suggestion is that we only nothing other than libdvdcss, w32/w64 codecs and another essential package (if there any). after that, if there any user want something from DMO then we'll use the community repo mechanism.

as a less multimedia person (I only use audacious and totem on my daily usage) I feel that my ideas might not suitable for a multimedia person like wayne or the others. I think we'll need to hear other's opinion about it.

Transitman
Posts: 27
Joined: 08 Jun 2013 21:37

Re: Need help testing

Postby Transitman » 26 Jun 2014 21:36

kurotsugi;

I have an issue with what you propose.

Code: Select all

my proposal are:
1. announce it on UP note, forcefully 'purify' the system during UP upgrade.
2. announce it on UP note, suggest for clean install. 
3. announce it, let user choose what to do with DMO. we can help them by creating a script to 'purify' solydxk if they want to do it.
1. First part to announce the changes in a UP note is fine, but to forcefully purify someone's system during a UP upgrade smacks of something Canonical, Apple and Windows would do. I would be pissed if something like that happened. I am well aware of what laws are and are not allowing certain software packages. It is not up to ZZ and Schoelje to play policemen in this.
If someone wants to purify their system, then give them the tools, but don't force it down the users throat. That would create a lot of ill-will and potentially lose users who would otherwise not move on to another distro.

2. I have no issue with this. Making a suggestion is a lot better than forcing someone to do something. Linux is about freedom of choice, not what the developers want.

3. I have no issue with this either. In fact if someone can put together a script to do just that and then let testers use it to see if it does work without breaking anything, then it could fly. But if it breaks something, then let the end user decide for themselves what they really want to do.
If the script does not do what is intended, then option 2 should be suggested only, and again let the end user decide what they want to do.


Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 5 guests