Hi All,
This is my first thread on this forum. Please help in resolving an error that I am facing. I could compile and link successfully franco kernel after downloading the source from franco's github!!
The only problem I face is with wifi. It displays error in the wi-fi option!! This is some what similar to what we used to get in the initial version of gingerbread kernel what Franco had made earlier!! I get the same error even with the stock GB source code of LG or with paulo's kernel source!!! Strange!!!!
The wifi driver(bcm4325) seems to be same except for some tweaks to the original GB source(In the case of Franco's)!! In either case, I am getting the error. The only difference I see is that of the compiler option -Ofast(Optimization option) was used by Franco while since I updated to the latest version of gcc, I do not get the -Ofast option!! So it uses the -Os option instead!!
Error is(logcat):
D/WifiService( 1726): setWifiEnabledBlocking : Country code is COM
E/WifiService( 1726): Failed to load Wi-Fi driver.
Same compiling options were used to compile both zImage and modules?? What could be wrong here? I am not sure what could be wrong here!!! Can anybody help me on this??
Thanks in advace.
I get this on sense too
(but I replaced all that Android wifi stuff,so on Sense,its wierd )
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
I dont use -Ofast anymore. Did you manually add wireless.ko to lib/modules from your compiled kernel?
Sent from my u8800 using XDA Premium App
dr.notor said:
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
Click to expand...
Click to collapse
I tried it thro' the init.rc too. I dont any other ways to do insmod!!
But it failed even on that account!!
franciscofranco said:
I dont use -Ofast anymore. Did you manually add wireless.ko to lib/modules from your compiled kernel?
Sent from my u8800 using XDA Premium App
Click to expand...
Click to collapse
Yup franco. I copied to modules and then signed it with command:
"java -classpath testsign.jar testsign port.zip signed-port.zip"
I really can't understand why this is getting failed as the same compile options were used for both zImage and wireless.ko!! Rest all works fine except the wifi error!!! The idea i think is as long as all the executables are of same signature, then it should work fine, right?? I am confused on what could be the problem!!!
dr.notor said:
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
Click to expand...
Click to collapse
Today I will try with other compile options, either O1, O2.... etc.
Strange thing is that I face this problem with all other available kernels also!! Like for ex., original GB source from LG, paulo's kernel!! All of it!!
shashi_hv said:
I tried it thro' the init.rc too. I dont any other ways to do insmod!!
But it failed even on that account!!
Click to expand...
Click to collapse
Uh, I do not understand a word.
Code:
$ su
# busybox insmod /system/lib/modules/wireless.ko
What is the output of the above.
dr.notor said:
Uh, I do not understand a word.
Code:
$ su
# busybox insmod /system/lib/modules/wireless.ko
What is the output of the above.
Click to expand...
Click to collapse
Weird!!! Though I see the file being there thro' file manager, I get the error as "No such file or directory"!!
I was telling that I tried to insert this same command even in the init.rc file at the boot option!!
shashi_hv said:
Weird!!! Though I see the file being there thro' file manager, I get the error as "No such file or directory"!!
I was telling that I tried to insert this same command even in the init.rc file at the boot option!!
Click to expand...
Click to collapse
You have been already told that you need to manually add /system/lib/modules with the ones you want (such as wireless.ko or tun.ko or cifs.ko) to the ZIP you are flashing.
Flashing zImage only will not flash the modules!!!!
As for your file manager, I recommend this as a "file manager"
Code:
# ls -l /system/lib/modules
-rw-r--r-- 1 0 0 19948 Aug 1 2008 tun.ko
-rw-r--r-- 1 0 0 191854 Aug 1 2008 wireless.ko
dr.notor said:
You have been already told that you need to manually add /system/lib/modules with the ones you want (such as wireless.ko or tun.ko or cifs.ko) to the ZIP you are flashing.
Flashing zImage only will not flash the modules!!!!
As for your file manager, I recommend this as a "file manager"
Code:
# ls -l /system/lib/modules
-rw-r--r-- 1 0 0 19948 Aug 1 2008 tun.ko
-rw-r--r-- 1 0 0 191854 Aug 1 2008 wireless.ko
Click to expand...
Click to collapse
I know that notor!!!
I copied the tun.ko and wireless.ko to the appropriate folder and built the zip file which i flashed!!
The problem is very weird. I see the file wireless.ko if I browse thro' file manager. Even when i press tab in busybox, wireless.ko gets auto populated or even the ls command lists it!!
It is much more weird that if I tried to do insmode ....../tun.ko, i get the error as 'exec format error' but a 'no such file' for the wireless.ko!! Though I flashed both these of these!!
You know, go wipe the files in /system/lib/modules and flash your kernel and modules from the SAME KERNEL you have compiled.
Also, it is insmod, not insmode and generally if you are posting something, copy and paste the exact output of a command instead of telling us stories about what the output says.
Yup thats what i was thinking too.. i would wipe and try copying it once again.
Definitely i would have shown you the screen shots.. but i am not in a position to grab those and paste it here, as i am in office right now.. but the point is i understand some of linux system and familiar wirh it!!
I tried to create and flash the zip the standard way thats available on net and it did not worked!! Thats the point!! So wanted to know am i missing anything!!
Sent from my LG Optimus One P500 using XDA Premium App
Well, things like 'exec format error' clearly suggest that you flashed some weird corrupt junk...
dr.notor said:
Well, things like 'exec format error' clearly suggest that you flashed some weird corrupt junk...
Click to expand...
Click to collapse
I tried this!!!
1. su
2. rm -f /system/lib/modules/wireless.ko
3. rm -f /system/lib/modules/tun.ko
Now the files were not there in the directory. Flashed the same zip file which I used earlier and found the wireless.ko and tun.ko in the same path!!! But still the problem prevails!!
Just to confirm once again that I indeed copied the compiled wireless.ko and tun.ko and built the zip file!! No problem in that!!!
Why do not you try to do insmod of any existing file in the modules path and report what error you get?? I think even you should get the same error even in your phone too!! I tried this command on an already existing libra.ko in the same path and got the same error!!!
for a few weeks i has compiled my kernel with optimizations -O3 and got "no such device" when tried to insmod the wifi module ...
possibly the wifi module gets corrupted when the kernel is to much optimized...
andy572 said:
for a few weeks i has compiled my kernel with optimizations -O3 and got "no such device" when tried to insmod the wifi module ...
possibly the wifi module gets corrupted when the kernel is to much optimized...
Click to expand...
Click to collapse
Yeah. Just leave the thing alone. There is basically nothing you will optimize by subverting various crazy -O3 -fzomgoptimized -fflying-phone flags to kernel compile. Leave the stock CFLAGS stuff alone.
dr.notor said:
Yeah. Just leave the thing alone. There is basically nothing you will optimize by subverting various crazy -O3 -fzomgoptimized -fflying-phone flags to kernel compile. Leave the stock CFLAGS stuff alone.
Click to expand...
Click to collapse
On a different note, can anybody tell me who will load the wireless.ko and tun.ko at boot time? I mean is there any kind of scripts like the init.rc or any other *.sh scripts under /system/etc?
I tried to see in the init.qcom.wifi.sh script, but its based on the property 'wlan.driver.status'!! I dont see this property under getprop command, but added one using setprop, but no success!!!
Suggestion: restore the stock init **** and leave it alone. There is absolutely no need to mess with that to get WiFi working on any ROM. Others, like tun.ko, you need to load manually via initscript or whatever. Go fix your kernel compile and it will just work.
Related
Hi XDA Community!
I know some Custom ROMS includes shell scripts that are executed at the boot.
Now, I'm cooking one, already made the script, just searching for a way to autostart it at boot.
I'm trying to add my script to some /etc/init.d folder but in my cooked ROM there is just a system/etc folder, extracted from an update.zip without any init.d
HowTo?
[edit] Checked Cyan's ROM and I see /system/etc folder with content, and init.d is there.
Jack_R1 said:
On Cyanogen, for example, /etc is mounted to /system/etc on start.
Click to expand...
Click to collapse
Yes. In my rom, it is also mounted.
But init.d does not exists.
And I don't even know if it works that way on Android...
HowTo?
Edited my post above.
Jack_R1 said:
Edited my post above.
Click to expand...
Click to collapse
Thx for your time.
Yes I also did.
In fact, I search for the answer quite some time before posting.
I see this folder in Cyan's ROM.
But it still do not tell me how to make my script run at boot:
- do I have to create init.d?
- will my script be under names conventions (like 01xx 02xx 03xx)
- will it loads automaticaly by Android 2.2 ?
some progress:
i found etc/init* in ramdisk!
trying a few things on that and report
-------------------------------------
Sent via the XDA Tapatalk App
On CM, try putting your script in /system/bin then adding it's name to /system/etc/init.d/20userinit.
There is also an app in the market called autostart which runs a script at /data/opt/autostart.sh which you have to create. I use it because it's the first way I found to execute scripts at startup and I just stuck with it, so I've never used the CM script, but I think that's the proper place to add it.
Unfortunately, I haven't seen a way to run things at startup on froyo yet. When someone figures that one out, please report.
fubaya said:
Unfortunately, I haven't seen a way to run things at startup on froyo yet. When someone figures that one out, please report.
Click to expand...
Click to collapse
I'm trying Autostart (root), the app you told me, but it seems you also say that you found no way to do such thing on FroYo...
Do you mean autostart (the app) do NOT work on FroYo?
leonnib4 said:
I'm trying Autostart (root), the app you told me, but it seems you also say that you found no way to do such thing on FroYo...
Do you mean autostart (the app) do NOT work on FroYo?
Click to expand...
Click to collapse
Yes, autostart doesn't seem to work on Froyo. You talked about both Cyan and Froyo, which one are you using?
fubaya said:
Yes, autostart doesn't seem to work on Froyo. You talked about both Cyan and Froyo, which one are you using?
Click to expand...
Click to collapse
I said I was aware Cyan was using bootscripts, but Im using stock rooted froyo.
In fact, Im cooking one.
Found it!
In Cyanogen sources:
in boot.img
in ramdisk
init.rc
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
dsixda should include in its rom kitchen
Emulating the effect of the Autostart app
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/
ddvo said:
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/
Click to expand...
Click to collapse
Did you create the 20autostart folder? Are you performing this with Autostart running? I'm trying to have insmod tun.ko perform at each boot so my VPN works without having to open TerminalE and doing it at command line on the phone.
connexion2005 said:
Did you create the 20autostart folder?
Click to expand...
Click to collapse
20autostart is a shell script file, not a folder. All scripts in the directory /etc/init.d are executed on boot in alphanumerical order.
connexion2005 said:
Are you performing this with Autostart running?
Click to expand...
Click to collapse
Autostart is non-functional at least on my HTC Desire with rooted 2.2 (Froyo); you can uninstall it, while the method I explained above is guaranteed to work.
ddvo said:
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/
Click to expand...
Click to collapse
I've tried it but it doesn't work for me.
there is a rcS file which seems to run everything in the init.d folder
i made a file "20autostart" file containing the script you posted.
I didn't have an "opt" folder in "/data", created one.
Created "autostart.sh, containing "swapon /data/swap256"(script works with gscript).
But it isn't run and no autostart.out or .err file is created after reboot. Seems like it isn't run at all..
There is an "sh" file in the "/bin" folder so it should be able to call that function.
I have no experience what so ever with this but i've done all the steps necessary.
Never mind, created an other solution!
Hi NRG, I just checked again with my system, and there it still works.
Maybe because it's a specific custom ROM version of Android 2.2?
Mine is called "Eight Minutes to Eight O´Clock A.M." from android.modaco.com/content/htc-desire-desire-modaco-com/312051/oclock-custom-rom/
Maybe you used the wrong shell path: /bin/sh instead of /system/bin/sh.
Which other solution have you found meanwhile?
Tasker can run things at boot if anyone needs another way to do it. You can run shell commands with Tasker and the Locale Execute Plugin.
/data/local/tmp
Hi, you are looking for - /data/local
chmod 755
Hey Folks, mybe one of you can give me a hint.
I extracted the boot.img saved before with oneclick-recovery for zte v9 light using mytools from another post (unpack-bootimg.pl etc) and everything worked. i am using Ubuntu Linux on my pc. After i added the quoted lines i repacked it, using the repack script from that mytools and flashed it using
Code:
flash_image boot /sdcard/boot.img
reboot
Well- thats what bricked my phone. Dont worry, got the official zte flashing tool, a clean android 2.2 and unbricked it after a few days of worrying... But what am i making wrong to get the init.d contents get executed on boot?
leonnib4 said:
Found it!
In Cyanogen sources:
in boot.img
in ramdisk
init.rc
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
dsixda should include in its rom kitchen
Click to expand...
Click to collapse
Because Motorola hasn't provided the .config file for the Droid X yet, I used 'make mapphone_defconfig' and then enabled config_tun in the resulting .config file. That .config file was used to generate tun.ko - it's currently functioning and working on my droid X phone. Since it's not the .config file used by Motorola there may be some oddities, unexpected problems or your house may explode if you use it. I don't take any responsibility for anything that happens if you use this - use it at your own risk.
It hasn't bricked my phone and it's been working without a problem, but your mileage may vary.
Attached is the .config file that was used as well as the tun.ko file
Enjoy
Noob Warning:
What does this do for us ?
pman219 said:
What does this do for us ?
Click to expand...
Click to collapse
This lets you run OpenVPN or http://code.google.com/p/get-a-robot-vpnc/ (allows you to connect to cisco, nortel or freeswan IPSEC servers
Would I need the config file or is that just for compiling other kernel modules for the DX?
The config file would really only be used to compile other modules. All you need is the tun.ko file
I placed this in /dev/net/tun/tun.ko
then I ran chmod 777 /dev/net/tun/tun.ko
then I ran insmod /dev/net/tun/tun.ko
I then tried the Gui app (get-a-robot-vpnc) and it fails immediately when trying to connect - am I missing something?
I'm new to android.
kris7778 said:
I placed this in /dev/net/tun/tun.ko
then I ran chmod 777 /dev/net/tun/tun.ko
then I ran insmod /dev/net/tun/tun.ko
I then tried the Gui app (get-a-robot-vpnc) and it fails immediately when trying to connect - am I missing something?
I'm new to android.
Click to expand...
Click to collapse
Hi,
You should place tun.ko in /sdcard/ or /system/lib/modules (if you have it mounted /system read,write)... I use the app "openvpn settings" - in that program when you go into the settings and choose "advanced" you can click the checkbox next to "load tun kernel module", then in "TUN module settings" set "load module using" to "insmod" and type in the proper path to tun.ko in the "path to tun module" area.
You may need to, as root (su) run:
mkdir /dev/net
busybox mknod /dev/net/tun char 10 100
ln -s /dev/net/tun /dev/tun
Best of luck
Do I need to set the path to the openvpn binary also? (Not sure where this gets installed)
And... what is required in the config file.
This is all I use on linux:
IPSec gateway X.X.X.X
IPSec ID mygroupid
IPSec secret mysecret
thanks!
kris7778 said:
Do I need to set the path to the openvpn binary also? (Not sure where this gets installed)
And... what is required in the config file.
This is all I use on linux:
IPSec gateway X.X.X.X
IPSec ID mygroupid
IPSec secret mysecret
thanks!
Click to expand...
Click to collapse
Hi Chris,
I think that would be something that the get-a-robot-vpnc folks will have to help you out with.
I got your tun.ko working with the commandline vpnc. It appears that get-a-robot-vpnc is just not quite calling vpnc how i need it to.
Thanks for your help.
Sent from my DROIDX using XDA App
You can pull .config from /proc/config.gz
mrozzeh said:
You can pull .config from /proc/config.gz
Click to expand...
Click to collapse
While that file apparently exists on other phones, it does not on the droid x - atleast not the last time that i checked
anyone know how you would recompile this for the .32 kernel
Invalid module format
I get an invalid module format error while trying to load this module. I am running Froyo if that makes any difference. THX
Can someone post instructions.....
HI,
Can someone post some instruction how to get the vpn connections working in Droid X? Please...
I can help with a donation.... $$
SOGJC said:
HI,
Can someone post some instruction how to get the vpn connections working in Droid X? Please...
I can help with a donation.... $$
Click to expand...
Click to collapse
I would love to get some instructions as well. I have a corp 5520 with group authentication that would be very nice to be able to connect to. Anyone successfully connect with the DroidX?
Anyone?
Still cannot get this to work on my DroidX - currently on 2.3.340 stock.
mab2,
As you were able to get this file, is there any way you are able to dump a file so I can use to get EVDO internet settings stick on QPST?
VPN Connections
Are you rooted?
I will post instructions if needed, I connect to a Cisco ASA and use VPN Connections - works like a charm.
Reply
rhyzar said:
Anyone?
Still cannot get this to work on my DroidX - currently on 2.3.340 stock.
Click to expand...
Click to collapse
Are you rooted?
I will post instructions if needed, I connect to a Cisco ASA and use VPN Connections - works like a charm.
We now have a working cifs.ko and nls_utf.ko. I was able to mount my win7 shares using cifs_manager and stream a few movies using mvideoplayer from the mounted share.
My initial problem seemed to be that I used the android ndk toolchain and the nook kernel is compiled with the codeSourcery toolchain.
After I re-compiled using the codeSourcery toolchain everything works (at least for now)
For those who want to try this.
Download the cifs.ko and nls_utf8.ko modules.
http://dl.dropbox.com/u/16190398/Nook Color 1.0/cifs.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.0/nls_utf8.ko
Mount /system as read write and create a directory under /system/lib called modules. Copy the cifs.ko and nls_utf8.ko modules under this directory.
Type the following from your windows or linux console
adb shell
#mount -o remount,rw /dev/block/mmcblk0p5 /system
#su
#cd /system/lib
#mkdir modules
#exit
#exit
Now you are back in your windows or linux command prompt
adb push cifs.ko /system/lib/modules
adb push nls_utf8.ko /system/lib/modules
adb shell
#su
#insmod /system/lib/modules/cifs.ko
#insmod /system/lib/modules/nls_utf8.ko
if everything went well you should see no errors.
#lsmod
(THis should give you a list of running modules)
You should see something like
nls_utf8 1856 0 - Live 0xbf153000
cifs 240060 0 - Live 0xbf113000
#exit
#exit
Download cifs_manager from the android market and follow the instructions from
http://forum.xda-developers.com/showthread.php?t=756158
If you have Astro file manager installed then tapping on the mounted share from cifs_manager will automatically launch Astro and list the folder/files under that share.
BTW, you can copy the modules anywhere you like even under /sdcard/modules but the default path used by cifs_manager is /system/lib/modules. You can edit the path from cifs manager to point to the location of your cifs.ko module.
---- 05/06/2011 Update ------------
New version of cifs.ko, slow-work.ko for the 1.2 update. This is for kernel version 2.6.32.9
Note, cifs.ko requires some symbols from slow-work.ko so you will need to load slow-work.ko first. If you use cifs-manager, under advanced settings
you can check load modules at startup via insmod and put the path to multiple modules for e.g /system/lib/modules/slow-work.ko:/system/lib/modules/cifs.ko.
Everything seems to be working fine for me. Let me know if you run into issues.
http://dl.dropbox.com/u/16190398/Nook Color 1.2/slow-work.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.2/cifs.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.2/nls_utf8.ko
Alright! This is fantastic! I can even play my SNES roms over wifi. Thanks for sharing.
The only issue I have noticed is that you need to run the insmod commands every time you reboot the device, and I reboot a lot. For now I'm just using gScript to run the 2 commands whenever I need, but it would be great to have them run when the program starts. I know you're just sharing and this has been mentioned in the app thread, just wanted to make my observations known.
Edit: Found a nifty toggle in the settings of cifs managaer that runs the insmod command at startup. I guess I should look before I complain...
any chance you can provide your build environment, so that the rest of us can work on hacking the kernel.
thetoady said:
any chance you can provide your build environment, so that the rest of us can work on hacking the kernel.
Click to expand...
Click to collapse
Setting up the environment is ridiculously easy esp if you have access to a linux box. There is a very well documented wiki page which outlines the process of building your own custom kernel for the nook color.
http://nookdevs.com/NookColor:_Build_the_Original_Kernel
I downloaded the codesourcery tool chain and did the minimum install as I did not care about the IDE and added the path to my environment. THat was about it. Everything else I followed the wiki page.
Here is my .config file if you like. When you run "make menuconfig" you can choose to load an alternate config file instead of the default. Just put this .config (after renaming it to .config_myconfig or something) under your distro/kernel directory.
Let me know if you need anything specific and I'll try to help. I had to add the .txt extension to the config file for xda upload but you can rename it to anything you want.
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
Seems more like an error in configuring CIFS_Manager.
If the module doesnt load you get a different error from Cifs_Manager
"No such device".
Can you try using adb shell and use insmod to load the module manually.
CHeck with lsmod if the module is loaded.
Can you post you cifs_manager screen for the share that you are trying to mount.
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
I'm sure you noticed that there's an error in dascud instructions... the 2nd insmod command has a filename typo..
its should read
HTML:
#insmod /system/lib/modules/nls_utf8.ko
dascud.. thanks a ton... as mentioned in my previous post can you please make the change in your post
madrascafe said:
dascud.. thanks a ton... as mentioned in my previous post can you please make the change in your post
Click to expand...
Click to collapse
Done. Were you able to mount the CIFS shares ?
dascud said:
Done. Were you able to mount the CIFS shares ?
Click to expand...
Click to collapse
Yes. No problem at all. I even opened files from root explored & played some music. Thank you for this
firstly thanks dascud's great work! Awesome!
I found a problem when mount with option iocharset=utf8, cifsmanager report below error message then failed to mount
Mounting the share has failed with an error.
mount: Can not access a needed share library
When I remove iocharset=utf8, mount success but I failed to access any folder including non-western characters.
ctos said:
firstly thanks dascud's great work! Awesome!
I found a problem when mount with option iocharset=utf8, cifsmanager report below error message then failed to mount
Mounting the share has failed with an error.
mount: Can not access a needed share library
When I remove iocharset=utf8, mount success but I failed to access any folder including non-western characters.
Click to expand...
Click to collapse
CIfs_manager only loads the cifs.ko modules. You will need to load nls_utf8.ko manually or using a script to display non-western character set. I think you can use something like gscript for the purpose.
I've followed the instructions, but trying to launch the cifsmanager I get
Application not installed on Device
from reading the FAQ on the cifsmanager page, it says its a problem with the launcher. is this because I've updated the NC to 1.01? thanks
dascud said:
CIfs_manager only loads the cifs.ko modules. You will need to load nls_utf8.ko manually or using a script to display non-western character set. I think you can use something like gscript for the purpose.
Click to expand...
Click to collapse
gscript works for me. thanks a lot!
Sent from my LogicPD Zoom2 using XDA App
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
I got this when I put the computer name in the share path. I switched to using IP address instead and it worked.
Hi,
Thanks for the files. I didn't follow the steps in the instructions because there is an easier way. Like mention before, ClifsManager only need cifs.ko.
I basically just copy cifs.ko to my sd card. In the CM setting, just change path to
/sdcard/cifs.ko
Setting up shares is easy too, share path is your ip/<sharefolder>, mount point /sdcard/<foldername> and your user/pwd. This worked with Windows 7.
ClifsManager is definitely one of the must have on the NC.
Is there any chance of getting an tun.ko driver built so that this can be used in conjunction with OpenVPN?
Thanks!
smlong426 said:
Is there any chance of getting an tun.ko driver built so that this can be used in conjunction with OpenVPN?
Thanks!
Click to expand...
Click to collapse
Here you go.
http://forum.xda-developers.com/showthread.php?t=889736
Will this, or any software for that matter, allow me to openly share one or more folders on the NC device (SD card), so I can access that NC shared directory from a windows box and copy files back and forth?
KryptoNyte39 said:
Will this, or any software for that matter, allow me to openly share one or more folders on the NC device (SD card), so I can access that NC shared directory from a windows box and copy files back and forth?
Click to expand...
Click to collapse
What you need is a Samba server for Nook. Looks like this has already been accomplished. Maybe you can post a howto once you get this working.
http://forum.xda-developers.com/showpost.php?p=8239139&postcount=128
I am trying to compile a clean AOSP ROM for my O2X, there is a few things I am having trouble with.
1. What is the significance of overriding the build prop with the following:
Code:
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=lge_star BUILD_ID=FRG83G BUILD_DISPLAY_ID=GRJ22 BUILD_FINGERPRINT=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys PRIVATE_BUILD_DESC="star-user 2.2.2 FRG83G 2ED2ADCFFC release-keys"
Clearly its used for something, else CM7 wouldn't be doing it.
2. When I try to boot the compiled system (using either CM or EternityProject kernel), it simply stops at the LG logo, no logcat, no dmsg, nothing and after a while it reboots. What could I be missing?
I am using the init.rc from the CM7 p990 source, do I need some extra modules for it to boot? (I have added busybox and bash)
Tips on how I could debug the issue would be appreciated (any additional logs?).
I've managed to get froyo building and running from source (I used the nvidia branch and merged 2.2.2 myself)
I just used the stock LG kernel though
Got almost everything but gave up because it was a huge pain in the ass
You dont really need those
Are you trying to create the device tree yourself?
fallout0 said:
I've managed to get froyo building and running from source (I used the nvidia branch and merged 2.2.2 myself)
I just used the stock LG kernel though
Got almost everything but gave up because it was a huge pain in the ass
You dont really need those
Are you trying to create the device tree yourself?
Click to expand...
Click to collapse
Yea I am trying to create a device tree that will make AOSP compile and run. Its compiling just fine and it uses bits from the CyanogenMod device tree. The problem is that it wont run, it gives me no logcat output at all.
Here is the p990.mk:
http://pastebin.com/SxUZZDau
The boardconfig and proprietaries are identical to CM7. (Merged star-common and p990 configs since I have no use for p999)
Try using the stock kernel + init.rc - that is just use the boot image from modaco for now
You should be able to adb shell into it and check dmesg to see what's going on
fallout0 said:
Try using the stock kernel + init.rc - that is just use the boot image from modaco for now
You should be able to adb shell into it and check dmesg to see what's going on
Click to expand...
Click to collapse
Same problem, no dmsg or logcat.
Im gonna start from scratch now
About your first question (and sb correct me if I'm wrong), its just for market stuff to show up on the device, whilst making About>System display GRJ22 etc. etc.
L10nH34Rt said:
About your first question (and sb correct me if I'm wrong), its just for market stuff to show up on the device, whilst making About>System display GRJ22 etc. etc.
Click to expand...
Click to collapse
That would make it rather useless
KernelCrap said:
Same problem, no dmsg or logcat.
Im gonna start from scratch now
Click to expand...
Click to collapse
Also you HAVE to check out the code from nvidia because the tegra2 has a bug in the CPU and their code base has a work around for it if you don't the dynamic linker doesn't work and you'll find every executable will segfault ( when you flash your system image from recovery try and go into system/bin and run. /ls for example)
In the board configuration you'll notice a HAVE_TRGRA something or rather line
check out bionic that's where that fix is applied
fallout0 said:
Also you HAVE to check out the code from nvidia because the tegra2 has a bug in the CPU and their code base has a work around for it if you don't the dynamic linker doesn't work and you'll find every executable will segfault ( when you flash your system image from recovery try and go into system/bin and run. /ls for example)
In the board configuration you'll notice a HAVE_TRGRA something or rather line
check out bionic that's where that fix is applied
Click to expand...
Click to collapse
Im gonna try to build using the 2.3.3 gingerbread-tegra source from nvidia
EDIT: Same problem, when running something i get "Segmentation fault". I am using the gingerbread-tegra source from nvidia :S
I have the following in BoardConfig.mk:
TARGET_HAVE_TEGRA_ERRATA_657451 := true
Busybox is working fine though :/
Shouldn't the source from nvidia allow me to execute the compiled binaries without giving segmentation fault?
The funny thing is that busybox is working, and I can access dmesg through busybox.
KernelCrap said:
That would make it rather useless
Click to expand...
Click to collapse
It wouldn't if you couldn't access the market now would it?
L10nH34Rt said:
It wouldn't if you couldn't access the market now would it?
Click to expand...
Click to collapse
I'd rather have it boot atm.
Still same problem even though I have moved to the gingerbread-tegra source
IMHO its a wasted effort. You'll have trouble getting camera/hdmi etc.etc to work... Just clone CM repo and cherry-pick from there.
L10nH34Rt said:
IMHO its a wasted effort. You'll have trouble getting camera/hdmi etc.etc to work... Just clone CM repo and cherry-pick from there.
Click to expand...
Click to collapse
For starters I don't care about camera or hdmi, I want a clean AOSP rom - CM is great, but it includes too many extra features for my taste.
Are you sure you checked out the tegra branch from nvidia? gingerbread-tegra?
I could only get froyo to boot myself - gingerbread would crash inside surfaceflinger with the froyo graphics libraries. I think the cygonenmod guys had access to leaked gingerbread libraries.
Hi guys, where i can find sources from nvidia ? I only found the kernel git...
Thank's
fallout0 said:
Are you sure you checked out the tegra branch from nvidia? gingerbread-tegra?
I could only get froyo to boot myself - gingerbread would crash inside surfaceflinger with the froyo graphics libraries. I think the cygonenmod guys had access to leaked gingerbread libraries.
Click to expand...
Click to collapse
I am sure and I am using the leaked libraries too. Anything else i can try?
Sent from my Optimus 2X using XDA App
If all the executables are seg faulting then you won't even get to logcat and the shell won't run unfortunately.
Try this...
find all the blocks of code in the source that have the #ifdef HAVE_TEGRA..ERRATA
and remove them
That way you'll definitely know that its compiling that section of the code. That has to work
fallout0 said:
If all the executables are seg faulting then you won't even get to logcat and the shell won't run unfortunately.
Try this...
find all the blocks of code in the source that have the #ifdef HAVE_TEGRA..ERRATA
and remove them
That way you'll definitely know that its compiling that section of the code. That has to work
Click to expand...
Click to collapse
Will try that once I get home later today
I commented it out the following places:
Code:
./bionic/libc/Android.mk:497: ifeq ($(TARGET_HAVE_TEGRA_ERRATA_657451),true)
./bionic/linker/Android.mk:46:ifeq ($(TARGET_HAVE_TEGRA_ERRATA_657451),true)
Still not booting, now the error is (from logcat):
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
But /system/bin/sh does exists, with the following permissions (also tried with chmod 777):
Code:
-rwxr-xr-x 1 root shell 82840 sh
If I do adb shell when in recovery and executes the binary files, they all seg fault (except for busybox) :/
Here is my BoardConfig.mk:
http://pastebin.com/ZsmJp0v1
Note: The information below is quite dated. If you are interested in watching TV on Android without root with the RTL-SDR dongles check out Aerial TV on XDA.
--------
Ok guys, I am proud to announce that I was able to run a DVB-T tuner on my Nexus 7
If your kernel is 3.1.10-g52027f9 and your dongle is RTL2832U based
If you have a rooted Nexus 7 with kernel 3.1.10-g52027f9 and a RTL2832U based DVB-T dongle, then you can also have your dongle up and running in a matter of minutes. Here are the steps:
Download http://dl.dropbox.com/u/24106229/NexusDvb.rar
Install droidtv.apk from the rar (you can also find it at https://github.com/chrulri/droidtv)
Get a Terminal emulator and cd to the folder where you have extracted the rar. Type in:
su
sh startdvb
Make sure that all of the files and folders inside /dev/dvb have highest permissions.
Start DroidTV and enjoy!!!
Different dongle, kernel 3.1.10-g52027f9
If you have the same kernel and a dongle that has its drivers built in the kernel according to http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices , then you can download this rar file - http://dl.dropbox.com/u/24106229/all-modules.rar (Last updated 20 Aug 22:22 GMT). Those are all of the kernel modules I compiled. You may be able to find your usb driver there.
Compiling kernel modules
If you don't have the same kernel or a dongle is not supported, you will need to get the kernel source and compile the modules yourself. Here's how you do that.
Make sure you are running Linux and have make and git already installed
Download dvbn7comp and put it into a new directory. Make sure dvbn7comp is executable by running chmod +x dvbn7comp inside the folder
Invoke the script like this ./dvbn7comp <kernel_version>. For example if you want to have the modules compiled for 3.1.10-g05b777c, you would run ./dvbn7comp 3.1.10-g05b777c
Wait - it may take a while. Usually about 15 minutes depending on your network and CPU speed.
After the script finishes running, the .ko files would be put in a directory called output_3.1.10-g05b777c
That's it!
Note: The script will download the kernel source and the toolchain and it will attempt to find the commit that contains the required kernel version. Then it will configure the kernel for DVB-T support and will compile the modules and copy them to the output folder. If you run the script again and the sources are already present, it will not download them again, so any subsequent runs of the script would be faster!
Patching the precompiled binaries [NEW]
phamthanhnam said:
For those who have another kernel version, you don't need to recompile dvb modules. If your kernel version is not in git revisions, you will just fail with 'fatal: ambiguous argument '3.1.10-xxxxxxxx': unknown revision or path not in the working tree'. Fortunately, there's a much faster and much simpler way to get dvb modules for your kernel version. You don't need git, make, toolchain, kernel source...
Nearly every Android kernel for Nexus 7 is based on 3.1.10 linux kernel (because of nvidia's closed source driver for graphics card), so kernel version for your Nexus 7 will be always 3.1.10-xxxxxxxx.
You can get directly precompiled binary modules (aka *.ko files) at post #1 and patch them for your kernel version:
Code:
perl -pi -e 's/3.1.10-g52027f9/3.1.10-xxxxxxxx/g' *.ko
Alternaties: Get precompiled binary modules at post #80 (more complete than modules from post #1) and patch them:
Code:
perl -pi -e 's/3.1.10-g22b4fcd/3.1.10-xxxxxxxx/g' *.ko
Alternaties 2: Post #129, the same way:
Code:
perl -pi -e 's/3.1.10-g05b777c/3.1.10-xxxxxxxx/g' *.ko
Basically this command replaces 'magic version' in *.ko files. Version mismatch will prevent insmod with an 'exec format error'.
Replace xxxxxxxx by your kernel-version, for example if your kernel version is 3.1.10-g30c5396, use:
Code:
perl -pi -e 's/3.1.10-g52027f9/3.1.10-g30c5396/g' *.ko
That's it!
More info: This way works with Cyanogen Mod kernels/ROMs!!!
Click to expand...
Click to collapse
How to modify the startdvb script
Code:
echo "Starting DVB support"
insmod dvb-core.ko # core support for DVB
insmod dvb-pll.ko # I am not sure if this is even needed
insmod rc-core.ko # Support for remote control, some drivers won't load otherwise
insmod dvb-usb.ko # Support for usb tuners
insmod dvb-usb-***** # Add here your driver. If more than one needed, add another line
# if firmware is needed, make sure the firmware is in the right folder, it should be /lib/firmware, but I'm not 100% sure
# Also some devices won't need the steps below
echo "Waiting for device"
sleep 5
cd /
mkdir /dev/dvb
mkdir /dev/dvb/adapter0
cd /dev/dvb/adapter0
ln -s /dev/dvb0.frontend0 frontend0
ln -s /dev/dvb0.demux0 demux0
ln -s /dev/dvb0.dvr0 dvr0
ln -s /dev/dvb0.dvr0 dvr0.ts
chmod -R 777 /dev/dvb* # The original script doesn't have it, but try adding a -R before 777 might ease things a bit
echo "DONE!"
Troubleshooting
If any error message occurs, type in dmesg in the terminal. This will give more information why something failed.
How do I know if I'm successful
To check whether you have insmoded the kernels right and after connecting the device whether it has been discovered, use dmesg and look for message similar to "Found DVB device xxx in warm state".
I got it running!!!
If you got it running, please do share with us! It seems like there's a lot of fiddling for some devices to be done so any information will prove invaluable for somebody!!!
NOTE: I don't have the time to support this thread any more, sorry if I am not responding to it! All of the directions above are still valid and working! Browse the comments, you might find that someone has compiled the correct modules for your device/kernel or you might ask someone to do it for you! If you want any of the information above to be edited, please PM me!
Where to get the DVB tuner
Hi,
Thanks for posting. it is very interesting.
can you post where did you buy the tuner from and the price?
the only one i could find with RTL2832U is priced at 27$ from ebay.
How can i compile the kernel modules for a different device?
thanks.
Very cool!
Could a similar technique could be used for ATSC here in the U.S.?
I actually have compiled all of the drivers that come with the Linux kernel as well
You can get them from here - http://dl.dropbox.com/u/24106229/all-modules.rar
If your device is listed as compatible somewhere here - http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices then you may be lucky You just need to know which kernel module to load with insmod (see the startdvb script to see how to do it).
If it's not there or you have a different kernel version, you will need to follow https://source.android.com/source/building-kernels.html . Except for you only need to build the modules, and you need to fiddle around with the Makefiles in order to force some of the components (like the dvb-usb.ko) to be compiled as modules. Good luck!
As far as the tuner I am using, it's http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=120958257586 this one. I actually got it for another purpose (http://sdr.osmocom.org/trac/wiki/rtl-sdr), which if I have the time I can try to build an app to bring it to the Android as well
another question
Thanks for the quick reply!
I couldn't find the right *.ko file in the modules you attached (it is supposed to be af9005 and af9015, and for my other dvb-t - IT9135)
Could i bother you to upload these, since i have no idea how to compile them.
I tried using af9013.ko that you attached but with no success, most likely because i had to use af9005 instead.
I added insmod af9013.ko to your script, attached is a screenshot from my emulator:
Thanks again. Your help is much appreciated!
another question
double post by mistake
Hi, I was wondering about this a few weeks ago.. great to see it working.. do you know if the Sony Play TV tuner would work? I have one of those...
Cheers,
Mick
martintzvetomirov said:
I actually have compiled all of the drivers that come with the Linux kernel as well
You can get them from here - http://dl.dropbox.com/u/24106229/all-modules.rar
If your device is listed as compatible somewhere here - http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices then you may be lucky You just need to know which kernel module to load with insmod (see the startdvb script to see how to do it).
If it's not there or you have a different kernel version, you will need to follow https://source.android.com/source/building-kernels.html . Except for you only need to build the modules, and you need to fiddle around with the Makefiles in order to force some of the components (like the dvb-usb.ko) to be compiled as modules. Good luck!
As far as the tuner I am using, it's http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=120958257586 this one. I actually got it for another purpose (http://sdr.osmocom.org/trac/wiki/rtl-sdr), which if I have the time I can try to build an app to bring it to the Android as well
Click to expand...
Click to collapse
---------- Post added at 09:37 AM ---------- Previous post was at 08:49 AM ----------
Here is the driver i need... i assume i need to be able to produce a .ko file some way for it?
http://linuxtv.org/wiki/index.php/Sony_PlayTV_dual_tuner_DVB-T#Drivers
aspletec this
Hi.
In the file Martin attached with all the modules there is a module for you DVB-T, it's called dib0070.ko
Try this one.
micks_address said:
Hi, I was wondering about this a few weeks ago.. great to see it working.. do you know if the Sony Play TV tuner would work? I have one of those...
Cheers,
Mick
---------- Post added at 09:37 AM ---------- Previous post was at 08:49 AM ----------
Here is the driver i need... i assume i need to be able to produce a .ko file some way for it?
Click to expand...
Click to collapse
Thanks, once i copy it to the folder with the startdvb file.. what other steps do i need?
lionsh said:
Hi.
In the file Martin attached with all the modules there is a module for you DVB-T, it's called dib0070.ko
Try this one.
Click to expand...
Click to collapse
you need to update the startdvb script to inclue ismode yourdriver.ko
micks_address said:
Thanks, once i copy it to the folder with the startdvb file.. what other steps do i need?
Click to expand...
Click to collapse
I edited the startdvb file to reference the dib0070.ko but i get init failed.. i wonder doesn the nexus have enough power to power the tuner via USB?
Cheers,
Mick
lionsh said:
Hi.
In the file Martin attached with all the modules there is a module for you DVB-T, it's called dib0070.ko
Try this one.
Click to expand...
Click to collapse
micks_address said:
Thanks, once i copy it to the folder with the startdvb file.. what other steps do i need?
Click to expand...
Click to collapse
You need to add the line 'insmod dib0070.ko' to startdvb.
You will probably also need to copy the 'dvb-usb-dib0700-1.20.fw' firmware file from that link you posted earlier into /etc/firmware.
OK guys, my bad! I didn't originally submit all of the files. Please, redownload again - http://dl.dropbox.com/u/24106229/all-modules.rar
I didn't compile the usb drivers, the ones that you would actually need Now everything should be there.
lionsh said:
Thanks for the quick reply!
I couldn't find the right *.ko file in the modules you attached (it is supposed to be af9005 and af9015, and for my other dvb-t - IT9135)
Could i bother you to upload these, since i have no idea how to compile them.
Click to expand...
Click to collapse
You will need dvb-usb-af9005.ko and possibly dvb-usb-af9005-remote.ko
micks_address said:
Hi, I was wondering about this a few weeks ago.. great to see it working.. do you know if the Sony Play TV tuner would work? I have one of those...
Click to expand...
Click to collapse
You will need dvb-usb-dib0700.ko and the firmware from the web page you pointed me at.
micks_address said:
I edited the startdvb file to reference the dib0070.ko but i get init failed.. i wonder doesn the nexus have enough power to power the tuner via USB?
Click to expand...
Click to collapse
It was able to properly power my tuner without external power but surely this won't be the case with all of them. That can't cause the init to fail though! Use dmesg to get more info on why this has happened.
lionsh said:
you need to update the startdvb script to inclue ismode yourdriver.ko
Click to expand...
Click to collapse
Yes, that's right. So here's how to do it
Code:
echo "Starting DVB support"
insmod dvb-core.ko # core support for DVB
insmod dvb-pll.ko # I am not sure if this is even needed
insmod rc-core.ko # Support for remote control, some drivers won't load otherwise
insmod dvb-usb.ko # Support for usb tuners
insmod ***** # Add here your driver. If more than one needed, add another line
# if firmware is needed, make sure the firmware is in the right folder, it should be /lib/firmware, but I'm not 100% sure
# Also some devices won't need the steps below
echo "Waiting for device"
sleep 5
cd /
mkdir /dev/dvb
mkdir /dev/dvb/adapter0
cd /dev/dvb/adapter0
ln -s /dev/dvb0.frontend0 frontend0
ln -s /dev/dvb0.demux0 demux0
ln -s /dev/dvb0.dvr0 dvr0
ln -s /dev/dvb0.dvr0 dvr0.ts
chmod -R 777 /dev/dvb* # The original script doesn't have it, but try adding a -R before 777 might ease things a bit
echo "DONE!"
Hope this helps!
If any error message occur, type in dmesg in the terminal. This will give more information why something failed. Also to check whether you have insmoded the kernels right and after connecting the device it has been discovered, use dmesg again and look for message similar to "Found DVB device xxx in warm state"
Hi Martin,
first of all many thanks!
i used 9005,9005-remote and 9015 ko files and updated the script as follow:
Code:
echo "Starting DVB support"
insmod dvb-core.ko
insmod dvb-pll.ko
insmod rc-core.ko
insmod dvb-usb.ko
insmod dvb-usb-af9005.ko
insmod dvb-usb-af9005-remote.ko
insmod dvb-usb-af9015.ko
echo "Waiting for device"
sleep 5
cd /
mkdir /dev/dvb
mkdir /dev/dvb/adapter0
cd /dev/dvb/adapter0
ln -s /dev/dvb0.frontend0 frontend0
ln -s /dev/dvb0.demux0 demux0
ln -s /dev/dvb0.dvr0 dvr0
ln -s /dev/dvb0.dvr0 dvr0.ts
chmod -R 777 /dev/dvb*
echo "DONE!"
I receive several errors.
first i get 9015.ko file not found, i'm attaching screen shot with ls that clearly lists the file (WTF?!)
and *dvr0.ts file is also written as no such file/dir.
I even copied the .fw files for 9005 and 9015 to etc/firmware
can you take a look ,i must be missing something stupid.
also, is there a dvb-usb-IT9135.ko file?
many thanks for your contribution.
I created the files :
frontend0
demux0
dvr0
dvr0.ts
in /dev/dvb/adapter0 and now i don't get an error on running sh startdvb (except on *9015.ko being not found)
when i open droid tv and select DVB-T and some country using dvb-t i get an error of unable to determine frontend
so something still missing/wrong.
UPDATE
using dmesg i saw an error for init 9015.ko - Unknown symbol af9013_attach (err 0)
maybe the compilation of this driver was not right, since it is 9015 and not 9013?
I do hope that it's the lack og 9015.ko which is keeping me from watching DVB-T. If I had the dvb-usb-IT9135.ko file i could try a different DVB-T tuner.
Loving the progress on this, for me dtv isn't what I'm looking for I would love to see a working live video input displayed on my nexus for a project I'm working on using a usb composite video in Interface the type you use to rip vhs to the computer, I'm guessing and hoping the solution is pretty much the same? Any advise and help on this please?
Thanks
Great work on this, so far I've managed to get my DVB tuner properly configured and connected!
The only issue is Droid TV seems very unstable... Are there any alternatives?
I get reboots when scanning for channels. Might try recompiling a newer version of w_scan when I get a minute.
The channels I manually added only have a signal of 20% with no picture. The signal is fine when the tuner is connected to my PC though.
Maybe the Nexus doesn't give it enough power?
Hi,
Can you state which module do you use for your DVB-T tuner?
Psych0Chimp said:
Great work on this, so far I've managed to get my DVB tuner properly configured and connected!
The only issue is Droid TV seems very unstable... Are there any alternatives?
I get reboots when scanning for channels. Might try recompiling a newer version of w_scan when I get a minute.
The channels I manually added only have a signal of 20% with no picture. The signal is fine when the tuner is connected to my PC though.
Maybe the Nexus doesn't give it enough power?
Click to expand...
Click to collapse
lionsh said:
I created the files :
frontend0
demux0
dvr0
dvr0.ts
in /dev/dvb/adapter0 and now i don't get an error on running sh startdvb (except on *9015.ko being not found)
when i open droid tv and select DVB-T and some country using dvb-t i get an error of unable to determine frontend
so something still missing/wrong.
UPDATE
using dmesg i saw an error for init 9015.ko - Unknown symbol af9013_attach (err 0)
maybe the compilation of this driver was not right, since it is 9015 and not 9013?
I do hope that it's the lack og 9015.ko which is keeping me from watching DVB-T. If I had the dvb-usb-IT9135.ko file i could try a different DVB-T tuner.
Click to expand...
Click to collapse
I have an A-Link dongle that seems to be running Afatech inside. Among the things you have done, I also attached and insmodded af9013.ko and got my receiver mounted in warm state and its actually scanning the channels in DroidTV as we speak. (No luck on the first try).
I have dvb-usb-af9015, 9005, 9005-remote, af9013 and the af9015 firmware (in the etc/firmware folder).
These seemed to do the trick.
that is so strange, i tried all these combinations, including af9013.ko with no luck.
did you get an error on af9015 like i did?
i have copied the firmware also. did you d\l it from http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices#DVB-T_USB_Devices?
when you ran startddvb script did you receive any errors? I get an error that the files in /dev/dvb/adapter0 are missing.
only when i create the files manually it passes, but then i can't initialize droid tv.
which kernel version do you use? i have 3.1.10 g52027f9
can you upload the files+script that you used?
Sikki said:
I have an A-Link dongle that seems to be running Afatech inside. Among the things you have done, I also attached and insmodded af9013.ko and got my receiver mounted in warm state and its actually scanning the channels in DroidTV as we speak. (No luck on the first try).
I have dvb-usb-af9015, 9005, 9005-remote, af9013 and the af9015 firmware (in the etc/firmware folder).
These seemed to do the trick.
Click to expand...
Click to collapse