Hi, I've been able to install the kernel, but I am having issues
installing the file system. I am using the m5-rc14 userspace with the
m5-rc14 kernel.
I get a segmentation fault upon running the kernel. I straced the
init and received:
\h:\w\$ strace -f -ff -tt -s 200 /init
04:02:38.896362 execve("/init", ["/init"], [/* 59 vars */]) = 0
04:02:38.909790 gettid() = 1464
04:02:38.912689 syscall_983045(0xbea0d614, 0, 0x20, 0, 0xbe9ee000,
0xbea0d6d0, 0xbea0d720, 0xf0005, 0xbea0d720, 0, 0x80b8, 0x80b4, 0,
0xbea0d608, 0x17c77, 0x17f2c, 0x60000010, 0xbea0d614, 0, 0, 0xc764, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0
04:02:38.916168 socket(PF_FILE, SOCK_STREAM, 0) = 3
04:02:38.919250 connect(3, {sa_family=AF_FILE,
[EMAIL PROTECTED], 19) = -1 ECONNREFUSED (Connection refused)
04:02:38.923248 close(3) = 0
04:02:38.926208 sigaction(SIGCHLD, {0x8211, [], SA_NOCLDSTOP}, NULL,
0xc0fb8) = 0
04:02:38.929718 umask(0) = 022
04:02:38.932373 ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost
isig icanon echo ...}) = 0
04:02:38.936523 dup(1) = 3
04:02:38.939422 write(3, "init: HOW ARE YOU GENTLEMEN\n", 28init: HOW
ARE YOU GENTLEMEN
) = 28
04:02:38.943328 close(0) = 0
04:02:38.945983 close(1) = 0
04:02:38.948577 close(2) = 0
04:02:38.951202 open("/dev/null", O_RDWR|O_LARGEFILE) = 0
04:02:38.954345 dup2(0, 1) = 1
04:02:38.956939 dup2(0, 2) = 2
04:02:38.959625 write(3, "init: reading config file\n", 26init:
reading config file
) = 26
04:02:38.963592 brk(0) = 0x20000
04:02:38.966217 brk(0x20000) = 0x20000
04:02:38.968994 brk(0x21000) = 0x21000
04:02:38.971832 open("/etc/init.rc", O_RDONLY|O_LARGEFILE) = 4
04:02:38.975006 lseek(4, 0, SEEK_END) = 5746
04:02:38.991088 lseek(4, 0, SEEK_SET) = 0
04:02:38.993286 brk(0x22000) = 0x22000
04:02:38.998413 read(4, "## Global environment setup\n##\nenv {\n
PATH /sbin:/system/sbin:/system/bin\n LD_LIBRARY_PATH /system/lib
\n ANDROID_BOOTLOGO 1\n ANDROID_ROOT /system\n
ANDROID_ASSETS /system/app\n ANDROID_"..., 5746) = 5746
04:02:39.002288 close(4) = 0
04:02:39.003845 brk(0x23000) = 0x23000
04:02:39.005310 mkdir("/proc", 0755) = -1 EEXIST (File exists)
04:02:39.006622 mkdir("/dev", 0755) = -1 EEXIST (File exists)
04:02:39.007843 mkdir("/dev/pts", 0755) = -1 EEXIST (File exists)
04:02:39.009368 mkdir("/sys", 0755) = -1 EEXIST (File exists)
04:02:39.011230 mkdir("/d", 0755) = -1 EEXIST (File exists)
04:02:39.012451 mount("/dev/pts", "/dev/pts", "devpts", 0, NULL) = -1
EBUSY (Device or resource busy)
04:02:39.017883 mount("/proc", "/proc", "proc", 0, NULL) = -1 EBUSY
(Device or resource busy)
04:02:39.026428 mount("/sys", "/sys", "sysfs", 0, NULL) = -1 EBUSY
(Device or resource busy)
04:02:39.033416 mount("/d", "/d", "debugfs", 0, NULL) = -1 EBUSY
(Device or resource busy)
04:02:39.038238 mount("/tmp", "/tmp", "tmpfs", 0, NULL) = 0
04:02:39.043457 open("/proc/cmdline", O_RDONLY|O_LARGEFILE) = 4
04:02:39.046417 read(4, "root=1f03 rootfstype=jffs2 ro\n", 1023) = 30
04:02:39.048187 close(4) = 0
04:02:39.049346 chmod("/proc/cmdline", 0400) = 0
04:02:39.050689 open("/system_properties", O_RDWR|O_CREAT|O_EXCL|
O_LARGEFILE, 0600) = 4
04:02:39.052368 ftruncate(4, 32768) = 0
04:02:39.053588 open("/system_properties", O_RDONLY|O_LARGEFILE) = 5
04:02:39.056884 unlink("/system_properties") = 0
04:02:39.058624 mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_SHARED,
4, 0) = -1 EINVAL (Invalid argument)
04:02:39.059997 close(5) = 0
04:02:39.061096 close(4) = 0
04:02:39.063110 open("/etc/default.prop", O_RDONLY|O_LARGEFILE) = 4
04:02:39.064422 lseek(4, 0, SEEK_END) = 130
04:02:39.065521 lseek(4, 0, SEEK_SET) = 0
04:02:39.066619 read(4, "# default system properties\n# these may be
overridden by /data/local.prop\n\nnet.bt.name = Android\n\n# end
default system properties\n", 130) = 130
04:02:39.069152 close(4) = 0
04:02:39.070251 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
04:02:39.072601 +++ killed by SIGSEGV +++
Process 1464 detached
I can't seem to figure out what's going wrong. Any ideas?
On Apr 24, 12:26 pm, [EMAIL PROTECTED] wrote:
> Hi,
> Please ignore it.
> It is caused by the wrong file system.
> Keep working on the blank screen issue.
>
> -Leon
>
> On Apr 24, 1:46 am, [EMAIL PROTECTED] wrote:
>
> > Hi,
> > I use the toolchain(cs2005q3.2-glibc2.5)
> > inhttp://www.progbox.co.uk/wordpress/?p=453.
> > But I got the following error in /dev/log/main:
>
> > dalvikvmToo many exceptions during init (failed on 'java/lang/
> > NoClassDefFoundError' 'java/lang/NoClassDefFoundError')
> > dalvikvmVM aborting
> > le deps in cache file; removing and retrying
> > dalvikvmDexOpt: --- BEGIN 'core.jar' (bootstrap=1) ---
> > dalvikvmDexOpt: waiting for verify+opt, pid=1688
> > dalvikvmDexOpt: --- END 'core.jar' --- status=0x0009, process failed
> > dalvikvmUnable to extract+optimize DEX from '/system/framework/
> > core.jar'
> > dalvikvmDexOpt: incorrect opt magic number (0xff ff ff ff)
>
> > Not sure whether it was caused by the toolchain.
> > Should I use cs2007q3-glibc2.5 to compile the source ?
>
> > Thanks,
> > Leon
>
> > On Apr 5, 7:35 pm, sim0nx <[EMAIL PROTECTED]> wrote:
>
> > > I can't believe it !!!
> > > Android runs on the maemo n810 !!!
>
> > > After reading
> > > this:http://groups.google.lu/group/android-internals/browse_thread/thread/...
> > > for the 100th time, and following the instructions on the mentioned
> > > link:http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-...
> > > it works.
>
> > > Here are the specifics I've implemented:
> > > * patch /etc/init.rc
> > > ---- begin : init.rc
> > > ....
> > > ## qemu-init {
> > > ## exec /etc/qemu-init.sh
> > > ## }
> > > network-property {
> > > exec /etc/set_network.sh
>
> > > }
>
> > > /bin/chmod -R a+rw /data /tmp
> > > /bin/chmod a+rw .
> > > /bin/chmod -R a+rw data
>
> > > # rm /dev/log (if you have)
> > > # mkdir /dev/log;touch /dev/log/{main,events,radio}
> > > * you can see usefull infos from strace log and /dev/log/main
>
> > > and instead of:
> > > chroot . /a.sh
> > > I execute the android init process:
> > > chroot . /init
>
> > > Not sure yet what exactly of those steps solved the problem (maybe the
> > > qemu one), but it does work.
> > > After a quick try I see that the touchscreen doesn't work (the
> > > keyboard does though), but that shouldn't be too hard to fix.
>
> > > BTW, this is using an m5 kernel, and binder.c
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Internals" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-internals?hl=en
-~----------~----~----~----~------~----~------~--~---
