{Solved} Can not successfully boot into systemd

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.

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.

Re: {Solved} Can not successfully boot into systemd

WorMzy, hiciu - Thank you for taking time to respond. Due to life getting in the way, I have not been able to get on my Arch laptop and get the information requested. But I can answer some of your questions.WorMzy, I'm not sure why it's dumping me into Emergency Mode and does not give any particular reason. My first post shows what is on the screen once it goes into emergency mode on boot up. I can give the suggestion of blacklisting the module and see if that makes a difference. Often times the one thing you think would have no effect ends up solving the problem. Certainly have nothing to loose giving it a try.

hiciu - Once I type in the root password I have full access to all folders so I have no doubt I will have access to /usr/lib/firmware/radeon/R300_cp.bin. I re-imaged my partition so I will need to re-do everything I did to get to that point and I will post the fstab and /proc/mounts from emergency mode as you requested. To answer your question, no, I do not have any of my folders on a seperate partition including my home folder. All resides strictly on sda5.

The question came up in regards to /usr on a seperate partition. It may help to note, that sda1 has Windows XP installed in which I have not booted into for well over a year. sda6 is just an additional data partition.

[ 133.386804] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
[ 133.387136] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

Not sure if this additional info will help but wanted to supply as much info as possible.

Re: {Solved} Can not successfully boot into systemd

bgc1954 and 10PinkPanther - Thank you for taking the time to respond but with all do respect, I don't have an issue with either the video or wifi firmware working just fine under init. It's when I install systemd-sysvcompat (which removed sysvinit) does this firmware seem not to be found?

Prior to starting this transition from init to pure systemd, I performed all updates then cloned my Arch partition. Each time I attempt to transition and I can't boot into my OS, I re-image the partition so I am right back to where I started. I will then take advice from the helpful users here or if I read something else where, try it, it fails, I take notes, and then I re-image my partition again. Each time, video and wifi work like a champ.

As I progress through this issue, I am looking more as you mentioned bgc1954 as syslog-ng could possible be the issue. I plan on reading more through the forums to hopefully find a thread that matches this issue.

Re: {Solved} Can not successfully boot into systemd

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=""

Re: {Solved} Can not successfully boot into systemd

Please get rid of the /dev/{shm,pts} and /dev/sr0 entries from your /etc/fstab. The /dev entries are handled by systemd (and initscripts, for that matter), and /dev/sr0 failing to mount anything is likely what drops you to the emergency prompt.

Re: {Solved} Can not successfully boot into systemd

just so you know, you don't have to dump your initramfs with bsdtar to see what is inside. We have the lsinitcpio tool. Its neat!

Also, you are telling bgc1594 and 10PinkPanther that you don't have issues with your wireless and video, but I think that they were simply responding to the errors you were posting. You are asking for help, and then posting all the errors you can find (which is okay... probably good), so logically it would see that you want help eliminating errors from the list. Isn't that what they were providing? I think you just may end up puching away quality help with your comments in post #9.

Re: {Solved} Can not successfully boot into systemd

falconindy wrote:

Please get rid of the /dev/{shm,pts} and /dev/sr0 entries from your /etc/fstab. The /dev entries are handled by systemd (and initscripts, for that matter), and /dev/sr0 failing to mount anything is likely what drops you to the emergency prompt.

Add 'radeon' to MODULES array in /etc/mkinitcpio.conf and run 'mkinitcpio -p linux'. Somehow it pulls radeon/R300_cp.bin file into initcpio. (I think you will not be able to load fglrx after this, so don't do this if you use amd catalyst).

WonderWoofy wrote:

just so you know, you don't have to dump your initramfs with bsdtar to see what is inside. We have the lsinitcpio tool. Its neat!

Re: {Solved} Can not successfully boot into systemd

Thank you all for the help. I am now enjoying a pure systemd Arch Linux.To let you know what I did and did not do.When I installed systemd-sysvcompat this time, I went into my rc.conf and commented out my daemons line. I then proceeded to use systemctl enable name.service for all of the items I had in my daemons area of my rc.conf.

I took falconindy's advice and fixed my /etc/fstab as suggested and rebooted. Wifi firmware, and video firmware loaded fine and I was up at ttl quickly.

I then proceeded to remove initscripts, rebooted again and all is well.

WonderWoofy - The responses from bgc1594 and 10PinkPanther were more along the lines of RTFM responses. The thread clearly states that both the wifi and video firmware work fine with init and at the time did not work with systemd. Not completely sure what fixed that but if you read post #9 you would have seen that I stated "With all do respect" I was not discrepecful at all and never have been in this forum.

Thanks again everyone for your patience, guidance, and willingness to offer suggestions to a fellow Arch Linux user.

Re: {Solved} Can not successfully boot into systemd

With all do respect, maybe my post was a RTFM but obviously you went back to the wikis and redid some steps and it worked--along with falconindy's suggestion. Sometimes we all miss a step somewhere and things don't work out. That's why you see constant posts where users are advised to read the wiki's again and retry their steps.

As far as commenting out daemons line in rc.conf, I believe you said, at one point, it was saved as rc.conf.pacsave. Even if you changed it back to /etc/rc.conf at some point, a pure systemd doesn't read the rc.conf so that step wasn't likely necessary--just my opinion. Glad it all worked for you.

Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz

Re: {Solved} Can not successfully boot into systemd

bgc1954 - Thank you. I printed the systemd wiki on 11/6/2012, I realized that it had actually had some updates since I printed it.

Removing initscripts moved the rc.conf to rc.conf.pacnew. I moved it back as rc.conf because I have a static IP and my network setup is in rc.conf. Unless systemd has a way of setting static IPs? I admit on that one I have not taken the time to look.

Re: {Solved} Can not successfully boot into systemd

Re: {Solved} Can not successfully boot into systemd

Thanks 10PinkPanther. I must say I am most impressed by the quicker boot times. Also noticed that Thunar now automounts CDs and External devices. I installed Thunar-Volman package a while back and spent minimal time trying to get automount to work. I was just fine mounting devices via the command line.

Re: {Solved} Can not successfully boot into systemd

I'm using older hardware. Laptop is a Compaq Presario v2000 which has been a great laptop for Arch. Also with using old hardware (desktop is a piece meal from old parts also running Arch) I use OpenBox because it's nice and minimalistic. Also, running Arch with no DE or WM on a headless file and print server running SAMBA. Just secure shell into it from the laptop and perform updates or any maintenance that needs to be done.