I have a Rage 128 in a G4 cube, and I'm having some trouble getting it
to send display to the ADC video port. If I use 'video=ofonly', I can
use an ADC monitor (a 17" ADC CRT), but as far as I can tell, that
bypasses the aty128fb driver. (The FBdev X server doesn't work with
'video=ofonly', but that's another story.)
If I use 'video=aty128fb', I can drive a VGA monitor hooked to the VGA
port (but my VGA monitor isn't doing so well these days). The
suggested 'video=aty128fb:vmode:14' didn't seem to have any effect
(seen on a YDL list, among others).
Here's the aty128fb output from dmesg (kernel 2.6.9 w/ Debian patches):
aty128fb: Invalid ROM signature 1110 should be 0xaa55
aty128fb: BIOS not located, guessing timings.
aty128fb: Rage128 PF PRO AGP [chip rev 0x1] 16M 128-bit SDR SGRAM (1:1)
Other card info:
# lspci -v -s 0:10.0 # [numeric PCI ID: 1002:5046]
0000:00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128
PF/PRO AGP 4x TMDS (prog-if 00 [VGA])
Flags: bus master, stepping, 66MHz, medium devsel, latency 255, IRQ 48
Memory at 94000000 (32-bit, prefetchable) [size=64M]
I/O ports at 802400 [size=256]
Memory at 90000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [50] AGP version 2.0
Capabilities: [5c] Power Management version 2
Suggestions? Should I look at some of the development code instead of
the mainline kernel drivers? If the Rage128 registers are readable, I
can try to modify the driver probe routine to see how OF set the
registers up to enable the ADC port (vs VGA).
thanks for reading this far,
--
- Charles Lepple
|
