blank screen with cursor blinking with android-x86_64-5.1-rc1.iso or any later versions, android-x86-4.4-r5.iso no problem

[jack zhang]

If I install using bootable USB stick made with android-x86_64-6.0-r3.iso, or android-x86_64-5.1-rc1.iso, or android-86_64_8.1-rc2.iso on a intel based PC, after installation finishes, PC boots up to a blank black screen with cursor blinking.

If I install using bootable USB stick made with android-x86_64-4.4-r5.iso on a intel based PC, after installation finishes, PC boots up to Android fine.

can someone tell me if there is any changes from 4.4 to 5.1 that might cause this???

[Mauro Rossi]

Hi Jack,

check your PC specs, 

kitkat-x86 has 32bit user space on top of 64bit kernel, hence it will boot on Core 2 Duo cpu for example,

while lollipop-x86 and later have x86_64 ABI support, but it requires SSE4.

Mauro

[jack zhang]

hi Mauro:

 

           I double checked, the CPU is Atom x7-E3950.  According to the following table, SSE4.1 and SSE4.2 are supported under Atom x7-E3950. can you tell me how to trouble shoot it from here?

           https://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors

[Mauro Rossi]

Hi,

if the system allows you to switch to console [ALT]+ [F1], the procedure to collect log is explained here:

https://groups.google.com/forum/#!searchin/android-x86/busybox$20mount|sort:date/android-x86/A_YZfaksxmQ/n54Dbiu5AAAJ

if the systems does not allow to switch to console, you will need to install to ext4 partition of HDD or USB drive,

boot in DEBUG mode and then collect /data/log.txt using Linux PC

Mauro

[jack zhang]

Hi Mauro:

           I added 'nomodeset' option in the grub.  now the screen shows 'loading stage 1.5'. any idea?

[Chih-Wei Huang]

jack zhang <jackm...@gmail.com> 於 2019年1月22日 週二 上午7:38寫道：

>
> Hi Mauro:
> I added 'nomodeset' option in the grub. now the screen shows 'loading stage 1.5'. any idea?

Sounds like the kernel is not booted yet.

Did your device only support legacy booting?
Could you switch to UEFI booting?
With UEFI booting the problem will be less.


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

[jack zhang]

I can enable UEFI instead of Legacy in the BIOS. But then it just stops at a UEFI shell.  see attached photo.

[Mauro Rossi]

Hi,

as an empirical consideration, 

what happens if you try to boot lollipop-x86 and later 32bit iso?

This test would give information if ABI x86_64 is the root cause or also 32bit images are affected.

Next step: 

If you PC also has Windows 10 or Linux OS, you may try to boot in Virtualbox redirect 'console=ttyS0 console=tty0' to a file and see if kernel panic has been logged.

Mauro

[ahmed sniper]

Mr Maro can help me in my problem

It’s about resolution issue and i describe it here
https://youtu.be/t4j4fUC-QuY

[jack zhang]

HI Mauro:

        I played with few BIOS settings, now after installation, it shows some gibberish characters, screen doesn't respond to [ALT]+[CTRL]+[F1].   see screen shot