Database Users

BusyBox Error

Im working with Andrizoid atm at seeing if we can get some progress on his Ubuntu project. Heres the issue.
Code:
busybox mount -o --bind ./dev/pts /data/local/ubuntu/dev/pts
mount: cannot read /etc/fstab: No such file or directory
In doing a little research I came across this
If there is no entry for /dev/fd0 in my fstab when I issue the command above, mount gets very confused because it doesn't know where to mount the floppy.
Click to expand...
Click to collapse
This come from http://www.tuxfiles.org/linuxhelp/fstab.html which gives a quick breakdown of what the etc/fstab file is. When i went exploring I couldnt find an etc/fstab
Code:
[B]
mount: cannot read /etc/fstab: No such file or directory
[/B]
The thing about Android though...there IS NO /ETC/FSTAB file because its become obsolete.
The init program directly mounts all filesystems and devices using either hard-coded file names or device names generated by probing the sysfs filesystem (thereby eliminating the need for a /etc/fstab file in Android). After device/system files are mounted, init reads /etc/init.rc and invokes the programs listed there (one of the first of which is the console shell).
Click to expand...
Click to collapse
EDIT: Conclusion
After bouncing some ideas around, I've come to the conclusion that it HAS to be a Busybox issue.
An Android specific variation of Busybox should take into account the fact that there isnt an etc/fstab file. The fact that these commands work on other phones leads me to think that its an Eris specific issue. If anyone remembers there were issues when using the Busybox available on the market on the Eris.
Looks like we need a Busybox update

es0tericcha0s said:
Or is there something else I can do?
Click to expand...
Click to collapse
Modify the mount command.
If the version of BusyBox is the Android version, report this issue (as a bug?). If it's the standard Linux BusyBox, the devs may not be interested. Or, if BusyBox is just calling the standard mount command, then it's not a BusyBox issue for them to worry about.

hallstevenson said:
Modify the mount command.
If the version of BusyBox is the Android version, report this issue (as a bug?). If it's the standard Linux BusyBox, the devs may not be interested. Or, if BusyBox is just calling the standard mount command, then it's not a BusyBox issue for them to worry about.
Click to expand...
Click to collapse
I'm using the Android Busybox, and those commands are being executed in an adb shell so I doubt that its calling the standard mount command-it should be calling the (hopefully) Android specific mount command. The things thats confusing me is that those same commands worked just fine for other phones. I dont see why I would get an error and others would have no issue with it?
EDIT:
And if you ave any recommendations for what I should modify the mount command to, let me know.

You mention a reference to /dev/fd0 but I'm 99.9% that's referring to the *nix mount command. The Android/BusyBox version should know better than to look for a floppy drive.
Where is BusyBox maintained ?
I did find a page about an Android ROM from Nov 2008 that mentions
- changed the "mount" symlink to be busybox's mount instead of toolbox's mount
- added an /etc/fstab file that busybox's mount can use, that lists the standard system partitions.
Click to expand...
Click to collapse
Is "mount" in fact an internal adb command ?

hallstevenson said:
You mention a reference to /dev/fd0 but I'm 99.9% that's referring to the *nix mount command. The Android/BusyBox version should know better than to look for a floppy drive.
Where is BusyBox maintained ?
I did find a page about an Android ROM from Nov 2008 that mentions Is "mount" in fact an internal adb command ?
Click to expand...
Click to collapse
The floppy drive reference was just from some background info I pulled on the etc/fstab file. I wasnt actually trying to mount a floppy disk
I have no idea where I would put in a bug report or anything. I know Stericson was the publisher of the BusyBox app thats avaiable on the market, but the one for the Eris is different anyways so idk if he could help.
Im not sure what you mean by your last statement, but mount is not a command that you can use in a shell on its own. You have to use busybox mount ...
If you can show me where you found that rom from I may be able to finish this. I was just talking to a buddy of mine about making my own /etc/fstab and slipping it in just so that the mount command would work. If theres already one put together then thats way less work for me

What I meant by referring to that info you found was that person couldn't have been talking about the Android version. I didn't think you were trying to mount a floppy.
You sure that there's no "adb mount" ? Look here, http://forum.xda-developers.com/showthread.php?t=517874. They refer to "adb shell mount".
Personally, I would just create an /etc/fstab file (I believe it can be empty) and see what happens.

hallstevenson said:
What I meant by referring to that info you found was that person couldn't have been talking about the Android version. I didn't think you were trying to mount a floppy.
You sure that there's no "adb mount" ? Look here, http://forum.xda-developers.com/showthread.php?t=517874. They refer to "adb shell mount".
Personally, I would just create an /etc/fstab file (I believe it can be empty) and see what happens.
Click to expand...
Click to collapse
well ive got an /ect/fstab file that i took from here http://www.android-devs.com/?p=152
Code:
# /etc/fstab: static file system information
#
# file system mount point type options dump pass
/dev/block/mmcblk0p2 / ext2 defaults 1 1
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /media/sdcard vfat defaults 0 0
But thats from a guide about debian on the N1 and the way they are doing it is much different from the method I'm using.
adb shell mount give the error that mount isnt found. it has to be called through busybox-at least in the instance that im using it in
Code:
busybox mount -o --bind /dev/pts /data/local/ubuntu/dev/pts

Linux chroot mount scripts

The actual creation of an arm linux chroot image is probably out here on teh internetz somewhere, but I can assist with my mounting shell script (which works).
My image is of a debian arm chroot, and the image filesystem is ext2 (a good idea for fewer writes. ie innately non-journaling), has been used extensively on fw DE .17 and I'm currently trying it out on WW .29 (thank you, miloj).
I would upload my debian img somewhere, but I've actually broken it somewhat (it works for my needs, but it's nonetheless a bit too hacked up to be reliable).
I've modified it somewhat for generalization, some of it is probably wrong and/or redundant, and it IS hackish and ugly, but it works for me (tm).
* the chroot image only need a root account (and probably bash installed, but it usually is)
* You need busybox installed.
* You need to upload your chroot image named linux.img to the internal sdcard in a folder named linux
A shell script to set things up is attached.
What you need to do:
push the install script and run it:
Code:
adb push installlinuxstuff.sh /data/local/
adb shell sh /data/local/installlinuxstuff.sh
Now you can (from adb shell or terminal emulator on device):
Code:
su -
/data/local/mnt/linux.sh
/data/local/mnt/notlinux.sh
Feel free to remove the install script at
/data/local/installlinuxstuff.sh
when you've got it up and running.
Alternative way to run the scripts from adb shell:
Code:
adb shell su -c /data/local/mnt/linux.sh
adb shell su -c /data/local/mnt/notlinux.sh
I usually symlink start and stop (in my case deb and undeb) shell scripts placed in /data/local/mnt in /system/bin (ie shell scripts with 'su -c /data/local/mnt/whatever.sh' in them) for easy start an stop from terminal emulator, and if you've gotten this far you may welcome the small advice. (in other words - don't do this unless you _really_ know what you're doing)

Debian ARMHF or ARMEL?
If you would uploaded it (good place is google drive , sharing as public, as there are no ads or bull**** and the download is extremely fast) I would love to try your image - after modifying your script so it can work on a UHS-1 class MicroSD I want to try running this off of (should give it a little more speed).

zamaditix said:
Debian ARMHF or ARMEL?
If you would uploaded it (good place is google drive , sharing as public, as there are no ads or bull**** and the download is extremely fast) I would love to try your image - after modifying your script so it can work on a UHS-1 class MicroSD I want to try running this off of (should give it a little more speed).
Click to expand...
Click to collapse
Armel (I use the same chroot installation on my phone in a smaller image file (with less stuff installed)). I've got loads of personal stuff all over it and besides - it's somewhat broken. I really don't want to try to fix it.
So I'm working on retracing my steps, creating a clean armhf ext2 image (debian wheezy base installation for now) and redo the mount script, but I can't make any promises on a release date.
Anyhu - there are loads of images (armel, at least) on teh internetz (BT5 and too many ubuntu, for instance).
Just check so our kernel can mount the filesystem.
Edit: if not you can just create a new image file with a filsystem that's mountable and copy the chroot files to it.

So the ideal image for this tablet is armhf? If I wanted to create a Gentoo image, I would go with armv7? I'm just not sure exactly which ARM architecture this tablet is.

EndlessDissent said:
So the ideal image for this tablet is armhf? If I wanted to create a Gentoo image, I would go with armv7? I'm just not sure exactly which ARM architecture this tablet is.
Click to expand...
Click to collapse
The CPU is the Tegra 3 if you want to google it and it is an ARMv7 w/ NEON extensions chip. ARMv7 specification requires hardware fp so naturally it is ARMhf.
Nice to hear, keep us updated on your progress. I'm currently running an armel copy of Ubuntu 12.04 but it has problems with some packages and others are armhf only.

When I run linux.sh, I get an error that /sdcard can't be mounted because it doesn't exist.
Code:
mount: mounting /sdcard on /data/local/mnt/linux/sdcard failed: No such file or directory
I also tried changing the script to mount /mnt/sdcard, but that didn't work either.

EndlessDissent said:
When I run linux.sh, I get an error that /sdcard can't be mounted because it doesn't exist.
Code:
mount: mounting /sdcard on /data/local/mnt/linux/sdcard failed: No such file or directory
I also tried changing the script to mount /mnt/sdcard, but that didn't work either.
Click to expand...
Click to collapse
Yes, it is somewhat hackish, like I wrote. My image has got an sdcard folder (/sdcard) inside of it where I mount /sdcard from android. (Ie chroot and mkdir /sdcard)

followed this:
http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-rooted-transformer-prime/
make sure you have busybox installed der. Or at least the cp command in /system/bin
works well on my TF300T, Yea its not native but im currently configuring it for kernel building ;-D

FlyingPoo said:
followed this:
http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-rooted-transformer-prime/
make sure you have busybox installed der. Or at least the cp command in /system/bin
works well on my TF300T, Yea its not native but im currently configuring it for kernel building ;-D
Click to expand...
Click to collapse
Why does the mount script remount a non-existing block device with an ancient (according to android) filesystem?
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Edit: I read all the scripts, and they all mount that crap. It's not made for transformers, and on the android device it's made for it leaves /system mounted rw after you've run it, and WHEN run (installed) it modifies too much in /system/bin
Code:
# At first it copies loads of crap to /system/bin, and then:
cd /system/bin/
chmod 4777 *
It's not even "hackish" - it's just... wrong...
Will loop1 work every mount?
Code:
mknod /dev/loop1 b 7 0
losetup /dev/block/loop1
I'm almost only asking, since this thread was supposed to be about scripts?

gasingvar said:
Yes, it is somewhat hackish, like I wrote. My image has got an sdcard folder (/sdcard) inside of it where I mount /sdcard from android. (Ie chroot and mkdir /sdcard)
Click to expand...
Click to collapse
Thanks. I created /sdcard, and it works almost perfectly now. However, mounting devpts at /dev/pts doesn't seem to work. I replaced that line with
Code:
mount --bind /dev $mnt/dev
and it seems to work fine. Is there anything wrong with my method?
/dev/void said:
Why does the mount script remount a non-existing block device with an ancient (according to android) filesystem?
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Edit: I read all the scripts, and they all mount that crap. It's not made for transformers, and on the android device it's made for it leaves /system mounted rw after you've run it, and WHEN run (installed) it modifies too much in /system/bin
Code:
# At first it copies loads of crap to /system/bin, and then:
cd /system/bin/
chmod 4777 *
It's not even "hackish" - it's just... wrong...
Will loop1 work every mount?
Code:
mknod /dev/loop1 b 7 0
losetup /dev/block/loop1
I'm almost only asking, since this thread was supposed to be about scripts?
Click to expand...
Click to collapse
I'm assuming you're talking about the link in the post you quoted, even though you seem to be referencing the OP's use of the word "hackish". The script in the OP doesn't do any of that stuff. It just creates a few directories in /data/local/mnt/ and writes the mount/unmount scripts, which themselves only un/mount appropriate directories for the tablet. As for your question, I'm not nearly experienced enough to answer it. Sorry.

EndlessDissent said:
Thanks. I created /sdcard, and it works almost perfectly now. However, mounting devpts at /dev/pts doesn't seem to work. I replaced that line with
Code:
mount --bind /dev $mnt/dev
and it seems to work fine. Is there anything wrong with my method?
Click to expand...
Click to collapse
AFAIK your mount seems to be more complete, ie more android hardware goodies accessable from the chroot environment. However - that means more things possibly going wrong (like writing to a device who's critical to the android environment).
Personally I'd try to find what "hardware goodies" and whatnot I'd need to get the chroot environment working optimally, and not mount ALL of /dev.
EndlessDissent said:
I'm assuming you're talking about the link in the post you quoted, even though you seem to be referencing the OP's use of the word "hackish". The script in the OP doesn't do any of that stuff. It just creates a few directories in /data/local/mnt/ and writes the mount/unmount scripts, which themselves only un/mount appropriate directories for the tablet. As for your question, I'm not nearly experienced enough to answer it. Sorry.
Click to expand...
Click to collapse
Yes, and the OP is very honest about his script(s) being "hackish", which I interpret to mean 'not optimal, possibly redundant but working', all of which it is (and I applaud the early release, since for instance I could get things rolling), but the ubuntu image installation and mounting scripts from the other poster ( whom I was addressing ) are plain faulty.

I am looking for a armhf build of ubuntu or debian that I can chroot (newer the better), if anyone knows of such a build that would be fantastic but if not does anyone know of an easy to follow guide to compile such a thing?

I found two pretty good guides. I mostly followed THIS ONE, but I found that it doesn't mount enough before "first boot", so what I did was follow the guide until the point where you move the image to the tablet. Then I ran the OP's installlinux.sh script, and then the mount script. However, the mount/unmount scripts need to be edited before using them. Comment out the sdcard line and probably the devpts line (mounting devpts didn't work; Bash complained that devpts didn't exist; I had to replace it with the line I mentioned a few posts above, but as /dev/void says, it could be problematic, so be careful). Mount the image, make the /sdcard directory, exit, unmount, and edit the scripts again to mount/unmount /sdcard.
Next time you enter the chroot, feel free to run the
Code:
sh /debootstrap/debootstrap --second-stage
command to build the image, and follow the linked guide until the next time it tells you to exit the session (NOTE: The second echo "whatever" > sources.list command is wrong; it should be echo "whatever" >> sources.list; Also, remember to replace "squeeze" with the appropriate Debian version, in my case, "testing"). Instead of exiting right after the apt-get update, I'd recommend playing around with the chroot and configuring whatever apps you install. You can just use the OP's scripts now and ignore the script in the linked guide.
When the guide I linked above gets to this line:
Code:
sudo debootstrap --verbose --arch armel --foreign squeeze /mnt/squeeze/ http://ftp.debian.org/debian
just replace armel with armhf, and if you want a testing image, replace squeeze with testing.
Sorry I'm not attaching my image. I made it gigantic (5GB), so I don't really have anywhere to store it, and you probably wouldn't want to download a file that big. Plus, it already has Openbox and a bunch of other things you probably don't want installed. I'm assuming you'd want GNOME or KDE instead.

[Q] How do I install parted command?

I'm trying to wipe and format a microSD card that I have plugged in via OTG and already have it wiped with this;
Code:
dd if=/dev/zero of=/dev/block/sda
Now I'm looking into how to recreate a MBR and partition table and it says to use the parted command, which I'm glad about as I'm familiar with the command from using Ubuntu but it's not installed and I can not find any instructions on how to get it. Can anyone explain how to install it? I know I could just plug the SD card into a computer and do it but I'm having fun doing all this on a tablet. Lol

Bump
Anyone?

I have got the same question, any other solutions?

This is the most complete information I have found yet, but it doesn't work. Either from me messing something up or it not being correct for the Nexus 7 being that it was made two years ago. http://www.droidforums.net/forum/htc-droid-eris/78650-internal-storage-partitions-screwed-up.html
I pushed all six files to /sbin/ with no errors and changed their permissions with no issues but I restart the tablet and none of the six files are in /sbin/

Just for the heck of it I extracted the six files to the SD card in the tablet, CD'd to it and used chmod 0755 on all six files then tried to run it and this is what I get.
Code:
[email protected]:/storage/emulated/legacy/folder # parted
sh: parted: not found
127|[email protected]:/storage/emulated/legacy/folder # ls
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
... how can you NOT find that?

herqulees said:
... how can you NOT find that?
Click to expand...
Click to collapse
Depending on how your PATH env var is set, the current directory might or might not be being searched for program load(s). So indicating the current directory explicitly with a leading "./" such as
$ ./parted
will certainly work (if a read & execute bit set on file, and the filesystem is not mounted -noexec ) .
But...
...if those files are dynamically linked rather than statically linked, and the appropriate link-libraries they reference come up missing during run-time linking it is possible to still see a "not found" message. Sort of a red-herring error message, but there you go.
I just looked in TWRP's /sbin (ramdisk) just now. Don't see parted in there.
[Edit] I do see the string "fdisk" inside the busybox executable though! - maybe boot into recovery and see what
busybox fdisk /dev/block/sda
gets you? (I suppose result depends on whether or not TWRP kernel plumbs the device into place.)
Perhaps the quickest solution is to simply use a PC and media reader to do the partitioning from a PC instead of the N7. You might even want to boot a "Live CD" version of Linux to get at the tools you need. (BTW, I think that Ubuntu's Live CD mounts a fuse FS over the top of the RO DVD/CD, so you can even download and install packages as needed).

I managed to get everything to work by doing this:
1. Using this app https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en I remounted /system as RW
2. Using the CyanogenMod File Manager I copied the parted file to /system/bin (from the root of the SD card)
3. Then using the File Manager still, go to the Properties of the parted file and go to Permissions and under R, W, and X put a check mark in the three boxes bellow each. (I don't know which ones it needs permissions for so I just give it permissions to everything, kinda frowned upon to do but I trust this program so...)
By doing this you can completely stay out of command line, but at the same time you're installing a command line program so you shouldn't be afraid of the command line in the first place. Lol.
Note: After this you can go to a terminal window and type su to get root access then type
Code:
parted /dev/block/sda
you will of opened your external memory card, now use parted as you would normally.

[Q] FUSE (Filesystem in Userspace) module for Nook Color? Compatibility, injection?

I'm surprised I couldn't find any real information or discussion on the FUSE module/fuse.ko module injection for the Nook Color.
It's a required component of programs, such as Cryptonite, to do on-the-fly mounting of file systems within an Android system, and also to be able to mount NTFS volumes additionally in a USB OTG scenario..
I've searched google, searched through the XDA threads and posts, and the only thing I found with any pertinent information regarding FUSE and the Nook Color was here-- and actually includes the fuse module in it, zipped and contains within the fuse.ko module to inject.
[14 Apr 2012][USER/DEV] USB Host Support & Development [CM7/CM9]
http://forum.xda-developers.com/showthread.php?t=1459892
(second post, attachment at bottom)
So can someone please give me the run down on the current status of FUSE within the kernels and roms currently existing on the Nook Color, must it be manually injected, are kernels set-up to properly use the module?
It seems easy enough to implement, but I'm no real developer, am I just missing something?
With regards to the fuse.ko module attachment in the above thread, I've downloaded the 'fuse.ko' module and placed it on the root of my sdcard, and attempted to load it in on my CM7 rom.
Just SU'd in terminal emulator, output was
# insmod /sdcard/fuse.ko
#
Click to expand...
Click to collapse
and also tried copy and pasting 'fuse.ko' from my sdcard to /system/lib/modules and doing an 'insmod /system/lib/modules/fuse.ko', and it just simply enters it in with a '#' after.
But that doesn't seem to be working. 'lsmod' doesn't output anything, the mount feature is still not working after testing, so it seems it wasn't actually injected properly.
Any suggestions, information someone can provide, would love to get the module inserted and mounting working properly.
Thanks!

Some more digging and experimenting I came across this post which explains similarities (with another android phone) not being able to do the same thing I'm doing, except within the replies there seems to be some basis for support for getting this up, as the terminal commands to check on the fuse module is outputting some commands.
http://code.google.com/p/cryptonite/issues/detail?id=17&can=1&q=fuse.ko
A member trying to provide support for the issue told the poster to input the following commands to get a more in-depth overview of why FUSE support was not working.
Thanks for the bug report. On a root terminal or adb root shell, what's the output of the following commands:
gunzip -c /proc/config.gz | grep CONFIG_FUSE_FS
losetup -f
ls -l -a /dev/fuse
ls -l -a /system/lib/modules
Click to expand...
Click to collapse
Now, when I attempt the above commands in my CM7.2, this is my output
$ su
# gunzip -c /proc/config.gz | grep CONFIG_FUSE_FS
gunzip: : No such file or directory​# CONFIG_FUSE_FS is not set​# losetup -f
/dev/block/loop1​# ls -l -a /dev/fuse
crw------- 1 root root 10, 229 Apr 7 22:53 /dev/fuse​# ls -l -a /system/lib/modules
drwxr-xr-x 2 root root 4096 Apr 7 22:18 .
drwxr-xr-x 2 root root 8192 Apr 7 07:52 ..
---xrwxr-x 1 system sdcard_rw 75046 Apr 7 22:18 fuse.ko​
Click to expand...
Click to collapse
So there seems to be SOMETHING there..
Hope this helps, any suggestions/input would be greatly appreciated!

echoedge said:
Some more digging and experimenting I came across this post which explains similarities (with another android phone) not being able to do the same thing I'm doing, except within the replies there seems to be some basis for support for getting this up, as the terminal commands to check on the fuse module is outputting some commands.
http://code.google.com/p/cryptonite/issues/detail?id=17&can=1&q=fuse.ko
A member trying to provide support for the issue told the poster to input the following commands to get a more in-depth overview of why FUSE support was not working.
Now, when I attempt the above commands in my CM7.2, this is my output
So there seems to be SOMETHING there..
Hope this helps, any suggestions/input would be greatly appreciated!
Click to expand...
Click to collapse
I don't know about fuse in the kernel, but CM10 /CM10.1 uses the fuse command to mount the embedded sdcards in emmc. Some devices like the HD/HD+ have the internal sdcard as just a part of /data so they need fuse to mount the internal SD. It is a command at /bin/sdcard. If you look at init.xxx.rc (where xxx is your device) in CM10 you will see how it is used. Then look at mount after boot and you will see the /dev/fuse mount. I'm not sure if it is actually used in encore.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
I don't know about fuse in the kernel, but CM10 /CM10.1 uses the fuse command to mount the embedded sdcards in emmc. Some devices like the HD/HD+ have the internal sdcard as just a part of /data so they need fuse to mount the internal SD. It is a command at /bin/sdcard. If you look at init.xxx.rc (where xxx is your device) in CM10 you will see how it is used. Then look at mount after boot and you will see the /dev/fuse mount. I'm not sure if it is actually used in encore.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
That's interesting, because the next thing I was wondering about was how to do this on CM10. I don't have enough technical knowledge of the deep file system and module system/actions to make clear judgment on this issue, if the above is the case (which I'm sure it is since I've been around long enough to know that you know your stuff), then I don't know why it's not working by default to mount file systems. Same program.. was going to try to inject it somehow, or at least check the command line feedback on it to perhaps get a clue. If I get a chance I'll post the response, unless someone has some knowledge on it that can help?
But yeah, backing up, apparently what I did WAS succesful. The fuse module was injected (CM7.2).
But it's not a default start-up module. I have to manually do a terminal emulation and input
modprobe fuse
Click to expand...
Click to collapse
And it is working fine :good:
So good deal, let's see what's up with this in CM10

OK, CM10 is a bit different, here's the run-down.
Again, these commands
gunzip -c /proc/config.gz | grep CONFIG_FUSE_FS
losetup -f
ls -l -a /dev/fuse
ls -l -a /system/lib/modules
Click to expand...
Click to collapse
The output (BEFORE doing an manual insmod)
$ su
# gunzip -c /proc/config.gz | grep CONFIG_FUSE_FS
# CONFIG_FUSE_FS is not set​# losetup -f
/dev/block/loop0​# ls -l -a /dev/fuse
/dev/fuse: No such file or directory​
Click to expand...
Click to collapse
also "modprobe fuse" outputs "module 'fuse' not found"
now downloading the fuse.ko file from the USB OTG thread and putting it on the sdcard and doing a
# insmod /sdcard/fuse.ko
insmod: init module 'sdcard/fuse.ko' failed (Exec format error)​
Click to expand...
Click to collapse
and then trying to place the 'fuse.ko' in the system/lib/modules, a "modprobe fuse" command now doesn't output 'modprobe: module 'fuse' not found', but
modprobe: 'fuse.ko': invalid module format
Click to expand...
Click to collapse
so it appears the 'fuse.ko' isn't compatible with CM10, only CM7/9 possibly?
But then again it looks like there is a version of the module FUSE already embedded in CM10, but it's of a specific variant which doesn't support the userbase filesystems?? There is no /dev/fuse, but doesn't
# gunzip -c /proc/config.gz | grep CONFIG_FUSE_FS
# CONFIG_FUSE_FS is not set​
Click to expand...
Click to collapse
imply that it is there-- just not configured to mount the file system with a program like cryptonite?
I've tried all I know to do right now, any direction in this? Would like to get this working on both roms for cross-compatibility purposes. Am hoping getting it to work in CM10 is just a small tweak away, but maybe not? Anyone with more knowledge than I can share advice on the workings of this within the CM10 system?
Thanks ​

leapinlar said:
I don't know about fuse in the kernel, but CM10 /CM10.1 uses the fuse command to mount the embedded sdcards in emmc. Some devices like the HD/HD+ have the internal sdcard as just a part of /data so they need fuse to mount the internal SD. It is a command at /bin/sdcard. If you look at init.xxx.rc (where xxx is your device) in CM10 you will see how it is used. Then look at mount after boot and you will see the /dev/fuse mount. I'm not sure if it is actually used in encore.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Yeah, I'm at a loss for what needs to be/could be done.
I don't understand the technicalities of what you're saying leapinlar, sorry, do you care to reiterate?
I'm not sure what you mean by "look at the mount after boot" and you will see /dev/fuse mount, what action is needed to do this?
Is there a fuse.ko in the CM10/CM10.1 file system? If so, where?
The one for CM7/CM9 is just incompatible I'm guessing, so it's saying invalid module format.
What needs to be done is to "modprobe fuse" to activate the module, or something like you were saying above to get it to recognize and make a pathway for /dev/fuse (can you explain again how to enable this?)
Thanks

echoedge said:
Yeah, I'm at a loss for what needs to be/could be done.
I don't understand the technicalities of what you're saying leapinlar, sorry, do you care to reiterate?
I'm not sure what you mean by "look at the mount after boot" and you will see /dev/fuse mount, what action is needed to do this?
Is there a fuse.ko in the CM10/CM10.1 file system? If so, where?
The one for CM7/CM9 is just incompatible I'm guessing, so it's saying invalid module format.
What needs to be done is to "modprobe fuse" to activate the module, or something like you were saying above to get it to recognize and make a pathway for /dev/fuse (can you explain again how to enable this?)
Thanks
Click to expand...
Click to collapse
Go to terminal emulator and type mount. It will display all of the devices mounted. Sometimes on some devices it shows a device /dev/fuse and its properties.
There is no fuse.ko as far as I know. What I was saying is there is a binary file (/system/bin/sdcard) that is invoked during startup to mount the internal sd card via fuse.
I have no clue whether that helps you with your problem or not, I was just telling you that fuse is sometimes used in CM10.
Sent from my Nook HD+ running CM10 on Hybrid SD

Ouya SD Card Mount Enable [SD Card Read FIX]

Lets start by saying i did not have anything to do with the making of this I'm just re-posting for the people who had it tough like me.
What i did was use Ouya Tool Box to root, su, busy box etc.
Installed ES file explorer, ES Task Man
Edited /system/etc/vold.fstab
--------------------------------------------
alynnafoxie Posts: 2Member
June 27 edited June 27 in General Development
This should be able to be done on any Ouya since they are all rooted, but you have to have root access.
This fix will give you full access to your USB flash drive as a "sd card". It will even be listed in the 'storage settings' and will be visible from Windows under the "Ouya Console" drive that pops up when it is connected.
First you must mount /system read-write. You can either use adb shell, or sideload "Android Terminal emulator" if you have a keyboard:
adb shell
mount -o remount,rw /system
After this you need to edit the file /system/etc/vold.fstab. There will be two lines at the end:
Change this:
dev_mount sdcard /storage/sdcard1 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2
dev_mount usbdrive /mnt/usbdrive auto /devices/platform/tegra-ehci.2/usb2
to this:
#dev_mount sdcard /storage/sdcard1 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2
dev_mount usbdrive /storage/sdcard1 auto /devices/platform/tegra-ehci.2/usb2
How does this work? Well, the first line, we comment out. It refers to a storage device on the tegra that is connected to nothing at all, basically the on chip SD/MMC that we have no slot to stick said MMC card to. The second line, we tell vold to detect the USB stick we boot with or insert, as a SD card. Really any storage device can be here (try it with a hard disk!) but in our case we want the first USB storage device to be here. In theory this hotplugs well, as I have tested removing it and reinserting it locally. It will look like an SD card to the Ouya. I am going to test moving an app to it and running it in a moment.
Really this file hack should not be necessary, the proper way to do this is editing init.rc and changing
export SECONDARY_STORAGE /storage/sdcard1
to
export SECONDARY_STORAGE /mnt/usbdrive
However /init.rc cannot be edited without modifying the bootloader, and since Ouya has no button to go into recovery yet, I am not willing to risk or even talk about editing /init.rc in your boot image.
Anyway, if anyone else wants to try this and confirm it works for them i'll watch this thread for a bit. Maybe the Ouya devs can incorporate it into a build, or just set SECONDARY_STORAGE in /init.rc right.
However the fix I just gave is easier because if you change SECONDARY_STORAGE you're gonna have to change every reference to /storage/sdcard1 down the line.
--Alynna
Post edited by alynnafoxie on June 27

good info thanks

Secondary storage
m03m1x said:
Lets start by saying i did not have anything to do with the making of this I'm just re-posting for the people who had it tough like me.
What i did was use Ouya Tool Box to root, su, busy box etc.
Installed ES file explorer, ES Task Man
Edited /system/etc/vold.fstab
--------------------------------------------
alynnafoxie Posts: 2Member
June 27 edited June 27 in General Development
This should be able to be done on any Ouya since they are all rooted, but you have to have root access.
This fix will give you full access to your USB flash drive as a "sd card". It will even be listed in the 'storage settings' and will be visible from Windows under the "Ouya Console" drive that pops up when it is connected.
First you must mount /system read-write. You can either use adb shell, or sideload "Android Terminal emulator" if you have a keyboard:
adb shell
mount -o remount,rw /system
After this you need to edit the file /system/etc/vold.fstab. There will be two lines at the end:
Change this:
dev_mount sdcard /storage/sdcard1 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2
dev_mount usbdrive /mnt/usbdrive auto /devices/platform/tegra-ehci.2/usb2
to this:
#dev_mount sdcard /storage/sdcard1 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2
dev_mount usbdrive /storage/sdcard1 auto /devices/platform/tegra-ehci.2/usb2
How does this work? Well, the first line, we comment out. It refers to a storage device on the tegra that is connected to nothing at all, basically the on chip SD/MMC that we have no slot to stick said MMC card to. The second line, we tell vold to detect the USB stick we boot with or insert, as a SD card. Really any storage device can be here (try it with a hard disk!) but in our case we want the first USB storage device to be here. In theory this hotplugs well, as I have tested removing it and reinserting it locally. It will look like an SD card to the Ouya. I am going to test moving an app to it and running it in a moment.
Really this file hack should not be necessary, the proper way to do this is editing init.rc and changing
export SECONDARY_STORAGE /storage/sdcard1
to
export SECONDARY_STORAGE /mnt/usbdrive
However /init.rc cannot be edited without modifying the bootloader, and since Ouya has no button to go into recovery yet, I am not willing to risk or even talk about editing /init.rc in your boot image.
Anyway, if anyone else wants to try this and confirm it works for them i'll watch this thread for a bit. Maybe the Ouya devs can incorporate it into a build, or just set SECONDARY_STORAGE in /init.rc right.
However the fix I just gave is easier because if you change SECONDARY_STORAGE you're gonna have to change every reference to /storage/sdcard1 down the line.
--Alynna
Post edited by alynnafoxie on June 27
Click to expand...
Click to collapse
FYI, they might have included it in an upgraded, since my usb cards gets mounted to: /mnt/usbdrive, but there also seams to be a symbolic link in the root folder, which is quite nice.

TobiasFP said:
FYI, they might have included it in an upgraded, since my usb cards gets mounted to: /mnt/usbdrive, but there also seams to be a symbolic link in the root folder, which is quite nice.
Click to expand...
Click to collapse
sadly I I did not like the way that was working. So I found this method. It shows you in the storage menu that you have something mounted (SD it says) It feels more natural and I don't know if its a placebo effect but things are faster and xfering faster

Help?
I feel like I'm doing everything right...
[email protected]~/android/platform-tools $ sudo adb devices
[sudo] password for joshua_munoz:
List of devices attached
015d4a8245200a00 device
[email protected]~/android/platform-tools $ adb shell
[email protected]:/$ su
[email protected]:/# mount -o rw,remount /system
[email protected]:/# exit
[email protected]:/$ exit
[email protected]~/android/platform-tools $ adb push vold.fstab /system/etc/vold.fstab
failed to copy 'vold.fstab' to '/system/etc/vold.fstab': Permission denied
[email protected]PadT420S~/android/platform-tools $ sudo adb push vold.fstab /system/etc/vold.fstab
failed to copy 'vold.fstab' to '/system/etc/vold.fstab': Permission denied
Can you discern what I might be doing wrong? I'm trying to push the edited vold.fstab file back into /system/etc (since that's where I adb pulled it from to edit it), but CANNOT get the dang thing to be rw for the life of me. As such, I haven't been able to see if this fix works, and my 32GB USB drive shows up as an empty, blank sdcard1 when I plug it in.

!!!! please don't use this method now. I tried it a few days ago and it did not work after a Ouya Update. sorry. i should have mentioned.
HashBrownJM said:
I feel like I'm doing everything right...
[email protected]~/android/platform-tools $ sudo adb devices
[sudo] password for joshua_munoz:
List of devices attached
015d4a8245200a00 device
[email protected]~/android/platform-tools $ adb shell
[email protected]:/$ su
[email protected]:/# mount -o rw,remount /system
[email protected]:/# exit
[email protected]:/$ exit
[email protected]~/android/platform-tools $ adb push vold.fstab /system/etc/vold.fstab
failed to copy 'vold.fstab' to '/system/etc/vold.fstab': Permission denied
[email protected]~/android/platform-tools $ sudo adb push vold.fstab /system/etc/vold.fstab
failed to copy 'vold.fstab' to '/system/etc/vold.fstab': Permission denied
Can you discern what I might be doing wrong? I'm trying to push the edited vold.fstab file back into /system/etc (since that's where I adb pulled it from to edit it), but CANNOT get the dang thing to be rw for the life of me. As such, I haven't been able to see if this fix works, and my 32GB USB drive shows up as an empty, blank sdcard1 when I plug it in.
Click to expand...
Click to collapse

Well, shoot. Then I guess I'm up a creek in terms of getting my USB drive to read?

HashBrownJM said:
Well, shoot. Then I guess I'm up a creek in terms of getting my USB drive to read?
Click to expand...
Click to collapse
no it should be auto mounting as /mnt/usbdrive
install ES file manager after your Root and get SuperUser.
i use the on ouya root.
http://forum.xda-developers.com/showthread.php?t=2387507

m03m1x said:
no it should be auto mounting as /mnt/usbdrive
install ES file manager after your Root and get SuperUser.
i use the on ouya root.
http://forum.xda-developers.com/showthread.php?t=2387507
Click to expand...
Click to collapse
ES definitely shows the USB drive as a USB drive, which as a result, has made ePSXe (installed from the Play Store) able to find my PSX ROMs. RetroArch still says sdcard0 and sdcard1, and on sdcard1 (the USB drive), it shows as empty.
What to do?

HashBrownJM said:
ES definitely shows the USB drive as a USB drive, which as a result, has made ePSXe (installed from the Play Store) able to find my PSX ROMs. RetroArch still says sdcard0 and sdcard1, and on sdcard1 (the USB drive), it shows as empty.
What to do?
Click to expand...
Click to collapse
i dont know what else to tell you homie. when my ouya turns on i look to see if the LED indicator is blinking "access" behaviour. If it doesn't it didn't read it. If you don't have a LED sorry. check /mnt/usbdrive thats what i use now. all my emus etc. can see it.

m03m1x said:
i dont know what else to tell you homie. when my ouya turns on i look to see if the LED indicator is blinking "access" behaviour. If it doesn't it didn't read it. If you don't have a LED sorry. check /mnt/usbdrive thats what i use now. all my emus etc. can see it.
Click to expand...
Click to collapse
It's definitely being read. Has a little blinking LED. If ES and ePSXe are reading it, I know it's working. Just gotta figure out why RetroArch won't read it, or find some other emulators that will.
What emulators are you using?

If you got the PSX emulator to read your Roms already then it sounds like it is the Retroarch messing up. I would recommend loading individual emulators anyways.