1 |
I've add rescue in grub2 setting, same error with others many strange |
2 |
problems, the last with resolv.conf. What's happens? I want to modify it to |
3 |
add mine dns servers; open the file, modify it, but is impossible to save |
4 |
because system says "file not exist". |
5 |
|
6 |
BTW i want to repeat all the step from the first with a new installation, |
7 |
only a question: why you emerge @world before the kernel? I always emerged |
8 |
kernel before, but Probably isn't the better choice. |
9 |
|
10 |
Thanks for your time, i hope to have early a System that works fine. |
11 |
|
12 |
Regards. |
13 |
|
14 |
|
15 |
Il sabato 28 novembre 2015, Duncan <1i5t5.duncan@×××.net> ha scritto: |
16 |
|
17 |
> mr_L4N posted on Sat, 28 Nov 2015 01:00:47 +0100 as excerpted: |
18 |
> |
19 |
> > Unfortunately I've followed that guide and i can't log in console. |
20 |
> > Impossible to press any keys. |
21 |
> |
22 |
> Please reply in context (under the bit you're replying to), so replying |
23 |
> to you in context in turn is easy. Here, I have your context, but it's |
24 |
> still out of context because your reply out of context of the original, |
25 |
> which was unfortunately below your reply, itself makes little sense. |
26 |
> |
27 |
> So filling in a bit of that missing context, the problem is no keyboard/ |
28 |
> mouse, in X, after installing directly to systemd, and ctrl-alt-F1 |
29 |
> doesn't yield a text console to see if the keyboard works there. |
30 |
> |
31 |
> Now to try to reply to it... |
32 |
> |
33 |
> Please also try ctrl-alt-F2 and ctrl-alt-F3. Depending on how systemd is |
34 |
> configured, X may actually be running on VT1, in which case ctrl-alt-F1 |
35 |
> wouldn't do anything since you're already on VT1. But the F2 and F3 |
36 |
> variants should, as in that case VT2 and VT3 should be free. |
37 |
> |
38 |
> If that doesn't work, try adding this to your kernel commandline options |
39 |
> (in grub2 or whatever) before booting it: |
40 |
> |
41 |
> rescue |
42 |
> |
43 |
> That tells systemd to boot to the rescue target, which should give you a |
44 |
> terminal prompt, with a message saying to either enter the root password, |
45 |
> or press ctrl-D to continue. |
46 |
> |
47 |
> Assuming you get that prompt, the next question is whether you can |
48 |
> actually either enter the password or press ctrl-D there, in which case |
49 |
> your keyboard is working fine at the text console. |
50 |
> |
51 |
> If you can login to root, you'll be at the rescue target, which should |
52 |
> have early services started and filesystems mounted, but will not have |
53 |
> started the normal services that start with multi-user.target or |
54 |
> graphical.target (which is basically multi-user plus the X/graphical |
55 |
> login). |
56 |
> |
57 |
> FWIW, when I setup systemd here, I configured systemd to boot to multi- |
58 |
> user by default, instead of graphical. That way I get a text login with |
59 |
> all services started but the X login, and can run startx from there, to |
60 |
> directly start my desktop environment session of choice (a somewhat |
61 |
> lighter than default kde). It's up to you whether you want to do that as |
62 |
> it is after all your machine, but FWIW I prefer the text login here, and |
63 |
> it does sure help when troubleshooting X or DE related issues. If that |
64 |
> sounds useful (possibly even temporarily), you can set that up by |
65 |
> creating /etc/systemd/system/default.target as a symlink, pointed at |
66 |
> /usr/lib/systemd/system/multi-user.target , thus overriding the shipped |
67 |
> /usr/lib/systemd/system/default.target -> graphical.target . |
68 |
> |
69 |
> Anyway, once logged in at the rescue target, you can run: |
70 |
> |
71 |
> systemctl start multi-user.target |
72 |
> |
73 |
> That should start remaining system services and give you a normal text |
74 |
> console login, without starting X. Once there, you can continue |
75 |
> troubleshooting X's problems, trying to figure out why it's not seeing |
76 |
> your keyboard and mouse. |
77 |
> |
78 |
> Alternatively, try systemd.unit=multi-user.target on the kernel |
79 |
> commandline. I've not actually tried it, but according to the systemd |
80 |
> documentation (systemd.special (7) manpage), systemd.unit= can be used to |
81 |
> override the normal default.target, which in your case apparently is |
82 |
> currently pointing at graphical.target (the shipped default) as described |
83 |
> above. So this should boot you directly to multi-user.target without |
84 |
> having to go thru rescue.target first. |
85 |
> |
86 |
> -- |
87 |
> Duncan - List replies preferred. No HTML msgs. |
88 |
> "Every nonfree program has a lord, a master -- |
89 |
> and if you use the program, he is your master." Richard Stallman |
90 |
> |
91 |
> |
92 |
> |