[SOLVED] Pure systemd (systemd-sysvcompat) causes slowdown

Apologies in advance for the vague issue report: i'm not too sure how to go about diagnosing the problem.
I've set up systemd as directed in the wiki: https://wiki.archlinux.org/index.php/sy … stallation
Things work just fine for the "mixed" installation.
However, when i go all in and install systemd-sysvcompat, i notice a considerable slowdown in the performance of my computer. (E.g. flash videos are laggy when watching full screen, and some code i'm working on takes 10s on a particular benchmark vs. 2s with the mixed install.)
When i run "top" there's nothing using a copious amount of CPU or memory that could explain the slowdown.
I guess that either there's something different in the daemons that run. Maybe there's some cpu power management or something not being enabled. Well, i don't know really, hence the post!
Any idea how i can go about tracking this one down?
Thanks.
edit: [SOLVED], well disappeared on its own...
After reinstalling initscripts, rebooting, then reinstalling systemd-sysvcompat (removing initscripts), and making the required changes to /boot/grub/menu.lst, things seem to be back to full speed... Weirdness. Apologies for posting too soon.
Last edited by yourealwaysbe (2012-09-09 01:09:17)

Similar Messages

[SOLVED] Reinstalling Arch on pure systemd - Localization problem.

Hi
I have accident regarding today filesystem update, so I decide to install arch again on pure systemd from the begining.
I am now on freshly installed xfce and i just noticed my userspace is totally not localized, despite proper localization steps.
/etc/locale.gen
pl_PL.UTF-8 UTF-8
# cat /etc/vconsole.conf
KEYMAP=pl
FONT=lat2-16
CONSOLEFONT=lat2a-16
FONT_MAP=8859-2
# locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX
pl_PL.utf8
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=pl_PL.utf8@euro
LC_CTYPE="pl_PL.utf8@euro"
LC_NUMERIC="pl_PL.utf8@euro"
LC_TIME="pl_PL.utf8@euro"
LC_COLLATE="pl_PL.utf8@euro"
LC_MONETARY="pl_PL.utf8@euro"
LC_MESSAGES=C
LC_PAPER="pl_PL.utf8@euro"
LC_NAME="pl_PL.utf8@euro"
LC_ADDRESS="pl_PL.utf8@euro"
LC_TELEPHONE="pl_PL.utf8@euro"
LC_MEASUREMENT="pl_PL.utf8@euro"
LC_IDENTIFICATION="pl_PL.utf8@euro"
LC_ALL=
What i should do?
Last edited by utops (2012-10-06 11:46:37)

utops wrote:
karol wrote:
Create ~/.config/locale.conf
$ cat $HOME/.config/locale.conf
LANG="pl_PL.UTF-8"
and reboot.
I know nothing about xfce, but can you tell me what part of the console stuff is in English? Can you copy / paste an example?
$HOME config don't work either.
From grub to login and from using CLI apps like nano and wifi-menu,mc,no polish language there.
Everything is in english...
Like system sudenly goes blind and don't see what i put in to configs.
Everything worked well on my old pretty instalation i already miss that times.
EDIT:
Sudenly it worked again.
Dunno what happened,just working again...
Ok,so thx for tips guys,have a good evening...
see my previous post.
please mark the thread as solved.

Systemd (systemd-sysvcompat) cannot be installed [SOLVED]

I installed systemd today.
It seems that EVERYTHING is working and I get not errors.
So, I decided to go to step 5 of a pure systemd installation.
But when I do this is what I get:
pacman -Syu systemd-sysvcompat
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
:: systemd-sysvcompat and sysvinit are in conflict. Remove sysvinit? [y/N]
If I choose N then
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: systemd-sysvcompat and sysvinit are in conflict
So I figure, well this means I need to say Y and I try:
pacman -Syu systemd-sysvcompat
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
:: systemd-sysvcompat and sysvinit are in conflict. Remove sysvinit? [y/N] Y
error: failed to prepare transaction (could not satisfy dependencies)
:: initscripts: requires sysvinit
so ... what gives?
Anyone has any ideas?
R.
Last edited by ralvez (2012-08-31 04:10:05)

Allan,
Thanks for the reply.
I had considered doing just that but in the wiki it reads:
Note: In a pure systemd installation, ** installing systemd-sysvcompat removes initscripts and sysvinit **, permits the export of LANG in /etc/locale.conf, and creates symlinks to halt, reboot, etc.
So I figured that may be I had skipped something and therefore in my case it was not working... better sure than sorry
Thanks again.
R.

[Solved] Installting A Pure systemd System From Scratch

Hello all,
A few months back I gave Arch a spin and it was great, but decided to wait for Windows 8 RTM to come out to check it out as well.
Windows 8 being the horrible thing it is, Arch is the way to go, and I would like to do a test installation alongside Windows 7, in order to make sure I can make the switch permanently.
Having followed the forums pretty consistently, it seems that systemd is the future.
Instead of waiting for it to be integrated (which is supposed to happen at some point), I was wondering if I can somehow install a pure systemd system as part of the basic installation and not installing initscripts at all.
Thanks, Adam.
Last edited by adam777 (2012-08-28 12:55:27)

mhertz wrote:
luvfree wrote:[...].
I'm going to reinstall anyway so why not wait until the iso doesn't pacstrap the old initscripts and sysvinit?
Just makes for a cleaner install all around.
I'm certainly not going to leave this install on with 4 installed desktop environments.[...]
I myself was also reinstalling alot and imaging and whatnot when I first began with linux(arch), but after some time I realised that it was pointless and linux dosen't need those reinstalls for optimization like windows did, and pacman has nifty switches to get you sorted on what you've explicitly installed and hence, can go delete the cruft not used anymore, or to list files not owned by any installed packages, to clean up in etc...
Nowadays, I newer reinstall unless something would go _really_ wrong, and only backup config-files and home-files, and keep a livecd around for rescue-operations, and an automated personal install script for if I ever do need to reinstall...
Anyway, of course it's your own choise
I understand and the arch way is awesome.
but it is still on the new side to me.
I've bloated this install with 4 desktop environments so a reinstall is inevitable. lol
once I settle on which one to keep I'll do just that.
it will be some time though I'm sure.
I'm just keeping my eye out for an iso without the old initscripts pacstapped to begin with.
it just HAS to be a cleaner install.
Thanks for your input though.
CHEERS.
Oh yeah and by the way I've used nothing but linux for over 10 years now.
No windoze here.
Last edited by luvfree (2012-09-05 03:40:22)

[SOLVED] After Systemd update...2 problems!

Yesterday I update my system and switch to the pure systemd as of arch linux wiki.
Everything is working well, boot time is lightning fast, every programs are working except for Amarok and Vlc.
When I click on the start menu (I'm using KDE) -> then multimedia and Amarok or Vlc, the icon bounce without opening the program's window.
I must kill the Amarok and/or Vlc process in the monitor.
Running in console show absolutely nothing for Vlc.
Running Amarok in sudo in console output:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
unnamed app(774): KUniqueApplication: Cannot find the D-Bus session server: "/usr/bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed
All my daemon of before systemd are active and systemd setting are ok too.
Does anyone have the same behavior or can point me to a possible solution?
Thanks,
Last edited by Chuck Arch Linux (2014-12-08 00:43:33)

jasonwryan wrote:
ngoonee wrote:I'm deleting your other thread, no cross-posting allowed (please read the rest of the Forum Etiquette as well).
And less than half an hour after being warned for it: https://bbs.archlinux.org/viewtopic.php … 4#p1163234
Do it again and you will be banned.
Sorry, by the way, can you help me?
Thanks
edit
Time solved this issue....
Last edited by Chuck Arch Linux (2014-12-08 00:44:38)

[SOLVED] Borked systemd setup -- dbus errors during boot; can't login

I have error messages very similar to this post. Unfortunately, as the author states, he never persisted in solving it but instead re-installed from scratch. I'd rather not do that.
For reference, I have a pure systemd setup -- no rc.conf file, no initscripts package, etc.
At boot I get the "Welcome to Arch!" messages followed by the various [OK] lines and then I get blindingly fast repeating lines about dbus not starting and attempting to restart it too quickly. If I walk away for about 1-2min, I finally see a login screen, but after entering my username/password, it just sits there and does nothing.
As for suspects... I had systemd working fine.
-- I updated some packages (not more than a few days worth and I'd have to check the list)
-- I also took care of manual updates to some .pacnew files I periodically check for. In this group were some biggies: group, shadow, and passwd. I did recall the odd bit about uuidd changing from uid 995 to 68, but in reading about that since then, it doesn't seem to be a big deal.
I've been booting in by appending
systemd.unit=emergency.target
to the kernel line, but my exploration hasn't been all that helpful. `journalctl since=date` reveals the errors, but I don't get much information about why dbus is having issues starting.
emergency.target also doesn't seem to be that helpful since I can't do anything with a read-only system. I'd love some suggestions about what, specifically, to check for before I reboot from Windows back into Arch and record more careful notes, probably by jotting notes onto a flash drive. Any places to start? For reference, I've done:
-- systemctl status dbus: lists as inactive (dead) and simply shows the errors I see at boot (failed to start)
-- systemctl list-units
-- systemctl list-unit-files
-- journalctl and looking around for instances of fail or failed or dbus
If I start systemd-logind.service or dbus.service, it displays a status message about running fsck and then takes me to a login prompt automatically. Then I can type in my username and password and then there's nothing after that. No prompt, just an apparent hang.
Thanks for any suggestions -- I'll take them and then collect more detailed results and report back.
Thanks!
Last edited by jwhendy (2012-11-08 16:07:33)

As I wondered, I think it's a problem with passwd. I don't have a dbus entry and must have missed it when I was copying things around between my version and the .pacnew. Downloading an install disc now since I can't seem to change it from the recovery console due to mounting root read-only.
I'd love to know of a way to boot that avoids starting dbus and other things that might break while still having read/write access to root. Will mark solved once I update /etc/passwd and reboot.

[solved] udev = systemd-tools: system no longer boots completely

Hi guys. Today I updated my system, and now it won't boot past the boot messages. It appears that my ttys aren't being "made" (?). The actual errors appear to be
[ TIME ] Timed out waiting for device dev-tty2.device
[ TIME ] Timed out waiting for device dev-tty3.device
Booting into rescue.target doesn't complete either.
Downgrading systemd-184-2 => systemd-44-7, and replacing systemd-tools with udev allows me to boot successfully again.
Additional info:
cpu: Intel Core i5-3570K
kernel: linux-3.3.7-1-x86_64
graphics card: GeForce GTX 560 Ti
graphics driver: xf86-video-nouveau 0.0.16_git20120512-1 (relevant, maybe? 0.0.16_git20120512-2 makes X give up with a "No screens found" error
system init: systemd (via systemd-sysvcompat)
Advice please.
EDIT: boot screen images
EDIT EDIT: I can connect via SSH to the affected machine. Here's the journal: http://codepad.org/76aB2DnD
EDIT EDIT EDIT: That apparently got snipped. Here's part 2, starting from line 806: http://codepad.org/5UGdsuwE
Last edited by WorMzy (2012-06-02 00:15:21)

Huh. I guess the problem was a couple of stale and crusty {,f}getty .service files, and an obsolete slim.service file I created a while back.
Removing them fixed my problem, although tty1 still shows boot messages (not a problem, and may not even be "new" behaviour)
Cheers Tomegun.

[SOLVED] Verifying systemd conversion

Good Afternoon Fellow Archers,
I have an x86_64 installation of Arch when Arch was still using sysV init. When systemd was recommended, I switched over as recommended. So my system should be pure systemd, at least so I think. And the changeover was fairly easy. I just had to change how I start/stop/enable/restart daemons using systemctl. Minor.....
I have no "/etc/init.d" dirtree, and "/etc/rc.d" only has six entries in it, all scripts, and no dirtrees of any kind. It has a date/time stamp that keeps getting refreshed periodically. LIke today, after a "pacman -Syu" in which a new systemd was installed (204). In "/etc/rc.d" there are six scripts, "bluetooth, ip6tables, iptables, ntpd, ntpdate, and ppp".
I have looked at the systemd wiki, checked out the forums, and followed links to other related articles on the site...but I do not find the specific information (guide) I am looking for.
I am looking for a way to determine absolutely, if I have a pure systemd installation now, or if there are any remnants of sysV that I still need to convert/remove.
Question: How can I determine if I have a pure systemd implementation?
And in asking, I also highly recommend adding the answer to the wiki page of "systemd" to allow others to determine that they are running a pure systemd implementation.
I will certainly be appreciative for any information/quide.
Sincerly and respectfully,
Dave
Last edited by dcbdbis (2013-05-22 23:40:24)

Thank you for the link, and for the reply,
I didn't use the code tags as it was not code that I wanted someone to copy and paste into their own system.
I'll use them next time... my apologies.
And also my thanks for the responses. I'm good to go now.
Dave....
PS: I followed the other forum link, and like one of the poster's, I deleted my /etc/rc.d dir. Rebooted. Everything came back up just perfect. So systemd it is! I already had the sysv compat utilities installed.
Last edited by dcbdbis (2013-05-22 23:47:46)

Problem: murmur (mumble server) restarts on pure systemd system

Hi. I have a pure systemd install (no rc.conf).
I installed murmur form "community" and started it with
systemctl start murmur
The service starts but restarts every two minutes or so with these lines in journalctl:
PID file /run/murmur/murmur.pid not readable (yet?) after start.
murmur.service operation timed out. Terminating.
Unit murmur.service entered failed state.
murmur.service holdoff time over, scheduling restart.
Any clues?
Last edited by SoleSoul (2012-08-18 22:42:41)

I now use murmur-ice from the AUR, but my problem was resolved after manually creating /run/murmur/murmur.pid, setting permissions, and restarting the systemd service. Never had a problem after that. Not sure why this wasn't getting created automatically; my /var/run and /run symlinks are correct and no problems with other services.
Sorry I can't be of more help, but it seems to have something to do with a conflict between the service and the desired pid file.

[Solved] Overriding systemd Unit Files Isn't Working

I'm trying to set up some custom dependencies for various services, some of which are supported packages, some are custom packages I've developed. I am running into problems following the procedure described here - specifically, service files in /etc/systemd/system are ignored, and the only way to override them is to edit the files in /usr/lib/systemd/system. I have verified this issue on both a VPS instance and my desktop. Both systems were originally built well before systemd and have been converted to pure systemd systems. Does anyone else see these issues, or know of any reason this would be happening and/or how to resolve it?
Steps to reproduce. This example uses httpd and mysql, but I've tested it with several other services, always with the same results:
Enable the service unit and create a new override:
systemctl enable httpd.service
rm /etc/systemd/system/multi-user.target.wants/httpd.service
cp /usr/lib/systemd/system/httpd.service /etc/systemd/system/multi-user.target.wants/httpd.service
Edit /etc/systemd/system/multi-user.target.wants/httpd.service, adding a line 'Wants=mysqld.service' to the [Unit] section.
Make systemd changes effective, and verify them. The first command results in an error that says "Failed to issue method call: Invalid argument". The final command will show an empty list ("Wants="), when it should list mysqld. Running systemd-delta also shows no override.
systemctl reenable httpd
systemctl daemon-reload
systemctl show -p "Wants" httpd.service
Change the replacement unit file to .include the packaged unit file:
cat > /etc/systemd/system/multi-user.target.wants/httpd.service << __EOF
.include /usr/lib/systemd/system/httpd.service
[Unit]
Wants=mysqld.service
__EOF
Repeat step #3, with the same results
Reenable the package's unit:
rm /etc/systemd/system/multi-user.target.wants/httpd.service
systemctl enable httpd.service
Edit the original unit file in /usr/lib/systemd/system/httpd.service, adding the 'Wants=myslqd.service' to the Unit section
Repeat step 3
Result is the correct and expected one this time ("Wants=myslqd.service")
Last edited by dwheeler (2012-11-14 19:53:10)

Well...
I'm still having problems with .service custom files!
I want to customize the ExecStart from original cronie.service file, like this:
# cat /etc/systemd/system/cronie.service
.include /usr/lib/systemd/system/cronie.service
[Service]
ExecStart=/usr/sbin/crond -n -s -m off
==============================
# systemctl restart cronie.service
Failed to issue method call: Unit cronie.service failed to load: Invalid argument. See system logs and 'systemctl status cronie.service' for details.
==============================
# systemd-delta
[OVERRIDDEN] /etc/systemd/system/cronie.service → /usr/lib/systemd/system/cronie.service
--- /usr/lib/systemd/system/cronie.service 2012-11-22 20:04:00.000000000 -0200
+++ /etc/systemd/system/cronie.service 2012-11-27 16:09:49.944085437 -0200
@@ -1,10 +1,3 @@
-[Unit]
-Description=Periodic Command Scheduler
+.include /usr/lib/systemd/system/cronie.service
[Service]
-ExecStart=/usr/sbin/crond -n
-ExecReload=/bin/kill -HUP $MAINPID
-Restart=always
-[Install]
-WantedBy=multi-user.target
+ExecStart=/usr/sbin/crond -n -s -m off
==============================
# systemctl status cronie.service
cronie.service - Periodic Command Scheduler
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
CGroup: name=systemd:/system/cronie.service
Nov 27 13:52:59 xpto systemd[1]: Starting Periodic Command Scheduler...
Nov 27 13:52:59 xpto systemd[1]: Started Periodic Command Scheduler.
Nov 27 13:52:59 xpto /usr/sbin/crond[309]: (CRON) INFO (running with inotify support)
Nov 27 14:01:01 xpto /usr/sbin/crond[8216]: pam_unix(crond:session): session opened for user root by (uid=0)
Nov 27 14:01:01 xpto /USR/SBIN/CROND[8217]: (root) CMD (run-parts /etc/cron.hourly)
==============================
What am I doing wrong?
Thanks in advance.

[solved] Boot issues after update caused by LVM

Hi,
I know that there are some threads regarding boot issues but I haven't been able to find a solution for my problem.
I have the following partitions:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 74.5G 0 disk
├─sda1 8:1 0 128M 0 part /boot
├─sda2 8:2 0 2G 0 part [SWAP]
└─sda3 8:3 0 72.4G 0 part
├─vg_trinity-root (dm-0) 254:0 0 10G 0 lvm /
└─vg_trinity-home (dm-1) 254:1 0 25G 0 lvm /home
I have
USELVM="yes"
in my rc.conf and the following im mkinitcpio.conf:
HOOKS="base udev autodetect pata scsi sata lvm2 filesystems"
Still, when booting the volume group does not get activated. The following message appears:
:: running hook [lvm2]
Activating logical volumes...
No volume groups found
Waiting 10 seconds for device /dev/mapper/vg_trinity-root ...
ERROR: Unable to find root device '/dev/mapper/vg_trinity-root'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
At that point I just run
lvm vgchange -ay
exit the shell and booting continues. So somehow activation of the volume group does not occur early enough. I reinstalled udev, mkinitcpio, linux and generated a new boot image as proposed in https://bbs.archlinux.org/viewtopic.php … 4#p1059124 but to no avail. Is there anything else that might be wrong with my configuration?
Thanks for any help.
mK
Last edited by musiKk (2012-09-09 16:23:17)

My apologies. Usually I'm quite good at searching but this one slipped right past me. Marking as solved (even though the root cause is still WIP).

[SOLVED]PulseAudio systemd daemon doesn't work

Hello.
I try to set PulseAudio as systemd service, but I'm still getting errors.
Here is how my .service file looks like.
$cat /usr/lib/systemd/system/[email protected]
[Unit]
Description=PulseAudio Sound System
Before=sound.target
[Service]
BusName=org.pulseaudio.Server
ExecStart=/usr/bin/pulseaudio --start
Restart=always
User=%1
[Install]
WantedBy=multi-user.target
And here is what I get (dan is my username):
$ systemctl start [email protected]
$ systemctl status [email protected]
[email protected] - PulseAudio Sound System
Loaded: loaded (/usr/lib/systemd/system/[email protected]; disabled)
Active: failed (Result: start-limit) since Mon 2013-09-16 11:42:46 CEST; 2s ago
Process: 1407 ExecStart=/usr/bin/pulseaudio --start (code=exited, status=217/USER)
Sep 16 11:42:45 530uarch systemd[1]: Failed to start PulseAudio Sound System.
Sep 16 11:42:45 530uarch systemd[1]: Unit [email protected] entered failed state.
Sep 16 11:42:46 530uarch systemd[1]: [email protected] holdoff time over, scheduling restart.
Sep 16 11:42:46 530uarch systemd[1]: Stopping PulseAudio Sound System...
Sep 16 11:42:46 530uarch systemd[1]: Starting PulseAudio Sound System...
Sep 16 11:42:46 530uarch systemd[1]: [email protected] start request repeated too quickly, refusing to start.
Sep 16 11:42:46 530uarch systemd[1]: Failed to start PulseAudio Sound System.
Sep 16 11:42:46 530uarch systemd[1]: Unit [email protected] entered failed state.
Thank you
Last edited by Kotrfa (2013-09-16 17:02:35)

Ahhh. Thank you for that. I will add it to my awesome autostart script.
Solved
Last edited by Kotrfa (2013-09-16 17:03:20)

[Solved -sorta] systemd-fsck []: fsck: /sbin/fsck.ext4: execute failed

Greetings.
I am getting the following on boot:
Starting Version 218
A password is required to access the MyStorage volume:
Enter passphrase for /dev/sda3
/dev/mapper/MyStorage-rootvol: clean, 210151/983040 files, 2284613/3932160 block
[ 78.084720] systemd-fsck [280]: fsck: /sbin/fsck.ext4: execute failed: Exec format error
[ 78.085215] systemd-fsck [287]: fsck: /sbin/fsck.ext2: execute failed: Exec format error
I then end up at a login prompt but if I try to login, I get “Login incorrect”. Sometimes Getty will stop and restart on tty1. Then I get returned to the login prompt.
This came about after upgrading with Pacman (which included “upgraded e2fsprogs (1.42.12-1 -> 1.42.12-2)”) a few days ago. Pacman completed successfully but on reboot the system froze forcing a hard reset.
I've booted to a USB and run fsck on the boot partition (the only ext2 partition). Ditto on the root and home volumes. All fine. I've also mounted all three and can access the data.
I would have thought it was something to do with the e2fs upgrade but it obviously scanned the root volume fine and I haven't been able to find any similar reports online.
I've searched online for ideas and I've also searched for logs which might give me some indication of what the cause is but at this point, I've reached my limits.
I'd just nuke the data and start again but I really want to understand what happened here.
Any thoughts on what caused this or suggestions on how to proceed?
Thank you.
Stephen
Last edited by FixedWing (2015-03-16 01:40:20)

Head_on_a_Stick wrote:
https://wiki.archlinux.org/index.php/Pa … ond_repair
However, it may be simplest to just re-install in your case -- it depends whether you want to use the troubleshooting & repairing as a learning process or if you just want your system up & running again ASAP...
All fixed and working just like nothing happened.
I did use the advice at the referred link plus a few others on archlinux.org and elsewhere. Yes, an absolutely wonderful learning experience!
I manually reinstalled e2fsprogs. That got Pacman working again and I was able to boot into the system. Then I used Pacman to reinstall e2fsprogs properly plus the other seven packages which were also installed during the same Pacman session despite their being corrupted.
What I really don't get is how Pacman could accept a package with 0 bytes and install it? How could such a package possible pass the security check? When I reinstalled the packages, Pacman of course refused to install the corrupt packages in the cache and deleted them. So why didn't that happen initially? I can only think that a corrupt file in that process terminated prematurely and that Pacman wasn't robust enough to detect this so simply continued on, now skipping the scans and installing the corrupt packages. So just to be sure it wasn't a corrupt file in Pacman itself, I also forced a reinstall of that package as well. I've upgraded packages since without issue so I have to assume that whatever the issue was is now gone.
Anyway, thanx for the help!
Stephen

[SOLVED]Pacman systemd missing file

Everytime when I run pacman I get this error:
error: could not open file /var/lib/pacman/local/systemd-217-8/desc: No such file or directory
I think i messed up something when upgrading system.
Can you help me to solve this issue?
Thanks
Last edited by Arch3R (2014-11-29 19:14:08)

Just reinstall systemd:
pacman -S systemd
select yes if it prompts due to it already being installed.
You might also want to run `pacman -Qk` to see if any other packages have been damaged.
EDIT: I just did some silly trial and error and deleted that file from my system (probably would have been smarter to move/rename it). Reinstalling systemd failed due to a conflicting file error as all the files for the package are there, but the pacman database doesn't realize they belong to that package. In this case I used --force with the single specific package:
pacman -S --force systemd
Note that this use of --force is an apparent necessity to fix this specific problem. This does not support using it when uncertain why something fails - I knew why it was failing.
Last edited by Trilby (2014-11-29 19:01:55)

[SOLVED] cpupower/systemd, cannot set 'performance' governor at boot

Hi all, i upgraded to systemd and everything is working fine and faster: the only one thing i'm missing is cpufrequtils since this was the only way to set the "performance" governor at boot and have it stay this way.
Since i upgraded to cpupower and enabled the cpupower.service unit, the governor is automatically switched to ondemand even if i specified performance in the /etc/conf.d/cpupower config file: i don't get what's happening because if i restart the cpupower.service unit manually everything is fine and it will not switch to ondemand on its own o_O
Processor information
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
stepping : 5
microcode : 0x11
cpu MHz : 1600.000
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips : 5322.83
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
/etc/conf.d/cpupower
# Define CPUs governor
# valid governors: ondemand, performance, powersave, conservative, userspace.
governor='performance'
# Limit frequency range
# Valid suffixes: Hz, kHz (default), MHz, GHz, THz
#min_freq="2668MHz"
#max_freq="2668MHz"
# Specific frequency to be set.
# Requires userspace governor to be available and loaded.
#freq=
# Utilizes cores in one processor package/socket first before processes are
# scheduled to other processor packages/sockets.
# See man (1) CPUPOWER-SET for additional details.
#mc_scheduler=0
# Utilizes thread siblings of one processor core first before processes are
# scheduled to other cores. See man (1) CPUPOWER-SET for additional details.
#smp_scheduler=0
# Sets a register on supported Intel processore which allows software to convey
# its policy for the relative importance of performance versus energy savings to
# the processor. See man (1) CPUPOWER-SET for additional details.
#perf_bias=
# vim:set ts=2 sw=2 ft=sh et:
sytemctl status cpupower.service
cpupower.service - Apply cpupower configuration
Loaded: loaded (/usr/lib/systemd/system/cpupower.service; enabled)
Active: active (exited) since Sat, 01 Sep 2012 10:50:05 +0200; 1min 27s ago
Process: 2148 ExecStart=/usr/lib/systemd/scripts/cpupower (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/cpupower.service
journalctl |grep -i cpupower
(empty)
I even tried to mimic an rc.local with a custom service i use to set RTC max frequency (for the Android emulator) but it doesn't set the governor to performance, even if i know this script works since i can query max_user_freq and read 2048 as i need it to be, here is the script launched by the custom service.
#!/bin/bash
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
echo 2048 > /proc/sys/dev/hpet/max-user-freq
cpupower frequency-set -g performance
Does this happen for you too? I remember having this problem one year ago, and switched to cpufrequtils since that was working: now that is being deprecated i would like to pinpoint the problem and solve it once and for all, can you help me?
I think i could auto-start some script via gnome-session-properties but i would love to have a systemd-only solution working :-/
Thank you,
Manuel
Last edited by bmanuel (2012-09-07 17:39:01)

z0id wrote:Are the proper kernel modules loaded?
Sure they are, "ondemand" and "performance" modules should be compiled-in into the default kernel, i can even run it *after* logging in gnome-shell and the settings will stay correctly.
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
ondemand performance

[SOLVED] Pure systemd (systemd-sysvcompat) causes slowdown

Similar Messages

Maybe you are looking for