You may be able to logcat to redirect to some file, and then read that file in other linux environment (install the disk to other linux vm and mount under that linux.) -- Chen
On Mon, May 11, 2009 at 9:25 PM, Kasuko <kas...@gmail.com> wrote: > > Ok giving the parameter console=tty0 I can grab the console but it > keeps being taken away from me. Android is constantly trying to "wake > up" and it writes alot to logcat which I can't read fast enough. Any > help on how to kill the wake up process and let me stay in the > terminal. > > On May 11, 9:14 am, Kasuko <kas...@gmail.com> wrote: > > I don't have access to a console in the virtual box and I don't think > > I can adb from my terminal to the VB installation. > > > > I have to figure out how to boot into console. > > > > On May 11, 9:02 am, Androidphan <niels.kee...@tass.nl> wrote: > > > > > Use adblogcat. > > > > > On May 11, 2:41 pm, Kasuko <kas...@gmail.com> wrote: > > > > > > Is there anyway to get thelogcatinformation without access to > > > > anything. I can't boot into a console. Which seems to mean it > probably > > > > isn't related to the fb. Hmmmm. > > > > > > On May 8, 9:36 pm, Chen Yang <sunsety...@gmail.com> wrote: > > > > > > > would you like to provide thelogcatinformation? it may not be the > fb > > > > > related according to your description. > > > > > -- > > > > > Chen > > > > > > > On Sat, May 9, 2009 at 5:17 AM, Kasuko <kas...@gmail.com> wrote: > > > > > > > > I am having this exact same issue. When I boot normally or > changing > > > > > > the boot options to vga=778 the screen resizes but stays black. > When I > > > > > > try vesafb or intelfb it does not resize. This makes me suspect > that > > > > > > the framebuffer is being initialized just something is going > wrong. I > > > > > > know vesa fb is installed. I have read and tried every how to. > And the > > > > > > same as FrankieCZ I also ran the prebuilt image and it worked > fine. > > > > > > > > Kasuko > > > > > > > > On Apr 27, 12:46 pm, FrankieCZ <franki...@centrum.cz> wrote: > > > > > >> Yes, I have copied bzImage for sure. > > > > > > > >> I'm still compiling (now I have another problem during > compilation but > > > > > >> this is probably related to my Linux envinroment (not enough RAM > or > > > > > >> something))... > > > > > > > >> Frank > > > > > > > >> On Apr 27, 6:27 pm, Yi Sun <beyo...@gmail.com> wrote: > > > > > > > >> > One more question and just a double check --- have you copied > bzImage to > > > > > >> > vendor/asus/eee_701 after you build the kernel and before you > build > > > > > >> > installer_img? > > > > > > > >> > On Mon, Apr 27, 2009 at 2:49 AM, FrankieCZ < > franki...@centrum.cz> wrote: > > > > > > > >> > > I did check of kernel config file, VESA fb. is included in > the kernel > > > > > >> > > for sure. When I do /proc/fb I cannot see VESA, actually, > where should > > > > > >> > > I see it? > > > > > >> > > It seems VESA fb is included but probably not initialized. I > have also > > > > > >> > > downloaded one Android image (compiled by someone else) and > this image > > > > > >> > > runs perfectly in VirtualBox (but don't know details about > this > > > > > >> > > image). > > > > > > > >> > > Now, I'm trying to compile everything from scratch (with the > lastest > > > > > >> > > version of Android from git) and I will see if something > change...it > > > > > >> > > takes some time to compile it etc. :) > > > > > > > >> > > Frank > > > > > > > >> > > On Apr 27, 12:10 am, Yi Sun <beyo...@gmail.com> wrote: > > > > > >> > > > Please also check the content of /proc/fb If u vessfb > driver is > > > > > >> > > > installed coreectly, you should see VESA in that file. The > > > > > >> > > > surfaceflinger crash is because it can not find > /dev/graphics/fb > > > > > >> > > > during the init process and it is caused by wrong fb > driver > > > > > >> > > > installation and configuration. > > > > > >> > > > Please do check .config file to make sure u indeed enabled > VESA fb. > > > > > >> > > > Even u have already applied patches there are still many > other things > > > > > >> > > > can went wrong > > > > > > > >> > > > On Apr 26, 2009, at 3:04 AM, Chen Yang < > sunsety...@gmail.com> wrote: > > > > > > > >> > > > > oops, have you compiled the kernel with builtin vesafb? > > > > > >> > > > > it is not there by default. > > > > > >> > > > > -- > > > > > >> > > > > Chen > > > > > > > >> > > > > On 4/26/09, FrankieCZ <franki...@centrum.cz> wrote: > > > > > > > >> > > > >> Unfortunately, still the same. > > > > > >> > > > >> I removed vesafb, add vga=788, I can boot and see black > screen only > > > > > >> > > > >> (I'm waiting enough time to be sure that Android GUI > will not > > > > > >> > > > >> appear). > > > > > >> > > > >> I've tried to change vesafb into intelfb (in cmdline), > just if > > > > > >> > > > >> something will change, but nothing. > > > > > > > >> > > > >> Obviously, there is some problem with SurfaceFlinger / > GUI > > > > > >> > > > >> initialization, maybe because I'm running it under > VirtualBox? Is > > > > > >> > > > >> there any special FB or video driver to be compiled > into the Kernel? > > > > > > > >> > > > >> Frank > > > > > > > >> > > > >> On Apr 26, 10:24 am, Chen Yang <sunsety...@gmail.com> > wrote: > > > > > >> > > > >>> please remove the vesafb in cmdline and append vga=788 > > > > > >> > > > >>> and have a try. :) > > > > > >> > > > >>> -- > > > > > >> > > > >>> Chen > > > > > > > >> > > > >>> On Sun, Apr 26, 2009 at 3:57 PM, FrankieCZ < > franki...@centrum.cz> > > > > > >> > > > >>> wrote: > > > > > > > >> > > > >>>> Hi, > > > > > > > >> > > > >>>> for booting I'm using these cmdline parameters: > > > > > > > >> > > > >>>> console=tty0 console=ttyS1,115200n8 console=tty0 > > > > > >> > > > >>>> androidboot.hardware=eee_701 vesafb > > > > > > > >> > > > >>>> (during Kernel compilation, VESAFB drivers in > menuconfig were > > > > > >> > > > >>>> selected. Generally, I've applied all patches > provided on the wiki > > > > > >> > > > >>>> (except those 2 for atl2 driver) > > > > > > > >> > > > >>>> (if I don't specify vga parameter I can boot to > console mode and > > > > > >> > > > >>>> access console via alt+f1, if I specify vga parameter > (does not > > > > > >> > > > >>>> matter, which resolution / bit depth, I cannot access > console > > > > > >> > > > >>>> after) > > > > > > > >> > > > >>>> thelogcatoputput: > > > > > > > >> > > > >>>> I/SurfaceFlinger(2536): SurfaceFlinger is starting > > > > > >> > > > >>>> I/SurfaceFlinger(2536): SurfaceFlinger's main thread > ready to run. > > > > > >> > > > >>>> Initializing graphics H/W... > > > > > >> > > > >>>> E/MemoryHeapBase(2536): error opening /dev/pmem: No > such file or > > > > > >> > > > >>>> directory > > > > > >> > > > >>>> E/GLLogger(2536): couldn't load <libhgl.so> library > (Cannot find > > > > > >> > > > >>>> library) > > > > > >> > > > >>>> I/SurfaceFlinger(2536): EGL informations: > > > > > >> > > > >>>> I/SurfaceFlinger(2536): # of configs : 6 > > > > > >> > > > >>>> I/SurfaceFlinger(2536): vendor : Android > > > > > >> > > > >>>> I/SurfaceFlinger(2536): version : 1.31 Android > META-EGL > > > > > >> > > > >>>> I/SurfaceFlinger(2536): extensions: > > > > > >> > > > >>>> I/SurfaceFlinger(2536): Client API: OpenGL ES > > > > > >> > > > >>>> E/GLLogger (2536) validate_display_surface:488 error > 300d > > > > > >> > > > >>>> (EGL_BAD_SURFACE) > > > > > >> > > > >>>> W/SurfaceFlinger(2536): ro.sf.lcd_density not > defined, using 160 > > > > > >> > > > >>>> dpi > > > > > >> > > > >>>> by default. > > > > > >> > > > >>>> E/GLLogger (2536): call to OpenGL ES API with no > current context > > > > > >> > > > >>>> I/SurfaceFlinger(2536): OpenGL informations: > > > > > >> > > > >>>> E/GLLogger (2536): call to OpenGL ES API with no > current context > > > > > >> > > > >>>> D/Zygote (2535): Process 2536 terminated by signal > (11) > > > > > >> > > > >>>> I/Zygote (2535): Exit Zygote because system server > (2536) has > > > > > >> > > > >>>> terminated > > > > > > > >> > > > >>>> As you said, libhgl.so problem is probably not > important but for > > > > > >> > > > >>>> some > > > > > >> > > > >>>> reason SurfaceFlinger is terminated (segfault) and > therefore, > > > > > >> > > > >>>> Zygote > > > > > >> > > > >>>> fails to start (better say is terminated) as well. > > > > > > > >> > > > >>>> BTW: Is there any possibility how to access console > if I specify > > > > > >> > > > >>>> vga > > > > > >> > > > >>>> parameter? And, is there any possibility how to > getlogcatoutput > > > > > >> > > > >>>> from > > > > > >> > > > >>>> VirtualBox window - some copy&paste or > accessinglogcatoutput file > > > > > >> > > > >>>> (if I redirectedlogcatoutput to the file)? > > > > > > > >> > > > >>>> Frank > > > > > > > >> > > > >>>> On Apr 26, 3:56 am, Yi Sun <beyo...@gmail.com> > wrote: > > > > > >> > > > >>>>> The libhgl error is harmless, please send us > thelogcatoutput and > > > > > >> > > > >>>>> make sure you are using right frame buffer driver as > mentioned > > > > > >> > > > >>>>> in the > > > > > >> > > > >>>>> wiki > > > > > > > >> > > > >>>>> On Apr 25, 2009, at 10:12 AM, FrankieCZ < > franki...@centrum.cz> > > > > > >> > > > >>>>> wrote: > > > > > > > >> > > > >>>>>> Problem is solved. I did everything again and > problem with > > > > > >> > > > >>>>>> dalvik- > > > > > >> > > > >>>>>> cache is not present (seems there was some problem > during > > > > > >> > > > >>>>>> creating img > > > > > >> > > > >>>>>> file, evenly i've tried it twice...). Now, I have > another > > > > > >> > > > >>>>>> problem, > > > > > >> > > > >>>>>> which is related to SurfaceFlinger and problem > with: > > > > > > > >> > > > >>>>>> 608 E/GLLogger( 441): couldn't load <libhgl.so> > library > > > > > >> > > > >>>>>> (Cannot find > > > > > >> > > > >>>>>> library) > > > > > > > >> > > > >>>>>> and segfault problem...so GUI is not starting still > :( > > > > > > > >> > > > >>>>>> This seems to be more common problem (as far as I > could see more > > > > > >> > > > >>>>>> people facing with it), so I'm trying to figure out > how to solve > > > > > >> > > > >>>>>> it.... > > > > > > > >> > > > >>>>>> Anyway, thanks, > > > > > > > >> > > > >>>>>> Frank > > > > > > > >> > > > >>>>>> On Apr 25, 6:06 pm, Chen Yang < > sunsety...@gmail.com> wrote: > > > > > >> > > > >>>>>>> You may be able to reference the init.rc to see > which > > > > > >> > > > >>>>>>> partition is > > > > > >> > > > >>>>>>> mounted as /data( by default it seems to be > /dev/block/sda8), > > > > > >> > > > >>>>>>> do you > > > > > >> > > > >>>>>>> have the right partition and file system > type(ext3)? > > > > > >> > > > >>>>>>> -- > > > > > >> > > > >>>>>>> Chen > > > > > > > >> > > > >>>>>>> On Sat, Apr 25, 2009 at 11:57 PM, FrankieCZ > > > > > >> > > > >>>>>>> <franki...@centrum.cz> > > > > > >> > > > >>>>>>> wrote: > > > > > > > >> > > > >>>>>>>> Hi all, > > > > > > > >> > > > >>>>>>>> I've tried to port Android on my x86 laptop and > run it inside > > > > > >> > > > >>>>>>>> VirtualBox. I was following this tutorial: > > > > > > > >> > > > http://code.google.com/p/patch-hosting-for-android-x86-support/wiki/B > > > > > >> > > > >>>>>>>> ... > > > > > > > >> > > > >>>>>>>> Everything went > > > > ... > > > > read more ยป > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
