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