1 |
2013/1/26 Canek Peláez Valdés <caneko@×××××.com> |
2 |
|
3 |
> On Sat, Jan 26, 2013 at 7:08 PM, João Matos <jaoneto@×××××.com> wrote: |
4 |
> > Hi list, |
5 |
> > |
6 |
> > I'm having this problem for a while, but I've decided to solve it know. |
7 |
> > Every time I boot my system (couple times a day), I have to hid Ctrl + D |
8 |
> > when the boot process is interrupted by the "emergency mode". |
9 |
> > |
10 |
> > I think it started when I was compiling the kernel myself, and removing |
11 |
> lot |
12 |
> > of stuff. Although, I checked and the mandatory options for systemd are |
13 |
> ok. |
14 |
> > |
15 |
> > When I run "journalctl -b -p err" the only information I get is: |
16 |
> > |
17 |
> > Jan 26 20:29:20 KONOHA NetworkManager[1497]: claim_connection: assertion |
18 |
> > `nm_connection_get_path (NM_CONNECTION (connection)) == NULL' failed |
19 |
> > Jan 26 20:29:24 localhost dhcpcd[1557]: wlan0: sendmsg: Cannot assign |
20 |
> > requested address |
21 |
> > Jan 26 20:30:42 localhost pulseaudio[2073]: [pulseaudio] pid.c: Daemon |
22 |
> > already running. |
23 |
> > Jan 26 20:30:42 localhost pulseaudio[2080]: [pulseaudio] pid.c: Daemon |
24 |
> > already running. |
25 |
> > |
26 |
> > It give me no clue. |
27 |
> > |
28 |
> > Attached the .conf from my gentoo-3.7.1 |
29 |
> > |
30 |
> > After I hit Ctrl + D, the system works normally. |
31 |
> > |
32 |
> > Any help will be appreciated :) |
33 |
> |
34 |
> Are you using udev-197 with systemd-197? mgorny masked it, and said |
35 |
> this in package.mask: |
36 |
> |
37 |
|
38 |
I'm using them. Last time I updated my system there weren't any warning. |
39 |
Anyway, this problem is happening since the previous version. |
40 |
|
41 |
> |
42 |
> # Does not boot. Something with udev is probably broken. Feel free |
43 |
> # to unmask, debug and provide me with a patch. |
44 |
> |
45 |
> You need to be using the same version for udev and systemd (they are |
46 |
> the same package). If you are using the same version for udev and |
47 |
> systemd, are you using an initramfs? When was the last time you built |
48 |
> it, if you do? |
49 |
> |
50 |
|
51 |
I don't have initramfs. Just the kernel. But it used to work normaly. |
52 |
|
53 |
> |
54 |
> Could you boot with "systemd.log_target=kmsg" and |
55 |
> "systemd.log_level=debug", and post the whole output of "journalctl |
56 |
> -b"? It prints only the logs from the last boot. |
57 |
> |
58 |
> |
59 |
journalctl -b attached. |
60 |
|
61 |
|
62 |
> Regards. |
63 |
> -- |
64 |
> Canek Peláez Valdés |
65 |
> Posgrado en Ciencia e Ingeniería de la Computación |
66 |
> Universidad Nacional Autónoma de México |
67 |
> |
68 |
> |
69 |
|
70 |
|
71 |
-- |
72 |
João de Matos |
73 |
Linux User #461527 |
74 |
Graduando em Engenharia de Computação 2005.1 |
75 |
UEFS - Universidade Estadual de Feira de Santana |