Hi All,
I tried to run logcat in my platform, it shows

# logcat
Unable to open log device '/dev/log/main': No such file or directory

Seems that it can't find the correct device node. I tried to trace the
source code of logcat and the logger driver.
I found the logcat try to open /dev/log/main as LOGGER_LOG_MAIN while the
logger.c driver is register 3 device nodes as /dev/log_main, /dev/log_events
and /dev/log_radio.

It seems like my filesystem is correct...
# ls /dev/log*
/dev/log_events
/dev/log_main
/dev/log_radio

but the logcat is trying to read wrong node?

2008/11/20 Joe Onorato <[EMAIL PROTECTED]>

> Try running logcat.  It looks like adbd is running, adb logcat might work
> too, if you have usb configured right.
>
> -joe
>
>
>
> On Thu, Nov 20, 2008 at 7:23 AM, Wang Mac <[EMAIL PROTECTED]> wrote:
>
>> Hi all,
>> I'm porting Android to QCOM 8K platform. I tried to follow
>> http://elinux.org/Android_on_OMAP#Start_via_scripts w/ some
>> modifications.
>>
>> I used following script to start android
>> ==============
>> #!/bin/sh
>>
>> mkdir /mnt/disk
>> mount -o loop /mnt/flash/android.img /mnt/disk
>>
>> cp /dev/null /mnt/disk/dev/null
>>
>> umask 000
>> chroot /mnt/disk /a.sh
>> ==============
>>
>> android.img is ramdisk.img + system.img + data.img.
>>
>> and a.sh is...
>> ==============
>> #!/system/bin/sh
>> echo "Booting Android..."
>> export PATH="/sbin:/system/sbin:/system/bin:$PATH"
>> export LD_LIBRARY_PATH=/system/lib
>> export ANDROID_ROOT=/system
>> export ANDROID_ASSETS=/system/app
>> export ANDROID_DATA=/data
>> export EXTERNAL_STORAGE=/sdcard
>> export DRM_CONTENT=/data/drm/content
>> umask 000
>> /init &
>> /system/bin/sh
>> ==============
>>
>> After a.sh is executed. The LCD only shows "A N D R O I D _"... it seems
>> that the VM is not started.
>>
>> below is the processes list
>> ==============
>> # ps
>> USER     PID   PPID  VSIZE RSS   WCHAN    PC         NAME
>> root     1     0     2852  508   c004a0c0 4018e1cc S init
>> root     2     0     0     0     c005c674 00000000 S kthreadd
>> root     3     2     0     0     c004ca30 00000000 S ksoftirqd/0
>> root     4     2     0     0     c0073560 00000000 S watchdog/0
>> root     5     2     0     0     c00594b4 00000000 S events/0
>> root     6     2     0     0     c00594b4 00000000 S khelper
>> root     10    2     0     0     c00594b4 00000000 S suspend/0
>> root     69    2     0     0     c00594b4 00000000 S kblockd/0
>> root     83    2     0     0     c00594b4 00000000 S kmmcd
>> root     88    2     0     0     c00594b4 00000000 S btaddconn
>> root     89    2     0     0     c00594b4 00000000 S btdelconn
>> root     106   2     0     0     c00594b4 00000000 S modem_notifier
>> root     109   2     0     0     c00594b4 00000000 S smd_tty
>> root     117   2     0     0     c00594b4 00000000 S qmi
>> root     126   2     0     0     c00594b4 00000000 S nmea
>> root     131   2     0     0     c0037cac 00000000 D rpcrouter
>> root     139   2     0     0     c00385c0 00000000 S krpcserversd
>> root     145   2     0     0     c00594b4 00000000 S ctl0
>> root     149   2     0     0     c00594b4 00000000 S ctl1
>> root     153   2     0     0     c00594b4 00000000 S ctl2
>> root     175   2     0     0     c007f148 00000000 S pdflush
>> root     177   2     0     0     c007f148 00000000 S pdflush
>> root     178   2     0     0     c0082c9c 00000000 S kswapd0
>> root     181   2     0     0     c00594b4 00000000 S aio/0
>> root     200   2     0     0     c00594b4 00000000 S mdp_dma_wq
>> root     201   2     0     0     c00594b4 00000000 S mdp_vsync_wq
>> root     202   2     0     0     c00594b4 00000000 S mdp_pipe_ctrl_w
>> root     321   2     0     0     c01a374c 00000000 S mtdblockd
>> root     337   2     0     0     c00594b4 00000000 S kondemand/0
>> root     340   2     0     0     c00594b4 00000000 S rpciod/0
>> root     363   1     1516  436   c00a5eb0 400d51d4 S /sbin/udevd
>> root     623   1     2852  316   c00a5eb0 401b61d4 S /usr/sbin/telnetd
>> root     632   1     1996  432   c00a5eb0 401411d4 S /usr/sbin/dropbear
>> root     650   2     0     0     c00594b4 00000000 S diag
>> root     663   2     0     0     bf0177bc 00000000 S USB mass_storag
>> root     668   1     17996 532   ffffffff 400d1804 S
>> /opt/qcom/bin/./port_bridge
>> root     669   1     2856  648   c004a0c0 4018e298 S -ash
>> root     674   669   2852  544   c004a0c0 4018e298 S /bin/sh
>> root     677   2     0     0     c0185bbc 00000000 S loop0
>> root     679   674   692   304   c004a0c0 afe0c50c S /system/bin/sh
>> root     680   679   268   180   c00a5814 0000c36c S /init
>> root     681   679   692   300   c01693cc afe0b54c S /system/bin/sh
>> root     715   680   724   312   c004a0c0 afe0c50c S /system/bin/sh
>> system   717   680   796   252   c013e26c afe0b78c S
>> /system/bin/servicemanager
>> root     743   680   1824  324   ffffffff afe0c0fc S /system/bin/mountd
>> root     744   680   652   252   c01d1ce8 afe0c0fc S /system/bin/debuggerd
>> radio    754   680   3252  596   ffffffff afe0bdfc S /system/bin/rild
>> media    764   680   15700 2992  ffffffff afe0b78c S
>> /system/bin/mediaserver
>> bluetooth 868   680   1156  564   c00a5814 afe0c6dc S
>> /system/bin/dbus-daemon
>> root     893   680   788   264   c01d1ce8 afe0c0fc S /system/bin/installd
>> root     935   680   1264  120   ffffffff 0000e664 S /sbin/adbd
>> root     963   715   872   332   00000000 afe0b54c R ps
>> ==============
>>
>> it seems that all important daemon are running, except
>> "/system/bin/app_process -Xzygote /system/bin --zygote
>> --start-system-server"
>>
>> Since there were no message in the console, can someone point me what
>> should I notice and where I can see the error logs?
>>
>> Regards,
>> Mac
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to