您尚未登录。

#1 2021-11-12 17:07:42

Tamako
会员
注册时间: 2019-02-18
帖子: 23

X 服务启动失败

之前正常,syu更新系统后无法用 startx 启动桌面

Xorg.0.log

[   107.978] 
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[   107.978] 
X.Org X Server 1.21.1.1
X Protocol Version 11, Revision 0
[   107.978] Current Operating System: Linux Arch 5.14.16-arch1-1 #1 SMP PREEMPT Tue, 02 Nov 2021 22:22:59 +0000 x86_64
[   107.978] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=560d132ae9 rw quiet resume=/dev/sda6
[   107.978]  
[   107.978] Current version of pixman: 0.40.0
[   107.978] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   107.978] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   107.978] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 12 16:15:57 2021
[   107.978] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   107.978] (==) No Layout section.  Using the first Screen section.
[   107.978] (==) No screen section available. Using defaults.
[   107.978] (**) |-->Screen "Default Screen Section" (0)
[   107.978] (**) |   |-->Monitor "<default monitor>"
[   107.979] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   107.979] (==) Automatically adding devices
[   107.979] (==) Automatically enabling devices
[   107.979] (==) Automatically adding GPU devices
[   107.979] (==) Automatically binding GPU devices
[   107.979] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   107.979] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[   107.979] 	Entry deleted from font path.
[   107.979] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[   107.979] 	Entry deleted from font path.
[   107.979] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[   107.979] 	Entry deleted from font path.
[   107.979] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF,
	/usr/share/fonts/OTF
[   107.979] (==) ModulePath set to "/usr/lib/xorg/modules"
[   107.979] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   107.979] (II) Module ABI versions:
[   107.979] 	X.Org ANSI C Emulation: 0.4
[   107.979] 	X.Org Video Driver: 25.2
[   107.979] 	X.Org XInput driver : 24.4
[   107.979] 	X.Org Server Extension : 10.0
[   107.979] (++) using VT number 2

[   107.980] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_33
[   107.982] (--) PCI:*(1@0:0:0) 11de:1374:7377:0000 rev 161, Mem @ 0xf6000000/16777216, 0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[   107.982] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   107.982] (II) LoadModule: "glx"
[   107.982] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   107.983] (II) Module glx: vendor="X.Org Foundation"
[   107.983] 	compiled for 1.21.1.1, module version = 1.0.0
[   107.983] 	ABI class: X.Org Server Extension, version 10.0
[   107.983] (==) Matched nouveau as autoconfigured driver 0
[   107.983] (==) Matched nv as autoconfigured driver 1
[   107.983] (==) Matched modesetting as autoconfigured driver 2
[   107.983] (==) Matched fbdev as autoconfigured driver 3
[   107.983] (==) Matched vesa as autoconfigured driver 4
[   107.983] (==) Assigned the driver to the xf86ConfigLayout
[   107.983] (II) LoadModule: "nouveau"
[   107.983] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[   107.983] (II) Module nouveau: vendor="X.Org Foundation"
[   107.983] 	compiled for 1.21.1.1, module version = 1.0.17
[   107.983] 	Module class: X.Org Video Driver
[   107.983] 	ABI class: X.Org Video Driver, version 25.2
[   107.983] (II) LoadModule: "nv"
[   107.983] (WW) Warning, couldn't open module nv
[   107.983] (EE) Failed to load module "nv" (module does not exist, 0)
[   107.983] (II) LoadModule: "modesetting"
[   107.983] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   107.983] (II) Module modesetting: vendor="X.Org Foundation"
[   107.983] 	compiled for 1.21.1.1, module version = 1.21.1
[   107.983] 	Module class: X.Org Video Driver
[   107.983] 	ABI class: X.Org Video Driver, version 25.2
[   107.983] (II) LoadModule: "fbdev"
[   107.984] (WW) Warning, couldn't open module fbdev
[   107.984] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   107.984] (II) LoadModule: "vesa"
[   107.984] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[   107.984] (II) Module vesa: vendor="X.Org Foundation"
[   107.984] 	compiled for 1.21.1.1, module version = 2.5.0
[   107.984] 	Module class: X.Org Video Driver
[   107.984] 	ABI class: X.Org Video Driver, version 25.2
[   107.984] (II) NOUVEAU driver 
[   107.984] (II) NOUVEAU driver for NVIDIA chipset families :
[   107.984] 	RIVA TNT            (NV04)
[   107.984] 	RIVA TNT2           (NV05)
[   107.984] 	GeForce 256         (NV10)
[   107.984] 	GeForce 2           (NV11, NV15)
[   107.984] 	GeForce 4MX         (NV17, NV18)
[   107.984] 	GeForce 3           (NV20)
[   107.984] 	GeForce 4Ti         (NV25, NV28)
[   107.984] 	GeForce FX          (NV3x)
[   107.984] 	GeForce 6           (NV4x)
[   107.984] 	GeForce 7           (G7x)
[   107.984] 	GeForce 8           (G8x)
[   107.984] 	GeForce 9           (G9x)
[   107.984] 	GeForce GTX 2xx/3xx (GT2xx)
[   107.984] 	GeForce GTX 4xx/5xx (GFxxx)
[   107.984] 	GeForce GTX 6xx/7xx (GKxxx)
[   107.984] 	GeForce GTX 9xx     (GMxxx)
[   107.984] 	GeForce GTX 10xx    (GPxxx)
[   107.984] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   107.984] (II) VESA: driver for VESA chipsets: vesa
[   107.984] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[   107.984] (EE) open /dev/dri/card0: No such file or directory
[   107.984] (WW) Falling back to old probe method for modesetting
[   107.984] (EE) open /dev/dri/card0: No such file or directory
[   107.984] vesa: Refusing to run on UEFI
[   107.985] (EE) Screen 0 deleted because of no matching config section.
[   107.985] (II) UnloadModule: "modesetting"
[   107.985] (EE) Device(s) detected, but none match those in the config file.
[   107.985] (EE) 
Fatal server error:
[   107.985] (EE) no screens found(EE) 
[   107.985] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[   107.985] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   107.985] (EE) 
[   107.987] (EE) Server terminated with error (1). Closing log file.

离线

#2 2021-11-12 19:01:18

matrikslee
会员
注册时间: 2017-04-21
帖子: 298
个人网站

Re: X 服务启动失败

nv的显卡?应该是驱动炸了,用旧版本驱动吧

离线

#3 2021-11-13 07:07:04

silkriver
会员
注册时间: 2020-07-24
帖子: 119

Re: X 服务启动失败

我用官方驱动也出现过这样的问题,好像是未及时重启系统导致的。之后只要更新后提示重启就照办,到目前为止X服务一直都正常。

离线

#4 2021-11-18 11:53:55

Tamako
会员
注册时间: 2019-02-18
帖子: 23

Re: X 服务启动失败

更新一下,算是解决了。
之后几天在终端syu,又更新了一版nvidia显卡驱动,修改了一下x配置文件,报错信息发生变化,根据信息找到这个主题:https://bbs.archlinux.org/viewtopic.php?id=270862
nvidia 官方驱动不再支持本机显卡,根据下面的建议更换了nouveau,修改x配置文件,终于点亮屏幕。
但是体验不如从前,比如窗口偶尔闪烁,网页刷新或切换标签时偶尔闪现背后的窗口内容,对于有动画特效的网页帧率明显不足。
两人应该对此问题负责:
1. Nvidia,未兼容旧显卡。
2. ArchLinux,更新脚本未检查用户环境兼容性。
考虑是不是要换 Manjaro 了。

离线

#5 2021-11-18 13:29:02

luxni
会员
注册时间: 2014-06-08
帖子: 235

Re: X 服务启动失败

问题来了,为什么更新脚本要检查用户环境兼容性?

Tamako 说:

更新一下,算是解决了。
之后几天在终端syu,又更新了一版nvidia显卡驱动,修改了一下x配置文件,报错信息发生变化,根据信息找到这个主题:https://bbs.archlinux.org/viewtopic.php?id=270862
nvidia 官方驱动不再支持本机显卡,根据下面的建议更换了nouveau,修改x配置文件,终于点亮屏幕。
但是体验不如从前,比如窗口偶尔闪烁,网页刷新或切换标签时偶尔闪现背后的窗口内容,对于有动画特效的网页帧率明显不足。
两人应该对此问题负责:
1. Nvidia,未兼容旧显卡。
2. ArchLinux,更新脚本未检查用户环境兼容性。
考虑是不是要换 Manjaro 了。


虽然人菜菜的,但也想做个有趣的人。

离线

#6 2021-11-18 14:57:46

SamLukeYes
会员
所在地: Canton, China
注册时间: 2020-07-19
帖子: 173
个人网站

Re: X 服务启动失败

Tamako 说:

两人应该对此问题负责:
1. Nvidia,未兼容旧显卡。
2. ArchLinux,更新脚本未检查用户环境兼容性。
考虑是不是要换 Manjaro 了。

NVIDIA 是否应该负责我不知道,这取决于你和 NVIDIA 之间的协议。
Arch Linux 没有理由为这种事情负责,使用 Arch Linux 的任何后果都应该由用户自行承担。如果不同意这一点,那么恐怕大多数 GNU/Linux 发行版都不适合你。
如果你想要一个永远不会因为更新而损坏的发行版,那么你需要的是 NixOS。Manjaro 在大多数时候只是把事情弄得更糟糕。


Using Arch Linux on Surface Pro 6

离线

#7 2021-11-18 17:09:27

Mr.I
路人丙
所在地: Kerbal
注册时间: 2015-08-29
帖子: 249

Re: X 服务启动失败

Archlinux  ==>  Manjaro  ❌
NVIDIA  ==>  AMD  ✅

离线

#8 2021-11-19 05:44:34

twobooks
会员
所在地: rainforest
注册时间: 2020-05-19
帖子: 45

Re: X 服务启动失败

可以根据你的显卡型号选用AUR包 nvidia-390xx-dkms, nvidia-390xx-utils 或 nvidia-340xx-dkms, nvidia-340xx-utils 等等
每次内核更新可能要从新下载编译 dkms 包, 比如 5.14.16 => 5.15.2, 但 5.14.11 => 5.14.16 就可以省略了。

离线

#9 2021-11-19 08:51:15

SamLukeYes
会员
所在地: Canton, China
注册时间: 2020-07-19
帖子: 173
个人网站

Re: X 服务启动失败

twobooks 说:

每次内核更新可能要从新下载编译 dkms 包, 比如 5.14.16 => 5.15.2, 但 5.14.11 => 5.14.16 就可以省略了。

dkms 不是每次更新内核的时候都会自己重新编译吗


Using Arch Linux on Surface Pro 6

离线

#10 2021-11-19 09:35:53

twobooks
会员
所在地: rainforest
注册时间: 2020-05-19
帖子: 45

Re: X 服务启动失败

解开一个包你就知道了, 比如 nvidia-340xx.tar.gz

-rw-r--r-- 1 twobooks users 25417 Nov 11 04:46 0001-kernel-5.7.patch
-rw-r--r-- 1 twobooks users  3104 Nov 11 04:46 0002-kernel-5.8.patch
-rw-r--r-- 1 twobooks users  3508 Nov 11 04:46 0003-kernel-5.9.patch
-rw-r--r-- 1 twobooks users   762 Nov 11 04:46 0004-kernel-5.10.patch
-rw-r--r-- 1 twobooks users  6439 Nov 11 04:46 0005-kernel-5.11.patch
-rw-r--r-- 1 twobooks users  6443 Nov 11 04:46 0006-kernel-5.14.patch
-rw-r--r-- 1 twobooks users   275 Nov 11 04:46 20-nvidia.conf
-rw-r--r-- 1 twobooks users   350 Nov 11 04:46 nvidia-340xx.install
-rw-r--r-- 1 twobooks users  4102 Nov 11 04:46 PKGBUILD

有些内核升级时 AUR Nvidia Driver 需要一个patch, pacman不会帮你下载这个patch, yay能不能我没有用过不知道。

最近编辑记录 twobooks (2021-11-19 09:39:09)

离线

#11 2021-11-19 11:35:27

SamLukeYes
会员
所在地: Canton, China
注册时间: 2020-07-19
帖子: 173
个人网站

Re: X 服务启动失败

twobooks 说:

解开一个包你就知道了, 比如 nvidia-340xx.tar.gz

-rw-r--r-- 1 twobooks users 25417 Nov 11 04:46 0001-kernel-5.7.patch
-rw-r--r-- 1 twobooks users  3104 Nov 11 04:46 0002-kernel-5.8.patch
-rw-r--r-- 1 twobooks users  3508 Nov 11 04:46 0003-kernel-5.9.patch
-rw-r--r-- 1 twobooks users   762 Nov 11 04:46 0004-kernel-5.10.patch
-rw-r--r-- 1 twobooks users  6439 Nov 11 04:46 0005-kernel-5.11.patch
-rw-r--r-- 1 twobooks users  6443 Nov 11 04:46 0006-kernel-5.14.patch
-rw-r--r-- 1 twobooks users   275 Nov 11 04:46 20-nvidia.conf
-rw-r--r-- 1 twobooks users   350 Nov 11 04:46 nvidia-340xx.install
-rw-r--r-- 1 twobooks users  4102 Nov 11 04:46 PKGBUILD

有些内核升级时 AUR Nvidia Driver 需要一个patch, pacman不会帮你下载这个patch, yay能不能我没有用过不知道。

我不知道你是怎么检查 AUR 软件包的更新的,反正常用的 AUR helper 肯定都有检查更新的功能。如果打包过程有影响软件包内容的更新(例如增加了新 patch),维护者会 bump pkgrel,这样用户就能收到更新的通知。如果维护者没有 bump pkgrel,那就属于打包错误了,应该向软件包维护者报告问题;但如果是你自己获取更新信息的渠道不畅通,那就是你自己的问题了。注意这不是通常所说的 rebuild,AUR 软件包原则上不为不更改任何源文件的 rebuild 而 bump pkgrel。


Using Arch Linux on Surface Pro 6

离线

页脚