Fatal server error ee xf86openconsole switching vt failed - Исправление ошибок и поиск оптимальных решений проблем

Содержание

Arch Linux
#1 2020-02-14 12:29:38
[Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#2 2020-02-14 12:49:21
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#3 2020-02-14 12:54:22
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#4 2020-02-14 13:01:36
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#5 2020-02-14 13:07:50
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#6 2020-02-14 13:09:50
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#7 2020-02-14 13:13:52
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#8 2020-02-14 13:23:40
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#9 2020-02-14 13:27:57
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#10 2020-02-14 13:28:14
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#11 2020-02-14 13:31:29
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#12 2020-02-14 13:41:48
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
#13 2020-02-14 14:17:28
Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual
On WSL, startx gets fatal server error: x86OpenConsole: Switching VT failed #3946
Comments
Thread: Startx wont work
Startx wont work
Re: Startx wont work
Re: Startx wont work
Re: Startx wont work

Arch Linux

You are not logged in.

#1 2020-02-14 12:29:38

[Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

This is my log file (/home/user/.local/share/Xorg.1.log):

[ 176.323] (++) using VT number 1

[ 176.324] (EE) systemd-logind: TakeControl failed: Only owner of session may take control
[ 176.325] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 176.326] (—) PCI:*(0@0:2:0) 8086:1616:17aa:5036 rev 9, Mem @ 0xe0000000/16777216, 0xc0000000/536870912, I/O @ 0x00003000/64, BIOS @ 0x. /131072
[ 176.326] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 176.326] (II) «glx» will be loaded. This was enabled by default and also specified in the config file.
[ 176.326] (II) LoadModule: «glx»
[ 176.327] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 176.328] (II) Module glx: vendor=»X.Org Foundation»
[ 176.328] compiled for 1.20.7, module version = 1.0.0
[ 176.328] ABI class: X.Org Server Extension, version 10.0
[ 176.328] (II) LoadModule: «modesetting»
[ 176.328] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 176.328] (II) Module modesetting: vendor=»X.Org Foundation»
[ 176.328] compiled for 1.20.7, module version = 1.20.7
[ 176.328] Module class: X.Org Video Driver
[ 176.328] ABI class: X.Org Video Driver, version 24.1
[ 176.328] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 176.328] (EE)
Fatal server error:
[ 176.330] (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)
[ 176.331] (EE)
[ 176.332] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 176.335] (EE) Please also check the log file at «/home/arch-user/.local/share/xorg/Xorg.1.log» for additional information.
[ 176.336] (EE)
[ 176.337] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
[ 176.337] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
[ 176.337] (EE) Server terminated with error (1). Closing log file.

Startx wont work since I try some new setup for my I3 from this git : https://github.com/simrat39/dotfiles

Thanks,

PS : sorry for my english

Last edited by StickySpooky (2020-02-14 14:31:18)

#2 2020-02-14 12:49:21

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

If you reverse the changes made by that script is the issue still present?
/home/user/.local/share/Xorg.1.log appears to be missing the start of the log. Please post the whole log file in code tags.

#3 2020-02-14 12:54:22

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

Here is my full log :

[ 176.308] (WW) Failed to open protocol names file lib/xorg/protocol.txt
[ 176.309]
X.Org X Server 1.20.7
X Protocol Version 11, Revision 0
[ 176.312] Build Operating System: Linux Arch Linux
[ 176.313] Current Operating System: Linux arch-arthur 5.4.13-arch1-1 #1 SMP PREEMPT Fri, 17 Jan 2020 23:09:54 +0000 x86_64
[ 176.313] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5c6fae45-fdb9-4fc2-b0b7-7e24bdc7a287 rw loglevel=3 quiet
[ 176.315] Build Date: 14 January 2020 07:13:52AM
[ 176.315]
[ 176.316] Current version of pixman: 0.38.4
[ 176.317] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 176.317] Markers: (—) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 176.320] (==) Log file: «/home/arch-user/.local/share/xorg/Xorg.1.log», Time: Fri Feb 14 11:04:50 2020
[ 176.321] (==) Using config file: «/etc/X11/xorg.conf»
[ 176.322] (==) Using system config directory «/usr/share/X11/xorg.conf.d»
[ 176.322] (==) ServerLayout «X.org Configured»
[ 176.322] (**) |—>Screen «Screen0» (0)
[ 176.322] (**) | |—>Monitor «Monitor0»
[ 176.322] (**) | |—>Device «Card0»
[ 176.322] (**) |—>Input Device «Mouse0»
[ 176.322] (**) |—>Input Device «Keyboard0»
[ 176.322] (==) Automatically adding devices
[ 176.322] (==) Automatically enabling devices
[ 176.322] (==) Automatically adding GPU devices
[ 176.322] (==) Automatically binding GPU devices
[ 176.322] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 176.322] (WW) The directory «/usr/share/fonts/OTF» does not exist.
[ 176.322] Entry deleted from font path.
[ 176.322] (WW) The directory «/usr/share/fonts/Type1» does not exist.
[ 176.322] Entry deleted from font path.
[ 176.322] (WW) The directory «/usr/share/fonts/100dpi» does not exist.
[ 176.322] Entry deleted from font path.
[ 176.322] (WW) The directory «/usr/share/fonts/75dpi» does not exist.
[ 176.322] Entry deleted from font path.
[ 176.322] (WW) The directory «/usr/share/fonts/OTF» does not exist.
[ 176.322] Entry deleted from font path.
[ 176.322] (WW) The directory «/usr/share/fonts/Type1» does not exist.
[ 176.322] Entry deleted from font path.
[ 176.322] (WW) The directory «/usr/share/fonts/100dpi» does not exist.
[ 176.322] Entry deleted from font path.
[ 176.322] (WW) The directory «/usr/share/fonts/75dpi» does not exist.
[ 176.322] Entry deleted from font path.
[ 176.322] (**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/TTF,
/usr/share/fonts/misc,
/usr/share/fonts/TTF
[ 176.322] (**) ModulePath set to «/usr/lib/xorg/modules»
[ 176.322] (WW) Hotplugging is on, devices using drivers ‘kbd’, ‘mouse’ or ‘vmmouse’ will be disabled.
[ 176.322] (WW) Disabling Mouse0
[ 176.322] (WW) Disabling Keyboard0
[ 176.322] (II) Module ABI versions:
[ 176.322] X.Org ANSI C Emulation: 0.4
[ 176.322] X.Org Video Driver: 24.1
[ 176.322] X.Org XInput driver : 24.1
[ 176.322] X.Org Server Extension : 10.0
[ 176.323] (++) using VT number 1

#4 2020-02-14 13:01:36

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

How do you login as arch-user?
What is the output of

See https://bbs.archlinux.org/help.php#bbcode for the difference between quote tags and code tags.

#5 2020-02-14 13:07:50

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

I log with «su» command , I was on the root account.

Last edited by StickySpooky (2020-02-14 13:08:37)

#6 2020-02-14 13:09:50

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

If you logout as root and login as arch-user then execute startx is the issue still present?

#7 2020-02-14 13:13:52

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

There are quite a few things done in that script that are very specific to that user.Are you simrat93 ? If not you really shouldn’t use anything from there. And especially not that .xinitrc .

#8 2020-02-14 13:23:40

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

Ok, I got another problem, here is the log file :

When I do the startx, it launch the xserver but then closed instantly with an error message :

Last edited by StickySpooky (2020-02-14 13:26:29)

#9 2020-02-14 13:27:57

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

There are quite a few things done in that script that are very specific to that user.Are you simrat93 ? If not you really shouldn’t use anything from there. And especially not that .xinitrc .

I am not, just wanna try his I3 settup, that was a bad idea to execute his python script

#10 2020-02-14 13:28:14

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

If you are still using the config from that repo. that .xinitrc is broken. exec i3 should be the last line without a &, nm-applet should have a & but no exec and you are missing a whole lot of necessary and relevant preconditions: https://wiki.archlinux.org/index.php/Xinit#xinitrc read the blue note boxes.

Edit: Yes you definitely shouldn’t have. Even if the .xinitrc was the only thing that was broken there is a whole lot in that repo, that hardcodedly assumes your user to be simrat93 and does quite a few invasive changed based on that assumption. You can «repair» out of this but you have to check all the files that were adjusted.

Last edited by V1del (2020-02-14 13:32:23)

#11 2020-02-14 13:31:29

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

Thanks, the desktop WORKS, thanks that was my xinitrc

#12 2020-02-14 13:41:48

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

How do I tag solved ?

#13 2020-02-14 14:17:28

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

How do I tag solved ?

Edit your first post and add [SOLVED] to the title.

How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.

Источник

On WSL, startx gets fatal server error: x86OpenConsole: Switching VT failed #3946

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.

If you have a feature request, please post to the UserVoice.

If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.

Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from «C:Windowsminidump».

Please fill out the below information:

Your Windows build number: (Type ver at a Windows Command Prompt)

What you’re doing and what’s happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

What’s wrong / what should be happening instead:

Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args , and link the contents of some_command.strace in a gist here).

For WSL launch issues, please collect detailed logs.

The text was updated successfully, but these errors were encountered:

Источник

Thread: Startx wont work

Thread Tools

Display

Startx wont work

Simply put, im using Linux Subsystem for Windows, which used 16.04, but when i try to use STARTX, i receive this error

im trying to launch either the Lubuntu Desktop environment, or the MATE, whichever i can get to load, id be happy

Re: Startx wont work

I am just trying to wrap my head around what you are actually running, since it mentions Microsoft. Is this something that is supposed to run in Microsoft Windows, or Wubi (no longer supported), or in a virtual machine in Windows? Linux typically uses vt1-vt6 for text terminals and vt7 for X, but your system is apparently having a problem switching to vt7 for X. What hardware do you have, including graphics hardware and drivers?

I have run various Linux versions in (Oracle) Virtualbox, but on an Ubuntu host, I have not run Windows in virtualbox or virtualbox on a Windows host. If you run something under Windows, it could be exposed to Windows vulnerabilities and slowness (with all the antivirus and malicious software scanning and checking for and installing updates). I recently had a low end Win10 laptop spend 8 hours alternately hogging my Internet and 100% disk access, and even after settling down some, alternating between 40% cpu time and 100% disk access installing major updates for about 8 hours including rebooting several times. Fortunately the laptop also dual boots Ubuntu 16.04, so I can use my Java stock/option trading platform (thinkorswim) in Ubuntu on that laptop while Chromecasting investing education (not available in Linux) from my Android phone to the 32″ 1080p HDTV I use as a monitor for my desktop PC.

Re: Startx wont work

A short google for «Linux subsystem for windows xserver» led me to this article. You need an xserver on Windows to run graphical Linux applications in the Linux subsystem for Windows.

Re: Startx wont work

Windows 10 provides a Feature called «Windows Subsystem for Linux,» Which allows you to run a full Ubuntu Bash Shell, within windows, no restrictions other than having no Native GUI support

Источник

Hello,

It is Ubuntu 18.04.1 on Windows Subsystem for linux.
      a@W0:~$ cat /etc/lsb-release
      DISTRIB_ID=Ubuntu
      DISTRIB_RELEASE=18.04
      DISTRIB_CODENAME=bionic
      DISTRIB_DESCRIPTION=»Ubuntu 18.04.1 LTS»

It is not possible to run the command «startx».
the first time, I found a problem with DBUS, solved this way:
sudo mkdir /var/run/dbus
sudo dbus-daemon —config-file=/usr/share/dbus-1/system.conf

Now, I have the error indicated above.
I do not know if it’s because of my correction or for some other Reason.
Serious errors are as follows:
   a@W0:~$ cat /var/log/Xorg.1.log | grep EE
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
   [ 12722.394] (EE) systemd-logind: failed to get session: PID 1320 does not belong to any known session
   [ 12722.401] (EE)
   [ 12722.402] (EE) xf86OpenConsole: Switching VT failed
   [ 12722.403] (EE)
   [ 12722.403] (EE)
   [ 12722.404] (EE) Please also check the log file at «/var/log/Xorg.1.log» for additional information.
   [ 12722.405] (EE)
   [ 12722.407] (EE) Server terminated with error (1). Closing log file.

Thank you for your advice
—
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
DistroRelease: Ubuntu 18.04
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Microsoft 4.4.0-17134.471-Microsoft 4.4.35
Tags: bionic uec-images
Uname: Linux 4.4.0-17134-Microsoft x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
—
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
DistroRelease: Ubuntu 18.04
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Microsoft 4.4.0-17134.471-Microsoft 4.4.35
Tags: bionic uec-images
Uname: Linux 4.4.0-17134-Microsoft x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
—
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
DistroRelease: Ubuntu 18.04
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Microsoft 4.4.0-17134.471-Microsoft 4.4.35
Tags: bionic uec-images
Uname: Linux 4.4.0-17134-Microsoft x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Источник

Печать

Страницы: [1] Вниз

Тема: Установил графическую оболочку в Ubuntu — она не запускается (Прочитано 2177 раз)

0 Пользователей и 1 Гость просматривают эту тему.

angryelizar

Установил графическую оболочку в Ubuntu — она не запускается.

При вводе команды startx выдает это

X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-97-generic x86_64 Ubuntu Current Operating System: Linux DESKTOP-UM857VQ 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014 x86_64 Kernel command line: BOOT_IMAGE=/kernel init=/init ro Build Date: 13 October 2017 01:57:05PM xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Fri Nov 3 10:31:32 2017 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) xf86OpenConsole: Switching VT failed (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error Couldn't get a file descriptor referring to the console

Что это значит и как это исправить?

« Последнее редактирование: 03 Ноября 2017, 07:41:17 от angryelizar »

контроль — иллюзия

symon.2014

Что это значит и как это исправить?

Система подсказывыет заглянуть сначала сюда.

cat /var/log/Xorg.1.log ну и здесь показать.

angryelizar

[ 5.789] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 5.790] X Protocol Version 11, Revision 0 [ 5.790] Build Operating System: Linux 4.4.0-97-generic x86_64 Ubuntu [ 5.790] Current Operating System: Linux DESKTOP-UM857VQ 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014 x86_64 [ 5.790] Kernel command line: BOOT_IMAGE=/kernel init=/init ro [ 5.790] Build Date: 13 October 2017 01:57:05PM [ 5.790] xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) [ 5.790] Current version of pixman: 0.33.6 [ 5.791] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 5.791] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 5.792] (==) Log file: "/var/log/Xorg.1.log", Time: Fri Nov 3 10:31:32 2017 [ 5.798] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 5.799] (==) No Layout section. Using the first Screen section. [ 5.799] (==) No screen section available. Using defaults. [ 5.799] (**) |-->Screen "Default Screen Section" (0) [ 5.799] (**) | |-->Monitor "<default monitor>" [ 5.799] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 5.799] (==) Automatically adding devices [ 5.799] (==) Automatically enabling devices [ 5.799] (==) Automatically adding GPU devices [ 5.799] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 5.800] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 5.800] Entry deleted from font path. [ 5.801] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 5.801] Entry deleted from font path. [ 5.801] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 5.801] Entry deleted from font path. [ 5.802] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 5.802] Entry deleted from font path. [ 5.802] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 5.802] Entry deleted from font path. [ 5.802] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [ 5.802] (==) ModulePath set to "/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules" [ 5.802] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 5.802] (II) Loader magic: 0x7fc5e9e3edc0 [ 5.802] (II) Module ABI versions: [ 5.802] X.Org ANSI C Emulation: 0.4 [ 5.802] X.Org Video Driver: 20.0 [ 5.802] X.Org XInput driver : 22.1 [ 5.802] X.Org Server Extension : 9.0 [ 5.803] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) [ 5.803] (++) using VT number 1


[     5.803] (II) no primary bus or device found
[     5.803] (II) LoadModule: "glx"
[     5.814] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     5.830] (II) Module glx: vendor="X.Org Foundation"
[     5.830]    compiled for 1.18.4, module version = 1.0.0
[     5.830]    ABI class: X.Org Server Extension, version 9.0
[     5.831] (==) AIGLX enabled
[     5.831] (==) Matched modesetting as autoconfigured driver 0
[     5.831] (==) Matched fbdev as autoconfigured driver 1
[     5.831] (==) Matched vesa as autoconfigured driver 2
[     5.831] (==) Assigned the driver to the xf86ConfigLayout
[     5.831] (II) LoadModule: "modesetting"
[     5.835] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     5.835] (II) Module modesetting: vendor="X.Org Foundation"
[     5.835]    compiled for 1.18.4, module version = 1.18.4
[     5.835]    Module class: X.Org Video Driver
[     5.836]    ABI class: X.Org Video Driver, version 20.0
[     5.836] (II) LoadModule: "fbdev"
[     5.839] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[     5.840] (II) Module fbdev: vendor="X.Org Foundation"
[     5.840]    compiled for 1.18.1, module version = 0.4.4
[     5.840]    Module class: X.Org Video Driver
[     5.840]    ABI class: X.Org Video Driver, version 20.0
[     5.840] (II) LoadModule: "vesa"
[     5.844] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     5.844] (II) Module vesa: vendor="X.Org Foundation"
[     5.844]    compiled for 1.18.1, module version = 2.3.4
[     5.844]    Module class: X.Org Video Driver
[     5.844]    ABI class: X.Org Video Driver, version 20.0
[     5.844] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     5.845] (II) FBDEV: driver for framebuffer: fbdev
[     5.845] (II) VESA: driver for VESA chipsets: vesa
[     5.845] (WW) xf86OpenConsole: VT_GETSTATE failed: Inappropriate ioctl for device
[     5.845] (WW) xf86OpenConsole: VT_ACTIVATE failed: Inappropriate ioctl for device
[     5.845] (EE)
Fatal server error:
[     5.845] (EE) xf86OpenConsole: Switching VT failed
[     5.846] (EE)
[     5.846] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[     5.846] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[     5.847] (EE)
[     5.851] (WW) xf86CloseConsole: KDSETMODE failed: Inappropriate ioctl for device
[     5.851] (WW) xf86CloseConsole: VT_GETMODE failed: Inappropriate ioctl for device
[     5.852] (EE) Server terminated with error (1). Closing log file.

symon.2014

5.803] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound

systemctl -a | grep dbus
PS. (ИМХО) И почему то мне кажется, что видюха nvidia , и ей не нравится свободный драйвер.

angryelizar

Теперь выдаёт

Failed to connect to bus: No such file or directory

symon.2014

Установил графическую оболочку в Ubuntu

Изначально что поставил? Mini.iso или сервер? И видеокарта какая?

angryelizar

стыдно признаться, это Ubuntu с нового обновления винды Fall Creators Update.
Видеокарта — Intel HD Graphics

symon.2014

Так вроде там только консоль (впрочем не совсем в курсах )

angryelizar

Так вроде там только консоль (впрочем не совсем в курсах )

ну тогда ладно. полюбому я Ubuntu 17.10 второй системой поставил, пофиг
Спасибо за ответ!

Печать

Страницы: [1] Вверх

Источник

Description

Tomas Pelka

2018-11-26 10:21:42 UTC

Description of problem:
Xorg keeps respawning, I thing it was caused when I switch to second user while the first one was still logged in. 

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.20.3-3.el8.x86_64
xorg-x11-drv-nouveau-1.0.15-4.el8.1.x86_64
kernel-4.18.0-44.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
Nov 26 11:16:19 T5400 gdm-launch-environment][16054]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Nov 26 11:16:19 T5400 systemd-logind[1040]: Session c343 logged out. Waiting for processes to exit.
Nov 26 11:16:19 T5400 gdm[6691]: Child process -16061 was already dead.
Nov 26 11:16:19 T5400 gdm[6691]: Child process 16054 was already dead.
Nov 26 11:16:19 T5400 systemd-logind[1040]: Removed session c343.
Nov 26 11:16:19 T5400 gdm[6691]: Unable to kill session worker process
Nov 26 11:16:19 T5400 systemd-logind[1040]: New session c344 of user gdm.
Nov 26 11:16:19 T5400 systemd[1]: Started Session c344 of user gdm.
Nov 26 11:16:19 T5400 gdm-launch-environment][16081]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Nov 26 11:16:19 T5400 gdm-launch-environment][16081]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Nov 26 11:16:19 T5400 gdm[6691]: GdmDisplay: display lasted 0.195688 seconds
Nov 26 11:16:19 T5400 systemd-logind[1040]: Session c344 logged out. Waiting for processes to exit.
Nov 26 11:16:19 T5400 gdm[6691]: Child process -16088 was already dead.
Nov 26 11:16:19 T5400 gdm[6691]: Child process 16081 was already dead.
Nov 26 11:16:19 T5400 gdm[6691]: Unable to kill session worker process
Nov 26 11:16:19 T5400 systemd-logind[1040]: Removed session c344.
Nov 26 11:16:19 T5400 systemd-logind[1040]: New session c345 of user gdm.
Nov 26 11:16:19 T5400 systemd[1]: Started Session c345 of user gdm.
Nov 26 11:16:19 T5400 gdm-launch-environment][16110]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: _XSERVTransMakeAllCOTSServerListeners: server already running
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: _XSERVTransMakeAllCOTSServerListeners: server already running
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (--) Log file renamed from "/var/lib/gdm/.local/share/xorg/Xorg.pid-16120.log" to "/var/lib/gdm/.local/share/xorg/Xorg.2.log"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: X.Org X Server 1.20.3
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: X Protocol Version 11, Revision 0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Build Operating System:  4.14.0-49.el7a.noaead.x86_64
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Current Operating System: Linux T5400 4.18.0-44.el8.x86_64 #1 SMP Fri Nov 23 20:37:53 UTC 2018 x86_64
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-4.18.0-44.el8.x86_64 root=/dev/mapper/rhel-rhel8 ro resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/rhel8 rd.lvm.lv=rhel/swap rhgb quiet
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Build Date: 19 November 2018  04:45:34PM
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Build ID: xorg-x11-server 1.20.3-3.el8
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Current version of pixman: 0.34.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         Before reporting problems, check http://wiki.x.org
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         to make sure that you have the latest version.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Markers: (--) probed, (**) from config file, (==) default setting,
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         (++) from command line, (!!) notice, (II) informational,
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Log file: "/var/lib/gdm/.local/share/xorg/Xorg.2.log", Time: Mon Nov 26 11:16:19 2018
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Using config directory: "/etc/X11/xorg.conf.d"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) No Layout section.  Using the first Screen section.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) No screen section available. Using defaults.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (**) |-->Screen "Default Screen Section" (0)
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (**) |   |-->Monitor "<default monitor>"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) No monitor specified for screen "Default Screen Section".
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         Using a default monitor configuration.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Automatically adding devices
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Automatically enabling devices
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Automatically adding GPU devices
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Automatically binding GPU devices
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Max clients allowed: 256, resource mask: 0x1fffff
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) FontPath set to:
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         catalogue:/etc/X11/fontpath.d,
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         built-ins
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) ModulePath set to "/usr/lib64/xorg/modules"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) The server relies on udev to provide the list of input devices.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         If no devices become available, reconfigure udev or disable AutoAddDevices.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Loader magic: 0x55908332d020
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Module ABI versions:
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         X.Org ANSI C Emulation: 0.4
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         X.Org Video Driver: 24.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         X.Org XInput driver : 24.1
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         X.Org Server Extension : 10.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (++) using VT number 1
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) systemd-logind: took control of session /org/freedesktop/login1/session/c345
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) xfree86: Adding drm device (/dev/dri/card0)
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 14 paused 0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (--) PCI:*(1@0:0:0) 10de:1c81:19da:2454 rev 161, Mem @ 0xfb000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000dc80/128, BIOS @ 0x????????/65536
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) LoadModule: "glx"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Module glx: vendor="X.Org Foundation"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         compiled for 1.20.3, module version = 1.0.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         ABI class: X.Org Server Extension, version 10.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Matched modesetting as autoconfigured driver 0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Matched fbdev as autoconfigured driver 1
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Matched vesa as autoconfigured driver 2
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (==) Assigned the driver to the xf86ConfigLayout
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) LoadModule: "modesetting"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Module modesetting: vendor="X.Org Foundation"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         compiled for 1.20.3, module version = 1.20.3
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         Module class: X.Org Video Driver
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         ABI class: X.Org Video Driver, version 24.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) LoadModule: "fbdev"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Module fbdev: vendor="X.Org Foundation"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         compiled for 1.20.1, module version = 0.5.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         Module class: X.Org Video Driver
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         ABI class: X.Org Video Driver, version 24.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) LoadModule: "vesa"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) Module vesa: vendor="X.Org Foundation"
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         compiled for 1.20.2, module version = 2.4.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         Module class: X.Org Video Driver
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:         ABI class: X.Org Video Driver, version 24.0
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) FBDEV: driver for framebuffer: fbdev
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (II) VESA: driver for VESA chipsets: vesa
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (WW) xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (EE)
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Fatal server error:
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (EE) xf86OpenConsole: Switching VT failed
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (EE)
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Please consult the The X.Org Foundation support
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:          at http://wiki.x.org
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]:  for help.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (EE) Please also check the log file at "/var/lib/gdm/.local/share/xorg/Xorg.2.log" for additional information.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (EE)
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (WW) xf86CloseConsole: KDSETMODE failed: Operation not permitted
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (WW) xf86CloseConsole: VT_SETMODE failed: Operation not permitted
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (WW) xf86CloseConsole: VT_ACTIVATE failed: Operation not permitted
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: (EE) Server terminated with error (1). Closing log file.
Nov 26 11:16:19 T5400 /usr/libexec/gdm-x-session[16116]: Unable to run X server


Expected results:


Additional info:
NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1)

Comment 1

Tomas Pelka

2018-11-26 10:25:08 UTC

Also can see following messages from kernel:

Nov 26 11:24:10 T5400 kernel: nouveau 0000:01:00.0: DRM: core notifier timeout
Nov 26 11:24:12 T5400 kernel: nouveau 0000:01:00.0: DRM: core notifier timeout
Nov 26 11:24:14 T5400 kernel: nouveau 0000:01:00.0: DRM: base-0: timeout
Nov 26 11:24:16 T5400 kernel: nouveau 0000:01:00.0: DRM: core notifier timeout
Nov 26 11:24:18 T5400 kernel: nouveau 0000:01:00.0: DRM: base-1: timeout
Nov 26 11:24:20 T5400 kernel: nouveau 0000:01:00.0: DRM: core notifier timeout
Nov 26 11:24:22 T5400 kernel: nouveau 0000:01:00.0: DRM: core notifier timeout

Comment 2

Tomas Pelka

2018-11-26 11:44:54 UTC

I can see kernel messaged above on NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) too.

Seems to be caused by DVI monitor attached to the output, if I boot single head using DP only I can't see these messages.

Comment 7

RHEL Program Management

2021-02-01 07:30:45 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Источник

[solved] raspberry and vc4

Hi, how do i enable vc4 on raspberry pi 3 b?
do i have to recompile kernel?
» » mesa?
from a debian distro i see the compiling mesa tutorial

Code: Select all: git clone git://anongit.freedesktop.org/mesa/mesa cd mesa ./autogen.sh --prefix=$WLD --enable-gles2 --with-egl-platforms=x11,wayland,drm --enable-gbm --enable-shared-glapi --with-gallium-drivers=vc4 --without-dri-drivers --disable-va --disable-vdpau --disable-xvmc --disable-omx make -j4 && make install

it is a —disable-omx option on compiling mesa that focus my attention is vc4 the best video acceleration? could you address me to some tutorial that explains steps if this vc4 is available on raspberry pi 3 b on arch armv7h?

ciao e grazie !

Last edited by acconciox on Sun Nov 27, 2016 6:13 pm, edited 1 time in total.

acconciox: Posts: 110; Joined: Thu May 05, 2016 4:39 pm

Re: raspberry and vc4

by jaab » Mon Nov 21, 2016 8:28 pm

Please have a look at this post:

viewtopic.php?f=64&t=9811

The driver is supplied by Raspberry. Mesa supplied by Arch has vc4 support. The Raspberry driver is still under development but improving and generally usable.

I am not using it now. But when I did Firefox reported:
webGl renderer = Broadcom—Gallium 0.4 vc4 v3d 2.1

Regards,

jaab: Posts: 26; Joined: Sat Oct 22, 2016 8:32 am

Re: raspberry and vc4

by acconciox » Thu Nov 24, 2016 12:21 am

This is from
/home/alarm/.local/share/xorg/Xorg.0.log

Code: Select all: [ 156.367] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 156.369] (II) xfree86: Adding drm device (/dev/dri/card0) [ 156.370] (II) no primary bus or device found [ 156.370] falling back to /sys/devices/platform/soc/soc:gpu/drm/card0 [ 156.370] (II) LoadModule: "glx" [ 156.381] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 156.399] (II) Module glx: vendor="X.Org Foundation" [ 156.399] compiled for 1.18.4, module version = 1.0.0 [ 156.399] ABI class: X.Org Server Extension, version 9.0 [ 156.399] (==) AIGLX enabled [ 156.399] (II) LoadModule: "fbturbo" [ 156.399] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so [ 156.404] (II) Module fbturbo: vendor="X.Org Foundation" [ 156.404] compiled for 1.18.0, module version = 0.5.1 [ 156.404] Module class: X.Org Video Driver [ 156.404] ABI class: X.Org Video Driver, version 20.0 [ 156.404] (II) FBTURBO: driver for framebuffer: fbturbo [ 156.405] (WW) xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted [ 156.405] (EE) Fatal server error: [ 156.405] (EE) xf86OpenConsole: Switching VT failed [ 156.405] (EE) [ 156.405] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 156.405] (EE) Please also check the log file at "/home/alarm/.local/share/xorg/Xorg.0.log" for additional information. [ 156.405] (EE) [ 156.405] (WW) xf86CloseConsole: KDSETMODE failed: Operation not permitted [ 156.405] (WW) xf86CloseConsole: VT_SETMODE failed: Operation not permitted [ 156.405] (WW) xf86CloseConsole: VT_ACTIVATE failed: Operation not permitted [ 156.405] (EE) Server terminated with error (1). Closing log file.

thanks you i did this:

Code: Select all: VC4 runs well with parameters cmdline.txt: cma=128M # also tested 256 config.txt: gpu_mem=256 avoid_warnings=2 dtoverlay=vc4-kms-v3d and without xorg.conf

I’m not sure i understand this

and without xorg.conf

Code: Select all: locate xorg.conf /etc/X11/xorg.conf.d /etc/X11/xorg.conf.d/90-emulate3buttons.conf /etc/X11/xorg.conf.d/99-fbturbo.conf /usr/share/X11/xorg.conf.d /usr/share/X11/xorg.conf.d/10-evdev.conf /usr/share/X11/xorg.conf.d/10-quirks.conf /usr/share/X11/xorg.conf.d/70-synaptics.conf /usr/share/X11/xorg.conf.d/90-emulate3buttons.conf /usr/share/man/man5/xorg.conf.5.gz /usr/share/man/man5/xorg.conf.d.5.gz

I dont have this file: /vc4-kms-v3d-overlay.dtb

/boot/overlays:

Code: Select all: ls vc4* vc4-fkms-v3d.dtbo vc4-kms-v3d.dtbo

there is not /vc4-kms-v3d-overlay.dtb
how to install ?

im using this:

Code: Select all: Linux alarmpi 4.4.33-1-ARCH #1 SMP Sat Nov 19 14:09:17 MST 2016 armv7l GNU/Linux sing system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

after reinstalling xorg-server still i cant run startx

at the moment is there some user running vc4?

thanks you for help

acconciox: Posts: 110; Joined: Thu May 05, 2016 4:39 pm

Re: raspberry and vc4

by jaab » Thu Nov 24, 2016 9:32 pm

I have just done:

cd /etc/X11/xorg.conf.d
sudo mv 99-fbturbo.conf 99-fbturbo.~

Changed config.txt to:
gpu_mem=64
dtparam=audio=on
hdmi_drive=2
avoid_warnings=2
dtoverlay=vc4-kms-v3d

See part of my /var/log/Xorg.0.log

Code: Select all: 241.259] (==) Depth 24 pixmap format is 32 bpp [ 241.530] (==) modeset(0): Backing store enabled [ 241.530] (==) modeset(0): Silken mouse enabled [ 241.530] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message. [ 241.531] (==) modeset(0): DPMS enabled [ 241.531] (II) modeset(0): [DRI2] Setup complete [ 241.531] (II) modeset(0): [DRI2] DRI driver: vc4 [ 241.531] (II) modeset(0): [DRI2] VDPAU driver: vc4 [ 241.542] (--) RandR disabled [ 241.568] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 241.568] (II) AIGLX: enabled GLX_ARB_create_context [ 241.568] (II) AIGLX: enabled GLX_ARB_create_context_profile [ 241.568] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile [ 241.568] (II) AIGLX: enabled GLX_INTEL_swap_event [ 241.568] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 241.568] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB [ 241.568] (II) AIGLX: enabled GLX_ARB_fbconfig_float [ 241.568] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float [ 241.568] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 241.570] (II) AIGLX: Loaded and initialized vc4 [ 241.570] (II) GLX: Initialized DRI2 GL provider for screen 0

I am running it. I use ligthdm. xfce (gtk2) and lxde-gtk3 run fine. lxqt does not start. Calibre, a qt5 app, renders very poorly.

Ciao

jaab: Posts: 26; Joined: Sat Oct 22, 2016 8:32 am

Re: raspberry and vc4

by acconciox » Fri Nov 25, 2016 12:23 am

thanks !!!

cd /etc/X11/xorg.conf.d
sudo mv 99-fbturbo.conf 99-fbturbo.~

Changed config.txt to:
gpu_mem=64 # for mmal purpose 128 is probably better
dtparam=audio=on
hdmi_drive=2
avoid_warnings=2
dtoverlay=vc4-kms-v3d

it is also suggested cma=128 in /boot/cmdline.txt

acconciox: Posts: 110; Joined: Thu May 05, 2016 4:39 pm

Re: raspberry and vc4

by jaab » Fri Nov 25, 2016 8:42 am

Hi,

Before doing the changes I read this:

https://github.com/anholt/linux/wiki/Raspberry-Pi-3

Eric Anholt is the Broadcomm engineer supported by Raspberry for vc4 driver development. He recommends to keep gpu mem low, so I kept gpu at 64 mb.

Doing free before and after enabling vc4 shows a bump up in used memory. Enabling compositing in xfce window manager shows another bump up in user memory. vc4 has a memory cost. If you get into swapping you loose performance. With the fb driver I am swapping occasionally up to 150 mb.

Cma will improve driver performance at a cost for the rest of the system. I have not tested it enough to give an opinion.

Regards,

jaab: Posts: 26; Joined: Sat Oct 22, 2016 8:32 am

Re: raspberry and vc4

by acconciox » Fri Nov 25, 2016 11:01 am

if i try to use mpv

Code: Select all: mpv /media/MOVIE/test.avi Playing: /media/MOVIE/test.avi (+) Video --vid=1 (mpeg4) (+) Audio --aid=1 (mp3) * failed to add service - already in use?

vlc crash i have to restart x

ffplay works but

Code: Select all: libGL error: MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information

acconciox: Posts: 110; Joined: Thu May 05, 2016 4:39 pm

Re: raspberry and vc4

by jaab » Fri Nov 25, 2016 2:00 pm

cma=128 in /boot/cmdline.txt is probably advisable.

Below is the journalctl extract

Code: Select all: nov 24 23:01:17 alarmpi kernel: vc4-drm soc:gpu: failed to allocate buffer with size 7372800 nov 24 23:01:17 alarmpi kernel: vc4-drm soc:gpu: failed to allocate buffer with size 7372800 nov 24 23:01:17 alarmpi kernel: [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA: nov 24 23:01:21 alarmpi kernel: vc4-drm soc:gpu: failed to allocate buffer with size 9216000 nov 24 23:01:21 alarmpi kernel: vc4-drm soc:gpu: failed to allocate buffer with size 9216000 nov 24 23:01:21 alarmpi kernel: vc4-drm soc:gpu: failed to allocate buffer with size 9216000 nov 24 23:01:21 alarmpi kernel: vc4-drm soc:gpu: failed to allocate buffer with size 9216000 nov 24 23:01:21 alarmpi kernel: vc4-drm soc:gpu: failed to allocate buffer with size 9216000 nov 24 23:01:21 alarmpi kernel: vc4-drm soc:gpu: failed to allocate buffer with size 9216000 nov 24 23:01:21 alarmpi kernel: [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:

jaab: Posts: 26; Joined: Sat Oct 22, 2016 8:32 am

Re: raspberry and vc4

by acconciox » Sat Nov 26, 2016 12:55 am

Code: Select all: (II) xfree86: Adding drm device (/dev/dri/card0) [ 74.527] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0 [ 74.528] (II) no primary bus or device found

reading around from gentoo vc4 (im pretty desperate…)

Once you’re booted up, you can verify that your module is properly loaded with lsmod. You’re supposed to have a vc4 module in there. Also, it’s important to verify that /dev/dri/card0 exists. If you don’t have that device, nothing’s going to work.

after adding cma in config.txt
cma_lwm=16
cma_hwm=128
cma_offline_start=16
# dtoverlay=vc4-kms-v3d
* running without vc4 at the moment chromium crash system and i have to powerdown the raspi and reboot to write here

if you pointed me on one direction and i did not understand, please, point me on the right direction

acconciox: Posts: 110; Joined: Thu May 05, 2016 4:39 pm

Re: raspberry and vc4

by jaab » Sat Nov 26, 2016 10:24 pm

All I can say is that this is my config.txt

Code: Select all: [alarm@alarmpi boot]$ cat config.txt # See /boot/overlays/README for all available options gpu_mem=16 dtparam=audio=on hdmi_drive=2 avoid_warnings=2 dtoverlay=vc4-kms-v3d

Reduced gpu_mem in steps to 16 mb minimun as it is not used by the vc4 driver.

This is my cmdline.txt

Code: Select all: [alarm@alarmpi boot]$ cat cmdline.txt root=/dev/sda2 rw rootwait rootdelay=5 console=ttyAMA0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200 elevator=bfq

No cma. See my Xorg.0.log

Code: Select all: [ 27.006] Kernel command line: 8250.nr_uarts=0 cma=256M@256M dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1200 bcm2709.boardrev=0xa02082 bcm2709.serial=0xf4e8cf48 smsc95xx.macaddr=B8:27:EB:E8:CF:48 bcm2708_fb.fbswap=1 bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 root=/dev/sda2 rw rootwait rootdelay=5 console=ttyS0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyS0,115200 elevator=bfq

It seems that when the KMS driver kicks in it sets the cma for itsd buffers??

My mpv works:

Code: Select all: [alarm@alarmpi Vídeos]$ mpv There_Will_Be_Blood_2007_DVDRip_x264.mp4 Playing: There_Will_Be_Blood_2007_DVDRip_x264.mp4 (+) Video --vid=1 (*) (h264) (+) Audio --aid=1 --alang=eng (*) (aac) libGL error: MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information AO: [alsa] 48000Hz stereo 2ch float VO: [opengl] 712x426 => 1012x426 yuv420p [osd/libass] PlayResX undefined, setting to 960 (Paused) AV: 00:18:54 / 02:31:52 (12%) A-V: 0.000

It must be something else.

Regards,

jaab: Posts: 26; Joined: Sat Oct 22, 2016 8:32 am

Return to ARMv7h

Who is online

Users browsing this forum: No registered users and 1 guest

Источник

I need help running the Windows Subsystem for Linux

I followed these instructions: «How to Run a Linux Desktop Using the Windows Subsystem for Linux«.
But instead of installing the LXDE environment I chose Gnome. Other than that I did exactly as instructed.

So towards the end of the page after running XLaunch, I am supposed to enter this command «

startlxde«, assuming I installed the LXDE environment. So what am I supposed to enter if I installed Gnome? startgnome did not work.

Thanks guys

JDL

Re: I need help running the Windows Subsystem for Linux

You should be able to just type in: startx

Re: I need help running the Windows Subsystem for Linux

Quote Originally Posted by yancek

You should be able to just type in: startx

I tried it. It told me that that command was not found, but I could install «xinit», so I did.
When I used «startx» again after installing xinit, it replied this:

Code:

 startx  xauth:  file /home/drpeppercan/.Xauthority does not exist   config/udev: failed to bind the udev monitor   [config] failed to pre-init udev  X.Org X Server 1.20.9  X Protocol Version 11, Revision 0   Build Operating System: Linux 4.15.0-130-generic x86_64 Ubuntu  Current Operating System: Linux DESKTOP-TKTALUL 4.4.0-19041-Microsoft #488-Microsoft Mon Sep 01 13:43:00 PST 2020 x86_64Kernel command line: BOOT_IMAGE=/kernel init=/init   Build Date: 17 January 2021  09:13:31AM                                                                                 xorg-server 2:1.20.9-2ubuntu1.2~20.04.1 (For technical support please see http://www.ubuntu.com/support)                Current version of pixman: 0.38.4  Before reporting problems, check http://wiki.x.org  to make sure that you have the latest version.  Markers: (--) probed, (**) from config file, (==) default setting,   (++) from command line, (!!) notice, (II) informational,  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar  6 07:12:48 2021                                                    (==) Using system config directory "/usr/share/X11/xorg.conf.d"  (EE)   Fatal server error:   (EE) xf86OpenConsole: Switching VT failed   (EE)  (EE)  Please consult the The X.Org Foundation support  at http://wiki.x.org  for help.   (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.  (EE)   (EE) Server terminated with error (1). Closing log file.  xinit: connection to X server lost   deallocvt: ioctl VT_DISALLOCATE: Inappropriate ioctl for device

Last edited by javierdl; March 6th, 2021 at 03:58 PM.

Re: I need help running the Windows Subsystem for Linux

I’ve never used MS-WSL with a GUI, since it is a text only solution to my knowledge. You’ll need to run an X/Server as a Windows program. The free ones are less than great, IME.

If you want a full Unix/Linux GUI on a system running MS-Windows, use a virtual machine like virtualbox and install a normal Linux distro. Gnome is fairly bloated, so it will likely have bad performance compared to almost any other DE in that situation. Be certain to provide the maximum allowed GPU-RAM. The default amount is fine for a Linux server, but not for any desktop. You can change between different DEs in linux, since the GUI is just another program. The only trick is to avoid conflicting user settings. For that, when you are trying lots of different GUIs, create a new userid for each DE you want to try out. That will prevent settings for each userid running a different DE/GUI from writing to the same files. KDE won’t conflict with Gnome, but most of the other GUIs are Gnome-based.

LXDE was replaced a few yrs ago by LXQt. They changed from GTK to Qt for the libraries used. Qt is what KDE uses. GTK is what Gnome, Mate, Cinnamon, and most others. Of course, you don’t need a DE at all. Those are 100% optional. DEs run on top of a Window Manager (WM). Running with just a WM is much lighter, but takes a little more skill than someone completely new would have.

BTW, when following a guide, maybe follow it exactly, get that working, then try doing something different.

One last thing. By running an X/Server, you can run X/Clients on other Unix systems. Normally, we do that only on the same LAN, but that isn’t actually a hard limitation. It is possible to run X/Client applications over the internet to be displayed on your local X/Server. Depending on the bandwidth between the systems, it could be an ok experience.

Re: I need help running the Windows Subsystem for Linux

TheFu thank you so much for sharing your insight about MS-WSL. It will help me to lower my expectations of it, keeping me from a disappointment. So I will try to get it working mostly out of curiosity. As opposed to expecting to replace my dual-boot Linux.

BTW, when following a guide, maybe follow it exactly, get that working, then try doing something different.

I’ll try that then.
I already installed Gnome. How do I uninstall it?

Re: I need help running the Windows Subsystem for Linux

Will this do?

sudo apt-get remove ubuntu-gnome-desktop
sudo apt-get remove gnome-shell

… I think it did.

Last edited by javierdl; March 7th, 2021 at 03:37 AM.

Re: I need help running the Windows Subsystem for Linux

LOL, it worked with LXDE!
I cannot say it’s a pretty distro, but it works!

Re: I need help running the Windows Subsystem for Linux

I don’t think I have access to the internet though

Also, I cannot run Software. It says:
«Sorry, something went wrong: Failed to connect to system D-Bus: Could not connect: No such file or directory«

Advanced Network Configuration in menu://applications/Preferences won’t run.

This is what I got when running «ifconfig» to check the network connectivity:

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 1500
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0xfe<compat,link,site,host>
loop (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wifi0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.38 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::7d47:8a6d:593f:fc28 prefixlen 64 scopeid 0xfd<compat,link,site,host>
ether 94:e7:0b:51:8a:d8 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I haven’t touched the Firewall, maybe that’s the problem. I just don’t know exactly which apps to let through nor how exactly.

Last edited by javierdl; March 7th, 2021 at 05:30 PM.

Re: I need help running the Windows Subsystem for Linux

This is the summary of the steps I followed before:

Start by clicking Start and entering «turn windows». The Turn Windows Features on or off item should be displayed. Then scroll down to Windows Subsystem for Linux.

Restart Windows.

Open the Windows Store, search for Linux, and install Ubuntu.

Once complete, click Launch from within the Windows Store or open it from the Start menu.
On the first run, you’ll be prompted to input a username and password to create a user account.

Run these commands
sudo apt update
sudo apt upgrade

While this upgrade is running, head to Sourceforge to download and install the VcXsrv Windows X Server utility.

Install the Linux desktop. Many Linux desktop environments are available but to keep things simple we’ll install LXDE:
sudo apt install lxde

Following installation of LXDE, input these commands:

export DISPLAY=:0
export LIBGL_ALWAYS_INDIRECT=1

Open the Xlaunch tool, and choose One large window, and Display number: 0

Click Next on the following pages until the end.

Start the LXDE desktop environment
startlxde

Steps to start Ubuntu / LXDE every time.

Open Ubuntu

Enter these commands:
export DISPLAY=:0
export LIBGL_ALWAYS_INDIRECT=1

Open the Xlaunch tool, and choose One large window, and Display number: 0
Click Next on the following pages until the end.

Start the LXDE desktop environment
startlxde

Note that it is not possible to damage Windows 10 using the Linux environment. Any commands you input will damage only the Windows Subsystem for Linux and the chosen operating system. Windows 10 will remain safe and secure.

Sources

How to Get the Linux Bash Shell on Windows 10

How to Run a Linux Desktop Using the Windows Subsystem for Linux

5 Linux Distros You Can Install in Windows Subsystem for Linux

Last edited by javierdl; March 8th, 2021 at 03:03 PM.

Источник

Arch Linux

#1 2020-02-14 12:29:38

[Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#2 2020-02-14 12:49:21

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#3 2020-02-14 12:54:22

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#4 2020-02-14 13:01:36

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#5 2020-02-14 13:07:50

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#6 2020-02-14 13:09:50

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#7 2020-02-14 13:13:52

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#8 2020-02-14 13:23:40

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#9 2020-02-14 13:27:57

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#10 2020-02-14 13:28:14

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#11 2020-02-14 13:31:29

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#12 2020-02-14 13:41:48

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

#13 2020-02-14 14:17:28

Re: [Solved] starx doesn’t work — xf86OpenConsole: Cannot open virtual

On WSL, startx gets fatal server error: x86OpenConsole: Switching VT failed #3946

Thread: Startx wont work

Thread Tools

Display

Startx wont work

Re: Startx wont work

Re: Startx wont work

Re: Startx wont work

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> angryelizar

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> symon.2014

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> angryelizar

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> symon.2014

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> angryelizar

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> symon.2014

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> angryelizar

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> symon.2014

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> angryelizar

[solved] raspberry and vc4

[solved] raspberry and vc4

Re: raspberry and vc4

Re: raspberry and vc4

Re: raspberry and vc4

Re: raspberry and vc4

Re: raspberry and vc4

Re: raspberry and vc4

Re: raspberry and vc4

Re: raspberry and vc4

Re: raspberry and vc4

Who is online

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://ubuntuforums.org/images/icons/icon5.png" alt="Question" /> I need help running the Windows Subsystem for Linux

Re: I need help running the Windows Subsystem for Linux

Re: I need help running the Windows Subsystem for Linux

Re: I need help running the Windows Subsystem for Linux

Re: I need help running the Windows Subsystem for Linux

Re: I need help running the Windows Subsystem for Linux

Re: I need help running the Windows Subsystem for Linux

Re: I need help running the Windows Subsystem for Linux

Re: I need help running the Windows Subsystem for Linux

Читайте также:

angryelizar

symon.2014

angryelizar

symon.2014

angryelizar

symon.2014

angryelizar

symon.2014

angryelizar

I need help running the Windows Subsystem for Linux