After installation, xorg.conf is missing. I am unable to create it with Sax2, as the /usr/X11R6/bin/ (and lib and lib64) directories are empty. This happens with both KDE and LXDE installs on 11.4 x64.
I see that Sax2 is deprecated, however auto-detection is not working. Under 11.3 I created dummy devices in order to get VNC working as a guest within Citrix XenServer.
On 03/25/2011 04:13 PM, Rick DeBay wrote:
>
> xorg.conf is missing. I am unable to create it with Sax2
xorg.conf was been depreciated Linux wide, in favor of ‘automatic’
configuration
Sax2 was dropped as openSUSE 11.2 (or maybe .1) was released, because
it was hopelessly broken (or something like that) and when the
community asked hackers to step up and fix/support it no one did…
lots said about that which google can find…
so, the question is: what is not working that you wanted to fix the
old (pre 11.2/.1) way?
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
I am installing as a guest under Citrix XenServer. Auto detection does not work, as there is no graphic console. With 11.3 I created a dummy device within xorg.conf, and that allowed VNC to work.
GREAT!!
i especially liked this part: “One feature that is also a little bit
important is to make it distribution independent to make it easy for
other distributions to use it, improve it and contribute back, so we
will make a world better place for all of us.”
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
On 03/25/2011 05:36 PM, Rick DeBay wrote:
>
> I am installing as a guest under Citrix XenServer. Auto detection does
> not work, as there is no graphic console. With 11.3 I created a dummy
> device within xorg.conf, and that allowed VNC to work.
if you happen to have a nice backup that old xorg.conf, i think if
you put it in 11.4 (where it was in your previous version) it will
“just work” (on the same hardware)…
hmmmm…you might want to delete everything except that dummy device…
NOTE: there is a good chance i do NOT know what i’m talking about
<read my caveat below please>…there are however several post in
these fora about how to force the system to build a xorg.conf, which
(i understand) will be read if found by the system and override the
‘automatic’ configuration magic…
if those don’t help maybe a real guru will happen along who can point
you to the right place…or you might try some other version of this
search string http://tinyurl.com/624e2vy
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
Unfortunately that is rather a waste of time, because hardly any of the forum volunteers are developers, and developers don’t typically come to the forum.
Auto-detection is now either done by the kernel (KMS) or by the xorg-xserver system. If you think this an openSUSE issue, use openFATE (see Wiki), and look for a request for a Sax2 replacement. To know which graphic drivers support KMS, please see the 11.4 Release Notes (e.g. via YaST). That may leave you with the xorg-xserver approach. For that, I have just provided some advice and help in your latest new thread before coming here, so it may not take account of comments here.
I pieced this together out of configuration files found on the internet (since neither Xorg -configure nor Sax2 could give me a default file to edit), and my previous experience getting 11.2 to work. This gives me a VNC desktop, although from the logs the X-server doesn’t look too happy during initialization.
This is the relevant guidance, copied from the other thread so all the relevant detail is here:
Alternatively you could add a dummy screen device as appropriate to the config file(s) in /etc/X11/xorg.conf.d/
50-monitor.conf similar statements to the Monitor section of xorg.conf: configures the hardware of a monitor
50-device.conf similar Driver statements to the Device section of xorg.conf: configures the graphic chip/card’s driver
50-screen.conf similar Device and Monitor statements to the Screen section of xorg.conf: defines the monitor and graphics chip/card combination.
For individual statements, you can refer to “man” pages for xorg.conf, and for a particular named graphics driver.
Don’t change the default “Identifier” statements and references to them in xorg.conf.d as they link. You won’t need every statement. Just add these lines:
Driver “dummy” Add this to file 50-device.conf
Modeline “1024x768” 53.08 1024 1056 1256 1288 768 784 791 807 Add this to file 50-monitor.conf
*Add following lines to file 50-screen.conf immediately after the line: Identifier “Default Screen” *
SubSection “Display”
Depth 24
Modes “default”
EndSubSection
Although I haven’t tried this “dummy” config before, you shouldn’t need any more lines than those. Give it a try and let us know what happens.
@Rick_DeBay: My last post was a hint towards manual configuration (ie add the required ‘dummy’ interface entries by a direct edit). As consused mentioned, edit the configuration files in /etc/X11/xorg.conf.d/ as an alternative to the leagcy /etc/X11/xorg.conf file (with its different sections). Using relevant fragments from older versions is a good approach for those systems where automatic detection is problematic. As Carlos mentioned, get the problem reported by way of a bug report, if you want this ‘auto-detection’ to work in a later release.
On 03/29/2011 07:36 PM, Rick DeBay wrote:
>
> I pieced this together out of configuration files found on the internet
> (since neither Xorg -configure nor Sax2 could give me a default file to
> edit), and my previous experience getting 11.2 to work. This gives me a
> VNC desktop, although from the logs the X-server doesn’t look too happy
> during initialization.