Forum › Forums › Official Releases › antiX-21/22 “Grup Yorum” › x.org fatal server error / no screens found / vesa ?
- This topic has 8 replies, 3 voices, and was last updated Jan 2-2:31 pm by hamster.
-
AuthorPosts
-
December 26, 2021 at 2:48 pm #73710Member
hamster
Good day and Merry Christmas to all of you,
Using a persistant live-usb stick on various computers, I got this error message today when I was trying to boot with my Lenovo X230 into Antix-Live
The funny thing is that work well when I tried the same, using my IMAC (using failsave option).What could cause the following problem? I never had issues before, worked well yesterday and now it won’t boot. I attached a copy of my .local/share/xorg/Xorg.0.log output.
Thanks for your help folks!
Cheers- This topic was modified 1 year, 4 months ago by hamster.
Attachments:
December 26, 2021 at 8:42 pm #73733Member
Xecure
::My guess is that it saved the vesa driver configuration when selecting “safe video mode” or “fail-safe” in the Apple hardware, and now has trouble booting again with the original Lenovo laptop.
When you get again to the command prompt, log in as your normal user in the terminal, and run
sudo rm /etc/X11/xorg.conf
which removes the previous xorg configuration set by failsafe. You can then restart the login manager and see if works again.
sudo service slimski restartIf that doesn’t work, reboot. And if it still fails, then we will explore forcing the correct graphic driver. You would use the xorg boot parameter.
xorg=intel
for intel integrated driver, or a different driver like nouveau for Nvidia, or amdgpu for AMD.antiX Live system enthusiast.
General Live Boot Parameters for antiX.December 27, 2021 at 1:49 pm #73829Memberhamster
::Thank you for your kind support. Deleting the xorg.conf file did not help. The failsafe option is still in somewhere and overrides the current setting. However, xorg=intel in the boot option helps, however, this is workaround is somewhat aukward as one must pay pretty close attention on which device you’re booting up your stick. If you boot your stick on a UEFI device, you don’t get the boot option displayed and one must go thru a “menu” to chose failsafe. If you do that, you end up in boot-dead-loop as intel is still pre-set and it tries to use intel AND failsafe which won’t work of course.
Cheers
PatrickDecember 27, 2021 at 3:08 pm #73834Moderator
caprea
::Please can you look if on the live usb anything relevant is blacklisted in /etc/modprobe.d/
or /usr/lib/modprobe.d/ ?Also might in /usr/lib/modprobe.d/no-mode-set.conf something was added.
December 28, 2021 at 7:09 am #73936Memberhamster
::Hi Caprea,
I checked, but could not find anything fancy in there. I also checked the no-mode-set.conf file, but did not find anything suspicious.
Don’t know where this setting “failsafe” was written/carved to.
Thank you. Happy New Year!
PatrickAttachments:
December 28, 2021 at 8:07 am #73938Moderator
caprea
::What’s in the live-blacklist.conf ?
The “options radeon modeset=0” can get deleted to restore the stick to its original state.
December 29, 2021 at 7:40 am #74018Memberhamster
::Hi Caprea,
See below the content of the live-blacklist.conf. No fancy stuff in there as far as I can judge.
I also deleted (# hashed) the “options radeon modeset=0” entry but that did not bring any changes.
I guess I have to live with it. It is not that much of a deal breaker after all. I am simply curious what could cause this.
Anyhow, I appreciate your help.
CheersAttachments:
December 29, 2021 at 9:31 pm #74068Moderator
caprea
::You can delete the file live-blacklist.conf
It blacklists a lot of video drivers included the intel i915, which is possibly used by your laptop
January 2, 2022 at 2:31 pm #74447Memberhamster
::Hi Caprea,=0
Happy New Year. Thanks for your advice. Unfortunately, deleting the live-blacklist.conf file did not help neither. It’s OK, I just type in the xorg=intel command at boot promt and that works fine.
Cheers
Patrick -
AuthorPosts
- You must be logged in to reply to this topic.

