Is there any way it is not in the "default mode"? when it stoped, instead of hitting Ctrl D, I taped my password and "systemctl default", so it could try to start again the default boot process. And it worked.
I'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'm not able to disable consolekit support. So I'll wait them to fix it. 2013/1/27 João Matos <jaon...@gmail.com> > > > > 2013/1/27 Canek Peláez Valdés <can...@gmail.com> > >> On Sun, Jan 27, 2013 at 12:31 PM, João Matos <jaon...@gmail.com> wrote: >> > >> > >> > >> > 2013/1/26 Canek Peláez Valdés <can...@gmail.com> >> >> >> >> On Sat, Jan 26, 2013 at 7:08 PM, João Matos <jaon...@gmail.com> wrote: >> >> > Hi list, >> >> > >> >> > I'm having this problem for a while, but I've decided to solve it >> know. >> >> > Every time I boot my system (couple times a day), I have to hid Ctrl >> + D >> >> > when the boot process is interrupted by the "emergency mode". >> >> > >> >> > I think it started when I was compiling the kernel myself, and >> removing >> >> > lot >> >> > of stuff. Although, I checked and the mandatory options for systemd >> are >> >> > ok. >> >> > >> >> > When I run "journalctl -b -p err" the only information I get is: >> >> > >> >> > Jan 26 20:29:20 KONOHA NetworkManager[1497]: claim_connection: >> assertion >> >> > `nm_connection_get_path (NM_CONNECTION (connection)) == NULL' failed >> >> > Jan 26 20:29:24 localhost dhcpcd[1557]: wlan0: sendmsg: Cannot assign >> >> > requested address >> >> > Jan 26 20:30:42 localhost pulseaudio[2073]: [pulseaudio] pid.c: >> Daemon >> >> > already running. >> >> > Jan 26 20:30:42 localhost pulseaudio[2080]: [pulseaudio] pid.c: >> Daemon >> >> > already running. >> >> > >> >> > It give me no clue. >> >> > >> >> > Attached the .conf from my gentoo-3.7.1 >> >> > >> >> > After I hit Ctrl + D, the system works normally. >> >> > >> >> > Any help will be appreciated :) >> >> >> >> Are you using udev-197 with systemd-197? mgorny masked it, and said >> >> this in package.mask: >> > >> > >> > I'm using them. Last time I updated my system there weren't any warning. >> > Anyway, this problem is happening since the previous version. >> > >> >> >> >> # Does not boot. Something with udev is probably broken. Feel free >> >> # to unmask, debug and provide me with a patch. >> >> >> >> You need to be using the same version for udev and systemd (they are >> >> the same package). If you are using the same version for udev and >> >> systemd, are you using an initramfs? When was the last time you built >> >> it, if you do? >> > >> > >> > I don't have initramfs. Just the kernel. But it used to work normaly. >> >> >> >> >> >> Could you boot with "systemd.log_target=kmsg" and >> >> "systemd.log_level=debug", and post the whole output of "journalctl >> >> -b"? It prints only the logs from the last boot. >> >> >> > >> > journalctl -b attached. >> >> From your logs: >> >> Jan 27 15:16:27 KONOHA systemd[1]: Activating default unit: >> emergency.target >> >> You have emergency.target as default unit. The default.target can be >> set in different ways: >> >> - Check /usr/lib64/systemd/system/default.target >> > > Nothing found here. The file is: > > [Unit] > Description=Graphical Interface > Documentation=man:systemd.special(7) > Requires=multi-user.target > After=multi-user.target > Conflicts=rescue.target > Wants=display-manager.service > AllowIsolate=yes > > [Install] > Alias=default.target > > > - Check /etc/systemd/system/default.target >> > > doesn't exist. > > >> - Check if you use --unit=emergency.target in your grub config >> - Check if you pass the "emergency" kernel parametr in your grub config >> > > Nothing wrong with grub. > > >> udev-197 in the tree installs everything to /; systemd-197 installs to >> /usr. I'm pretty sure that is not going to end well; I haven't >> upgraded to 197 in neither package. >> >> Check your default.target; for some reason is set to emergency. >> >> Regards. >> -- >> Canek Peláez Valdés >> Posgrado en Ciencia e Ingeniería de la Computación >> Universidad Nacional Autónoma de México >> >> > I've also tryed "systemctl disable emergency.service" and "systemctl > disable emergency.target" before but got nothing. > > Anyway, thank you for your help :). I'll try to downgrade. But I still > think it is about kernel config. > > -- > João de Matos > Linux User #461527 > Graduando em Engenharia de Computação 2005.1 > UEFS - Universidade Estadual de Feira de Santana > -- João de Matos Linux User #461527 Graduando em Engenharia de Computação 2005.1 UEFS - Universidade Estadual de Feira de Santana
