I have my computer upgraded to suse11.3 (64bit) and at the same time I use a new screen with a resolution of 1920x1080. However the desktop always comes up with 1280x1024. Output of xrand -q:
linux:~ # xrandr -q
Screen 0: minimum 1280 x 1024, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 77.0*
manual entry of xrand -s gives:
linux:~ # xrandr -s 1920x1080
Size 1920x1080 not found in available modes
Video card is XGI Volari Z7_Z9_Z9S
I have read probably all of the posts re display settings, have created an xorg.conf file:
Section “Monitor”
Identifier “default”
Option “Preferred Mode” “1920x1080”
EndSection
No Joy so far. Any ideas are appreciated.
Thanks
Uli
Unfortunately, the minimal xorg.conf approach (with preferred mode entry) will only work on its own if xrandr reports the desired display mode. A lot has to do with your graphics card and associated driver being used. It might help if you also provide
It looks like Xorg tries to load the preferred ‘xgi’ driver, but its not available, so the ‘vesa’ driver is used instead, with only limited capability and resolutions possible.
now I have mucked around with the driver and with other xorg video drivers and now it does not boot into runlevel 5 any more. Says module vesa, fbdev and xig are not found. Any possibility to get at least the old settings back from commandline? Otherwise I have to reinstall everything again.
uli
now I have mucked around with the driver and with other xorg video drivers and now it does not boot into runlevel 5 any more…
It depends what you have done - you need to elaborate. Did you delete any xorg packages? (xorg-x11-driver-video for example) Did you edit any xorg configuration files (in /etc/x11/xorg.conf, or /etc/X11/xorg.d/ directory)?
Can you boot up into a graphical environment via failsafe mode?
Failsafe mode does not boot into graphical either. I installed xorg-x11-driver-video from the Suse packet search and 1-click install function. First the process froze and then the message came up that Yast does not respond and whether the application should be terminated. So I terminated it and tried again. This time it went through but from then on it did not start into the gui. So I went from the command line into YAST and uninstalled the driver again - no change. Didn’t go into /etc/X11 at all. I don’t know whether a previous generic driver was overwritten and the interrupted install process is the cause or not.
after reinstalling xorg-x11-driver-video this are the last 30 lines in Xorg.0.log:
479.565] (II) Initializing built-in extension XKEYBOARD
479.565] (II) Initializing built-in extension XC-MISC
479.565] (II) Initializing built-in extension SECURITY
479.565] (II) Initializing built-in extension XINERAMA
479.565] (II) Initializing built-in extension XFIXES
479.565] (II) Initializing built-in extension RENDER
479.565] (II) Initializing built-in extension RANDR
479.565] (II) Initializing built-in extension COMPOSITE
479.565] (II) Initializing built-in extension DAMAGE
479.577] (II) AIGLX: Screen 0 is not DRI2 capable
479.577] (II) AIGLX: Screen 0 is not DRI capable
479.580] (II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so
479.580] (II) GLX: Initialized DRISWRAST GL provider for screen 0
479.580] [dix] Could not init font path element /usr/share/fonts/misc:unscaled, removing from list!
479.580] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list!
479.580] [dix] Could not init font path element /usr/share/fonts/100dpi:unscaled, removing from list!
479.580] [dix] Could not init font path element /usr/share/fonts/75dpi:unscaled, removing from list!
479.580] [dix] Could not init font path element /usr/share/fonts/URW/, removing from list!
479.580] [dix] Could not init font path element /usr/share/fonts/cyrillic:unscaled, removing from list!
479.580] [dix] Could not init font path element /usr/share/fonts/truetype/, removing from list!
479.580] [dix] Could not init font path element built-ins, removing from list!
479.580]
Fatal server error:
479.580] could not open default font ‘fixed’
479.580]
Please consult the The X.Org Foundation support
at X.Org Wiki - Home
for help.
479.581] Please also check the log file at “/var/log/Xorg.0.log” for additional information.
479.581]
BTW, the Xorg.0.log originally pasted before the most recent issues, shows that “fbdev” was the driver in use, and that is the most basic/limited catch all driver. The “vesa” driver was subsequently unloaded.
BTW, the Xorg.0.log originally pasted before the most recent issues, shows that “fbdev” was the driver in use, and that is the most basic/limited catch all driver. The “vesa” driver was subsequently unloaded.
Thanks consused, you’re correct. I only took a fleeting look at the log (very busy with work at the moment), but essentially my comments about the driver in use still stand.
Please feel free to chip in further if you can assist with the OP’s predicament.
Ok, but my reading is similar to yours i.e. OBS repo enabled by 1-click, infiltration of incompatible xorg-x11 package release, and/or missing dependencies after YaST failed. Package and repo info urgently needed. Followed by possible delete/disable repo, and re-install original xorg-x11 package(s). Sort out screen settings, but as you said, available resolutions will be limited (by fbdev).
Thanks deano_ferrari and consused for your efforts. Because of those problems I was a bit careless with the partition change (in this forum too). Then the computer did not boot any more. As I need the computer I spend 4 hours today reinstalling and configuring printer/scanner, nfs configuration to file server, Internet, mail, etc.
I forgot about the command zypper ve must be old age…
The repositories added were the xorg repositories - that was all.
However in case I have too much time and try to play around again I did a
rpm -qa |grep xorg-x11 > /home/uli/xorgfiles.txt for further reference what worked.
Thanks again
Uli
