我想创建一个桌面快捷方式来关闭笔记本电脑上的保护模式。为此,我需要运行以下命令: echo 0 | sudo tee /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode 我创建了一个桌面条目,但我不知道如何以超级用户身份运行它。这样它就什么也不做。我发现的最接近的是 pkexec 但这不起作用。
我有一台 Lenovo IdeaPad 1 11ADA05,我想在其上安装 Kubuntu。我可以很好地启动实时会话,一切正常(图形、WiFi、声音......)。但是安装程序看不到这台机器的 eMMC。我玩过不同的 UEFI 设置,打开和关闭安全启动,甚至在 UEFI 中有一个“设置模式”,但似乎没有任何区别。一个通用的非机器特定的 Windows10 安装 U 盘看到 eMMC 并安装得很好,所以我想它不会太奇特?!?这是实时会话中的硬件探针,我什至无法判断内核是否找到了 eMMC 应该连接到的 SD 控制器,有人可以看看吗? https://linux-hardware.org/?probe=5885335d44
它似乎可以很好地运行 Kubuntu,如果我无法安装它会很遗憾。UEFI 将 eMMC 列为 Ramaxel 64GB,此外“硬盘”列为未安装。我打开机箱,找到了安装 M.2 的安装孔(我猜),PCB 上也有焊盘,但 M.2 插座没有焊接,所以这只是万不得已的解决方案,如果eMMC根本不能用。。。
期待任何提示!
我一直在尝试通过 ThinkPad USB 3 Pro 扩展坞(具有 DisplayLink 标签)的 DVI 端口将额外的显示器与具有 Ubuntu 18.04 的 Lenovo IdeaPad L340 连接。所有其他驱动程序(声音、USB)都是开箱即用的,但不是显示器。
我遵循了 Ubuntu 18.04 驱动程序版本的安装步骤:5.1 https://support.displaylink.com/knowledgebase/articles/684649
但是在运行脚本的步骤中失败了:
sudo ./displaylink-driver-5.1.26.run
Verifying archive integrity... 100% All good.
Uncompressing DisplayLink Linux Driver 5.1.26 100%
DisplayLink Linux Software 5.1.26 install script called: install
Distribution discovered: Ubuntu 18.04.4 LTS
WARNING: Version 1.7.0 of EVDI kernel module is already running.
Please reboot before attempting to re-install DisplayLink Linux Software.
Installation terminated.
经过一番谷歌搜索;我做了以下事情:
$ sudo ./displaylink-driver-5.1.26.run --keep --noexec
displaylink-driver-5.1.26$ sudo ./displaylink-installer.sh uninstall
DisplayLink Linux Software 5.1.26 install script called: uninstall
Distribution discovered: Ubuntu 18.04.4 LTS
Uninstalling
Removing EVDI from kernel tree, DKMS, and removing sources.
Stopping displaylink-driver systemd service
Failed to stop displaylink-driver.service: Unit displaylink-driver.service not loaded.
Failed to disable unit: Unit file displaylink-driver.service does not exist.
Removing suspend-resume hooks
Removing udev rule
Removing Core folder
Uninstallation steps complete.
Please note that the evdi kernel module is still in the memory.
A reboot is required to fully complete the uninstallation process.
由于 displaylink-driver.service 不存在,因此卸载似乎没有进行。我重新启动了几次;我什至尝试在控制台模式下运行 Ubuntu,以避免 X 服务器出现任何问题。
按照此处的步骤更改 X 服务器的配置没有帮助: https: //support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades
这里提到的构建 DisplayLink / EVDI 都没有帮助: https ://forums.developer.nvidia.com/t/building-displaylink-evdi/73626
- lsusb 命令结果:
$lsusb
Bus 002 Device 004: ID 17ef:1017 Lenovo
Bus 002 Device 003: ID 17e9:433f DisplayLink
Bus 002 Device 002: ID 17ef:1016 Lenovo
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 174f:1176 Syntek
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 0cf3:e500 Atheros Communications, Inc.
Bus 001 Device 004: ID 17ef:1017 Lenovo
Bus 001 Device 008: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 002: ID 17ef:1016 Lenovo
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- dkms 初始状态:
$dkms status
nvidia, 440.59, 5.3.0-59-generic, x86_64: installed
- 构建 DisplayLink / EVDI 后的 dkms 状态
$ dkms status
evdi, devel, 5.3.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!)
nvidia, 440.59, 5.3.0-59-generic, x86_64: installed
- 内核版本
$uname -a
Linux 5.3.0-59-generic #53~18.04.1-Ubuntu
我将不胜感激任何帮助;如果需要更多信息,请告诉我。
谢谢。
我昨天买了一台联想 IdeaPad 5 15are05 并在上面安装了 Ubuntu 20.04。问题是,触摸板不起作用。
我也尝试过 18.04 甚至 Debian 10,但它运行的唯一操作系统是 Windows。
我浏览了很多论坛,但没有发现任何对我有帮助的东西。但是,我确实找到了一些命令,我认为您会发现这些输出很有趣
cat /proc/bus/input/devices
:
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="Elan Touchscreen"
P: Phys=
S: Sysfs=/devices/platform/AMDI0010:01/i2c-1/i2c-ELAN0001:00/input/input4
U: Uniq=
H: Handlers=mouse0 event4
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=661800001000003
即使它说“触摸屏”,我也知道这是我的触摸板。我怎么知道这个?好吧,当我使用 进入终端ctrl+alt+f3
并尝试使用触摸板时,它会输出以下内容:
elants_i2c i2c-ELAN0001:00: unknown packet 0e 00 04 03
03 表示我正在触摸它。该值在不同的操作中发生变化,例如,在“释放”触摸板时变为 01。
这意味着触摸板列在 ELAN0001 下,“触摸屏”也列在其下。我认为它说它是触摸屏并不奇怪,因为它们非常相似。
xinput
输出这个:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ NEWMEN1500 Mouse Consumer Control id=13 [slave pointer (2)]
⎜ ↳ NEWMEN1500 Mouse id=15 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ NEWMEN1500 Mouse Consumer Control id=14 [slave keyboard (3)]
↳ NEWMEN1500 Mouse id=12 [slave keyboard (3)]
↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)]
↳ Ideapad extra buttons id=10 [slave keyboard (3)]
触摸板应该列在虚拟核心指针下,但不是。
我真的很想知道如何解决这个问题,因为我需要触摸板才能工作而且我不想购买新的笔记本电脑,所以请帮助我!
我有一台带有 rtl8821ce wifi 适配器的联想 320 笔记本电脑。我使用的是 Ubuntu 19.04,并且适配器在遵循 这些步骤后工作。
我升级到 19.10,wifi 现在不工作了。
的输出lshw -C network
如下
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: enp2s0
version: 10
serial: 8c:16:45:45:5c:35
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168g-3_0.0.1 04/23/13 latency=0 link=no multicast=yes port=MII
resources: irq:16 ioport:4000(size=256) memory:a2104000-a2104fff memory:a2100000-a2103fff
*-network UNCLAIMED
description: Network controller
product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:03:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress cap_list
configuration: latency=0
resources: ioport:3000(size=256) memory:a2000000-a200ffff
*-network
description: Ethernet interface
physical id: 3
logical name: bnep0
serial: b0:fc:36:38:c0:d0
capabilities: ethernet physical
configuration: broadcast=yes ip=192.168.44.52 multicast=yes
这篇文章和我有同样的问题 - 包括从其他驱动程序安装驱动程序 - 但遵循接受的答案对我不起作用。
还有什么我可以做的吗?
$ lspci -nnk | grep 0280 -A3
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821]
Subsystem: Lenovo RTL8821CE 802.11ac PCIe Wireless Network Adapter [17aa:c024]
Kernel modules: wl, 8821ce, rtl8821ce
$ sudo dkms status
bcmwl, 6.30.223.271+bdcom, 5.3.0-22-generic, x86_64: installed
rtl8821ce, 5.2.5.2.1.30816.20190425, 5.3.0-22-generic, x86_64: installed
$ sudo modprobe rtl8821ce && dmesg | grep rtl
modprobe: ERROR: could not insert 'rtl8821ce': Device or resource busy
我最近从 LTS 18.04 升级到 ubuntu 19.04,并且无法连接到家庭 wifi。
swarna@swarna-Lenovo-Ideapad-Flex-15:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
我正在使用英特尔无线 7260:
swarna@swarna-Lenovo-Ideapad-Flex-15:~$ sudo lshw -class network
[sudo] password for swarna:
*-network
description: Ethernet interface
product: RTL810xE PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:01:00.0
logical name: enp1s0
version: 08
serial: 08:9e:01:ec:56:91
size: 10Mbit/s
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=half firmware=rtl8106e-2_0.0.1 04/23/13 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
resources: irq:16 ioport:3000(size=256) memory:b0504000-b0504fff memory:b0500000-b0503fff
*-network
description: Wireless interface
product: Wireless 7260
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 73
serial: 0c:8b:fd:6f:5b:a8
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=17.3216344376.0 ip=192.168.225.78 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:46 memory:b0400000-b0401fff
感觉是crda的问题,由于Process '/sbin/crda' failed with exit code 255.
日志中的错误,在REGDOMAIN中添加了IND:
swarna@swarna-Lenovo-Ideapad-Flex-15:~$ cat /etc/default/crda
# Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set
# the initial regulatory domain setting for IEEE 802.11 devices which operate
# on this system.
#
# Governments assert the right to regulate usage of radio spectrum within
# their respective territories so make sure you select a ISO/IEC 3166-1 alpha2
# country code suitable for your location or you may infringe on local
# legislature. See `/usr/share/zoneinfo/zone.tab' for a table of timezone
# descriptions containing ISO/IEC 3166-1 alpha2 country codes.
REGDOMAIN=IND
并重新启动系统。但还是得到了:
swarna@swarna-Lenovo-Ideapad-Flex-15:~$ crda
COUNTRY environment variable not set.
此外,我将 setregdomain 更改为也将 IND 设置为 REGDOMAIN
swarna@swarna-Lenovo-Ideapad-Flex-15:/lib/crda$ cat setregdomain
#!/bin/sh
set -e
REGDOMAIN=IND
CRDA_CONF=/etc/default/crda
[ -r "$CRDA_CONF" ] && . "$CRDA_CONF"
[ -z "$REGDOMAIN" ] && exit 0
exec /sbin/iw reg set "$REGDOMAIN"
并重新启动。
还是一样 -
swarna@swarna-Lenovo-Ideapad-Flex-15:~$ crda
COUNTRY environment variable not set.
我也尝试了以下方法(在浏览了互联网上提供的各种建议之后),但没有任何效果:
sudo service network-manager restart; reboot
sudo modprobe iwlwifi 11n_disable=1; reboot
sudo rmmod iwlmvm iwlwifi; reboot
我能够连接到其他 wi-fi,完全没有任何变化。我的系统有双启动,并且 Windows 与我的家庭 wifi 连接良好。
另外,我不确定 crda 问题是否只是一个红鲱鱼,还有其他需要解决的问题。
在此之后我无法继续。有人可以建议我可能做错了什么并帮助我解决问题吗?请让我知道是否需要附加任何其他信息。
发布答案,这里是日志:
我已REGDOMAIN=IN
按照建议修改 /etc/default/crda 以保持:
swarna@swarna-Lenovo-Ideapad-Flex-15:/var/log$ cat /etc/default/crda
# Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set
# the initial regulatory domain setting for IEEE 802.11 devices which operate
# on this system.
#
# Governments assert the right to regulate usage of radio spectrum within
# their respective territories so make sure you select a ISO/IEC 3166-1 alpha2
# country code suitable for your location or you may infringe on local
# legislature. See `/usr/share/zoneinfo/zone.tab' for a table of timezone
# descriptions containing ISO/IEC 3166-1 alpha2 country codes.
REGDOMAIN=IN
我还从 /lib/crda/setregdomain 中删除了我的更改:
#!/bin/sh
set -e
REGDOMAIN=
CRDA_CONF=/etc/default/crda
[ -r "$CRDA_CONF" ] && . "$CRDA_CONF"
[ -z "$REGDOMAIN" ] && exit 0
exec /sbin/iw reg set "$REGDOMAIN"
现在我明白了
swarna@swarna-Lenovo-Ideapad-Flex-15:~$ iw reg get
global
country IN: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5150 - 5350 @ 160), (N/A, 23), (N/A)
(5725 - 5875 @ 80), (N/A, 23), (N/A)
但:
swarna@swarna-Lenovo-Ideapad-Flex-15:~$ crda
COUNTRY environment variable not set.
我也尝试连接到另一个wifi,在这种情况下我没有看到crda错误,并且连接成功。
swarna@swarna-Lenovo-Ideapad-Flex-15:~$ nmcli device wifi list
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
* Lakme Infra 1 270 Mbit/s 87 ▂▄▆█ WPA1 WPA2
JioFi4_0413B0 Infra 6 65 Mbit/s 52 ▂▄__ WPA2
IvanDominic Infra 3 135 Mbit/s 19 ▂___ WPA1 WPA2
Abhi2316@kbroadband Infra 1 270 Mbit/s 9 ▂___ WPA2
我一直在尝试启用我的笔记本电脑的蓝牙(Lenovo Ideapad-Y400),它带有一个 Atheros 蓝牙,它的内核有一些问题。
首先我无法打开我的蓝牙,但我意识到运行sudo rfkill block bluetooth
两次,然后再次运行两次sudo rfkill unblock bluetooth
,蓝牙配置菜单能够找到设备并配对它们但1分钟后崩溃,然后蓝牙是找不到任何东西。此外,如果我在这种特殊情况下关闭蓝牙,我将无法再次打开它,我必须再次运行才能打开它rfkill un/block
。
然后,我从这里尝试了解决方案,它就像一个魅力,现在我可以打开和关闭我的蓝牙。似乎我的内核版本有这个问题,我也安装了 Ukuu,以安装更新的内核,但是我的显卡崩溃了(现在我正在使用修补内核使我的蓝牙工作“Linux 4.15.0.39.48”) . 但是现在我的蓝牙找不到任何设备。 我尝试运行bluetoothctl
,我打开它(power on
),并使其可发现(discoverable on
),并且运行scan on
我的计算机也找不到任何设备,同样运行hcitool
。同样的东西安装bluez
。
你能帮我解决这些问题吗?
太感谢了。
在这里,我添加了一些在一些论坛中要求他们获取系统上下文的输出。
lsusb
输出:
tonny@tonny-IdeaPad:~$ lsusb
Bus 002 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
Bus 002 Device 004: ID 1c4f:0054 SiGma Micro
Bus 002 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 2341:0010 Arduino SA Mega 2560 (CDC ACM)
Bus 003 Device 002: ID 5986:0295 Acer, Inc
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm'
输出:
02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8161 Gigabit Ethernet [1969:1091] (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. AR8161 Gigabit Ethernet [10ec:0123]
Kernel driver in use: alx
Kernel modules: alx
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
Subsystem: Lenovo AR9485 Wireless Network Adapter [17aa:3218]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2392] (rev 30)
Bus 002 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
Bus 002 Device 004: ID 1c4f:0054 SiGma Micro
Bus 002 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 2341:0010 Arduino SA Mega 2560 (CDC ACM)
Bus 003 Device 002: ID 5986:0295 Acer, Inc
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
3: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
4.15.0-39-generic
[ 0.029218] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 0.062621] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 2.567931] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
[ 2.567935] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
[ 2.567939] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
[ 2.567943] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
[ 2.567947] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
[ 3.278355] usb 1-1.3: Product: Bluetooth USB Host Controller
[ 28.220952] Bluetooth: Core ver 2.22
[ 28.220966] Bluetooth: HCI device and connection manager initialized
[ 28.220969] Bluetooth: HCI socket layer initialized
[ 28.220971] Bluetooth: L2CAP socket layer initialized
[ 28.220976] Bluetooth: SCO socket layer initialized
[ 384.853147] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 384.853148] Bluetooth: BNEP filters: protocol multicast
[ 384.853151] Bluetooth: BNEP socket layer initialized
[ 384.859967] Bluetooth: RFCOMM TTY layer initialized
[ 384.859973] Bluetooth: RFCOMM socket layer initialized
[ 384.859978] Bluetooth: RFCOMM ver 1.11
[ 390.827177] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 406.953061] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 415.912118] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 432.037908] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 447.907815] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 464.034678] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 479.904574] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 496.030502] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 511.900372] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 528.026264] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 543.896136] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 560.022140] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 575.891942] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 592.020923] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 607.894811] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 624.023613] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 777.881657] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 794.008537] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 809.879435] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 826.007324] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 841.878218] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 858.005108] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 873.876001] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 890.002848] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 905.872706] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 921.999639] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 937.870565] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 953.997372] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 969.868344] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 985.994169] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1001.865092] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1017.992021] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1033.861796] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1049.988802] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1065.859696] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1081.985522] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1097.856388] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1113.984241] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1129.857239] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1145.985096] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1161.856925] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1177.984835] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1193.856821] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1209.984714] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1225.856513] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1241.983407] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1257.855314] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1273.982145] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1289.854167] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1305.982240] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1321.852850] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1337.979835] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1353.851642] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1369.978715] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1385.849399] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1401.977363] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1417.848295] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1433.975231] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1449.846078] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1465.972883] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1481.843773] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1497.970744] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1513.842642] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1529.969438] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1545.840336] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1561.967232] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1577.838132] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1593.965101] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1609.835897] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1625.962878] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1641.833680] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1657.959569] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1673.830460] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1689.957340] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1705.828338] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1721.955222] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1737.826076] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1753.952992] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1769.823808] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1785.949672] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1801.820675] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1817.947455] Bluetooth: hci0: last event is not cmd complete (0x0f)
编辑1:
systemd-analyze blame | nc termbin.com 9999
输出:
http://termbin.com/yxiq
这里面有:
4min 29.496s apt-daily-upgrade.service
2min 24.962s apt-daily.service
29.199s systemd-journal-flush.service
23.755s dev-sda3.device
14.333s systemd-udevd.service
12.446s systemd-sysctl.service
10.066s snap-core-5662.mount
6.799s snapd.service
6.294s NetworkManager-wait-online.service
5.449s NetworkManager.service
4.790s dev-loop9.device
4.690s networkd-dispatcher.service
4.686s dev-loop16.device
4.563s dev-loop18.device
4.483s keyboard-setup.service
4.438s plymouth-quit-wait.service
4.026s dev-loop8.device
3.987s dev-loop17.device
3.953s dev-loop23.device
3.671s dev-loop13.device
3.587s dev-loop21.device
3.521s dev-loop10.device
3.483s dev-loop24.device
3.480s winbind.service
3.239s dev-loop0.device
3.078s home.mount
2.961s udisks2.service
2.915s plymouth-start.service
2.832s systemd-modules-load.service
2.563s dev-loop22.device
2.560s dev-loop20.device
2.558s dev-loop19.device
2.557s dev-loop14.device
2.556s dev-loop15.device
2.418s dev-loop12.device
2.416s dev-loop11.device
2.414s dev-loop7.device
2.388s grub-common.service
2.367s apparmor.service
2.256s systemd-fsck@dev-disk-by\x2duuid-1d27b8c5\x2db30c\x2d48e3\x2d85ff\x2d4d20591d080f.service
1.952s dev-loop3.device
1.852s dev-loop5.device
1.816s systemd-rfkill.service
1.617s snap-core-5742.mount
1.586s gdm.service
1.582s ModemManager.service
1.573s snap-gtk\x2dcommon\x2dthemes-818.mount
1.527s snap-gtk\x2dcommon\x2dthemes-701.mount
1.521s dev-loop2.device
1.517s swapfile.swap
1.468s dev-loop4.device
1.450s snap-gnome\x2dcharacters-139.mount
1.353s snap-gnome\x2dcalculator-238.mount
1.333s plymouth-read-write.service
1.311s wpa_supplicant.service
1.275s snap-spotify-21.mount
1.196s snap-spotify-26.mount
1.192s snap-gnome\x2dcalculator-260.mount
1.169s snap-gnome\x2dcalculator-222.mount
1.167s fstrim.service
1.144s apport.service
1.130s fwupd.service
1.130s snap-spotify-24.mount
1.114s snap-gnome\x2dcharacters-124.mount
1.082s systemd-tmpfiles-setup-dev.service
1.024s snap-gnome\x2dlogs-40.mount
1.012s gpu-manager.service
997ms systemd-remount-fs.service
993ms teamviewerd.service
952ms dev-hugepages.mount
950ms sys-kernel-debug.mount
949ms dev-mqueue.mount
937ms snap-gnome\x2dlogs-45.mount
829ms snap-gnome\x2d3\x2d26\x2d1604-70.mount
820ms snap-gtk\x2dcommon\x2dthemes-808.mount
813ms accounts-daemon.service
794ms snap-gnome\x2dcharacters-117.mount
776ms dev-loop6.device
772ms dev-loop1.device
677ms networking.service
670ms snap-gnome\x2dsystem\x2dmonitor-57.mount
647ms systemd-random-seed.service
619ms snap-vlc-555.mount
613ms speech-dispatcher.service
613ms thermald.service
613ms bluetooth.service
610ms systemd-logind.service
608ms avahi-daemon.service
603ms rsyslog.service
590ms pppd-dns.service
577ms packagekit.service
531ms snap-gnome\x2dsystem\x2dmonitor-51.mount
487ms snap-gnome\x2dsystem\x2dmonitor-54.mount
482ms snap-core-5897.mount
471ms kmod-static-nodes.service
422ms colord.service
421ms systemd-journald.service
314ms systemd-tmpfiles-setup.service
312ms console-setup.service
297ms binfmt-support.service
270ms bolt.service
221ms systemd-update-utmp.service
211ms snap-gnome\x2dlogs-43.mount
192ms setvtrgb.service
191ms upower.service
172ms snap-gnome\x2d3\x2d26\x2d1604-74.mount
170ms systemd-timesyncd.service
161ms polkit.service
158ms systemd-resolved.service
124ms systemd-udev-trigger.service
90ms snap-firefox-152.mount
60ms ufw.service
51ms [email protected]
32ms [email protected]
30ms snapd.seeded.service
8ms systemd-update-utmp-runlevel.service
7ms alsa-restore.service
7ms ureadahead-stop.service
7ms kerneloops.service
6ms rtkit-daemon.service
6ms proc-sys-fs-binfmt_misc.mount
5ms systemd-backlight@backlight:acpi_video0.service
5ms dns-clean.service
2ms systemd-user-sessions.service
2ms sys-fs-fuse-connections.mount
2ms sys-kernel-config.mount
1ms nvidia-persistenced.service
1ms snapd.socket
我无法让我的 Lenovo 100S ideapad 从我的 Ubuntu 18 LTS 可启动 USB 启动。笔记本电脑目前装有 Windows 10 32 位。在 EFI BIOS 中禁用安全启动以便我可以更改启动顺序后,Windows BitLocker 已启动并锁定驱动器。现在每次计算机启动时,都会进入 BitLocker 驱动器恢复。
DEVICE SPECIFICATIONS=
Product Name: Lenovo ideapad 100S-11IBY
BIOS Version: E2CN13WW
EC Version: E2EC12WW
Lenovo SN: YD00S4Y4
CPU: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz
System Memory: 2048 MB
Storage: SanDisk DB4032
Preinstalled OS license SDK0J91117 WIN
OA3 Key ID 3259182586809
如果我尝试正常启动计算机,它会首先进入 BitLocker 驱动器恢复。我点击“跳过此驱动器”按钮继续(因为我不想让 Windows 回到计算机上)。然后它给了我以下选项:
- 继续:这只会再次导致 BitLocker 菜单。
- 使用设备:这允许我使用“EFI USB 设备”、“EFI DVD/CDROM”(我没有)和“EFI 网络”(我没有设置)。如果我选择“EFI USB 设备”(插入了 Ubuntu 18 安装媒体),我会得到“系统没有任何 USB 启动选项。请在启动管理器菜单中选择其他启动选项。”
如果我按下“Novo”按钮然后F1键,我会得到一个菜单,上面写着“引导选项菜单”,然后是“EFI 引导设备”,然后选择了“Windows 引导管理器”,并带有灰色突出显示。在它下面显示 [up] 和 [down] 更改选项,ENTER 选择一个选项,ESC 退出“但是当我按下向上或向下时它不会更改选择。
当我使用“Novo”按钮然后 F1 键进入 BIOS 时,它会显示我在上面的设备规格下发布的“信息”,我的“配置”选项包括“安全启动”(我已关闭),“ Reset to Setup Mode”和“BIOS Back Flash”(关闭)。还有其他选择,但我认为它们与我的问题无关。
有任何想法吗?