Xf86closeconsole kdsetmode failed input output error

Не генерируется Xorg.conf

Логи смотреть не пробовали? (/var/log/Xorg. ) может там простая ошибка.

Посмотрел, ошибки есть:

Your xorg.conf file is /home/user/xorg.conf.new

собственно файл-то есть?

Your xorg.conf file is /home/user/xorg.conf.new

ls -l показывает что есть, с такими правами: -rw-r—r—

Ну так поздравляю — вот твой конфиг, положи его куда надо и пользуйся

Ну так поздравляю — вот твой конфиг, положи его куда надо и пользуйся

Спасибо, буду пытаться дальше.

Какая видеокарта? Какой драйвер? lspci | grep VGA давай

Источник

Arch Linux

You are not logged in.

#1 2015-10-20 04:29:36

Xorg error after update

I updated system but Xorg is not working.
Also, I can’t use GNOME.

This is pacman update log

And following is Xorg log.

I can’t find out why xorg makes errors like
[514445.690] (II) UnloadModule: «evdev»
[514445.690] (II) systemd-logind: releasing fd for 13:72
[514445.693] (EE) systemd-logind: failed to release device: Connection was disconnected before a reply was received

What should I do to fix this problem?

#2 2015-10-20 09:30:46

Re: Xorg error after update

514445.690 — 514183.251 = 262.439

Why this more than 4 minutes delay between these two events?

Could you describe what is attached to your machine: screens, input devices, .

#3 2015-10-20 09:56:32

Re: Xorg error after update

514445.690 — 514183.251 = 262.439

Why this more than 4 minutes delay between these two events?

Could you describe what is attached to your machine: screens, input devices, .

Two monitors are connected to NVIDIA GPU, one usb mouse, one usb keyboard, and one USB hub.
The keyboard is connected through the USB hub.

#4 2015-10-20 14:44:38

Re: Xorg error after update

OK you answered the second question.
What about the first one?

#5 2015-10-21 04:53:42

Re: Xorg error after update

I found that the logs before [514183.251] was generated before update because gnome-session was restarted.
Between [514183.251] and [514445.690], I updated and rebooted the system.
The logs after [514445.690] was generated during reboot process.

I tried to restart gdm and now gnome works.
However, log in time is long.
I’m looking for solutions now.

#6 2015-10-21 09:37:39

Re: Xorg error after update

When you say ‘I rebooted the system’, are you just speaking of logout/login?
Because on my machine ‘/var/log/Xorg.0.log’ is recreated at each reboot, and the previous log is kept in ‘/var/log/Xorg.0.log.old’.
The time-stamp is reset and shows the number of seconds since the reboot time, ie the end of the systemd hook of initcpio ramfs:

in Xorg log, the time-stamp is:

10:46:51 + 29.293s = 10:47:20

Your time-stamp is pretty high, comparing with mine.
But I don’t use Gnome, maybe it’s related.

‘login time is long’: in systemd journal, you could see where a delay comes from; at what point time is consumed.
You could post the output of ‘journalctl -b’ of a long login time.

Источник

Arch Linux

You are not logged in.

#1 2014-01-14 18:06:45

[SOLVED] Xorg keeps crashing after update

Xorg crashes randomly since the last upgrade (xorg-server 1.15.0-5, xf86-video-intel 2.99.907-1 ).

Configuration file, /etc/xorg.conf.d/20-intel.conf:

(but the same happens without the configuration file.)

Anyone having this problem?

SOLVED: many days without crashes after changing «AccelMethod» to «uxa», see post #8.

Last edited by pie86 (2014-01-18 11:04:48)

#2 2014-01-15 09:54:43

Re: [SOLVED] Xorg keeps crashing after update

I’m also having troubles with the upgrade to 1.15 and 2.99.907 respectively although the stacktrace looks very different:

After searching for a while I found this bug reports: https://bugs.freedesktop.org/show_bug.cgi?id=73224 and https://bugs.archlinux.org/task/38335?opened=4955 . Although the traces are not identical it was the only relevant thing I managed to locate. However they discuss that X 1.15.. does not work with xf86-video-intel-2.21.15, but is supposed to work with 2.99. Well — not for me I had to downgrade back to X 1.14 and xf86-video-intel 2.21. I hope this helps you to somehow fix your problem

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

• Темы без ответов
• Активные темы
• Поиск
• Статус форума

Решено: Не стартует X (Причина ясна, как исправить?)

Решено: Не стартует X

Сообщение wi: » 17.11.2007 15:09

Комментировал по каждой строчке — работает, только если убрать все это.

P.S.:
Driver «nvidia».
compiz, естественно, стартовать перестал, а жаль.

Re: Решено: Не стартует X

Сообщение Juliette » 17.11.2007 15:32

Re: Решено: Не стартует X

Сообщение korisk » 17.11.2007 15:33

Есть предположение, что вы пересобрали ядро
изменив значения в разделе Direct Rendering Manager.

А за подробностями, наверное, в
cat /var/log/Xorg.0.log

Re: Решено: Не стартует X

Сообщение wi: » 18.11.2007 21:11

На тот момент, уверен (хотя, давно это было), не пересобирал.

Re: Решено: Не стартует X

Сообщение Portnov » 18.11.2007 21:41

Re: Решено: Не стартует X

Сообщение wi: » 18.11.2007 22:50

Re: Решено: Не стартует X

Сообщение wi: » 18.11.2007 22:55

Источник

Xf86closeconsole kdsetmode failed input output error

This problem is because I tried to get steam play to work and broke native steam games in the process. When I tried to fix the later Gnome Desktop Manager won’t work.
https://steamcommunity.com/app/221410/discussions/0/1741094390461378203/

um I broke the computer it won’t start GNOME. I think it is because of this line:

system info from hardid:
Computer-
Processor : AMD FX(tm)-6300 Six-Core Processor
Memory : 16324MB (6013MB used)
Machine Type : Desktop
Operating System : Ubuntu 18.04.1 LTS
User Name : jessica (Jessica)
Date/Time : Wed 12 Sep 2018 09:08:08 AM EDT
-Display-
Resolution : 1920×1080 pixels
OpenGL Renderer : AMD PITCAIRN (DRM 2.50.0, 4.15.0-34-generic, LLVM 6.0.0)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel — HDA ATI SB
Audio Adapter : HDA-Intel — HDA ATI HDMI
-Input Devices-
Power Button
Power Button
AT Translated Set 2 keyboard
Logitech Performance MX
Eee PC WMI hotkeys
HDA ATI HDMI HDMI/DP,pcm:3
HDA ATI HDMI HDMI/DP,pcm:7
HDA ATI HDMI HDMI/DP,pcm:8
HDA ATI HDMI HDMI/DP,pcm:9
HDA ATI HDMI HDMI/DP,pcm:10
HDA ATI HDMI HDMI/DP,pcm:11
HDA ATI SB Front Mic
HDA ATI SB Rear Mic
HDA ATI SB Line
HDA ATI SB Line Out
HDA ATI SB Front Headphone
-Printers-
No printers found
-SCSI Disks-
Optiarc DVD RW AD-7260S
ATA WDC WD10EZEX-00K
ATA Hitachi HDS72105
ATA INTEL SSDSC2BW12
Generic USB Storage-CFC
Generic USB Storage-SDC
Generic USB Storage-SMC
Generic USB Storage-MSC

right, the issue with games. have you fixed issues with games?
what you need is to look at your OS as a whole, not just a tool to run games.

I have noticed from your older thread that your steam still uses obsolete path on .local/share/. when you will install latest ubuntu make sure your’re installing steam from repos and its new folder is under

there’s no magic pill to fix your games. you have OS that have to be up to date or even have to use latest video drivers to comply with Steam Play requirements. What you should try to achieve is not «fixing games» but looking for information how to properly install latest video drivers for your GPU and how to properly install steam.
step by step.
once you have your latest video driver up and running for native steam games then you can try to approach Steam Play games. if anything will fail to work check that game in winehq for workarounds or check Steam Play community created lists for reports on that game.

I strongly suggest to look for assistance with GPU drivers on specialized ubuntu resourses, because it have nothing to do with steam or Steam Play, it’s core OS changes that have to be made with a great caution.

UPD
next time when you look for forums please check post date. you used an obsolete command from 2008 here
https://ubuntuforums.org/archive/index.php/t-882267.html
this module is already obsolete so there’s no wonder you’re getting issues with such changes. look for information for your specific distro, 1-2 years old max.

that would be your first real lesson for using commands from forums to «fix» something. I’m not sure why you had to kick your OS core to mske Steam Play working as it does not require any core changes to your OS.
what I would suggest, first anf foremost, stop applying «fixes» from forums if you do not understand the meaning of change and risks of such change.
secondly, backup your games, data and do fresh install of Ubuntu. install steam from ubuntu repos, install proper video drivers.
then about Steam Play. this tool is just like wine, if your game have issues with wine it will have same issues with Steam Play. all changes applied to your OS regarding wine or Steam Play should not touch your OS core. google for every command you’ve got as a suggestion to try. learn what it does and what are risks! don’t follow suggestions blindly

Steam play and native steam had different issues. 🙁
I wasn’t doing anything right now to fix «Steam Play» or anything with Wine. I was just trying to get native steam and steam game binaries to work.

I’ll make sure to back up often.

To be fair whether it is my stupidity or not there seems to be a lot of ways I have found to destroy my graphics, while switching drivers like I did this week.

right, the issue with games. have you fixed issues with games?
what you need is to look at your OS as a whole, not just a tool to run games.

I have noticed from your older thread that your steam still uses obsolete path on .local/share/. when you will install latest ubuntu make sure your’re installing steam from repos and its new folder is under

there’s no magic pill to fix your games. you have OS that have to be up to date or even have to use latest video drivers to comply with Steam Play requirements. What you should try to achieve is not «fixing games» but looking for information how to properly install latest video drivers for your GPU and how to properly install steam.
step by step.
once you have your latest video driver up and running for native steam games then you can try to approach Steam Play games. if anything will fail to work check that game in winehq for workarounds or check Steam Play community created lists for reports on that game.

I strongly suggest to look for assistance with GPU drivers on specialized ubuntu resourses, because it have nothing to do with steam or Steam Play, it’s core OS changes that have to be made with a great caution.

Источник

I have installed Gnome 3.16 on my Ubuntu 15.04 (previously updated from 14.04) via:

sudo add-apt-repository ppa:gnome3-team/gnome3
sudo add-apt-repository ppa:gnome3-team/gnome3-staging
sudo apt-get install gnome

However, I am unable to log into the Gnome desktop:

• If I select gdm as my default desktop manager, my system boots to a black screen only showing the cursor. I can switch into tty, but no other X component loads.
• If I leave lightdm selected, I am able to log in to Unity, but if I choose either Gnome or Gnome Classic I get a black screen for a couple of seconds after typing my password, then I’m back at the login screen. Gnome Flashback (both Compiz and Metacity options) works, but they are obviously not what I’m interested in using.

I’ve tried different suggestions from similar, but older, questions, including:

• Removing any nvidia-* packages
• Removing my .Xauthority file
• Manually stopping gdm then running startx

None of these brought any improvement. The only potentially useful log info I can find is in the rather peculiarly-named /var/log/gdm/(null)-greeter.log:

(WW) xf86CloseConsole: KDSETMODE failed: Input/output error
(WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
(EE) 
Fatal server error:
(EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
(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) 
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f13a8d92556]
(EE) 1: /usr/bin/X (0x7f13a8bdf000+0x1b7749) [0x7f13a8d96749]
(EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f13a68a5000+0x352f0) [0x7f13a68da2f0]
(EE) 3: ?? [0x7f13ab7f08c0]
(EE) 
(EE) Segmentation fault at address 0x7f13ab7f08c0
(EE) 
FatalError re-entered, aborting
(EE) Caught signal 11 (Segmentation fault). Server aborting

There is no error message in /var/log/Xorg.0.log.

Has anyone seen this before and do they have any suggestions?

Thank you.

Модератор: Модераторы разделов

#Section "Extensions"
#    Option         "Composite" "Enable"
#    Option         "Render" "Enable"
#EndSection

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

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

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

Description: Ubuntu 18.04 LTS
Release: 18.04

xorg:
  Installed: 1:7.7+19ubuntu7

First I suspended my laptop, while a few applications were running (Firefox, Chrome and some others much smaller). A couple of hours later, I opened the lid and expected the Gnome session would resume.

What happened instead was a crash of the X server, then the login page was shown again and a new Gnome session started: the old session got killed!

In the Xorg.0.log.old file I found this, not sure if related:

[ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[ 21189.338] (II) Server terminated successfully (0). Closing log file.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] È una directory: ‘/proc/driver/nvidia/gpus/0000:01:00.0’
.proc.driver.nvidia.registry: Binary: «»
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018
 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: ‘/var/log/boot.log’
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 8 23:03:30 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05cc]
 NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc]
InstallationDate: Installed on 2018-06-21 (17 days ago)
InstallationMedia: Ubuntu 18.04 LTS «Bionic Beaver» — Release amd64 (20180426)
MachineType: Dell Inc. Precision M4800
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/vg-root ro scsi_mod.scan=sync quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/02/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0T3YTY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2