fbdev and vesa for hyper-v

[IL Ka]

Hello.

I run Linux as Hyper-V guest.

It seems that there is no DRI/DRM driver for Hyper-V videocard, but there
is Framebuffer driver for it.

So, I enabled framebuffer driver and my idea was to run XOrg using fbdev
driver on top of it.
But there is no such driver in modern Linux distros.

Question #1) Is it true that fbdev is deprecated and removed in favour of
DRM/DRI?
Can I still compile it by my self? Is it worth doing in my case?

My second idea was to run plain old VESA driver.
But vesa driver found that my kernel has driver for videocard and refused
to work:
" Ignoring device with a bound kernel "

Question #2)  Can I "force" vesa to run with hyperv_fb enabled?
If no, why?
Is it becase vesa does not know "state" of video card when it is under
control of hyperv_fb?

I think I can have 2 records in my loader: one for "command line mode"
(that runs kernel with video=hyperv_fb) and another for "video mode" that
runs kernel without of it, and starts xdm.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: fbdev and vesa for hyper-v

[IL Ka]

Hello Adam,

Could have fooled me. I see fbdev driver builds in current versions of
> Arch, Debian, Fedora, Gentoo, and openSUSE. What distro are you using
> that lacks it?
>

Slackware:) I see xf86-video-fbdev in "extras" folder, but it is i586
version.
And there is no x64 version.

After reading your answer I decided to read docs, and here is the reason:
https://mirrors.slackware.com/slackware/slackware-14.2/source/x/x11/package-blacklist
"We don't want this one, as it causes failure of X with no xorg.conf"

I was not right about "modern linux": it is only Slackware-specific issue,
I am sorry.

Thank you.
Ilya.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: fbdev and vesa for hyper-v

[IL Ka]

PS: I just build fbdev from /extras/sources on slackware dvd and it seems
to work now.

[20.515] (**) FBDEV(0): claimed PCI slot 0@0:8:0
[20.515] (II) FBDEV(0): using default device
[20.515] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[20.515] (==) FBDEV(0): RGB weight 888
[20.515] (==) FBDEV(0): Default visual is TrueColor
[20.515] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[20.515] (II) FBDEV(0): hardware: hyperv_fb (video memory: 8192kB)





On Mon, Feb 25, 2019 at 8:06 PM Adam Jackson  wrote:

> On Mon, 2019-02-25 at 18:33 +0300, IL Ka wrote:
>
> > I run Linux as Hyper-V guest.
> >
> > It seems that there is no DRI/DRM driver for Hyper-V videocard, but
> > there is Framebuffer driver for it.
> >
> > So, I enabled framebuffer driver and my idea was to run XOrg using
> > fbdev driver on top of it.
> > But there is no such driver in modern Linux distros.
>
> Could have fooled me. I see fbdev driver builds in current versions of
> Arch, Debian, Fedora, Gentoo, and openSUSE. What distro are you using
> that lacks it?
>
> > Question #1) Is it true that fbdev is deprecated and removed in
> > favour of DRM/DRI?
>
> Generally people would prefer that new video drivers use the drm driver
> infrastructure and not fbdev. In that sense fbdev is "deprecated", but
> not "removed", it's still there and works as well as it ever did.
>
> > Can I still compile it by my self? Is it worth doing in my case?
>
> You can, but again, I bet your distro has it built already.
>
> - ajax
>
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Error

[IL Ka]

Hello.
Any errors in /var/log/Xorg.0.log ?

On Thu, Sep 12, 2019 at 11:25 AM sujan mlr  wrote:

> Hello,
>
> I am getting following error after the patching and reboot of the machine.
> Patched form Oracle Linux 7.6 to 7.7, Now GUI is not coming ssh to the
> machine works fine.
>
> Error:
>
>
>
>
>
>
>
>
>
> *(EE)Fatal server error:(EE) failed to create screen
> resources(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.*
>
> Please help me in tackling this issue.
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: X Window System map review

[IL Ka]

Hello.

1. Window manager is a separate client. Word processor and Web browser do
not use it directly. They talk to XOrg an XOrg consults Window manager (if
any) asking it to draw window. Technically, you can run client even without
of Window manager.

2. Drivers may be in Kernel or in Xorg itself. With modern installations
you almost always have drivers inside of kernel, but Xorg can work with
kernels that know nothing about your video (except it is VGA
compatibility).

3. There is also session manager (
https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html), but it is
fully optional

Everything else look correct IMHO..

On Thu, Sep 12, 2019 at 4:40 PM Kenny Armstrong  wrote:

> Hello all.  I am writing a lesson for the Linux Professional Institute on
> a basic X Window System setup.  Part of that lesson includes a simple
> diagram of an X installation.  I have pieced this together from the X.org
> documentation and a video of a talk by James Gettys.  Nonetheless, I wish
> to make sure that what I have is not misrepresenting the structure of an X
> installation.  I know that there is more to an X setup than what I have
> depicted here, but I want to make sure that what is in the image is at
> least correct.
>
> Thanks in advance for any help on the matter!
>
> - Kenny Armstrong
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Debian 10.3: X does not start

[IL Ka]

In most cases there is no need to run "-configure" since X can autodetect
many things using defaults provided by distro.
Have you tried official debian wiki (it is about amdgpu, not general
modesetting)
https://wiki.debian.org/AtiHowTo  ?

I think that "/dev/dri/card0: No such file or directory"  means there is no
kernel driver (no module compiled or not loaded by udev)
Do you run custom kernel? Have you tried to load module manually using
(modprobe)?


On Wed, Mar 25, 2020 at 9:00 PM Klaus Jantzen 
wrote:

> Hello,
>
> I installed Debian on a PC with AMD Ryzen 5 3400 G.
>
> My first trials ended with a message
>
> "Cannot run in framebuffer mode ..." from xorg.
>
> Due to some research in the net I am using the following xorg.conf.
> It is basically what I got when I did a "X -configure".
> ==
> Section "ServerLayout"
>  Identifier "X.org Configured"
>  Screen  0  "Screen0" 0 0
>  Screen  1  "Screen1" RightOf "Screen0"
>  InputDevice"Mouse0" "CorePointer"
>  InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
>
> Section "Files"
>  ModulePath   "/usr/lib/xorg/modules"
>  FontPath "/usr/share/fonts/X11/misc"
>  # FontPath "/usr/share/fonts/X11/cyrillic"
>  FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
>  FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
>  FontPath "/usr/share/fonts/X11/Type1"
>  FontPath "/usr/share/fonts/X11/100dpi"
>  FontPath "/usr/share/fonts/X11/75dpi"
>  FontPath "built-ins"
> EndSection
>
> Section "Module"
>  Load  "glx"
> EndSection
>
> Section "InputDevice"
>  Identifier  "Keyboard0"
>  Driver  "kbd"
> EndSection
>
> Section "InputDevice"
>  Identifier  "Mouse0"
>  Driver  "mouse"
>  Option"Protocol" "auto"
>  Option"Device" "/dev/input/mice"
>  Option"ZAxisMapping" "4 5 6 7"
> EndSection
>
> Section "Monitor"
>  Identifier   "Monitor0"
>  VendorName   "Monitor Vendor"
>  ModelName"Monitor Model"
> EndSection
>
> Section "Monitor"
>  Identifier   "Monitor1"
>  VendorName   "Monitor Vendor"
>  ModelName"Monitor Model"
> EndSection
>
> Section "Device"
>  ### Available Driver options are:-
>  ### Values: : integer, : float, : "True"/"False",
>  ### : "String", : " Hz/kHz/MHz",
>  ### : "%"
>  ### [arg]: arg optional
>  #Option "Accel"  # []
>  #Option "SWcursor"   # []
>  #Option "EnablePageFlip" # []
>  #Option "SubPixelOrder"  # []
>  #Option "ZaphodHeads"# 
>  #Option "AccelMethod"# 
>  #Option "DRI3"   # []
>  #Option "DRI"# 
>  #Option "ShadowPrimary"  # []
>  #Option "TearFree"   # []
>  #Option "DeleteUnusedDP12Displays" # []
>  #Option "VariableRefresh"# []
>  Identifier  "Card0"
>  # Driver  "amdgpu"
>  Driver  "modesetting"
>  BusID   "PCI:9:0:0"
> EndSection
>
> Section "Device"
>  ### Available Driver options are:-
>  ### Values: : integer, : float, : "True"/"False",
>  ### : "String", : " Hz/kHz/MHz",
>  ### : "%"
>  ### [arg]: arg optional
>  #Option "Accel"  # []
>  #Option "SWcursor"   # []
>  #Option "EnablePageFlip" # []
>  #Option "SubPixelOrder"  # []
>  #Option "ZaphodHeads"# 
>  #Option "AccelMethod"# 
>  #Option "DRI3"   # []
>  #Option "DRI"# 
>  #Option "ShadowPrimary"  # []
>  #Option "TearFree"   # []
>  #Option "DeleteUnusedDP12Displays" # []
>  #Option "VariableRefresh"# []
>  Identifier  "Card1"
>  # Driver  "amdgpu"
>  Driver  "modesetting"
>  BusID   "PCI:9:0:1"
> EndSection
>
> Section "Screen"
>  Identifier "Screen0"
>  Device "Card0"
>  Monitor"Monitor0"
>  SubSection "Display"
>  Viewport   0 0
>  Depth 1
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 4
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 8
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 15
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 16
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 24
>  EndSubSection
> EndSection
>
> Section "Screen"
>  Identifier "Screen1"
>  Device "Card1"
>  Monitor"Monit

force separate screens for intel with xrandr

[IL Ka]

Hello,

I use intel driver for laptop with two outputs: LVDS and HDMI.
Both monitors are merged to one big screen, but I want them to use separate
screens, so I can use DISPLAY=:0.1.

I was trying to declare separate screens, but it doesn't work: I see two
screens in my log, but X still has one screen that includes both monitors.

If it were xinerama, then it would be possible to disable it and have two
screens, but it seems that xrandr can't be disabled.

I also tried to declare two separate devices binding them to outputs using
Option "Monitor-.." or Screen.
Former doesn't effect number of screens while latter (Screen 1) simply
leads to black screen.

Does it mean intel (with DRI/KMS) doesn't support it?
Is it possible to have two separate screens with my configuration?
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: force separate screens for intel with xrandr

[IL Ka]

PS: I was able to separate them with "ZaphodHeads", but Zaphod is for
multiseats, and I do not want to have different keyboards and mice.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: force separate screens for intel with xrandr [SOLVED]

[IL Ka]

I now answering my own question:)

ZaphodHeads is exactly what I was looking for.
I created 2 devices with Screen and ZaphodHeads, and it know works


Section "Monitor"
Identifier  "External"
  Option "PreferredMode" "1920x1200"
Option  "RightOf"   "Onboard"
EndSection


Section "Device"
Identifier  "intelExt"
Driver  "intel"
BusID   "PCI:0:2:0"
Option "ZaphodHeads" "HDMI1"
Screen 1
EndSection

Section "Device"
Identifier  "intelOnb"
Driver  "intel"
BusID   "PCI:0:2:0"
   Option "ZaphodHeads" "LVDS1"
Screen 0
EndSection


Section "Screen"
Identifier "Onboard"
Monitor "Onboard"
Device "intelOnb"
SubSection "Display"
EndSubsection
EndSection

Section "Screen"
Identifier "External"
Monitor "External"
Device "intelExt"
SubSection "Display"
Modes "1920x1200"
EndSubsection
EndSection

Section "ServerLayout"
Identifier "DefaultLayout"
Screen 0 "Onboard"
Screen 1 "External"
EndSection
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: no screens found(EE) - Cannot use AMD R5 M330 as output to monitor

[IL Ka]

Here is what happened:

> [   347.043] (WW) RADEON(0): No outputs definitely connected, trying again...
> [   347.043] (WW) RADEON(0): Unable to find connected outputs - setting 
> 1024x768 initial framebuffer
> [   347.043] (II) RADEON(0): mem size init: gart size :7fbcf000 vram size: 
> s:8000 visible:fbbe000
>
>
It seems that you have 2 video cards: intel (built into CPU I believe) and
ATI.
Intel is connected, not ATI.

I think you need to enable ATI video card in your BIOS settings.
There should be something like "discrete video card" or "on board video
card" switch.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

xdm-config for :0 doesn't call Xstartup?

[IL Ka]

Hello.

I found that xdm-config has the following lines
DisplayManager*startup: /usr/lib64/X11/xdm/Xstartup
DisplayManager._0.startup: /usr/lib64/X11/xdm/GiveConsole

As I understand, that means GiveConsole is run instead of Xstartup,
so sessreg is not called, and I do not see my login in "w" output.

I am sure this is how it worked for decades, so it could be that I
misunderstand something.

Is it a bug?

Ilya.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: xdm-config for :0 doesn't call Xstartup?

[IL Ka]

Hello.
>xdm runs Xstartup on behalf of the user.
Hmm.. man page says: "After the user logs in, xdm runs the Xstartup script
as root.".
There is a $USER argument passed to this script, but the script itself runs
as root.

>. What does your Xstartup say?

exec /usr/bin/sessreg  -a -w /var/log/wtmp -u /var/run/utmp -x
/usr/lib64/X11/xdm/Xservers -l $DISPLAY -h "" $USER

I am pretty sure the problem is the following line in xdm-config:

DisplayManager*startup: /usr/lib64/X11/xdm/Xstartup
! The following three resources set up display :0 as the console.
DisplayManager._0.startup: /usr/lib64/X11/xdm/GiveConsole

GiveConsole is:
chown $USER /dev/console

So, sessreg is simply not called when xdm serves screen :0

I was able to fix it by copying sessreg line to the GiveConsole, but it
looks like a strange hack..
Ilya






On Sun, Oct 18, 2020 at 5:35 PM Chris Sorenson  wrote:

> xdm runs Xstartup on behalf of the user. Or, at least it's supposed to.
> Xstartup should then call sessreg which should invoke wtmp and utmp.
> However, it's possible to bypass wtmp/utmp by passing "-w none" to
> sessreg, in which case "w" won't show the login. What does your Xstartup
> say?
>
>
> On 10/18/2020 07:00 AM, xorg-requ...@lists.x.org wrote:
> >
>
> >
> > Message: 1
> > Date: Sun, 18 Oct 2020 00:12:22 +0300
> > From: IL Ka 
> > To: xorg 
> > Subject: xdm-config for :0 doesn't call Xstartup?
> > Message-ID:
> >rm33zezeml9qkenphvkazh+upn+tdb7sbjjkl9qv8je...@mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hello.
> >
> > I found that xdm-config has the following lines
> > DisplayManager*startup: /usr/lib64/X11/xdm/Xstartup
> > DisplayManager._0.startup: /usr/lib64/X11/xdm/GiveConsole
> >
> > As I understand, that means GiveConsole is run instead of Xstartup,
> > so sessreg is not called, and I do not see my login in "w" output.
> >
> > I am sure this is how it worked for decades, so it could be that I
> > misunderstand something.
> >
> > Is it a bug?
> >
> > Ilya.
> >
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: xdm-config for :0 doesn't call Xstartup?

[IL Ka]

This is my private laptop, and "w" works when I add sessreg to the
GiveConsole.

As far as I understand, the problem is resource "startup" overridden for
display 0, because of concrete value that has more precedence than wildcard.

DisplayManager*startup: /usr/lib64/X11/xdm/Xstartup
DisplayManager._0.startup:  /usr/lib64/X11/xdm/GiveConsole

I wrote a small tool to check my guess.

#include 
#include 

int main(int argc, char* argv[])
{
char *type;
XrmValue display0, display1;
XrmDatabase xrdb = XrmGetFileDatabase("/etc/X11/xdm/xdm-config");
XrmGetResource(xrdb, "DisplayManager._0.startup", "*", &type,
&display0);
XrmGetResource(xrdb, "DisplayManager._1.startup", "*", &type,
&display1);
printf("0: %s\n1: %s\n", display0.addr, display1.addr);
XrmDestroyDatabase(xrdb);
return 0;
}

It's output is:
0: /usr/lib64/X11/xdm/GiveConsole
1: /usr/lib64/X11/xdm/Xstartup

So, for the _0 we have only GiveConsole, and it doesn't have anything about
sessreg.
https://github.com/freedesktop/xdm/blob/master/config/GiveConsole

Ilya.


On Mon, Oct 19, 2020 at 7:40 AM Chris Sorenson  wrote:

> Those snippets from your scripts look correct, is your sessreg set to
> executable?
>
> Does anyone else have access to your system?
>
> Might it have been hacked to prevent programs like "w," "who," or
> "lastlog" from showing that someone's ghosted in for nefarious purposes?
>
> >
> > On 10/18/2020 05:11 PM, IL Ka wrote:
> >
> > >
> > > On Sun, Oct 18, 2020 at 5:35 PM Chris Sorenson  wrote:
> > >
> >
> > Hello.
> >
> > >
> > > xdm runs Xstartup on behalf of the user.
> > >
> >
> > Hmm.. man page says: "After the user logs in, xdm runs the Xstartup
> > script
> > as root.".
> >
> > There is a $USER argument passed to this script, but the script itself
> > runs
> > as root.
> >
> > >
> > > What does your Xstartup say?
> > >
> >
> > exec /usr/bin/sessreg  -a -w /var/log/wtmp -u /var/run/utmp -x
> > /usr/lib64/X11/xdm/Xservers -l $DISPLAY -h "" $USER
> >
> > I am pretty sure the problem is the following line in xdm-config:
> >
> > DisplayManager*startup: /usr/lib64/X11/xdm/Xstartup
> > ! The following three resources set up display :0 as the console.
> > DisplayManager._0.startup: /usr/lib64/X11/xdm/GiveConsole
> >
> > GiveConsole is:
> > chown $USER /dev/console
> >
> > So, sessreg is simply not called when xdm serves screen :0
> >
> > I was able to fix it by copying sessreg line to the GiveConsole, but it
> > looks like a strange hack..
> > Ilya
> >
>
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: How to make a custom xkb layout/variant mapping permanent in an xorg session?

[IL Ka]

Hi.
I believe xsession could be used:
https://wiki.debian.org/Xsession

On Fri, Feb 5, 2021 at 12:09 PM aprekates  wrote:

> OS: Debian GNU/Linux 10 (buster) x86_64
> Kernel: 4.19.0-13-amd64
> DE: KDE
> Display: x11
> server: X.Org 1.20.4
>
> I managed to create a custom xkb mapping using a home directory which
> contains a xkb keymap description (my-map-usgr-workman) and a symbols
> file and feeding those in xkbcomp:
>
> ~/.config/xkb$ tree
> .
> ├── my-map-usgr-workman
> ├── symbols
> │   ├── ergogr
>
> $ xkbcomp -I$HOME/.config/xkb my-map-usgr-workman  $DISPLAY
>
> My question is : What is the way to make those changes permanent during
> a reboot?.
>
>
> --
>
> Some related guides i have found regarding on ways to create a new xkb
> layout or variant and how to enable those changes (two tasks that go
> together usually).
>
> - a couple of sites proposing the local folder way of enabling a new layout
>
>   https://www.vinc17.net/unix/xkb.en.html
>   https://a3nm.net/blog/xkbcomp.html
>   https://www.choam.eu/altgr-intl/
>
> - a guide proposing to change xkb conf files directly in the system
>
>
> https://michal.kosmulski.org/computing/articles/custom-keyboard-layouts-xkb.html
>
> - a site that suggest to uphold the 11th commandment was "thou shalt not
> edit things in /usr/share"
>
> https://www.choam.eu/altgr-intl/ 
>
> Alexandros
>
>
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: problem opening/loading an X11 font.

[IL Ka]

>
> xterm: cannot load font
> '-b&h-lucidatypewriter-medium-r-normal-sans-11-80-100-100-m-70-iso10646-1'
>
Hi.
What does ``xfontsel`` show?
Have you tried to provide a font explicitly with ``xterm -fn``?

You can also try xft/fontconfig fonts (they are rendered on the client, not
server) and much smoother in most cases.
See "-fa" option in xterm and "fc-match" tool

By the way: there is a free X11 server for Windows called "xming", you do
not need cygwin
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: problem opening/loading an X11 font.

[IL Ka]

>
>
> '-b&h-lucidatypewriter-medium-r-normal-sans-0-0-100-100-m-0-iso10646-1'
> Warning: Cannot convert string
> "-b&h-lucidatypewriter-medium-r-normal-sans-0-0-100-100-m-0-iso10646-1"
> to type FontStruct
> Warning: Missing charsets in String to FontSet conversion
> Missing charset ISO8859-1 for fallback fontset
> Warning: Unable to load any usable fontset
> xterm: cannot load font
> "-b&h-lucidatypewriter-medium-r-normal-sans-0-0-100-100-m-0-iso10646-1"
>

Lets try not to provide particular charset and DPI

$ xterm -fn '-*-lucidatypewriter-*-*-*-*-*-*-*-*-*-*-*-*'

Does it work?

Try to reinstall font packages on your cygwin:

https://cygwin.com/packages/summary/xorg-x11-fonts-src.html

>
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: No screen, no prompt

[IL Ka]

>
>
> Does anyone have any idea what to do to get that root prompt back?
>
> Hi.
Debian list is a better place for this question.

Reboot, click "tab", and when you see GRUB menu, choose the "recovery"
entry.

Or in the same menu click "e" to open the boot menu editor.
Find linux command (it should be linux
/boot/vmlinuz-some-verison blah-bla-bla quiet), and append
"systemd.unit=multi-user.target" to the list of arguments.
Click F10 to boot.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: No screen, no prompt

[IL Ka]

I do not have experience with R128 driver, unfortunately.

> [32.360] (II) R128(0): initializing int10
> [32.361] (EE) R128(0): V_BIOS address 0x35d70 out of range

I believe that means the card can't emulate the old Video BIOS interface.
It shouldn't prevent it from working

> [32.362] (WW) R128(0): DDC2/I2C is not properly initialized
> [32.362] (WW) R128(0): DDC2/I2C is not properly initialized
> [32.362] (II) R128(0): EDID for output VGA-0
> [32.363] (II) R128(0): Output VGA-0 disconnected
> [32.363] (WW) R128(0): No outputs definitely connected, trying
again...

Card can't read EDID from your monitor, hence it doesn't "see" it.

This must be the problem. Let's wait for someone who has experience with
R128. You can also try another monitor and VGA cable.
It could be that DDC is broken in this cable.

> [33.769] (EE) [drm] drmOpen failed.
> [33.769] (EE) R128(0): [dri] DRIScreenInit failed.  Disabling DRI.
DRM also failed, not sure why.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: No screen, no prompt (R128 driver blackscreen)

[IL Ka]

So, you have 2 video outputs:

One is R128:
> [32.185] (WW) R128(0): DDC2/I2C is not properly initialized
> [32.185] (WW) R128(0): DDC2/I2C is not properly initialized
> [32.185] (II) R128(0): EDID for output VGA-0

It doesn't see any monitor.

Another is modeset (kernel) based driver for i965 (built-in video card)
>[33.240] (II) modeset(G0): [DRI2]   DRI driver: i965
> [   33.240] (II) modeset(G0): [DRI2]   VDPAU driver: i965

There is a monitor there
> [33.005] (II) modeset(G0): EDID for output VGA-1-1
> [33.005] (II) modeset(G0): Manufacturer: DEL  Model: a00b  Serial#:
860631884
> [33.005] (II) modeset(G0): Year: 2004  Week: 41

Just a random idea: disable (via BIOS setup) built-in card and disconnect
monitor from it
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Find a good config guide

[IL Ka]

Hi.
Not sure about a step-by-step guide, but I suggest reading classic old
books series "Definitive Guides to the X Window System" (aka "colour
books")
Especially "X Windows System Administrator's Guide" and "X Windows System
User Guide".
They are pretty old but really helped me with understand the generic
XWindows configuration process (what is server, how client finds it, what
is display manager and window manager, what is resource etc)

https://www.amazon.com/Windows-System-Administrators-Definitive-Guides/dp/0937175838

https://www.amazon.com/Window-System-Users-Definitive-Guides/dp/0937175145