Re: Android on N810 File System Problem

Re: Android on N810 File System Problem

[Dirk Behme]

Jonathan,

CCing OMAP mailing list, there are more people to help.

Jonathan Herriott wrote:
> Hi,
> 
> I'm trying to get android installed on an N810.  I have successfully
> installed the kernel, 

Which kernel (2.6.x, x == ?)  do you use on N810? If I remember 
correctly, with N810 people use an older kernel than the one coming 
with Android SDK.

> but I am having major issues with the file
> system.  I followed the tutorial you provided at
> http://elinux.org/Android_on_OMAP, but I get a segmentation fault when
> I try to init the kernel.  I made sure to use the same android SDK
> version that was used to patch the kernel.
> 
> My steps for reproduction are:
> 
> 1) On my computer, unpack the ramdisk image to a folder.
> 2) Untar system, dev, and data to the unpacked ramdisk image.
> 3) Tar up the patched file system and scp it to /opt on the device.
> Ssh to the device and unpack the file system in /opt
> 4) Run umask 000 && chroot /opt/android /init
> 5) Receive a segmentation fault.

Can you send us the complete segementation fault output?

Regards

Dirk

Re: Android on N810 File System Problem

[Igor Stoppa]

On Fri, 2008-04-25 at 21:36 +0300, ext Felipe Balbi wrote:

> Current linux-omap's head has all the necessary pieces to get n810
> working. 

Somehow.

> Touchscreen, keypad, ambient light sensor, led, usb, everything
> is there.

You forget power management. It should partially be redone together with
the omap3 work, but stuff like DVFS has a quite different implementation
due to the different capabilities of the implementations.

> Maybe it's easier to get android's patches on top of current linux-omap
> ?

For any practical case where the device has to be used as mobile
platform I think it's not an option to use the current l-o.

Hopefully it will be in the future.

-- 
Cheers, Igor

---

Igor Stoppa
Next Generation Software
Nokia Devices R&D - Helsinki

Re: Android on N810 File System Problem

[Felipe Balbi]

On Fri, Apr 25, 2008 at 07:42:52AM +0200, Dirk Behme wrote:
> Jonathan,
>
> CCing OMAP mailing list, there are more people to help.
>
> Jonathan Herriott wrote:
>> Hi,
>>
>> I'm trying to get android installed on an N810.  I have successfully
>> installed the kernel, 
>
> Which kernel (2.6.x, x == ?)  do you use on N810? If I remember  
> correctly, with N810 people use an older kernel than the one coming with 
> Android SDK.
>
>> but I am having major issues with the file
>> system.  I followed the tutorial you provided at
>> http://elinux.org/Android_on_OMAP, but I get a segmentation fault when
>> I try to init the kernel.  I made sure to use the same android SDK
>> version that was used to patch the kernel.
>>
>> My steps for reproduction are:
>>
>> 1) On my computer, unpack the ramdisk image to a folder.
>> 2) Untar system, dev, and data to the unpacked ramdisk image.
>> 3) Tar up the patched file system and scp it to /opt on the device.
>> Ssh to the device and unpack the file system in /opt
>> 4) Run umask 000 && chroot /opt/android /init
>> 5) Receive a segmentation fault.
>
> Can you send us the complete segementation fault output?

Current linux-omap's head has all the necessary pieces to get n810
working. Touchscreen, keypad, ambient light sensor, led, usb, everything
is there.

Maybe it's easier to get android's patches on top of current linux-omap
?

but anyway, it seems that you don't have android's fs support on your
kernel... Are you getting a "VFS: could not mount root" or something
like that?

-- 
Best Regards,

Felipe Balbi
me@felipebalbi.com
http://blog.felipebalbi.com

Re: Android on N810 File System Problem

[Igor Stoppa]

On Fri, 2008-04-25 at 21:52 +0300, ext Felipe Balbi wrote:
> On Fri, Apr 25, 2008 at 09:31:42PM +0300, Igor Stoppa wrote:
> 
> > You forget power management. It should partially be redone together with
> > the omap3 work, but stuff like DVFS has a quite different implementation
> > due to the different capabilities of the implementations.
> 
> no comments.

since you have a both TRMs, you can check it by yourself: DMA stalling
is not available in 2420

> > > Maybe it's easier to get android's patches on top of current linux-omap
> > > ?
> > 
> > For any practical case where the device has to be used as mobile
> > platform I think it's not an option to use the current l-o.
> 
> For some experiments with android is good enough.

maybe ... i'm not the one experimenting, i'm just saying that it's
better to get a bunch of charged batteries, in case one wants to carry
the tablet around.

> > Hopefully it will be in the future.
> 
> as soon as people start releasing code...

in case you haven't noticed, there's some major rework ongoing for power
management

as i said, hopefully in the future also n810 will benefit from it

-- 
Cheers, Igor

---

Igor Stoppa
Next Generation Software
Nokia Devices R&D - Helsinki

Re: Android on N810 File System Problem

[Felipe Balbi]

On Fri, Apr 25, 2008 at 09:31:42PM +0300, Igor Stoppa wrote:

> You forget power management. It should partially be redone together with
> the omap3 work, but stuff like DVFS has a quite different implementation
> due to the different capabilities of the implementations.

no comments.

> > Maybe it's easier to get android's patches on top of current linux-omap
> > ?
> 
> For any practical case where the device has to be used as mobile
> platform I think it's not an option to use the current l-o.

For some experiments with android is good enough.

> Hopefully it will be in the future.

as soon as people start releasing code...

-- 
Best Regards,

Felipe Balbi
me@felipebalbi.com
http://blog.felipebalbi.com

Re: Android on N810 File System Problem

[Jonathan Herriott]

I'm using vanilla Kernel 2.6.21.0 with the patch from
http://android-on-n8xx.googlecode.com/files/linux-2.6.21_rx-34_android-m5-rc14.bz2.
 I was told in another thread that I need to use the m3 userspace
files, but when trying to use those, I have the same issue.

I'm assuming you want the strace when running init:

\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,
path=@property_service}, 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


Thanks,
Jonathan

On Thu, Apr 24, 2008 at 10:42 PM, Dirk Behme <dirk.behme@googlemail.com> wrote:
> Jonathan,
>
>  CCing OMAP mailing list, there are more people to help.
>
>
>  Jonathan Herriott wrote:
>
> > Hi,
> >
> > I'm trying to get android installed on an N810.  I have successfully
> > installed the kernel,
> >
>
>  Which kernel (2.6.x, x == ?)  do you use on N810? If I remember correctly,
> with N810 people use an older kernel than the one coming with Android SDK.
>
>
>
> > but I am having major issues with the file
> > system.  I followed the tutorial you provided at
> > http://elinux.org/Android_on_OMAP, but I get a segmentation fault when
> > I try to init the kernel.  I made sure to use the same android SDK
> > version that was used to patch the kernel.
> >
> > My steps for reproduction are:
> >
> > 1) On my computer, unpack the ramdisk image to a folder.
> > 2) Untar system, dev, and data to the unpacked ramdisk image.
> > 3) Tar up the patched file system and scp it to /opt on the device.
> > Ssh to the device and unpack the file system in /opt
> > 4) Run umask 000 && chroot /opt/android /init
> > 5) Receive a segmentation fault.
> >
>
>  Can you send us the complete segementation fault output?
>
>  Regards
>
>  Dirk
>
>
>

Re: Android on N810 File System Problem

[Felipe Balbi]

On Fri, Apr 25, 2008 at 09:47:09PM +0300, Igor Stoppa wrote:
> On Fri, 2008-04-25 at 21:52 +0300, ext Felipe Balbi wrote:
> > On Fri, Apr 25, 2008 at 09:31:42PM +0300, Igor Stoppa wrote:
> > 
> > > You forget power management. It should partially be redone together with
> > > the omap3 work, but stuff like DVFS has a quite different implementation
> > > due to the different capabilities of the implementations.
> > 
> > no comments.
> 
> since you have a both TRMs, you can check it by yourself: DMA stalling
> is not available in 2420
> 
> > > > Maybe it's easier to get android's patches on top of current linux-omap
> > > > ?
> > > 
> > > For any practical case where the device has to be used as mobile
> > > platform I think it's not an option to use the current l-o.
> > 
> > For some experiments with android is good enough.
> 
> maybe ... i'm not the one experimenting, i'm just saying that it's
> better to get a bunch of charged batteries, in case one wants to carry
> the tablet around.

true

> 
> > > Hopefully it will be in the future.
> > 
> > as soon as people start releasing code...
> 
> in case you haven't noticed, there's some major rework ongoing for power
> management
> 
> as i said, hopefully in the future also n810 will benefit from it

Agreed here.

-- 
Best Regards,

Felipe Balbi
me@felipebalbi.com
http://blog.felipebalbi.com

Re: Android on N810 File System Problem

[Jonathan Herriott]

I forgot to ask.  Am I required to put the userspace files on separate
storage, or is it okay sticking it on the device's local file system?

On 4/25/08, Jonathan Herriott <herriojr@gmail.com> wrote:
> I'm using vanilla Kernel 2.6.21.0 with the patch from
>  http://android-on-n8xx.googlecode.com/files/linux-2.6.21_rx-34_android-m5-rc14.bz2.
>   I was told in another thread that I need to use the m3 userspace
>  files, but when trying to use those, I have the same issue.
>
>  I'm assuming you want the strace when running init:
>
>  \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,
>  path=@property_service}, 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
>
>
>  Thanks,
>
> Jonathan
>
>
>  On Thu, Apr 24, 2008 at 10:42 PM, Dirk Behme <dirk.behme@googlemail.com> wrote:
>  > Jonathan,
>  >
>  >  CCing OMAP mailing list, there are more people to help.
>  >
>  >
>  >  Jonathan Herriott wrote:
>  >
>  > > Hi,
>  > >
>  > > I'm trying to get android installed on an N810.  I have successfully
>  > > installed the kernel,
>  > >
>  >
>  >  Which kernel (2.6.x, x == ?)  do you use on N810? If I remember correctly,
>  > with N810 people use an older kernel than the one coming with Android SDK.
>  >
>  >
>  >
>  > > but I am having major issues with the file
>  > > system.  I followed the tutorial you provided at
>  > > http://elinux.org/Android_on_OMAP, but I get a segmentation fault when
>  > > I try to init the kernel.  I made sure to use the same android SDK
>  > > version that was used to patch the kernel.
>  > >
>  > > My steps for reproduction are:
>  > >
>  > > 1) On my computer, unpack the ramdisk image to a folder.
>  > > 2) Untar system, dev, and data to the unpacked ramdisk image.
>  > > 3) Tar up the patched file system and scp it to /opt on the device.
>  > > Ssh to the device and unpack the file system in /opt
>  > > 4) Run umask 000 && chroot /opt/android /init
>  > > 5) Receive a segmentation fault.
>  > >
>  >
>  >  Can you send us the complete segementation fault output?
>  >
>  >  Regards
>  >
>  >  Dirk
>  >
>  >
>  >
>

Re: Android on N810 File System Problem

[Dirk Behme]

Jonathan Herriott wrote:
> I'm using vanilla Kernel 2.6.21.0 with the patch from
> http://android-on-n8xx.googlecode.com/files/linux-2.6.21_rx-34_android-m5-rc14.bz2.
>  I was told in another thread that I need to use the m3 userspace
> files, but when trying to use those, I have the same issue.
> 
> I'm assuming you want the strace when running init:
> 
> \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,
> path=@property_service}, 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

Mmh, there are some reports on this list with similar SIGSEGV:

http://marc.info/?l=linux-omap&m=120393103218574&w=2
http://marc.info/?l=linux-omap&m=120400327301855&w=2
http://marc.info/?l=linux-omap&m=120834030203728&w=2

But It doesn't look like the archives have a detailed solution for 
this. Seems that changing some parameters (e.g. switching to other 
binder driver, SDK etc.) made the error go away.

I'm CCing Anil and colorant, maybe they remember what helped.

Dirk

> On Thu, Apr 24, 2008 at 10:42 PM, Dirk Behme <dirk.behme@googlemail.com> wrote:
> 
>>Jonathan,
>>
>> CCing OMAP mailing list, there are more people to help.
>>
>>
>> Jonathan Herriott wrote:
>>
>>
>>>Hi,
>>>
>>>I'm trying to get android installed on an N810.  I have successfully
>>>installed the kernel,
>>>
>>
>> Which kernel (2.6.x, x == ?)  do you use on N810? If I remember correctly,
>>with N810 people use an older kernel than the one coming with Android SDK.
>>
>>
>>
>>
>>>but I am having major issues with the file
>>>system.  I followed the tutorial you provided at
>>>http://elinux.org/Android_on_OMAP, but I get a segmentation fault when
>>>I try to init the kernel.  I made sure to use the same android SDK
>>>version that was used to patch the kernel.
>>>
>>>My steps for reproduction are:
>>>
>>>1) On my computer, unpack the ramdisk image to a folder.
>>>2) Untar system, dev, and data to the unpacked ramdisk image.
>>>3) Tar up the patched file system and scp it to /opt on the device.
>>>Ssh to the device and unpack the file system in /opt
>>>4) Run umask 000 && chroot /opt/android /init
>>>5) Receive a segmentation fault.
>>>
>>
>> Can you send us the complete segementation fault output?
>>
>> Regards
>>
>> Dirk
>>
>>
>>
> 
> 

Re: Android on N810 File System Problem

[Jonathan Herriott]

I had it confirmed in another thread that the issue is that the local
filesystem for the N810 is jffs, which is unsupported and I need to
install it on an mini SD card with ext2/ext3 on it.

On 4/26/08, Dirk Behme <dirk.behme@googlemail.com> wrote:
> Jonathan Herriott wrote:
>
> > I'm using vanilla Kernel 2.6.21.0 with the patch from
> >
> http://android-on-n8xx.googlecode.com/files/linux-2.6.21_rx-34_android-m5-rc14.bz2.
> >  I was told in another thread that I need to use the m3 userspace
> > files, but when trying to use those, I have the same issue.
> >
> > I'm assuming you want the strace when running init:
> >
> > \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,
> > path=@property_service}, 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
> >
>
>  Mmh, there are some reports on this list with similar SIGSEGV:
>
>  http://marc.info/?l=linux-omap&m=120393103218574&w=2
>  http://marc.info/?l=linux-omap&m=120400327301855&w=2
>  http://marc.info/?l=linux-omap&m=120834030203728&w=2
>
>  But It doesn't look like the archives have a detailed solution for this.
> Seems that changing some parameters (e.g. switching to other binder driver,
> SDK etc.) made the error go away.
>
>  I'm CCing Anil and colorant, maybe they remember what helped.
>
>  Dirk
>
>
>
> > On Thu, Apr 24, 2008 at 10:42 PM, Dirk Behme <dirk.behme@googlemail.com>
> wrote:
> >
> >
> > > Jonathan,
> > >
> > > CCing OMAP mailing list, there are more people to help.
> > >
> > >
> > > Jonathan Herriott wrote:
> > >
> > >
> > >
> > > > Hi,
> > > >
> > > > I'm trying to get android installed on an N810.  I have successfully
> > > > installed the kernel,
> > > >
> > > >
> > >
> > > Which kernel (2.6.x, x == ?)  do you use on N810? If I remember
> correctly,
> > > with N810 people use an older kernel than the one coming with Android
> SDK.
> > >
> > >
> > >
> > >
> > >
> > > > but I am having major issues with the file
> > > > system.  I followed the tutorial you provided at
> > > > http://elinux.org/Android_on_OMAP, but I get a
> segmentation fault when
> > > > I try to init the kernel.  I made sure to use the same android SDK
> > > > version that was used to patch the kernel.
> > > >
> > > > My steps for reproduction are:
> > > >
> > > > 1) On my computer, unpack the ramdisk image to a folder.
> > > > 2) Untar system, dev, and data to the unpacked ramdisk image.
> > > > 3) Tar up the patched file system and scp it to /opt on the device.
> > > > Ssh to the device and unpack the file system in /opt
> > > > 4) Run umask 000 && chroot /opt/android /init
> > > > 5) Receive a segmentation fault.
> > > >
> > > >
> > >
> > > Can you send us the complete segementation fault output?
> > >
> > > Regards
> > >
> > > Dirk
> > >
> > >
> > >
> > >
> >
> >
> >
>
>

Re: Android on N810 File System Problem

[Dirk Behme]

Jonathan Herriott wrote:
> I had it confirmed in another thread

Any pointer to this thread?

Thanks

Dirk

>  that the issue is that the local
> filesystem for the N810 is jffs, which is unsupported and I need to
> install it on an mini SD card with ext2/ext3 on it.
> 
> On 4/26/08, Dirk Behme <dirk.behme@googlemail.com> wrote:
> 
>>Jonathan Herriott wrote:
>>
>>
>>>I'm using vanilla Kernel 2.6.21.0 with the patch from
>>>
>>
>>http://android-on-n8xx.googlecode.com/files/linux-2.6.21_rx-34_android-m5-rc14.bz2.
>>
>>> I was told in another thread that I need to use the m3 userspace
>>>files, but when trying to use those, I have the same issue.
>>>
>>>I'm assuming you want the strace when running init:
>>>
>>>\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,
>>>path=@property_service}, 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
>>>
>>
>> Mmh, there are some reports on this list with similar SIGSEGV:
>>
>> http://marc.info/?l=linux-omap&m=120393103218574&w=2
>> http://marc.info/?l=linux-omap&m=120400327301855&w=2
>> http://marc.info/?l=linux-omap&m=120834030203728&w=2
>>
>> But It doesn't look like the archives have a detailed solution for this.
>>Seems that changing some parameters (e.g. switching to other binder driver,
>>SDK etc.) made the error go away.
>>
>> I'm CCing Anil and colorant, maybe they remember what helped.
>>
>> Dirk
>>
>>
>>
>>
>>>On Thu, Apr 24, 2008 at 10:42 PM, Dirk Behme <dirk.behme@googlemail.com>
>>
>>wrote:
>>
>>>
>>>>Jonathan,
>>>>
>>>>CCing OMAP mailing list, there are more people to help.
>>>>
>>>>
>>>>Jonathan Herriott wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>I'm trying to get android installed on an N810.  I have successfully
>>>>>installed the kernel,
>>>>>
>>>>>
>>>>
>>>>Which kernel (2.6.x, x == ?)  do you use on N810? If I remember
>>
>>correctly,
>>
>>>>with N810 people use an older kernel than the one coming with Android
>>
>>SDK.
>>
>>>>
>>>>
>>>>
>>>>
>>>>>but I am having major issues with the file
>>>>>system.  I followed the tutorial you provided at
>>>>>http://elinux.org/Android_on_OMAP, but I get a
>>
>>segmentation fault when
>>
>>>>>I try to init the kernel.  I made sure to use the same android SDK
>>>>>version that was used to patch the kernel.
>>>>>
>>>>>My steps for reproduction are:
>>>>>
>>>>>1) On my computer, unpack the ramdisk image to a folder.
>>>>>2) Untar system, dev, and data to the unpacked ramdisk image.
>>>>>3) Tar up the patched file system and scp it to /opt on the device.
>>>>>Ssh to the device and unpack the file system in /opt
>>>>>4) Run umask 000 && chroot /opt/android /init
>>>>>5) Receive a segmentation fault.
>>>>>
>>>>>
>>>>
>>>>Can you send us the complete segementation fault output?
>>>>
>>>>Regards
>>>>
>>>>Dirk
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
> 

Re: Android on N810 File System Problem

[Jonathan Herriott]

http://groups.google.com/group/android-internals/browse_thread/thread/7028432fa76f57e8/71709fc4adcb2ddd

On 4/26/08, Dirk Behme <dirk.behme@googlemail.com> wrote:
> Jonathan Herriott wrote:
>
> > I had it confirmed in another thread
> >
>
>  Any pointer to this thread?
>
>  Thanks
>
>  Dirk
>
>
>
> >  that the issue is that the local
> > filesystem for the N810 is jffs, which is unsupported and I need to
> > install it on an mini SD card with ext2/ext3 on it.
> >
> > On 4/26/08, Dirk Behme <dirk.behme@googlemail.com> wrote:
> >
> >
> > > Jonathan Herriott wrote:
> > >
> > >
> > >
> > > > I'm using vanilla Kernel 2.6.21.0 with the patch from
> > > >
> > > >
> > >
> > >
> http://android-on-n8xx.googlecode.com/files/linux-2.6.21_rx-34_android-m5-rc14.bz2.
> > >
> > >
> > > > I was told in another thread that I need to use the m3 userspace
> > > > files, but when trying to use those, I have the same issue.
> > > >
> > > > I'm assuming you want the strace when running init:
> > > >
> > > > \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,
> > > > path=@property_service}, 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
> > > >
> > > >
> > >
> > > Mmh, there are some reports on this list with similar SIGSEGV:
> > >
> > > http://marc.info/?l=linux-omap&m=120393103218574&w=2
> > > http://marc.info/?l=linux-omap&m=120400327301855&w=2
> > > http://marc.info/?l=linux-omap&m=120834030203728&w=2
> > >
> > > But It doesn't look like the archives have a detailed solution for this.
> > > Seems that changing some parameters (e.g. switching to other binder
> driver,
> > > SDK etc.) made the error go away.
> > >
> > > I'm CCing Anil and colorant, maybe they remember what helped.
> > >
> > > Dirk
> > >
> > >
> > >
> > >
> > >
> > > > On Thu, Apr 24, 2008 at 10:42 PM, Dirk Behme
> <dirk.behme@googlemail.com>
> > > >
> > >
> > > wrote:
> > >
> > >
> > > >
> > > >
> > > > > Jonathan,
> > > > >
> > > > > CCing OMAP mailing list, there are more people to help.
> > > > >
> > > > >
> > > > > Jonathan Herriott wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm trying to get android installed on an N810.  I have
> successfully
> > > > > > installed the kernel,
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > Which kernel (2.6.x, x == ?)  do you use on N810? If I remember
> > > > >
> > > >
> > >
> > > correctly,
> > >
> > >
> > > >
> > > > > with N810 people use an older kernel than the one coming with
> Android
> > > > >
> > > >
> > >
> > > SDK.
> > >
> > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > but I am having major issues with the file
> > > > > > system.  I followed the tutorial you provided at
> > > > > > http://elinux.org/Android_on_OMAP, but I get a
> > > > > >
> > > > >
> > > >
> > >
> > > segmentation fault when
> > >
> > >
> > > >
> > > > >
> > > > > > I try to init the kernel.  I made sure to use the same android SDK
> > > > > > version that was used to patch the kernel.
> > > > > >
> > > > > > My steps for reproduction are:
> > > > > >
> > > > > > 1) On my computer, unpack the ramdisk image to a folder.
> > > > > > 2) Untar system, dev, and data to the unpacked ramdisk image.
> > > > > > 3) Tar up the patched file system and scp it to /opt on the
> device.
> > > > > > Ssh to the device and unpack the file system in /opt
> > > > > > 4) Run umask 000 && chroot /opt/android /init
> > > > > > 5) Receive a segmentation fault.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > Can you send us the complete segementation fault output?
> > > > >
> > > > > Regards
> > > > >
> > > > > Dirk
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Re: Android on N810 File System Problem

[Kalle Valo]

"ext Felipe Balbi" <me@felipebalbi.com> writes:

> Current linux-omap's head has all the necessary pieces to get n810
> working. Touchscreen, keypad, ambient light sensor, led, usb, everything
> is there.

What about sound?

-- 
Kalle Valo

Re: Android on N810 File System Problem

[Felipe Balbi]

On Sun, Apr 27, 2008 at 12:43:19PM +0300, Kalle Valo wrote:
> "ext Felipe Balbi" <me@felipebalbi.com> writes:
> 
> > Current linux-omap's head has all the necessary pieces to get n810
> > working. Touchscreen, keypad, ambient light sensor, led, usb, everything
> > is there.
> 
> What about sound?

I'm sure it'll come from alsa-devel soon.

-- 
Best Regards,

Felipe Balbi
me@felipebalbi.com
http://blog.felipebalbi.com

Re: Android on N810 File System Problem

[Igor Stoppa]

On Mon, 2008-04-28 at 01:32 +0300, ext Felipe Balbi wrote:
> On Sun, Apr 27, 2008 at 12:43:19PM +0300, Kalle Valo wrote:
> > "ext Felipe Balbi" <me@felipebalbi.com> writes:
> > 
> > > Current linux-omap's head has all the necessary pieces to get n810
> > > working. Touchscreen, keypad, ambient light sensor, led, usb, everything
> > > is there.
> > 
> > What about sound?
> 
> I'm sure it'll come from alsa-devel soon.

I also wonder if any kernel to userspace interface has changed since we
released the FW: that could compromise the execution of system services.

It would be probably good to check if any "obsolete interface" option
has to be enabled when configuring the new kernel.

-- 
Cheers, Igor

---

Igor Stoppa
Next Generation Software
Nokia Devices R&D - Helsinki

Re: Android on N810 File System Problem

[Jarkko Nikula]

On Mon, 28 Apr 2008 02:04:17 +0300
"ext Igor Stoppa" <igor.stoppa@nokia.com> wrote:

> > > What about sound?
> > 
> > I'm sure it'll come from alsa-devel soon.
> 
> I also wonder if any kernel to userspace interface has changed since
> we released the FW: that could compromise the execution of system
> services.
> 
Note that my native ALSA implementation doesn't work with our OS200x
because it's using GStreamer - DSP GW - DSP centric audio architecture
[1]. However, I think it should be possible to build GStreamer to run on
top of my work since x86 SDK build is using native ALSA and OSS drivers.

But I assume Android folks doesn't have this restriction :-)


Jarkko

1.
http://maemo.org/development/documentation/how-tos/3-x/multimedia_architecture.html

Re: Android on N810 File System Problem

[Tony Lindgren]

* Felipe Balbi <me@felipebalbi.com> [080427 15:31]:
> On Sun, Apr 27, 2008 at 12:43:19PM +0300, Kalle Valo wrote:
> > "ext Felipe Balbi" <me@felipebalbi.com> writes:
> > 
> > > Current linux-omap's head has all the necessary pieces to get n810
> > > working. Touchscreen, keypad, ambient light sensor, led, usb, everything
> > > is there.
> > 
> > What about sound?
> 
> I'm sure it'll come from alsa-devel soon.

I've merged Jarkko's asoc patch to linux-omap for testing. Have not
gotten any sound out of it on my n810 though.. Maybe some alsamixer
settings issue?

Kalle, do you have any tips on getting WLAN to work on n8x0?

Don't know if there's anything new there to you, but I posted some
info on getting things to work with current linux-omap kernel at:

http://www.muru.com/linux/n8x0/

Regards,

Tony

Re: Android on N810 File System Problem

[Brian Swetland]

[Tony Lindgren <tony@atomide.com>]
> 
> I've merged Jarkko's asoc patch to linux-omap for testing. Have not
> gotten any sound out of it on my n810 though.. Maybe some alsamixer
> settings issue?
> 
> Kalle, do you have any tips on getting WLAN to work on n8x0?

This was the show-stopper for me.  When I last got things hobbling
along on n8x0, the binary-only wlan module was incompatible with
newer kernels than 2.6.21 (changes in some network data structures).

The newer android builds expect 2.6.24 or more recent.  I'm hoping
that Nokia will release a newer build of the wlan module for 2.6.24
at some point.  That'd be a big motivator for me to spend time hacking
on the platform again.

The other thing I'd like to sort out is how to interact with the
battery charging and status without needing proprietary userspace
code.  Probably a lot easier to reverse engineer than the wlan driver
at least.

Brian

Re: Android on N810 File System Problem

[Brian Swetland]

[Jonathan Herriott <herriojr@gmail.com>]
> I had it confirmed in another thread that the issue is that the local
> filesystem for the N810 is jffs, which is unsupported and I need to
> install it on an mini SD card with ext2/ext3 on it.

I think what you're seeing here is the property service in init
failing to create and mmap it's arena, which it tries to do in /,
which in our world is initramfs.  The android init/boot model is a
little different in that we don't pivot over to a root filesystem,
we mount the system, data, etc partitions under the ramfs on /

You might be able to hack around this by editing the string
"/system_properties" to "/tmp/em_properties" or something like
that, assuming you have tmpfs mounted on /tmp.

Brian

> On 4/26/08, Dirk Behme <dirk.behme@googlemail.com> wrote:
> > Jonathan Herriott wrote:
> >
> > > I'm using vanilla Kernel 2.6.21.0 with the patch from
> > >
> > http://android-on-n8xx.googlecode.com/files/linux-2.6.21_rx-34_android-m5-rc14.bz2.
> > >  I was told in another thread that I need to use the m3 userspace
> > > files, but when trying to use those, I have the same issue.
> > >
> > > I'm assuming you want the strace when running init:
> > >
> > > \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,
> > > path=@property_service}, 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
> > >
> >
> >  Mmh, there are some reports on this list with similar SIGSEGV:
> >
> >  http://marc.info/?l=linux-omap&m=120393103218574&w=2
> >  http://marc.info/?l=linux-omap&m=120400327301855&w=2
> >  http://marc.info/?l=linux-omap&m=120834030203728&w=2
> >
> >  But It doesn't look like the archives have a detailed solution for this.
> > Seems that changing some parameters (e.g. switching to other binder driver,
> > SDK etc.) made the error go away.
> >
> >  I'm CCing Anil and colorant, maybe they remember what helped.
> >
> >  Dirk
> >
> >
> >
> > > On Thu, Apr 24, 2008 at 10:42 PM, Dirk Behme <dirk.behme@googlemail.com>
> > wrote:
> > >
> > >
> > > > Jonathan,
> > > >
> > > > CCing OMAP mailing list, there are more people to help.
> > > >
> > > >
> > > > Jonathan Herriott wrote:
> > > >
> > > >
> > > >
> > > > > Hi,
> > > > >
> > > > > I'm trying to get android installed on an N810.  I have successfully
> > > > > installed the kernel,
> > > > >
> > > > >
> > > >
> > > > Which kernel (2.6.x, x == ?)  do you use on N810? If I remember
> > correctly,
> > > > with N810 people use an older kernel than the one coming with Android
> > SDK.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > > but I am having major issues with the file
> > > > > system.  I followed the tutorial you provided at
> > > > > http://elinux.org/Android_on_OMAP, but I get a
> > segmentation fault when
> > > > > I try to init the kernel.  I made sure to use the same android SDK
> > > > > version that was used to patch the kernel.
> > > > >
> > > > > My steps for reproduction are:
> > > > >
> > > > > 1) On my computer, unpack the ramdisk image to a folder.
> > > > > 2) Untar system, dev, and data to the unpacked ramdisk image.
> > > > > 3) Tar up the patched file system and scp it to /opt on the device.
> > > > > Ssh to the device and unpack the file system in /opt
> > > > > 4) Run umask 000 && chroot /opt/android /init
> > > > > 5) Receive a segmentation fault.
> > > > >
> > > > >
> > > >
> > > > Can you send us the complete segementation fault output?
> > > >
> > > > Regards
> > > >
> > > > Dirk
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Android on N810 File System Problem

[Jarkko Nikula]

On Mon, 28 Apr 2008 16:38:28 -0700
"ext Tony Lindgren" <tony@atomide.com> wrote:

> I've merged Jarkko's asoc patch to linux-omap for testing. Have not
> gotten any sound out of it on my n810 though.. Maybe some alsamixer
> settings issue?
> 
Have you set CONFIG_OMAP_MUX? Otherwise McBSP2 pins are muxed for EAC
block by the bootloader.


Jarkko

Re: Questions on Android

[Brian Swetland]

[Anil S <anils@mistralsolutions.com>]
> Hello Brian,
> 
> 	It would be really great if you could share thoughts on the
> questions given here on Android:
> 
> I was able to add support for the keypad, touch and network in Android,
> however the interfaces like GPS, Accelerometer, vibrator, hardware 3D
> acceleration, battery etc. are not integrated with Android right now. I
> would appreciate if you could throw some light on these open issues. How
> exactly can these interfaces be integrated with Android? 

We're trying to use the standard kernel/driver interfaces when possible,
but for things that may have a good deal of variation in implementation,
we're looking to provide a very thin "hardware interface library" layer
to adapt between the bottom of the userspace stack and the drivers or
whatnot for specific hardware platforms.  

We'll continue to adopt standardized kernel solutions as they become
available -- We're now using the power supply framework in 2.6.24 for
monitoring battery/charge state (post M5 SDK -- it'll be in the next 
release), for example.

Brian

Re: Android on N810 File System Problem

[Jonathan Herriott]

I actually have another issue, but I don't know if it should still be
in this thread or not.  Anyways, start android, but it just stays on
the red oscillating eye forever.  When I start it the a.sh way, I get
the following output:

/start_android.sh
+ echo Starting Android...
Starting Android...
+ rm -f /media/mmc1/tmp/android-SurfaceFlingerSynchro
/media/mmc1/tmp/contacts_presence.db /media/mmc1/tmp/im_transient.db
/media/mmc1/tmp/messagebus.pid /media/mmc1/tmp/system_bus_socket
+ umount -l /proc
+ umount -l /sys
+ mount -t proc proc /media/mmc1/proc
+ mount -t sysfs sysfs /media/mmc1/sys
+ umask 000
+ chroot /media/mmc1 /a.sh
+ export PATH=/sbin:/system/sbin:/system/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
+ 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
+ /system/bin/app_process -Xzygote /system/bin --zygote
+ /system/bin/dbus-daemon --system
+ runtime
+ /system/bin/sh
\h:\w\$ ******** NO FRAMEBUFFER VSYNC WAIT IOCTL **************
 Prepping: /system/app/AlarmProvider.apk:/system/app/Browser.apk:/system/app/Calendar.apk:/system/app/Camera.apk:/system/app/Contacts.apk:/system/app/Development.apk:/system/app/GDataFeedsProvider.apk:/system/app/Gmail.apk:/system/app/GmailProvider.apk:/system/app/GoogleApps.apk:/system/app/GoogleAppsProvider.apk:/system/app/Home.apk:/system/app/ImProvider.apk:/system/app/Maps.apk:/system/app/MediaPickerActivity.apk:/system/app/MediaProvider.apk:/system/app/Phone.apk:/system/app/PimProvider.apk:/system/app/ApiDemos.apk:/system/app/SettingsProvider.apk:/system/app/Sms.apk:/system/app/SyncProvider.apk:/system/app/TelephonyProvider.apk:/system/app/XmppService.apk:/system/app/YouTube.apk
File not found: /system/app/AlarmProvider.apk
File not found: /system/app/Calendar.apk
File not found: /system/app/Camera.apk
File not found: /system/app/GDataFeedsProvider.apk
File not found: /system/app/Gmail.apk
File not found: /system/app/GmailProvider.apk
File not found: /system/app/MediaPickerActivity.apk
File not found: /system/app/PimProvider.apk
File not found: /system/app/ApiDemos.apk
File not found: /system/app/Sms.apk
File not found: /system/app/SyncProvider.apk
File not found: /system/app/YouTube.apk
 Prep complete
fatal error opening "/sys/android_power/last_user_activity"

Does anyone happen to have the patch for this?  Apparently the patch I
received from the N8XX site does not contain it.

On Tue, Apr 29, 2008 at 2:49 AM, Jarkko Nikula <jarkko.nikula@nokia.com> wrote:
> On Mon, 28 Apr 2008 16:38:28 -0700
>  "ext Tony Lindgren" <tony@atomide.com> wrote:
>
>  > I've merged Jarkko's asoc patch to linux-omap for testing. Have not
>  > gotten any sound out of it on my n810 though.. Maybe some alsamixer
>  > settings issue?
>  >
>  Have you set CONFIG_OMAP_MUX? Otherwise McBSP2 pins are muxed for EAC
>  block by the bootloader.
>
>
>  Jarkko
>

Re: Android on N810 File System Problem

[Tony Lindgren]

* Jarkko Nikula <jarkko.nikula@nokia.com> [080429 02:49]:
> On Mon, 28 Apr 2008 16:38:28 -0700
> "ext Tony Lindgren" <tony@atomide.com> wrote:
> 
> > I've merged Jarkko's asoc patch to linux-omap for testing. Have not
> > gotten any sound out of it on my n810 though.. Maybe some alsamixer
> > settings issue?
> > 
> Have you set CONFIG_OMAP_MUX? Otherwise McBSP2 pins are muxed for EAC
> block by the bootloader.

Cool yeah that was it! Playing with mpg123 now :) I also updated the
config on my website for to enable muxing.

Tony

Re: Android on N810 File System Problem

[Kalle Valo]

"ext Tony Lindgren" <tony@atomide.com> writes:

> * Felipe Balbi <me@felipebalbi.com> [080427 15:31]:
>> On Sun, Apr 27, 2008 at 12:43:19PM +0300, Kalle Valo wrote:
>> > "ext Felipe Balbi" <me@felipebalbi.com> writes:
>> > 
>> > > Current linux-omap's head has all the necessary pieces to get n810
>> > > working. Touchscreen, keypad, ambient light sensor, led, usb, everything
>> > > is there.
>> > 
>> > What about sound?
>> 
>> I'm sure it'll come from alsa-devel soon.
>
> I've merged Jarkko's asoc patch to linux-omap for testing. Have not
> gotten any sound out of it on my n810 though.. Maybe some alsamixer
> settings issue?
>
> Kalle, do you have any tips on getting WLAN to work on n8x0?

Unfortunately no. It's not a big task, but proprietary umac.ko is the
biggest problem. It needs to be recompiled.

> Don't know if there's anything new there to you, but I posted some
> info on getting things to work with current linux-omap kernel at:
>
> http://www.muru.com/linux/n8x0/

That's really handy, thanks.

-- 
Kalle Valo

Re: Android on N810 File System Problem

[Kalle Valo]

Brian Swetland <swetland@google.com> writes:

> [Tony Lindgren <tony@atomide.com>]
>> 
>> I've merged Jarkko's asoc patch to linux-omap for testing. Have not
>> gotten any sound out of it on my n810 though.. Maybe some alsamixer
>> settings issue?
>> 
>> Kalle, do you have any tips on getting WLAN to work on n8x0?
>
> This was the show-stopper for me.  When I last got things hobbling
> along on n8x0, the binary-only wlan module was incompatible with
> newer kernels than 2.6.21 (changes in some network data structures).

That's exactly the problem. I have written something about it here:

https://garage.maemo.org/pipermail/cx3110x-devel/2007-December/000007.html

Currently there's nothing I can do to resolve the issue,
unfortunately.

-- 
Kalle Valo

Re: Android on N810 File System Problem

[Brian Swetland]

[Kalle Valo <kalle.valo@nokia.com>]
> Brian Swetland <swetland@google.com> writes:
> >
> > This was the show-stopper for me.  When I last got things hobbling
> > along on n8x0, the binary-only wlan module was incompatible with
> > newer kernels than 2.6.21 (changes in some network data structures).
> 
> That's exactly the problem. I have written something about it here:
> 
> https://garage.maemo.org/pipermail/cx3110x-devel/2007-December/000007.html

Just did a quick diff between v2.6.21 and v2.6.24 and the skbuff changes
are pretty daunting.  Doesn't look like there's an easy hack here...

> Currently there's nothing I can do to resolve the issue, unfortunately.

Pity.  It'd be nice to get newer kernels running on the n8x0 -- it's
nice hardware.

Brian

Re: Android on N810 File System Problem

[Felipe Balbi]

On Wed, 30 Apr 2008 03:20:36 -0700, Brian Swetland <swetland@google.com>
wrote:
> [Kalle Valo <kalle.valo@nokia.com>]
>> Brian Swetland <swetland@google.com> writes:
>> >
>> > This was the show-stopper for me.  When I last got things hobbling
>> > along on n8x0, the binary-only wlan module was incompatible with
>> > newer kernels than 2.6.21 (changes in some network data structures).
>>
>> That's exactly the problem. I have written something about it here:
>>
>>
>
https://garage.maemo.org/pipermail/cx3110x-devel/2007-December/000007.html
> 
> Just did a quick diff between v2.6.21 and v2.6.24 and the skbuff changes
> are pretty daunting.  Doesn't look like there's an easy hack here...
> 
>> Currently there's nothing I can do to resolve the issue, unfortunately.
> 
> Pity.  It'd be nice to get newer kernels running on the n8x0 -- it's
> nice hardware.

eheheh, reverse engineering 2.6.21 driver with a jtag sounds fun :-p

-- 
Best Regards,

Felipe Balbi
http://felipebalbi.com
me@felipebalbi.com

Re: Android on N810 File System Problem

[Kalle Valo]

Brian Swetland <swetland@google.com> writes:

> [Kalle Valo <kalle.valo@nokia.com>]
>> Brian Swetland <swetland@google.com> writes:
>> >
>> > This was the show-stopper for me.  When I last got things hobbling
>> > along on n8x0, the binary-only wlan module was incompatible with
>> > newer kernels than 2.6.21 (changes in some network data structures).
>> 
>> That's exactly the problem. I have written something about it here:
>> 
>> https://garage.maemo.org/pipermail/cx3110x-devel/2007-December/000007.html
>
> Just did a quick diff between v2.6.21 and v2.6.24 and the skbuff changes
> are pretty daunting.  Doesn't look like there's an easy hack here...
>
>> Currently there's nothing I can do to resolve the issue, unfortunately.
>
> Pity.  It'd be nice to get newer kernels running on the n8x0 -- it's
> nice hardware.

Trust me, I share the pain. If a solution comes up, I'll let you know.

It's also a good idea to follow cx3110x-devel:

https://garage.maemo.org/mailman/listinfo/cx3110x-devel

-- 
Kalle Valo

RE: Questions on Android

[shivananda.hebbarp]

 
>[Anil S <anils@mistralsolutions.com>]
> Hello Brian,
> 
> 	It would be really great if you could share thoughts on the
questions 
> given here on Android:
> 
> I was able to add support for the keypad, touch and network in 
> Android, however the interfaces like GPS, Accelerometer, vibrator, 
> hardware 3D acceleration, battery etc. are not integrated with Android

> right now. I would appreciate if you could throw some light on these 
> open issues. How exactly can these interfaces be integrated with
Android?

Hi Anil,

I had reported some Power management behavior after bringing up android
on 2430. Here is the thread .
http://marc.info/?l=linux-omap&m=120948254632401&w=2

Basically the Android GUI comes up and transitions from Active to Sleep
mode happens properly for the first 2 times.(by pressing the up and down
keys).
But the third time ,it never comes from the deep sleep mode. 

Do you any idea about this ?Any inputs on this is highly appreciated.

Regards,
Shivananda

Re: Android on N810 File System Problem

[Dirk Behme]

Brian Swetland wrote:
> [Tony Lindgren <tony@atomide.com>]
> 
>>I've merged Jarkko's asoc patch to linux-omap for testing. Have not
>>gotten any sound out of it on my n810 though.. Maybe some alsamixer
>>settings issue?
>>
>>Kalle, do you have any tips on getting WLAN to work on n8x0?
> 
> This was the show-stopper for me.  When I last got things hobbling
> along on n8x0, the binary-only wlan module was incompatible with
> newer kernels than 2.6.21 (changes in some network data structures).
> 
> The newer android builds expect 2.6.24 or more recent.  I'm hoping
> that Nokia will release a newer build of the wlan module for 2.6.24
> at some point.  That'd be a big motivator for me to spend time hacking
> on the platform again.

Have a look to the section

-- cut --
...

In the end I think what would be realistically possible ...
is that Nokia provides one person whose sole task is to support the
community by mantaining the closed code and providing new binaries that
link against recent libraries. The community would still be able to set
the direction for the development and ask for updates, so that these
closed areas would not hold back work done in the open part. Which is
the majority.

...
-- cut --

of

http://lists.maemo.org/pipermail//maemo-developers/2008-May/017556.html

Maybe you "as community" should "ask for updates" on maemo-developers 
list?

Dirk