Jump to content

How I Converted My Arch to 100% Systemd or...

V.T. Eric Layton

By V.T. Eric Layton
in Bruno's All Things Linux

 Share

Recommended Posts

V.T. Eric Layton

V.T. Eric Layton

Posted
Posted

...How I Totally Borked My Arch Installation and Learned to Love the Bomb

 

Hokee-dokee, folks...

 

Since I can't seem to get auto-mounting to work anymore on my Arch installation and I'm still getting those annoying NOHZ soft_irq errors, I believe I'll completely convert my Arch installation from inits over to systemd today. If all goes well... YAY! If not, there are other remedies.

 

0_61_nuclear_blast.jpg

 

Stay tuned for the updates...

Link to comment
Share on other sites
  • Replies 122
  • Created
  • Last Reply

Top Posters In This Topic

  • V.T. Eric Layton

    51

  • securitybreach

    42

  • amenditman

    20

  • abarbarian

    6

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

V.T. Eric Layton
V.T. Eric Layton

Some very interesting Arch Linux/systemd reading:   Are We Removing What Defines Arch Linux? - Allen McRae     Trolling Arch Linux - Jason Ryan

securitybreach
securitybreach

Excellent, I knew you would   While searching lm_sensors and systemd, I ran across this post from the Archlinux buglist: https://bugs.archlinux.org/task/25251?opened=7654&status%5B0%5D=   It

amenditman
amenditman

I'm glad I'm waiting 'til you pros get this all figured out.   I could do it, but this would just kill the few brain cells and hair follicles I have left.   Good luck!

V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

OK, here we go...

 

1) Install systemd from core using pacman:

 

 #pacman -S systemd

 

2) I intend to run pure systemd, so I won't need to append my kernel line with "init=/bin/systemd" to get systemd to load at boot.

 

3) Installed via pacman: python2-dbus, python2-cairo, systemd-arch-units, systemd-sysvcompat (must remove sysvinit).

 

4) Removed initscripts.

 

5) Create the following files:

 

https://wiki.archlin...iguration_files

 

6) Cross fingers and reboot.

- system reboot failed... had to manually reset machine

- successful boot up - startx, but no network access - wicd daemon fails to start, but can be started manually.

 

=====

 

I'm posting this from Arch using systemd now. I'm sure there are issues other than the wicd daemon. We'll have to play around a bit more to see what's not working.

 

Stay tuned...

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

DEBUGGING SESSION

 

1) No network startup at boot

- no dhcpd

- no wicd daemon

 

This is probably an issue with rc.conf and systemd's use of the DAEMONS array on that file. Solution so far - unknown. I can still manually start the wicd daemon from the command line once I'm in the GUI.

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

Well, as some of you may know, even though Arch is not my primary OS on my main system, I let Arch's GRUB (legacy) control my system's MBR on my #1 drive. With all this borking around with Arch going on, I was worried that I might lose my bootloader. So, I had this bright idea to install LILO in my primary OS (Slackware) and let it take over the MBR.

 

The problem is that LILO, in my opinion, just doesn't have the ability to boot odd installations like mine with multiple operating systems spread across three hard drives. Well, guess what... I got LILO installed and configured in Slackware to boot all my operating systems. There was only one problem. Only Slack would boot with USB keyboard and mouse support. Weird, huh? I even added the initrd line to LILO's entries. That didn't help at all.

 

So what now? No biggie, I thought. I'll just chroot from Slack into Arch and reinstall GRUB on the MBR. Hmm... I've done this before with great success. Tonight, it just didn't want to go easily. I ended up having to use a slightly different chroot method than I had used previously. I found it at this fellow's site --> http://www.hanckmann.net/?q=node/42 It worked wonderfully.

 

I'm back to using Arch's GRUB to boot my system. I'll just have to be careful to not bork it up again.

 

I'm tired of computering for the day. I still have network/wicd issues in Arch to resolve. I know it's just a configuration thing, but I'm so unfamiliar with systemd, that it's going to be challenge to find out how to fix all these bugaboos.

 

I'm off to beddy-bye... long bike ride tomorrow and no computers. ;)

Link to comment
Share on other sites
securitybreach

securitybreach

Posted
Posted

So what now? No biggie, I thought. I'll just chroot from Slack into Arch and reinstall GRUB on the MBR. Hmm... I've done this before with great success. Tonight, it just didn't want to go easily. I ended up having to use a slightly different chroot method than I had used previously. I found it at this fellow's site --> http://www.hanckmann.net/?q=node/42 It worked wonderfully.

 

I'm back to using Arch's GRUB to boot my system. I'll just have to be careful to not bork it up again.

 

I'm tired of computering for the day. I still have network/wicd issues in Arch to resolve. I know it's just a configuration thing, but I'm so unfamiliar with systemd, that it's going to be challenge to find out how to fix all these bugaboos.

 

I'm off to beddy-bye... long bike ride tomorrow and no computers. ;)

Excellent, that is the same link I use for chrooting in :thumbup:

Link to comment
Share on other sites
amenditman

amenditman

Posted
Posted
... long bike ride tomorrow and no computers. ;)
Nice! Glad to hear you are getting out on the road on two wheels. Any chance it's a big old hog?
Link to comment
Share on other sites
ichase

ichase

Posted
Posted

Have you configured wpa-supplicant yet? :sweatingbullets:

Ray has a good point, about a week ago, wpa_supplicant was upgraded. The /etc/wpa_supplicant.conf was automatically saved as /etc/wpa_supplicant.conf.pacsaved. I had to go to that file and save it as wpa_supplicant.conf so it worked with the upgraded wpa_supplicant package. I'm pretty confident you are using wext within wicd as it is most recommended. Wext looks to your wpa_supplicant.conf file. Just a suggestion but for an "old timer" you are already performing wonders in a short period of time. I do believe this "Lab Rat" will be living a long life. ;)

Link to comment
Share on other sites
abarbarian

abarbarian

Posted
Posted

 

I'm off to beddy-bye... long bike ride tomorrow and no computers. ;)

 

Lucky sod. Hope the sun do shine but not too hot . :good2:

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

Nice! Glad to hear you are getting out on the road on two wheels. Any chance it's a big old hog?

 

Umm... how I wish! I miss my motorcycle something fierce. Thanks for reminding me, Bob. >_

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted
Ray has a good point...

 

Yes, that was a good suggestion. However, you guys must have missed it above where I stated that I can manually start the service. Once started all was well. The issue is that systemd does not utilize the rc.conf to start daemons reliably. You have to do something extra sometimes. I'll post about that in a minute.

 

...for an "old timer" you are already performing wonders in a short period of time. I do believe this "Lab Rat" will be living a long life. ;)

 

SQUEAK! Mouse_by_BioMechMoose.gif

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

ISSUES

  • wicd daemon not starting

-debug solution: must register the daemon with systemd

 

# systemctl enable wicd.service

  • cups daemon not starting
  • ntpd daemon not starting
  • tor daemon not starting
  • et cetera not starting

-debug solution: must register daemons with systemd

 

 # systemctl enable <daemon name>.service

  • system time using UTC

-debug solution: create file /etc/adjtime

 

0.0 0.0 0.0
0
LOCAL

 

STILL NEEDING ATTENTION

  • sensors not working
  • still not auto-mouting in thunar

+++++

 

I'm making progress! :)

Link to comment
Share on other sites
abarbarian

abarbarian

Posted
Posted

Yes, that was a good suggestion. However, you guys must have missed it above where I stated that I can manually start the service. Once started all was well. The issue is that systemd does not utilize the rc.conf to start daemons reliably. You have to do something extra sometimes. I'll post about that in a minute.

 

 

 

SQUEAK! Mouse_by_BioMechMoose.gif

 

http://www.game-voyage.com/games/1b7/wack_a_rat_action.html

 

There is a plot afoot to get all rats. Beware. :hysterical:

Link to comment
Share on other sites
amenditman

amenditman

Posted
Posted

I'm glad, more and more, that auto-mounting is no kind of deal for me. This sounds like a project. Heck, you might even learn a thing or two in the process. o:)

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

I'm learning that systemd is not the terrible ogre that I thought it to be just a few days ago. It does have some advantages over the old inits system. It's more efficient, easier to manipulate, and faster. However, as with anything new, it has a learning curve. And actually, it's not new. It's been around for quite some time. I've read some articles about it going back to 2009 or so. There is a lot of documentation online about it. I think quite a few of the more progressive distributions have or will go this route. I understand that Pat V. has no plans to implement it any time soon in Slackware, so I guess by the time he does, I'll won't be a systemd virgin anymore (thanks to my current Arch adventure). Yes. I'm keeping notes. ;)

 

http://www.game-voya...rat_action.html

 

There is a plot afoot to get all rats. Beware. :hysterical:

 

Like I have two hours to burn playing that. Thanks. ;)

Link to comment
Share on other sites
securitybreach

securitybreach

Posted
Posted

I'm learning that systemd is not the terrible ogre that I thought it to be just a few days ago. It does have some advantages over the old inits system. It's more efficient, easier to manipulate, and faster. However, as with anything new, it has a learning curve. And actually, it's not new. It's been around for quite some time. I've read some articles about it going back to 2009 or so. There is a lot of documentation online about it. I think quite a few of the more progressive distributions have or will go this route. I understand that Pat V. has no plans to implement it any time soon in Slackware, so I guess by the time he does, I'll won't be a systemd virgin anymore (thanks to my current Arch adventure). Yes. I'm keeping notes. ;)

 

Like I have two hours to burn playing that. Thanks. ;)

 

Excellent, I knew that you would not have a problem :thumbsup:

 

I may have to check out systemd pretty soon B)

 

BTW how is the mounting issue now? All resolved?

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

I can mount. Never had a problem with that. It's just that my Thunar auto-mount no longer functions. :( I'm still working on a solution.

Link to comment
Share on other sites
securitybreach

securitybreach

Posted
Posted

I can mount. Never had a problem with that. It's just that my Thunar auto-mount no longer functions. :( I'm still working on a solution.

 

Well that is what I was referring to ;)

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

I have no fear of flying with the command line, as you know. It's just that auto-mount is a convenience I liked, particularly with my mp3 player and CDs. :yes: I'll get it to work in systemd. You watch. :)

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

ISSUE

  • no auto-mount in thunar

-debug solution: installed python2-udiskie (an automounter app that works with udisks), added udiskie & before windows manager in .xinitrc.

 

STILL NEEDING ATTENTION

  • sensors not working - need to find out how to load module in systemd
  • intermittent freeze at halt - system halts but does not power off

 

Man! Tons of progress today. I love my Arch again. :)

Link to comment
Share on other sites
securitybreach

securitybreach

Posted
Posted

ISSUE

  • no auto-mount in thunar

-debug solution: installed python2-udiskie (an automounter app that works with udisks), added udiskie & before windows manager in .xinitrc.

 

STILL NEEDING ATTENTION

  • sensors not working - need to find out how to load module in systemd
  • intermittent freeze at halt - system halts but does not power off

Man! Tons of progress today. I love my Arch again. :)

 

Excellent, I knew you would :thumbup:

 

While searching lm_sensors and systemd, I ran across this post from the Archlinux buglist: https://bugs.archlinux.org/task/25251?opened=7654&status%5B0%5D=

 

It may provide some incite into getting this working, or not :hysterical:

  • Like 1
Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted

AHA! What I needed to know was the name of the daemon/service. I thought it was sensorsd, but it's not. It's lm_sensors. WOO-HOO! Thanks, Josh! :yes:

 

ISSUE

  • sensors not working - need to find out how to load module in systemd

-debug solution: register sensors daemon with systemd

 

 # systemctl enable lm_sensors.service

 

STILL NEEDING ATTENTION

  • nothing that I know of at the moment.

+++++

 

This has been a successful project. YAY! :)

Link to comment
Share on other sites
V.T. Eric Layton

V.T. Eric Layton

Posted
  • Author
Posted 

vtel57_Arch~:$ sensors -f
f71882fg-isa-0500
Adapter: ISA adapter
+3.3V:	    +3.34 V  
in1:		  +1.07 V  (max =  +2.04 V)
in2:		  +1.09 V  
in3:		  +0.87 V  
in4:		  +0.63 V  
in5:		  +0.45 V  
in6:		  +0.34 V  
3VSB:		 +3.36 V  
Vbat:		 +3.30 V  
fan1:	    3211 RPM
fan2:		   0 RPM  ALARM
fan3:		 644 RPM
fan4:		   0 RPM  ALARM
temp1:	   +114.8 F  (high = +491.0 F, hyst = +483.8 F)
				   (crit = +491.0 F, hyst = +483.8 F)  sensor = transistor
temp2:	   +258.8 F  (high = +491.0 F, hyst = +483.8 F)
				   (crit = +491.0 F, hyst = +483.8 F)  sensor = thermistor
temp3:	    +87.8 F  (high = +491.0 F, hyst = +487.4 F)
				   (crit = +491.0 F, hyst = +487.4 F)  sensor = transistor

 

NOTE: temp2 is a faulty mobo thermistor - disregard.

Link to comment
Share on other sites
securitybreach

securitybreach

Posted
Posted

AHA! What I needed to know was the name of the daemon/service. I thought it was sensorsd, but it's not. It's lm_sensors. WOO-HOO! Thanks, Josh! :yes:

 

This has been a successful project. YAY! :)

 

No problem, glad I could help you out :thumbup:

 

B)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...