|Summary:||problem with Inspiron 8000|
|Product:||[Retired] Red Hat Linux||Reporter:||John Mizell <john.mizell>|
|Component:||XFree86||Assignee:||X/OpenGL Maintenance List <xgl-maint>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||David Lawrence <dkl>|
|Version:||9||CC:||dave.habben, dkelson, garlick, mharris, msw|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2004-09-24 19:15:33 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
|Bug Blocks:||79579, 100644|
Description John Mizell 2003-01-09 14:56:11 UTC
Description of problem: During installation the Monitor's vertical and horizontal syncs were not detected and could not run the graphical install. After install I ran redhat- config-xfree86 and it still could not find the vertical and horizontal syncs. It ran dcc probe and reported none for all four values. My monitor is a dell LCD 1600X. I could not solve the problem in either cases other wise because it did not let me select my monitor settings manually. Version-Release number of selected component (if applicable): How reproducible: I can reporduce it everytime. Steps to Reproduce: 1. Try installing it on dell inspiron 8000 notebook with 15 inch LCD screen and ati video card. 2. Also can reproduce when Phoebe beta is installed by running redhat-config- xfree86 3. Actual results: all four values are reported back as "none" VendorName: None ModelName: None HorizSync: None VertRefresh: None Expected results: VendorName: Dell ModelName: 1600X HorizSync: 31.5 -90.0 VertRefresh: 59.0 - 85.0 Additional info:
Comment 1 Bill Nottingham 2003-01-10 05:00:53 UTC
LCDs can't really be DDC probed. What were the errors when you tried to pick manually? Was is just not in the list?
Comment 2 Brent Fox 2003-01-10 14:29:41 UTC
jrmizell: please try redhat-config-xfree86-0.7.1-4 out of Rawhide and see if that fixes the problem. That version made some Inspiron 4000's work for the first time, so maybe it will work for you too. (See bug #80402).
Comment 3 Brent Fox 2003-01-10 16:08:32 UTC
Changed the summary to something more descriptive
Comment 4 Brent Fox 2003-01-14 20:11:17 UTC
Comment 5 John Mizell 2003-01-15 03:13:35 UTC
tried the redhat-config-xfree86 from rawhide and it did not work. It trys a dcc probe even though it is a LCD screen and still does not get any values for it. IT does not give me a list to try and pick from. The only list avalible is in the anaconda installer. After running redhat-config-xfree86 from the beta and from rawhide you get a screen that says it could not read the xfree86 configuration file or it is corrupt. Then try to do the detection which fails with the message I gave before describing the actual results. Then gives you options to try again or cancel.
Comment 6 Mike A. Harris 2003-01-15 07:19:48 UTC
Just for correctness... Some LCD's can be DDC probed, but most can't.
Comment 7 Dave Habben 2003-01-21 19:45:17 UTC
I have the same problem with the graphical installer of Phoebe 8.0.92 & 8.0.93, this is on a Dell Inspiron 8000 w/ ATI Rage 128 Mobilty M4 & 15 inch screen. The text installer created a XF86Config file which contained the following: DefaultDepth 24 SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection None of these modes seem to work with this release of XFree86 (but they did on Red Hat Linux 8.0) When I change it to: DefaultDepth 24 SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" EndSubSection Or: DefaultDepth 16 SubSection "Display" Depth 16 Modes "1600x1200" "1280x1024" EndSubSection I can at least use XFree86 using the r128 driver and DRI Acceleration. I would recommend that whichever tool (possibly redhat-config-xfree86) generates this config file has a modes line that looks like: Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" That way at least it will have some modes in there that do work. Tracking down why resolutions <= 1024x768 don't work could be filed as a new bug.
Comment 8 Brent Fox 2003-02-06 05:42:24 UTC
Ok, I think I'm starting to get an understanding of what's happening. When r-c-xfree86 runs and generates a file from scratch, it does the following things: 1) probes the video card and monitor 2) does some algorithms to figure out what modes this card/monitor combo can reasonably support 3) generates the file 4) starts the X server with this baseline file. What is happening is that the monitor can't be probed, so the detection code reverts back to a generic monitor. Unfortunately, this causes step 2 to determine that the monitor can't do anything above 1024x768. Since it seems that this mointor can't do anything <= 1024x768, it causes steps 3 and 4 to fail. This problem occurs on my laptop, whose screen cannot be probed. However, since my screen can do <= 1024x768, falling back to the lower resolution isn't such a bad thing. In your case it causes the tool to not work. Unfortunately, I'm not sure what I can do about it. Ultimately, we need a better way to detect LCDs as that would solve everything. Given where we are in the release cycle, I'm not comfortable with making the kinds of changes neccessary to address this. It also doesn't help that I don't have access to an Inspiron 8000 to test with. Here's one workaround that you might try. 1) Move your existing /etc/X11/XF86Config file out of the way 2) Run 'redhat-config-xfree86 --set-hsync='31.5-90.0' --set-vsync='59.0-85.0' --set-resolution='1600x1200' 3) See if an /etc/X11/XF86Config file was created 4) See if that file works. Any luck with the workaround?
Comment 9 Brent Fox 2003-02-08 14:29:41 UTC
msw: can you try testing the latest tree on your Inspiron? I'm curious to see if the latest r128 driver allows this screen to do lower resolutions. Also msw, do you know which screen you have? It looks like there are three possible screens for this laptop: From Dell's website: 15 inch UltraSharpTM UXGA+ TFT active-matrix display with 1600 x 1200 resolution 15 inch Ultra XGA TFT active-matrix display with 1600 x 1200 resolution 15 inch Super XGA+ TFT active-matrix display with 1400 x 1050 resolution I can't find anything on their website about the other possible resolutions that these screens can handle.
Comment 10 Brent Fox 2003-02-17 20:15:10 UTC
msw's test on his laptop did not work. When redhat-config-xfree86 can't probe a monitor, it tries to use 800x600. After talking with msw, I'm going to transfer this bug to XFree86 since I believe that the real problem is that the r128 driver isn't allowing the screen to do 800x600, which it should be able to do.
Comment 11 John Mizell 2003-05-04 19:10:17 UTC
I found a temporary work a round until the xfree86 detection method is fixed. Just use the Vesa card settings to get X up and running. Here is an example: redhat-config-xfree86 --set-resolution='1024X768'--set-hsync='31.5-90.0'--set-vsync='59.0-85.0'--set-driver='vesa'--set-card='driver VESA driver (generic)'--set-videoram='0' Thanx, John Mizell
Comment 12 Dax Kelson 2003-05-14 16:15:19 UTC
I'm adding this comment on behalf of Tim Garlick <email@example.com> who discovered this same problem after doing a fresh install of RHL9. He was running RHL7.1 (he thinks) before with no problems. We just now downloaded the -10 packages from Rawhide and tried again with no avail. He is running the "vesa" driver as a workaround.
Comment 13 Don Hardaway 2003-06-19 15:15:20 UTC
I have been reporting this problem to m harris for a year without any resolution. The only two things that I have found to work is to use the vesa driver and not have a faster display or get the beta driver from: http://www.scitechsoft.com/products/enterprise/enterprise_download/snap_linux_download.html The r128 driver sucks.
Comment 14 Dax Kelson 2003-06-19 16:00:00 UTC
Has anyone tried the lastest XFree86 from rawhide (4.3.0-15 right now)? * Wed May 28 2003 Mike A. Harris <firstname.lastname@example.org> 4.3.0-13 - Updated to XFree86-4.3.0-xf-4_3-branch to pick up the latest fixes from the stable XFree86 4.3.0 branch
Comment 15 Dax Kelson 2003-08-06 23:31:01 UTC
Any word if this is fixed with the severn beta?
Comment 16 Dave Habben 2003-11-01 18:22:55 UTC
This looks like this might have gotten fixed for the upcoming 4.4.0 release: http://bugzilla.xfree86.org/show_bug.cgi?id=661
Comment 17 Mike A. Harris 2004-09-24 19:15:33 UTC
Yep, it seems to be fixed now. Please upgrade to Fedora Core 2 or later, and if this issue turns out to still be reproduceable, please file a bug report in the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates.