I also have no errors with kernel 3.7 from liquorix (64-bit). This makes me think though - has anyone switched to upstart or systemd on Debian? I just tried systemd in VBox and, while VBox performance is hard to measure, it booted in basically the same time (although because of VBox it isn't too accurate).

cwwgateway wrote:I also have no errors with kernel 3.7 from liquorix (64-bit). This makes me think though - has anyone switched to upstart or systemd on Debian? I just tried systemd in VBox and, while VBox performance is hard to measure, it booted in basically the same time (although because of VBox it isn't too accurate).

I had another distros using systemd.

Boot time check:dmesg showed very fast response, something in th order of 14.x second, while older method is around 25-30 seconds.However I do not really get that advantage on such a 'huge boot time reduction' because actually the desktop is ready only around 30 seconds.

Reboot issue:then on many reboot I notice a few times it does not want to boot my desktop.upon some discussion, I eventually return to old method sysv

on another computer, 10-yr old, most of the time it cannot cold boot.return to sysv resolved that issue.

I tried systemd for a while and it worked, but then an update broke it so I went back to sysv.

I tried it again somewhat recently after the update to GNOME 3.6, because Plymouth and GDM 3.6 weren't getting along with sysv as the system manager, but for some reason I failed to get a proper 3D-acceleted environment, it seems the Intel graphics driver failed to load properly and I ended up on the Gallium driver through LLVM-pipe or whatever... (Plymouth and GDM seemed to get along fine with systemd handling everything, though...) Since not having the Intel driver working wasn't going to cut it I went back to sysv and removed Plymouth instead so everything works, though I am disappointed I can't have a nice splash screen...

I will note that boot times did improve slightly with systemd, but my computer already boots relatively quickly, and I still have to wait a little while for the desktop to appear after I've logged in anyway, so the few extra seconds or so I saved really didn't matter too much.

systemd:one and half year install broke to pieces due to a in-the-fly change to systemd (even if the change was prepared for almost 6 months)reinstall afresh with a systemd based iso and the boot time is slightly faster but this experience made me think: if debian decides to switch to systemd (is there other option?) we gonna have serious issues in sid/testing when that happens.

Thanks for the pointers, I've installed systemd, and it seems to be working fine so far. It reduces bootup time by a few seconds. I might be imagining things, but it also seems as though my system is a bit more responsive than before.

mockturtl wrote:There's some sort of conflict between libjack0 and libjack-jackd2-0 on multi-arch -- they both provide a virtual package libjack-0.116 required to install ia32-libs (needed for this Steam game).

Accept this solution? [Y/n/q/?] yThe following packages will be DOWNGRADED: libcurl3-gnutls libudev-dev libudev0 udev The following NEW packages will be installed: libcurl3-gnutls:i386 libtheora0:i386 libudev0:i386 0 packages upgraded, 3 newly installed, 4 downgraded, 0 to remove and 6 not upgraded.Need to get 1,707 kB of archives. After unpacking 1,590 kB will be used.Do you want to continue? [Y/n/?] y