Created attachment 14277 [details]
X does not start. Logs attached.
(--) 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
 320 x 240, 72Hz
 400 x 300, 72Hz
 512 x 384, 70Hz
[11e] 640 x 400, 70Hz
 640 x 480, 60Hz, 75Hz, 85Hz, 100Hz, 160Hz
 800 x 600, 60Hz, 75Hz, 85Hz
 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
 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" ?
dropping NEEDINFO bug off the tracker.
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.
Whoops, forgot to close.