chroot into Android-x86 4.0 RC1 from Ubuntu 11.10

[Prasanna Kumar T S M]

Is it possible to chroot into android-x86 system from Ubuntu 11.10, if so how to do it? I am running a 64-bit version of Ubuntu. I am able to chroot to fedora 32 bit system but I am not able to chroot to android-x86 system. Is there anything I am missing?

I just ran "chroot /android/system" as root (/android/system is where the system folder of android-x86 is present). The command says "chroot: failed to run command `/bin/bash': No such file or directory
". system/bin/bash is an symbolic link to system/bin/mksh. I am not even able to execute mksh - I guess that is why the chroot command fails. Is there any way to solve this? I am not getting internet access inside android-x86 as I only have ethernet port and not WiFi.

Thanks for the help,
Prasanna Kumar T S M.

[Frank van Beek]

Hi Prasanna,

On 2 September 2012 19:47, Prasanna Kumar T S M

<prasanna...@gmail.com> wrote:
> Is it possible to chroot into android-x86 system from Ubuntu 11.10, if so
> how to do it? I am running a 64-bit version of Ubuntu. I am able to chroot
> to fedora 32 bit system but I am not able to chroot to android-x86 system.
> Is there anything I am missing?

Ubuntu and Fedora are very similar. They run on the same hardware and
share the same kernel code. That's why you are able to run Fedora
executables from within Ubuntu.

Android x86 is also Linux and x86 based, but that doesn't mean that
the binaries can be run in any other Linux/x86 OS. The Ubuntu kernel
simply does not know how to execute the Android binaries.

You could use Virtualbox to run Android from within Ubuntu, but
setting up Virtualbox will take some effort.


Frank.

[prasannatsmkumar]

On Mon, Sep 3, 2012 at 2:06 AM, Frank van Beek <f.v....@gmail.com> wrote:
> Hi Prasanna,
>
> On 2 September 2012 19:47, Prasanna Kumar T S M
> <prasanna...@gmail.com> wrote:
>> Is it possible to chroot into android-x86 system from Ubuntu 11.10, if so
>> how to do it? I am running a 64-bit version of Ubuntu. I am able to chroot
>> to fedora 32 bit system but I am not able to chroot to android-x86 system.
>> Is there anything I am missing?
>
> Ubuntu and Fedora are very similar. They run on the same hardware and
> share the same kernel code. That's why you are able to run Fedora
> executables from within Ubuntu.
>
> Android x86 is also Linux and x86 based, but that doesn't mean that
> the binaries can be run in any other Linux/x86 OS. The Ubuntu kernel
> simply does not know how to execute the Android binaries.
>

Is it possible to teach Linux kernel about Android executables? As I
could see both are ELF binaries - I guess adding some code in Kernel
could make it launch Android binaries. Is it possible, if so how?

> You could use Virtualbox to run Android from within Ubuntu, but
> setting up Virtualbox will take some effort.

I am having a system without hardware VT so running Android in
Virtualbox is dead slow.

>
> Frank.
>
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>

Thanks,

[Frank van Beek]

> Is it possible to teach Linux kernel about Android executables? As I
> could see both are ELF binaries - I guess adding some code in Kernel
> could make it launch Android binaries. Is it possible, if so how?

You might get it to a point where you would be able to do a ls or cat,
but I don't think that is what you are looking for. :)

If you want to start a random App, you would have to have a running
Dalvik and some hardware abstraction layer to emulate the touchscreen
and network(!). This could take months or maybe even years of
development.

[prasannatsmkumar]

Sad :(.

[ALoGeNo]

Hi Prasanna, you cant run android with a linux kernel, but you CAN run linux with an android kernel, then maybe you can do chroot, I'm building my unofficial releases with bash included if you wanna try, in any case to do chroot you must to use "chroot /android/system /system/xbin/bash" (with my unofficial build) or "chroot /android/system /system/bin/sh" (if you run a official release like RC2.

You can find my unofficial releases at (without ethernet support): http://android-x86.sceners.org/en/
And of course you can find another unofficial releases (WITH ethernet support) http://tablets-x86.org

Cheers, I hope that help.

[ALoGeNo]

Sorry wrong link here is the good one http://tabletsx86.org/

[prasannatsmkumar]

> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.

> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-x86/-/LmexwLTXkBsJ.

>
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-x86...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.

I will try the unofficial release in tabletsx86.org with ethernet
support tonight or tomorrow and get back to you.

Thanks,

[prasannatsmkumar]

On Fri, Sep 7, 2012 at 5:58 AM, ALoGeNo <ALo...@android-x86.org> wrote:
> Sorry wrong link here is the good one http://tabletsx86.org/
>

> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/android-x86/-/FtI9rhiiqkAJ.

>
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-x86...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.

I tried the generic image available. I copied the kernel and other
files after extracting it from the iso image (including the files in
system folder). Then modified my grub to point to it. But not much
use. The kernel boots, detects the android location and then the
screen goes blank. Nothing happens. I guess some problem with display
or other driver. Any idea on how to resolve this?

Thanks,