Problem with configuring X.org

T-Aoki said:
There's one exception.

If using nvidia GPU without any of graphics/nvidia-drm-[510|515|61|66]-kmod, /etc/X11/xorg.conf (or /usr/local/etc/X11/xorg.conf.d/20-nvidia.conf in example 3 of Chapter 5.4.3 in the handbook, which anyway does not exist by default) is needed as xorg doesn't know how to configure it and attempts to use non-existent (on FreeBSD) nouveau driver, thus, fail.

This always applies for legacy drivers (470 series and older), as graphics/nvidia-drm-[510|515|61|66]-kmod does not support legacy branches of drivers.
Click to expand...
And this is why I stick with AMD GPUs.
 
Colleagues, this is strange, but I downloaded the images of the GhostBSD (both simple and XFCE) and installed them in the same machine.
With the same old cable HDMI. With the same large, but old monitor, who does not support the EDID.
In both cases, X.org earned at the installer phase and works great to the present. Maybe they are practicing the magic of voodoo there?
 
ogogon said:
With the same old cable HDMI. With the same large, but old monitor, who does not support the EDID.
Click to expand...
This would be the problem. Auto-configuration for screens on X11 uses EDID to work. Without it, manual confiuration as noted on Chapter 5.4 of the handbook (especially 5.4.4) would be mandatory.

I've never tried GhostBSD, but aren't there any question about the spec (or vendor and model) and interface (VGA, DisplayPort, HDMI,...) of your monitor? If so, GhostBSD would have generated required configuration file and installed it with its installer.
 
T-Aoki said:
This would be the problem. Auto-configuration for screens on X11 uses EDID to work. Without it, manual confiuration as noted on Chapter 5.4 of the handbook (especially 5.4.4) would be mandatory.
Click to expand...
Before booting GhostBSD I thought so too.

T-Aoki said:
I've never tried GhostBSD, but aren't there any question about the spec (or vendor and model) and interface (VGA, DisplayPort, HDMI,...) of your monitor? If so, GhostBSD would have generated required configuration file and installed it with its installer.
Click to expand...
Not at all. There was not a single question.
At first, a certain image was loaded into a RAM disk a very long time, even tediously. Then, obviously, they started from it.
I immediately saw a desktop, very good in resolution and color for this equipment, and on it an icon - "Install to disk".

I can find fault with many things - /usr/ports behaves very strangely, wg-quick does not work fully, their installer logic is poorly thought out.
BUT THEY KNOW HOW TO SET UP A X.ORG, DAMN IT!
 
ogogon said:
Before booting GhostBSD I thought so too.


Not at all. There was not a single question.
At first, a certain image was loaded into a RAM disk a very long time, even tediously. Then, obviously, they started from it.
I immediately saw a desktop, very good in resolution and color for this equipment, and on it an icon - "Install to disk".

I can find fault with many things - /usr/ports behaves very strangely, wg-quick does not work fully, their installer logic is poorly thought out.
BUT THEY KNOW HOW TO SET UP A X.ORG, DAMN IT!
Click to expand...
Does it running on anything ACCELELRATED drivers?
If I'm forced to build GUI installer on FreeBSD, I'll go thrhough the safest side. Assuming install-to-RAMDISK first,

  1. Check for boot method. (UEFI or Legacy BIOS)
  2. Somehow detect or decide resolution and depth. (If UEFI, detect current resolution and color depth [not 100% sure, but would be possible]. If BIOS, assuming not-too-old hardwares, fall back to XGA [1024*768] 16bit color.)
  3. Install non-accelerated driver (scfb for UEFI and vesa for BIOS) but not accelerated ones at all.
  4. Start X.
And let the admin installing and configuring accelerated driver like drm-*-kmod, nvidia-driver or xf86-video-intel and so on.
Possibly talented developers would try to detect hardware accelerators and monitors with EDID and automatically install and configure them, and if whichever (including EDID info!!!!!) are missing, keep safe state as-is.
 
You must log in or register to reply here.
Back
Top