I am using the m3-rc37 tools and the corresponding kernel on N810. The
red
cylon keeps swinging but nothing happens after that. From the trace i
can see
the following errors:
15:53:39.584808 open("/dev/alarm", O_RDWR|O_LARGEFILE) = 6
15:53:39.590454 ioctl(6, 0x40086104, 0xbeef5bd0) = -1 ENOIOCTLCMD
(Unknown error 515)
15:53:39.593597 writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Unable to
read rtc, No such file or directory\n\0", 47}], 3) = 56
15:53:39.602172 writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Invalid time
detected, 1 set to 1167652800\n\0", 44}], 3) = 53
15:53:39.607421 ioctl(6, 0x40086105, 0xbeef5bd0) = -1 ENOIOCTLCMD
(Unknown error 515)
15:53:39.611022 writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Unable to
set rtc to 1167652800: No such file or directory\n\0", 60}], 3) = 69
And later
[pid 1426] 15:53:39.820434 writev(3, [{"\4", 1}, {"ServiceManager\0",
15}, {"ServiceManager: waiting for service SurfaceFlinger\n\0", 52}],
3 <unfinished ...>
[pid 1429] 15:53:39.826965 getpid( <unfinished ...>
Is the first error fatal ? Why isn't the SurfaceFlinger starting. I do
see
15:53:39.680603 writev(3, [{"\4", 1}, {"ServiceManager\0", 15},
{"ServiceManager: addService(ui_hardware, 0x1357c)\n\0", 50}], 3) = 66
I am wondering why the SurfaceFlinger is not starting and is this the
reason for not seeing any
progress beyond red cyclon swinging ? Any clues would be
appreciated ? i have set the permissions
to 0666 on most of the stuff. I am using ext2 filesystem on a SD card.
As i am using m3, i am using
the the driver/binder.
thanks
mohan
On Apr 18, 1:57 am, stolzi <[EMAIL PROTECTED]>
wrote:
> > Did you use init to start android ?
>
> My setup is slightly different. I am going to describe it in detail at
> the project pages.
> As mentioned earlier I'm using a multiboot initfs which lets me choose
> from which drive (flash, mmc1, mmc2) to boot. On the mmc I have the
> Android filesystem and a small script eventually starting android's
> init.
>
> Regards,
> Sebastian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Internals" group.
To post to this group, send email to android-internals@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
