LMDE Breakages (Tracking SID)

Archived topics about LMDE 1 and LMDE 2
Locked
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

Well--Here's what my "normal" one looks like (bear in mind that I just upgraded to version 208):

Code: Select all

dean@linux:~$ dmesg | grep systemd
[    0.588904] systemd-udevd[90]: starting version 208
[    0.589140] random: systemd-udevd urandom read with 2 bits of entropy available
[    2.271963] systemd[1]: systemd 208 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[    2.282987] systemd[1]: Inserted module 'autofs4'
[    2.283260] systemd[1]: Set hostname to <linux>.
[    2.368796] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[    2.369103] systemd[1]: Starting Syslog Socket.
[    2.369174] systemd[1]: Listening on Syslog Socket.
[    2.369190] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    2.369244] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.369254] systemd[1]: Starting Remote File Systems (Pre).
[    2.369288] systemd[1]: Reached target Remote File Systems (Pre).
[    2.369298] systemd[1]: Starting Delayed Shutdown Socket.
[    2.369343] systemd[1]: Listening on Delayed Shutdown Socket.
[    2.369353] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    2.369395] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    2.369409] systemd[1]: Starting udev Kernel Socket.
[    2.369450] systemd[1]: Listening on udev Kernel Socket.
[    2.369462] systemd[1]: Starting udev Control Socket.
[    2.369502] systemd[1]: Listening on udev Control Socket.
[    2.369528] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[    2.369624] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    2.369638] systemd[1]: Starting Journal Socket.
[    2.369696] systemd[1]: Listening on Journal Socket.
[    2.369712] systemd[1]: Starting Syslog.
[    2.369743] systemd[1]: Reached target Syslog.
[    2.369813] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[    2.370192] systemd[1]: Mounting Debug File System...
[    2.370498] systemd[1]: Mounting Huge Pages File System...
[    2.378047] systemd[1]: Starting Load Kernel Modules...
[    2.378436] systemd[1]: Mounting POSIX Message Queue File System...
[    2.378748] systemd[1]: Starting udev Coldplug all Devices...
[    2.379150] systemd[1]: Starting Journal Service...
[    2.379679] systemd[1]: Started Journal Service.
[    2.389961] systemd-journald[217]: Vacuuming done, freed 0 bytes
[    2.449995] systemd-udevd[247]: starting version 208
[    2.544122] systemd-udevd[289]: renamed network interface eth0 to eth1
[    3.187508] systemd-journald[217]: Received request to flush runtime journal from PID 1
Take a look at the link I posted--he breaks SystemD down to easy to "digest" bits :)
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
GeneC
Level 7
Level 7
Posts: 1598
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

Try #2
Still not working.

================
  • 1. Install systemd (I know the gui is not necessary)

    Code: Select all

    gene@Debian-SID:~$ sudo apt-get install systemd libpam-systemd systemd-gui systemd-sysv
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    The following extra packages will be installed:
      systemd-ui
    The following packages will be REMOVED:
      sysvinit-core
    The following NEW packages will be installed:
      libpam-systemd systemd systemd-gui systemd-sysv systemd-ui
    0 upgraded, 5 newly installed, 1 to remove and 1 not upgraded.
    Need to get 1,246 kB of archives.
    After this operation, 5,277 kB of additional disk space will be used.
    Do you want to continue? [Y/n] y
    2.
    Make sure you have removed cron or anacron & install systemd-cron
    DONE

    3. Edit /etc/default/grub (probably not necessary, as Autocrosser pointed out)

    Code: Select all

    GRUB_CMDLINE_LINUX_DEFAULT="init=/bin/systemd"
    and

    Code: Select all

    sudo update-grub
    4. Re-boot
    To no Gui, but command line.
    • a. logged in
      b. ran 'startx' = Fatal Server Error: (EE) Could not create a lock file in /tmp/.txo-lock
      xinit: server error
      c. ran /usr/bin/xfce4-session = 'Cannot open display"
    5.
    Get your syslog & post it --look for anything "weird"
    (This SID install is sda2=Debian-SID. I have a triple boot on this box.)
    download syslog (its large)-- :arrow:
    http://www.mediafire.com/view/02qu95w7bgv9tfz/syslog
Last edited by GeneC on Mon Apr 28, 2014 10:59 am, edited 1 time in total.
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

We posted at the same time ;) Now to trim boot time you need to look at services that are high on the blame list & see if you can clean-up/trim/remove them.....I've not cleaned mine up due to the changes in versions, but as soon as it stabilizes....I'm heading there....


I've got revised cron target scripts available. Debian uses a old version of systemd-cron, so I went upstream & got the latest version....I'll tar the files if you want them...
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

Hey Gene---

Copy your current boot.log for the dead system & post it...I'm seeing no mention of systemd in your syslog.....just normal old-style sysvinit info???
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
GeneC
Level 7
Level 7
Posts: 1598
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

^ I could not make our much from syslog

boot.log

Code: Select all

Scanning for Btrfs filesystems

INIT: version 2.88 booting

[[36minfo[39;49m] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Synthesizing the initial hotplug events...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Waiting for /dev to be fully populated...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Setting preliminary keymap...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Setting parameters of disc: (none)[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Activating swap...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Activating lvm and md swap...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Checking file systems...fsck from util-linux 2.20.1
[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Cleaning up temporary files... /tmp[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[[36minfo[39;49m] Loading kernel module lp.
[[36minfo[39;49m] Loading kernel module ppdev.
[[36minfo[39;49m] Loading kernel module parport_pc.
[[36minfo[39;49m] Loading kernel module fuse.
[....] Mounting local filesystems...mount: mount point /media/gene/Deb-Compiz does not exist
[?25l[?1c7[1G[[31mFAIL[39;49m8[?25h[?0c[31mfailed.[39;49m
[....] Activating swapfile swap...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Cleaning up temporary files...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Setting kernel variables ...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Setting up resolvconf...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Starting firewall: ufw...Setting kernel variables (/etc/ufw/sysctl.conf)...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Configuring network interfaces...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Starting rpcbind daemon...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting NFS common utilities: statd idmapd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Cleaning up temporary files...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Setting up ALSA...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[[36minfo[39;49m] Setting console screen modes and fonts.
]R[9;30][14;30][....] Setting up console font and keymap...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Setting sensors limits[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.

INIT: Entering runlevel: 2

[[36minfo[39;49m] Using makefile-style concurrent boot in runlevel 2.
[....] Not starting fancontrol; run pwmconfig first. ...[?25l[?1c7[1G[[33mwarn[39;49m8[?25h[?0c [33m(warning).[39;49m
[....] Starting NFS common utilities: statd idmapd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
Tue Apr  8 16:32:19 2014: Starting hdapsd
Tue Apr  8 16:32:19 2014: Could not find a suitable interface
[....] Enabling additional executable binary formats: binfmt-support[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting enhanced syslogd: rsyslogd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting CUPS Bonjour daemon: cups-browsed[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
Starting printer spooler: lpd.
[....] Starting periodic command scheduler: cron[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting ACPI services...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting anac(h)ronistic cron: anacron[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting NTP server: ntpd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting system message bus: dbus[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Loading cpufreq kernel modules...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone (acpi-cpufreq).
[....] Starting MTA: exim4[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting Common Unix Printing System: cupsd[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting virtual private network daemon:[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] Starting Light Display Manager: lightdm[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
[....] CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU1...CPU2...CPU3...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c.
saned disabled; edit /etc/default/saned
[[36minfo[39;49m] PulseAudio not started: Configured for per-user sessions.
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

Hmmm....I'm not seeing anything that would indicate that you have systemd running....My last boot.log looks like:

Code: Select all

Welcome to Linux Mint LMDE

[ OK ] Listening on Syslog Socket.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on udev Control Socket.
[ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[ OK ] Listening on Journal Socket.
[ OK ] Reached target Syslog.
         Starting Create list of required static device nodes...rrent kernel...
         Mounting Debug File System...
         Mounting Huge Pages File System...
         Starting Load Kernel Modules...
         Mounting POSIX Message Queue File System...
         Starting udev Coldplug all Devices...
         Starting Journal Service...
[ OK  ] Started Journal Service.
[ OK  ] Reached target Encrypted Volumes.
         Starting Apply Kernel Variables...
         Expecting device dev-disk-by\x2duuid-96a36798\x2d9c4...90854.device...
         Starting File System Check on Root Device...
         Expecting device dev-disk-by\x2duuid-083a8b7a\x2d334...8eb80.device...
         Expecting device dev-disk-by\x2duuid-92f3ffaa\x2d19b...c3bc6.device...
         Expecting device dev-disk-by\x2duuid-0eba7eb5\x2da57...b1b16.device...
         Expecting device dev-disk-by\x2duuid-1e6c9958\x2dcc1...4ca21.device...
[ OK  ] Set up automount home.automount.
[ OK  ] Set up automount mnt-MintEX2.automount.
[ OK  ] Set up automount mnt-MintEX2home.automount.
         Expecting device dev-disk-by\x2duuid-7d134d4b\x2d020...62bab.device...
         Expecting device dev-disk-by\x2duuid-d27ad08b\x2d78b...a9836.device...
[ OK  ] Set up automount media-Storage.automount.
[ OK  ] Created slice Root Slice.
[ OK  ] Created slice User and Session Slice.
[ OK  ] Created slice System Slice.
[ OK  ] Created slice system-getty.slice.
[ OK  ] Reached target Slices.
[ OK  ] Mounted Debug File System.
[ OK  ] Mounted Huge Pages File System.
[ OK  ] Mounted POSIX Message Queue File System.
[ OK  ] Started Apply Kernel Variables.
[ OK  ] Started Create list of required static device nodes ...current kernel.
         Starting Create static device nodes in /dev...
[ OK  ] Started Load Kernel Modules.
         Mounting FUSE Control File System...
[ OK  ] Started udev Coldplug all Devices.
         Starting Show Plymouth Boot Screen...
[ OK  ] Mounted FUSE Control File System.
[ OK  ] Started Create static device nodes in /dev.
         Starting udev Kernel Device Manager...
[ OK  ] Started udev Kernel Device Manager.
         Starting LSB: Set preliminary keymap...
         Starting LSB: Tune IDE hard disks...
         Starting Copy rules generated while the root was ro...
[ OK  ] Started Copy rules generated while the root was ro.
systemd-fsck[225]: /dev/sdb1: clean, 361424/4481024 files, 6300476/17920000 blocks
[ OK  ] Started File System Check on Root Device.
[ OK  ] Started LSB: Tune IDE hard disks.
[ OK  ] Started LSB: Set preliminary keymap.
         Starting Remount Root and Kernel File Systems...
[ OK  ] Started Remount Root and Kernel File Systems.
         Starting Load/Save Random Seed...
[ OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
         Mounting User Runtime Directory...
         Mounting Lock Directory...
[ OK  ] Mounted User Runtime Directory.
[ OK  ] Mounted /tmp.
[ OK  ] Mounted Lock Directory.
[ OK  ] Started Load/Save Random Seed.
[ OK  ] Created slice system-ifup.slice.
[ OK  ] Found device SAMSUNG_HD103SJ.
         Activating swap /dev/disk/by-uuid/96a36798-9c4b-4c48...f7d951a90854...
[ OK  ] Found device SAMSUNG_HD103SJ.
         Starting File System Check on /dev/disk/by-uuid/d27a...5a2a32da9836...
[ OK  ] Found device SAMSUNG_HD103SJ.
         Starting File System Check on /dev/disk/by-uuid/7d13...66479c862bab...
[ OK  ] Activated swap /dev/disk/by-uuid/96a36798-9c4b-4c48-b5a6-f7d951a90854.
[ OK  ] Reached target Swap.
[ OK  ] Found device SAMSUNG_HD103SJ.
         Starting File System Check on /dev/disk/by-uuid/1e6c...e1b8cc94ca21...
[ OK  ] Found device OCZ-VERTEX3_MI.
         Starting File System Check on /dev/disk/by-uuid/0eba...098196cb1b16...
[ OK  ] Found device OCZ-VERTEX3_MI.
         Starting File System Check on /dev/disk/by-uuid/92f3...eeacfb1c3bc6...
[ OK  ] Found device Samsung_SSD_840_EVO_250GB.
         Starting File System Check on /dev/disk/by-uuid/083a...2fc914e8eb80...
systemd-fsck[542]: /dev/sdc2: clean, 164991/11378688 files, 19298944/45500160 blocks (check in 3 mounts)
systemd-fsck[544]: /dev/sdc1: clean, 365454/3276800 files, 5961600/13107200 blocks (check in 3 mounts)
[ OK  ] Started File System Check on /dev/disk/by-uuid/92f3f...f-eeacfb1c3bc6.
         Mounting /mnt/MintEX2...
[ OK  ] Started File System Check on /dev/disk/by-uuid/0eba7...a-098196cb1b16.
         Mounting /mnt/MintEX2home...
[ OK  ] Mounted /mnt/MintEX2.
[ OK  ] Mounted /mnt/MintEX2home.
systemd-fsck[514]: /dev/sda1: recovering journal
systemd-fsck[514]: /dev/sda1: clean, 244760/5120000 files, 5038889/20480000 blocks
[ OK  ] Started File System Check on /dev/disk/by-uuid/7d134...4-66479c862bab.
         Mounting /mnt/Mint16...
systemd-fsck[522]: Storage: clean, 147127/29949952 files, 42279862/119775488 blocks
[ OK  ] Started File System Check on /dev/disk/by-uuid/1e6c9...0-e1b8cc94ca21.
         Mounting /media/Storage...
[ OK  ] Mounted /mnt/Mint16.
systemd-fsck[501]: /dev/sda4: recovering journal
systemd-fsck[501]: /dev/sda4: clean, 1082568/24829952 files, 21971457/99295232 blocks
[ OK  ] Started File System Check on /dev/disk/by-uuid/d27ad...5-5a2a32da9836.
         Mounting /mnt/Mint16home...
[ OK  ] Mounted /media/Storage.
systemd-fsck[556]: /dev/sdb2: recovering journal
[ OK  ] Mounted /mnt/Mint16home.
[ OK  ] Reached target Local File Systems.
         Starting LSB: Raise network interfaces....
         Starting Recreate Volatile Files and Directories...
         Starting Tell Plymouth To Write Out Runtime Data...
[ OK  ] Reached target Remote File Systems.
         Starting LSB: Prepare console...
         Starting Trigger Flushing of Journal to Persistent Storage...
[ OK  ] Started Trigger Flushing of Journal to Persistent Storage.
[ OK  ] Started Recreate Volatile Files and Directories.
         Starting Update UTMP about System Reboot/Shutdown...
[ OK  ] Started Update UTMP about System Reboot/Shutdown.
[ OK  ] Started Tell Plymouth To Write Out Runtime Data.
[ OK  ] Started LSB: Prepare console.
         Starting LSB: Set console font and keymap...
[ OK  ] Started LSB: Raise network interfaces..
[ OK  ] Reached target Network.
         Starting LSB: RPC portmapper replacement...
[ OK  ] Reached target Host and Network Name Lookups.
[ OK  ] Started LSB: Set console font and keymap.
[ OK  ] Started LSB: RPC portmapper replacement.
[ OK  ] Reached target RPC Port Mapper.
         Starting LSB: NFS support files common to client and server...
systemd-fsck[556]: /dev/sdb2: clean, 157207/10788864 files, 14850204/43129344 blocks
[ OK  ] Started File System Check on /dev/disk/by-uuid/083a8...9-2fc914e8eb80.
         Mounting /home...
[ OK  ] Mounted /home.
[ OK  ] Started LSB: NFS support files common to client and server.
[ OK  ] Reached target System Initialization.
[ OK  ] Listening on ACPID Listen Socket.
[ OK  ] Listening on CUPS Printing Service Sockets.
[ OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK  ] Reached target systemd-cron.
[ OK  ] Listening on D-Bus System Message Bus Socket.
[ OK  ] Reached target Sockets.
[ OK  ] Reached target Timers.
         Starting Restore Sound Card State...
         Starting Console System Startup Logging...
[ OK  ] Started Console System Startup Logging.
[ OK  ] Started Restore Sound Card State.
[ OK  ] Reached target Sound Card.
[ OK  ] Started Show Plymouth Boot Screen.
[ OK  ] Reached target Paths.
[ OK  ] Reached target Basic System.
         Starting Bluetooth service...
         Starting ifup for eth1...
[ OK  ] Started ifup for eth1.
         Starting LSB: start Samba NetBIOS nameserver (nmbd)...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting LSB: start Samba daemons for the AD DC...
         Starting LSB: keep memory of all UPnP devices that a...d themselves...
         Starting LSB: Apache2 web server...
         Starting Deferred execution scheduler...
[ OK  ] Started Deferred execution scheduler.
         Starting CUPS Printing Service...
[ OK  ] Started CUPS Printing Service.
         Starting LSB: disk temperature monitoring daemon...
         Starting LSB: Start the GNUstep distributed object mapper...
         Starting LSB: Create dynamic part of /etc/motd...
         Starting LSB: SMART monitoring daemon...
         Starting LSB: create NVIDIA device nodes...
         Starting OpenBSD Secure Shell server...
[ OK  ] Started OpenBSD Secure Shell server.
         Starting LSB: Start NTP daemon...
         Starting D-Bus System Message Bus...
[ OK  ] Started D-Bus System Message Bus.
         Starting LSB: SANE network scanner server...
         Starting Enable support for additional executable binary formats...
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
         Starting Initialize hardware monitoring sensors...
         Starting System Logging Service...
         Starting Network Manager...
         Starting /etc/rc.local Compatibility...
         Starting Login Service...
         Starting Permit User Sessions...
         Starting Accounts Service...
[ OK  ] Started LSB: Create dynamic part of /etc/motd.
[ OK  ] Started LSB: SMART monitoring daemon.
[ OK  ] Started /etc/rc.local Compatibility.
[ OK  ] Started LSB: Start the GNUstep distributed object mapper.
[ OK  ] Started LSB: keep memory of all UPnP devices that an...ced themselves.
[ OK  ] Started LSB: SANE network scanner server.
[ OK  ] Started Permit User Sessions.
         Starting Terminate Plymouth Boot Screen...
         Starting Wait for Plymouth Boot Screen to Quit...
[ OK  ] Started LSB: create NVIDIA device nodes.
         Mounting Arbitrary Executable File Formats File System...
[ OK  ] Mounted Arbitrary Executable File Formats File System.
[ OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
GeneC
Level 7
Level 7
Posts: 1598
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

Hey AC.. thanks for the help. I am stumped for now. I know systemd runs on this box, as I had Manjaro running with systemd. I am going to revert to the last clone with systemv init and tackle this again later. It appears I am the only one here with this issue, so its probably particular to me and this setup..

Really appreciate the help.. :wink:
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

No Prob Gene---

I'm not sure why your system is not running it...might be links that got left for some reason...

After you revert, you might use Synaptic to do the update & then see if there is any residual configs left behind....There have been times I have gone in & manually cleaned my house....;)
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
kurotsugi
Level 6
Level 6
Posts: 1026
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID)

Post by kurotsugi »

@GeneC: based on your explanation there might be something wrong with X. I have systemd on my system for months and everything is just fine. the easiest way to tell if you're running systemd is by 'systemd-analyze' command. on most cases systemd-gui isn't needed. in case if init=/bin/systemd didn't work we can use init=/lib/systemd/systemd.

@wayne: on my experience, samba didn't work well with systemd and makes the boot a lot longer.

Code: Select all

wayne@hp8000:~$ systemd-analyze blame
         12.952s nmbd.service
         12.345s samba-ad-dc.service
you can run 'systemd-analyze critical-chain' to know which service stalling your boot. after that, you can disable it if you didn't need it. as for dmesg report, it tell everything happened with systemd and didn't mean that systemd is broken. you can filter what dmesg said with |grep fail or |grep error.
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

kurotsugi wrote:@GeneC: based on your explanation there might be something wrong with X. I have systemd on my system for months and everything is just fine. the easiest way to tell if you're running systemd is by 'systemd-analyze' command. on most cases systemd-gui isn't needed. in case if init=/bin/systemd didn't work we can use init=/lib/systemd/systemd.

@wayne: on my experience, samba didn't work well with systemd and makes the boot a lot longer.

Code: Select all

wayne@hp8000:~$ systemd-analyze blame
         12.952s nmbd.service
         12.345s samba-ad-dc.service
you can run 'systemd-analyze critical-chain' to know which service stalling your boot. after that, you can disable it if you didn't need it. as for dmesg report, it tell everything happened with systemd and didn't mean that systemd is broken. you can filter what dmesg said with |grep fail or |grep error.
Thank You for coming in....the more eyes--the better....

The other service I see that I bet is not needed: 6.223s ModemManager.service
Unless you are using Dialup or equivalent--that one is not needed...

My startup looks like:

Code: Select all

systemd-analyze blame
          2.967s plymouth-start.service
          1.202s apache2.service
           684ms hddtemp.service
           499ms nmbd.service
           467ms samba-ad-dc.service
           387ms systemd-fsck@dev-disk-by\x2duuid-1e6c9958\x2dcc1c\x2d4fd0\x2db9
           235ms systemd-fsck@dev-disk-by\x2duuid-7d134d4b\x2d020c\x2d4c69\x2da8
           227ms NetworkManager.service
           205ms accounts-daemon.service
           156ms systemd-fsck@dev-disk-by\x2duuid-92f3ffaa\x2d19b8\x2d4006\x2d8a
           155ms systemd-fsck@dev-disk-by\x2duuid-0eba7eb5\x2da57a\x2d402d\x2da9
           153ms mnt-Mint16.mount
           147ms systemd-fsck@dev-disk-by\x2duuid-083a8b7a\x2d334c\x2d4567\x2dbb
           138ms bluetooth.service
           136ms systemd-fsck@dev-disk-by\x2duuid-d27ad08b\x2d78b4\x2d44de\x2da9
           136ms avahi-daemon.service
           125ms systemd-logind.service
           116ms smbd.service
            95ms keyboard-setup.service
            85ms systemd-fsck-root.service
            76ms media-Storage.mount
            71ms console-setup.service
            66ms alsa-restore.service
            65ms polkit.service
            65ms networking.service
            60ms udisks2.service
            55ms systemd-udev-trigger.service
            55ms ntp.service
            54ms kmod-static-nodes.service
            53ms nfs-common.service
            52ms systemd-modules-load.service
            52ms sys-kernel-debug.mount
            52ms dev-hugepages.mount
            51ms rsyslog.service
            45ms dev-mqueue.mount
            43ms systemd-sysctl.service
            41ms hdparm.service
            35ms systemd-tmpfiles-clean.service
            33ms binfmt-support.service
            30ms colord.service
            28ms lm-sensors.service
            26ms bootlogs.service
            26ms rpcbind.service
            26ms plymouth-quit.service
            25ms plymouth-quit-wait.service
            24ms sysfsutils.service
            23ms console-kit-daemon.service
            21ms minissdpd.service
            19ms kbd.service
            18ms nvidia-kernel.service
            17ms gdomap.service
            16ms user@1001.service
            12ms systemd-tmpfiles-setup-dev.service
            12ms gdm3.service
            11ms mnt-Mint16home.mount
            11ms plymouth-read-write.service
            10ms systemd-random-seed.service
            10ms console-kit-log-system-start.service
            10ms motd.service
             9ms smartmontools.service
             8ms systemd-user-sessions.service
             8ms user@113.service
             7ms saned.service
             7ms upower.service
             6ms rc-local.service
             6ms home.mount
             5ms rtkit-daemon.service
             5ms proc-sys-fs-binfmt_misc.mount
             5ms systemd-remount-fs.service
             4ms mnt-MintEX2home.mount
             4ms dev-disk-by\x2duuid-96a36798\x2d9c4b\x2d4c48\x2db5a6\x2df7d951a
             4ms systemd-tmpfiles-setup.service
             3ms mnt-MintEX2.mount
             2ms tmp.mount
             2ms pulseaudio.service
             2ms run-lock.mount
             2ms run-user.mount
             1ms systemd-udevd.service
             1ms systemd-update-utmp.service
             1ms systemd-journal-flush.service
             1ms sys-fs-fuse-connections.mount
             1ms systemd-update-utmp-runlevel.service
             1ms udev-finish.service
Thats with config files cleaned up a bit. Total startup time looks like:

Code: Select all

systemd-analyze
Startup finished in 1.781s (kernel) + 13.388s (userspace) = 15.170s
And my Critical Chain:

Code: Select all

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 @13.386s
└─multi-user.target @13.386s
  └─ssh.service @9.504s
    └─basic.target @3.138s
      └─systemd-ask-password-plymouth.path @3.138s
        └─-.mount @105ms
          └─system.slice @156ms
            └─-.slice @155ms
So, even with loading quite a bit you can get a fairly quick bootup.....
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
kurotsugi
Level 6
Level 6
Posts: 1026
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID)

Post by kurotsugi »

I wonder what you did you the samba config files :3
AFAIK modem manager is needed for usb gsm connection. i keep it running because it never stall my boot process and didn't affect the boot time

Code: Select all

graphical.target @13.564s
└─multi-user.target @13.563s
  └─pulseaudio.service @13.554s +9ms
    └─NetworkManager.service @11.054s +2.497s
      └─basic.target @11.003s
        └─sockets.target @11.003s
          └─dbus.socket @11.003s
            └─sysinit.target @10.958s
              └─rpcbind.service @10.729s +228ms
                └─network.target @10.728s
                  └─networking.service @9.558s +1.169s
                    └─local-fs.target @9.555s
                      └─run-rpc_pipefs.mount @11.872s
                        └─local-fs-pre.target @4.985s
                          └─systemd-remount-fs.service @4.837s +147ms
                            └─keyboard-setup.service @2.885s +1.937s
                              └─systemd-udevd.service @2.579s +303ms
                                └─systemd-tmpfiles-setup-dev.service @1.631s +947ms
                                  └─systemd-journald.socket @1.627s
                                    └─-.mount @1.625s
systemd have paralel service activation so that disable a service didn't always means you'll get faster boot time. on 'systemd-analyze critical-chain' you only need to watch the red coloured ones.
GeneBenson
Level 4
Level 4
Posts: 352
Joined: Fri Sep 17, 2010 9:55 pm

Re: LMDE Breakages (Tracking SID)

Post by GeneBenson »

Hi autocrosser,

I am curious as to how you got that output in boot.log. Did you modify a setting in journald.conf? Do you have bootlogd installed?
autocrosser wrote:Hmmm....I'm not seeing anything that would indicate that you have systemd running....My last boot.log looks like:

Code: Select all

Welcome to Linux Mint LMDE

[ OK ] Listening on Syslog Socket.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on udev Control Socket.
[ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[ OK ] Listening on Journal Socket.
[ OK ] Reached target Syslog.
         Starting Create list of required static device nodes...rrent kernel...
         Mounting Debug File System...
         Mounting Huge Pages File System...
         Starting Load Kernel Modules...
         Mounting POSIX Message Queue File System...
         Starting udev Coldplug all Devices...
         Starting Journal Service...
[ OK  ] Started Journal Service.
[ OK  ] Reached target Encrypted Volumes.
         Starting Apply Kernel Variables...
         Expecting device dev-disk-by\x2duuid-96a36798\x2d9c4...90854.device...
         Starting File System Check on Root Device...
         Expecting device dev-disk-by\x2duuid-083a8b7a\x2d334...8eb80.device...
         Expecting device dev-disk-by\x2duuid-92f3ffaa\x2d19b...c3bc6.device...
         Expecting device dev-disk-by\x2duuid-0eba7eb5\x2da57...b1b16.device...
         Expecting device dev-disk-by\x2duuid-1e6c9958\x2dcc1...4ca21.device...
[ OK  ] Set up automount home.automount.
[ OK  ] Set up automount mnt-MintEX2.automount.
[ OK  ] Set up automount mnt-MintEX2home.automount.
         Expecting device dev-disk-by\x2duuid-7d134d4b\x2d020...62bab.device...
         Expecting device dev-disk-by\x2duuid-d27ad08b\x2d78b...a9836.device...
[ OK  ] Set up automount media-Storage.automount.
[ OK  ] Created slice Root Slice.
[ OK  ] Created slice User and Session Slice.
[ OK  ] Created slice System Slice.
[ OK  ] Created slice system-getty.slice.
[ OK  ] Reached target Slices.
[ OK  ] Mounted Debug File System.
[ OK  ] Mounted Huge Pages File System.
[ OK  ] Mounted POSIX Message Queue File System.
[ OK  ] Started Apply Kernel Variables.
[ OK  ] Started Create list of required static device nodes ...current kernel.
         Starting Create static device nodes in /dev...
[ OK  ] Started Load Kernel Modules.
         Mounting FUSE Control File System...
[ OK  ] Started udev Coldplug all Devices.
         Starting Show Plymouth Boot Screen...
[ OK  ] Mounted FUSE Control File System.
[ OK  ] Started Create static device nodes in /dev.
         Starting udev Kernel Device Manager...
[ OK  ] Started udev Kernel Device Manager.
         Starting LSB: Set preliminary keymap...
         Starting LSB: Tune IDE hard disks...
         Starting Copy rules generated while the root was ro...
[ OK  ] Started Copy rules generated while the root was ro.
systemd-fsck[225]: /dev/sdb1: clean, 361424/4481024 files, 6300476/17920000 blocks
[ OK  ] Started File System Check on Root Device.
[ OK  ] Started LSB: Tune IDE hard disks.
[ OK  ] Started LSB: Set preliminary keymap.
         Starting Remount Root and Kernel File Systems...
[ OK  ] Started Remount Root and Kernel File Systems.
         Starting Load/Save Random Seed...
[ OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
         Mounting User Runtime Directory...
         Mounting Lock Directory...
[ OK  ] Mounted User Runtime Directory.
[ OK  ] Mounted /tmp.
[ OK  ] Mounted Lock Directory.
[ OK  ] Started Load/Save Random Seed.
[ OK  ] Created slice system-ifup.slice.
[ OK  ] Found device SAMSUNG_HD103SJ.
         Activating swap /dev/disk/by-uuid/96a36798-9c4b-4c48...f7d951a90854...
[ OK  ] Found device SAMSUNG_HD103SJ.
         Starting File System Check on /dev/disk/by-uuid/d27a...5a2a32da9836...
[ OK  ] Found device SAMSUNG_HD103SJ.
         Starting File System Check on /dev/disk/by-uuid/7d13...66479c862bab...
[ OK  ] Activated swap /dev/disk/by-uuid/96a36798-9c4b-4c48-b5a6-f7d951a90854.
[ OK  ] Reached target Swap.
[ OK  ] Found device SAMSUNG_HD103SJ.
         Starting File System Check on /dev/disk/by-uuid/1e6c...e1b8cc94ca21...
[ OK  ] Found device OCZ-VERTEX3_MI.
         Starting File System Check on /dev/disk/by-uuid/0eba...098196cb1b16...
[ OK  ] Found device OCZ-VERTEX3_MI.
         Starting File System Check on /dev/disk/by-uuid/92f3...eeacfb1c3bc6...
[ OK  ] Found device Samsung_SSD_840_EVO_250GB.
         Starting File System Check on /dev/disk/by-uuid/083a...2fc914e8eb80...
systemd-fsck[542]: /dev/sdc2: clean, 164991/11378688 files, 19298944/45500160 blocks (check in 3 mounts)
systemd-fsck[544]: /dev/sdc1: clean, 365454/3276800 files, 5961600/13107200 blocks (check in 3 mounts)
[ OK  ] Started File System Check on /dev/disk/by-uuid/92f3f...f-eeacfb1c3bc6.
         Mounting /mnt/MintEX2...
[ OK  ] Started File System Check on /dev/disk/by-uuid/0eba7...a-098196cb1b16.
         Mounting /mnt/MintEX2home...
[ OK  ] Mounted /mnt/MintEX2.
[ OK  ] Mounted /mnt/MintEX2home.
systemd-fsck[514]: /dev/sda1: recovering journal
systemd-fsck[514]: /dev/sda1: clean, 244760/5120000 files, 5038889/20480000 blocks
[ OK  ] Started File System Check on /dev/disk/by-uuid/7d134...4-66479c862bab.
         Mounting /mnt/Mint16...
systemd-fsck[522]: Storage: clean, 147127/29949952 files, 42279862/119775488 blocks
[ OK  ] Started File System Check on /dev/disk/by-uuid/1e6c9...0-e1b8cc94ca21.
         Mounting /media/Storage...
[ OK  ] Mounted /mnt/Mint16.
systemd-fsck[501]: /dev/sda4: recovering journal
systemd-fsck[501]: /dev/sda4: clean, 1082568/24829952 files, 21971457/99295232 blocks
[ OK  ] Started File System Check on /dev/disk/by-uuid/d27ad...5-5a2a32da9836.
         Mounting /mnt/Mint16home...
[ OK  ] Mounted /media/Storage.
systemd-fsck[556]: /dev/sdb2: recovering journal
[ OK  ] Mounted /mnt/Mint16home.
[ OK  ] Reached target Local File Systems.
         Starting LSB: Raise network interfaces....
         Starting Recreate Volatile Files and Directories...
         Starting Tell Plymouth To Write Out Runtime Data...
[ OK  ] Reached target Remote File Systems.
         Starting LSB: Prepare console...
         Starting Trigger Flushing of Journal to Persistent Storage...
[ OK  ] Started Trigger Flushing of Journal to Persistent Storage.
[ OK  ] Started Recreate Volatile Files and Directories.
         Starting Update UTMP about System Reboot/Shutdown...
[ OK  ] Started Update UTMP about System Reboot/Shutdown.
[ OK  ] Started Tell Plymouth To Write Out Runtime Data.
[ OK  ] Started LSB: Prepare console.
         Starting LSB: Set console font and keymap...
[ OK  ] Started LSB: Raise network interfaces..
[ OK  ] Reached target Network.
         Starting LSB: RPC portmapper replacement...
[ OK  ] Reached target Host and Network Name Lookups.
[ OK  ] Started LSB: Set console font and keymap.
[ OK  ] Started LSB: RPC portmapper replacement.
[ OK  ] Reached target RPC Port Mapper.
         Starting LSB: NFS support files common to client and server...
systemd-fsck[556]: /dev/sdb2: clean, 157207/10788864 files, 14850204/43129344 blocks
[ OK  ] Started File System Check on /dev/disk/by-uuid/083a8...9-2fc914e8eb80.
         Mounting /home...
[ OK  ] Mounted /home.
[ OK  ] Started LSB: NFS support files common to client and server.
[ OK  ] Reached target System Initialization.
[ OK  ] Listening on ACPID Listen Socket.
[ OK  ] Listening on CUPS Printing Service Sockets.
[ OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK  ] Reached target systemd-cron.
[ OK  ] Listening on D-Bus System Message Bus Socket.
[ OK  ] Reached target Sockets.
[ OK  ] Reached target Timers.
         Starting Restore Sound Card State...
         Starting Console System Startup Logging...
[ OK  ] Started Console System Startup Logging.
[ OK  ] Started Restore Sound Card State.
[ OK  ] Reached target Sound Card.
[ OK  ] Started Show Plymouth Boot Screen.
[ OK  ] Reached target Paths.
[ OK  ] Reached target Basic System.
         Starting Bluetooth service...
         Starting ifup for eth1...
[ OK  ] Started ifup for eth1.
         Starting LSB: start Samba NetBIOS nameserver (nmbd)...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting LSB: start Samba daemons for the AD DC...
         Starting LSB: keep memory of all UPnP devices that a...d themselves...
         Starting LSB: Apache2 web server...
         Starting Deferred execution scheduler...
[ OK  ] Started Deferred execution scheduler.
         Starting CUPS Printing Service...
[ OK  ] Started CUPS Printing Service.
         Starting LSB: disk temperature monitoring daemon...
         Starting LSB: Start the GNUstep distributed object mapper...
         Starting LSB: Create dynamic part of /etc/motd...
         Starting LSB: SMART monitoring daemon...
         Starting LSB: create NVIDIA device nodes...
         Starting OpenBSD Secure Shell server...
[ OK  ] Started OpenBSD Secure Shell server.
         Starting LSB: Start NTP daemon...
         Starting D-Bus System Message Bus...
[ OK  ] Started D-Bus System Message Bus.
         Starting LSB: SANE network scanner server...
         Starting Enable support for additional executable binary formats...
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
         Starting Initialize hardware monitoring sensors...
         Starting System Logging Service...
         Starting Network Manager...
         Starting /etc/rc.local Compatibility...
         Starting Login Service...
         Starting Permit User Sessions...
         Starting Accounts Service...
[ OK  ] Started LSB: Create dynamic part of /etc/motd.
[ OK  ] Started LSB: SMART monitoring daemon.
[ OK  ] Started /etc/rc.local Compatibility.
[ OK  ] Started LSB: Start the GNUstep distributed object mapper.
[ OK  ] Started LSB: keep memory of all UPnP devices that an...ced themselves.
[ OK  ] Started LSB: SANE network scanner server.
[ OK  ] Started Permit User Sessions.
         Starting Terminate Plymouth Boot Screen...
         Starting Wait for Plymouth Boot Screen to Quit...
[ OK  ] Started LSB: create NVIDIA device nodes.
         Mounting Arbitrary Executable File Formats File System...
[ OK  ] Mounted Arbitrary Executable File Formats File System.
[ OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

GeneBenson wrote:Hi autocrosser,

I am curious as to how you got that output in boot.log. Did you modify a setting in journald.conf? Do you have bootlogd installed?
I'm running the newest version of systemd (208.1) on a experimental sourced install--(I DO run experimental as my daily-driver)

I did clean up a bit of the output (just deleted timestamps), but thats the way the boot.log really looks now....

Nice & readable--gives you a good idea of what is going on....
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
wayne128
Level 10
Level 10
Posts: 3412
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

@kurotsugi,
thanks for your pointers.
on my experience, samba didn't work well with systemd and makes the boot a lot longer.
I have NAS with all sorts of backup OS images and media files, for sharing with home users and watching movies/media from other computers and media players to TVs.
Samba is necessary to run on my home network.

here is the systemd-analyze critical-chain,

wayne@hp8000:~$ 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.

Code: Select all

graphical.target @21.418s
└─multi-user.target @21.418s
  └─smbd.service @20.987s +430ms
    └─nmbd.service @8.326s +12.660s
      └─basic.target @8.322s
        └─sockets.target @8.322s
          └─dbus.socket @8.322s
            └─sysinit.target @8.307s
              └─nfs-common.service @7.881s +425ms
                └─rpcbind.target @7.881s
                  └─rpcbind.service @7.733s +147ms
                    └─network.target @7.733s
                      └─networking.service @5.586s +2.146s
                        └─local-fs.target @5.309s
                          └─run-rpc_pipefs.mount @8.174s
                            └─local-fs-pre.target @5.306s
                              └─systemd-remount-fs.service @4.888s +418ms
                                └─keyboard-setup.service @2.221s +2.665s
                                  └─systemd-udevd.service @2.055s +166ms
                                    └─systemd-tmpfiles-setup-dev.service @1.307s +747ms
                                      └─systemd-journald.socket @1.226s
                                        └─-.mount @1.225s
wayne@hp8000:~$ 

capture dmesg | grep error and fail here for reference...

Code: Select all

wayne@hp8000:~$ dmesg | grep error
[    0.236260] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
wayne@hp8000:~$ dmesg | grep fail
[    0.236250] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20131115/dsfield-211)
[    0.236254] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f744ff98), AE_ALREADY_EXISTS (20131115/psparse-536)
[    0.236264] acpi PNP0A08:00: _OSC failed (AE_ALREADY_EXISTS); disabling ASPM
[    5.584464] 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.
wayne@hp8000:~$ 
woodsman
Level 4
Level 4
Posts: 305
Joined: Tue May 11, 2010 10:22 pm

Re: LMDE Breakages (Tracking SID)

Post by woodsman »

LMDE, fully updated.

* Where is the gphoto2 package? (To be able to run gphoto2 --auto-detect)

* Can we get the hardinfo package added to the repositories? (Similar to lswh but offers a different format and includes some nominal benchmarks.)

* I understand that something has to be the default (A4), but when installing printers and LANG=en_US.UTF-8, the printer configuration tool should automatically change the default paper size to Letter rather than A4.

* Seems to be a common problem with LMDE: my camera is not recognized.

* Requesting some minor cosmetic changes to Cinnamon.

I hope this information helps. Please let me know how I can help test and debug. :)
wayne128
Level 10
Level 10
Posts: 3412
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

woodsman wrote:LMDE, fully updated.
hi woodsman, i hope you know this thread are for those people who track Debian unstable repos or tracking Debian sid :mrgreen:

Not supported by LMDE, officially. :mrgreen: :wink:

so welcome to the dark side..

anyway...see my code tags on these two packages , both in Sid and you can see that I have hardinfo installed

* Where is the gphoto2 package? (To be able to run gphoto2 --auto-detect)

* Can we get the hardinfo package added to the repositories? (Similar to lswh but offers a different format and includes some nominal benchmarks.)

Code: Select all

wayne@hp8000:~$ apt-cache policy gphoto2 hardinfo
gphoto2:
  Installed: (none)
  Candidate: 2.5.4-1
  Version table:
     2.5.4-1 0
        500 http://ftp.jp.debian.org/debian/ sid/main i386 Packages
hardinfo:
  Installed: 0.5.1-1.3
  Candidate: 0.5.1-1.3
  Version table:
 *** 0.5.1-1.3 0
        500 http://ftp.jp.debian.org/debian/ sid/main i386 Packages
        100 /var/lib/dpkg/status
wayne@hp8000:~$ 


I believe your LMDE is tracking the offical repos from Linuxmint, which is UP8 at the moment.
If you must install gphoto2 and hardinfo, what you can do is temporarily add Debian Sid repos to your /etc/sources.list, then do a apt-get update, install only these two , hopefully there is no dependency issue or else it can be a mess..Once you tested them working, you should comment out the Debian Sid repos..


I do not use printer and camera on this installation so no comment on these two.

Please take note, sid or unstable can break big time, if you like to play with unstable, it is recommended to get prepare for breakages on any update.

So the few things we normally do are:
1. clone or backup the OS image to external USB drive so as we can restore easily if it breaks.
2. install apt-listbugs so as to be awared on bugs each time when we dist-upgrade, bugs always happen and at time a long list appear. we check those bugs reports and at time take some risk to dist-upgrade even with those bugs unresolved.
3. pay attention to what sid wants to remove.. sometime it wants to remove 400-500 packages and remove the whole desktop environment :lol: :mrgreen:
and of course we just wait and be patience. :mrgreen:
Last edited by wayne128 on Mon Apr 28, 2014 11:14 pm, edited 1 time in total.
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

wayne128 wrote:

Code: Select all

wayne@hp8000:~$ dmesg | grep error
[    0.236260] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
wayne@hp8000:~$ dmesg | grep fail
[    0.236250] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20131115/dsfield-211)
[    0.236254] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f744ff98), AE_ALREADY_EXISTS (20131115/psparse-536)
[    0.236264] acpi PNP0A08:00: _OSC failed (AE_ALREADY_EXISTS); disabling ASPM
[    5.584464] 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.
wayne@hp8000:~$ 
Hi Wayne!!!

Came up #1 on a google search: https://bbs.archlinux.org/viewtopic.php?id=145075 Looks to "fix" your problem--Tell me if that works.....

As for my samba times--I have a very minimal config for samba - it is almost a non-service on my system.....
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
GeneBenson
Level 4
Level 4
Posts: 352
Joined: Fri Sep 17, 2010 9:55 pm

Re: LMDE Breakages (Tracking SID)

Post by GeneBenson »

Hi autocrosser,

Thanks for the quick reply. I just asked because I don't have a boot.log at all. :?
autocrosser wrote:
GeneBenson wrote:Hi autocrosser,

I am curious as to how you got that output in boot.log. Did you modify a setting in journald.conf? Do you have bootlogd installed?
I'm running the newest version of systemd (208.1) on a experimental sourced install--(I DO run experimental as my daily-driver)

I did clean up a bit of the output (just deleted timestamps), but thats the way the boot.log really looks now....

Nice & readable--gives you a good idea of what is going on....
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

GeneBenson wrote:Hi autocrosser,

Thanks for the quick reply. I just asked because I don't have a boot.log at all. :?
Well-- As soon as you goto SystemD you will.... ;)

And I highly recommend the pdf & link I posted on the bottom of page 6 to anyone that wants to get more than the basic config out of it....I'm glad we didn't go with Upstart (no flamewars intended....)
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
wayne128
Level 10
Level 10
Posts: 3412
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

autocrosser wrote: Hi Wayne!!!

Came up #1 on a google search: https://bbs.archlinux.org/viewtopic.php?id=145075 Looks to "fix" your problem--Tell me if that works.....
.
hi autocrosser,

i read this
Instead graphical.target now Wants display-manager.service and all display managers are supposed to install the appropriate Alias. Afaik all display manager service files have been updated ragarding this and a "systemctl reenable slim.service" should fix it.
but struggle on how to do systemctl reenable slim.service :oops:

Edit: oops.. what am i doing?
this installation has lightdm, I change to autologin via lightdm
no slim installed.. so i guess i just ignore the slim-service as it does no harm :!: ??
Locked

Return to “LMDE Archive”