[Solved] [Systemd] Systemd PKGBUILD on i686 (in a VM) - Linker failure

Hi all!
I'm trying to recompile Systemd using the PKGBUILD from ABS (rsynced again today - 18-6-2014). However, I cannot get it to build.
Obviously the Arch Linux builders can compile this, so I am doing something wrong, in some way shape or form.
Why I am even trying to do this:
I want to recompile Systemd for i586 - because I would like to run Arch Linux on the 16 year old Pentium MMX laptop. I have created a build script that builds everything in base and that base depends on, and have rebuilt everything except Systemd for i586 (changed makepkg.conf as per the wiki article https://wiki.archlinux.org/index.php/Install_Arch_i586 which may/may not be accurate).
I have tried both for i686 (default) and i586, so the issue is not related to the compilation architecture.
Problem:
During the compiling process, an error comes up from the ld.gold linker:
/usr/bin/ld.gold: error: .libs/pam_systemd.ver:2:1: syntax error, unexpected LOCAL, expecting STRING or QUOTED_STRING or EXTERN
/usr/bin/ld.gold: fatal error: unable to parse the version script file .libs/pam_systemd.ver
So, the .libs/pam_systemd.ver file is invalid in some way shape or form.
What I have tried:
Originally, the problem was with gudev, which I decided was not needed (this system will be CLI only due to low RAM), so I added --disable-gudev to the configure flags in the PKGBUILD. However research suggests that I need pam_systemd for logging in - so I do have to build pam_systemd.
I am unfamiliar with ld.gold, so further research showed that it was a linker, and that version files are special files that are used to mark libraries. I have base-devel installed, so it is not a missing dependency.
Looking at the original source tarball, the .libs directory (which poking around in the makefile revealed to be the obj directory) does not exist, so pam_systemd.ver must have been put there at some point. I have looked for references to pam_systemd.ver by running cat on every file and grepping the output, but failed to find any direct references. I have also looked at the other .sym files, which also appear to be the same as version script files. However, there is not one for pam_systemd.
Peering at the makefile using grep and searching in less have shown me that references to pam_systemd are fairly normal - and do not include any --version-script arguments to ld.gold, so I think that the .ver files are not supposed to exist. But what created them? Why? And why, if they are automagically created, are they invalid?
The mystery deepens - and my google fu leaves me. Please - can anyone shed some light on this?
I can post more info if required.
Thanks,
pypi
Last edited by pypi (2014-06-21 21:12:34)

Hi there!
I have a solution: adding CFLAGS="$CFLAGS -fno-lto" prior to the configure command fixes the build error!
This was borrowed from the development systemd Linux From Scratch 'Systemd-214' page (http://www.linuxfromscratch.org/lfs/vie … stemd.html. Any comments on what link time optimization does that might possibly create a dodgy version script would be appreciated - I'd love to know more about why this works.
Looking on the bright side, I now know what LTO is, at least vaguely. You learn new things every day, especially using Arch Linux
Thanks,
pypi

Similar Messages

[Solved] Starting systemd --user as a systemd --system process?

Hey guys,
I would like to run systemd --user as a system service using this .service file I wrote:
$ cat [email protected]
[Unit]
Description=Systemd --user instance for %I
Documentation=man:systemd
[Service]
User=%I
ExecStart=/usr/lib/systemd/systemd --user --log-level=debug
[Install]
WantedBy=multi-user.target
I enabled it for my user using `systemctl enable systemd-user@evan`, however, when starting it it fails with the following errors:
Jul 21 21:14:42 desktop systemd[12920]: systemd 204 running in user mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Jul 21 21:14:42 desktop systemd[12920]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system/[email protected]/[email protected]/systemd-12920.
Jul 21 21:14:42 desktop systemd[12920]: Failed to create root cgroup hierarchy: Permission denied
Jul 21 21:14:42 desktop systemd[12920]: Failed to allocate manager object: Permission denied
Is it possible to run systemd --user like this? Do I need to add something to my [email protected]?
Last edited by EvanPurkhiser (2013-07-22 02:10:10)

EDIT: I just realized that the systemd-user-session-units package will only include specific units at build-time weather I have have the programs or not. You're right, I should just use this package!
Well, to be honest, maybe I'm trying to hack around a problem that doesn't even really exist, but I don't think the systemd-user-sessions-units package meets my needs.
The way I would like to have my user sessions setup is something like this:
I would like to have an instance of systemd --user always running under my user so I can keep things like transmission-daemon always running, even when I don't have a user session open. When I do start my user session (via logging into getty) I want to bring my systemd instance up to a certain target. For example, logging in via tty1 should bring up graphical.target, which will start X11 and all that, while logging into any other tty will start console.target (for stuff like ssh-agent etc).
Thinking more about this I suppose there's really no reason I couldn't use the [email protected] from systemd-user-session-units, but since I won't use most of the other user units included, I would rather just not use it.
Here's what my .profile looks like:
if systemctl -q is-active systemd-user@evan
then
# Default systemd to the console target
target="console"
# If we're logging in from VT1 start the graphical target
if [[ $XDG_VTNR == 1 ]] && ! systemctl --user -q is-active graphical.target &> /dev/null
then
export DISPLAY=:0
target="graphical"
fi
# Set all environment variables in the systemd --user instance (still working on this)
env | systemctl --user set-environment -
# Bring up systemd --user to the specified target
systemctl --user start ${target}.target
fi
source "$HOME/.bashrc"
Last edited by EvanPurkhiser (2013-07-22 03:56:13)

[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)

Not yet solved, /usr/lib/systemd/systemd does not exit

Hi,
I was on 3.8.2 kernel, and did a full system backup with rsync to later upgrade, but after upgrading and rebooting, it just shows me
Error: Root device mounted successfully, but /bin/systemd does not exist.
Bailing out, you are on your own. Good Luck
tty's could not initialize [*or something similar, I'm not sure]
[root /]#
Then I just replaced my system with the backup I did earlier. But it shows the same
I did search for info but no clue.
Currently trying with an older backup.
Thanks in advance
Last edited by arcaid (2013-05-14 23:58:26)

progandy wrote:
Error: Root device mounted successfully, but /usr/lib/systemd/systemd does not exist.
The initscript tests if init is executable, so "does not exist" could also mean "is not executable"
Somehow your root has a problem with its execute permissions. Did you somehow remove them, /usr/lib/systemd/systemd should be 755 or "-rwxr-xr-x"?
While I'm not sure why is this modified, maybe the backups I did doesn't hold the attributes, I'm storing them in an NTFS partition but it can store the attributes doesn't it?
Well I changed the attributes as you mentioned, but then it makes me wonder if then pretty much the other root files are too with other attributes..which is really bad.
Nevertheless I changed it and now it shows permission denied and a kernel panic, sigh.
Here is an image of it: http://imageshack.us/photo/my-images/689/dsc06698b.jpg
Thanks in advance
@Pantera
The problem here is kinda different, while at the beggining it was the problem you mention and solution, now the thing is that it says that "/usr/lib/systemd/systemd does not exit" and not /bin/systemd which it was in the beggining. thanks though.

[SOLVED] Some systemd processes (e.g. systemd-journald) can't start.

After a fresh install on a new laptop (dual boot with Windows 8.1 vie rEFInd) I notice some error messages whilst booting. systemd-journald fails to start, and I also see some errors relating to the creation of the volatile filesystem. It's hard for me to give a lot detail about this as without journaling as I'm not sure how to get the error messages.
I did see this from dmesg:
[ 128.638674] systemd[1]: Starting Stop Read-Ahead Data Collection...
[ 128.662550] systemd[1]: Started Stop Read-Ahead Data Collection.
[ 194.545294] systemd[1]: Starting Journal Socket (/dev/log).
[ 194.545391] systemd[1]: Listening on Journal Socket (/dev/log).
[ 194.545471] systemd[1]: Starting Journal Socket.
[ 194.545540] systemd[1]: Listening on Journal Socket.
[ 194.545613] systemd[1]: Starting Journal Service...
[ 194.546604] systemd[1]: Started Journal Service.
[ 194.549797] systemd-journald[711]: Failed to get machine id: No such file or directory
[ 194.553931] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 194.554205] systemd[1]: Stopping Journal Service...
[ 24.362121] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m
[ 24.364106] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /var/log/journal/%m
[ 24.404888] systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
[ 24.409499] systemd[1]: Failed to start Create Volatile Files and Directories.
[ 24.412303] systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
And if I check the status of journald through systemctl I get:
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: failed (Result: start-limit) since Wed 2014-08-27 10:37:50 UTC; 1h 2min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Process: 720 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=1/FAILURE)
Main PID: 720 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
I've tried reinstalling systemd, and adding systemd to HOOKS in mkinitcpio.conf, neither of these things seem to help. I also can't start the services manually.
If anybody can help it would be greatly appreciated, thanks!
Last edited by Tim Butters (2014-08-28 15:49:50)

Normally, as Loqs said, 'systemd-firstboot --setup-machine-id' should have been run when you first installed the systemd package.
You can verify if the '/etc/machine-id' file exists:
$ ls -l /etc/machine-id
-rw-r--r-- 1 root root 33 25 mars 2009 /etc/machine-id
If you don't find one, maybe use 'systemd-machine-id-setup' instead to create one.
But have you seen error messages during the Arch installation? Because that should not be necessary.
Edit: 'systemd-firstboot' is new in systemd 216, so should not be found in the live installation disk 2014.08.
Last edited by berbae (2014-08-28 15:44:52)

How to solve this problem? '' can not activate cellular data network failure'' authenticating PDP from already thank you

how to solve this problem? '' can not activate cellular data network failure'' authenticating PDP from already thank you

What does this have to do with using an iPhone in an enterprise environment?
What carrier are you using and where did you get the phone?

[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] 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] 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)

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)

[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] systemd, systemd-journal constantly at high CPU %age

Hi all,
I've switched a computer to systemd, and everything works nicely. The system is responsive and booting is even faster than before. Yay!
However, both my CPU cores are constantly between 80% and 90%. When I do top in a terminal, I see systemd constantly in the 90%-100% range and systemd-journal in the 60%-100% range, also continuously. My CPU temperature is a lot higher than normal as well (currently at 61.0C)
Is this normal?
Last edited by diederick76 (2012-09-13 06:03:11)

I'm having a similar problem. I temporarily fixed it by replacing the cupsd.conf with the cupsd.con.default. Everything ran great, got the printer configured again, journald stopped thrashing my precious SSD by producing millions of these warnings (I didn't wc them, but I was probably getting thousands every second) and all was well. Until I "shared" the printer again. Immediately cupsd got locked into restarting thousands of times every second, once again thrashing my cpu and SSD.
Edit:
I guess I should probably share my cupsd.conf. I didn't manually edit it, I used the web interface:
cat /etc/cups/cupsd.conf
LogLevel warn
SystemGroup sys root
# Allow remote access
Port 631
Listen /var/run/cups/cups.sock
# Share local printers on the local network.
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
<Location />
# Allow shared printing...
Order allow,deny
Allow all
</Location>
<Location /admin>
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
Edit02:
I should mention that I tried the fix described here: https://bbs.archlinux.org/viewtopic.php?id=146154
Deiderick: Have you "shared" your printer? I suspect that this may be what is causing the problem.
To Mods: At this point, because the OP's problem has been resolved, and this thread is marked "solved" should I make a new thread? It is possible that my problem is not identical to the OP's.
As a side note, I ran "journalctl | wc -l" it took about a minute of maxing out one core to finish. The final number: 1232889. I have a feeling that this reflects only a fraction of the warnings that cups produced, seeing as I only allocated limited hd space for journal messages.
Edit03: After re-reading the etiquette thread, I've decided to start a new thread. This one is marked "solved" and although very similar, it may not be exactly the same problem that I am having.
Last edited by Convergence (2012-09-23 00:28:14)

[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] 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] writing systemd service file to run script

i have completely migrated to systemd. now, i am trying to write a service file to run a startup script (~/.startup.sh). one of the functions of the script is to set the brightness of the screen:
echo "95" > /sys/class/backlight/intel_backlight/brightness
i created /etc/systemd/system/startup.service:
[Unit]
Description=Run startup script
[Service]
Type=oneshot
ExecStart=~/.startup.sh
[Install]
WantedBy=multi-user.target
but i get the following error:
Failed to issue method call: Unit startup.service failed to load: Invalid argument. See system logs and 'systemctl status startup.service' for details.
i have two questions:
1. what am i missing?
2. how can i avoid permission issues associated with modifying the brightness file (e.g., permission denied errors, the need to put in the password, etc.)?
thanks.
Last edited by anti-destin (2012-08-01 22:26:04)

thanks for the replies.
just a note: using an absolute path didn't fix the issue.
but i went ahead and created the file /etc/tmpfiles.d/backlight.conf:
w /sys/class/backlight/intel_backlight/brightness - - - - 95
and that worked.
is there a reason for recommending using a tmpfile rather than a service?
in any case, i'm marking this as solved.

[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] [Systemd] Systemd PKGBUILD on i686 (in a VM) - Linker failure

Similar Messages

Maybe you are looking for