You could always try our CM10.1 build. Only thing to change is the kernel.

To get a custom kernel running is a little bit more complicated. I will look at the dmesg above,.

But keep in mind, our CM10.1 does not need a custom kernel, it should run with every 3.0.8 stock kernel.

Problems are always, the touch and the sensors, but we could try to fix it. Yous should have a StockRFom for flashing back before you try this.

Hmm... thats complicated.

Only to know the the real name of the display does not mean that the driver is working for it.

Looks interesting, I think that one of the parameters of the screen drivers is wrong.

Could you please upload the driver file, so I can look at the content?

Would be nice to see your other changes..

Okay... I have looked at the driver and perhaps I have found your problem..

Look at the Line with:

#define H_FP 150

This is the right margin of your display, perhaps you can change it to higher or lower value and it helps.

hmm.. not easy I think.

what happens if you change the left offset of the screen (h_PB)?

I think this is a trial and error situation. There are a few parameters to play with..

screen->left_margin = H_BP;
screen->right_margin = H_FP;
screen->hsync_len = H_PW;
screen->upper_margin = V_BP;
screen->lower_margin = V_FP;
screen->vsync_len = V_PW;

I'm sorry that I can give no better advice, you are the only one who could play with this defines.