| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | zlice has quit IRC (Quit: zlice) | [19:03] |
| Belliash | hello
Where can I report problems with http://git.linuxtv.org/cgit.cgi/media_build.git ? I cannot get IT9135 to work as I cannot build necessary drivers. | [10:31] |
| ...... (idle for 27mn) | ||
| And I cannot use drivers provided with kernel, because it does not suport DD Cine S2 v6.5 :-( | [11:01] | |
| ........... (idle for 53mn) | ||
| any1 around? | [11:54] | |
| .......................... (idle for 2h8mn) | ||
| *** | vdr changes his alias to p_body|away
p_body|away changes his alias to vdr vdr changes his alias to p-body | [14:02] |
| ............................ (idle for 2h19mn) | ||
| p-body changes his alias to p_body|away | [16:22] | |
| ........................ (idle for 1h57mn) | ||
| wondiws | hi guys, I've got this chinese DVB-T mini-dongle that has a ITE IT9135 chip on it. Now I download the firmware, and this loads apparantly without errors. But I don't receive anything on my linux system. How do I troubleshoot this? | [18:19] |
| devinheitmueller | wondiws: I didn't say anyone would actually answer. :-p | [18:22] |
| wondiws | devinheitmueller, I've been long enough on IRC to know the deal ;)
can I do something with the 4 device nodes I get under /dev/dvb/adapter0? | [18:22] |
| devinheitmueller | It's probably a driver bug. the 9135 driver has had a variety of issues, largely dependent on exactly which version of the driver you're running.
Probalbly make sense for you to start by installing the media_build tree with the latest driver, and see if the issue is already fixed. | [18:24] |
| wondiws | :(
I don't get the wiki: my usbid resolves to Kworld UB499-2T on the wiki, but that page has all kinds of devices on it | [18:25] |
| devinheitmueller | There are lots of different products which use the same chipset. | [18:26] |
| wondiws | 048d:9135
devinheitmueller, but I get this idea because some devices with a Realtek chipset are listed there | [18:26] |
| devinheitmueller | Also, in some cases the product vendor is lazy and doesn't use their own USB ID, so what you're getting is the default USB ID burned into the chip, and then all the product vendors use the drivers provided by the chip vendor.
which page are you referring to? | [18:27] |
| wondiws | www.linuxtv.org/wiki/index.php/Kworld_UB499-2T
but I guess that page only highlight my device on the page | [18:27] |
| devinheitmueller | Looks like for some reason the Wiki has a page name with the product name, which just points back to the list of all DVB-T devices supported.
Weird. | [18:28] |
| wondiws | but my usbid is supported according to the page | [18:29] |
| devinheitmueller | Supported as in "somebody put a driver into Linux and it worked at some point". Regressions though are very common in Linux TV.
(e.g a driver which worked fine in 3.2 broke in 3.3 and nobody noticed) | [18:29] |
| wondiws | devinheitmueller, I'm in 4.1.6-1 | [18:40] |
| devinheitmueller | I was just using those version numbers as examples. | [18:40] |
| wondiws | but now after all this time (how long have we been chatting), I get two errors: | [18:41] |
| devinheitmueller | The point is that there are lots of cases where a device works well and then a new kernel release comes out and that device gets broken. | [18:41] |
| wondiws | dtv access error: cannot demux: No such device
core stream error: cannot pre fill buffer oh, damn, it's because I removed the device :P obviously | [18:41] |
| ................ (idle for 1h16mn) | ||
| devinheitmueller, I think I broke my dongle now :( | [19:57] | |
| oh it works again, but the connector is shaky | [20:07] | |
| ............ (idle for 55mn) | ||
| anyone in here? :) | [21:02] | |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |