People affected by this bug are probably wondering why the kernel team doesn’t just add the patch and fix it. It would be some effort to make a kernel driver out of it. Did you try it when the hdmi was originally off? Joseph Salisbury jsalisbury wrote on I already thought about offering a package of the driver on my blog, but sadly even with some online tutorials I wasn’t able to create a working package. It really look like bModo 12 is just another casing of WeTab. At least the chrontel driver did not work with my DVI-D screen.
|Date Added:||14 February 2014|
|File Size:||20.32 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Joseph Salisbury jsalisbury wrote on I know it is off-topic, but googling 10 minutes there is no right place to discuss this issue.
I’m using a WeTab which uses the same hardware as the bModo 12 so it should normally work. To be filled by O. This change was made by a bot. I’m the creator of this blog.
Wed Feb 13 Timo Aaltonen tjaalton on See full activity log. Even though the linux driver is a piece of crap it offers much higher resolutions.
Other bug subscribers Subscribe someone else. Status changed to Confirmed 2.
Zhang Weiwu zhangweiwu wrote on There is a driver for the chromebook called chrontelbut that driver is more or less a hacked daemon that sends some data to the chip and gives me the following error message:. Perhaps that’s because I am not using a chrome book.
(PDF) CH7036 Datasheet download
It finally works for me. I used an x tablet, crhontel 12, designed for Windows 7. I don’t actually know if it’s a hardware problem screen not supportedor a driver problem. 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.
I guess it is easier and more useful to push for a chrkntel from Debian side, since multiple desk distros depend on Debian.
Bug # “Chrontel CH chip not supported” : Bugs : linux package : Ubuntu
As said, the device works on Windows 7. How can I take advantage of that with VLC or mplayer?
Maybe with that the driver ignores the missing signal. There was no cyrontel message in the complete process following your instruction, but HDMI display shows ‘no signal’.
ch_debug.c – chromiumos/third_party/chrontel – Git at Google
People affected by this bug are probably wondering why the kernel team doesn’t just add the patch and fix it. I don’t know packaging to try it myself. Yes, including running git bisection searches GraphicsCard: I’m running a WeTab with ubuntu and the ch chip is not supported. Maybe close this one and re-file it in Debian?
As you can see the resolution is x, that means in Linux I down-tuned it even lower than Windows 7, because in xrandr, the next resolution below x is x Duplicates of this bug Bug It would be some effort to make a kernel driver out of it.
Carli s wrote on This can be done by mailing the Linux Kernel Mailing List or opening a bug at bugzilla. There is a driver for the chromebook called chrontelbut that driver is more or less a hacked daemon that sends some data to the chip and gives me the following error message: Email me about changes to this bug report.