I just followed this article to run ubuntu on my nexus s with CM7 running on it.
but each time I typing "bootubuntu"
I got this error:
mount: mounting /dev/loop1 on /data/local/ubuntu failed: Invalid argument
This error should happen when executing this line in bootubuntu:
mount -t ext2 /dev/block/loop1 /data/local/ubuntu
Any ideas ?
Are you sure that the kernel you are using supports the ext2 filesystem and loopback device?
Last lines of "dmesg" command might be helpful (if it exists).
how-to-install-ubuntu-on-your-android
This is the article I followed.
I'm not sure whether CM7 support ext2 and loop device, but I see somewhere people said they run ubuntu on CM7 successfully, that's why I post this thread and hope someone can confirm it and show me the steps.
Or let me know your experience on how to run Ubuntu on nexus s.
I like the busybox way to run ubuntu, means if I run a native ubuntu, I can't use my phone feature anymore.
If you read this: http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
Just a few lines into the text there is this paragraph:
For example, G2 Phone and Nexus One both come with loop device support so there’s no need for us to compile a new kernel for it but for others, you may have to.
Click to expand...
Click to collapse
I don't know whether the cm7 kernel kernel supports loop either, but there are many kernels floating around this forum. Maybe one of them does.
Thanks man.
Finally I figure this out. When I got this phone, the seller had already pre-installed a rooted CM7 and busybox. That may cause the problem.
After I re-install the busybox with the latest version, it works.
So CM7 and Nexus S are good to run Ubuntu.
Thanks for taking your time once again.
Related
I'm trying to build a new version of Apps2SD (version 2.6). I'm trying to get this version compatible with EXT4. I have resurrected my Darktremor Kernel (for those of you who don't know what that is...which is probably almost everyone...this is a kernel I built when the Hero source came out), which has EXT4 support.
I have set my ext partition to be EXT4.
The problem I'm having is, if I use the following command:
mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sd
I get the following errors:
During boot: Invalid argument
In ADB shell: No such device
I've tried using -t ext4, but I just get "No such device".
What am I doing wrong here? I've search all over XDA and the Internet. I see Roms that have EXT4 in them, but nobody talks about how to manually mount one (I can find all sorts of information about EXT3, but it appears the attitude with EXT4 is "it just works.")
Thanks.
tkirton said:
What am I doing wrong here? I've search all over XDA and the Internet. I see Roms that have EXT4 in them, but nobody talks about how to manually mount one (I can find all sorts of information about EXT3, but it appears the attitude with EXT4 is "it just works.")
Thanks.
Click to expand...
Click to collapse
I wish I could help, but I haven't messed around with the kernel or even EXT4... hmm, maybe it's time for me to start! You have any specific tutorials you'd recommend tkirton?
pseudoremora said:
I wish I could help, but I haven't messed around with the kernel or even EXT4... hmm, maybe it's time for me to start! You have any specific tutorials you'd recommend tkirton?
Click to expand...
Click to collapse
I have a guide on how to compile your own kernel. The same guide is one of the threads in XDA, but I know how hard it is sometimes to search for something (hence why I'm asking about EXT4)
http://www.darktremor.com/kernels.html
See if that helps as a starting document.
Sorry that I having nothing useful to offer on this subject. However, am I assuming correctly that current recovery images would support an EXT4 when doing Nandroid backups for A2SD users?
Ceger
tkirton said:
I have a guide on how to compile your own kernel. The same guide is one of the threads in XDA, but I know how hard it is sometimes to search for something (hence why I'm asking about EXT4)
http://www.darktremor.com/kernels.html
See if that helps as a starting document.
Click to expand...
Click to collapse
****, I probably should have searched, I'm sure I would have found it. Thanks though, definitely going to take a look at this!
Ceger said:
Sorry that I having nothing useful to offer on this subject. However, am I assuming correctly that current recovery images would support an EXT4 when doing Nandroid backups for A2SD users?
Ceger
Click to expand...
Click to collapse
Honestly I never tried to backup or restore on an EXT4 drive. I'm sure it will work, but I'm suspecting there's issues with the kernel source. I never had a reason to go to EXT4 (EXT3 suited my needs just fine and there aren't a lot of Roms that support EXT4).
tkirton said:
Honestly I never tried to backup or restore on an EXT4 drive. I'm sure it will work, but I'm suspecting there's issues with the kernel source. I never had a reason to go to EXT4 (EXT3 suited my needs just fine and there aren't a lot of Roms that support EXT4).
Click to expand...
Click to collapse
I'll ask Toast and Fresh as their Dev ROM supports EXT4, so they should know if Nandroid backs that up or not... I suppose.
Ceger
Ceger said:
I'll ask Toast and Fresh as their Dev ROM supports EXT4, so they should know if Nandroid backs that up or not... I suppose.
Ceger
Click to expand...
Click to collapse
I'm not doubting it does...Amon_RA stated in several threads that it does. But that kernel and the one used to boot are completely different. The problem I'm running into is the one for boot (the 1.5 kernel, or version 2.6.27 of the kernel). It won't activate there, although there is an entry called /dev/block/mmcblk0p2 (so the kernel does see something...it just won't mount).
Maybe the issue is busybox. I'll see if I can find busybox on the recovery kernel and port it.
I was thinking it could be because .27 uses ext4-dev. I've seen a gang load of ext4 patches for .27 I used the rename patch in my kernel. But it seems not to work. When testing it I thought it did work. As a2sd in our init.d was seeming to be working and I had all my apps. But after everyone was saying they couldn't get it to work, I'm thinking I may need to try another patch. But yeah I'm not sure what the issue is. Maybe we can contact cyanogen or amon on this as I know they get it to work somehow.
toastcfh said:
I was thinking it could be because .27 uses ext4-dev. I've seen a gang load of ext4 patches for .27 I used the rename patch in my kernel. But it seems not to work. When testing it I thought it did work. As a2sd in our init.d was seeming to be working and I had all my apps. But after everyone was saying they couldn't get it to work, I'm thinking I may need to try another patch. But yeah I'm not sure what the issue is. Maybe we can contact cyanogen or amon on this as I know they get it to work somehow.
Click to expand...
Click to collapse
I'm coming up with the same conclusion...the ext4dev drivers don't appear to work. They load up (I'm getting that from a device dump), but they won't mount. Apparently, it won't mount in recovery, either.
I'm wondering if I grab a 1.6 or better source if I can recompile the part for ext4 inside the rest of the Hero 1.5 source. If I remember correctly with Linux compiling, as long as I have the correct dependencies, I should be able to compile it.
While browsing thru the forums earlier..i remembered a thread where a ported version of debian could run on the g1 using vnc viewer...i tried messing with the vibrant..but it seems its doesnt have ext2 as one of the kernel drivers..or at least it fails to mount it..As u all are aware..this phone has crazy hardware..given size and weight.the hardware is more than capable...maybe we can get a working port of debian or another slimmed down version of linux to run on this phone..ie puppy or dsl....what i was thinking was maybe making an update.zip with a referenced .img file so we can boot to linux via recovery vs using vnc viewer..Not sure if this is a shot in the dark..any insight greatly appreciated ...Bless up!
The stock kernel does have ext2 and ext3 drivers. However, it doesn't mount those partitions by default. Check the dev forum for the userinit enabler zip. You could then use a userinit script to mount an ext partition.
Note that ext4 is NOT supported by default, so you will need to reformat if you have that.
Ubuntu has already been installed on android phones
http://nexusonehacks.net/nexus-one-hacks/ubuntu-on-nexus-one-android/
I personally do not see a huge benefit running a fully fledged linux os on the phone, but everyone has their own use and purpose.
I'd be down for Debian
If we ever got this running on our vibrants, I'd be so dang happy. I would love to try out GIMP
I've tried most of the kernels on this forum, though I haven't found one that "Linux Installer" plays nice with. Each time I try it greets me with a messages about the kernel not supporting LOOP features, and a lack of EXT2 or EXT3 support . Anybody know of a kernel or anything I can do to enable these?
Thanks!
I'm not sure how well it would work, but for ext2/3 you could compile just the module then, assuming thats all it needs, try using insmod to load it into kernel space
vaderj said:
I'm not sure how well it would work, but for ext2/3 you could compile just the module then, assuming thats all it needs, try using insmod to load it into kernel space
Click to expand...
Click to collapse
Not saying that you didn't know what I was talking about, but just so that everybody is on the same page;
http://www.androlib.com/android.application.com-galoula-linuxinstall-tFjz.aspx
I suppose I could do that to try to enable ext2 or 3, but any idea what LOOP is?
http://forum.xda-developers.com/showthread.php?p=16961006
3.3 is out. Please update, and contact me by email if any trouble. [email protected]
Galoula made a huge update; I did all translations and debug. New tutorial, new quick installation guide.
Loop is a feature of Linux kernel; the symbole name you need to activate when you rebuild kernel is:
CONFIG_BLK_DEV_LOOP=y
As of today, most ROM now support it.
Hi all
can't post in the dev forum so i'm posting here instead. I have installed insanitycm009 and i love it so far, much faster than the previous insanity rom (none cm one) but i'm having some problems with random reboots.
I believe that it may have something to do with my filesystem as i was previously running ext4 on the last insanity rom. i loaded the ext4 manager app i have and it is unable to help me as i don't have a cf-root kernel installed. i am running glitch kernel v10.
ext4 manager shows my filesystems as follows:
/system = yaffs2
/dbdata = unknown
/data = unknown
/cache = yaffs2
as you can see the os is unable to identify the filesystems so i think this is the cause for the reboots. How can i fix this?
insanity cm is based on cyanogenmod 7
this is a custom built rom from the google sources that has nothing to do with other custom roms that are usually based on Samsung roms.
cm7 and miui and of course insanity cm need another type of kernel that is built to support a rom built in that fashion. the filesystem is also handled differently for example other partions are created and other filesystems used (yaffs for example) that means that probably the ext4 manager can't handle the environment. If you want to check what filesystems and partitions you have open the adb shell and type "mount" the same thing works in terminal emulator (an app from the market)
If there really was a problem with your filesystem that would cause you not to be able to read what it, the phone would probably not even boot.
read the insanity thread to see whether other people have the same problem or even a solution.
EDIT:
I know that's not really helpful, I'm sorry
thanks very much for your response.
I have had a quick look through the thread and have been unable to find anything remotely similar to what i am experiencing. (granted it was a quick look)
Don't suppose you have any thoughts do you as to what might be causing the reboots?
If i can't solve it i might just go back to a stock rom and see if i still get the reboots then.
Hi all,
Have any of you been able to get a Cifs share mounted under android 4.3 on the N10.
I've tried various kernels and managers like Cifs manager but with no joy, they complain of invalid argument.
It seems like there has been success on the N7 according to this thread http://forum.xda-developers.com/showthread.php?t=2107224&page=7 but I can't see anything for the N10.
If it does work for you could you let me know what ROM / Kernel combo you use?
Not only 4.3. I haven't managed to make it work on 4.2.2 either
Sent from my GT-I9505 using Tapatalk 4
http://forum.xda-developers.com/showthread.php?t=2430056
^^^^^^^ What zod said. Working fine for me
I tried several combinations to mount CIFS shares with mountmanager:
Trinity + Carbon Rom, Sentinel, CM10.2 = works without problems
Flaming Monkey + Carbon Rom, Sentinel, CM10.2 = works - but without UTF-8 (for special characters like öäü...)
KTManta + Carbon Rom, Sentinel, CM10.2 = doesnt work.
Any Kernel + Purity Rom, AOKP, PA = doesn't work.
Could someone please confirm if CIFS is finally dead on Android? I haven't seen a single user manage to make it work. I even asked kernel developers to patch their kernel with this only solution provided here and even though they were happy in the beginning they never wanted to talk about it later which makes me think it was a hell or them.
I'd really like to know if I should just uninstall all CIFS related staff and just forget about it.
Edit:
Sorry I think it's wrong threat
andreasy said:
Could someone please confirm if CIFS is finally dead on Android? I haven't seen a single user manage to make it work. I even asked kernel developers to patch their kernel with this only solution provided here and even though they were happy in the beginning they never wanted to talk about it later which makes me think it was a hell or them.
I'd really like to know if I should just uninstall all CIFS related staff and just forget about it.
Edit:
Sorry I think it's wrong threat
Click to expand...
Click to collapse
Google sure seems to be trying really hard to kill CIFS (and any network filesystems for that matter) on Android. As it stands now (in 4.3) there is no possible way to get CIFS working properly on the stock ROMs with a stock kernel. This is because the geniuses at Google removed loadable module support from the stock kernel and because of the way they implemented the multi-user stuff (using filesystem namespaces). The thing that kills me is that there is absolutely no reason for Google to make this so difficult. They could have simply compiled support for network filesystems into the kernel if they wanted to remove modules for "security". It would also be trivial for them to add a mount point which propagates to the user namespaces. They did this crap on purpose. And that is exactly the reason why my next tablet will not be an Android one. You shouldn't have to hack your tablet to get basic functionality that should just work out of the box. I'm done being scroogled.
Anyhow, I did manage to get CIFS working on my Nexus 7 which is running 4.3. See my post here for details. Now, I don't think my kernel will work on your Nexus 10. But, if you flash someone else's custom kernel (or compile your own) for the Nexus 10 which does have CIFS support/modules you should be able to use my update.zip which does not contain the kernel. I don't have a Nexus 10 to test on, so I can't promise anything but I don't see why it wouldn't work.
With new 4.3.1 Rom Versions I have troubles with CIFS Mount.
I can mount my NAS without problems with Terminal command, and I can see all mounted Files and Folders in Terminal.
But any App (like ES Fileexplorer, Solidexplorer, Power-Amp....) can't see any files. The Folder always keeps empty.
I have tried several mount points: /sdcard/cifs, storage/emulated/legacy/cifs, /data/media/cifs. Always the mount is visible in Terminal but not in all apps.
I have tried many mount options like: noperm, rw, file_mode, dir_mod, gid.....
cien12 said:
With new 4.3.1 Rom Versions I have troubles with CIFS Mount.
I can mount my NAS without problems with Terminal command, and I can see all mounted Files and Folders in Terminal.
But any App (like ES Fileexplorer, Solidexplorer, Power-Amp....) can't see any files. The Folder always keeps empty.
I have tried several mount points: /sdcard/cifs, storage/emulated/legacy/cifs, /data/media/cifs. Always the mount is visible in Terminal but not in all apps.
I have tried many mount options like: noperm, rw, file_mode, dir_mod, gid.....
Click to expand...
Click to collapse
Hi there, could you post the command line you use to mount your NAS drive ? I keep getting "Invalid argument", this is what I've tried
Code:
mount -t cifs //192.168.1.3/music /mnt/music
pkfox said:
Hi there, could you post the command line you use to mount your NAS drive ? I keep getting "Invalid argument", this is what I've tried
Code:
mount -t cifs //192.168.1.3/music /mnt/music
Click to expand...
Click to collapse
You have to get su access first with "su"
mount -r -o noperm,rw,file_mode=0777,dir_mode=0777,uid=1000,gid=1000,unc=\\\\192.168.0.10\\music,username=***,password=*** -t cifs none /sdcard/cifs
Thanks that worked, do you know of a way to mount automatically at boot time on Android ? I notice there is no /etc/fstab
Thanks again.
Hi all, if your goal is simply to play music and video from your NAS to your android device, you can use Kodi (xbmc) that can access cifs path directly!