Suchergebnisse

I'm try to compile Original 5.2 and I get this error: Quellcode (3 Zeilen) This was almost the final rpocedure, making rootfs. I think maybe is related with making nfi file, because I got this in result folder: Quellcode (11 Zeilen) nfi file has size 0, rootfs.jffs2 seems to be Ok, and vmlinux too, maybe fail in some final procedure. I can't get any info about vfi3 packet, is not in synaptic and even in google I can't find info about vfi3 word related with linux. Any info about this vfi3 command…

If VTI have some changes in OE enviroment, we need same sources compiled specifically for VTI. I Don't if there is an Makefile for VTI as for original and openpli. If i'ts posible will be glad to try to compile. @scope34 : did you compile with original image or VTI 2.0. Maybe some VTI member can clarify if there was some change in i2c_core.ko or related module that makes this device don't even intialize in VTI but yes in Original 5.2 Regards

Nearly everyone in the same situation, due to i2c's error can not make it work. In ORiginal 5.1 or 5.2 you can load all modules without erros but you make a scan and nothing is found. Regards

You must load modules, where you put it is your choice, normaly are loaded to /lib/modules/xxx folder or some subfolder. You don't need any particular attributes just load it. insmod /lib/modules/dvbt/ mxl5005s.ko. After install all modules (dvb-usb-af9015.ko must be the last) if you have no error you cand check with dmesg message if there is no erro loading this modules. Regards

After many and many probes I give up :D, tomorrow is september 1 and must back to work. Whith diffrents drivers, usbtuner binaries and images sometimes can't load module, sometime load Ok but whe try to scan I see error mesage and in dmesg I get some error tryng to execute i2c commands. Maybe this happens only with Avermedia Volar Black HD, maybe some people with others AF9015 tuners can report log, to check if is a driver problem, or its only my device problem. Quellcode (19 Zeilen) Regards

Zitat: „Originally posted by albter another question ........ "ftp the script and usbtuner utility to /usr/bin" where I can download the script ????? gracias y saludos from spain“ In some other post there are a compiled version of usbtuner, I think from scope34 too. Regards from Spain too

In page 2 of this thread you got some attachements from user scope34. Regards

Zitat: „Originally posted by DrData Drivers for PLi (they use gcc4.1.1 Kernel) would be nice. I had no success when I patch vermagic to 4.1 in Scope34 drivers in PLi“ I did it and the USBtuner was recognized, and dev/dvb/adapter1/ correctly created, have tu make symlink for vtuner but finally crash when try to use usbtuner or other. Regards

You forget to restart enigma2 after running usbtuner. Regards

tns try to paste logs after adding code tags, if you do it in pop up code window all log will be added in only one line. code xxxxxxxxxxxxxxxxxxxxxxxxxxxx code add code sdfa asdf asdf asdf saf code Thank you, and thank por your script for loading and unloading modules, this make things easier. Regards

Zitat: „Originally posted by tonskidutch oké aktiv hub for usb means also additional power~ dvb-S2 usb and or dvb-C need more than standard supply USB port on VU+ is only 500 mA ciao“ Yes but in DVB-T you don't need to feed the antenna, and the same dvb-t stick in same usb-port in same machine works, the only diference are drivers and modules, and of couse DE image. Regards

Have you try to scan ? I see many cmd 3 , unknow cmd 9, and some PIDLIST: but nothing more . Regards

Yes I got firmware in the right folder. Is loaded correctly Quellcode (3 Zeilen) With Chuscha drivers I load in this order: mxl5005s.ko de_dvb-core.ko dvb-usb.ko af9013.ko dvb-usb-af9015.ko I do it with modprobe, starting always with a clean VTI 2.0 image. Finally I always ger some error from I2C module Quellcode (8 Zeilen) Quellcode (6 Zeilen) I see in your log when you try to scan : Quellcode (15 Zeilen) Remenber you recompiled usbtuner.c without message 9. Quellcode (14 Zeilen) That's why i't…

Not working, seems to have some fail in driver, no matter Chuscha or vu_duo after loading af9015 driver I get this with dmesg: Quellcode (9 Zeilen) Regards

I wil try to change drivers because when I try to load af9015 ask for some symbol from 9013 Quellcode (6 Zeilen) I load af9013 driver and the same.

Zitat: „Originally posted by Cali03 Hi I don't use udev and i get the usb tdt avaible using the solution of Chuscha when you insmod the dvb-usb-af9015.ko add adapter_nr=1 and you get all file needed in /dev/dvb/adapter1. ++“ I did it but still the same result, my usb tuner is AF9015, maybe the drivers are diferents. It's mandatory to load all modules?, in Chusca post's I only see it's mandatory to load mxl5005s.ko. Regards

I see you got some progress, but I still trying to make /dev/ nodes, I can load both drivers (the one from Chuscha and the one from vu_duo) but I get the same result. Only some nodes are created: Quellcode (3 Zeilen) I start udevd with debug parameter and this is what I see Quellcode (64 Zeilen) udev.rules make his work but only this 3 nodes are created (demux0,dvr0 and net0). Wich modules are mandatory to load? I load in this order, mxl5005s.ko, de_dvb-core or vt-dvb-core, dvb-usb, dvb-usb-af90…

Zitat: „Originally posted by Cus2k yes friend Quellcode (1 Zeile)“ But this is to use the usbtuner from DE, in this post you can download usbtuner.c and a compiled usbtuner for vu 5.1 in this you can see: Quellcode (1 Zeile) so there is no parameter to execute, always use adapter1/frontend0. The matter here is to create /dev/ nodes to use the device. Regards

Hi, I've read all info you gave us and i'ts very hard to me but i'm still watching and making some probes, I'm running VTI 2.0 tryng to use an Avermedia 850. I think I understand the way udev works, in our case use the program parameter to add the device, the same way that look for dvb to add all node to adapter0 you say we must do the same with vt-dvb. So make udev.rules to look for vt-dvb devices and with printf make the echo with the name of the device and node that will be added. After loadi…

Thank you, I just received the e-mail, but is not yet in Download Database. Regards