> > So this patch helps? I'll add it. > > --- a/drivers/ps3/ps3av.c > +++ b/drivers/ps3/ps3av.c > @@ -731,6 +731,9 @@ static const struct ps3av_monitor_quirk > .monitor_name = "L226WTQ", > .clear_60 = PS3AV_RESBIT_1920x1080I | > PS3AV_RESBIT_1920x1080P > + }, { > + .monitor_name = "SyncMaster", > + .clear_60 = PS3AV_RESBIT_1920x1080I > } > }; > works fine! >> default resolution might be worth a thought. This should work on all HD >> screen. >> > > I'm considering to remove the 1080i modes from ps3av_preferred_modes[], as > many HDMI screens seem to have problems with interlaced modes. > That would decrease the size of psav_monitor_quirks[] (note that I currently > don't add screens that advertise broken modes if their best advertised video > mode does work). > In addition 1080i looks bad on most screens that support it anyway. > > What do people think? > > In contrast to this, many screens (like yours) seem to support 1080p, while > they don't advertise it. So perhaps we need .set* fields in > psav_monitor_quirks[], too? I'm a bit reluctant to do that, as many vendors > are not very specific when it comes to the monitor_name field (my collection > has e.g. `SAMSUNG', `SyncMaster', `SONY TV'). > > Your right my screen supports 1080p but it leaves me with a message on the screen (that doesn't disappear by itself) telling me that this is not the optimal resolution and to switch to 1650x1080. I'm not sure how other screens behave but if they behave the same way this should be considered. >> btw, I get the following message while booting: >> PS3AV_CID_AV_VIDEO_DISABLE_SIG: failed 2 port 10 >> >> does this ring a bell? I'm using kernel 2.6.22 with ps3 patches >> > > Do you put your kernel in FLASH ROM (otheros.bld)? > Does it still happen after upgrading to a kernel that has > ps3-wip/ps3av-vesa-stripes-workaround.diff applied (e.g. Geoff's current git > tree)? > Yes kernel is written to flash memory. I added ps3-wip/ps3av-vesa-stripes-workaround.diff to my source tree, the message persists, even using Geoff's git tree with my .config file and running oldconfig didn't change the behavior. I'll append my .config file. The message is the very first line printed at kernel boot. Stefan