How about X1250 on Asus/M2A-VM ?
![](https://seccdn.libravatar.org/avatar/54acddf2588226a9c2703a26e6119651.jpg?s=120&d=mm&r=g)
Hello! Xorg.0.log: (II) RADEONHD(0): Initializing INT10 (II) RADEONHD(0): Primary V_BIOS segment is: 0xc000 (**) RADEONHD(0): Depth 24, (--) framebuffer bpp 32 (--) RADEONHD(0): Detected an RS690 on a ATI Radeon X1250 for Asus/M2A-VM (II) RADEONHD(0): Mapped IO at 0x2b1c1773d000 (size 0x00010000) (II) RADEONHD(0): Getting BIOS copy from INT10 (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x1043 SubsystemID: 0x826d IOBaseAddress: 0xde00 Filename: BR25534A.bin BIOS Bootup Message: ATI Radeon Xpress ?1250? for Asus/M2A-VM (II) RADEONHD(0): Framebuffer space used by Firmware (kb): 19 (II) RADEONHD(0): Start of VRAM area used by Firmware: 134198272 (--) RADEONHD(0): VideoRAM: 131072 kByte (II) RADEONHD(0): Framebuffer space used by Firmware (kb): 19 (II) RADEONHD(0): Start of VRAM area used by Firmware: 134198272 (II) RADEONHD(0): AtomBIOS requests 19kB of VRAM scratch space (II) RADEONHD(0): AtomBIOS VRAM scratch base: 0x7ffb400 (WW) RADEONHD(0): rhdAtomBIOSAllocateFbScratch: FW FB scratch area not located at the end of VRAM. Scratch End: 0x7fff401 VRAM End: 0x8000000 (II) RADEONHD(0): Cannot get VRAM scratch space. Allocating in main memory instead (II) RADEONHD(0): Default Engine Clock: 40000 (II) RADEONHD(0): Default Memory Clock: 20000 (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 120000 (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0 (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Input: 1350 (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Input: 100 (II) RADEONHD(0): Maximum Pixel Clock: 40000 (II) RADEONHD(0): Reference Clock: 1432 (II) Loading sub module "i2c" (II) LoadModule: "i2c"(II) Module "i2c" already built-in (II) RADEONHD(0): Default Engine Clock: 40000 (II) RADEONHD(0): I2C bus "RHD I2C line 0" initialized. (II) RADEONHD(0): Default Engine Clock: 40000 (II) RADEONHD(0): I2C bus "RHD I2C line 1" initialized. (II) RADEONHD(0): Default Engine Clock: 40000 (II) RADEONHD(0): I2C bus "RHD I2C line 2" initialized. (II) RADEONHD(0): Default Engine Clock: 40000 (II) RADEONHD(0): I2C bus "RHD I2C line 3" initialized. (II) Loading sub module "ddc" (II) LoadModule: "ddc"(II) Module "ddc" already built-in (II) RADEONHD(0): I2C device "RHD I2C line 0:ddc2" registered at address 0xA0. (II) RADEONHD(0): I2C device "RHD I2C line 0:ddc2" removed. (II) RADEONHD(0): I2C device "RHD I2C line 1:ddc2" registered at address 0xA0. (II) RADEONHD(0): I2C device "RHD I2C line 1:ddc2" removed. (II) RADEONHD(0): I2C device "RHD I2C line 2:ddc2" registered at address 0xA0. (II) RADEONHD(0): I2C device "RHD I2C line 2:ddc2" removed. (II) RADEONHD(0): I2C device "RHD I2C line 3:ddc2" registered at address 0xA0. (II) RADEONHD(0): I2C device "RHD I2C line 3:ddc2" removed. (II) RADEONHD(0): Detected VGA mode. (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0 (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 120000 (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Input: 100 (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Input: 1350 (II) RADEONHD(0): Maximum Pixel Clock: 40000 (II) RADEONHD(0): Reference Clock: 1432 (--) RADEONHD(0): Attaching Output DAC B to Connector VGA (--) RADEONHD(0): Attaching Output DAC A to Connector DVI-I (EE) RADEONHD(0): RHDLVTMAInit: unhandled connector type: 2 (EE) RADEONHD(0): Failed to detect a connected monitor (II) RADEONHD(0): Destroying DAC B (II) RADEONHD(0): Destroying DAC A (II) RADEONHD(0): I2C bus "RHD I2C line 0" removed. (II) RADEONHD(0): I2C bus "RHD I2C line 1" removed. (II) RADEONHD(0): I2C bus "RHD I2C line 2" removed. (II) RADEONHD(0): I2C bus "RHD I2C line 3" removed. (II) UnloadModule: "radeonhd" (II) UnloadModule: "int10" (II) Unloading /usr/lib/xorg/modules//libint10.so (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found conntest: Checking connectors on 0x791E, 0x1043, 0x826D (@01:05:00): Load Detection: RHD_OUTPUT_NONE HotPlug: RHD_HPD_0 DDC: RHD_DDC_NONE LVDS Info: 18bits, single link, LDI Panel found. Power Timing: 0x000, 0x000, 0x00, 0x00, 0x000 Macro: 0x00000000, Clock Pattern: 0x0001 -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/30fae5bce90608fb3df5c018c586aea6.jpg?s=120&d=mm&r=g)
--- xeb@mail.ru schrieb:
(EE) RADEONHD(0): RHDLVTMAInit: unhandled connector type: 2 (EE) Screen(s) found, but none have a usable configuration.
Fatal server error: no screens found
Thats the same thing which happens to my Gigabyte X1300 pro (515) with a DVI Monitor attached (LG-2000CE). The Connector detection reports a LVTMA but LVTMA is only valid for Panels and not for DVI monitors. Currently radeonhd always uses LVDS if a LVTMA connector is beeing detected, but for what i know the DVI spec uses TMDS for signal transmitting, isn't? I'll post my verbose logs in the evening. LieGrü, strub Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/33d15f8ccb02a24170ec27c0630ae2b6.jpg?s=120&d=mm&r=g)
Hi, currently suspend to ram support is not working correctly on my card. I don't want to be imposing, because I am very pleased with the work done on this driver so far. However, right now the main thing keeping me with vesa over radeonhd is the inability to supend. Should I expect this to be fixed soon? The problem, in my case, is that resume from suspend gives a very corrupted screen. Switching to terminal gives a black screen, and switching back to X still gives me a corrupted screen. If it will help, I can produce a Xorg log or anything else. Thanks for all your hard work! -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/5e89cd3aaa767545a7ab3f858376b213.jpg?s=120&d=mm&r=g)
Hi,
try to change resolution using ctrl+alt+
Hi, currently suspend to ram support is not working correctly on my card. I don't want to be imposing, because I am very pleased with the work done on this driver so far. However, right now the main thing keeping me with vesa over radeonhd is the inability to supend. Should I expect this to be fixed soon?
The problem, in my case, is that resume from suspend gives a very corrupted screen. Switching to terminal gives a black screen, and switching back to X still gives me a corrupted screen. If it will help, I can produce a Xorg log or anything else. Thanks for all your hard work!
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/33e428940a66ca4bbe800b691b096a5e.jpg?s=120&d=mm&r=g)
Level 1 schrieb:
Hi, currently suspend to ram support is not working correctly on my card. I don't want to be imposing, because I am very pleased with the work done on this driver so far. However, right now the main thing keeping me with vesa over radeonhd is the inability to supend. Should I expect this to be fixed soon?
The problem, in my case, is that resume from suspend gives a very corrupted screen. Switching to terminal gives a black screen, and switching back to X still gives me a corrupted screen. If it will help, I can produce a Xorg log or anything else. Thanks for all your hard work! Does it look as in http://www.privatvermietung-kiel.de/tmp/pict0038.jpg for you too? I reported that allready on 07.10.2007 in "rhd_conntest of X1400 on Toshiba A100-773".
I just tried pressing ctrl+alt+
![](https://seccdn.libravatar.org/avatar/4ca3f0091a6f5d84813e4a712d774671.jpg?s=120&d=mm&r=g)
On Mon, Oct 15, 2007 at 05:19:24PM +0200, Felix M?ller wrote:
Level 1 schrieb:
Hi, currently suspend to ram support is not working correctly on my card. I don't want to be imposing, because I am very pleased with the work done on this driver so far. However, right now the main thing keeping me with vesa over radeonhd is the inability to supend. Should I expect this to be fixed soon?
The problem, in my case, is that resume from suspend gives a very corrupted screen. Switching to terminal gives a black screen, and switching back to X still gives me a corrupted screen. If it will help, I can produce a Xorg log or anything else. Thanks for all your hard work! Does it look as in http://www.privatvermietung-kiel.de/tmp/pict0038.jpg for you too? I reported that allready on 07.10.2007 in "rhd_conntest of X1400 on Toshiba A100-773".
I just tried pressing ctrl+alt+
but that does not help. Hopefully this issue gets fixed. ;)
Thanks Felix M?ller
We are working on much more pressing issues at the moment. Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/4ca3f0091a6f5d84813e4a712d774671.jpg?s=120&d=mm&r=g)
On Mon, Oct 15, 2007 at 10:31:55AM +0200, Mark Struberg wrote:
--- xeb@mail.ru schrieb:
(EE) RADEONHD(0): RHDLVTMAInit: unhandled connector type: 2 (EE) Screen(s) found, but none have a usable configuration.
Fatal server error: no screens found
Thats the same thing which happens to my Gigabyte X1300 pro (515) with a DVI Monitor attached (LG-2000CE).
The Connector detection reports a LVTMA but LVTMA is only valid for Panels and not for DVI monitors.
LVTMA is a shared LVDS/TMDS device. When set up correctly, it does DVI.
Currently radeonhd always uses LVDS if a LVTMA connector is beeing detected, but for what i know the DVI spec uses TMDS for signal transmitting, isn't?
Connector is not LVTMA, connector is one of VGA, DVI, LVDS. When LVDS is there, LVTMA is always there too, as this is the only output which can support LVDS. As for RS690 support, egbert is working on that. Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/30fae5bce90608fb3df5c018c586aea6.jpg?s=120&d=mm&r=g)
--- Luc Verhaegen
(EE) RADEONHD(0): RHDLVTMAInit: unhandled connector type: 2 Connector is not LVTMA, connector is one of VGA, DVI, LVDS. When LVDS is there, LVTMA is always there too, as this is the only output which can support LVDS. Sorry, it is DVI.
As mentioned before my card is a Gigabyte X1300 Pro 256MB with a DVI attached TFT. I'll also attach my X log and hope it helps. I currently only have a digital monitor cable but I'll look for a VGA cable in my company and do further tests tomorrow. And btw, thanks for the amazing work you all do! LieGrü, strub Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail
participants (6)
-
Felix Möller
-
Karel Podvolecky
-
Level 1
-
Luc Verhaegen
-
Mark Struberg
-
xeb@mail.ru