stuck at urandom warning missed due to rate limiting

[Hassin Ayaz]

Hello 

I am trying to boot android-x86 over network . 

the booting freezes at the following warning message: 

------------------------------------------------------------------------

random: 7 urandom warning(s) missed due to ratelimiting 

------------------------------------------------------------------------

both at VM and actual laptop the same error prompts 

i am using the latest nougat branch 

attached is the VM output image 

[Mauro Rossi]

Hi,

You need to set  CONFIG_RANDOM_HW=y in the android-x86 defconfig files

I have enabled also all the other CONFIG_RANDOM_HW_* options with y (built-in module) in order to have them in very early stages of boot.

In 64 bit kernel with linux git based branch I still see some panic

and I'm checking youling257 suggestions about that, 

but 32 bit working 

cryptomgr_test[936] exited with preempt_count 2

Mauro

[Hassin Ayaz]

Hi ... thanks a lot 

i will make the kernel changes and come up with the result here 

[Hassin Ayaz]

Hello

I have not found any RANDOM_HW option in the androidx86_def via menuconfig

Would you kindly tell where to find it?

Thanks for the help

[Mauro Rossi]

Hi,

It's because it is CONFIG_HW_RANDOM

sorry for the typo

Mauro

[Hassin Ayaz]

Hi ... thanks 

i have recompiled adding HW_RANDOM related configs , but still the urandom problem exists at 32bit OS 

i tried to boot using virtualbox 

will i use an old kernel ? 

[Chih-Wei Huang]

Then which kernel do you use now?

I noticed you seems don't have the option
androidboot.selinux=permissive in kernel cmdline.
This is necessary since nougat-x86.

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

[Hassin Ayaz]

Hi Mr Chih-Wei  

thanks  a lot .... adding the permissive parameter booting forwards , but now booting is stuck at android splash screen 

here is my kernel command line parameters 

imgargs kernel ip=dhcp root=/dev/nfs rw androidboot.hardware=android_x86_64 ROOT=${server_ip}:${nfs_path} androidboot.selinux=permissive androidboot.selinux=enforcing xforcevesa HWACCEL=1 acpi_sleep=s3_bios,s3_mode

[Hassin Ayaz]

i am using 4.9 kernel 

[Chih-Wei Huang]

2018-07-31 2:16 GMT+08:00 Hassin Ayaz <hassi...@gmail.com>:
> Hi Mr Chih-Wei
>
> thanks a lot .... adding the permissive parameter booting forwards , but
> now booting is stuck at android splash screen
> here is my kernel command line parameters
>
> imgargs kernel ip=dhcp root=/dev/nfs rw androidboot.hardware=android_x86_64
> ROOT=${server_ip}:${nfs_path} androidboot.selinux=permissive
> androidboot.selinux=enforcing xforcevesa HWACCEL=1
> acpi_sleep=s3_bios,s3_mode

Why do you have two androidboot.selinux?
Android-x86 has to run in permissive mode.
Enforcing mode won't work.

Besides, these options are unnecessary. Remove them:

androidboot.hardware=android_x86_64
xforcevesa HWACCEL=1