If I had HDMI turned off to start with, your method would not turn it on. There was no error message in the complete process following your instruction, but HDMI display shows 'no signal'.
$ sudo /usr/sbin/ch7036_start /usr/sbin/ch7036_monitor: starts Found device ID 0x56 Found revision ID 0x81 Mode 1024x768 (95) 1024x768, dot clock 65000000 -Hsync -Vsync H: start 1048, end 1184, skew 0, total 1344 V: start 771, end 777, total 806 Firmware size = 3295 bytes. As said, the device works on Windows 7. I down-tuned the resolution, because even on Windows 7, the max resolution offered for HDMI is 1280x720, smaller than LVDS's native resolution and CH7036's advertised max resolution (both are 1366x768). As you can see the resolution is 1024x768, that means in Linux I down- tuned it even lower than Windows 7, because in xrandr, the next resolution below 1366x768 is 1024x768. I was rather surprised when I look up the specs of WeTab and found that bModo has exactly the same configuration, including CPU type, memory, hard disk space and resolution. It really look like bModo 12 is just another casing of WeTab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
