Systemd & systemd-sysvinit : 207-5 208-1 | unable to hibernate

Hi !
After the update of systemd and systemd-sysvinit from v. 207-5 to v. 208-1, I'm experiencing an issue with xfce4-power-manager which cannot detect the ability of the computer to hibernate and so it desactivates the option (despite pm-hibernate works very well).
The only solution I've found is to downgrade these two packages, and everything runs smooth.
Is somebody experiencing the same issue and is there an obvious workaround I missed ?
SilverWyrda

Hi !
@venam : Yes, it seems to be a linked issue...
@Jristz : I've the option to hibernate too only in the "Buttons" menu on the XFCE panel. However, the option is grayed out under the xfce4-power-manager menu, which also control for me the hibernate shortcut... I use polkit-gnome and I've tried lxpolkit but it was a bad experiment insofar as I've not been able to mount some partitions from thunar anymore so... (and typing the password to hibernate . . . ).
Thanks to you for your answers .
Last edited by SilverWyrda (2013-10-11 17:33:55)

Similar Messages

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] Unable to hibernate (and garbles the screen when it fails)

Hello, I'm unable to hibernate (but I can suspend fine).
When I run
sudo systemctl hibernate
it will run the command, turn off the screen and come back all garbled (like static from a tv), with the computer still on but the processes stopped.
I followed all the instructions on the hibernation wiki.
I rebuilt grub adding the swap partition and added the resume hook to mkinitcpio.
My swap partition is 23.4GB and my ram is 16gb, so that shouldn't be an issue.
I've had a look at my xorg logs, run systemctl --all | grep errors with nothing, and nothing came up from the system journal ( I forgot the command as it was deleted from my bash history).
What other logs can I provide to help determine the error?
Thanks
edit:
It's been solved now, I believe an update to the kernel has done the trick. I can suspend to disk fine now.
For those googling, I'm running 3.11.6-1-ARCH
Last edited by lugubrious (2013-11-13 00:21:27)

Still nothing unfortunately.
I masked alsa90 under /etc/pm/sleep.d to be -x. That was the only file out of the pm directories. (I only have it for KDE too).
I've also double checked my grub config to add resume, and mkinitcpio which has the resume hook.
This is the relevant part of journalctl, this is when I run sudo systemlctl hibernate
Oct 16 15:36:08 arch64 sudo[2228]: lugub : TTY=pts/0 ; PWD=/home/lugub ; USER=root ; COMMAND=/usr/bin/systemctl hibernate
Oct 16 15:36:08 arch64 sudo[2228]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 16 15:36:08 arch64 systemd[1]: Cannot add dependency job for unit xscreensaver.service, ignoring: Unit xscreensaver.service failed to load: No such file or directory.
Oct 16 15:36:08 arch64 systemd[1]: Starting Sleep.
Oct 16 15:36:08 arch64 systemd[1]: Reached target Sleep.
Oct 16 15:36:08 arch64 systemd[1]: Starting Hibernate...
Oct 16 15:36:08 arch64 kernel: PM: Hibernation mode set to 'platform'
Oct 16 15:36:08 arch64 systemd-sleep[2231]: Suspending system...
Oct 16 15:36:08 arch64 slim[340]: (II) AIGLX: Suspending AIGLX clients for VT switch
Oct 16 15:36:08 arch64 kernel: PM: Marking nosave pages: [mem 0x00092000-0x000fffff]
Oct 16 15:36:08 arch64 kernel: PM: Marking nosave pages: [mem 0xcfda0000-0xffffffff]
Oct 16 15:36:08 arch64 kernel: PM: Marking nosave pages: [mem 0xc4000000-0xc7ffffff]
Oct 16 15:36:08 arch64 kernel: PM: Basic memory bitmaps created
The error with xscreensaver service comes up when I sleep, (and run xscreensaver lock && suspend), but I can sleep fine with it.
Oct 16 15:57:07 arch64 systemd[1]: Cannot add dependency job for unit xscreensaver.service, ignoring: Unit xscreensaver.service failed to load: No such file or directory.
Oct 16 15:57:07 arch64 systemd[1]: Starting Sleep.
Oct 16 15:57:07 arch64 systemd[1]: Reached target Sleep.
Oct 16 15:57:07 arch64 systemd[1]: Starting Suspend...
Oct 16 15:57:07 arch64 systemd-sleep[559]: Suspending system...
Oct 16 15:57:07 arch64 kernel: PM: Syncing filesystems ... done.
Oct 16 15:57:07 arch64 kernel: PM: Preparing system for mem sleep
Oct 16 15:57:08 arch64 slim[341]: (II) AIGLX: Suspending AIGLX clients for VT switch
Oct 16 15:57:17 arch64 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Oct 16 15:57:17 arch64 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 16 15:57:17 arch64 systemd[1]: Time has been changed
Oct 16 15:57:17 arch64 systemd[446]: Time has been changed
Oct 16 15:57:17 arch64 systemd-sleep[559]: System resumed.
When I ran pm-hibernate as suggested above it didn't suspend either, but this came up on journalctl
Oct 16 14:37:03 arch64 kernel: PM: Cannot find swap device, try swapon -a.
Oct 16 14:37:03 arch64 kernel: PM: Cannot get swap writer
Any ideas? Thanks
Last edited by lugubrious (2013-10-16 03:28:19)

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

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

Portege M300 - unable to hibernate or standy-by.

Hi,
I have very strange problem with my 2,5 years old Portege M300. For some time now I cannot hibernate or put it in stand-by mode. Everything goes as it should, "going to stand by" windows appears and computers dies, hdd led blinks every 10 seconds and nothing happens even if wait for hours.
It is the same with hibernation. It also sometimes happends that computer dies in similar way during regular job.
It almost looks like the hdd stopped working. I have done some basic hdd testing and it looks like everything is ok.
Do you have any ideas what could be the reason?
Regards
Blazej

Hi
When did you reinstall the OS?
Possibly its only a OS issue I mean its possible that your OS is muddled up and therefore some functions dont work as it should
At the other hand a hardware issue (i.e. HDD, memory) could be also possible.
But first of all if would be interesting to know if the notebook would functions after recovering.
Bye

Unable to Hibernate my U410

Hi!
I've tried many ways, and I can't get the hibernate option out of my U410
Scenario:
1) I have installed a fresh Windows 7 Professional OS due to school requirement of the OS and changed a new MSATA SSD TO 128GB as I hope to get more spaces for my storage, and after installation I realized that the hibernate button(MOST IMPORTANT FUNCTION) is missing!
2)I've tried many ways to get it up(powercfg, create hibernation partition(8192mb)) but it is still not appearing.
3) I've seen many discussed that I can go to the BIOS setting to enable the function, but I can't seem to find the option to do so!
So Hoping someone could help me over here!!
Thank You!
Solved!
Go to Solution.

Did you install energy management software and the vga drivers properly? Please do so!! See if it hibernates after that.
Ishaan Ideapad Y560(i3 330m), Hp Elitebook 8460p!(i5-2520M) Hp Pavilion n208tx(i5-4200u)
If you think a post helped you, then you can give Kudos to the post by pressing the Star on the left of the post. If you think a post solved your problem, then mark it as a solution so that others having the same problem can refer to it.

Unable to hibernate to disk

I installed and confugured Uswsusp according to the steps given at
http://wiki.archlinux.org/index.php/Suspend_to_Disk
When I fire the hibernate command ...it seems that it takes the memory dump on to the swap partition /dev/sda7.
But when I tried to resume it failed, the message displayed on the screen were like:
Invalid resume device swap:/dev/sda7
kinit: No resume Image , trying normal boot
And the normal boot is successful
Then I changed the the resume option in menu.lst to resume=/dev/sda7 instead of resume=swap:/dev/sda7
Now the messages while booting were
kinit: No resume Image , trying normal boot .
And the normal boot is successful.
My etc/suspend.conf is
# major 10, minor 231.
snapshot device = /dev/snapshot
# Set this to whatever your suspend partition is.
# You will not need to provide a resume parameter to your
# kernel when using uswsusp, as this file will be used.
# This neccesitates using a initrd, though!
resume device =/dev/sda7
compress = y
#image size = 350000000
#suspend loglevel = 2
#compute checksum = y
#early writeout = y
# You can only change these if you modified Makefile.diff
# and have the requirements installed.
#splash = y
#encrypt = n
Can smbdy please help ?

What command are you using to hibernate... The uswsusp command is s2disk which needs to be executed as root. IF you're using KDE and Gnome to hibernate, and you just choose an option from the menu, it is possible that some other hibernate command is executed that way, which would produce the symptoms you describe.

Unable to hibernate win xp (857 bios 1.8)

i flashed new 1.8 bios (over 1.6) because i wanted to test raid 1 on ich5. went all fine but now i cant hibernate winxp anymore. xp freezes with message box 'preparing to hibernate'. this was an issue up to bios 1.4 or so with 1 gb ram but was runing fine with 1.5 and 1.6..
any ideas?

i flashed new 1.8 bios (over 1.6) because i wanted to test raid 1 on ich5. went all fine but now i cant hibernate winxp anymore. xp freezes with message box 'preparing to hibernate'. this was an issue up to bios 1.4 or so with 1 gb ram but was runing fine with 1.5 and 1.6..
any ideas?

Unable to Hibernate my T60

Hi There,
Whenever I try to hibernate my T60, it goes into hibernation for a few seconds and comes out of it in a flash. I get an error message "Insufficient System Resources" in the system tray.
I was going through this post of "icantux" and I must say it makes perfect sense. However, in my case, I have 30GB of hard disk space in my primary partition out of which 13GB seems to be free.
My question is:
1. Is this space not enough yet?
2. Is there something else to this hibernation other than the disk space that counts?
My IT admin is clueless about what is causing this problem. With the same ghost image installed in other T60s, the hibernation works great. This leads me to believe that a software/driver conflict can't be a root cause for this.
I'll be glad if someone could help me out here. This is a wonderful community and there is enough reasons to spend a whole day on it learning some interesting things.
Thanks,
Venkstein
Solved!
Go to Solution.

Hi Venkstein,
Welcome to the Lenovo forum
This is just a guess, but have you added RAM to your system? If so, perhaps the hibernation file is too small to hold the memory image. You might try disabling then re-enabling hibernation (through Fn-F3 / PowerManager or the Windows CP) to delete, then re-create the hibernation file.
Good luck!
-Frank
Results of Your Ideal Business-Class Laptop survey, concluded 2009-07-29.
Did someone help you?
Say thanks! with a kudo.
Even better: Pay it forward, help someone else.

[SOLVED] systemd 207, lvm2 and luks booting issue

Hi
i'm using an encrypted lvm (luks) on my notebook.
/boot on /dev/sda1
lvm on /dev/sda2
main-root
main-home
main-swap
since the systemd 207 upgrade i am unable to boot my system.
this error appears at startup:
A start job is running for dev-mapper-main\x2droot.device
so i'm guessing that systemd is unable to use the encrypted lvm2, since this error is aknowledged on the
after checking some threads i tried:
mkinitcpio -p linux
but there was no effect.
HOOKS="base systemd autodetect block keymap encrypt lvm2 filesystems fsck vbox
some people tried suggesting downgrading to systemd 204 but i dont have any pkg file and building with abs leads to the following error
while makepkg -s:
==> Starting prepare()...
patching file src/core/swap.c
Hunk #1 FAILED at 220.
1 out of 1 hunk FAILED -- saving rejects to file src/core/swap.c.rej
==> ERROR: A failure occured in prepare().
Aborting...
am i supposed to remove the patches from the build? i'm not really sure and more of a beginner in this area.
Can anyone help me solve either the build or the boot issue ?
i should mention that i am only able to access my system by using chroot from an arch boot stick.
Thank you so much.
Kind Regards
Last edited by ziv667 (2013-10-01 11:27:06)

https://wiki.archlinux.org/index.php/Mk … mmon_hooks
systemd: This will install a basic systemd setup in your initramfs, and is meant to replace the 'base', 'usr', 'udev' and 'timestamp' hooks. Other hooks (like encryption) would need to be ported, and may not work as intended. As of systemd 207, this hook does not work as intended when combined with lvm2 and may break your boot. You also may wish to still include the 'base' hook (before this hook) to ensure that a rescue shell exists on your initramfs.
Have you tried keeping udev instead of replacing it with systemd hook?
Have you tried https://wiki.archlinux.org/index.php/Ar … ck_Machine ? It has systemd 204.
Last edited by karol (2013-10-01 11:16:57)

Wrong defaults for sysctl -p since upgrade to systemd 207?

I've run into this when trying to increase the inotify watches limit following these instructions.
Since upgrading systemd to version 207 sysctl.conf no longer exists, so instead I've put the following line in /etc/sysctl.d/99-sysctl.conf:
fs.inotify.max_user_watches = 524288
But when running "sudo sysctl -p" I get the following message:
$ sudo sysctl -p
sysctl: cannot open "/etc/sysctl.conf": No such file or directory
This is because according to the man page for sysctl:
-p[FILE], --load[=FILE]
Load in sysctl settings from the file specified or
/etc/sysctl.conf if none given.
So, "sysctl -p" by default looks for the sysctl.conf file, which no longer exists in up-to-date arch boxes.
The solution of course is simply running:
sudo sysctl -p /etc/sysctl.d/99-sysctl.conf
But my question is, shouldn't "sysctl -p" look for settings files in /etc/sysctl.d and run all of them by default, instead of looking for a file which does not exist? (and that, even if it exists, will not be run on startup). From my understanding, "sysctl -p" is supposed to apply by default the same settings that will be applied on the next reboot.

@kaszak696: no, "sysctl --system" also gives an error message:
$ sudo sysctl --system
[sudo] password for amatriain:
* Applying /usr/lib/sysctl.d/50-coredump.conf ...
kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e
* Applying /usr/lib/sysctl.d/50-default.conf ...
kernel.sysrq = 16
kernel.core_uses_pid = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
* Applying /etc/sysctl.d/99-sysctl.conf ...
fs.inotify.max_user_watches = 524288
* Applying /etc/sysctl.conf ...
sysctl: cannot open "/etc/sysctl.conf": No such file or directory
Thanks for finding another example of sysctl wrongly assuming that sysctl.conf exists
I'll report the bug to upstream.

System crashed (unable to install systemd)

Hey guys,
I partially upgraded my system "my bad" and now i'm unable to access the system and i think it's a systemd related problem which i'm unable to fix so asking for help,
systemd: /usr/share/zsh/site-functions/_systemd exists in filesystem
systemd: /usr/share/zsh/site-functions/_systemd-analyze exists in filesystem
systemd: /usr/share/zsh/site-functions/_systemd-delta exists in filesystem
systemd: /usr/share/zsh/site-functions/_systemd-inhibit exists in filesystem
systemd: /usr/share/zsh/site-functions/_systemd-nspawn exists in filesystem
systemd: /usr/share/zsh/site-functions/_systemd-run exists in filesystem
systemd: /usr/share/zsh/site-functions/_systemd-tmpfiles exists in filesystem
systemd: /usr/share/zsh/site-functions/_timedatectl exists in filesystem
systemd: /usr/share/zsh/site-functions/_udevadm exists in filesystem
Errors occurred, no packages were upgraded.
getting whole bunch of these messages while installing systemd.

systemd installed but still not able to access the system.
On boot it shows
Unable to mount /dev/sda1
then it drops me into ramfs, where i unable to write anything(It hangs on me there)???

Systemd & systemd-sysvinit : 207-5 208-1 | unable to hibernate

Similar Messages

Maybe you are looking for