On 07/21/2011 01:37 AM, Felix Miata wrote:
On 2011/07/20 22:45 (GMT+0300) Stan Goodman composed:
Felix Miata wrote:
Some displays provide broken information to the driver via the EDID service. Try editing /etc/X11/xorg.conf.d/50-monitor.conf so that it reads as follows, than restart X to see if that's all that's required:
Section "Monitor" Identifier "Default Monitor" Option "PreferredMode" "1280x1024" EndSection
If it doesn't work, provide us access to the resulting /var/log/Xorg.0.log so we can look for reasons why not.
That was an adventure. After changing the file, I rebooted (CTRL-ALT-Backspace didn't restart X). The list of available monitor settings was much expanded, including one for 1280x1024x32 (labeled 31B), which I chose. This got me a warning that this is an invalid designation. That didn't surprise me, because the setting the system has been choosing for itself is given as 31A, which I was choosing previously, only to be greeted by the same rejection, and the system chose it anyway.
31a and 31b are parameters for the vga= component of the Grub kernel line that traditionally only affects the ttys, and impact X not. Since KMS was implemented in Spring last year for 11.3, vga= doesn't actually do anything for most Intel, ATI & NVidia users. Please provide the output of your executing 'cat /proc/cmdline' if you're going to continue delaying our access to Xorg.0.log. It's not necessary if you give us Xorg.0.log, because it's included there.
The only difference between 31a and 31b is color bits, 16 vs 24 or 32 IIRC, and since it applies only to ttys, no one and nothing should care between them, if it even gets used in the first place.
For most Intel, ATI & NVidia users who want to specify tty mode via Grub kernel line in openSUSE 11.3 & up, vga= needs to be replaced with video=, in Stan's case, video=1280x1024 or video=1280x1024@60 or possibly another that includes also the bits number.
For users of other than the 3 chips above, and for those 3 who require KMS be disabled for whatever reason, vga= still works for the ttys. IOW, even with Intel, vga= will work if the same Grub line also includes nomodeset or i915.modeset=0.
FWIW https://bugzilla.novell.com/show_bug.cgi?id=675793 is the bug about vga= I filed last year.
Please don't confuse what happens to, or Grub specifications for, tty video with X video. If you're not running *buntu, they aren't materially related, if related at all.
Letting the system choose its own settings again, it chose the easy way out by booting to level 3, even after I rebooted and specified "5" at the first graphic screen. In level 3, I went again to the file I had just edited, and removed the changes I had made. We are back again in level 5.
I've extracted the Xorg.0.log file that you asked for, but I haven't yet installed an ftp client on this machine, so I can't upload it for your
You don't have MC installed? It's the only FTP client I use.
inspection, and it's two large (26kB) to send to the list.
Two = 2^1, not usually anything to do with being oversize. ;-)
Golly, I committed a misspelling! And on the INTERNET, of all places!!! :-(
openSUSE list admins don't object to certain attachments, Xorg.0.log among them. Go for it.
I went for it. It is attached.
Unfortunately, the lines are not date/time-stamped, else I would know how to truncate it. If you can tell me how to define a short part that you want to see, I could send it now in a message. Else it will wait for tomorrow (?), when I may have FTP installed.
We want the whole thing. It gets written anew on each X start. It can run anywhere in size from under 10k to over 100k.
-- Stan Goodman Qiryat Tiv'on Israel