Ctrl-Alt-F1 = Black,blank screen?
Oct. 31st, 2015 12:15 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
oio11You probably don't have a getty process running on tty1 (the first console). Check your /etc/inittab to see if getty is started on that console in runlevel 5.
http://www.linuxquestions.org/questions/linux-general-1/ctrl-alt-f1-%3D-black-blank-screen-385376/
Virtual terminals not working? Check your keyboard.
(This is a boring post that I’m writing for people that have this same problem in the future. Just skip it.)
Every good Linux user knows that if you want to drop from X down into a text-based virtual terminal, you can press control-alt-F1 (or any other key up to F6), and control-alt-F7 returns you to the graphical mode. But what if that doesn’t work? In my case, it turned out to be my keyboard. My Microsoft Natural Ergonomic Keyboard 4000 has a key marked “F Lock” and unless that FLock key is activated (the “F” LED should be on), the wrong keystrokes were being sent to my Linux Ubuntu version of Intrepid Ibex. How can you debug this? Well, it took me a while.
After some Googling, here’s how I’d write the flowchart:
– Try running “chvt 1” to switch your console to virtual terminal 1.
– If “chvt 1” does not work, you might get the message “Couldnt get a file descriptor referring to the console”. You probably need to be superroot. Once you run as root, that command should work.
– Maybe “chvt 1” fails in some other way. Dude, you’re outside my area of expertise. You could try typing “sudo modprobe vga16fb; sudo modprobe fbcon” . Or you could try typing the command “setupcon” to set up the font and keyboard on the Linux console. Or it’s possible that you need to edit /boot/grub/menu.lst and tweak the vga= setting or remove the “splash” parameter. Or you might want to check your /etc/gdm/gdm.conf file.
– Quick check: you might have the “DontVTSwitch” option set in your /etc/X11/xorg.conf file, which would disable virtual terminal switching.
– If running “chvt 1” as superroot does work, then you probably have an issue with your keyboard mappings somehow.
– If you have a Microsoft Natural Ergonomic Keyboard 4000, make sure that the “F-Lock” key near the top-right of the main part of the keyboard is properly engaged. The “F” LED below the keyboard should be on.
– Next, run xev (possibly as root) to see raw xevents as you press keys. This thread helped, where the person said
Recently I tried to switch to VT (console) and I couldn’t – Ctrl+Alt+F1 didn’t work (and they used to couple of weeks ago). I don’t even know where to look for the problem; xev detects KeyRelease XF86_Switch_VT_1 event, /etc/inittab contain getty respawns.
When I ran xev myself, and pressed control-alt-F1, I saw an event like
KeyPress event, serial 38, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 1848943, (42,37), root:(1751,59),
state 0x0, keycode 146 (keysym 0xff6a, Help), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
The fact that I saw a “Help” event rather than “XF86_Switch_VT_1” was what made me suspicious. Sure enough, activating the “F-Lock” key then triggered this event:
KeyRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x1a6, subw 0x3400002, time 2873229, (38,51), root:(1747,73),
state 0xc, keycode 67 (keysym 0x1008fe01, XF86_Switch_VT_1), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
and life was good. You might also consider tweaking xmodmap to return the values you expect. Or you might have a strange XkbModel or XkbLayout setting where switching your keyboard language or layout (e.g. from pc105 to pc104) might help.
https://www.mattcutts.com/blog/virtual-terminal-not-working/
no subject
Date: 2015-10-31 03:46 am (UTC)nvidia - Xorg does not see my monitor EDID - Ask Ubuntu
Xorg.0
.. o monitor specified for screen "Default Screen Section".
Using a default monitor configuration. ..
http://askubuntu.com/questions/218871/xorg-does-not-see-my-monitor-edid
no subject
Date: 2015-10-31 03:59 am (UTC)Ох уж эти иксы
Довольно часто бывает, что после окончания начальной загрузки вы лицезреете чёрный экран. Что случилось? Возможно, слетел видеодрайвер. Разумеется, для не искушённого пользователя лучше воспользоваться драйверами из репозиториев. Для того, чтобы войти в ваш любимый Gnome или KDE для запуска менеджера пакетов, нажмите Ctrl-Alt-F1, и вы попадёте в терминал. Зайдите с правами рута, и заставьте ваш Xorg заюзать VESA драйвера: команда dpkg-reconfigure xserver-xorg для дебиана/убунту, yast2 для SUSE, а там выбираете VESA-совместимую видеокарту. Или nano /etc/X11/xorg.conf, ищете там слово intel, nvidia и подобное в секции Driver и меняете на vesa. Далее запускаем иксы: kdm или gdm или startxfce4 и т.д. (по вкусу). Если экран и дальше чёрный, прибиваете иксы с помощью Ctrl-Alt-Backspace и смотрите, где кошка зарыта: cat /var/log/Xorg.0.log | grep EE и гуглите текст ошибки.
Сеть
Для начала поговорим о беспроводной сети. Проверьте наличие сети с помощью команды ifconfig. Естественно, ваша точка доступа должна быть включена и настроена. Если в выводе команды отсутствует интерфейс, названный ath0 или wlan0, то нужно что-то делать. Есть такие замечательные драйвера, как madwifi. Инструкцию по установке можно найти там же. Если они не помогли, вам возможно поможет такая утилита, как NDISwrapper. Этот костыль позволит использовать виндовые драйвера для адаптеров беспроводной сети в линуксе.
sudo ndiswrapper -i /path/to/driver.inf
Потом загрузите модуль ndiswrapper: sudo modprobe -v ndiswrapper
Далее попробуем поднять сеть:
sudo ifconfig wlan0 up
sudo iwlist wlan0 scan
Если на первую команду система ругается вроде «Interface Doesn't Support Scanning», то вы неверно выбрали название интерфейса, или не тот драйвер. Вторая команда запустит поиск беспроводной сети.
Теперь о проводной сети. Допустим, что патчкорд вставлен в сетевую карту, и соответствующий интерфейс присутствует в выводе ifconfig'a. Далее будем говорить о случае получения интернета с помощью NAT по витой паре. Проверим наличие инета дедовским способом: ping %sitename%. Если система ругается вроде network is unreachable, то попробуем ещё так: ping %ip_of_site% — звоните вашему другу и просите сказать айпишник гугла ;) Если теперь пинг проходит, значит у вас не выставлен адрес DNS сервера. Делаете nano /etc/resolv.conf и пишете там строку вида nameserver %IP_of_dns_server%.
http://habrahabr.ru/post/55232/
no subject
Date: 2015-10-31 04:07 am (UTC)Some settings are only accessible through editing xorg.conf by hand.
How can I edit my xorg config file?
Open a terminal (or console) as root, then run :
# editor /etc/X11/xorg.conf
What if I do not have an xorg config file?
If xorg.conf is missing for some reason, Xorg will probe your hardware on every startup. Though this works fine in most cases, some settings remain inaccessible. To create a starting point for customization, do the following.
Switch to a console as root (not a terminal emulator in X), then run:
# /etc/init.d/gdm stop && /etc/init.d/gdm3 stop && /etc/init.d/kdm stop && /etc/init.d/xdm stop
$ cd /etc/X11/
# Xorg -configure
Alternatively, reboot the machine in single user mode, then run:
$ cd /etc/X11/
# Xorg -configure
Follow the on-screen instructions. This should give you something to work with.
Question: what should be done if generating this file fails, giving the message, 'Number of created screens does not match the number of detected devices'?
Anyway, probably, this is unnecessary. Per this comment and this advice, it seems best to create the directory /etc/X11/xorg.conf.d and place in it a few files in order to tweak sections of the implicit xorg.conf, as for example is done here.
Xorg reads vendor configuration information from the directory /usr/share/X11/xorg.conf.d, as stated by man xorg.conf.d.
Rather than in xorg.conf, another quite useful way to adjust X settings is on the fly, in a desktop environment's list of scripts to run at startup.
https://wiki.debian.org/Xorg
no subject
Date: 2015-10-31 04:55 am (UTC)Compton is a good way to get total tear-free output in lightweight de's that don't have opengl compositing. its a lightweight compositor that has an opengl backend that is capable of vsync on intel: https://github.com/chjj/compton. I wrote a guide on using it here: http://ubuntuforums.org/showthread.php?t=2144468
Another option is the intel "TearFree" xorg option, but afiak this only works properly on recent kernel/drivers (this option requires SNA to work and I'm not sure if it will work with debian's rather old stock 3.2 kernel, and I've never tried it on debian), and the performance is rather atrocious which is why I prefer usng an opengl compositor: create a file "/usr/share/X11/xorg.conf.d/20-intel.conf" and add
Code: Select all
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
Option "TearFree" "true"
EndSection
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
by Nyromith » 2013-05-20 10:10
http://crunchbang.org/forums/viewtopic. ... %23p248917
http://www.webupd8.org/2012/10/xfce-syn ... -xfwm.html
http://lists.debian.org/debian-user/200 ... 01097.html
It goes like this:
1. Download and install this:
http://packages.siduction.org/xfcenext/ ... _amd64.deb
2. Download and install this:
http://packages.siduction.org/xfcenext/ ... _amd64.deb
3. Download and force-install this:
https://launchpad.net/~nilarimogard/+ar ... _amd64.deb
4. Edit this file: /var/lib/dpkg/status
On the dependency list remove this dependency: libwnck22 (>= 1:2.22)
5. Relog and run this command:
xfconf-query -c xfwm4 -p "/general/sync_to_vblank" -s true
That's it! Now I have a tear-free XFCE environment with only the bare minimum of required packages. It fixes window tearing, video tearing and almost fixes graphical tearing, although there is one tear line near the top of the screen.
I'll see if there are some bugs, and write here if something stops working.
Hope I won't get into the Debian prison for this kind of solution
http://forums.debian.net/viewtopic.php?t=104149