Hi Yi.
I've just tested your patch.
EXT2-fs problem is resolved.
but
"sh:can't access tty; job control turned off " message is still.
I am wating android UI for 10 minutes.
any suggestion?
Here is result message.
...
[time..] init: /init.rc: 89: invalid option 'enabled'
ANDROID [time..] atl2: disagrees about version
of symbol struct_module
[time..] softcursor: disagrees about version of symbol struct_module
[time..] bitblit: disagrees about version of symbol struct_module
[time..] font: disagrees about version of symbol struct_module
...
[time..] drm: disagrees about version of symbol struct_module
[time..] i915: disagrees about version of symbol struct_module
[time..] fbcon: disagrees about version of symbol struct_module
sh: can't access tty: job control turned off
#
Thanks
shlee.
On 4월12일, 오전11시38분, Yi Sun <[email protected]> wrote:
> Shlee, thank you for trying this out.
> Yes I did not remove these modules from init.rc. And they are harmless
> for VB env anyway.
>
> The ext2 errors maybe a concern and it is the first time I see this. I
> will see if I can reproduce the same.
>
> The typo in the line 89 of init.rc should be fixed and I will do.
>
> The sh error message is harmless as well.
>
> Suppose, when you reach current stage, you should see android UI to
> come up in around 30 seconds. Have you seen the Android UI to come up?
> Yi
>
> On Apr 11, 2009, at 2:13 AM, shleeforandroid <[email protected]>
> wrote:
>
>
>
>
>
> > Hi Yi
>
> > environment:
> > VirtualBox : Sun xVirtualBox 2.1.4
> > Host : Windows XP, guest: Ububtu8.10
>
> > I did android building process on guest environment(Ubuntu).
>
> > I downloaded above patches from
> > http://code.google.com/p/patch-hosting-for-android-x86-support/
> > (boot_able_img.patch,
> > alarm.patch,
> > frameworks.patch,
> > e2fsprogs.patch )
>
> > And I applied boot_able_img.patch, alarm.patch, e2fsprogs.patch.
> > And I could accept installed.img successfully.
> > And I converted *.img to *.vdi on DOS cmd using VBoxManage.exe.
> > ( VBoxManage.exe convertfromraw -format VDI c:\installer.img c:
> > \installer.vdi )
>
> > I
>
> > finally I can see this result.
> > ....
> > [time..] init: /init.rc: 89: invalid option 'enabled'
>
> > ANDROID [time..] EXT2-fs warning: mounting
> > unchecked fs, running e2fsck recommended
> > [time..] EXT-fs warning: mounting unchecked fs, running e2fsck
> > recommended
> > [time..] atl2: disagrees about version of symbol struct_module
> > [time..] softcursor: disagrees about version of symbol struct_module
> > [time..] bitblit: disagrees about version of symbol struct_module
> > [time..] font: disagrees about version of symbol struct_module
> > ...
> > [time..] drm: disagrees about version of symbol struct_module
> > [time..] i915: disagrees about version of symbol struct_module
> > [time..] fbcon: disagrees about version of symbol struct_module
> > [time..] attempt to access beyond end of device
> > [time..] sda: rw=0, want=1022448, limit=1021432
> > [time..] attempt to access beyond end of device
> > [time..] sda: rw=0, want=1022448, limit=1021432
> > [time..] EXT2-fs error (device sda8): ext2_readdir:bad page in #505
> > [time..] Remounting filesystem read-only
> > sh: can't access tty: job control turned off
> > #[time ..] eth0: link up, 100Mbps, full-duplex
> > _ <== if enter
> > #
>
> > If I modified /vendor/asus/eee_701/init.rc not to include modules
> > (atl2.ko, softcursor.ko ... etc),
> > I did see
>
> > ...
> > some logs
>
> > ANDROID
> > sh: can't access tty: job control turned off
> > [time..] eth0: link up, 100Mbps, full-duplex
>
> > What can I do to fix this problem? Any suggestion?
>
> > Thanks
> > shlee
>
> > On 4월10일, 오전3시43분, Yi Sun <[email protected]> wrote:
> >> THen you don't need to worry about i915 at all. forget about it, just
> >> make sure you have config the vesa fb correctly as Chen said. And
> >> make
> >> sure you have passed in the correct cmdline.
>
> >> On Thu, 2009-04-09 at 11:36 -0700, shleeforandroid wrote:
> >>> hi Yi.
> >>> I have no eeePC.
> >>> so, I am testing on just VM.
>
> >>> On Apr 10, 3:24 am, Yi Sun <[email protected]> wrote:
> >>>> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]>" 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 <[email protected]> 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 <[email protected]> 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 <[email protected]>
> >>>>>>>>> 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
>
> ...
>
> 추가 정보 »- 따온 텍스트 숨기기 -
>
> - 따온 텍스트 보기 -
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
