Bug 118860
Summary: | X starts but no display on ati rage mobility and dell inspiron 7500 | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thomas J. Baker <tjb> | ||||||||||||||
Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||||||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||||
Priority: | medium | ||||||||||||||||
Version: | rawhide | CC: | bostjan, frederikseyns, jdennis | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | i686 | ||||||||||||||||
OS: | Linux | ||||||||||||||||
Whiteboard: | |||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2005-10-05 22:27:57 UTC | Type: | --- | ||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
Embargoed: | |||||||||||||||||
Attachments: |
|
Description
Thomas J. Baker
2004-03-21 19:00:06 UTC
Created attachment 98740 [details]
/var/log/XFree86.0.log
Created attachment 98741 [details]
lspci -vv
a clean install of fc2t2 doesn't help. Could you please attach a copy of the file /var/log/XFree86.0.log after the failure. Also please take a peek at /var/log/messages and see if there is anything suspicious, but the most important thing is the X server log file. I'm sorry, you already attached the log file, my mistake. I got the ATI driver to work by adding vga=792 to the kernel command line. I remembered from years ago that that was a fix when I first started installing RH on Dell laptops. So it's not a perfect fix but my laptop is now more than a paper weight. According to the X server log file attached to this report, you are using a non-Red Hat custom built kernel. Please update your installation to the latest rawhide packages available so that you're running our latest testing codebase, and boot into the official Red Hat kernel. If you are able to reproduce this problem using an official Red Hat built kernel, please attach your X server log and config file, and /var/log/messages as individual uncompressed file attachments using the link below, and we will try to troubleshoot further. Thanks in advance. This system has always been running a Red Hat kernel. From the log: OS Kernel: Linux version 2.6.3-2.1.253.2.1 (bhcompile.redhat.com) (gcc version 3.3.3 20040216 (Red Hat Linux 3.3.3-2.1)) #1 Fri Mar 12 14:01:55 EST 2004 Oops, I was requesting the same info in 2 bug reports, one of which had a non-Red Hat kernel, and I must have gotten the two crossed. We still need your config file used during this problem, and the /var/log/messages file however. I'll review this again once they're attached. Thanks in advance. Just to update, I'm running current rashide from 11 May including xorg-x11-6.7.0-2 and kernel-2.6.5-1.358. If I don't have vga=792 on the kernel command line, I don't get anything displayed. I'm going to attach the config file, the error I get when I try to reconfig the display, the xorg log file, and the /var/log/messages with two boots. The first without vga=792 and the second with. Created attachment 100170 [details]
xorg.conf
Created attachment 100171 [details]
system-config-display --reconfig error
Created attachment 100172 [details]
Xorg.0.log
Created attachment 100173 [details]
/var/log/messages from two boots
I just did a diff on the xorg log files between non working and working. There are slight differences as one was started from run level 3 using startx while the other was started normally from run level 5 but the panel dimensions and write combining stuff could be where the problem lies. [root@millennium tmp]# diff Xorg.0.log /var/log/Xorg.0.log 16c16 < (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 11 21:12:48 2004 --- > (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 11 21:18:06 2004 54c54 < (--) using VT number 7 --- > (++) using VT number 7 424c424,425 < (WW) ATI(0): Inconsistent panel horizontal dimension: 1400 and 1401. --- > (WW) ATI(0): Inconsistent panel horizontal dimension: 1400 and 1399. > (WW) ATI(0): Inconsistent panel vertical dimension: 1050 and 1049. 435c436 < (==) ATI(0): Write-combining range (0xfd000000,0x800000) --- > (WW) ATI(0): Failed to set up write-combining range (0xfd000000,0x800000) 443c444 < (!!) ATI(0): Conflicting XF86Config VertRefresh specification(s) ignored. --- > (WW) ATI(0): Extraneous XF86Config VertRefresh specification(s) ignored. 655c656 < (==) ATI(0): Write-combining range (0xfd000000,0x800000) --- > (WW) ATI(0): Failed to set up write-combining range (0xfd000000,0x800000) 700c701,703 < AUDIT: Tue May 11 21:13:09 2004: 24533 X: client 5 rejected from local host --- > GetModeLine - scrn: 0 clock: 107859 > GetModeLine - hdsp: 1400 hbeg: 1448 hend: 1560 httl: 1688 > vdsp: 1050 vbeg: 1051 vend: 1054 vttl: 1066 flags: 5 [root@millennium tmp]# A Dell Inspiron 5000 with a working 1400x1050 configuration in FC1 also requires vga=792 to get anything on screen after an upgrade to FC2 (release). X starts but screen is blank otherwise. Similar "Inconsistent panel horizontal dimension" messages to above in Xorg.0.log Just wanted to say that I also have a Dell Inspiron 7500, and I was seeing the exact same problem that Thomas Baker reported here. I can confirm this bug on Fedora Core 2 final (clean install). Fortunately, his tip on passing the vga=792 option to the kernel works like a charm. This option not only allowed me to run startX, but it also allowed the Fedora Core 2 installer to run. (Without the option, a blank screen is shown when the installer switches to graphical mode, and it has to be run in text mode.) Note that Thomas's xorg.conf also works perfectly for me and allowed me to get up and running with FC2 on the Inspiron 7500. Trevor Does this problem occur with Fedora Core 3 test1 plus all Fedora development updates, using xorg-x11-6.7.99.902-8? I tried it on the first CVS release you did a couple of days ago and it didn't work. I reported the bug to Xorg bugzilla: https://freedesktop.org/bugzilla/show_bug.cgi?id=1109 but no updates to it have occured. I'll try the latest release this weekend. (I would have tried it sooner but it didn't seem like the bug was being addressed since there weren't any updates on the xorg bugzilla.) Right now, Xorg is in finalization for 6.8.0, and any bug that is not marked a blocker in bugzilla isn't being directly reviewed for 6.8.0. I've marked the bug as a candidate for blocker, however someone will review it and make a decision wether or not to accept it as a release blocker. I've added myself to CC on that bug, and we'll track the issue in the upstream bugzilla now. Thanks for reporting it there. Setting status to "UPSTREAM" Has this bug been fixed? According to the upstream bug report, it has not yet been investigated by X.Org developers. If you'd like to, you can track the bug report by adding yourself to the CC on the upstream bug report however. It is located at: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118860 Hope this helps. Just wanted to note that comment #17 also applies to Fedora Core 3 final. Hello, I have the same problem with Fedora Core 4 on my Dell Inspiron 7500. I am new with Linux/ Fedora. The solution must be adding "vga = 792" to a file, but witch file is it? I can't find the files called above. Are they renamed? Using a portable isn't very usefull if you have to connect another screen to it... It gets added to the kernel command line. You put it in /etc/grub.conf on the kernel line of the kernel you want to boot. I'm reopening this bug for current rawhide because the upstream bug referenced in comment #19 has been closed as fixed. Any hope of getting the patch added to the current rawhide x11? It's fixed in Xorg CVS HEAD according to the upstream bug report, which means the X11R7 release will have the fix. Fedora Core 5 will contain X11R7, so the fix will automatically be in FC5, and will be available to people when we integrate X11R7 into rawhide. Setting status to "NEXTRELEASE" (FC5) |