lunch vbox-x86-eng
make -j16
make install_vdi
Though the installer won't boot in Virtualbox. It complains about a
corrupted partition.
I've also tried:
lunch vbox-x86-eng
make -j16
make android_disk_vdi
But receive a kernel panic followed by:
"atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
access hardware directly."
My only though is that I need to try this on a machine that supports
hardware virtualization... though I really hope it's not depending on
me have VT-d capabilities.
Cheers,
Nathaniel
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
Cheers,
Nathaniel
On Wed, Nov 16, 2011 at 4:45 PM, Mark Renouf <mre...@google.com> wrote:
> Here's what I'm seeing. I tried both the "Install to" option and the "Boot
> from" option.
> "Install to" stops, waiting for a /dev/sdb2 (which apparently never appears)
> "Boot from" fails to boot fully because there is no /system partition
> mounted (or so it seems).
>
> I've also included a screenshot of my VirtualBox settings, I believe I have
> these correct.
>
> I'm hoping somebody can figure this out :-)
One cool thing I saw on the first boot, it put me right into the home
screen and I was able to use the keyboard to select things, including
a very nice swap to another page that showed very acceptable graphics
performance. Now, just need to get a mouse pointer.
:D
Hopefully someone comes up with a solution for this one!
Cheers,
Nathaniel
It's use is pretty limited. I think this turns into an
android-porting, or android-x86.org discussion pretty quickly.
:D
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
I believe that the framework has some debugging commands to help
figure out which input events it's receiving, and that would probably
be useful to debug this case. You'll probably get the best expertise
in android-platform, where the framework experts lurk.
JBQ
Cheers,
Nathaniel
On Thu, Nov 17, 2011 at 12:30 PM, Daniel FAGES <dfa...@gmail.com> wrote:
JBQ
Thanks,
Doug.
JBQ
Thanks,
On Nov 17, 2:47 pm, dfages <dfa...@gmail.com> wrote:
--
unsubscribe: android-kerne...@googlegroups.com
website: http://groups.google.com/group/android-kernel
On Nov 18, 12:00 am, Doug Schaefer <cdtd...@gmail.com> wrote:
> And I have a mouse pointer. Thanks for the help guys!
>
>
>
> On Thu, Nov 17, 2011 at 2:05 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> > Yup. Sorry the kernels are a bit hard to find without gitweb. Once I
> > have the relevant projects created, I'll create a proper list on
> > source.android.com.
>
> > JBQ
>
> > On Thu, Nov 17, 2011 at 10:55 AM, Daniel FAGES <dfa...@gmail.com> wrote:
> >> Quoting JBQ :
>
> >> The emulator kernel source is available:
>
> >> git clonehttps://android.googlesource.com/kernel/goldfish
> >> cd goldfish
> >> git checkout origin/android-goldfish-2.6.29
>
> >> 2011/11/17 Doug Schaefer <cdtd...@gmail.com>
>
> >>> Sorry guys, I lost track of where the kernel source is. Could you repeat
> >>> that?
>
> >>> Thanks,
> >>> Doug.
>
> >>> On Thu, Nov 17, 2011 at 1:43 PM, Daniel FAGES <dfa...@gmail.com> wrote:
> >>> > Yes, and you have to add the "PS/2 mouse" support to the vbox_defconfig
> >>> > to
> >>> > have the mouse working using VirtualBox.
>
> >>> > Dan.
>
> >>> > 2011/11/17 Jean-Baptiste Queru <j...@android.com>
>
> >>> >> Just as an FYI, the prebuilt vbox kernel exactly matches the sources
> >>> >> that I've released, so a straight rebuild as-is should get the same
> >>> >> results (fingers crossed), and you'll need to actually make changes in
> >>> >> order to make progress.
>
> >>> >> JBQ
>
> >>> >> On Thu, Nov 17, 2011 at 10:28 AM, Nathaniel Husted <nhus...@gmail.com>
> >>> >> wrote:
> >>> >> > I'll try that later as well. I know with a bit of searching there's a
> >>> >> > link JBQ posted to the 4.0.1 kernel sources that were released in the
> >>> >> > SDK. I figure that could be easily rebuild as well with appropriate
> >>> >> > x86 support.
>
> >>> >> > Cheers,
> >>> >> > Nathaniel
>
> >>> >> > On Thu, Nov 17, 2011 at 12:30 PM, Daniel FAGES <dfa...@gmail.com>
> >>> >> > wrote:
> >>> >> >> Hi,
> >>> >> >> I'm not sure you saw my post few hours ago but to get the mouse
> >>> >> >> pointer
> >>> >> >> you
> >>> >> >> have to rebuild the kernel with the good driver.
>
> >>> >> >> Dan.
>
> >>> >> >> 2011/11/17 Doug Schaefer <cdtd...@gmail.com>
> >>> >> >>> >>> <cdtd...@gmail.com>
> >>> >> >>> >>> wrote:
>
> >>> >> >>> >>>> That and there's no network access (reinstalled to get back to
> >>> >> >>> >>>> the
> >>> >> >>> >>>> home screen where keyboard navigation works).
>
> >>> >> >>> >>>> It's use is pretty limited. I think this turns into an
> >>> >> >>> >>>> android-porting, or android-x86.org discussion pretty quickly.
>
> >>> >> >>> >>>> :D
>
> >>> >> >>> >>>> On Wed, Nov 16, 2011 at 8:30 PM, Nathaniel Husted
> >>> >> >>> >>>> <nhus...@gmail.com>
> >>> >> >>> >>>> > <cdtd...@gmail.com>
> >>> >> >>> >>>> > wrote:
> >>> >> >>> >>>> >> A-ha, that did it. Now back to your original point. How do
> >>> >> >>> >>>> >> I
> >>> >> >>> >>>> >> get a
> >>> >> >>> >>>> >> mouse pointer.
>
> >>> >> >>> >>>> >> One cool thing I saw on the first boot, it put me right
> >>> >> >>> >>>> >> into
> >>> >> >>> >>>> >> the
> >>> >> >>> >>>> >> home
> >>> >> >>> >>>> >> screen and I was able to use the keyboard to select things,
> >>> >> >>> >>>> >> including
> >>> >> >>> >>>> >> a very nice swap to another page that showed very
> >>> >> >>> >>>> >> acceptable
> >>> >> >>> >>>> >> graphics
> >>> >> >>> >>>> >> performance. Now, just need to get a mouse pointer.
>
> >>> >> >>> >>>> >> :D
>
> >>> >> >>> >>>> >> On Wed, Nov 16, 2011 at 6:47 PM, Nathaniel Husted
> >>> >> >>> >>>> >> <nhus...@gmail.com>
> >>> >> >>> >>>> >> wrote:
> >>> >> >>> >>>> >>> This is the closest thing I've found in the archive that
> >>> >> >>> >>>> >>> discusses
> >>> >> >>> >>>> >>> instructions for running the VirtualBox option. It appears
> >>> >> >>> >>>> >>> that
> >>> >> >>> >>>> >>> Android just will not function with SATA drives.
> >>> >> >>> >>>> >>> Virtualbox
> >>> >> >>> >>>> >>> MUST
> >>> >> >>> >>>> >>> be
> >>> >> >>> >>>> >>> set up with an IDE controller.
>
> >>> >> >>> >>>> >>> Link:
>
> >>> >> >>> >>>> >>>https://groups.google.com/group/android-building/browse_thread/thread...
>
> >>> >> >>> >>>> >>> Cheers,
> >>> >> >>> >>>> >>> Nathaniel
>
> >>> >> >>> >>>> >>> On Wed, Nov 16, 2011 at 4:45 PM, Mark Renouf
> >>> >> >>> >>>> >>> <mren...@google.com>
> ...
>
> read more »- Hide quoted text -
>
> - Show quoted text -
1) Hardware acceleration. Looks like the software renderer is using
LLVM now, which is OK but not great. And it seems there is a tiny bit
of Mesa to hook that up. I'd like to see full blown Mesa to at least
get the open source graphics drivers working.
2) Network management. Android assumes wireless networking so there
are things missing.
android-x86.org has stuff for #2 and has been on/off again with #1
(off in Gingerbread). So I would look there to see if any progress is
being made towards notebook support. AOSP is really close which is
very cool, but there's still porting work to do.
JBQ
Cheers,
Nathaniel
Is hardware-acceleration for OpenGL ES is must? or we can live with SW
implementation?
If so - can you please elaborate how can I build ICS with the SW
implementation.
Thx
JBQ
JBQ
> ...
>
> read more »