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

Similar Messages

[SOLVED, sort of] Yet another UEFI boot issue

Hello everyone,
Let me start by saying sorry for the long (first) post.
I've ended up with a UEFI boot problem I can't solve. I've searched the forum and internet and I realize I'm not the only one who ran into problems with UEFI. Unfortunately, the problems other have had seem not similar to mine. I've spent almost 2 days now trying to figure this out, and I'm getting nowhere (though I've learnt some more about UEFI, which I guess is good). I was hoping someone here can give me some hints on how to proceed.
So lets start with the background. I recently bought a new computer (Lenovo Thinkpad Edge E530 with Windows 8) and of course I want to run ArchLinux on it (been using ArchLinux for almost 7 years now and no plans on switching). Installation went ok with only a few problems during installation that I managed to solve (or so I thought). I must admit I didn't follow the guide fully. I didn't want to remove the Restore and Windows partitions, so I figured it would be safe to reuse the existing UEFI System Partition, as long as there was enough room, which there was. Anyway, I now have a computer I can boot into ArchLinux and also Windows 8, just the way I want it, almost. There is this one final issue I haven't been able to figure out how to solve.
The problem
Whenever I reset/power on the computer, I must press Enter during the initial screen (showing a Lenovo logo, and a message about pressing Enter to interrupt normal startup). If I don't press Enter before the timeout (a second or so), the screen will go white and that's it. No beep, no message, no nothing but a white screen. A power cycle is the only way to leave this state. Occasionally the screen will be a white bar at the top and random colours below, but I'm guessing this only represents what is in graphics memory at the time (0x00, 0xFF or any other random value).
If i do press Enter however, then I'm presented with a menu where I can select what to boot; rEFInd (which is preselected) along with Windows 8 and some restore and diagnostic entries. Pressing enter will take me to the preselected rEFInd, pressing enter again (or wait for timeout) will boot linux, and I'm in. Nothing weird there. And if I select Windows in rEFInd, then windows boot, just as expected.
There is no difference whether I'm switching from Windows to Linux or Linux to Windows or just reboot the same OS I was using again. The result is the same whatever I choose to boot.
So the question is: Why do I have to select rEFInd manually and go through all these menus? Should I not be able to just power it on and let it boot the preselected rEFInd entry and continue from there, without me helping it?
Trying to solve it
Searching here and on the internet gave me some ideas on what to try, so here is a list of my attempts:
efibootmgr show me there is a rEFInd entry, and that it is the first one in boot order
I copied refindx64.efi to /boot/efi/EFI/Boot/bootx64.efi (replacing an existing entry)
I've updated the EFI firmware (from Lenovo) to the latest and greatest
One other guy had almost the same issue, but with a single boot of Windows. He solved it with Microsoft Boot Manager (there is an Automatic Repair, or something). I even dared trying this, though I must admit I was a bit hesitant about letting some Microsoft program trying to repair my computer. Anyway, it said it couldn't repair my problem, nor did it say I had one, so I am none the wiser.
None of the above gave anything.
So, that's it. I guess I can live with having to press Enter on every power up/reset, but it is very annoying having to do so, and even more so when I forget it because then I'm forced to power cycle it. I hope someone reading this can figure out what's going on, because I am clueless.
Best regards,
Johan
Last edited by 6feet5 (2013-01-08 19:03:50)

WonderWoofy wrote:@srs5694, have you thought about filing a bug report/feature request about the naming scheme here? I would imagine that something coming directly from the upstream developer would be something that they should take into consideration. Also, I imagine that renaming it to refindx64.efi kind of goes against the whole "vanilla packages" thing we tout around here... so it really makes me wonder why it is done in the first place.
I've just done that:
https://bugs.archlinux.org/task/33326
It's not been very important until recently; but I've been putting a lot of effort into the ancillary support scripts (install.sh and mvrefind.sh). They necessarily rely on the files having certain names, so installing them under other names robs users of functionality.
6feet5 wrote:I've decided to try and restore the whole unit, thinking it would take maybe an hour or two. It's been running now for almost 3 hours and only completed 20%.
Good luck with that!
FWIW, it seems that the number of EFI-related bug reports on Linux forums has gone way up recently. No doubt this is because EFI is now pretty much universal on new computers, so problems that used to affect one or two people now affect dozens or hundreds, and some of those post about them.

H87M-G43 and automatic boot issues

I have an H87M-G43 and for 4 weeks have been struggling to get a new clean Windows 8.1 UEFI build on the PC without odd automatic boot issues.
Here is the PC configuration:
CPU Intel Core i5-4440 3.1GHz
PSU Corsair CX430
DIMM1:
DIMM2: Corsair XMS3 DDR3 4GB CMX4GX3M1A1333C9
DIMM3:
DIMM4: Corsair XMS3 DDR3 4GB CMX4GX3M1A1333C9
SATA Port 1: SSD Samsung 840 EVO 120GB
SATA Port 2:
SATA Port 3: HDD Samsung 1TB SATA II
SATA Port 4: HDD Samsung 1TB SATA II
SATA Port 5: DVD Liteon IHAS124-14 24X
SATA Port 6:
JAUD1: Coolermaster 352 Series Case Front I/O Intel HD Audio connector
JUSB1: Coolermaster 352 Series Case Front I/O USB 2.0 connector
JUSB4: Coolermaster 352 Series Case Front I/O USB 3.0 connector
BIOS v1.6:
01. F6 Restore Defaults: Load Optimized Defaults
02. SATA Mode: [RAID Mode]
03. SATA3 Hot Plug: Enabled
04. SATA4 Hot Plug: Enabled
05. Initiate Graphics Adapter: IGD
06. Serial(COM) Port 0: Disabled
07. Parallel(LPT) Port: Disabled
08. Windows 8/8.1 Feature: Enabled
09. Resume From S3/S4/S5 by USB Device: Enabled
10. GO2BIOS: Enabled
SATA Port 3+4 RAID1 (Mirror)
Windows 8.1 UEFI installation
Install Windows Update:
1. Important Updates
2. Recommended Updates
3. Optional Updates
Install MSI Drivers/Software:
01. Intel Chipset Driver 9.4.0.1026
02. Intel SVGA Driver 10.18.10.3412
03. Realtek PCIE Network Drivers 8.23.11.26.2013
04. Intel RAID Driver 12.9.0.1001
05. Realtek HD Audio Drivers 6.0.1.7111
06. MSI Wallpaper
07. Intel AMT Driver 9.5.15.1730
08. Intel SBA 2.2.39.7991
09. Intel Smart Connect Technology 4.2.40.2418
10. Super Charger 1.2.020
I have not configured any of the Intel Management and Security, Small Business Advantage, Smart Connect software, just installed them.
The issues I get are:
1. JUSB1 connected and Resume From S3/S4/S5 by USB Device: Enabled in BIOS. When I shutdown the PC, it automatically boots 2-3 seconds later. If I set Resume From S3/S4/S5 by USB Device: Disabled or disconnect the JUSB1, the PC shutdown is fine.
2. Once the PC is shutdown OK, PC boots itself several hours later. Yesterday at 15:50pm PC was shutdown. At 21:18pm, PC automatically booted itself.
This is my first MSI and UEFI motherboard. What I would like is some advice on setting up the BIOS and the software to get sleep/hibernate working and no automatic boots.
I have contacted MSI regarding these issues, but they say they cannot reproduce them. I have subsequently googled these issues and of course, other MSI users are experiencing similar problems, but there are no obvious resolutions. Please can anyone help/advise?

Hi,
I have the MSI Z87-GD65 Gaming mobo and perhaps similar problem as discussed in this thread.
I wanted to be able to wake my PC from sleep mode via my USB connected mouse and keyboard. Therefore I went into BIOS and set the "Resume from S3/S4/S5 by USB Device" to "Enabled". And yes, now it is possible to wake my PC from sleep mode by just clicking any button on my keyboard or just moving my mouse a little bit. So far so good. BUT, another feature was also added which I did not want to have: By just clicking any button on my keyboard or moving my mouse a little bit the PC also started after I have "shut it down"! This could seem as the PC boot by itself but it does not, I have to move the mouse just a little bit (by accident for example when needing more space on my desk) or clicking a button on the keyboard. I THINK THE ROOT CAUSE TO THIS PROBLEM IS AS FOLLOWS: In BIOS, it says "Resume from S3/S4/S5 by USB Device". Instead it should only be "Resume from S3 by USB Device". S3 is the same as "Sleep" and S5 is the same as "Soft off" = PC shutdown. Do you understand what I mean? When I shut down my PC it is put into state “S5”. (NOTE: I have another PC with MSI Z77-GD65 and here it only says "Resume from S3 by USB Device" and no problem with any starting of that PC via USB device from a shutdown state, it only starts from the sleep state (=”S3”) as I want. How do I get rid of the "S5" state in BIOS for this USB wake up feature? (Btw "S4" is hibernate state which is not the same as a shutdown PC, therefore not causing this problem.)
ADDED No. 1: Please read msdn.microsoft.com/en-us/library/windows/desktop/aa373229(v=vs.85).aspx for explanation of the different system Power states I mention above.
ADDED No. 2: My Click BIOS version is 1.8 for Z87-GD65 with release date 2013-12-06. On a Youtube video I have seen that version 1.0 of this BIOS has Wake up "Resume from S3 by USB Device" and not ...S3/S4/S5...

Lvm2 on LUKS @ boot time: volume group found but not importing

I have so far succeeded in making ArchLinux boot as far as properly asking for my encrypted partition's passphrase and unlocking the encrypted partition (/dev/sda2) whererein lies the root filesystem; the encrypted partition contains a lvm2 group that has logical volumes on it for swap and root. However, instead of importing the group, it simply acknowledges that one exists;
:: Running Hook [lvm2]
Scanning logical volumes...
Reading all physical volumes. This may take a while...
Found exported volume group "crypt" using metadata type lvm2
Activating logical volumes...
Volume group "crypt" is exported
Waiting 10 seconds for device /dev/mapper/crypt-root ...
Root device '/dev/mapper/crypt-root' doesn't exist. Attempting to create it
Should I just increase timeout (and how do I?), or is there something else I must enable? The last 4 of my hooks are (and I know them by heart at this point): usbinput encrypt lvm2 filesystems. I do not have
I am at my wits' end. I've tried everything from different mount points in fstab (i.e. /dev/crypt/root instead of /dev/mapper/crypt-root) to putting the encrypted partition in /etc/crypttab to changing the order of "root=" and "cryptdevice=" in the kernel parameters in menu.lst, and this is as far as I have gotten.
Last edited by deconstrained (2010-11-18 11:33:47)

In https://bbs.archlinux.org/viewtopic.php?id=164267
there is a similar issue of today, but with a UUID naming instead of a label. Maybe you want to try the workaround described there with an udev-rule. If you re-typed the kernel line, please double-check it (asking that because you have lvm and LVM in there).
What's the problem with the "block" hook for you regarding the partition size?
The initramfs does not fit with the block hook? I'm asking that too, because the "block" hook includes the old "usb" one.
Is the usb-stick there at "/dev/disk/by-label/MARTINC" after boot?

[SOLVED]systemd: help on executing oneshots, timing issues

Hi,
I have problems with systemd. I want to upload a firmware to my bluetooth adapter which needs the device already created by bluetoothd. I made the service file /usr/lib/systemd/system/fw-upload-bcm20702a0.service
Unit]
Description=uploading firmware to BCM20702A0 buetooth adapter
Requires=bluetooth.service
After=bluetooth.service
[Service]
Type=oneshot
ExecStart=/usr/bin/brcm_patchram_plus_usb --patchram /lib/firmware/BCM20702A0_001.001.024.0156.0204.hcd hci0
[Install]
Alias=fw-upload-bcm20702a0.service
WantedBy=graphical.target
Manually executing this after system startup with
systemctl start fw-upload-bcm20702a0.service
works. But during system startup I get this error:
[root@gruenix ~]# systemctl status fw-upload-bcm20702a0.service
fw-upload-bcm20702a0.service - uploading firmware to BCM20702A0 buetooth adapter
Loaded: loaded (/usr/lib/systemd/system/fw-upload-bcm20702a0.service; enabled)
Active: failed (Result: exit-code) since Mo 2013-04-15 10:39:15 CEST; 36s ago
Process: 1273 ExecStart=/usr/bin/brcm_patchram_plus_usb --patchram /lib/firmware/BCM20702A0_001.001.024.0156.0204.hcd hci0 (code=exited, status=1/FAILURE)
Apr 15 10:39:15 gruenix brcm_patchram_plus_usb[1273]: device hci0 could not be found
Apr 15 10:39:15 gruenix brcm_patchram_plus_usb[1273]: option patchram with arg /lib/firmware/BCM20702A0_001.001.024.0156.0204.hcd
Apr 15 10:39:15 gruenix systemd[1]: fw-upload-bcm20702a0.service: main process exited, code=exited, status=1/FAILURE
Apr 15 10:39:15 gruenix brcm_patchram_plus_usb[1273]: hci0
Apr 15 10:39:15 gruenix systemd[1]: Failed to start uploading firmware to BCM20702A0 buetooth adapter.
Apr 15 10:39:15 gruenix systemd[1]: Unit fw-upload-bcm20702a0.service entered failed state
The error indicates that the device hci0 is not created in time. But what else can I do to assure that?
Harvey
Last edited by Harey (2013-08-14 09:49:22)

Today I revisited my problem and solved it. Just in case anybody is interested in the solution:
Preface: You need 2 small packages for this to work
1. hex2hcd - converts a hex file extracted from the windows driver package to hcd format
2. brcm_patchram_plus - a tool from broadcom to upload firmware files into the usb adpater
I made to AUR packages for convenience:
https://aur.archlinux.org/packages/?O=0&K=hex2hcd-git
and
https://aur.archlinux.org/packages/brcm … _plus-git/
Then you convert your windows firmware file to hcd format with hex2hcd and store it as /lib/firmware/fw-{vendor_id}_{device_id}.hcd (in my case: /lib/firmware/fw-0489_e031.hcd).
Now for the tricky part part: Create a script like this (improvements and comments welcome):
#!/bin/bash
# BCM20702A0 BT Adapter upload rampatch
# env Variables
logfile=/var/log/rampatch.log
# logfile check
if ! test -f ${logfile} ; then
# logfile does not exist, so create it
touch $logfile
fi
echo "-------------------------------------------------------" >> $logfile
entrytime=$(date +"%Y-%m-%d %H:%M:%S")
echo $entrytime " applying rampatch to BCM20702A0 bluetooth adapter" >> $logfile
# wait for hci0 to become available and usable
sleep 1
/usr/bin/brcm_patchram_plus_usb --patchram /lib/firmware/fw-0489_e031.hcd hci0 >> $logfile
entrytime=$(date +"%Y-%m-%d %H:%M:%S")
echo $entrytime " ..done" >> $logfile
echo "-------------------------------------------------------" >> $logfile
(This one writes to a logfile in /var/log/ for easier debugging)
This has to be triggered by systemd, so we need a service file /etc/systemd/system/loadfw.service:
[Unit]
Description=Load firmware into BCM20702A0 bluetooth USB adapter
After=basic.target
After=suspend.target
After=hibernate.target
[Service]
Type=oneshot
ExecStart=-{put your script location here}start_BCM20702A0.sh
[Install]
WantedBy=basic.target
WantedBy=suspend.target
WantedBy=hibernate.target
Enable it via
systemctl enable loadfw.service
and bazinga - the firmware gets loaded at every boot, suspend and hibernate.
Harvey

[solved] systemd services not starting at boot (or at all)

On my router, some systemd services fail to start at boot.
The services are :
adsl (pppoe connetction on the wan interface)
shorewall (funny again for a router)
logind (brings up only tty1, and not the others with a 'timeout' error)
adsl starts fine manually after booting up
the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
I really don't know, what happened to logind...
Last edited by scar (2012-11-30 10:20:44)

cups: avahi client failed
adsl: timeout (ppp0 running on eth0, the service did not found eth0)
shorewall: did not work by the systemctl command, only with the old rc script
I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
since this was a very old install (but up to date), I've decided to reinstall the whole thing,
Everything works
(But reinstalling does not solve any problem, it erases the problems...)
Last edited by scar (2012-11-30 10:21:20)

Touchpad and CD-Boot issues since 10.5.6

Hello *,
since I updated to 10.5.6. I am having strange problems. I have to deactivate the touch pad, otherwise, when I use it, the left mouse button functionality *also of the USB or MightiMouse* is not working anymore. Second problem: no boot from CD via pressing and holding c or d anymore. I can hold option and select the boot device, but I can not run e.g. the hardware test tool from the original installation cd and I also can not reinstall firmware - cd will be ejected. The problem was even worser, but after all kinds of troubleshooting - this is the current status. I reset PRAM and SMC several times, I reinstalled 10.5.6 combo update 2 times. I reinstalled from Leopard CD, I installed from TimeMachine Backup. I assume that something is wrong with my firmware / EFI since the update but there is no possibility to fail back or reinstall, because I can not boot from cd with c or for firmware upgrade via holding down power button. I have no idea what else I could try. Any tips?

I checked already, and there is no cable problem. The prove for this is also that it works for a short time under certain conditions. Then it looks like touchpad starts to send endless left-clicks, which blocks other left-clicks. Disabling the touch pad let me use my mighty mouse, which is also bad, because I usually never use it with my MacBook. If you disable it in system preferences, using your keyboard (which is a pain when you are not used to it - also check if keyboard-mouse is enabled) - you should be able to use a external mouse device. I read somewhere that booting into hardware-test tool can solve the problem. Unfortunately I'm not able to try this, because boot with 'd' or 'c' does not work (fortunately booting with alt and choosing the boot device works, but this does not allow you to start hardware-test.) It would be good to know if there is another possibility to start hardware-test or even better - to flash EFI. Even this does not work (holding down powerbutton during start up with inserted EFI-CD) - the CD will be ejected without any effect. Very strange...
BTW: I searched the web about this issue too, and I saw many other people having similiar problem with all kind of Macs with booting from cd, or problem with left mouse - even in this forum. Does not look like a pure MacBook problem for me...
Message was edited by: 23r0

[Solved] Systemd user service and timer dbus error

I have installed arch recently and added a few of my own services, for example the acpi_call commands and such. Now I want to create a systemd service that runs every 5 minutes and execute a script.
I searched a lot and I found that I must use timers. I got the thing with the timers working, but because my script has to do with a specific user, I want it to run only every 5 minutes when i am logged in as that user.
I tried to put the files in /etc/systemd/users, .config/local/users and all the possibilities but everytime i want to enable it, it says dbus connection refused.
Can somebody please provide me a way to execute a systemd service every 5 minutes while I am logged in as a specific user?
I did follow the wiki and created a dbus service and all. Everything works on that side but i can't enable my user service.
thanks!
Last edited by nopemopes (2015-03-25 11:10:06)

jasonwryan wrote:
What errors are you getting? https://bbs.archlinux.org/viewtopic.php?id=57855
Not a Sysadmin issue, moving to NC...
sorry, didn't mean to be incomplete.
The error says "Failed to get D-Bus connection: Connection refused".
I did what the wiki said: Create the dbus files, enable them and such.
No i put my service files + timer in the places mentioned by the wiki but everytime i try to enable them, that error shows up.
systemctl status dbus gives me all good
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
Active: active (running) since ma 2015-03-23 19:39:24 CET; 1h 18min ago
Docs: man:dbus-daemon(1)
Main PID: 246 (dbus-daemon)
CGroup: /system.slice/dbus.service
└─246 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
that's the log for dbus and these are my files:
drive_sync.service
[Unit]
Description=Drive sync
[Service]
Type=simple
ExecStart=drive_script.sh
drive_sync.timer
[Unit]
Description=Drive sync
[Service]
Type=simple
ExecStart=drive_script.sh
these files are located in ~/.config/systemd/user
Last edited by nopemopes (2015-03-23 20:00:55)

[SOLVED]systemd-fstab-generator and syslog error?

here is the bootup error message:
Nov 2 07:27:58 localhost [ 9.207762] systemd-fstab-generator[151]: Failed to create unit file: File exists
Nov 2 07:27:58 localhost [ 10.119699] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
Nov 2 07:27:58 localhost [ 10.544789] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 07:27:58 localhost [ 10.544974] systemd[1]: Failed to listen on Syslog Socket.
and my fstab is here:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb5 / jfs defaults 0 1
/dev/sdb6 /home ext4 defaults,user_xattr 0 1
/dev/sdb7 /var reiserfs defaults 0 1
/dev/sdb8 /tmp reiserfs defaults 0 1
Last edited by frat (2012-11-02 03:21:07)

systemd-fstab-generator is fixed,thank you.
syslog errors still:
Nov 2 10:29:44 localhost [ 10.051816] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 10:29:44 localhost [ 10.052000] systemd[1]: Failed to listen on Syslog Socket.
#systemctl status syslog
syslog.service
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)
#systemctl status syslog.socket
syslog.socket - Syslog Socket
   Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static)
   Active: inactive (dead)
   Docs: man:systemd.special(7)
   http://www.freedesktop.org/wiki/Software/systemd/syslog
   CGroup: name=systemd:/system/syslog.socket
any advice?
Last edited by frat (2012-11-02 02:56:37)

[Solved] systemd creates autofs after unmounting /boot

After logging in, i unmount /boot, so that i can unplug the usb drive where it resides, then systemd creates this mount:
# mount | grep /boot
systemd-1 on /boot type autofs (rw,relatime,fd=26,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
Typing this hangs forever:
ls /boot
/etc/fstab
UUID=2D75-67FC /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,nodev,nosuid,noexec 0 2
I don't really know what to make of this. Seems like a bug, given that ls hangs forever instead of showing nothing.
Last edited by teateawhy (2014-09-12 10:48:38)

My bad, i really masked the mount unit. Will try again tomorrow.
EDIT:
After masking the automount unit, it looks like this:
* /boot is mounted correctly at startup
* after unmounting /boot manually, no autofs mount shows up anymore
* ls does not hang and immediatly shows nothing, as expected
# systemctl status boot.automount
● boot.automount
Loaded: masked (/dev/null)
Active: inactive (dead)
# mount | grep /boot
(No output)
Last edited by teateawhy (2014-09-12 10:16:50)

DKA790GX Platinum SOLVED (backward FP connector and IGP driver issues)

Hi all. I just got my DKA790GX Platinum along with the rest of my new PC parts yesterday and got it all up and running last night with Vista Ultimate x64. So far everything runs smooth as silk except for a couple small hiccups...
1: The power LED doesn't light up. My front panel wires only have a 3 pin connector, so I'm using the 3 pin spot on JFP2 with the arrow on the connector on the + pin. SOLVED: Connector from the front panel was wired backward. Put the arrow to - and it worked perfectly!
2: the HD3300 onboard video seems limited to 1440x900 pixels resolution. My monitor supports 1680x1050, which I was running on my old computer with a radeon x1650xt. Since most of the reviews I'd read placed the HD3300 between the HD2xxx and HD3xxx series for performance, I figured it'd be a better card than the x16xx series. In this respect I guess not unless anyone has a way to enable higher resolutions on it. SOLVED: Installed the latest catalyst drivers from ATI for the HD3400 series and in the advanced control center under Monitor Properties 0 -> Attributes unchecked Use Extended Display Identification Data (EDID) or driver defaults then manually set my maximum resolution and refresh rate to those of my monitor. After this in the advanced control center under Display Options I was able to set my desktop area and refresh rate to the correct numbers.
3: Initially I was getting awful frame tearing or interlacing of some sort on video playback, including both DVDs and video files like AVI. This I was able to resolve by disabling Aero but I'd think there should be a better solution for such low intensity usage. I never had this problem on the x1650xt in XP. SOLVED: Installed the latest catalyst drivers from ATI for the HD3400 series and in the advanced control center under Monitor Properties 0 -> Attributes unchecked Use Extended Display Identification Data (EDID) or driver defaults then manually set my maximum resolution and refresh rate to those of my monitor. After this in the advanced control center under Display Options I was able to set my desktop area and refresh rate to the correct numbers.
Any ideas for any of these problems would be much appreciated!
Current system specs:
Mainboard: DKA790GX Platinum
CPU: Phenom 9950 Back box
RAM: 4GB OCZ 1066
Sound: Auzentech X-Meridian 7.1
HDD: Samsung 1TB SATA2
Chassis: Thermaltake Armor+MX
PSU: Antec 430w (will be replaced with a higher wattage supply when I have the money but works for now)
Monitor: Samsung 225BW (22" widescreen)
I'm using all the latest drivers from the MSI web site for the motherboard, and from the manufacturer websites for sound and monitor.

Yes, I downloaded the latest Samsung 225BW drivers from their web site though I find it questionable as to whether they're functioning properly or not; Adobe Photoshop CS3 gives an error on startup saying the monitor's color profile is corrupt. My guess is the drivers aren't fully compatable with Vista x64.
Meanwhile I got my replies from MSI, both from the customer service form which I filled out first, and the technical support form which I'd found shortly after submitting the first ticket. I've never gotten two such vastly different yet both so woefully inadequite answers from a company in my life
Tech Support's answer:
Quote from: MSI Tech. 11/06/2008
There is no problem with the on board HD3300 VGA which can support the full 1080P resolution which be sure to have the latest mb bios and a fresh/clean OS installation and follow by updated system and device drivers installation which there is no problem to support the 1680x1050 when the monitor can support it: http://global.msi.com.tw/index.php?func=downloaddetail&type=driver&maincat_no=1&prod_no=1552 ** http://global.msi.com.tw/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1552
Customer Service's answer
Quote
Dear customer,
The onboard VGA performance is lower than external VGA. It is normal.
Best regards
MSI technical support team
Tech support while correct didn't tell me anything I didn't already know, and the broken english is difficult to read. The customer service answer is ridiculously false, I have to wonder if this employee ever bothered to look up the answer (yes an IGP is typically less powerful than a discreet video card but the goals I was after were well within the card's capabilities. The fact that I was able to resolve the issues proves that). I hold MSI hardware in very high esteem. I've never had a problem with an MSI product that wasn't caused by another part failing (my K9N-Neo F in my previous computer popped a cap in the northbridge when the PSU blew out, and my wife had an MSI board literally melt a few years back in a power surge, neither was MSI's fault) but my estimation of their customer support has dropped a few notches today.
To sum this entire experience up though; this is simply one of the newer MSI boards on the market and it hasn't had a long time for drivers to be perfected. The ATI drivers work slightly better for now. As for how I figured it out, I read a review on the board somewhere (maybe newegg since that's where I bought it) that mentioned the catalyst drivers from ATI have had the HD3300 in them for a few months now even though it's not linked directly on their site yet. I figured the HD3400 would be worth a try. :D
In an unrelated topic, I've got a new problem though I'm not sure if it's related to the board at all. For some reason Portal stutters awfully in full screen mode even with details turned way down. It runs fine in windowed mode. On googling it I found several other people on the net have had the same problem but no answers have been put forward that I've seen. As far as I can tell it's a DX9 emulation error in Vista x64 but no way to prove it and no ideas for a solution. Then again the IGP could simply be insufficient to power that game despite being nearly twice as fast as the x1650XT I'd been using in my previous machine....

MSI-KN8 neo4 Plat and windows booting issues...please help!!!

let me start with my system specs:
msi- 7125 plat KN8 (1B0 bios)
amd 64 3500 venice
1 GB (2 x 512 MB) corsiar valueselect (set at 2.5V)
antec neopower 480W
gigabyte nvidia 6600gt
(2) 80 GB maxtor sata150
250 GB maxtor sata150
zalman 7700 series cpu fan
sony dvd burner.
Thanx in advance for any and all help i am, hopefully about to receive. i read quite a few of previous threads and didnt find one with my issue.
HERE GOES...
this entire system was running with a different brand mobo (just upgraded to this msi-7125) and was running great!!
however when i installed windows xp media center edition 2005, things where working great. that is until i installed the nforce system drivers from the disk that MSI provided me. once i installed the ethernet driver,ide-sw driver, network controller the ask me for a reboot after install was done, when the system restarted i got all the way the windows xp splash screen or loading screen. at that point windows stops loading stays on the loading screen for about 10 minutes, then the computer shuts off.
i have tried running memtest and had no errors, im positive that my psu is capable of handling my components.
i'm really stuck on this one, any help would great thanx again!!!
Sam

You should be able to get into Windows through safe mode. From here uninstall the drivers and restart. You should hopefully be able to get into Windows normally now. Get hold of the latest drivers from the Nvidia web site and try them.
Also check both Ethernet controllers are enabled in the BIOS.

[SOLVED]systemd and make a camera visible GUI-wise in your filemanager

After reading a lot about systemd in the wiki and in this forum I understand there are different opionons about systemd. Anyway, I have a adapted all the changes to rc.conf leaving out only a few daemons to start there. So why not give systemd a try? If you dont want to read the full posting I finally got it to work, basically by reading carefully and checking the suggested tests in the systemd wiki. (loginctl)
As suggested by the wiki, I tried the systemd yesterday. Enabled via systemctl some services to "replace" my rc.conf daemons. I got what I thought everything to work, including autologin directly to my Xfce4 desktop. Everything except the digital camera.
When starting Arch traditionally via initscripts I immediately can see the camera in the filemanager (Nautilus) when the camera is attached via USB.
Some minutes later, after adding "init=/usr/lib/systemd/systemd" to the APPEND line in Syslinux and rebooting, my machine reboots
fine.But when connecting the camera again it is not visible graphically.
The camera is there because when using gphoto2 (the commandline) as root I can transfer pictures etc.
Even if I am no happy CLI user I can handle it when necessary. Handling pictures a graphical view of them is much easier...
As the wiki about systemd says one can try it out. I have not removed anything from the system and when starting Arch again, the initscript way, I can see the camera again in my filemanager, gthumb works again and pictures can be transferred to my machine.
In the wiki again, this time about digital cameras
Permission issues
Camera devices should be granted permission using ACLs. For this to work, users need to have consolekit or systemd running and the user session must be registered with them accordingly.
Check this using /usr/bin/ck-list-sessions to verify a value of "TRUE" should be returned for both the "active" and "is-local" fields:
$ ck-list-sessions | grep TRUE
active = TRUE
is-local = TRUE
ACL=Atlantic Container Line is what first comes into my mind. I have had some connections to transport business...I admit I had to google it to find the correct interpretation of this mumbo-jumbo.
The wiki also gives a "hint", if this is not working try to use the obsolete camera group and edit some udev rules.
Should not be necessary when it has worked before systemd and earlier experiences
But what is this about "Permission issues"? Here is my listings relative the wiki hints. All seems OK.. or why the heck are there two sessions??
[leif@krasaki ~]$ ck-list-sessions | grep TRUE
is-local = TRUE
active = TRUE
is-local = TRUE
[leif@krasaki ~]$ ck-list-sessions
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:12:56.499847Z'
login-session-id = '1'
idle-since-hint = '2012-10-24T07:13:26.994037Z'
Session2:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:13:02.361157Z'
login-session-id = '1'
[leif@krasaki ~]$
As one can see, the ACTIVE values are here as the wiki says. But no camera. Those values are the same, wheter which way the machine is started. But 2 sessions??
Further reading in the systemd wiki article and consolekit vs systemd.logind gives a clue.
From the wiki:
In order to check the status of your user session, you can use loginctl. To see if your user session is properly set up, check if the following command contains Active=yes. All polkit actions like suspending the system or mounting external drives with Udisks should then work automatically.
So when started via systemd and running logintctl, it gives this surprising result. Does not matter wheter as normal user, nor as root....
[leif@krasaki ~]$ loginctl
SESSION UID USER SEAT
1 1000 leif seat0
1 sessions listed.
[leif@krasaki ~]$ loginctl show-session 1
Id=1
Timestamp=Wed, 24 Oct 2012 10:57:03 +0200
TimestampMonotonic=20040019
DefaultControlGroup=name=systemd:/user/leif/1
VTNr=1
TTY=tty1
Remote=no
Service=login
Leader=315
Audit=1
Type=tty
Class=user
Active=no
State=online
KillProcesses=no
IdleHint=yes
IdleSinceHint=1351069009642296
IdleSinceHintMonotonic=6664433
Name=leif
[leif@krasaki ~]$
Surprising? Should it not have been Active=Yes? So something is wrong in my settings although it had worked "before" starting using systemd..
OK, so far. Lost? Not yet. Double check again everything and I found the culprit, my ~/.bash_profile which had worked before seemed a bit different to what is suggested in the wiki. The old one, actually started 2 sessions, as also could be seen here above checking ck-list-sessions. That was the problem
Using a fresh edited ~/.bash_profile as suggested here, the camera is visible graphically
Finally, just for fun, start again the old initscipt way. Enabling daemon and so on. Still 2 sessions going on....Here it was the "/.xinitrc, which also had some old fashions and I removed the ck-launch-session from the exec line. So even here, now only 1 session..
Anyway, now the camera is visible, both starting with initscripts, naturally also some daemons active in rc.conf and by starting with systemd.
I rest my case and it seems systemd works with everything on my machine which is just a normal desktop used by an old man.
Thanks for reading...

Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
if [ -s /etc/locale.conf ]; then
. /etc/locale.conf
fi
export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION

[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)Toshiba P850 UEFI and issues with bootloaders

So I've been using Arch for over a year and a half and have installed it on 10+ systems. I got a new laptop in January 2013 which has a UEFI motherboard (I hate Intel) And ive tried installing Arch from pure memory and also from the beginners guide, the first day I got the laptop I installed Arch in 15 minutes with NO issues, now all of a sudden when I boot into UEFI (For some reason legacy support which is called "CSM" Does not seem to work with Arch, so I must use UEFI, if you know a way around this let me know) on the live disk, install goes successful, but when I try and install GRUB (Not grub-legacy) it says "UEFI Commands are not supported on this device" I read the article in the wiki about starting the kernel module, and I did that, install went successful with GRUB and I was able to make my grub file install to /boot/efi/EFI/grub.cfg. When I try and boot up it takes me to a grub screen for about 2 seconds, then reboots, then shows grub for 2 seconds, then reboots, etc..... And the grub menu that pops up ONLY says "grub" twice, it doesn't display any information as to what its going to load, so it seems like it failed. I DID change the root directory which is sda4, and I still get this issue.
My partitions are:
sda1 /boot 300MB
sda2 /boot/efi 700MB
sda3 SWAP 2048MB
sda4 / (the remaining amount of my 1TB HDD)
Does anyone have any tips? I really need to get this working.
EDIT: Also, I have tried SysLinux as well, that didn't work either. I don't care what bootloader I use as long as it can boot Arch! Ive currently got Debian installed and for some reason that's failing as well, but that disables my screen due to a kernel issue, I see the module fail to load in SystemD with Debian and it goes out, so I need Arch. Debian isn't that great anyways IMHO
SOLVED: Just installed via CSM instead. Took me some work arounds but i finally got it installed.
Last edited by Kitkin15 (2013-12-20 07:43:32)

grub-install --target=x86_64-efi --efi-directory=/boot/efi/ --bootloader-id=grub --recheck --debug
It told me to do that HERE
First, mount the ESP at your preferred mountpoint (usually /boot/efi, hereafter referred to as $esp). On a first install, you will need to mkdir /boot/efi, if that's where you want to mount it.
Now, install the GRUB UEFI application to $esp/EFI/grub and its modules to /boot/grub/x86_64-efi:
# grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=grub --recheck --debug
The way I understand it is that I still needed /boot to be the MBR boot partition, then /boot/efi as the UEFI partition so I can build compatibility with my legacy support later on, right now that's an even bigger pain as it doesn't fully work (After I get it running with UEFI I can tinker with it, if I cant get it running then ill have to wait for a BIOS update).
Also, ive tried the Alternative method listed below that and it still didn't load GRUB like it should have, same original error
Also, right now im trying to install with just using these partitions:
mkfs.fat -F32 /dev/sda1 #EFI BOOT 700MB
mkswap /dev/sda2 #SWAP 2048MB
mkfs.ext4 /dev/sda3 # / Remaining amount of my 1TB HDD
Right now im going to wipe my HDD and then try and install using GummiBoot, I had it all correct but my partitions were not GPT so it didn't work (Which is most likely why GRUB failed, I don't know too much about the differences but from what I know that's what did it) Now when I try to erase and re-partition using a GPT tool it gives me an error saying its not possible to partition /dev/sda or something along the likes of that, im going to see if I can try gparted live later tonight or tomorrow instead of the one they use in the beginners guide.
Im honestly confused as to how I got it running earlier this year when I set it up lmfao. I know I used cfdisk to partition and was still using UEFI.
Last edited by Kitkin15 (2013-12-18 22:05:24)

[SOLVED] systemd 207, lvm2 and luks booting issue

Similar Messages

Maybe you are looking for