xorg-server-21.1.4 black screen, but xorg-server-1.17.4 works. why?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
xorg-server-21.1.4 black screen, but xorg-server-1.17.4 works. why?
Whenever I build any xorg-server past 1.17.4 I get black screen and need to reboot.
I do see that (redhat ubuntu) have been hacking vesa + vga hardware detection, "integrating systemd", wayland (EGL only not full GL) and deleted MMIO (fast vesa support deleted).
Should I expect it to work or expect that "redhat+ubu has stopped releasing Xorg that work for non-big tech bases"?
Or is 20.x series for cell phones only or something? Should I expect it to work and keep trying?
I use Nvidia 1070 on an i5 PC, know my drivers work (accelerated and vesa), card is not the newest but should be supported i think.
some depends i met I think are "current / right". i'm skipping allot but giving some highlights...
xorgproto-2022.2
xtrans-1.4.0
xcb-proto-1.14
libpthread-stubs-0.3
libxcb-1.15
xcb-util-0.4.0
libX11-1.8.1
(and many more libX and font)
libpciaccess-0.16
libffi-3.0.12
libffi-3.4.2
## 1.20+ required for mesa-22+
wayland-1.20.0
wayland-protocols-1.24
(x keyboard stuff)
libdrm-2.4.112
libxshmfence-1.3
## mesa-22.1.7 xorg-21, but 13 for xorg 1.17/18
## mesa-22 breaks older xorg, "too new"
mesa-13.0.6
dbus-1.14.0
libepoxy-1.5.10
xorg-server-1.20.14 BLACK - requires reboot
xorg-server-1.18.4 BLACK - gives console
xorg-server-1.17.4 WORKS vesa + accelerated
YOU DIDN'T COMPILE IT. It does not work "fine" when compiled.
AND I STATED I ALSO HAVE INTEL HD 630 which also does the exact same thing: works vesa, causes need of reboot for (the accelerated driver).
And there are about 123,8923,299 google hits on Xorg not working. Don't pretend to me "it always works on Suse". And if it did for them and not for others: there would be who was attacking the code?
IF YOU DIDN'T COMPILE IT YOURSELF with all ./configure requirements met: don't answer.
The TW kernel does what it needs to do. The openSUSE developers have decades of experience making kernels that work the way they are expected to work for the vast majority of hardware and users. They know very well how to compile, which is how they are able to put a kernel that works into an rpm for general use. The Intel GPU-specific i915 driver they compile and include in the kernel rpm package works much better with the various intended userspace drivers than vesa or any other generic driver can do.
"If someone has helped you, and/or you agree with a member's post: mark it as solved". Or have Suse ubu mark it as solved and IP BAN you when they disagree the post is "good for their image". That's the truth over on their side of the fence.
SPAMMER. STOP POSTING SUSE ADVERTISEMENTS.
IF YOU DIDN'T COMPILE IT YOURSELF with all ./configure requirements met: don't answer.
YOU ALSO DID NOT COMPILE THE KERNEL, which I did compile, which I am sure there are 0 Nvidia or HD 630 PCI options for. It is not a kernel issue.
What does Suse do about xorg 1.12.4 HAS MTRR ERRORs display in logs when loading VESA ?
I see ubuntu has simply deleted MTRR detection from Xorg?
Please explain to me how deleting folders from Xorg and making Wayland folder "the only folder", when wayland supports only EGL (GL 2.0).
Looks to me like they are "gutting Xorg".
And exactly where they've "gutted things" is where they stop working.
I CONSIDER I MIGHT HAVE MISSING INFORMATION WITHHELD BY UBU SUSE REDHAT about their (malware hacks).
that's why I'm fishing for answers. but not pomp.
clearly, saying "suse are professionals and you are attick poo" is not an answer to a technical question. infact I might accuse the poster of politically attacking (the forum post). SHOW ME THE CODE.
. os-support/linux/ ALLOT OF TTY HANDLING altered - on same version which goes black and requires reboot. coincidence? hard to believe since 18.4 didn't have ubu hacking and while was black: gave back the console
. 1.18.4 heavily altered lnx_init.c
(crash stays black: doesn't need reboot gets console, has "new systemd support")
. 1.18.4 CRASHES but does not require reboot: gives back VT
ERROR setting MTRR Invalid arguements (22)
+ 1.16.4, gutted some but has xwayland (1st that does)also
- 1.13.4 REMOVED xaa/ first btw, so 1.12.4 is last xaa older cards
- 1.16.4, REMOVED hw/xfree86/xaa/ req for older intel+nv video cards
. fb/fb.h:fbOddStipple is removed after 16.4 - like 2012
. REMOVED: fb/ xaa/ shadowfb/ (fb shadowfb gutted)
I have a long list of remove and altered Xorg hw/ folders in my list. I've been "charting it". The full list is too long to post. Not the least of which is that xorg now REQUIRES 3D/mesa whereas before it was optional, and that wayland is now required not optoinal.
Nvidia 1050 PCI card. Works up to 1.17.4 , black at 18.4, and after 18.4 I also have no return to console (must reboot).
I'M WELL AWARE ubuntu has "hidden formula maybe". There hacks are exactly where things stop working every time. I'm well aware "theirs works" since they also have sister hacks post-install and mystery pre-compiles that "fix certain things they break". BUT I DID NOT INTEND to make a post all about blaming ubuntu suse redhat even though they probably intently have damaged X.
THE QUESTION IS THIS: How to compile xorg-1.18.4 with proper options so I don't get a black screen. The ./configure ARGS. ARGS and or depends I might be missing. I'm hoping someone who isn't trying to post mocking and insults has an answer.
(as to kernel options: i don't think so. prove it by naming it. a PCI option that could cause an offense. i haven't seen any)
Or if "it isn't supposed to work ? perhaps the Suse poster answered that question. but for me not really. i can't confirm that it would work on my hardware. and ubu steals root password on install and IP bans people from it's forums asking questions "they don't want discussed"
if i wanted to be IP BANNED by ubuntu - i'd be on an ubuntu forum getting banned wouldn't I?
Actuall I left exactly 1 forum post in Ubuntu after installing a recent ubuntu: "you should have a free speech forum - your practice of IP BANNING should be stopped"
Post #1: I use Nvidia 1070 on an i5 PC
Post #3: AND I STATED I ALSO HAVE INTEL HD 630
Post #6: YOU ALSO DID NOT COMPILE THE KERNEL, which I did compile, which I am sure there are 0 Nvidia or HD 630 PCI options for.
Post #10: Nvidia 1050 PCI card
I get the impression the OP is trying to convince this community we are selling Free Linux operating systems or something, don't know how to compile anything. The OP is the expert here, after all, the OP appears to suggest they are compile proficient.
Does the machine run both graphics device at the same time? "Optimus"
Or is there a hardware or UEFI switch to use either one or the other graphics devices?
My older MSI laptop has a switch and only uses one at a time. I ran Gentoo for some time but gave up because it's hard on the hardware, everything compiled from scratch in Gentoo. I also designed my own kernel to make it as slim and fast as possible, and there are lots of things that need to either be enabled or disabled to get Nvidia and or Intel GPU working properly. This Guide shows a few necessary kernel requirements/options.
Between the comments in Post #6 and the information in the Gentoo guide, suggest the OP is not as smart as they make themselves out to be.
My advice:
Don't be pointing the finger at everyone else just because you don't actually know what you a babbling about. Install from pre-compiled packages if you want it to work. Or keep practicing without vocalizing your frustrations in forums.
* disable rpcauth "ezdecode" requires des. rpc allows "remote logins without end user knowing" in win10; and glibc no longer supports it (separate lib now). it had been off by default in past, for xorg and i think not even in X10.
* LIBNETTLE is malware to obstruct build, why other options are not allowed in meson build
DES module not available (and other methods newly deleted - so hack is to re-enable)
UDEV-142 i have installed but no daemon is ever active. I've also built the chain without it.
UDEV when introduced was "buggy, people complained deleting /dev/files was useless and causing hardware lockups"
Not long after (was Linus Torvalds?) introduced the /sys folder.
I set my hardware presence and data in /sys. It does the same thing but better than udev. For example it's how i know my soundcard module is present and ready and how i set /dev/files. And I'm hearing sound fine thank you.
Why ubuntu kept "forcing udev then making systemd requiring newer udev" is a wonder, since /sys was introduced TO REPLACE IT. Version bumping?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.