android-x86-6.0-20151202.iso，efi gpt，can not run

[youling 257]

i copy bootia32.efi、bootx64.efi，but can not run 6.0.

[youling 257]

在 2015年12月4日星期五 UTC+8上午5:49:00，youling 257写道：

i copy bootia32.efi、bootx64.efi，but can not run 6.0.

I edit grub.cfg，Still can not run

  search --file --no-floppy --set=root /system.sfs

linuxefi /kernel root=/dev/ram0 androidboot.hardware=android_x86 quiet DATA=

initrdefi /initrd.img 

[Povilas Staniulis]

That ISO uses a 32bit kernel.
For me, anything newer than KitKat won't boot on my T100 (EFI only device) with 32bit kernels, only 64bit kernels work.

What device are you using ?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Chih-Wei Huang]

2015-12-04 9:53 GMT+08:00 Povilas Staniulis <wdmo...@gmail.com>:
> That ISO uses a 32bit kernel.
> For me, anything newer than KitKat won't boot on my T100 (EFI only device)
> with 32bit kernels, only 64bit kernels work.

T100 can run 32-bit kernel, of course.

> What device are you using ?

If it's 64-bit UEFI BIOS, it can't boot the 32-bit kernel.

[youling 257]

may be need new grub.cfg，

search --file --no-floppy --set=root /system.sfs

linuxefi /kernel root=/dev/ram0 androidboot.hardware=android_x86 quiet DATA=

initrdefi /initrd.img

It's for 5.1,what is for Marshmallow ?

[Povilas Staniulis]

On 12/4/2015 4:14 AM, Chih-Wei Huang wrote:
> 2015-12-04 9:53 GMT+08:00 Povilas Staniulis <wdmo...@gmail.com>:
>> That ISO uses a 32bit kernel.
>> For me, anything newer than KitKat won't boot on my T100 (EFI only device)
>> with 32bit kernels, only 64bit kernels work.
> T100 can run 32-bit kernel, of course.

It boots but hangs right before the boot animation.
64bit kernel works fine.

>> What device are you using ?
> If it's 64-bit UEFI BIOS, it can't boot the 32-bit kernel.
>

Without knowing the device, we can't tell.

[rbg]

quick test builds with 64bit kernel....img file untested....iso booted fine..no fluff added

here:

-------

https://drive.google.com/folderview?id=0B2evBKvIpdYkTHNoblBZRlBDSnc&usp=sharing#list

[youling 257]

img，iso，all can not run，efi，gpt.

https://drive.google.com/folderview?id=0B2evBKvIpdYkTHNoblBZRlBDSnc&usp=sharing#list 

[youling 257]

android_x86-5.1.1_r13-20150831.img，android_x86-5.1.1_r13-BLUEZ-20150906.img，android_x86-5.1.1_r18-BLUEZ-20150921.img，android_x86-5.1.1_r18-20150925.img，all build by RBG，all can run on my device，efi gpt.       but，android_x86-6.0.0_r26-20151203.img，it's not can，why ?

[Chih-Wei Huang]

Marshmallow-x86 is still under development.
It's not guaranteed to run on any device.

Please provide more info including the hardware spec,
test environment and procedure, and the (most important)
failed log (dmesg & logcat).

[youling 257]

Onda V891w Tablet features 8.9 Inch Full HD Retina Screen with 1920*1200 resolution,with Intel Quad Core 64bit Bay Trail Z3735F CPU,RAM 2GB,ROM 32GB,Dual Camera,Bluetooth 4.0,support OTG function.

32bit bios，32 bit Windows 8.1，can run android-x86_64-5.1-rc1.img，can run android-x86-5.1-rc1.iso

[spin877]

My tablet  Mediacom w101-3g

smpboot: CPU0: Intel(R) Atom(TM) CPU  Z3735F @ 1.33GHz (fam: 06, model: 37, stepping: 08)

not working 

dmesg http://pasted.co/e40f7aed

logcathttp://pasted.co/17517bc9

12-04 16:41:41.739  1983  1983 I SurfaceFlinger: SurfaceFlinger is starting
12-04 16:41:41.739  1983  1983 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
12-04 16:41:41.764  1983  1983 D libEGL  : loaded /system/lib/egl/libGLES_mesa.so
12-04 16:41:41.830  1983  1983 W EGL-DRI2: fail to get drm fd
12-04 16:41:41.830  1983  1983 W libEGL  : eglInitialize(0xf6b47000) failed (EGL_NOT_INITIALIZED)
12-04 16:41:41.830  1983  1983 W gralloc : FBIOPUT_VSCREENINFO failed, page flipping not supported
12-04 16:41:41.831  1983  1983 W gralloc : page flipping not supported (yres_virtual=800, requested=1600)
12-04 16:41:41.831  1983  1983 I gralloc : using (fd=12)
12-04 16:41:41.831  1983  1983 I gralloc : id           = inteldrmfb
12-04 16:41:41.831  1983  1983 I gralloc : xres         = 1280 px
12-04 16:41:41.831  1983  1983 I gralloc : yres         = 800 px
12-04 16:41:41.831  1983  1983 I gralloc : xres_virtual = 1280 px
12-04 16:41:41.831  1983  1983 I gralloc : yres_virtual = 800 px
12-04 16:41:41.831  1983  1983 I gralloc : bpp          = 32
12-04 16:41:41.831  1983  1983 I gralloc : r            = 16:8
12-04 16:41:41.831  1983  1983 I gralloc : g            =  8:8
12-04 16:41:41.831  1983  1983 I gralloc : b            =  0:8
12-04 16:41:41.831  1983  1983 I gralloc : width        = 203 mm (160.157639 dpi)
12-04 16:41:41.831  1983  1983 I gralloc : height       = 127 mm (160.000000 dpi)
12-04 16:41:41.831  1983  1983 I gralloc : refresh rate = 60.00 Hz
12-04 16:41:41.832  1983  1983 E SurfaceFlinger: hwcomposer module not found
12-04 16:41:41.833  1983  1983 W SurfaceFlinger: no suitable EGLConfig found, trying a simpler query
12-04 16:41:41.833  1983  1983 F SurfaceFlinger: no suitable EGLConfig found, giving up
--------- beginning of crash

[rbg]

for those with UEFI-Enabled x86 such as BayTrail / Atom SOC etc.

please use this installer:

    http://forum.xda-developers.com/windows-8-rt/win-8-development/winapp-android-x86-installer-uefi-t3225748

[youling 257]

i can install android-x86_64-5.1-rc1.img  on  10GB ext4 Partition，efi gpt.    this is only use system.img  data.img， it was no use

在 2015年12月5日星期六 UTC+8上午1:32:41，rbg写道：

[youling 257]

i install  android_x86-6.0.0_r26-20151203.img  on  10GB ext4 partition，it is stay at Android screen，http://i.imgur.com/VVR8L0I.jpg

[Mauro Rossi]

Hi spin877,

The logcat you posted remindes me about drm fb not initialized,
could you provide the two lsmod output in debug mode console, before and after the 1st exit command?

SIGABRT signal may be related to non accelerated SW rendering in conjunction with high resolution. Could you also try to lower the screen resolution, just to see what happens?

Also to be checked the status of external/drm_gralloc project wrt to your Intel HD graphics GPU.
Last time I checked this project in AOSP's marshmallow seemed not exactly aligned to hardware/drm_gralloc of lollipop,
but I need to actually check better myself, in android-x86 git, if this may have had consequences in marshmallow-x86. TBV & TBC

Mauro

[paul17]

Installed this yesterday
All worked fine. Excellent. Multi window works good. For some time, the play store worked good. Then it showed server error. Rebooted. Same error.

Also, USB devices do not show in any file managers, whether be it the default or 3rd party. To copy files from the Android to pen drives, I have to open the settings, storage, explore internal storage and then copy it to pen drive..

Dell inspiron 3521. Android dual booting with Windows 10

[youling 257]

32bit-kernels，Baytrail-Atom_SOC，android_x86-6.0.0_r26_BA-20151204.img，can not run.

[youling 257]

dmesg & logcat ？ how to do? i don't konw，

在 2015年12月4日星期五 UTC+8下午6:24:08，Chih-Wei Huang写道：

[fgdn17]

do you have:

   bitlocker turned off, secure boot disabled

and use: (Android-x86 Installer UEFI VERSION)

Download Here: (report installer issues)

   http://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483

sorry had incorrect pointer...

[youling 257]

Android-x86 Installer UEFI VERSION，it is use data.img，do you konw? i create 6GB ext4 partition for install Android x86 6.0 ，yours play store problem，you need ext4 partition . Android-x86 Installer UEFI VERSION， it is no use.
在 2015年12月6日星期日 UTC+8上午2:20:25，fgdn17写道：

[fgdn17]

read the instructions please.....

1. Select "Data Size" for file which will be used to store downloaded Apps and User Settings
2. Select the partition which Android will be installed to.

it uses DATA SIZE for 

• Create user data partition

take some time to read the instructions please.....

[youling 257]

ext4，ext4 ！ext4 needn't  data.img，do you konw？
https://drive.google.com/file/d/0B1HDhURlGNctOXFId2x2YWlmbVU/view?usp=sharing
在 2015年12月6日星期日 UTC+8上午8:50:54，fgdn17写道：

[IamBackX5]

I also have this problem with my T100, and this is not a installing problem... this is something with baytrail compability, because i install it by different methods, but result is the same. Just wait for new RC or Release builds and use KitKat/Lollipop before...

For now you can make only one thing that help developers to make some changes in newer builds - take logs... ALT+F1 and... i don't remember that is next :D Something like this:

dmesg > /sdcard/dmesg

logcat -f /sdcard/logcat

воскресенье, 6 декабря 2015 г., 10:10:32 UTC+5 пользователь youling 257 написал:

[youling 257]

how to do get dmesg and logcat ？ i don't konw . 
在 2015年12月6日星期日 UTC+8下午4:14:35，IamBackX5写道：

[youling 257]

i need Video Tutorial  to get logcat and dmesg .

[Mauro Rossi]

In debug mode after the last exit command that cause GUI to start

press [ALT]+[F1] 

plug an USB flash disk, that will appear usually as /storage/usb1

and use following commands:

cd /storage/usb1

dmesg > dmesg_app_that_crashed_YYYY-MM-DD.txt

cp /data/log.txt logcat_app_that_crashed_YYYY-MM-DD.txt

M.

[youling 257]

https://drive.google.com/folderview?id=0B1HDhURlGNctNXlQSG5aWi15MTg&usp=sharing

log,dmesg

在 2015年12月6日星期日 UTC+8下午10:31:17，Mauro Rossi写道：

[Chih-Wei Huang]

2015-12-05 0:02 GMT+08:00 spin877 <sfuma...@gmail.com>:
> My tablet Mediacom w101-3g
>
> smpboot: CPU0: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz (fam: 06, model: 37,
> stepping: 08)
>
> not working
>
> dmesg http://pasted.co/e40f7aed

According dmesg he i915 driver was loaded at 95s
which seems to be too late.
It looks like a known race condition of modules loading
but I don't know the root cause.

Currently you may try to add EXTMOD=i915
to the kernel cmdline as a workaround.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Chih-Wei Huang]

2015-12-07 7:22 GMT+08:00 youling 257 <youli...@gmail.com>:
> https://drive.google.com/folderview?id=0B1HDhURlGNctNXlQSG5aWi15MTg&usp=sharing
>
> log,dmesg

It's crashed in sensors.iio,
the same known issue as ASUS T100.
It's yet to be fixed.
(That's why sensors porting status was marked as partial)

Finally, please be modest in the public forum.
If you have another rude words,
you will be kicked out.

[spin877]

> According dmesg he i915 driver was loaded at 95s

I was in debug = 2 and hi given exit after 95 seconds . But it also happens if they are not in debug mode

[rbg]

there were some missing modules related to baytrail, the sources are being updated and
will be posted later today for testing. Thanks to the log / dmesg files.

[youling 257]

update dmesg file. 

but ,the new install.img,…………, so i copy an old install.img to udisk.

在 2015年12月8日星期二 UTC+8上午2:48:56，rbg写道：

[youling 257]

ok，This problem haven't solve

在 2015年12月4日星期五 UTC+8下午7:34:23，youling 257写道：

[rbg]

see last 4 comments here:

https://groups.google.com/forum/#!topic/android-x86/53pb0jXYhwY

[youling 257]

https://drive.google.com/folderview?id=0B1HDhURlGNctNXlQSG5aWi15MTg&usp=sharing


dmesg

[rbg]

- all the source code is available for you to build yourself...

- feel free to solve your issue and consider giving back to the community your contribution...

On Saturday, December 26, 2015 at 12:51:02 PM UTC-5, youling 257 wrote:

https://drive.google.com/folderview?id=0B1HDhURlGNctNXlQSG5aWi15MTg&usp=sharing


dmesg

[youling 257]

why “all the source code is available for you to build yourself...” ?  This problem only me ? 
 are you testing your's 6.0 on other bay trail tablet ?
在 2015年12月27日星期日 UTC+8上午4:38:23，rbg写道：

[Miker R]

Sir, If it's not LISTING a PARTITION to INSTALL ON, Aparently Um, You Can't Install????

I.E. You haven't done what is need for the installer to SEE the Partitions....

Mike

[youling 257]

Android x86 6.0，6.0.1，all can not run.

[Chih-Wei Huang]

2015-12-26 19:36 GMT+08:00 youling 257 <youli...@gmail.com>:
> Android x86 6.0，6.0.1，all can not run.
>

After checking the log you provided,
it's the same issue on T100.
Still under debugging...

[youling 257]

can't get log，logcat read failure，no log.txt this file.

在 2015年12月29日星期二 UTC+8下午4:52:00，Chih-Wei Huang写道：

[Chih-Wei Huang]

2015-12-29 19:50 GMT+08:00 youling 257 <youli...@gmail.com>:
> can't get log，logcat read failure，no log.txt this file.

Hmm? Isn't the log on the Google Drive provided by you?

Anyway, the iio sensor hal bug was fixed now.
That's another stupid bug I made.

[youling 257]

yes，the log on the Google Drive provided by me，but only the once，the log.txt，December 7，i don't remember how to get log at that time . December 7，at debug mode，i remember android/data folder，has log.txt file，only the once too. now ，dmesg > /mnt/dmesg.txt，can get dmesg ；logcat > /mnt/logcat.txt，logcat read failure，/android/data folder，no log.txt file.
在 2015年12月30日星期三 UTC+8上午2:57:11，Chih-Wei Huang写道: