Bug 14465 - savage panel setup probes an implausible panel size
Summary: savage panel setup probes an implausible panel size
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/savage (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86 (IA32) Linux (All)
: highest blocker
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-11 16:55 UTC by Clodoaldo Pinto Neto
Modified: 2010-12-01 21:29 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
xorg logs (37.61 KB, text/plain)
2008-02-11 16:55 UTC, Clodoaldo Pinto Neto 		no flags Details
View All

Description Clodoaldo Pinto Neto 2008-02-11 16:55:34 UTC 
Created attachment 14277 [details]
xorg logs

X does not start. Logs attached.
Comment 1 Adam Jackson 2008-02-24 16:10:40 UTC 
(--) SAVAGE(0): Detected current MCLK value of 14.318 MHz
(--) SAVAGE(0): 4088x1020 TFT LCD panel detected but not active
(--) SAVAGE(0): Found 13 modes at this depth:
   [10f] 320 x 200, 70Hz
   [134] 320 x 240, 72Hz
   [144] 400 x 300, 72Hz
   [154] 512 x 384, 70Hz
   [11e] 640 x 400, 70Hz
   [112] 640 x 480, 60Hz, 75Hz, 85Hz, 100Hz, 160Hz
   [115] 800 x 600, 60Hz, 75Hz, 85Hz
   [118] 1024 x 768, 60Hz, 70Hz, 75Hz, 85Hz, 100Hz, 130Hz
   [17b] 1280 x 768, 60Hz
   [16a] 1280 x 960, 60Hz, 85Hz
   [11b] 1280 x 1024, 60Hz, 75Hz, 85Hz, 100Hz
   [13e] 1400 x 1050, 60Hz, 75Hz
   [124] 1600 x 1200, 60Hz
(II) SAVAGE(0): <default monitor>: Using hsync value of 0.00 kHz
(II) SAVAGE(0): <default monitor>: Using vrefresh value of 0.00 Hz
(WW) SAVAGE(0): Unable to estimate virtual size

Heehee.  Utterly improbable panel size there.

Does it work if you use Option "UseBIOS" "no" ?
Comment 2 Daniel Stone 2009-08-31 17:32:07 UTC 
dropping NEEDINFO bug off the tracker.
Comment 3 Jesse Adkins 2010-12-01 21:28:52 UTC 
After looking at the log, I think this is a hardware issue. A lot of the stuff is just really odd. Regions going from 0x10000 to 0x10 after probing, the weird initial PCI probe card, func, etc. values, a 0x0 mode, a -1 bus, 0x1 ranges, and on.

I think the motherboard is insane. Since the reporter hasn't said anything in around three years, despite prodding, I'm closing this. This bug has nobody CC'd to it, so nobody's too interested in it.

Reporter : If you have some information, such as lspci -vvv, please do share that. Let's first make sure that your motherboard isn't insane, since those are really strange PCI values.
Comment 4 Jesse Adkins 2010-12-01 21:29:21 UTC 
Whoops, forgot to close.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.