Thanks, Yi.
I have all the following in my init.rc.
servicemanager, mediaserver, installd are running.
But adbd, mountd, and zygote are not launched. Any suggestion?
Thanks,
Brian
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
service servicemanager /system/bin/servicemanager
user system
critical
onrestart restart zygote
onrestart restart media
service mountd /system/bin/mountd
socket mountd stream 0660 root mount
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --
start-system-server
socket zygote stream 666
onrestart write /sys/android_power/request_state wake
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin
service installd /system/bin/installd
socket installd stream 600 system system
On Mar 29, 6:26 pm, Yi Sun <beyo...@gmail.com> wrote:
> Here is the part of the init.rc that I think is important for you to verify.
> Just make sure you have all of them enabled. You init.rc should be in
> /vendor/asus/eee_701/
>
> # adbd is controlled by the persist.service.adb.enable system property
> service adbd /sbin/adbd
> disabled
>
> on property:persist.service.adb.enable=1
> start adbd
>
> on property:persist.service.adb.enable=0
> stop adbd
>
> service servicemanager /system/bin/servicemanager
> user system
> critical
> onrestart restart zygote
> onrestart restart media
>
> service mountd /system/bin/mountd
> socket mountd stream 0660 root mount
>
> service zygote /system/bin/app_process -Xzygote /system/bin --zygote
> --start-system-server
> socket zygote stream 666
> onrestart write /sys/android_power/request_state wake
>
> service media /system/bin/mediaserver
> user media
> group system audio camera graphics inet net_bt net_bt_admin
>
> service installd /system/bin/installd
> socket installd stream 600 system system
>
> On Sun, Mar 29, 2009 at 4:55 PM, Brian <bgc...@gmail.com> wrote:
>
> > Thanks, Yi.
>
> > Now I can use adb to browse the android vm directories. Also, I
> > installed busybox. :)
>
> > I noticed that mine does not show either mountd or zygote. Maybe
> > init.rc is different?
> > Could you kindly post your init.rc so that I can do further debugging?
>
> > Thanks,
> > Brian
>
> > On Mar 29, 4:07 pm, Yi Sun <beyo...@gmail.com> wrote:
> > > Hi Brain,
> > > I just saw that I have replied your e-mail with such a bad English :-).
> > In
> > > order to run adbd, you need to either set persist.service.adb.enable=1 or
> > > run it directly in the init.rc.
>
> > > I don't have any issue with init.rc while I tried the android on my Eee
> > PC.
> > > The problem I had is with the i915 DRM/FB driver. After changed to use
> > right
> > > module, I was be able to run Android.
> > > Yi
>
> > > On Sun, Mar 29, 2009 at 3:01 PM, Brian <bgc...@gmail.com> wrote:
>
> > > > Thanks, Yi !
>
> > > > I think init.rc is not correctly executed. It probably exits before it
> > > > starts adb.
> > > > I manually started adbd, and connected android using adb successfully.
>
> > > > What problems did you have in init.rc?
>
> > > > Thanks,
> > > > Brian
>
> > > > On Mar 29, 2:21 pm, Yi Sun <beyo...@gmail.com> wrote:
> > > > > In your ps, I did not see adbd. If should be abled if
> > > > > persist.service.adb.enable=1
> > > > > Yi
>
> > > > > On Sun, Mar 29, 2009 at 8:26 AM, Brian <bgc...@gmail.com> wrote:
>
> > > > > > Thanks, Chen.
>
> > > > > > On Mar 28, 10:40 pm, Chen Yang <sunsety...@gmail.com> wrote:
> > > > > > > Brian:
> > > > > > > I cannot see the clear problem from your description. The
> > segfault
> > > > > > > issue seems to be common where the there is no framebuffer
> > devices
> > > > > > > activated.
> > > > > > > For connection over adb, you may need to enabled the pcnet32
> > > > driver
> > > > > > > in the kernel.
>
> > > > > > My pcnet32 driver is working. I can ping from the vm and ping the
> > vm
> > > > > > as well.
> > > > > > I tried ADB_HOST, but it did not work. I think this is because adbd
> > is
> > > > > > not running on android.
> > > > > > Is there an easy way to run it manually? When I just type adbd, it
> > > > > > does not return to the console
> > > > > > (I'm doing all of these by keep pressing alt+f1 whenever there is a
> > > > > > black screen.)
>
> > > > > > > One more question, when enabled vga=788 option, have you
> > waited
> > > > > > > some time to see the effect? The screen may become black for a
> > short
> > > > > > > time, during that time, the kernel is doing some initialization,
> > so
>
> > > > > > Yes. It goes to the similar stage where I get without vga=788.
> > > > > > But with vga=788, even alt+f1 does not work. I can't even see a
> > > > > > console briefly by pressing alt+f1.
>
> > > > > > I did ps.
> > > > > > (I may miss some processes before ata/0 due to screen size)
> > > > > > ata/0
> > > > > > ata_aux
> > > > > > ksuspend_usbd
> > > > > > khubd
> > > > > > kseriod
> > > > > > kmmcd
> > > > > > btaddconn
> > > > > > btdelconn
> > > > > > pdflush
> > > > > > pdflush
> > > > > > kswapd0
> > > > > > aio/0
> > > > > > scsi_eh_0
> > > > > > scsi_eh_1
> > > > > > kondemand/0
> > > > > > krfconmd
> > > > > > kjournald
> > > > > > kjournald
> > > > > > kjournald
> > > > > > /system/bin/sh
> > > > > > /system/bin/servicemanager
> > > > > > /system/bin/mediaserver
> > > > > > /system/bin/installd
>
> > > > > > Are you getting a similar list of processes?
> > > > > > Is this missing important processes?
>
> > > > > > Have you tried to build one with the latest repository? I'm
> > wondering
> > > > > > if this is because of some changes in the repository.
> > > > > > If you can post the installer.img you created for vmware, I'd like
> > to
> > > > > > try it out.
>
> > > > > > Thanks a lot!
> > > > > > - Brian
>
> > > > > > > looks like no response.
> > > > > > > --
> > > > > > > Chen
>
> > > > > > > On Sun, Mar 29, 2009 at 5:44 AM, Brian <bgc...@gmail.com> wrote:
>
> > > > > > > > Hi Chen,
>
> > > > > > > > When I added vga=788 in the cmdline in booting it, the screen
> > > > totally
> > > > > > > > freezes. Even alt + f1 does not display any.
> > > > > > > > I booted the kernel with vga=788 option. In that case, I have
> > the
> > > > > > > > following in /proc/cmdline.
> > > > > > > > console=ttyS1,115200n8 console=tty0
> > androidboot.hardware=eee_701
>
> > > > > > > > I tried to check /proc/devices. But for that I need to install
> > > > > > > > busybox. I don't know how to do it without installing busybox.
> > > > > > > > Unfortunately adb does not work (I tried ADBHOST, but I got
> > error:
> > > > > > > > device not found), although
> > > > > > > > the android vm has network connection in a bridged mode.
>
> > > > > > > > I am sure I turned on VESA VGA and Framebuffer Console support
> > when
> > > > I
> > > > > > > > compiled bzImage.
>
> > > > > > > > dmesg output keeps printing out the following.
> > > > > > > > <6> [timestamp] SurfaceFlinger[2956]: segfault at 38 ip
> > 80111049 sp
> > > > > > > > b5b56fec error 4 in libc.so [80100000+4b000]
>
> > > > > > > > Thanks for your help.
> > > > > > > > Brian
>
> > > > > > > > On Mar 27, 5:11 am, Chen Yang <sunsety...@gmail.com> wrote:
> > > > > > > >> hi,Brian:
> > > > > > > >> Sorry for late response on this thread.
> > > > > > > >> Would you like to check the whether the kernel has the VESA
> > > > > > > >> support? Would you like to provide the result with:
> > > > > > > >> #cat /proc/cmdline
> > > > > > > >> and
> > > > > > > >> #cat /proc/devices
> > > > > > > >> see whether fb is listed.
> > > > > > > >> --
> > > > > > > >> Chen
>
> > > > > > > >> On Fri, Mar 27, 2009 at 1:46 PM,Brian<bgc...@gmail.com>
> > wrote:
> > > > > > > >> > Hi,
>
> > > > > > > >> > I did all the steps following Chen's instructions. I am
> > still
> > > > having
> > > > > > a
> > > > > > > >> > problem. I have tried vmware workstation and fusion.
> > > > > > > >> > In the vmware workstation, I got a blank screen after
> > booting.
> > > > > > > >> > When I press alt + f1, I can see the following messages.
>
> > > > > > > >> > [time] init : cannot find '/system/bin/mountd', disabling
> > > > 'mountd'
> > > > > > > >> > sh : can't access tty: job control turned off
> > > > > > > >> > [time] warning: 'app_process' uses 32-bit capabilities
> > (legacy
> > > > > > support
> > > > > > > >> > in use)
>
> > > > > > > >> > How can I fix it? It's hard to pinpoint what to do.
>
> > > > > > > >> > Thanks,
> > > > > > > >> >Brian
>
> > > > > > > >> > On Dec 28 2008, 1:40 am, "Chen Yang" <sunsety...@gmail.com>
> > > > wrote:
> > > > > > > >> >> At hand, i only have VMware workstation, and I have
> > verified
> > > > the
> > > > > > steps, hope
> > > > > > > >> >> it helps.
> > > > > > > >> >> I assume that you have parepared the installer.img from
> > Lim's
> > > > > > description:
>
> > > > > > > >> >> 1. create the vmware disk file based on the installer.img
> > > > > > > >> >> you can use sfdisk -l installer.img to get the C/H/S
> > > > information
> > > > > > about it,
> > > > > > > >> >> although it reports issues, it won't do harm, at least from
> > my
> > > > > > observation.
> > > > > > > >> >> And get our interested line:
> > > > > > > >> >> ...
> > > > > > > >> >> for C/H/S=*/1/0 (instead of 49/255/63).
> > > > > > > >> >> ...
>
> > > > > > > >> >> Also, you may need to change the following entries: the
> > extent
> > > > > > description
> > > > > > > >> >> part, to the real block size of the image, basically, it's
> > size
> > > > of
> > > > > > > >> >> installer.img/512.
>
> > > > > > > >> >> Cut the following lines to one file with the installer.img
> > as
> > > > > > > >> >> installer.vmdk, and copy the installer.img together with
> > this
> > > > file
> > > > > > in the
> > > > > > > >> >> same directory.
> > > > > > > >> >> ---
> > > > > > > >> >> # Disk DescriptorFile
> > > > > > > >> >> version=1
> > > > > > > >> >> CID=b01deebc
> > > > > > > >> >> parentCID=ffffffff
> > > > > > > >> >> createType="monolithicFlat"
> > > > > > > >> >> # Extent description
> > > > > > > >> >> RW 794622 FLAT "installer.img" 0
> > > > > > > >> >> # The Disk Data Base
> > > > > > > >> >> #DDB
> > > > > > > >> >> ddb.virtualHWVersion = "4"
> > > > > > > >> >> ddb.geometry.cylinders = "49"
> > > > > > > >> >> ddb.geometry.heads = "255"
> > > > > > > >> >> ddb.geometry.sectors = "63"
> > > > > > > >> >> ddb.adapterType = "ide"
> > > > > > > >> >> ddb.toolsVersion = "0"
> > > > > > > >> >> --
>
> > > > > > > >> >> 2.create a new vmware target environment as linux 2.6
> > series,
> > > > and
> > > > > > create one
> > > > > > > >> >> primary hdd with IDE at least 1.8GB(maybe a little less is
> > > > > > possible, i
> > > > > > > >> >> haven't remebered the precise size, and I haven't tried
> > SCSI
> > > > yet,
> > > > > > but may be
> > > > > > > >> >> also possible). Add the installer.vmdk as one extra hard
> > disk
> > > > to
> > > > > > the virtual
>
> ...
>
> read more »
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
