|
From: Jarek L. <ja...@ne...> - 2005-05-26 22:20:40
|
>Thanks for your bug report. >I just commited a fix for this problem. It should be available in the >anonymous CVS in a couple of hours. The fix seems to work. It still outputs some, what seems to be, errormessages: $ gddccontrol Xinerama not supported Device: pci:01:00.0-0 Error while reading write message answer: Bad message Reading EDID 0x50 failed. Device: pci:01:00.0-1 Error while reading write message answer: Bad message Reading EDID 0x50 failed. Device: pci:01:00.0-2 dev:/dev/i2c-7: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-6: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-5: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-4: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-3: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-2: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-1: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. dev:/dev/i2c-0: No such device or address Be sure you've modprobed i2c-dev and correct framebuffer device. currentid(-1) != nextid(0), trying... Device: pci:01:00.0-2 i2c-algo-bit.o: readbytes: i2c_inb timed out. Error while reading read message answer: Bad message currentid == nextid (0) But the monitor is detected, the gui starts and you can change and save some things (brightness, contrast) and revert to factory settings. The "Magic Bright Mode" I can't seem to save, though I don't know what it is so it doesn't matter. Thank you for the amazingly fast response on my post btw. Regards, Jarek |