2007-03-03 11:35
|
xorg.conf (616 bytes) |
|
|
After doing a new and clean install (this time with rhgb), the graphics stay garbled, also when firstboot comes into action. Solution: reboot into runlevel 3. Copy the formentioned xorg.conf file from the similar server onto the computer and reboot. Rhgb works perfectly, unfortunately, firstboot doesn't kick into action after reboot. |
|
|
On request of Johnny Hughes, I also checked this problem with a clean install of RHEL5 beta 2. Here too the above mentioned problems occur. Installation (without vga=773 added) went fine, also firstboot went without any problem. Rebooting (because I switched SELinux off) caused the graphics during the splash-screen to become garbled and stay like that. CTRL+F1 - F8 doesn't respond. Cold reboot + xorg.conf file from twin-server did the trick. Adding vga=773 has as result that without rhgb, I don't see any lines (including the [OK]). Attached file is the RHEL5 generated xorg.conf |
|
2007-03-04 19:03
|
rhel5-org.conf (597 bytes) |
|
2007-03-04 19:04
|
patrickmoelands-xorg-working.conf (2,828 bytes) |
 |
This must be specific to your hardware / graphics combination. Does it still happen with the latest QA tree? |
|
|
Yes, the latest tree also causes the problem. |
 |
Does this also happen in final? |
|
|
Yes, even in CentOS 5.0 (final) the problem is still there. [edited/extra info] Additional, I have the problem also on my own pc (P4 motherboard with a GeForce2 Pro videocard). Here too, the xorg.conf file is extremely basic (no module section, no monitor info, no videocard info). |
|
|
Hmmm never saw that dring m installs. Moving from 5.0 beta to 5.0 |
|
|
I've worked out the problem. Two problems which seem related. During installation, the monitor isn't detected/configured properly (specific entries are missing from the new xorg.conf file). As a result of this, no usable info is present and the graphical login gets garbled. Furthermore, there are more specifications missing (the complete "Module" section is gone). This won't help after configurating a graphical card. Workaround is simple, read here: http://www.linuxforums.org/forum/redhat-fedora-linux-help/92715-centos-5-0-installation-woes-tips-tricks.html This problem has been tested on several independant systems (P3 + ATI, P3 + I810 and P4 + NVIDIA) and symptoms + cure is always the same. |
|
|
But that only happens *IF* your monitor isn't detected properly. If it is, you get a usable Xorg.conf afterwards. Keep in mind that Xorg7.1 works with a much smaller set of information in Xorg.conf, as most things are autodetected nowadays. The Modules section normally isn't needed anymore, for example. |
|
|
The Modules section is needed to get the Nvidia (legacy) driver working. Without it, no GLX extensions (to name something). |
|
|
Yes, but the ncidia driver install script will configure that part of your xorg.conf. |
|
|
Sure ... that is why I need to manually add those lines AFTER I install the Nvidia driver. Perhaps the newest non-legacy does, but the legacy driver doesn't. |
|
|
Yes, but should we care about closed drivers? Because with the recognized nv driver, the GLX module won't do anything for you. And other cards do work without that. [ralph@logout ~]$ xdpyinfo | grep "number of extensions" number of extensions: 31 [ralph@logout ~]$ grep -i modul /etc/X11/xorg.conf [ralph@logout ~]$ glxinfo | grep rendering direct rendering: Yes |
|
|
Getting any kind of monitor properly configured should be the main focus point. Using CentOS 4.x without problems, switching to CentOS 5.0 and having these kind of problems will make people leave. I tested CentOS 5.0 tonight on a P2 laptop, did a clean install and restarted it. NO graphicsl screen, just ending up with runlevel 3. Startx gave me errors! And that when CentOS 4.4 never gave any problem. Doing a system-config-display solved it. |
|
|
I have been trying to update my CentOS 4 kickstart files to CentOS 5 and found that no matter what I use as options to the "monitor" keyword, there is no "Monitor" section created in /etc/X11/xorg.conf for a monitor that does not respond to autodetection. Since this behavior seems to be independent of the video card chipset ( I get it on NVidia TNT Model 64 ) I'm also wondering if the category this bug is assigned to is appropriate. |
|
|
Can anyone test that on RHEL5? And then open a bug upstream if that also happens there, as we're not going to change the X sources ... |
|
|
Maybe related to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234401 |
|
|
I have opened this bug with RedHat as https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239827 |
|
|
Just for the record, this problem still exsists. |
 |
Patrick, have you already been able to test this with the 5.1 tree ? |
|
|
Yes I have. This problem also occurs when installing CentOS 5.1 (and RHEL5.1 and Fedora 8). Solution is the same. |
 |
The URL in note 5011 does not exist. Has this been deleted? |
|
|
URL has indeed changed. New one: http://www.linuxforums.org/forum/redhat-fedora-linux-help/95675-centos-5-0-rhel5-fedora-7-installation-problems-tips-tricks.html |
 |
can you explain in details the problems you have ? And don't mix it with the vga= kernel parameter bug that is an other and well known (and now fixed) issue : http://bugs.centos.org/view.php?id=1809 |
|
|
Again, the problem and the workaround: 1) Do a clean installation and reboot. 2) If you run firstboot, nothing goes wrong (graphical screen display fine), reboot again. 3) Graphical login is a complete mess. 4) Switch off and boot again, this time use Grub to go to runlevel 3. 5) Run system-config-display and select proper hardware and resolution. 6) Go to runlevel 5 and there are no problems. |
|
|
This is almost 2-yr old and we are at CentOS 5.3 (and will soon be 5.4). Does the problem still exist? |
|
|
With RHEL5.3, CentOS 5.3 and Scientific Linux 5.3 this problem remains. Last year I got it filmed using my mobile phone, the movie of the boot sequence (including the graphical problems) can be seen here: http://www.youtube.com/watch?v=qrIRvIUzbtY (the system was running Scientific Linux, but the result with CentOS is the same). Perhaps good to know is that the people of Fedora nowadays solved this problem simply by adding another option to the grub menu of the installation dvd called "install system with basic video driver" (this option has the following extra boot parameter added: "xdriver=vesa"). |
|
2009-10-18 18:46
|
screenshot-with-c53-xorg.png (108,913 bytes) |
|
|
Additional information after testing CentOS 5.4. When you install on a laptop with an Intel GMA X3100 Gfx chipset, you get a display where things are out of line (like resolutions of 1024x768 on a screen of 1280x800). See the attached image of the desktop (http://bugs.centos.org/file_download.php?file_id=771&type=bug). It appears that this is a problem related to the system thinking there is an external display connected where it isn't. More info can be found here: https://bugzilla.novell.com/show_bug.cgi?id=343858 http://ubuntuforums.org/showthread.php?t=610407 Fortunately, the solution here (too) is that you need to adapt your xorg.conf file. Add the following lines to solve the problem: - - - - - - - - - - - - Section "Device" Identifier "Videocard0" Driver "intel" Option "monitor-TV" "TVOutput" <=== this one!!! EndSection Section "Monitor" <=== this one!!! Identifier "TVOutput" <=== this one!!! Option "Ignore" "true" <=== this one!!! EndSection <=== this one!!! - - - - - - - - - - - - |
 |
closed due to inactivity. Please re-open if the problem exists with new versions. |
- Anonymous
