No I did not use the git apply patch, and those files do not exist. Here is my frame buffer section of kernel/.config # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set CONFIG_FB_VGA16=m # CONFIG_FB_UVESA is not set CONFIG_FB_VESA=y # CONFIG_FB_EFI is not set # CONFIG_FB_IMAC is not set # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I810 is not set # CONFIG_FB_LE80578 is not set CONFIG_FB_INTEL=m # CONFIG_FB_INTEL_DEBUG is not set CONFIG_FB_INTEL_I2C=y # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_VT8623 is not set # CONFIG_FB_CYBLA is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_VIRTUAL is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=y # CONFIG_LCD_LTV350QV is not set # CONFIG_LCD_ILI9320 is not set # CONFIG_LCD_VGG2432A4 is not set # CONFIG_LCD_PLATFORM is not set CONFIG_BACKLIGHT_CLASS_DEVICE=y # CONFIG_BACKLIGHT_CORGI is not set # CONFIG_BACKLIGHT_PROGEAR is not set # CONFIG_BACKLIGHT_MBP_NVIDIA is not set
On May 11, 12:25 pm, Yi Sun <[email protected]> wrote: > Make sure you are not using git apply, otherwise, the frameworks patch > may failed due to the changes in preloaded-class. git apply does patch > apply in an atomic way, so one failed, all failed. > > On Mon, 2009-05-11 at 21:12 +0800, Chen Yang wrote: > > Have you enabled network on your target platform? If yes, you may be > > able to use adb to connect it remotely. > > > According to previous discussion in the thread of eee_701, there were > > known problems in framework: > > 1) preloaded classes > > 2) battery related problem > >http://groups.google.com/group/android-porting/browse_thread/thread/6... > > > You may need to check whether you have solved those issues. > > -- > > Chen > > > On Mon, May 11, 2009 at 8:41 PM, Kasuko <[email protected]> wrote: > > > Is there anyway to get the logcat information 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 <[email protected]> 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 <[email protected]> > > 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 <[email protected]> > > 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 <[email protected]> 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 > > <[email protected]> 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 <[email protected]> > > 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 > > <[email protected]> wrote: > > > > >> > > > > oops, have you compiled the kernel with builtin > > vesafb? > > > >> > > > > it is not there by default. > > > >> > > > > -- > > > >> > > > > Chen > > > > >> > > > > On 4/26/09, FrankieCZ <[email protected]> > > 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 > > <[email protected]> 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 > > <[email protected]> > > > >> > > > >>> 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 > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
