Are you going to run it on the real eee PC target or just a VM? On Thu, 2009-04-09 at 11:11 -0700, shleeforandroid wrote: > Hi Brian.Yi > > thaks for your early reply. > I've struggled with android 2.6.25 kernel building with modifying some > config option. T.T;; > > I did like this to make latest drm module. > aa$ git clone git://anongit.freedesktop.org/git/mesa/drm > aa$ cd drm/linux-core && make > aa/drm/linux-core$ ls *.ko > drm.ko mach64.ko nouveau.ko radeon.ko sis.ko via.ko > i810.ko mga.ko r128.ko savage.ko tdfx.ko xgi.ko > > aa/drm/linux-core$ cp drm.ko ~/mydroid/vendor/asus/eee_701/modules/ > drm.ko > aa/drm/linux-core$ cd ~/mydroid > mydroid$ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 > DISABLE_DEXPREOPT=true make -j2 installer_img > > and I will modify init.rc. > <out/~/eee_701dir>$ vi rootimg/init.rc > ### Load some modules > # insmod /lib/modules/atl2.ko > # insmod /lib/modules/softcursor.ko > # insmod /lib/modules/bitblit.ko > # insmod /lib/modules/font.ko > # insmod /lib/modules/cfbimgblt.ko > # insmod /lib/modules/cfbfillrect.ko > # insmod /lib/modules/cfbcopyarea.ko > insmod /lib/modules/drm.ko > # insmod /lib/modules/i915.ko modeset=1 > insmod /lib/modules/fbcon.ko > > and will follow the Chen's method. > I just remove i915 module like above. > > Is this step ok? > I'm waiting the result of this steps. > How to fix fbcon problem? > > thanks > shlee. > > > On Apr 10, 1:03 am, Brian <bgc...@gmail.com> wrote: > > Hi Shlee, > > > > In the end, I used 2.6.27. But 2.6.25 should also work. > > The way I addressed the fb problem is to build and use the latest > > intel drm driver modules. > > Afterwards, you need to modify init.rc and some service files as > > posted in this mailing list. > > > > -Brian > > > > On Apr 9, 7:58 am, shleeforandroid <shlee3...@gmail.com> wrote: > > > > > > > > > hi brian > > > Congratulate your work !!!! > > > > > I've just reached to some part of your work that is posed " On Mar 30, > > > 8:49 am, Brian <bgc...@gmail.com>" below. > > > > > > > >> >> >Thanks, Jerry! > > > > > >> >> > I'm using kernel 2.6.27, and the modules have version 2.6.25 > > > > > >> >> > as you > > > > > >> >> > can see below. > > > > > >> >> > There are inconsistencies in the cupcake branch. > > > > > >> >> > I will either get kernel 2.6.25 or try to compile 2.6.27 > > > > > >> >> > modules. > > > > > >> >> > Thanks,Brian > > > > > >> >> > ./kernel/include/config/kernel.release:2.6.27-00120-g453dc2b-dirty > > > > > >> >> > $ modinfo > > > > > >> >> > ./out/target/product/eee_701/rootimg/lib/modules/i915.ko > > > > > >> >> > filename: > > > > > >> >> > ./out/target/product/eee_701/rootimg/lib/modules/ > > > > > >> >> > i915.ko > > > > > >> >> > license: GPL and additional rights > > > > > >> >> > description: Intel Graphics > > > > > >> >> > author: Tungsten Graphics, Inc. > > > > > >> >> > license: GPL > > > > > >> >> > srcversion: 73F81EDC4CAE593AA695C49 > > > > > >> >> > depends: drm,cfbfillrect,cfbimgblt,cfbcopyarea > > > > > >> >> > vermagic: 2.6.25-00101-gb6922fa SMP preempt mod_unload > > > > > >> >> > PENTIUMM > > > > > >> >> > parm: modeset:int > > > > > >> >> > parm: fbpercrtc:int > > > > > >> >> > parm: i915_rightof:int > > > > > I followed your steps, Chen's and Lim's method. > > > I can see "ANDROID" message on my VirtualBox and some errors. > > > > > !!! ** > > > I also want to build android kernel 2.6.25. but i can't this kernel > > > version . > > > Would you let me know the way? > > > I want to know how to accept 2.6.25 kernel version. > > > > > Thanks > > > shlee. > > > > > On 4월2일, 오후1시43분, Brian <bgc...@gmail.com> wrote: > > > > > > Hi Chen, > > > > > > Finally, Android booted successfully ! > > > > Thanks for all the help. > > > > I need to connect to it using adb, but I don't know its ip address. > > > > In my phone, I'm using an terminal emulator I downloaded from the > > > > market... > > > > > > Thanks, > > > > Brian > > > > > > On Apr 1, 9:13 pm, Chen Yang <sunsety...@gmail.com> wrote: > > > > > > > hi Brian: > > > > > You may need to modify the framework/base/preloaded-classes to > > > > > remove those non existing classes. > > > > > And you can reference Androidphan's reply in this thread. > > > > > You may encounter the NFE and NPE, reference > > > > > this:http://groups.google.com/group/android-porting/msg/64eb5a0158e6b815 > > > > > and Androdphan's > > > > > thread:http://groups.google.com/group/android-porting/msg/97bd8c7c44a189ec > > > > > -- > > > > > Chen > > > > > > > On Thu, Apr 2, 2009 at 12:05 PM, Brian <bgc...@gmail.com> wrote: > > > > > > > > The system is trying to run zygote, but I got the following error. > > > > > > I'm attaching my logcat output. > > > > > > > > E/Zygote ( 2126): Zygote died with exception > > > > > > E/Zygote ( 2126): java.lang.IllegalStateException: Missing > > > > > > class(es) > > > > > > for preloading, update preloaded-classes > > > > > > [com.android.internal.policy.impl.PhoneLayoutInflater > > > > > > com.android.internal.policy.impl.PhoneWindow > > > > > > com.android.internal.policy.impl.PhoneWindow$1 > > > > > > com.android.internal.policy.impl.PhoneWindow$ContextMenuCallback > > > > > > com.android.internal.policy.impl.PhoneWindow$DecorView > > > > > > com.android.internal.policy.impl.PhoneWindow$PanelFeatureState > > > > > > com.android.internal.policy.impl.PhoneWindow$PanelFeatureState > > > > > > $SavedState com.android.internal.policy.impl.PhoneWindow > > > > > > $PanelFeatureState$SavedState$1] > > > > > > E/Zygote ( 2126): at > > > > > > com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:299) > > > > > > E/Zygote ( 2126): at com.android.internal.os.ZygoteInit.main > > > > > > (ZygoteInit.java:512) > > > > > > E/Zygote ( 2126): at dalvik.system.NativeStart.main(Native > > > > > > Method) > > > > > > D/AndroidRuntime( 2126): Shutting down VM > > > > > > W/dalvikvm( 2126): threadid=3: thread exiting with uncaught > > > > > > exception > > > > > > (group=0xb00dfdf8) > > > > > > D/dalvikvm( 2126): DestroyJavaVM waiting for non-daemon threads to > > > > > > exit > > > > > > D/dalvikvm( 2126): DestroyJavaVM shutting VM down > > > > > > D/dalvikvm( 2126): VM cleaning up > > > > > > D/dalvikvm( 2126): LinearAlloc 0x0 used 2087468 of 4194304 (49%) > > > > > > D/skia ( 2126): purging 6K from font cache [1 entries] > > > > > > > > Any suggestion? > > > > > > > > Thanks, > > > > > > Brian > > > > > > On Apr 1, 5:13 pm, Chen Yang <sunsety...@gmail.com> wrote: > > > > > >> Cool. It seems that you don't have the essential process: zygote. > > > > > >> You > > > > > >> can check the logcat messages to see what was happenning. Thanks. > > > > > >> -- > > > > > >> Chen > > > > > > > >> On Thu, Apr 2, 2009 at 8:09 AM, Brian <bgc...@gmail.com> wrote: > > > > > > > >> > Hi all, > > > > > > > >> > I finally managed to boot android x86 with vga=788 option without > > > > > >> > black screen in vmware. > > > > > >> > Thanks for all the help! > > > > > > > >> > I'm trying to go to the next step. > > > > > >> > Even with vga=788 option, I don't see GUI. Why? Instead, I get a > > > > > >> > shell > > > > > >> > prompt. > > > > > >> > Here's the list of system processes stored under /system/bin/. > > > > > >> > /system/bin/sh > > > > > >> > /system/bin/servicemanager > > > > > >> > /system/bin/mountd > > > > > >> > /system/bin/mediaserver > > > > > >> > /system/bin/installd > > > > > > > >> > I tried to do "ADBHOST=<ip> adb install app.apk", but I got the > > > > > >> > following error "Error: Could not access the Package Manager. Is > > > > > >> > the > > > > > >> > system running?". > > > > > > > >> > I'd like to install this application with GUI and to start it. > > > > > >> > How can > > > > > >> > I do it? > > > > > > > >> > Thanks, > > > > > >> > Brian > > > > > > > >> > On Mar 30, 10:54 pm, Brian <bgc...@gmail.com> wrote: > > > > > >> >> Hi Chen, > > > > > > > >> >> I managed to compile kernel 2.6.25. > > > > > >> >> When I ran it without vga=788, I see a shell prompt. > > > > > >> >> The screen does not go to black one. > > > > > >> >> But I keep getting the following message. > > > > > >> >> [timestamp] android_power: wakeup (0->0) at ... > > > > > >> >> (Btw, how can I turn off this message?) > > > > > > > >> >> I still have a problem with vga=788. > > > > > >> >> This time I'm getting a kernel panic, which I'm attaching. > > > > > >> >> Has anyone seen this problem? What's a proper approach to > > > > > >> >> address this > > > > > >> >> problem? > > > > > > > >> >> Thanks, > > > > > >> >> Brian > > > > > > > >> >> Process netcfg (pid: 2031, ti=cf17c000 task=cf3001b0 > > > > > >> >> task.ti=cf17c000) > > > > > >> >> Stack: ... > > > > > > > >> >> Call Trace: > > > > > >> >> [<c01f12f2>] ? cursor_timer_handler+0x28/0x2b > > > > > >> >> ? run_timer_softirq+0x11d/0x176 > > > > > >> >> ? cursor_timer_handler+0x0/0x2b > > > > > >> >> ? __do_softirq+0x70/0xd5 > > > > > >> >> ? do_softirq+0x35/0x3a > > > > > >> >> ? local_bh_enable_ip+0x38/0x4f > > > > > >> >> ? _spin_unlock_bh+0x17/0x19 > > > > > >> >> ? dev_set_rx_mode+0x38/0x3c > > > > > >> >> ? dev_open+0x60/0x7e > > > > > >> >> ? dev_change_flags+0x9f/0x154 > > > > > >> >> ? devinet_ioctl+0x2da/0x5f8 > > > > > >> >> ? inet_ioctl+0x93/0xaf > > > > > >> >> ? sock_ioctl+0x1af/0x1d1 > > > > > >> >> ? sock_ioctl+0x0/0x1d1 > > > > > >> >> ? vfs_ioctl+0x22/0x69 > > > > > >> >> ? do_vfs_ioctl+0x222/0x235 > > > > > >> >> ? sys_socketcall+0x51/0x168 > > > > > >> >> ? sys_ioctl+0x40/0x5a > > > > > >> >> ? syscall_call+0x7/0xb > > > > > >> >> Code: .... > > > > > >> >> EIP: [<c012b22a>] mod_timer+0x9/0x27 SS:ESP 0068:cf17de18 > > > > > >> >> Kernel panic - not syncing: Fatal exception in interrupt > > > > > > > >> >> On Mar 30, 8:49 am, Brian <bgc...@gmail.com> wrote: > > > > > > > >> >> > Thanks, Jerry! > > > > > > > >> >> > I'm using kernel 2.6.27, and the modules have version 2.6.25 > > > > > >> >> > as you > > > > > >> >> > can see below. > > > > > >> >> > There are inconsistencies in the cupcake branch. > > > > > > > >> >> > I will either get kernel 2.6.25 or try to compile 2.6.27 > > > > > >> >> > modules. > > > > > > > >> >> > Thanks,Brian > > > > > > > >> >> > ./kernel/include/config/kernel.release:2.6.27-00120-g453dc2b-dirty > > > > > > > >> >> > $ modinfo > > > > > >> >> > ./out/target/product/eee_701/rootimg/lib/modules/i915.ko > > > > > >> >> > filename: > > > > > >> >> > ./out/target/product/eee_701/rootimg/lib/modules/ > > > > > >> >> > i915.ko > > > > > >> >> > license: GPL and additional rights > > > > > >> >> > description: Intel Graphics > > > > > >> >> > author: Tungsten Graphics, Inc. > > > > > >> >> > license: GPL > > > > > >> >> > srcversion: 73F81EDC4CAE593AA695C49 > > > > > >> >> > depends: drm,cfbfillrect,cfbimgblt,cfbcopyarea > > > > > >> >> > vermagic: 2.6.25-00101-gb6922fa SMP preempt mod_unload > > > > > >> >> > PENTIUMM > > > > > >> >> > parm: modeset:int > > > > > >> >> > parm: fbpercrtc:int > > > > > >> >> > parm: i915_rightof:int > > > > > > > >> >> > On Mar 30, 8:39 am, Jerry Fan <jerryfan1...@gmail.com> wrote: > > > > > > > >> >> > > HiBrian, > > > > > >> >> > > just type modinfo /path/to/anymodule.ko > > > > > >> >> > > compare modinfo output on any kernel ko files in your > > > > > >> >> > > Android kernel against > > > > > >> >> > > i915 from eeepc. In modinfo output, u will read vermagic > > > > > >> >> > > at last line. You > > > > > >> >> > > need to make sure every protperty in i915 vermagic matches > > > > > >> >> > > vermagic in your > > > > > >> >> > > android kernel. Any signle property mismatches will result > > > > > >> >> > > in the problem > > > > > >> >> > > you have. > > > > > > > >> >> > > On Mon, Mar 30, 2009 at 11:15 PM,Brian<bgc...@gmail.com> > > > > > >> >> > > wrote: > > > > > > > >> >> > > > Thanks, Jerry! > > > > > > > >> >> > > > (I'm very sorry. I somehow got a wrong name.) > > > > > > > >> >> > > > Please see the previous email. > > > > > > > >> >> > > > Thanks, > > > > > >> >> > > >Brian > > > > > > > >> >> > > > On Mar 30, 8:14 > > > > ... > > > > read more >>- Hide quoted text - > > > > - Show quoted text - > >
--~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
