[Solved]-[solved:indirectly]Chain loading services on boot in Systemd
I have what I believe is a simple issue, but am afraid that my ignorance of systemd services is preventing me from getting my desired result.
I want to boot into tty1-7 automatically and have them each launch independent chains of executions. Specifically, I'm trying to get tty1 to first log a user in and then to run a bash that I've written that loads fbv with an argument, and puts fbterm on top of it, and then load tmux...without me having to do anything.
Essentially I've gotten this sketched out for tty1:
[Service]
Type=oneshot
ExecStart=/home/<user_name>/fbterm-startbash ~/wallpaper.jpg
StandardInput=tty
StandardOutput=tty
TTYPath=/dev/tty1
I read through https://wiki.archlinux.org/index.php/Au … al_console and applied that, but there's no enabling of services there. Is there something simple that I'm missing about adding extra "ExecStart"s in the same service and how to time them?
(I put this in Apps and DE, because a terminal + tmux is my environment, let me know if that is incorrect.)
Last edited by SquidGuy (2013-06-08 14:08:56)
I'm not sure I can address your question directly, but I have an alternate - likely much simpler - solution.
Set up autologin to any of the ttys you want it on (see autologin in wiki if needed).
Then, in your shell profile (e.g, ~/.bash_profile), add a section with conditionals that check $XDG_VTNR:
if [[ $XDG_VTNR -eq 1 ]]; then
# stuff for tty1 here
elif [[ $XDG_VTNR -eq 2 ]]; then
# stuff for tty2 here
fi
EDIT: you may also want all that in a `if [[ $TERM == "linux" ]]` block.
Last edited by Trilby (2013-06-08 13:05:23)
Similar Messages
-
[SOLVED] can't load fglrx during booting
I installed ati proprietarity driver by this manual and it seems working. I rebooted to sure that fglrx loads without errors, set catalyst settings, graphics worked fine, but after next reboot I saw this:
Loading User-specified Modules [Busy]
4.825619] intel ips 0000:00;1f.6: failed to get i915 symbols, graphics turb disabled8
5.417268] brcms_module_init: register returned 0
ROR: could not insert 'fglrx': Invalid argument
[FAIL]
I am totally new to linux and ask to your qualified help..
Last edited by metalex (2012-05-02 13:47:07)Hi again! As Angelsoul writed, I didn't install the catalyst_hook, and now it really seems to be a kernel problem, becouse during the installation catalyst_hook:
Failed!!! Check out log: /var/log/catalyst-install.log
Automatic re-compilation is enabled now.
Answer 'Yes' whenever pacman ask you about updating
'linux-headers' in first place
Provide headers to your kernel ie:
linux-headers if you are using linux.
Most of custom kernels provides own headers.
Add nomodeset to your kernel line in /boot/grub/menu.lst , ie.:
kernel /boot/vmlinuz-linux root=/dev/sda1 ro nomodeset
-------------------------------------------- ^^^^^^^^^ ---------
If experiencing problems with building module or using more than
one kernel use catalyst_build_module command as root, more info:
# catalyst_build_module help
- ^^^^^^^^^^^^^^^^^^^^^ ----------------------------------------
For more info and more troubleshooting visit:
http://wiki.archlinux.org/index.php/ATI_Catalyst
[root@metalex-pc metalex]# catalyst_build_module help
usage: /usr/bin/catalyst_build_module {version|all|remove|remove_all|auto|autooff}
- with no specified kernel version it will use the current kernel version to build module
- all will try to build fglrx modules for all working system's kernels
- remove is removing unused fglrx modules and all empty /lib/modules/* directories
- remove_all is removing all fglrx modules and all empty /lib/modules/* directories
- auto will turn ON 'auto re-compilation of fglrx module with every kernel update'
- autooff will turn off auto re-compilation of fglrx module
[root@metalex-pc metalex]# catalyst_build_module all
[root@metalex-pc metalex]# catalyst_build_module
Building fglrx module for 3.3.4-1-ARCH kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
[root@metalex-pc metalex]# nano /var/log/catalyst-install.log
and it contains
2012-05-02 16:13:41
Building fglrx module for 3.3.4-1-ARCH kernel ...
Kernel header files are absent: directory /lib/modules/3.3.4-1-ARCH/build doesn't exist! Game over
2012-05-02 16:14:59
Building fglrx module for 3.3.4-1-ARCH kernel ...
Kernel header files are absent: directory /lib/modules/3.3.4-1-ARCH/build doesn't exist! Game over
Please, tell what I should do? Download kernel headers and run catalyst_build_module? Where I can download it?
Last edited by metalex (2012-05-02 13:23:14) -
[SOLVED] Windows 8.1, lost Arch boot loader, cannot reinstall or boot
Hi all,
Apologies but I am only posting as I have exhausted my (admittedly quite limited) knowledge and have spent hours trying to get it back up and running but nothing seems to work at all. This will probably be quite long, apologies if there is something really obvious that I have missed on the Wiki or anywhere, but I'm only posting as I can't seem to get anywhere with it at all despite reading and trying.
Essentially I had a Toshiba Satellite p850-321 laptop (UEFI, secure boot off, fast boot off) which I had dual booting with Windows 8 and Arch using rEFInd. I then had several moments of madness, starting when for some reason - on very little sleep so didn't think - decided to upgrade Windows 8 to 8.1. Unsurprisingly (but a surprise for me at the time), it then booted straight into Windows 8.1, no rEFInd. In hindsight, it had probably just set itself as boot priority but I thought it had overwritten rEFInd with its own bootloader or set it back to default or something so started on a way to try and get it back.
I then spent many hours trying to get my old bootable Arch USB stick to work with no joy, updating it to the latest arch iso and all sorts. It eventually worked when I updated the laptop BIOS. Booted from the USB, chrooted into arch, reinstalled rEFInd, played around, eventually got it to reboot and display rEFInd but Arch wouldn't start. At this point I noticed that my fstab looked strange (devices/labels mixed up from what I expected), so followed the Beginner's Guide again and recreated the fstab. My disk is partitioned as follows (main partitions of note):
/dev/sda2 - Windows EFI partition
/dev/sda4 Windows 8.1
/dev/sda6 arch swap partition (archswap)
/dev/sda7 arch root partition (archroot)
/dev/sda8 arch home partition (archhome)
Couldn't get rEFInd to work so decided to start again with gummiboot. Installed gummiboot, followed Beginner's Guide to install and configure it. Edited arch.conf and after having to mess about with the location of vmlinuz-arch.efi in the conf file, I have the options part looking like this:
options root=/dev/sda7 rw
Now gummiboot loads on startup but all I get on trying to load Arch from gummiboot is the dreaded:
ERROR: device '' not found. Skipping fsck
ERROR: Unable to find root device ''.
I've tried changing the root in options in arch.conf to UUID, PARTUUID and even different partitions (just to see what happened...) - the same. Is it likely to be due to me recreating the fstab and something is messed up there?
Another problem is that now, whatever I do, I cannot boot from the USB again to get in to even try to fix anything. The laptop on boot just hangs for a while and then loads the gummiboot from the disk drive rather than from the USB (I've set the boot priority, everything) and nothing will allow me to boot from the USB. That is probably a secondary issue, I can probably try to reinstall the BIOS again and see if that helps.
If anyone has had anything similar and has any solutions I'd be really grateful - anything. I don't mind being shown to be incredibly stupid, I get that a lot so have a lot of experience! - just anything that can get me back into Arch again without having to reinstall from scratch!
Thanks.
Last edited by pilf (2013-11-02 19:45:44)Thanks for replying, very much appreciated. The partitions were numbered sequentially, I only posted up the partitions that I thought were of interest to the issue (which wasn't very helpful!). The partitions are as follows:
Partition No Type
1 Win Recover
2 EFI System (EFI partition)
3 Microsoft Reserved
4 Microsoft Basic (Windows 8.1 installation)
5 Windows Recover
6 Linux Swap
7 Microsoft Basic (Arch root partition)
8 Microsoft Basic (Arch home partition)
9 Windows Recover
It looks like I have managed to solve it, but I admit I'm not sure what of the several changes I made that solved it. I managed to boot into the USB arch disk by resetting my BIOS back to defaults and then changing the boot order back, which was the only way it would boot the USB - without resetting back and putting the boot order back exactly how it was before it wouldn't boot from the USB. Anyway...
Checked the partitions with gdisk, no problems. I did sort the partitions as you mentioned, just in case. Changed the partition names using gdisk to the same names I had before (archroot, archhome, archswap). Changed the types from Microsoft Basic to Linux filesystem (partitions 7 and 8) and wrote the partition.
Mounted everything, chrooted, edited the gummiboot arch.conf file and noticed there were some strange characters in it, a forward slash before /root in the options for example. I had edited the arch.conf file from windows by booting into Windows, mounting the EFI partition (mountvol z: /s) and editing it that way, which would have messed up the formatting. It can't have only been that though as it wasn't booting anyway which is why I went into Windows to edit the file in the first place. Corrected the arch.conf file, rebooted and it booted. Some errors on boot which I need to correct but I can work on those as it boots into my arch installation.
So all solved. I thought I'd update just to say thanks for the advice and in case it helps anyone else in the future. -
Hello archers,
I use VirtualBox and I'm tired of loading modules manually so I figured that a conf file can be created in /etc/modprobe.d/ that will load those modules at boot. Well, easier said than done because it doesn't seem to work.
Here's my virtualbox.conf:
# modules relevant to VirtualBox
vboxdrv
vboxnetadp
vboxnetflt
and here's my systemctl status systemd-modules-load.service:
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: inactive (dead)
start condition failed at Sun 2013-10-20 09:27:06 CEST; 6s ago
none of the trigger conditions were met
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Looking forward to hearing from you.
Last edited by robin92 (2013-10-20 11:10:55)robin92 wrote:so I figured that a conf file can be created in /etc/modprobe.d/ that will load those modules at boot.
Why not read the Wiki and follow the instructions?
https://wiki.archlinux.org/index.php/VirtualBox
Last edited by loafer (2013-10-20 08:06:04) -
[solved] Large number of services enabled during first boot
I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.
To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.
Any ideas as to what might be causing this?
Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.
Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711
Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.
Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable [email protected].
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.
Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):
getty.target.wants:
* [email protected]
multi-user.target.wants:
* [email protected]
* iptables.service
* remote-fs.target
* sshd.service
sysinit.target.wants:
(none)
Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):
default.target.wants:
* systemd-readahead-collect.service
* systemd-readahead-replay.service
multi-user.target.wants:
* dhcpcd.service * krb5-kpropd.service
* fstrim.service * nscd.service
* ftpd.service * rsyncd.service
* gpm.service * systemd-journal-upload.service
* ip6tables.service * systemd-networkd.service
* krb5-kadmind.service * systemd-resolved.service
* krb5-kdc.service
sockets.target.wants:
* krb5-kpropd.socket * systemd-journal-remote.socket
* rlogin.socket * talk.socket
* rsh.socket * telnet.socket
* rsyncd.socket * uuidd.socket
* sshd.socket
sysinit.target.wants:
* dm-event.service
* systemd-timesyncd.service
system-update.target.wants:
* systemd-readahead-drop.service
Explicitly installed packages:
dhcpcd iputils procps-ng systemd-sysvcompat
diffutils linux-grsec psmisc tar
dnsutils logrotate reflector vim-systemd
file mlocate rsync wget
gradm mtr s-nail which
grub openssh screen whois
inetutils pacman
Last edited by tazmanian (2014-09-10 23:11:42)+1.
Here is the ports these services are listening:
$ ss -tpl
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 *:llmnr *:*
LISTEN 0 128 *:ssh *:*
LISTEN 0 128 :::llmnr :::*
LISTEN 0 128 :::19532 :::*
LISTEN 0 128 :::tell :::*
LISTEN 0 128 :::ssh :::*
LISTEN 0 128 :::telnet :::*
LISTEN 0 128 :::login :::*
LISTEN 0 128 :::shell :::*
LISTEN 0 128 :::rsync :::*
LISTEN 0 128 :::git :::* -
How can i solve "could not load language and text preference "
how can i solve " could not load language and text preference ".. help everyone...
Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up guest users” (without the quotes) in the search box. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
*Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.
Test while in safe mode. Same problem?
After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2. -
[SOLVED] Slow "dev-sda2.device" at boot...
First of all, hello everyone. This is my first post on Arch Linux forums, so don't hesitate to correct me if I am doing something wrong.
I have been trying to reduce the boot time on my HDD;
-Using readahead
-Quiet boot
I have managed to reduce the boot time dramatically, but there is a problem, which is a task on boot called dev-sda2.device and it takes more than 6 seconds
systemd-analyze
Startup finished in 1.226s (firmware) + 123ms (loader) + 5.340s (kernel) + 11.205s (userspace) = 17.895s
systemd-analyze blame
6.283s dev-sda2.device
1.728s systemd-readahead-collect.service
1.728s systemd-readahead-replay.service
1.215s wicd.service
656ms systemd-udevd.service
487ms [email protected]
443ms systemd-udev-trigger.service
438ms systemd-vconsole-setup.service
381ms systemd-sysctl.service
380ms boot.mount
378ms systemd-journald.service
259ms kmod-static-nodes.service
244ms systemd-remount-fs.service
202ms sys-kernel-config.mount
200ms dev-mqueue.mount
199ms sys-kernel-debug.mount
180ms tmp.mount
179ms dev-hugepages.mount
134ms systemd-tmpfiles-setup-dev.service
64ms [email protected]
53ms systemd-user-sessions.service
49ms systemd-logind.service
43ms wpa_supplicant.service
25ms systemd-random-seed.service
24ms systemd-readahead-done.service
23ms systemd-tmpfiles-setup.service
5ms systemd-journal-flush.service
5ms systemd-update-utmp.service
4ms alsa-restore.service
3ms [email protected]
2ms [email protected]
2ms [email protected]
1ms [email protected]
1ms systemd-backlight@backlight:intel_backlight.service
systemd-analyze critical-chain
graphical.target @11.205s
└─multi-user.target @11.205s
└─wicd.service @9.989s +1.215s
└─basic.target @9.986s
└─sockets.target @9.985s
└─dbus.socket @9.985s
└─sysinit.target @9.861s
└─systemd-update-utmp.service @9.855s +5ms
└─systemd-tmpfiles-setup.service @9.830s +23ms
└─local-fs.target @9.829s
└─boot.mount @9.447s +380ms
└─[email protected] @8.959s +487ms
└─dev-sda1.device @8.959s
As you can see, dev-sda2.device takes too long and I have no idea what it is. I have been searching it for two days, and found only one topic here, which didn't help me, so I am posting this topic.
-I updated my system today.
-UEFI
-Gummiboot
I know that 17 seconds is a very fast boot, but I want to make it faster. Why not if I can?
Thanks...
EDIT: Updating the system again fixed this.
Last edited by atahanacar (2015-05-19 10:35:31)What file system are you using, and what is the mount point for /dev/sda2?
there could be some mount options depending on your filesystem, that could slow down/speed up mounting.
depending on mount point, using x-systemd.automount option could help.
I actually have similar issue where mounting of my /home on btrfs takes 6-7s of my 18s boot time and I haven't found a solution. Most of the time I just suspend/hibernate my laptop anyway, so it's not such a big issue for myself. -
[SOLVED] High disk activity after kernel boot
Hi,
after kernel loading (just before getty starts) i notice extremely high disk activity for ~20 seconds for no reason. I think that it is something related to systemd and mount services.
When i set rootfs to read-only in syslinux kernel parameters then the system starts normally without delay. So, i think that something is constantly writing to (or checking?) my hard disk right after boot sequence.
I'm using kernel 3.7.9-1-ARCH.
$ systemd --version
systemd 197
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
$ systemd-analyze
Startup finished in 3121ms (kernel) + 6238ms (userspace) = 9360ms
$ systemd-analyze blame
1289ms NetworkManager.service
1173ms colord.service
812ms systemd-logind.service
722ms systemd-binfmt.service
660ms systemd-udevd.service
639ms systemd-sysctl.service
314ms tmp.mount
305ms systemd-remount-fs.service
300ms upower.service
219ms systemd-tmpfiles-setup.service
168ms polkit.service
160ms dev-sda2.swap
156ms systemd-vconsole-setup.service
129ms wpa_supplicant.service
125ms dev-mqueue.mount
121ms dev-hugepages.mount
108ms systemd-udev-trigger.service
101ms verynice.service
59ms systemd-user-sessions.service
48ms boot.mount
47ms hpfall.service
46ms home.mount
43ms cpupower.service
27ms sys-kernel-config.mount
4ms proc-sys-fs-binfmt_misc.mount
Syslinux kernel parameters (either ro or rw has the same result)
APPEND root=/dev/sda3 rw nomodeset vga=current clocksource=acpi_pm libahci.ignore_sss=1
Tried also with fsck hook and removing sda3 from fstab
APPEND root=/dev/sda3 rw nomodeset vga=current clocksource=acpi_pm libahci.ignore_sss=1 rootflags=noatime,barrier=0
my fstab:
# UUID=925aba97-6805-442b-bb51-3ea6c16a5a86
/dev/sda3 / ext4 rw,noatime,barrier=0 0 0
# UUID=dd60df02-7992-43c1-a0e0-79441e23268e
/dev/sda1 /boot ext4 rw,noatime 0 0
# UUID=d2621666-f2c5-4f36-8da3-c0f21a23246c
/dev/sda4 /home ext4 rw,noatime 0 0
# UUID=3d70bc7d-5b0c-4adc-ba84-f32c9d132bcc
/dev/sda2 none swap defaults 0 0
Thanks for your time.
Last edited by anelehto (2013-02-23 14:27:41)It was a problem with preload and its configuration.. I removed it and everything went back to normal!
-
[SOLVED] Possible to load GDM with startx?
I currently boot into the command line and then
startx
to get into GNOME. Is it possible to load GDM in .xinitrc or by any other means when I load my desktop environment? The reason I ask is because I can't get a lock screen to work unless I enable gdm.service at boot, which I don't want. Thanks.
Last edited by barretme (2013-05-09 02:23:48)barretme wrote:The reason I ask is because I can't get a lock screen to work unless I enable gdm.service at boot, which I don't want. Thanks.
Actually, if what you want is the ability to lock the screen you don't have to enable gdm.
Just add "gnome-screensaver &" to your .xinitrc (before "exec gnome-session").
The lock screen this way is rather shabby, but better than nothing. -
[solved] udev/command/module/service
The story started here: https://bbs.archlinux.org/viewtopic.php?id=147745 The aim is to use LIRC with lirc_serial module. To get it these operations must take place in a given order:
- udev must name a serial port
- serial port must be freed from (built in) kernel serial driver with command 'setserial /dev/ttyS0 uart none'
- lirc_serial driver must be loaded
- lircd service must be started
I have tried to add 'setserial ...' command into udev rule (RUN+=), add lirc_serial module to /etc/modules-load and enable lircd service - all these under systemd - but needed sequence of operation takes place randomly only. Currently I use custom script which I start manually after booting (and, of course, it does work always):
~ $ cat `which mylirc.sh`
#!/bin/bash
/usr/bin/systemctl stop lircd.service
/usr/bin/rmmod lirc_serial
/usr/bin/setserial /dev/ttyS0 uart none
/sbin/modprobe lirc_serial
/usr/bin/systemctl start lircd.service
Can anybody suggest legal systemd/udev way to get needed sequence of operations?
Last edited by student975 (2012-09-02 14:29:47)Have got solutions here: [email protected] - just use ExecStartPre:
~ $ cat /etc/systemd/system/lircd.service
[Unit]
Description=LIRC Daemon
After=network.target
[Service]
Type=forking
EnvironmentFile=/etc/conf.d/lircd.conf
PIDFile=/run/lirc/lircd.pid
ExecStartPre=/usr/bin/setserial /dev/ttyS0 uart none
ExecStartPre=/sbin/modprobe lirc_serial
ExecStartPre=/bin/mkdir -p /run/lirc
ExecStartPre=/bin/rm -f /dev/lircd
ExecStartPre=/bin/rm -f /run/lirc/lircd
ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd
ExecStart=/usr/sbin/lircd -d $LIRC_DEVICE -P /run/lirc/lircd.pid -H $LIRC_DRIVER $LIRC_CONFIGFILE
ExecStopPost=/bin/rm -f /dev/lircd
ExecStopPost=/bin/rm -fR /run/lirc
[Install]
WantedBy=multi-user.target -
{Solved} Can not successfully boot into systemd
I will first start off by saying I have read though the following threads:
https://bbs.archlinux.org/viewtopic.php?id=151633
https://bbs.archlinux.org/viewtopic.php?id=151885
And have tried to follow the Systemd wiki. I started out by switching to the new initscripts configuration system. I have the current systemd package installed. I then installed systemd-sysvcompat which of course had me remove sysvinit. I then removed initscripts which moved my rc.conf to rc.conf.pacsave.
I had to manually create /etc/hostname, /etc/locale.conf, and /etc/vconsole.conf as (mentioned in a previous post) I could not do with any "ctl" commands as I had not yet booted into a systemd setup.
This also caused an issue with trying to set up the timezone as:
# timedatectl set-timezone America/New_York
resulted in:
Failed to issue method call: Launch helper exited with unknown return code 1
So at this point I decided to try a reboot and I get:
Welcome to emergency mode! Type "systemctl defualt" or ^D to enter default mode.
Type "journelctl -b" to view system logs. Type "systemctl reboot" to reboot.
Give root password for maintenance
(or typed Control-D to continue): [ 71.520184] radeon_cp: Failed to load firmware
"radeon/R300_cp.bin"
[ 71.520205] [drm:r100_cp_init] *ERROR* failed to load firmware!
[ 71.520224] radeon 0000:01:05.0: failed initializing CP (-2)
[ 71.520237] radeon 0000:01:05.0: Disabling GPU acceleration
I entered emergency mode which brought me to the root terminal. I first attempted to mv rc.conf.pacnew to rc.conf expecting there to possibly be an issue with the daemons I had running or attempted to run but after reboot I got the same thing. Not sure what is going on with the radeon firmware because it's obviously there.
So I re-imaged the hard drive and decided to try again. This time I installed systemd-sysvcompat (removing sysvinit) and DID NOT remove initscripts. I rebooted and got the exact same thing as above. So at this point I am at a loss of ideas with moving forward. Why is systemd-sysvcompat causing the failure of the radeon firmware to load? I use Arch on my laptop, desktop as well as my server. Systemd is coming so I am trying with the laptop first to convert to pure systemd. If I am just missing a step please let me know and I appologize for posting. But hopefully others have run into this issue and could possibly give me a nudge in the right direction. It could be I am reading the wiki wrong or just not interpreting it correctly.
Thanks in advance for your guidance and assistance,
All the best,
Ian
Last edited by ichase (2012-11-16 16:55:10)hiciu,
Here is what you requested taken from emergency mode:
/etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
The next items due to length are linked to pastebin;
bsdtar -t -f /boot/initramfs-linux.img
http://pastebin.com/cZEJHVHm
dmesg
http://pastebin.com/MUGs1e9H
journalctl -b
http://pastebin.com/xgbfVJP8
This is a lot to look at so do know that I am very appreciative of you and any one else looking at these files taking your time to help me with this issue.
All the best,
Ian
Edit: I also wanted to mention that I was able to get rid of the syslog-ng errors previously mentioned by performing:
systemctl enable syslog-ng.service
Then rebooting. Granted I was still put back in emergency mode but was able to fix one issue.
Last edited by ichase (2012-11-16 03:33:41) -
How to solve the issue "OEL 5.6 boot Oracle ASMLib driver: FAILED" ?
Folks,
Hello. I am installing Oracle 11gR2 RAC using 2 VMs (rac1 and rac2) whose OS are Oracle Linux 5.6 in VMPlayer.
I downloaded Oracle Linux 5.6 Media Pack for x86_64 (file name V24479-01) from https://edelivery.oracle.com/linux.
I have installed OEL 5.6 for VM rac1 and done the follows:
1) install rpm and oracleasm packages for rac1.
2) edit /etc/hosts to set up IP addresses for eth0 and eth1 for rac1 and rac2.
3) edit eth0 and eth1 for rac1 by using command [root@rac1 \]# neat
But when boot the OS, I see "initializing Oracle ASMLib driver: FAILED".
When configure Oracle ASM library driver by running the command:
[root@rac1 /]#/etc/init.d/oracleasm configure -i
Its output "initializing Oracle ASMLib driver: FAILED"
I think the reason is the OS cannot initialize Oracle ASMLib driver. My question is:
Do any folk understand how to solve the issue "OEL 5.6 boot Oracle ASMLib driver: FAILED" ?
Thanks.Folks,
Hello. Thanks a lot for replying. OEL 5.6 comes with 2 kernels: uek and red hat
I have chosen to use red hat kernel for 64-bit. I run the following command:
[root@rac1 /]# uname -rm
Output: 2.6.18-238.el5x86_64
I have downloaded 4 files for this version of kernel from
http://www.oracle.com/technetwork/server-storage/linux/downloads/rhel5-084877.html as below:
oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5-debuginfo-2.0.5-1.el5.x86_64.rpm
oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm
I have installed the 4 files and got the error messages for the first 2 files as below:
[root@rac1 /]# rpm -ivh /home/oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
Error: Failed dependencies: kernel-xen=2.6.18-238.el5 is needed by oracleasm-2.6.18-238.el5xen-2.0.5-1.el5.x86_64.rpm
[root@rac1 /]# rpm -ivh /home/oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
Error: Failed dependencies: kernel-debug=2.6.18-238.el5 is needed by oracleasm-2.6.18-238.el5debug-2.0.5-1.el5.x86_64.rpm
The last 2 files have been installed successfully. But when reboot Oracle Linux Server-Base 2.6.18-238.el5, I still see :
"Initializing ASMLib driver: FAILED."
[root@rac1 /]#/etc/init.d/oracleasm configure -i
Its output "initializing Oracle ASMLib driver: OK "
My questions are:
Does the issue OS "Initializing Oracle ASMLib driver: FAILED" have effect later ? Do we need to solve it ?
Thanks. -
[Solved] Folding@Home Kills Network On Boot
Hello all,
I just did a fresh [testing] installation and using NetworkManager under Gnome 3.12.
Upon using the system this last few days I had some weird network issues where my wireless connection would connect fine during boot, but I could not do anything, not even pinging my local router.
Spending a few fruitless hours, I finally managed to connect the issue to Folding@Home, such that if folding is enabled on boot the network is behaving as described above.
If I disable folding (e.g. by pausing it and rebooting the system), network behaves just fine on next boot.
I really can't figure any logical connection between the two, but after several enabling and disabling I'm pretty sure Folding@Home is to blame.
I'm not sure what kind of log will be beneficial to the situation, but will be glad to test whatever is needed.
Thanks, Adam.
* EDIT *
Following advice from the F@H forum, it seems like some sort of weird race condition.
As a workaround, I created a systemd timer to delay the start of the foldingathome service after boot and everything seems to work fine.
[Unit]
Description=Delay foldingathome service
[Timer]
OnBootSec=5min
Unit=foldingathome.service
[Install]
WantedBy=multi-user.target
Last edited by adam777 (2014-04-15 08:21:21)Okay, it works now (after creating /mnt/home anew and rebooting). However, I wonder why did tp_smapi touch my mount points in the first place?
Last edited by marttt (2013-05-31 20:46:09) -
Error while loading service Document Services Configuration (NW 7.0 SP13)
Hello,
I'm in the process of configuring the Adobe Document Services. Now I've received the Certificate + Credentials from SAP which I requested as described in Note 736902. I try to install them according to the Adobe Document Services Configuration Guide which I've downloaded from https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/90355269-4d89-2a10-0bb9-f388704f1dcd. [original link is broken] I've copied the pfx File to /usr/sap/<SAPSID>/SYS/global/AdobeDocumentServices/TrustManagerService/trust/credentials.
Then I started Visual Administrator and opened Server <x> → Services → Document Services Configuration. Here I get this Error returned:
Error while loading service Document Services Configuration
com.sap.engine.services.adminadapter.exception.AdminException: com/adobe/ads/service/configuration/swing/CredentialTabUI
Does anyone has a hint how I can resolve this problem?
Regards
GregorHello,
I solved this problem by restarting J2EE and the Server.
Regards
Gregor -
[SOLVED] Can not shutdown/restart from KDE with systemd
Hello,
Recently, following I switched to a pure systemd setup. The process was simple and most things worked "right out of the bpx". However, I can not shutdown or restart from KDE!
Let's say that I do the 3 finger salute (ALT-CTRL-DEL) and select "Turn off computer" what I get is KDE shutting down, but then I will only get a console (TTY) login prompt. Pressing ALT-CTRL-DEL then will trigger a reboot. I can also login and use "systemctl poweroff". However, I don't understand why it doesn't work straight from KDE.
Are there some packages I must install? Are there some systemd services that I must enable? What other relevant info should I include in this post?
Active units :
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
proc-sys...misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
sys-devi...d-card0.device loaded active plugged MCP79 High Definition Audio
sys-devi...da-sda1.device loaded active plugged ST9500420ASG
sys-devi...da-sda2.device loaded active plugged ST9500420ASG
sys-devi...da-sda3.device loaded active plugged ST9500420ASG
sys-devi...da-sda4.device loaded active plugged ST9500420ASG
sys-devi...da-sda5.device loaded active plugged ST9500420ASG
sys-devi...da-sda6.device loaded active plugged ST9500420ASG
sys-devi...ock-sda.device loaded active plugged ST9500420ASG
sys-devi...et-eth0.device loaded active plugged RTL8111/8168B PCI Express Gigabit Ethernet controller
sys-devi...t-wlan0.device loaded active plugged AR928X Wireless Network Adapter (PCI-Express)
sys-devi...y-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devi...y-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...y-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...y-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-module-fuse.device loaded active plugged /sys/module/fuse
-.mount loaded active mounted /
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
home.mount loaded active mounted /home
run-user-1000-gvfs.mount loaded active mounted /run/user/1000/gvfs
sys-fs-f...nections.mount loaded active mounted FUSE Control File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted /tmp
cups.path loaded active waiting CUPS Printer Service Spool
systemd-...d-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-...word-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
bluetooth.service loaded active running Bluetooth service
colord-sane.service loaded active running Daemon for monitoring attached scanners and registering them with colord
colord.service loaded active running Manage, Install and Generate Color Profiles
console-...daemon.service loaded active running Console Manager
console-...-start.service loaded active exited Console System Startup Logging
cups.service loaded active running CUPS Printing Service
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
kdm.service loaded active running K Display Manager
NetworkManager.service loaded active running Network Manager
sshd.service loaded active running OpenSSH Daemon
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-...s-load.service loaded active exited Load Kernel Modules
systemd-...unt-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-...-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-...rigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-...ssions.service loaded active exited Permit User Sessions
systemd-...-setup.service loaded active exited Setup Virtual Console
udisks2.service loaded active running Storage Daemon
upower.service loaded active running Daemon for power management
wpa_supplicant.service loaded active running WPA supplicant
cups.socket loaded active running CUPS Printing Service Sockets
dbus.socket loaded active running D-Bus System Message Bus Socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-...control.socket loaded active listening udev Control Socket
systemd-...-kernel.socket loaded active running udev Kernel Socket
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
systemd-...es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
72 units listed. Pass --all to see inactive units, too.
Last edited by Prozzaks (2012-08-20 17:35:48)Demon wrote:For me the system only halts, it does not poweroff. How I can solve this?
As bgc1954 said, there is also a symlink "/sbin/poweroff". Just edit the file "/usr/share/config/kdm/kdmrc", go to [shutdown] an replace the line "HaltCmd=/sbin/halt" with "HaltCmd=/sbin/poweroff".
Maybe you are looking for
-
How to create a new tab in CRMD_ORDER for custom fields
Hi Expert, I have added custom fields in crmd_customer_ i through EEWB . Now i want to display the fields in a new tab in CRMD_ORDER. can you please guide me how to create a new Tab step by step procedure. Thanks & Regards, Avi
-
Lock Error while posting document through bapi_acc_document_post
Hi, We are trying to Post documents in R/3 using Bapi_acc_document_post from BW system using ABAP report. The report groups data using certain criteria and makes a Bapi call for each group. Problem : The program has 2 modes test mode and actual ru
-
My MacBook Pro is running slowly. I run Mountain Lion on it. I received the following report from Etrecheck. Can someone help me decipher it and provide me with steps to fix the slow speed? Problem description: slow computer EtreCheck version: 2.0.
-
Itunes only burns 40 minutes on an 80min cd?
I'm having trouble getting Itunes to burn a full cd. I make a playlist that is 50-79 minutes long and the cd appears to burn correctly, i.e. no error messages, etc. cd says it's complete. I put it in my cd player and at the 40 minute mark, it just en
-
How to close current form but leave calling form open
My case is like this, I am working on one form. It have 2 functions. One is serach function, let us call it A, the other is display/entry function, let us call it B. I first start window A to search record. From that record I open window B, when I cl