startup messages gone

Hi, I'm just wondering if anyone else has had the startup/shutdown messages stop showing on Wheezy?

i.e.
'Starting up service... blah'
[ ok ] Service Started successfully..

Now it only shows a systemd-fsck message about a partition being clean.

I know I can remove 'quiet' from /etc/default grub but that doesn't provide the same tidy output. I'd like to get the normal messages back, any ideas?

I've done a few fresh Wheezy 7.6 Amd64 installations and after a few reboots setting things up etc. it just stops giving the usual messages. I initially thought it was after the installation of nVidia drivers, but it started before that stage.

Thanks for any help.
EDIT: maye this is related to this.

Post

cat /etc/os-release

/etc/apt/sources.list

zippy@debian:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 7 (wheezy)"
NAME="Debian GNU/Linux"
VERSION_ID="7"
VERSION="7 (wheezy)"
ID=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="http://bugs.debian.org/"

zippy@debian:~$ cat /etc/apt/sources.list
# 

# deb cdrom:[Debian GNU/Linux 7.6.0 _Wheezy_ - Official amd64 kde-CD Binary-1 20140712-14:09]/ wheezy main
# deb cdrom:[Debian GNU/Linux 7.6.0 _Wheezy_ - Official amd64 kde-CD Binary-1 20140712-14:09]/ wheezy main

deb http://ftp.uk.debian.org/debian/ wheezy main contrib non-free
deb-src http://ftp.uk.debian.org/debian/ wheezy main contrib non-free

deb http://security.debian.org/ wheezy/updates main
deb-src http://security.debian.org/ wheezy/updates main

# wheezy-updates, previously known as 'volatile'
deb http://ftp.uk.debian.org/debian/ wheezy-updates main
deb-src http://ftp.uk.debian.org/debian/ wheezy-updates main

# For libdvdcss2:
deb http://download.videolan.org/pub/debian/stable/ /
deb-src http://download.videolan.org/pub/debian/stable/ /

# For Steam:
# deb http://ftp.uk.debian.org/debian/ testing main contrib non-free

You had testing in your repos. How did you install steam? What ws the command?

I did the following (from a webpage somewhere):

I’m starting from a clean Debian Wheezy 64 bit (amd64) install. Everything below is done as root (or using sudo). 1. Mixing in Jessie. If you haven’t got yet, put a line to fetch testing (“Jessie”) packages into your packages source file /etc/apt/sources.list: deb http://ftp.uk.debian.org/debian/ testing main contrib non-free 2. Then ensure that most packages are not taken from testing by choosing a default release via a file (you need to create it) named like: $ pico /etc/apt/apt.conf.d/10defaultRelease Add the following line: APT:efault-Release "stable"; (Don’t forget the semicolon!) 3. Mixing in 32 bits. Add the architecture for 32 bit (named i386) to your Debian installation – the Debian guys allow us to use both at the same time! dpkg --add-architecture i386 Go for it Install steam along with everything it needs (but not anything more) from Debian “testing”: apt-get update apt-get -t testing install steam:i386

I added the next 2 steps as otherwise my system wants pull in lots of Jessie files (as if the repo-pinning above wasn't working):

4. Comment-out the testing repository in /etc/apt/sources.list

5. To fix Team Fortress 2 message about en_US.UTF-8:
Uncomment en_US.UTF-8 UTF-8 in /etc/locale.gen and then run locale-gen as root.

Edit: I think I took the above from an earlier verion of the guide available on this website.

Another one of the countless victims of bad advice regarding mixing Debian repositories to install Steam. You have successfully borked your system.
In your situation I would recommend to either make a full upgrade to Jessie/Testing, so that your system gets to a clean state again, or reinstall Wheezy and use this method to install Steam.

Thanks very much, I didn't much like having the Jessie repos in my sources! Thanks for correcting me, I shall do a Wheezy reinstall & follow your guide.

Edit: I was also experiencing another couple of issues that I will put down as being symptoms of the same mixed-repo cause. The issues were the system hanging on every second shutdown & Akregator wasn't downloading RSS feeds either.