Thanks, Jeff.
It seems like that the modules are copied from vendor/asus/eee_701/
modules
How can I check magic numbers?
I'm attaching files in the directory. There is the module.versions
file and drm-patches. Maybe you can pinpoint what's going on with
these files better.
Thanks,
Brian
vendor/asus/eee_701/modules$ ls
atl2.ko cfbcopyarea.ko cfbimgblt.ko drm-patches font.ko
module.versions
bitblit.ko cfbfillrect.ko drm.ko fbcon.ko i915.ko
softcursor.ko
vendor/asus/eee_701/modules$ cat module.versions
Modules:
atl2.ko
Source:
http://people.redhat.com/csnook/atl2/atl2-2.0.5.tar.bz2
----------------------------
Modules:
bitblit.ko
cfbcopyarea.ko
cfbfillrect.ko
cfbimgblt.ko
fbcon.ko
font.ko
softcursor.ko
Source:
git://android.git.kernel.org/kernel/common.git android-2.6.25
commit b6922faa7d617f11440ab8096b8797ccdcebd10d
Author: Nick Pelly <npe...@google.com>
Date: Mon Nov 10 21:59:54 2008 -0800
android_paranoid_network: Use in_egroup_p to check gid's.
groups_search is not exported from sys.c which causes problems
for module
builds. in_egroup_p is exported and is just what we need.
-----------------------------
Modules:
drm.ko
i915.ko
Source:
git://anongit.freedesktop.org/git/mesa/drm modesetting-101
with drm-patches/* applied.
commit e664967bde876b1a1cd205885dafa88a744a6c3d
Author: Dima Zavin <dmitr...@google.com>
Date: Thu Jun 26 14:38:42 2008 -0700
intel_fb: Add a hack to allocate the virtual screen 2x the height
of the actual mode height, to allow a simplisti
commit 41bebc2b10235f631f057e4325ea87027a1f2d2b
Author: Dima Zavin <dmitr...@google.com>
Date: Thu Jun 26 14:48:58 2008 -0700
intel_fb: pan_display should call mode_set_base, and not
set_config.
Signed-off-by: Dima Zavin <dmitr...@google.com>
commit fe69162447b585918a8a26ab47b44c56a0209a83
Author: Dima Zavin <dmitr...@google.com>
Date: Thu Jun 26 14:48:41 2008 -0700
intelfb: Also fail check_var if the virtual screen dimensions
exceed the fb width/height.
Signed-off-by: Dima Zavin <dmitr...@google.com>
commit e4713780e7907e51bfc2f43667a67eee332b1449
Author: Dima Zavin <dmitr...@google.com>
Date: Thu Jun 26 14:48:18 2008 -0700
intelfb: Force color depth changes to be applied to hw if the mode
itself has not changed.
Signed-off-by: Dima Zavin <dmitr...@google.com>
commit 9c7137483d1ef47eaff99f98b3c4e552c726e5d9
Author: Maarten Maathuis <madman2...@gmail.com>
Date: Thu Aug 14 20:42:28 2008 +0200
nouveau: fix typo
On Mar 30, 7:50 am, Jerry Fan <jerryfan1...@gmail.com> wrote:
> Hi Brian,
> How did you compile your i915? Did you just copy i915.ko from somewhere
> else, becasue I see some version problem. In addition, I didn't see any
> CONFIG_i915 stuff in your .config. So, if you copied i915 from somewhere
> else, u need to make sure module magic number matches the magic number of ur
> kernel.
>
> On Mon, Mar 30, 2009 at 10:31 PM, Brian <bgc...@gmail.com> wrote:
>
> > I made a bit more progress.
>
> > In system/core/mountd/Android.mk,
>
> > #disabled - we are using vold now instead
> > #include $(BUILD_EXECUTABLE)
>
> > So, mountd is not compiled and is not included, but init.rc still uses
> > mountd instead of vold.
> > The code base's changing.
> > I compiled mountd and added it to system/bin, and mountd starts but
> > I'm not sure it's using some configuration file correctly.
>
> > The problem of app_process is still there. It does not start probably
> > because of framebuffer issues.
> > I'm attaching my dmesg. How can I start app_process correctly?
>
> > Thanks,
> > Brian
>
> > <6>[ 3.914300] EXT3 FS on sda8, internal
> > journal
> > <6>[ 3.915900] EXT3-fs: recovery
> > complete.
> > <6>[ 3.917404] EXT3-fs: mounted filesystem with ordered data
> > mode.
> > <6>[ 3.921754] kjournald starting. Commit interval 5
> > seconds
> > <6>[ 3.923860] EXT3 FS on sda5, internal
> > journal
> > <6>[ 3.930177] EXT3-fs: recovery
> > complete.
> > <6>[ 3.931682] EXT3-fs: mounted filesystem with ordered data
> > mode.
> > <4>[ 3.934621] atl2: disagrees about version of symbol
> > struct_module
> > <4>[ 3.936923] softcursor: disagrees about version of symbol
> > struct_module
> > <4>[ 3.939144] bitblit: disagrees about version of symbol
> > struct_module
> > <4>[ 3.940580] font: disagrees about version of symbol
> > struct_module
> > <4>[ 3.942807] cfbimgblt: disagrees about version of symbol
> > struct_module
> > <4>[ 3.945085] cfbfillrect: disagrees about version of symbol
> > struct_module
> > <4>[ 3.947296] cfbcopyarea: disagrees about version of symbol
> > struct_module
> > <4>[ 3.951003] drm: disagrees about version of symbol
> > struct_module
> > <4>[ 3.953283] i915: disagrees about version of symbol
> > struct_module
> > <4>[ 3.955435] fbcon: disagrees about version of symbol
> > struct_module
> > <6>[ 4.062929] eth0: link
> > up
> > <6>[ 5.366418] warning: `app_process' uses 32-bit capabilities
> > (legacy suppor
> > <6>[ 5.404949] SurfaceFlinger[2083]: segfault at 38 ip 80111049 sp
> > 9e1a8fec e
> > <6>[ 8.778217] SurfaceFlinger[2098]: segfault at 38 ip 80111049 sp
> > b5bc1fec e
> > <6>[ 15.141104] SurfaceFlinger[2114]: segfault at 38 ip 80111049 sp
> > 9e04dfec e
>
> > On Mar 29, 7:56 pm, Brian <bgc...@gmail.com> wrote:
> > > I found out that there is no mountd under /system/bin.
> > > It must be that mountd is not copied into system.img.
> > > Which code should I look at to ensure that system.img contains mountd?
>
> > > Thanks,Brian
>
> > > 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.
>
> ...
>
> read more »
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
