<div dir="ltr"><div><div>Is there any way it is not in the &quot;default mode&quot;?<br><br></div>when it stoped, instead of hitting Ctrl D, I taped my password and &quot;systemctl default&quot;, so it could try to start again the default boot process. And it worked.<br>

<br></div>I&#39;ll not try the downgrade right now bcz, after a emerge --sync, my portage started do complain about compiling net-misc/networkmanager with support for both systemd and consolekit, but I&#39;m not able to disable consolekit support. So I&#39;ll wait them to fix it.<br>

</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/1/27 João Matos <span dir="ltr">&lt;<a href="mailto:jaoneto@gmail.com" target="_blank">jaoneto@gmail.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">2013/1/27 Canek Peláez Valdés <span dir="ltr">&lt;<a href="mailto:caneko@gmail.com" target="_blank">caneko@gmail.com</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><div>On Sun, Jan 27, 2013 at 12:31 PM, João Matos &lt;<a href="mailto:jaoneto@gmail.com" target="_blank">jaoneto@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; 2013/1/26 Canek Peláez Valdés &lt;<a href="mailto:caneko@gmail.com" target="_blank">caneko@gmail.com</a>&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Sat, Jan 26, 2013 at 7:08 PM, João Matos &lt;<a href="mailto:jaoneto@gmail.com" target="_blank">jaoneto@gmail.com</a>&gt; wrote:<br>
&gt;&gt; &gt; Hi list,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; I&#39;m having this problem for a while, but I&#39;ve decided to solve it know.<br>
&gt;&gt; &gt; Every time I boot my system (couple times a day), I have to hid Ctrl + D<br>
&gt;&gt; &gt; when the boot process is interrupted by the &quot;emergency mode&quot;.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; I think it started when I was compiling the kernel myself, and removing<br>
&gt;&gt; &gt; lot<br>
&gt;&gt; &gt; of stuff. Although, I checked and the mandatory options for systemd are<br>
&gt;&gt; &gt; ok.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; When I run &quot;journalctl -b -p err&quot; the only information I get is:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Jan 26 20:29:20 KONOHA NetworkManager[1497]: claim_connection: assertion<br>
&gt;&gt; &gt; `nm_connection_get_path (NM_CONNECTION (connection)) == NULL&#39; failed<br>
&gt;&gt; &gt; Jan 26 20:29:24 localhost dhcpcd[1557]: wlan0: sendmsg: Cannot assign<br>
&gt;&gt; &gt; requested address<br>
&gt;&gt; &gt; Jan 26 20:30:42 localhost pulseaudio[2073]: [pulseaudio] pid.c: Daemon<br>
&gt;&gt; &gt; already running.<br>
&gt;&gt; &gt; Jan 26 20:30:42 localhost pulseaudio[2080]: [pulseaudio] pid.c: Daemon<br>
&gt;&gt; &gt; already running.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;  It give me no clue.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Attached the .conf from my gentoo-3.7.1<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; After I hit Ctrl + D, the system works normally.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Any help will be appreciated :)<br>
&gt;&gt;<br>
&gt;&gt; Are you using udev-197 with systemd-197? mgorny masked it, and said<br>
&gt;&gt; this in package.mask:<br>
&gt;<br>
&gt;<br>
&gt; I&#39;m using them. Last time I updated my system there weren&#39;t any warning.<br>
&gt; Anyway, this problem is happening since the previous version.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; # Does not boot. Something with udev is probably broken. Feel free<br>
&gt;&gt; # to unmask, debug and provide me with a patch.<br>
&gt;&gt;<br>
&gt;&gt; You need to be using the same version for udev and systemd (they are<br>
&gt;&gt; the same package). If you are using the same version for udev and<br>
&gt;&gt; systemd, are you using an initramfs? When was the last time you built<br>
&gt;&gt; it, if you do?<br>
&gt;<br>
&gt;<br>
&gt; I don&#39;t have initramfs. Just the kernel. But it used to work normaly.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Could you boot with &quot;systemd.log_target=kmsg&quot; and<br>
&gt;&gt; &quot;systemd.log_level=debug&quot;, and post the whole output of &quot;journalctl<br>
&gt;&gt; -b&quot;? It prints only the logs from the last boot.<br>
&gt;&gt;<br>
&gt;<br>
&gt; journalctl -b attached.<br>
<br>
</div></div>From your logs:<br>
<br>
Jan 27 15:16:27 KONOHA systemd[1]: Activating default unit: emergency.target<br>
<br>
You have emergency.target as default unit. The default.target can be<br>
set in different ways:<br>
<br>
- Check /usr/lib64/systemd/system/default.target<br></blockquote><div><br></div></div></div><div>Nothing found here. The file is: <br><br><span style="color:rgb(0,0,255)">[Unit]<br>Description=Graphical Interface<br>Documentation=man:systemd.special(7)<br>


Requires=multi-user.target<br>After=multi-user.target<br>Conflicts=rescue.target<br>Wants=display-manager.service<br>AllowIsolate=yes<br><br>[Install]<br>Alias=default.target</span><br><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">



- Check /etc/systemd/system/default.target<br></blockquote><div><br></div><div>doesn&#39;t exist.<br> <br></div><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">



- Check if you use --unit=emergency.target in your grub config<br>
- Check if you pass the &quot;emergency&quot; kernel parametr in your grub config<br></blockquote><div><br></div></div><div>Nothing wrong with grub.<br></div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">



udev-197 in the tree installs everything to /; systemd-197 installs to<br>
/usr. I&#39;m pretty sure that is not going to end well; I haven&#39;t<br>
upgraded to 197 in neither package.<br>
<br>
Check your default.target; for some reason is set to emergency.<br>
<div><div><br>
Regards.<br>
--<br>
Canek Peláez Valdés<br>
Posgrado en Ciencia e Ingeniería de la Computación<br>
Universidad Nacional Autónoma de México<br>
<br>
</div></div></blockquote></div></div><br></div><div class="gmail_extra">I&#39;ve also tryed &quot;systemctl disable emergency.service&quot; and &quot;systemctl disable emergency.target&quot; before but got nothing.<br><br>

</div>
<div class="gmail_extra">Anyway, thank you for your help :). I&#39;ll try to downgrade. But I still think it is about kernel config.<br clear="all"></div><div class="im"><div class="gmail_extra"><br>-- <br>João de Matos<br>

Linux User #461527<br>
Graduando em Engenharia de Computação 2005.1<br>UEFS - Universidade Estadual de Feira de Santana
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>João de Matos<br>Linux User #461527<br>Graduando em Engenharia de Computação 2005.1<br>UEFS - Universidade Estadual de Feira de Santana
</div>