The problem can also be on the server side (in most cases it is).
Did you check the firewall running on the server?
On Sat, May 5, 2012 at 8:46 AM, Jiejing.Zhang wrote:
> Hi,
>
> If you modify init.xxx.rc to let it don't mount /system etc, like below.
>
> on fs
> # mount ext4 partitions
> m
Hi,
If you modify init.xxx.rc to let it don't mount /system etc, like below.
on fs
# mount ext4 partitions
mount ext4 /dev/block/mmcblk0p5 /system
mount ext4 /dev/block/mmcblk0p5 /system ro remount
mount ext4 /dev/block/mmcblk0p7 /data nosuid nodev nodiratime noatime
noauto_da_alloc
I have faced this problems some days ago.
In my case the problem was the VMSPLIT2G and VMSPLIT3G kernel
configuration. I had some precompiled libraries with VMSPLIT3G but my
kernel was built with VMSPLIT2G.
By changing it my problem was solved. Please check this link (it is not in
French don't
Hi
I cannot find any thing wrong but this.
Freeing init memory: 156K
init: cannot open '/initlogo.rle'
Kernel panic - not syncing: Attempted to kill init!
Rebooting in 5 seconds..▒▒OK
The kernel source is all the same, the only different is android source
code, is it right?
Please check the a
-Original Message-
> From: Ki Seok Park
> Sender: android-kernel@googlegroups.com
> Date: Mon, 2 Apr 2012 23:03:40
> To: Android Linux Kernel Development
> Reply-To: android-kernel@googlegroups.com
> Cc:
> Subject: [android-kernel] [Kernel PANIC] ANDROID NFS Booting.
>
> host
ups.com
Date: Mon, 2 Apr 2012 23:03:40
To: Android Linux Kernel Development
Reply-To: android-kernel@googlegroups.com
Cc:
Subject: [android-kernel] [Kernel PANIC] ANDROID NFS Booting.
host : ubuntu 10.04 x64
android : google.gingerbread 2.3.3_r1
kernel : android.kernel 2.6.35.7
Hi.
I have a some
host : ubuntu 10.04 x64
android : google.gingerbread 2.3.3_r1
kernel : android.kernel 2.6.35.7
Hi.
I have a some board, using samsung s5pv210.
when Android is booting(on NAND), servicemanager is die.
request_su
