Fw:È davvero auspicabile che ti goda una bella giornata di lavoro
Troppo figo per essere vero? www.alrewilna1984.blogspot.ch Grazie di cuore,marco caminati
Re: rtl28xxu IR remote
> I think the most easiest way could be compile & install whole Kernel > from my tree. It is 3.10-rc4 + some fixes. Ok, but I first tried the easier alternative you advised below. > media_build.git has also option to fetch developer git tree from > linuxtv.org. Something like ./build --git > git://linuxtv.org/anttip/media_tree.git rtl28xxu . That approach seem to > be not documented on wiki: > http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers Thanks for the suggestion. It is documented only in ./build --help, it seems. I tried this latter way, it built succesfully, but the modules won't work: modprobe --force dvb_usb_rtl28xxu gives err kernel: dvb_core: exports duplicate symbol dvb_ca_en50221_camchange_irq (owned by kernel) -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: rtl28xxu IR remote
> Hi, I just compiled and tested Antti Palosaari branch and can confirm the > remote works for my RTL2832U. > I have updated the wiki[1] entry with the steps necessary to configure the > remote control. > Please confirm if these fixes your problem. Thanks, but I can't confirm if this fixes my problem, because the modules I obtain building Antti's branch are not compatible with my existing kernel, so I can't test them (modprobe --force fails, and using a brand new kernel would be too much work on Tinycore at the moment). On the other hand, I tried the sources fromgit://linuxtv.org/media_build.git, first with manual patches and then (when the latter got accepted) without them. But the ir remote does not work. I think Antti's repo and patching linuxtv repo should lead to the same results, right? -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
rtl28xxu ir remote
Thanks for the recent efforts as from subject. I tested it with no success, however. Indeed, with old r820t-unaware drivers (e.g., v4l version df33bbd60225), I used to get some output from cat /dev/input/eventX upon pressing ir remote buttons (passingrtl2832u_rc_mode=2 to modprobe). Now this does not work any longer. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
rtl2832u+r820t working
This usb dongle (0bda:2838) now works for me. Thanks to all people who worked on it, especially to Gianluca. Built from git://linuxtv.org/media_build under Linux box 3.8.10-tinycore #3810 SMP Tue Apr 30 15:45:26 UTC 2013 i686 GNU/Linux. ---INFRARED REMOTE--- I also ask if ir remote will be supported. With some old version of v4l (not supporting r820t) I managed to have the infrared working as a hid (/dev/input/eventX) device. So it should be possible to merge the code from that old version into the current one to have everything supported. The problem is that I can't remember which version was that, can anybody help me? Alternatively, I patched as from [1], and successfully built, current v4l: however, resulting .ko do not support ir remote, it seems (not even as an option to pass to modprobe). Any indication, please? Cheers [1] https://patchwork.kernel.org/patch/2468671/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: rtl2832u+r820t dvb-t usb kernel crash
> Hi Marco, > I have the same device and the same issue on a 2.6.32 32 bit kernel. > However, I was able to run the driver successfully on 3.2.44 and 3.9.0 > kernels (both 32 and 64 bit). > Also, I can run a similar device with a e4000 tuner with no problem even > on the old 2.6.32 kernel. > I just posted a few patches for the r820t tuner, can you try them and > check if they fix your problem? Thanks for your prompt work! I patched and built the modules in the same host OS. The system still crashes badly. Moreover, this time I get no crash log via klogd: last line in the log is May 7 00:01:54 box user.info kernel: usbcore: registered new interface driver dvb_usb_rtl28xxu So I have no error messages this time. If it's useful, I can try to set up netconsole to get them. Concurrently, I will build a more recent kernel to test the device, as suggested by Mauro. Cheers, Marco -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
rtl2832u+r820t dvb-t usb kernel crash
My thanks to Mauro for his work on this device. Eager to try it, I built sources yesterday following directions on http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers My environment is Tinycore Linux 4.7.5: Linux box 3.0.21-tinycore #3021 SMP Sat Feb 18 11:54:11 EET 2012 i686 GNU/Linux The PC hangs (not even REISUB working) as soon as I plug my device in usb port. Killing udevd and loading one module a time, I found that the crash occurs exactly when I load dvb-usb-rtl28xxu.ko AND the device is plugged. I.e., to crash I just need to sudo modprobe dvb-usb-rtl28xxu and plug. My device is as from subject, with lsusb giving 0bda:2838. It looks like this: http://www.hamradioscience.com/wp-content/uploads/2012/10/R820T-560x420.jpg I am quite sure it has a r820t tuner because sdr.osmocom.org logs told me so, and because I managed to make it work (as a DVB-T receiver) by patching some r820t code for an old kernel, see http://www.spinics.net/lists/linux-media/msg57707.html. Lars Buerding recently reported success on a newer kernel, so it might be a backport problem. However, I had similar results on a fresh Debian Wheezy yesterday. I append 1) the crash log (used klogd spitting on a -o sync mounted device). 2) lsusb -v for the device Regards, Marco * * May 6 12:56:50 box user.info kernel: usb 1-4: new high speed USB device number 4 using ehci_hcd May 6 12:56:50 box user.err kernel: WARNING: You are using an experimental version of the media stack. May 6 12:56:50 box user.err kernel: As the driver is backported to an older kernel, it doesn't offer May 6 12:56:50 box user.err kernel: enough quality for its usage in production. May 6 12:56:50 box user.err kernel: Use it with care. May 6 12:56:50 box user.err kernel: Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): May 6 12:56:50 box user.err kernel: 02615ed5e1b2283db2495af3cf8f4ee172c77d80 [media] cx88: make core less verbose May 6 12:56:50 box user.err kernel: a3b60209e7dd4db05249a9fb27940bb6705cd186 [media] em28xx: fix oops at em28xx_dvb_bus_ctrl() May 6 12:56:50 box user.err kernel: 4494f0fdd825958d596d05a4bd577df94b149038 [media] s5c73m3: fix indentation of the help section in Kconfig May 6 12:56:50 box user.err kernel: WARNING: You are using an experimental version of the media stack. May 6 12:56:50 box user.err kernel: As the driver is backported to an older kernel, it doesn't offer May 6 12:56:50 box user.err kernel: enough quality for its usage in production. May 6 12:56:50 box user.err kernel: Use it with care. May 6 12:56:50 box user.err kernel: Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): May 6 12:56:50 box user.err kernel: 02615ed5e1b2283db2495af3cf8f4ee172c77d80 [media] cx88: make core less verbose May 6 12:56:50 box user.err kernel: a3b60209e7dd4db05249a9fb27940bb6705cd186 [media] em28xx: fix oops at em28xx_dvb_bus_ctrl() May 6 12:56:50 box user.err kernel: 4494f0fdd825958d596d05a4bd577df94b149038 [media] s5c73m3: fix indentation of the help section in Kconfig May 6 12:56:50 box user.info kernel: usb 1-4: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state May 6 12:56:50 box user.info kernel: usbcore: registered new interface driver dvb_usb_rtl28xxu May 6 12:56:50 box user.alert kernel: BUG: unable to handle kernel NULL pointer dereference at 0028 May 6 12:56:50 box user.alert kernel: IP: [] 0xf11e171d May 6 12:56:50 box user.warn kernel: *pde = May 6 12:56:50 box user.emerg kernel: Oops: [#1] SMP May 6 12:56:50 box user.warn kernel: Modules linked in: dvb_usb_rtl28xxu dvb_usb_v2 rtl2830 dvb_core rc_core rt73usb rt2x00usb rt2x00lib mac80211 cfg80211 acpi_cpufreq cpufreq_userspace mperf cpufreq_stats cpufreq_powersave cpufreq_conservative squashfs scsi_wait_ May 6 12:56:50 box user.warn kernel: Pid: 52, comm: kworker/1:2 Tainted: P C 3.0.21-tinycore #3021 FUJITSU SIEMENS AMILO Li1705/AMILO Li1705 May 6 12:56:50 box user.warn kernel: EIP: 0060:[] EFLAGS: 00010246 CPU: 1 May 6 12:56:50 box user.warn kernel: EAX: EBX: ed07ff02 ECX: EDX: May 6 12:56:50 box user.warn kernel: ESI: ed232038 EDI: EBP: eee06a00 ESP: ed901f54 May 6 12:56:50 box user.warn kernel: DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 May 6 12:56:50 box user.emerg kernel: Process kworker/1:2 (pid: 52, ti=ed90 task=ed839030 task.ti=ed90) May 6 12:56:50 box user.emerg kernel: Stack: May 6 12:56:50 box user.warn kernel: ed232000 c05af00c eee03078 0001 eee03030 243e1b2c May 6 12:56:50 box user.warn kernel: ed8f2d80 ed232038 eee026c0 eee06a00 c013b0be eee02700 f11e1597 May 6 12:56:50 box user.warn kernel: eee06a05 ed8f2d80 eee026c0 ed8f2d90 ed839030 c013bc6f ed8f2d90 e
rtl2832u+r820t dvb-t usb
I have a rtl2832u+r820t dvb-t usb dongle; I use linux (x86). There is good support for using it as sdr. However, using it to watch dvb-t (I am in Europa) turned out to be difficult. The only way that worked: downgrade my linux kernel to 2.6.33.3, and compiling these sources: https://groups.google.com/d/msg/ultra-cheap-sdr/QiIo7834sLI/7YpqSRnYud4J which forced me to using an older commit of v4l (mercurial df33bbd60225), and to comment out all references to rtl2832u_rc_keys_map_table. In a word: it works, but the situation is disappointing. Since such dongles are probably to be sold massively (taking the place of the dismissed e4000-based ones), can anybody help me porting this stuff to a more maintainable form? PS: Be aware: identification of these cheap dongles can be very messy. In my case, lsusb returned 0bda:2838, which is the same as other ones having e4000 or fc0012, as ezcap EzTV646. Even the appearance can be misleading: there are e4000 looking exactly the same. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
