LMDE Breakages (Tracking SID)

Archived topics about LMDE 1 and LMDE 2
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
Locked
GregE

Re: LMDE Breakages (Tracking SID)

Post by GregE »

I mostly agree with Gene,

Install LMDE and then eschew update packs in favor of just running "testing". It is never bleeding edge and mostly boringly stable. It is a good reliable work system. Or add Gnome 3.8 from testing. A daily "sudo apt-get update && sudo apt-get dist-upgrade" often gives nothing to do.

Running Sid is a little more labor intensive and can trip you up if you are not careful. I have three computers and it is my hobby not my business. I am happy to run Sid on my main machine. When the worst occasionally happens I just move to machine two until I can fix it. As a user of Chromium, Gmail, Google Calendar and Google Docs it does not matter which device or desktop I use. But not everyone can operate like that, nor has the time to muck about.

I have never had a major issue with LMDE + testing. That does not mean it cannot happen, just not likely. Having said that, the initial change to testing can be a bit of work. Conflicts between Cinnamon from Mint and Cinnamon from testing can be difficult. Running Xfce4 is always a safe start.

:)
Top
GeneC

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

GregE wrote:.....
I have never had a major issue with LMDE + testing. That does not mean it cannot happen, just not likely. Having said that, the initial change to testing can be a bit of work. Conflicts between Cinnamon from Mint and Cinnamon from testing can be difficult. Running Xfce4 is always a safe start.

:)
Hi Greg..

Certainly agree with that on XFCE. Actually my SID install with XFCE is more trouble free than my Testing install with Gnome 3.8 shell. Its my basic day to day go to Operating System. Getting linux-image-3.15-rc2-siduction-amd64 from Siduction today.. 8)
Top
kurotsugi

Re: LMDE Breakages (Tracking SID)

Post by kurotsugi »

Install LMDE and then eschew update packs in favor of just running "testing". It is never bleeding edge and mostly boringly stable.
debian now have 'always releasable testing policy'. I guess that's the explanation behind 'testing' boredom in these days :lol:
Top
GregE

Re: LMDE Breakages (Tracking SID)

Post by GregE »

Hang on to your hats, Sid just dist-upgraded me to systemd. It works except for a strange 15 sec stop before going on to GDM3.
Top
GeneC

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

Interesting... :P
Seemingly big changes in SID today. We had been getting systemd packages all along, but it was not automatically implemented. Well today it SEEMS it has.

sysvinit-core is removed and more systemd packages are installed..

Commit Log for Sun Apr 27 07:47:43 2014


Removed the following packages:
gvfs-backends
libgoa-1.0-0
sysvinit-core


Upgraded the following packages:
abiword (3.0.0-4+b2) to 3.0.0-4+b3
abiword-plugin-grammar (3.0.0-4+b2) to 3.0.0-4+b3
abiword-plugin-mathview (3.0.0-4+b2) to 3.0.0-4+b3
dconf-editor (0.18.0-1) to 0.20.0-2
dconf-gsettings-backend (0.18.0-1) to 0.20.0-2
dconf-service (0.18.0-1) to 0.20.0-2
evince (3.12.0-1) to 3.12.1-1
evince-common (3.12.0-1) to 3.12.1-1
evolution-data-server-common (3.8.5-3) to 3.12.1-1
gedit (3.10.4-1) to 3.12.1-1
gedit-common (3.10.4-1) to 3.12.1-1
gir1.2-clutter-1.0 (1.18.0-2) to 1.18.2-1
gir1.2-gtk-3.0 (3.12.0-4) to 3.12.1-1
gir1.2-peas-1.0 (1.8.1-2) to 1.10.0-2
glib-networking (2.40.0-2) to 2.40.1-1
glib-networking-common (2.40.0-2) to 2.40.1-1
glib-networking-services (2.40.0-2) to 2.40.1-1
gnome-keyring (3.8.2-2+b1) to 3.12.0-2
gvfs (1.20.1-1) to 1.20.1-1+b1
gvfs-daemons (1.20.1-1) to 1.20.1-1+b1
gvfs-libs (1.20.1-1) to 1.20.1-1+b1
libabiword-3.0 (3.0.0-4+b2) to 3.0.0-4+b3
libclutter-1.0-0 (1.18.0-2) to 1.18.2-1
libclutter-1.0-common (1.18.0-2) to 1.18.2-1
libclutter-gtk-1.0-0 (1.4.4-3+b1) to 1.5.2-1
libdconf1 (0.18.0-1) to 0.20.0-2
libebook-1.2-14 (3.8.5-3+b2) to 3.12.1-1
libebook-contacts-1.2-0 (3.8.5-3+b2) to 3.12.1-1
libevdocument3-4 (3.12.0-1) to 3.12.1-1
libevview3-3 (3.12.0-1) to 3.12.1-1
libgail-3-0 (3.12.0-4) to 3.12.1-1
libgexiv2-2 (0.10.0-1) to 0.10.1-1
libgmpxx4ldbl (2:6.0.0+dfsg-2) to 2:6.0.0+dfsg-2.2
libgoa-1.0-common (3.8.3-2) to 3.12.1-1
libgtk-3-0 (3.12.0-4) to 3.12.1-1
libgtk-3-bin (3.12.0-4) to 3.12.1-1
libgtk-3-common (3.12.0-4) to 3.12.1-1
libgtksourceview-3.0-1 (3.10.2-1) to 3.12.1-1
libgtksourceview-3.0-common (3.10.2-1) to 3.12.1-1
libgudev-1.0-0 (204-8) to 204-9
libnm-glib-vpn1 (0.9.8.8-7) to 0.9.8.10-1
libnm-glib4 (0.9.8.8-7) to 0.9.8.10-1
libnm-util2 (0.9.8.8-7) to 0.9.8.10-1
libpam-gnome-keyring (3.8.2-2+b1) to 3.12.0-2
libpam-systemd (204-8) to 204-9
libpeas-1.0-0 (1.8.1-2) to 1.10.0-2
libpeas-common (1.8.1-2) to 1.10.0-2
libsnmp-base (5.7.2.1~dfsg-3) to 5.7.2.1~dfsg-4
libsnmp30 (5.7.2.1~dfsg-3) to 5.7.2.1~dfsg-4
libsqlite3-0 (3.8.4.3-1) to 3.8.4.3-2
libsystemd-daemon0 (204-8) to 204-9
libsystemd-id128-0 (204-8) to 204-9
libsystemd-journal0 (204-8) to 204-9
libsystemd-login0 (204-8) to 204-9
libudev1 (204-8) to 204-9
libudev1:i386 (204-8) to 204-9
systemd (204-8) to 204-9
ucf (3.0027+nmu1) to 3.0028
udev (204-8) to 204-9

Installed the following packages:
libcamel-1.2-49 (3.12.1-1)
libebackend-1.2-7 (3.12.1-1)
libecal-1.2-16 (3.12.1-1)
libedata-book-1.2-20 (3.12.1-1)
libedataserver-1.2-18 (3.12.1-1)
systemd-sysv (204-9)

ALSO:
With the gnome 3.12 transition some gnome apps (i see in gedit) radical theme changes occur.. :shock:
(What happens to my gedit window borders..)..
Looks nice, but way different.
Image
Top
GeneC

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

Well a reboot into the above ^ was less than satisfactory... :?
Rebooted to command prompt and 'x-server' would not start. First time I broke this Sid (Siduction) partition since I installed it last July. I would hold back on DU's until its sorted (unless you have a clone and want to play).
Top
GeneC

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

GregE wrote:Hang on to your hats, Sid just dist-upgraded me to systemd. It works except for a strange 15 sec stop before going on to GDM3.
Greg.
Not so good for me.. Had you previously made systemd specific changes to your /etc/default/grub ? as suggested by Debian wiki. https://wiki.debian.org/systemd
Configuring for testing
To test systemd before switching to it by default, you can add the following boot parameter to the kernel:

init=/bin/systemd
in effect =
/etc/default/grub

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="init=/bin/systemd"
then

Code: Select all

sudo update-grub
I hadn't and it failed. Trying again with the above modification.
Top
GeneC

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

I made the above ^ modifications and still no good. Boot into command prompt, x-server will not start. Have to get back to this later. Systemd is not working for me.

Using Lightdm

Code: Select all

gene@Debian-SID:~$ inxi -F
System:    Host: Debian-SID Kernel: 3.15-rc2-siduction-amd64 x86_64 (64 bit) Desktop: N/A 
           Distro: Debian GNU/Linux jessie/sid 
Machine:   Mobo: ASUSTeK model: M4A88TD-M/USB3 v: Rev X.0x
           Bios: American Megatrends v: 1501 date: 08/09/2012
CPU:       Quad core AMD Phenom II X4 955 (-MCP-) cache: 2048 KB 
           Clock Speeds: 1: 2100 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz
Graphics:  Card: NVIDIA GF104 [GeForce GTX 460]
           Display Server: X.Org 1.15.1 driver: nvidia Resolution: 1680x1050@60.0hz
           GLX Renderer: GeForce GTX 460/PCIe/SSE2 GLX Version: 4.4.0 NVIDIA 337.12
Top
autocrosser

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

Wow--they break Sid & make the Experimental updates I needed FINALLY available......
I'm trying to think of what I did to make Systemd work in my system.....

1. Revert any mods you have done to /etc/sysctl.conf
2. Make sure you have removed cron or anacron & install systemd-cron
3. Get your syslog & post it --look for anything "weird"

I'll try to think of what else I've done & post it when I remember it.....

try being in the command prompt & do: /usr/bin/gnome-session instead of xstart
Top
GeneC

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

Hey AC... :)

I see some other new systemd updates just came through.

Code: Select all

Commit Log for Sun Apr 27 18:08:53 2014


Upgraded the following packages:
baobab (3.12.0-1) to 3.12.1-1
libglib2.0-0 (2.40.0-2) to 2.40.0-3
libglib2.0-0:i386 (2.40.0-2) to 2.40.0-3
libglib2.0-bin (2.40.0-2) to 2.40.0-3
libglib2.0-data (2.40.0-2) to 2.40.0-3
libgudev-1.0-0 (204-9) to 204-10
libsnmp-base (5.7.2.1~dfsg-4) to 5.7.2.1~dfsg-5
libsnmp30 (5.7.2.1~dfsg-4) to 5.7.2.1~dfsg-5
libsystemd-daemon0 (204-9) to 204-10
libsystemd-id128-0 (204-9) to 204-10
libsystemd-journal0 (204-9) to 204-10
libsystemd-login0 (204-9) to 204-10
libudev1 (204-9) to 204-10
libudev1:i386 (204-9) to 204-10
udev (204-9) to 204-10
I'll try again tomorrow. Thanks.



autocrosser wrote:Wow--they break Sid & make the Experimental updates I needed FINALLY available......
I'm trying to think of what I did to make Systemd work in my system.....

1. Revert any mods you have done to /etc/sysctl.conf
None made
2. Make sure you have removed cron or anacron & install systemd-cron
Will do that tomrrow.
3. Get your syslog & post it --look for anything "weird"
Will do that tomrrow.
I'll try to think of what else I've done & post it when I remember it.....

try being in the command prompt & do: /usr/bin/gnome-session instead of xstart
Using XFCE on this install (My gnome shell is Debian Testing)... :wink:
Top
autocrosser

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

Well--how about /usr/bin/xfce-session ??

Not sure on that one....you can look in /usr/bin/ & see what executes your session & try a command line start.....

I'm very interested in your syslog....you "should" see a large number of entries & systemd MUST be PID 1 --if not, you will get a system fail.

After you get things running again I have some mods from upstream for systemd-cron to make things work better....
Top
GregE

Re: LMDE Breakages (Tracking SID)

Post by GregE »

Gene, mine was a pure Debian Sid system with no modifications. Experimental wanted to remove my xorg, so yours might not boot to x because of that. I went to experimental just to get the last few bits of Gnome 3.12, then disabled it and went back to Sid. Then did the Sid upgrade and it then installed systemd. I have not looked into it yet, but it is possible Gnome 3.12 needs systemd as a dependency. So now I have a 3.12 desktop running on Sid with systemd.

Edit: I am having issues with GDM3. During boot the system sits for some time with just a flashing cursor, then GDM starts. When I select shutdown from Gnome nothing happens and I have to open a terminal and shutdown that way. But when I make lightdm the default the problems disappear. Boot is fast with only a few seconds from Grub to lightdm login. Shutdown is also functional and fast.
Top
wayne128

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

Gene, GregE , etc

I read your d-u..on systemd.

My turn.. I backup image first.
My Debian xfce sid was previously with systemd removed as on earlier posts.

After d-u, reboot, seems no issue at this installation.
perhaps it is because I do not have systemd..

Code: Select all

wayne@hp8000:~$ apt-cache policy systemd
systemd:
  Installed: (none)
  Candidate: 204-10
  Version table:
     204-10 0
        500 http://ftp.jp.debian.org/debian/ sid/main i386 Packages
     204-8 0
        100 /var/lib/dpkg/status
wayne@hp8000:~$ uname -a
Linux hp8000 3.13-1-686-pae #1 SMP Debian 3.13.10-1 (2014-04-15) i686 GNU/Linux
wayne@hp8000:~$ su
Password: 
root@hp8000:/home/wayne# aptitude update && aptitude dist-upgrade
Ign http://dl.google.com stable InRelease
Hit http://dl.google.com stable Release.gpg                
Hit http://dl.google.com stable Release                    
Hit http://dl.google.com stable/main i386 Packages
Hit http://ftp.jp.debian.org sid InRelease     
Hit http://ftp.jp.debian.org sid/main Sources/DiffIndex
Ign http://www.duinsoft.nl debs InRelease      
Hit http://ftp.jp.debian.org sid/contrib Sources/DiffIndex
Hit http://ftp.jp.debian.org sid/non-free Sources/DiffIndex
Hit http://ftp.jp.debian.org sid/main i386 Packages/DiffIndex
Hit http://ftp.jp.debian.org sid/contrib i386 Packages/DiffIndex
Hit http://ftp.jp.debian.org sid/non-free i386 Packages/DiffIndex
Hit http://ftp.jp.debian.org sid/contrib Translation-en/DiffIndex
Hit http://ftp.jp.debian.org sid/main Translation-en/DiffIndex
Hit http://www.duinsoft.nl debs Release.gpg
Hit http://ftp.jp.debian.org sid/non-free Translation-en/DiffIndex
Ign http://dl.google.com stable/main Translation-en_SG
Ign http://dl.google.com stable/main Translation-en
Hit http://www.duinsoft.nl debs Release
Hit http://www.duinsoft.nl debs/all i386 Packages
Ign http://www.duinsoft.nl debs/all Translation-en_SG
Ign http://www.duinsoft.nl debs/all Translation-en
                            
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
                                         
root@hp8000:/home/wayne#

However these stuff from dmesg happens.. not sure what are these and what issues they will bring..

Code: Select all

[    7.264271] Call Trace:
[    7.264276]  [<c140bd8e>] ? dump_stack+0x3e/0x4e
[    7.264279]  [<c104d45e>] ? warn_slowpath_common+0x7e/0xa0
[    7.264302]  [<f88e99b9>] ? swsci+0x2b9/0x2d0 [i915]
[    7.264324]  [<f88e99b9>] ? swsci+0x2b9/0x2d0 [i915]
[    7.264327]  [<c104d4b3>] ? warn_slowpath_fmt+0x33/0x40
[    7.264349]  [<f88e99b9>] ? swsci+0x2b9/0x2d0 [i915]
[    7.264372]  [<f88ea632>] ? intel_opregion_setup+0xa2/0x3e0 [i915]
[    7.264395]  [<f88ea773>] ? intel_opregion_setup+0x1e3/0x3e0 [i915]
[    7.264411]  [<f8885521>] ? i915_driver_load+0x5e1/0xed0 [i915]
[    7.264418]  [<f86f4873>] ? drm_dev_register+0x83/0x1a0 [drm]
[    7.264423]  [<f86f6209>] ? drm_get_pci_dev+0x79/0x120 [drm]
[    7.264427]  [<c119ef03>] ? sysfs_do_create_link_sd.isra.2+0xa3/0x1a0
[    7.264430]  [<c1245f55>] ? pci_device_probe+0x65/0xc0
[    7.264434]  [<c12f2180>] ? __device_attach+0x30/0x30
[    7.264436]  [<c119f01d>] ? sysfs_create_link+0x1d/0x40
[    7.264438]  [<c12f2180>] ? __device_attach+0x30/0x30
[    7.264440]  [<c12f1fc4>] ? driver_probe_device+0x54/0x1e0
[    7.264443]  [<c1245e2f>] ? pci_match_device+0xf/0xa0
[    7.264445]  [<c12f21f1>] ? __driver_attach+0x71/0x80
[    7.264447]  [<c12f092f>] ? bus_for_each_dev+0x3f/0x70
[    7.264450]  [<c12f1bc6>] ? driver_attach+0x16/0x20
[    7.264452]  [<c12f2180>] ? __device_attach+0x30/0x30
[    7.264454]  [<c12f18bf>] ? bus_add_driver+0x12f/0x1e0
[    7.264456]  [<c12f2701>] ? driver_register+0x51/0xd0
[    7.264459]  [<f869e000>] ? 0xf869dfff
[    7.264461]  [<f869e000>] ? 0xf869dfff
[    7.264464]  [<c100213a>] ? do_one_initcall+0xea/0x150
[    7.264467]  [<c1045fb8>] ? set_memory_nx+0x58/0x60
[    7.264471]  [<c10ae11b>] ? load_module+0x188b/0x20e0
[    7.264475]  [<c10aea6c>] ? SyS_finit_module+0x5c/0x70
[    7.264480]  [<c1416fcd>] ? sysenter_do_call+0x12/0x28
[    7.264482] ---[ end trace e25d8a9df656de1c ]---
Top
GeneC

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

wayne128 wrote:Gene, GregE , etc

I read your d-u..on systemd.
.........

After d-u, reboot, seems no issue at this installation.
perhaps it is because I do not have systemd..
Hi Wayne.. :)

Yep. Mine runs fine with sysvinit, and no systemd and full DU. Thing is Debian SID WANTS to run systemd and remove sysvinit. I'd be happy to keep running sysvinit, but its to be abandoned by Debian in the near future, so want to get systemd running.

About to try again...

One question. Since systemd now removes sysvinit. Is modifying the /etc/default/grub with

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="init=/bin/systemd"
still necessary? (I would think not, because sysvinit is now removed)?
Top
autocrosser

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

GeneC wrote:
One question. Since systemd now removes sysvinit. Is modifying the /etc/default/grub with

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="init=/bin/systemd"
still necessary? (I would think not, because sysvinit is now removed)?
Hi Gene---

Won't hurt to use it..."Shouldn't" be necessary, but error on the safe side.....
Top
wayne128

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

Gene,

I went ahead to install systemd :lol: :mrgreen:

it installed libpam-systemd systemd-sysv and systemd-ui

No, I did not add init=/bin/systemd

the line on my /etc/default/grub is as highlighted in red below.
wayne@hp8000:~$ cat /etc/grub/default
cat: /etc/grub/default: No such file or directory
wayne@hp8000:~$ cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_enforce_resources=lax"
GRUB_CMDLINE_LINUX="initrd=/install/initrd.gz"

Reboot, hey.. i am typing this post ..

Code: Select all

wayne@hp8000:~$ apt-cache policy systemd systemd-sysv
systemd:
  Installed: 204-10
  Candidate: 204-10
  Version table:
 *** 204-10 0
        500 http://ftp.jp.debian.org/debian/ sid/main i386 Packages
        100 /var/lib/dpkg/status
systemd-sysv:
  Installed: 204-10
  Candidate: 204-10
  Version table:
 *** 204-10 0
        500 http://ftp.jp.debian.org/debian/ sid/main i386 Packages
        100 /var/lib/dpkg/status
wayne@hp8000:~$ uname -a
Linux hp8000 3.13-1-686-pae #1 SMP Debian 3.13.10-1 (2014-04-15) i686 GNU/Linux
wayne@hp8000:~$
Top
wayne128

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

I don't understand any systemd :oops:

so I just copy the dmesg | grep systemd here..
may be someone who is knowledgeable can explain

Code: Select all

wayne@hp8000:~$ dmesg | grep systemd
[    1.004437] systemd-udevd[68]: starting version 204
[    4.152314] systemd[1]: RTC configured in localtime, applying delta of 480 minutes to system time.
[    4.203155] systemd[1]: systemd 204 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[    4.380574] systemd[1]: Inserted module 'autofs4'
[    4.397679] systemd[1]: Set hostname to <hp8000>.
[    5.277664] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
[    5.277842] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    5.277896] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    5.277909] systemd[1]: Starting Remote File Systems (Pre).
[    5.277919] systemd[1]: Reached target Remote File Systems (Pre).
[    5.277929] systemd[1]: Starting Syslog Socket.
[    5.277959] systemd[1]: Listening on Syslog Socket.
[    5.277970] systemd[1]: Starting Delayed Shutdown Socket.
[    5.277988] systemd[1]: Listening on Delayed Shutdown Socket.
[    5.277997] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    5.278017] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    5.278028] systemd[1]: Starting Encrypted Volumes.
[    5.278037] systemd[1]: Reached target Encrypted Volumes.
[    5.278090] systemd[1]: Starting udev Kernel Socket.
[    5.278107] systemd[1]: Listening on udev Kernel Socket.
[    5.278149] systemd[1]: Starting udev Control Socket.
[    5.278172] systemd[1]: Listening on udev Control Socket.
[    5.278201] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[    5.278280] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    5.278292] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[    5.278320] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    5.278332] systemd[1]: Starting Journal Socket.
[    5.278366] systemd[1]: Listening on Journal Socket.
[    5.278380] systemd[1]: Starting LSB: live-config - System Configuration Components...
[    5.278753] systemd[1]: Starting Syslog.
[    5.278764] systemd[1]: Reached target Syslog.
[    5.322086] systemd[1]: Starting Load Kernel Modules...
[    5.322468] systemd[1]: Mounting Debug File System...
[    5.322811] systemd[1]: Starting udev Coldplug all Devices...
[    5.323148] systemd[1]: Starting Journal Service...
[    5.323534] systemd[1]: Started Journal Service.
[    5.323722] systemd[1]: Mounting POSIX Message Queue File System...
[    5.324092] systemd[1]: Mounting Huge Pages File System...
[    5.359686] systemd[1]: Started Set Up Additional Binary Formats.
[    5.359758] systemd[1]: Starting Create static device nodes in /dev...
[    5.380767] systemd[1]: Starting Apply Kernel Variables...
[    5.381158] systemd[1]: Starting File System Check on Root Device...
[    6.156976] systemd-udevd[173]: starting version 204
[    8.725525] CPU: 3 PID: 218 Comm: systemd-udevd Tainted: G           O 3.13-1-686-pae #1 Debian 3.13.10-1
wayne@hp8000:~$
Top
autocrosser

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

Hmmm---

Mine is almost stock--running SSDs so it looks like:

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash elevator=deadline"
GRUB_CMDLINE_LINUX=""

Information on SystemD config:
systemd-ebook-psankar.pdf.tar.gz
More good information: http://www.dedoimedo.com/computers/systemd-blame.html
Last edited by autocrosser on Mon Apr 28, 2014 10:21 am, edited 2 times in total.
Top
wayne128

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

I don't understand any systemd :oops:

so I just copy the dmesg | grep systemd here..
may be someone who is knowledgeable can explain

Code: Select all

wayne@hp8000:~$ dmesg | grep systemd
[    1.004437] systemd-udevd[68]: starting version 204
[    4.152314] systemd[1]: RTC configured in localtime, applying delta of 480 minutes to system time.
[    4.203155] systemd[1]: systemd 204 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[    4.380574] systemd[1]: Inserted module 'autofs4'
[    4.397679] systemd[1]: Set hostname to <hp8000>.
[    5.277664] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
[    5.277842] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    5.277896] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    5.277909] systemd[1]: Starting Remote File Systems (Pre).
[    5.277919] systemd[1]: Reached target Remote File Systems (Pre).
[    5.277929] systemd[1]: Starting Syslog Socket.
[    5.277959] systemd[1]: Listening on Syslog Socket.
[    5.277970] systemd[1]: Starting Delayed Shutdown Socket.
[    5.277988] systemd[1]: Listening on Delayed Shutdown Socket.
[    5.277997] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    5.278017] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    5.278028] systemd[1]: Starting Encrypted Volumes.
[    5.278037] systemd[1]: Reached target Encrypted Volumes.
[    5.278090] systemd[1]: Starting udev Kernel Socket.
[    5.278107] systemd[1]: Listening on udev Kernel Socket.
[    5.278149] systemd[1]: Starting udev Control Socket.
[    5.278172] systemd[1]: Listening on udev Control Socket.
[    5.278201] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[    5.278280] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    5.278292] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[    5.278320] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    5.278332] systemd[1]: Starting Journal Socket.
[    5.278366] systemd[1]: Listening on Journal Socket.
[    5.278380] systemd[1]: Starting LSB: live-config - System Configuration Components...
[    5.278753] systemd[1]: Starting Syslog.
[    5.278764] systemd[1]: Reached target Syslog.
[    5.322086] systemd[1]: Starting Load Kernel Modules...
[    5.322468] systemd[1]: Mounting Debug File System...
[    5.322811] systemd[1]: Starting udev Coldplug all Devices...
[    5.323148] systemd[1]: Starting Journal Service...
[    5.323534] systemd[1]: Started Journal Service.
[    5.323722] systemd[1]: Mounting POSIX Message Queue File System...
[    5.324092] systemd[1]: Mounting Huge Pages File System...
[    5.359686] systemd[1]: Started Set Up Additional Binary Formats.
[    5.359758] systemd[1]: Starting Create static device nodes in /dev...
[    5.380767] systemd[1]: Starting Apply Kernel Variables...
[    5.381158] systemd[1]: Starting File System Check on Root Device...
[    6.156976] systemd-udevd[173]: starting version 204
[    8.725525] CPU: 3 PID: 218 Comm: systemd-udevd Tainted: G           O 3.13-1-686-pae #1 Debian 3.13.10-1
wayne@hp8000:~$
and.. boot time, per dmesg record,
has ''''??-improved''' from old 17 seconds to now 23 seconds :twisted:
wayne@hp8000:~$ dmesg | tail
[ 12.075000] FS-Cache: Netfs 'nfs' registered for caching
[ 12.138795] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 15.035638] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input16
[ 15.748202] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[ 15.852079] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[ 15.852201] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 20.456106] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[ 20.459041] e1000e 0000:00:19.0 eth0: MAC Wakeup cause - Unicast Packet
[ 22.828882] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 22.829016] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
wayne@hp8000:~$
Top
wayne128

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

autocrosser wrote:
Information on SystemD config:
systemd-ebook-psankar.pdf.tar.gz
More good information: http://www.dedoimedo.com/computers/systemd-blame.html

thanks autocrosser for the link

I captured some as described by dedoimedo

haha, even have the systemd-analyze blame command :lol:

now the boot time is so much longer :evil:

Code: Select all

wayne@hp8000:~$ systemd-analyze
Startup finished in 3.892s (kernel) + 22.577s (userspace) = 26.469s

wayne@hp8000:~$ systemd-analyze blame
         12.952s nmbd.service
         12.345s samba-ad-dc.service
         10.083s acpi-support.service
          6.223s ModemManager.service
          4.742s exim4.service
          4.281s bootlogs.service
          4.174s avahi-daemon.service
          3.761s systemd-logind.service
          3.124s keyboard-setup.service
          2.663s acpi-fakekey.service
          2.517s networking.service
          2.198s console-screen.service
          1.789s systemd-modules-load.service
          1.595s live-config.service
          1.538s cron.service
           995ms polkitd.service
           964ms rsyslog.service
           940ms hdparm.service
           881ms sys-kernel-debug.mount
           879ms dev-mqueue.mount
           868ms dev-hugepages.mount
           815ms systemd-tmpfiles-setup-dev.service
           712ms lm-sensors.service
           601ms systemd-udev-trigger.service
           505ms udisks2.service
           482ms systemd-tmpfiles-setup.service
           474ms saned.service
           470ms systemd-fsck-root.service
           449ms systemd-update-utmp-runlevel.service
           435ms alsa-restore.service
           435ms console-kit-log-system-start.service
           433ms systemd-sysctl.service
           429ms smbd.service
           417ms smartmontools.service
           417ms motd.service
           417ms nfs-common.service
           416ms glances.service
           400ms lightdm.service
           391ms swapfile.swap
           327ms systemd-user-sessions.service
           280ms minissdpd.service
           279ms console-setup.service
           272ms systemd-udevd.service
           251ms udev-finish.service
           139ms rpcbind.service
           105ms systemd-random-seed-load.service
           105ms hddtemp.service
           102ms console-kit-daemon.service
            71ms upower.service
            55ms pppd-dns.service
            44ms rc-local.service
            35ms systemd-remount-fs.service
             3ms live-tools.service
             3ms systemd-journal-flush.
Last edited by wayne128 on Mon Apr 28, 2014 10:51 am, edited 1 time in total.
Top
Locked

Return to “LMDE Archive”