Re: xinit: unable to connect to X server: Connection refused even after dpkg-reconfigure

2020-10-23 Thread Samuel Thibault
Almudena Garcia, le ven. 23 oct. 2020 21:26:18 +0200, a ecrit: > Maybe It can be solved by implementing a DRM (Direct Rendering Manager), which > can allow us to using other drivers from the kernel, like Intel driver. No, there is no need for this, it just looks like a libpciaccess issue like you

Re: xinit: unable to connect to X server: Connection refused even after dpkg-reconfigure

2020-10-23 Thread Samuel Thibault
Which version of libpciaccess0 and hurd-libs0.3 do you have? Samuel

Re: xinit: unable to connect to X server: Connection refused even after dpkg-reconfigure

2020-10-23 Thread Almudena Garcia
Yes, this problem is known. I reported this two months ago. We think that the problem is related to the PCI Arbitrer, which has not implemented the necessary calls to make Xorg work. In my case, I tested It using the VESA driver (the only currently supported in Hurd), and VESA was not able to dete

xinit: unable to connect to X server: Connection refused even after dpkg-reconfigure

2020-10-23 Thread Paul Dufresne
I have done dpkg-reconfigure x11-common xserver-xorg-legacy and have chosen to let anyoone to connect. But I fail to: startx resulting in: paul@debian:~$ startx X.Org X Server 1.20.9 X Protocol Version 11, Revision 0 Build Operating System: GNU 0.9 i686-AT386 Debian Current Operating