我被臭名昭著的关机挂起/冻结错误困扰。每当我关闭薄荷糖时,只有启动屏幕上的第一个点变成绿色,然后才会冻结。我在Ubuntu 16.04上也有这个问题。我打算使用Linux进行游戏。这是我的系统规格-
Desktop: Cinnamon 3.0.7 (Gtk 3.18.9-1ubuntu3.1)
Distro: Linux Mint 18 Sarah
Machine: Mobo: Intel model: DG33FB v: AAD81072-307
Bios: Intel v: DPP3510J.86A.0407.2008.0218.0923 date: 02/18/2008
CPU: Quad core Intel Core2 Quad Q6600 (-MCP-) cache: 4096 KB
flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 19199
clock speeds: max: 2394 MHz 1: 1596 MHz 2: 1596 MHz 3: 2128 MHz
4: 1862 MHz
Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa)
Resolution: 1024x768@60.00hz
GLX Renderer: Gallium 0.4 on NVA8
GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes
Audio: Card-1 NVIDIA High Definition Audio Controller
driver: snd_hda_intel bus-ID: 01:00.1
Card-2 Intel 82801I (ICH9 Family) HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.4.0-21-generic
Network: Card: Intel 82566DC-2 Gigabit Network Connection
driver: e1000e v: 3.2.6-k port: 30e0 bus-ID: 00:19.0
IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 160.0GB (4.9% used)
ID-1: /dev/sda model: Hitachi_HDS72101 size: 160.0GB
Partition: ID-1: / size: 17G used: 5.4G (35%) fs: ext4 dev: /dev/sda5
ID-2: swap-1 size: 2.13GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 47.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 178 Uptime: 6 min Memory: 646.8/1990.4MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.421) inxi: 2.2.35
关闭网络之前先关闭网络没有任何影响,因此这不是由于远程服务器不可达所致。
重新启动工作正常。
journalctl --boot -1 -e --full的结果
Specifying boot ID has no effect, no persistent journal was found
详细启动过程中出现了一条失败消息,该消息表明无法加载内核模块。
详细关闭的结果(最后两行):
[OK] Reached target shutdown.
[54.278173] reboot: power down
的结果 systemctl status
● lol-desktop
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Thu 2016-11-17 18:35:37 IST; 5min ago
PS I用Windows 7双重启动它。
/var/log/journal
,因此您无法向全世界说明该日记记录了什么,而人们也无法从中诊断出(或最有可能)发生了什么错误。
journalctl --boot -1 -e --full
,编辑您的问题,然后将相关输出放在此处。这将向人们展示systemd当时的想法。