Android X86 won't boot

[Franco Palombo]

Hi, I recently build Android x86 9.0, and I built it with a custom deconfig. Specifically, with Nvidia SATA modules. Now, after 18 hours of compiling, I'm on the same situation as if I didn't made a custom kernel. I thought that the problem was on the HDD detection, because that's what I read from some other people. Please, someone give me a hand, I want to give a use to this computer!
System Specifications:
Motherboard: ASRock N68S-UCC
Ram: 4gb DDR2
GPU: AMD/ATI Radeon HD 6670 (1gb)
CPU: AMD Sempron 140 (OC @ 3.3GHz, Unlocked extra cores, detected as: AMD Athlon II x2 4400e)
I'm trying to boot Android x86 from a USB stick in Live mode. Trying to go to the installer will result in no drives showing up

Regards

[Daniel Cheung]

Can you post your kernal configuration file? Also, make sure you are referring to the correct one during the build process. I had problems in the beginning and started using this process:

• Make a copy of the Android X86_84 deconfig file and rename it to .config
• Launch the kernel configuration tool, make any changes, and save
• Rename the .config file to a different name, in my case I use "my_defconfig" with no file extension
  
• Use a script to load the build process

My compile bash script looks like this:

#!/bin/bash
. build/envsetup.sh
export LC_ALL=C
sudo make clean
lunch android_x86_64-userdebug
make -j5 iso_img TARGET_KERNEL_CONFIG=my_defconfig

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/ff9cddc4-b7b4-4b56-bb8d-b7c204b82729o%40googlegroups.com.

[Franco Palombo]

I've named it as android-x86_64-NvSATA
And, i dont have a compile bash script. I'm new to this, but i reconognize some of the commands that you used on your script.
To create the custom config file i used this commands:
. build/envsetup.sh
export ARCH=x86
lunch android_x86-eng
but after executing those commands and getting my custom config, i've never executed them again. idk if the effects of the commands persist after reboots, or changing compiling computers.
The command that i execued, to get the iso with the custom config was this:
make iso_img TARGET_PRODUCT=android_x86_64 TARGET_KERNEL_CONFIG=android-x86_64-NvSATA
the config file is located on /media/ffpp/ArchFranc/android_x86/source1/kernel/arch/x86/configs/

El martes, 16 de junio de 2020, 14:26:34 (UTC-3), BrokenE39 escribió:
> Can you post your kernal configuration file? Also, make sure you are referring to the correct one during the build process. I had problems in the beginning and started using this process:
>

> Make a copy of the Android X86_84 deconfig file and rename it to .configLaunch the kernel configuration tool, make any changes, and saveRename the .config file to a different name, in my case I use "my_defconfig" with no file extension

> Use a script to load the build process
> My compile bash script looks like this:
>
>
>
> #!/bin/bash
> . build/envsetup.sh
> export LC_ALL=C
> sudo make clean
> lunch android_x86_64-userdebug
> make -j5 iso_img TARGET_KERNEL_CONFIG=my_defconfig
>
>
> On Tue, Jun 16, 2020 at 6:00 AM Franco Palombo <ffpp...@hotmail.com> wrote:
> Hi, I recently build Android x86 9.0, and I built it with a custom deconfig. Specifically, with Nvidia SATA modules. Now, after 18 hours of compiling, I'm on the same situation as if I didn't made a custom kernel. I thought that the problem was on the HDD detection, because that's what I read from some other people. Please, someone give me a hand, I want to give a use to this computer!
>
> System Specifications:
>
> Motherboard: ASRock N68S-UCC
>
> Ram: 4gb DDR2
>
> GPU: AMD/ATI Radeon HD 6670 (1gb)
>
> CPU: AMD Sempron 140 (OC @ 3.3GHz, Unlocked extra cores, detected as: AMD Athlon II x2 4400e)
>
> I'm trying to boot Android x86 from a USB stick in Live mode. Trying to go to the installer will result in no drives showing up
>
>
>
> Regards
>
>
>
> --
>
> 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 andro...@googlegroups.com.

[Daniel Cheung]

Not sure how important the initial "export" and "launch" commands are in the grand scheme of things but I noticed you are not using the 64bit parameter when you are loading the kernel configurator but then in the build you are targeting X86-64. Also, the kernel configuration file is in a different location between when you call the GUI configurator and when you refer it in the compile process. You are saying load the configuration file in /work/config to configure but when it comes time to build, it will look in /kernel/arch/x86/configs/. I suggest you follow my steps in the previous post in copying the x86_64 defconfig and renaming it to .config and change your commands to this:

 . build/envsetup.sh

    export ARCH=x86_64

    lunch android_x86_64-eng

    make -C kernel O=/media/ffpp/ArchFranc/android_x86/source1/kernel/arch/x86/configs/ xconfig

I load the kernel configurator using these cmd:

. build/envsetup.sh
export ARCH=x86_64
lunch android_x86_64-userdebug
sudo make -C kernel O=/home/daniel/android_8/kernel/arch/x86/configs/ xconfig

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/e61e1eb5-6cf1-4680-8e69-7d821e4b0255o%40googlegroups.com.

[Mauro Rossi]

Hi Franco,

On Tuesday, June 16, 2020 at 8:04:29 PM UTC+2, Franco Palombo wrote:

I've named it as android-x86_64-NvSATA
And, i dont have a compile bash script. I'm new to this, but i reconognize some of the commands that you used on your script.
To create the custom config file i used this commands:
 . build/envsetup.sh
    export ARCH=x86
    lunch android_x86-eng
but after executing those commands and getting my custom config, i've never executed them again. idk if the effects of the commands persist after reboots, or changing compiling computers.
The command that i execued, to get the iso with the custom config was this:
make iso_img TARGET_PRODUCT=android_x86_64 TARGET_KERNEL_CONFIG=android-x86_64-NvSATA
the config file is located on /media/ffpp/ArchFranc/android_x86/source1/kernel/arch/x86/configs/

Checking the android-x86_64-NvSATA defconfig file, you need to enable CONFIG_SATA_NV

CONFIG_SATA_NV=y

 

[Franco Palombo]

Sorry, my idea wasn't to compile a custom kernel. the commands that i copied are from this https://groups.google.com/forum/#!topic/Android-x86/x5aBNnK4Ols guide, that are specifically to compile a custom kernel, but the part of creating a custom config is the part that i actually used. I've actually mooved the config file to where all the default configs are. idk if that is a problem, because in the output folder of the custom config there where some other files that i didn't copied. 

it seems like you are a bit more experienced with this. if you can, and have enough time, can you write a guide in to create a custom config and compile it ino an ISO? the one that i used its too old (2014 i think), and dosen't covers all my interests. 

regards

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/e61e1eb5-6cf1-4680-8e69-7d821e4b0255o%40googlegroups.com.

[Franco Palombo]

Ummmmmm. I though that i enabled it on the custom config GUI command. i dont remember how it was called, but i remember going into a submenu called Serial ATA... and then looking for Nvidia SATA... and enabling it and then saving the custom config. Maybe i did something wrong. for the moment, im hoping if someone can make an guide for noobs, so i can follow it, and see if i can get it to boot

thanks to all of you that are helping me to figure this out

[Daniel Cheung]

Making a guide is on my list. Just have to find the time outside of work to contribute.

--

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 view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/28d2ee49-c213-4921-8271-906b5dddacb1o%40googlegroups.com.

[Mauro Rossi]

On Tuesday, June 16, 2020 at 8:34:32 PM UTC+2, Franco Palombo wrote:

Ummmmmm. I though that i enabled it on the custom config GUI command. i dont remember how it was called, but i remember going into a submenu called Serial ATA... and then looking for Nvidia SATA... and enabling it and then saving the custom config. Maybe i did something wrong. for the moment, im hoping if someone can make an guide for noobs, so i can follow it, and see if i can get it to boot

thanks to all of you that are helping me to figure this out

The old procedure is still valid for building iso with modified kernel config

When you use this command

make iso_img TARGET_PRODUCT=android_x86_64 TARGET_KERNEL_CONFIG=android-x86_64-NvSATA

the file specified as TARGET_KERNEL_CONFIG has been used, but yours didn't have CONFIG_NVIDIA_NV enabled

When you use oldconfig or xconfig you need to be sure that the .config file with the options you changed is moved to kernel/arch/x86/configs/ and configs changed are kept

Mauro 

[Franco Palombo]

Guys, can I just build the kernel and paste it into the live cd USB? Or it won't have the needed kernel modules and it'll fail to boot?

[Michael Stuhr]

Does anybody around here recommend booting "GPARTED" from a USB stick to format your HD partition?

Seems to solve these sort of problems.

Get Outlook for Android

---

From: andro...@googlegroups.com <andro...@googlegroups.com> on behalf of Franco Palombo <ffpp...@hotmail.com>
Sent: Friday, June 19, 2020 4:49:08 AM
To: Android-x86 <andro...@googlegroups.com>
Subject: Re: Android X86 won't boot

 

Guys, I finally got android x86 to detect my HDD. The problem was that I forgot to save the custom config, so, using the steps given by BrokenE39, and thanks to Mauro Rossi, I got it to detect my HDD.

Now, I wanted to try and see how android performs on a PC (because, I only tried android X86 on a VM), so, I decided to before doing anything, try the live cd boot. It looks like, I'm on the same situation as on the start of this question, it gets stuck at:

Detecting Android-x86......... Found at /dev/sdb

_

And nothing else happens after that point. Idk why, but it seems like, android x86, stops loading the OS, because, I can see that the activity LED on my usb drive stops blinking. Could it be the graphics card that is generating problems at boot? I tried adding the kernel parameter nomodeset, but, doesn't changes anything, just stays in the same resolution as the GRUB menu.

regards

--

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 view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/2a1336c4-cfa2-4ab8-999d-53fd72ed2fd8o%40googlegroups.com.

[Michael Stuhr]

May be out of the blue...

Get Outlook for Android

---

From: Michael Stuhr <android...@gmail.com>
Sent: Friday, June 19, 2020 11:08:46 AM
To: andro...@googlegroups.com <andro...@googlegroups.com>

[Daniel Cheung]

Didn't another person had problems at the exact position and had to add some kind of vga mode? Need to dig around the threads for it but it was within the last week. As for HDD partition, I tried using GParted but could never get it right. So I just use the automated install process off the Live USB and let it set it. I then go back and reinstall using my custom image.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/DM6PR07MB45557B0E5D2FF9C68684426FA2980%40DM6PR07MB4555.namprd07.prod.outlook.com.

[Franco Palombo]

Well, if you can give me the link to see that post I'll really appreciate it. The problem of the HDD is solved, now the installer detects my HDD with no problems, and I can use the default "disk partition" tool. The only thing is that it doesn't boot. It would be really cool if I can make it boot without loosing the GPU capabilities.

[Michael Stuhr]

You see, I I just bought a new ssd for my new laptop and couldn't get android to boot past the android logo until I dug out my GPARTED usb. Works great, very happy, but trying to connect to wifi at home is a royal fizbin. Now I use my phone as a modem/router at home.

GPARTED is a pitb, you just need to get used to using the alt key for the underlined commands, if the touch screen doesn't work for you.

Get Outlook for Android

---

From: andro...@googlegroups.com <andro...@googlegroups.com> on behalf of Franco Palombo <ffpp...@hotmail.com>

Sent: Friday, June 19, 2020 12:02:44 PM

To: Android-x86 <andro...@googlegroups.com>
Subject: Re: Android X86 won't boot

Well, if you can give me the link to see that post I'll really appreciate it. The problem of the HDD is solved, now the installer detects my HDD with no problems, and I can use the default "disk partition" tool. The only thing is that it doesn't boot. It would be really cool if I can make it boot without loosing the GPU capabilities.

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/0487d267-b137-42dc-85f3-93aada38ee3co%40googlegroups.com.

[Daniel Cheung]

This is the link I was talking about: https://groups.google.com/forum/#!topic/android-x86/GVIm5M3K6To

He had to use nomodeset xforcevesa but he was facing a no boot situation. Try booting in debug and see if it's stuck somewhere first. My own device was not happy with pstore turned on and in some version it would get stuck.

As for wifi, do you know what brand and model the wifi card is? I myself is having issues with RTL8723BS again.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/DM6PR07MB45555854E8E2B81BE82306E6A2980%40DM6PR07MB4555.namprd07.prod.outlook.com.

[Franco Palombo]

Thanks for giving me the link, but as you say, I can boot, the person from the other post couldn't. I've already tried using nomodeset, xforcevesa, and nomodeset xforcevesa, but it didn't boot. Now that you said me to boot into debugging, I can see more clear where is the problem. I think it's on the kernel parameters, but I cannot find anything. I adjunct 2 photos, one of the error, and another of my kernel params.

The thing is that I had a OS installed (Ubuntu 20.04) with already grub2, so, in the installation process, I decided to skip the option to install a boot manager, so, that could be the thing that it's generating the problem. So, if someone has successfully booted Android x86 9.0, please, write down the kernel parameters so I can try them on my installation

El viernes, 19 de junio de 2020, 21:17:44 (UTC-3), BrokenE39 escribió:
> This is the link I was talking about: https://groups.google.com/forum/#!topic/android-x86/GVIm5M3K6To
>
>
> He had to use
> nomodeset xforcevesa but he was facing a no boot situation. Try booting in debug and see if it's stuck somewhere first. My own device was not happy with pstore turned on and in some version it would get stuck.
>
>
> As for wifi, do you know what brand and model the wifi card is? I myself is having issues with RTL8723BS again.
>
>
>
> On Fri, Jun 19, 2020 at 3:36 PM Michael Stuhr <android...@gmail.com> wrote:
>
>
>
>
>
>
>
>
> You see, I I just bought a new ssd for my new laptop and couldn't get android to boot past the android logo until I dug out my GPARTED usb. Works great, very happy, but trying to connect to wifi at home is a royal fizbin. Now I use my phone as a modem/router
> at home.
>
>
>
>
>
>
> GPARTED is a pitb, you just need to get used to using the alt key for the underlined commands, if the touch screen doesn't work for you.
>
>
>
>
>
>
>
>
>
>
> Get Outlook for Android
>
>
>
>
>

> From: andro...@googlegroups.com <andro...@googlegroups.com> on behalf of Franco Palombo <ffpp...@hotmail.com>
>
> Sent: Friday, June 19, 2020 12:02:44 PM
>
> To: Android-x86 <andro...@googlegroups.com>
>
> Subject: Re: Android X86 won't boot
>
>  
>
>
>
>
> Well, if you can give me the link to see that post I'll really appreciate it. The problem of the HDD is solved, now the installer detects my HDD with no problems, and I can use the default "disk partition" tool. The only thing is that
> it doesn't boot. It would be really cool if I can make it boot without loosing the GPU capabilities.
>
>
>
> --
>
> 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 andro...@googlegroups.com.

>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-x86/0487d267-b137-42dc-85f3-93aada38ee3co%40googlegroups.com.
>
>
>
>
>
>
>
>
>
> --
>
> 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 andro...@googlegroups.com.

[Franco Palombo]

Just to see if there was something wrong with my Android build, I decided to try the live cd from another computer. This time I tried on a HP laptop with a I5 7th gen, and the live cd booted with no problems, so, it might be something hardware related

[Franco Palombo]

I've decided to try and overwrite my grub installation with the one provided with the Android x86 installer. Now I get a different error. Take a look

[Daniel Cheung]

I guess I should of re-read your first post. I think your hardware is too old for Android 9. Try Android 7 live cd and see if it boots at all. Chi mentioned that older hardware are missing instructions that Android 9 is depending on. If that doesn't work, you may have to go down to 5 or 4.4.

On Sat, Jun 20, 2020 at 7:14 PM Franco Palombo <ffpp...@hotmail.com> wrote:

I've decided to try and overwrite my grub installation with the one provided with the Android x86 installer. Now I get a different error. Take a look

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/8f413935-6e50-46c0-8250-ff6c005633edo%40googlegroups.com.

[Franco Palombo]

Ok, probably the solution is using android 7.1. Do you guys recommend using lineageOS? ive used it in some of my devices and its a good os

El domingo, 21 de junio de 2020, 14:00:06 (UTC-3), BrokenE39 escribió:

I guess I should of re-read your first post. I think your hardware is too old for Android 9. Try Android 7 live cd and see if it boots at all. Chi mentioned that older hardware are missing instructions that Android 9 is depending on. If that doesn't work, you may have to go down to 5 or 4.4.

On Sat, Jun 20, 2020 at 7:14 PM Franco Palombo <ffpp...@hotmail.com> wrote:

I've decided to try and overwrite my grub installation with the one provided with the Android x86 installer. Now I get a different error. Take a look

--
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 andro...@googlegroups.com.

[Mauro Rossi]

Hi Franco,

If you tried x86_64 build I don't think it will work on AMD Sempron 140 cpu,

the minimum requirements for x86_64 are not satisfied,

you should try to build x86 32bit iso

Mauro

[Franco Palombo]

Too late, I've already deleted the repository clone. And I don't really like the idea of having a 32bit os on a 64 capable processor. It's like... I'm loosing performance? idk. I want to try lineage os, but I have some questions.
Is this the correct way to clone LOS 14.1: repo init -u git://git.osdn.net/gitroot/android-x86/manifest -m cm.xml -b nougat-x86 && repo sync --no-tags --no-clone-bundle

Do you recommend to build the whole ISO? Or just the kernel and use the already built ISO? And if you say that is better to build the whole ISO, how can I add gapps to the ISO? I think that the ones that you can download already have gapps, but the one that I built didn't had them.