You may be able to reference the init.rc to see which partition is
mounted as /data( by default it seems to be /dev/block/sda8), do you
have the right partition and file system type(ext3)?
--
Chen
On Sat, Apr 25, 2009 at 11:57 PM, FrankieCZ wrote:
>
> Hi all,
>
> I've tried to port Android on my
Problem is solved. I did everything again and problem with dalvik-
cache is not present (seems there was some problem during creating img
file, evenly i've tried it twice...). Now, I have another problem,
which is related to SurfaceFlinger and problem with:
608 E/GLLogger( 441): couldn't load
The libhgl error is harmless, please send us the logcat output and
make sure you are using right frame buffer driver as mentioned in the
wiki
On Apr 25, 2009, at 10:12 AM, FrankieCZ wrote:
>
> Problem is solved. I did everything again and problem with dalvik-
> cache is not present (seems
Hi,
for booting I'm using these cmdline parameters:
console=tty0 console=ttyS1,115200n8 console=tty0
androidboot.hardware=eee_701 vesafb
(during Kernel compilation, VESAFB drivers in menuconfig were
selected. Generally, I've applied all patches provided on the wiki
(except those 2 for atl2 driv
please remove the vesafb in cmdline and append vga=788
and have a try. :)
--
Chen
On Sun, Apr 26, 2009 at 3:57 PM, FrankieCZ wrote:
>
> Hi,
>
> for booting I'm using these cmdline parameters:
>
> console=tty0 console=ttyS1,115200n8 console=tty0
> androidboot.hardware=eee_701 vesafb
>
> (during
Unfortunately, still the same.
I removed vesafb, add vga=788, I can boot and see black screen only
(I'm waiting enough time to be sure that Android GUI will not appear).
I've tried to change vesafb into intelfb (in cmdline), just if
something will change, but nothing.
Obviously, there is some pro
On 4/26/09, FrankieCZ wrote:
>
> Unfortunately, still the same.
> I removed vesafb, add vga=788, I can boot and see black screen only
> (I'm waiting enough time to be sure that Android GUI will not appear).
> I've tried to change vesafb into intelfb (in cmdline), just if
> something will cha
oops, have you compiled the kernel with builtin vesafb?
it is not there by default.
--
Chen
On 4/26/09, FrankieCZ wrote:
>
> Unfortunately, still the same.
> I removed vesafb, add vga=788, I can boot and see black screen only
> (I'm waiting enough time to be sure that Android GUI will not ap
Please also check the content of /proc/fb If u vessfb driver is
installed coreectly, you should see VESA in that file. The
surfaceflinger crash is because it can not find /dev/graphics/fb
during the init process and it is caused by wrong fb driver
installation and configuration.
Please do
I did check of kernel config file, VESA fb. is included in the kernel
for sure. When I do /proc/fb I cannot see VESA, actually, where should
I see it?
It seems VESA fb is included but probably not initialized. I have also
downloaded one Android image (compiled by someone else) and this image
runs
One more question and just a double check --- have you copied bzImage to
vendor/asus/eee_701 after you build the kernel and before you build
installer_img?
On Mon, Apr 27, 2009 at 2:49 AM, FrankieCZ wrote:
>
> I did check of kernel config file, VESA fb. is included in the kernel
> for sure. When
Yes, I have copied bzImage for sure.
I'm still compiling (now I have another problem during compilation but
this is probably related to my Linux envinroment (not enough RAM or
something))...
Frank
On Apr 27, 6:27 pm, Yi Sun wrote:
> One more question and just a double check --- have you copied
I am having this exact same issue. When I boot normally or changing
the boot options to vga=778 the screen resizes but stays black. When I
try vesafb or intelfb it does not resize. This makes me suspect that
the framebuffer is being initialized just something is going wrong. I
know vesa fb is inst
would you like to provide the logcat information? it may not be the fb
related according to your description.
--
Chen
On Sat, May 9, 2009 at 5:17 AM, Kasuko wrote:
>
> I am having this exact same issue. When I boot normally or changing
> the boot options to vga=778 the screen resizes but stays
Is there anyway to get the logcat information without access to
anything. I can't boot into a console. Which seems to mean it probably
isn't related to the fb. H.
On May 8, 9:36 pm, Chen Yang wrote:
> would you like to provide thelogcatinformation? it may not be the fb
> related according to
Use adb logcat.
On May 11, 2:41 pm, Kasuko wrote:
> Is there anyway to get the logcat information without access to
> anything. I can't boot into a console. Which seems to mean it probably
> isn't related to the fb. H.
>
> On May 8, 9:36 pm, Chen Yang wrote:
>
> > would you like to provide
Have you enabled network on your target platform? If yes, you may be able to
use adb to connect it remotely.
According to previous discussion in the thread of eee_701, there were known
problems in framework:
1) preloaded classes
2) battery related problem
http://groups.google.com/group/android-por
I don't have access to a console in the virtual box and I don't think
I can adb from my terminal to the VB installation.
I have to figure out how to boot into console.
On May 11, 9:02 am, Androidphan wrote:
> Use adblogcat.
>
> On May 11, 2:41 pm, Kasuko wrote:
>
> > Is there anyway to get the
I don't have access to a console in the virtual box and I don't think
I can adb from my terminal to the VB installation.
I have to figure out how to boot into console.
On May 11, 9:02 am, Androidphan wrote:
> Use adblogcat.
>
> On May 11, 2:41 pm, Kasuko wrote:
>
> > Is there anyway to get the
I suggest you try to see what's going on there without the vga=788 option.
You can modify the boot command in grub. Then you can use logcat to see
what's going on.
Alt+F1 can switch to that console.
--
Chen
On Mon, May 11, 2009 at 9:18 PM, Kasuko wrote:
>
> I don't have access to a console in t
Ok giving the parameter console=tty0 I can grab the console but it
keeps being taken away from me. Android is constantly trying to "wake
up" and it writes alot to logcat which I can't read fast enough. Any
help on how to kill the wake up process and let me stay in the
terminal.
On May 11, 9:14 am
You may be able to logcat to redirect to some file, and then read that file
in other linux environment (install the disk to other linux vm and mount
under that linux.)
--
Chen
On Mon, May 11, 2009 at 9:25 PM, Kasuko wrote:
>
> Ok giving the parameter console=tty0 I can grab the console but it
>
Here it is.
I/vold( 1671): Android Volume Daemon version 2.0
D/vold( 1671): Bootstrapping complete
D/AndroidRuntime( 1672):
D/AndroidRuntime( 1672): >> AndroidRuntime START
<<
D/AndroidRuntime( 1672): CheckJNI is ON
I/( 1673): ServiceManager: 0x804ac38
W/Aud
On Mon, 2009-05-11 at 23:17 +0800, Chen Yang wrote:
> I/SurfaceFlinger( 1695): EGL informations:
> I/SurfaceFlinger( 1695): # of configs : 6
> I/SurfaceFlinger( 1695): vendor: Android
> I/SurfaceFlinger( 1695): version : 1.31 Android META-EGL
> I/Surfa
Make sure you are not using git apply, otherwise, the frameworks patch
may failed due to the changes in preloaded-class. git apply does patch
apply in an atomic way, so one failed, all failed.
On Mon, 2009-05-11 at 21:12 +0800, Chen Yang wrote:
> Have you enabled network on your target platform? I
No I did not use the git apply patch, and those files do not exist.
Here is my frame buffer section of kernel/.config
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not s
THis does not count, you need to show me following things:
1. cat /proc/fb
2. ls /dev/fb*
3. ls /dev/graphics/fb*
On Mon, 2009-05-11 at 12:43 -0700, Kasuko wrote:
> No I did not use the git apply patch, and those files do not exist.
> Here is my frame buffer section of kernel/.config
> # Frame buf
#cat /proc/fb
#
#ls /dev/fb*
/dev/fb*: No such file or directory
#ls /dev/graphics/fb*
/dev/graphics/fb*: No such file or directory
But why?
Thanks
-Corey Ling
On Mon, May 11, 2009 at 3:54 PM, Yi Sun wrote:
>
> THis does not count, you need to show me following things:
>
> On Mon, 2009-05-
Your kernel is wrong, repeat following things:
1. make clean in your kernel dir and make bzImage again
2. copy arch/x86/boot/bzImage to vendor/asus/eee_701/kernel
3. in your android source tree do make clean
4. rebuild your android
On Mon, 2009-05-11 at 16:14 -0400, Kasuko wrote:
> #cat /proc/fb
29 matches
Mail list logo
