info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Have you ever had a working PC that wouldn't go into the BIOS mode?
3 views
Skip to first unread message
Arlen Holder
Dec 12, 2020, 8:47:29 PM12/12/20
to
Have you ever had a working PC that wouldn't go into the BIOS mode?
o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
How did you resolve that issue?
1. The Windows machine boots to POST & then Windows 10 just fine.
2. Once booted to Windows, the USB keyboard & mouse work just fine.
3. But I can't get the PC to respect the BIOS F10 key press.
These are the key presses I know used to work:
o BIOS Menu ===> F10
o BOOT Menu ===> Escape
o DIAG Menu ===> F9
And yes, I'm pressing them (all the time) specifically at POST
o When it says to press "F10" to get into the BIOS.
It's like the keyboard isn't even there...
o The BIOS battery is only a few months old.
The reason I want to access the BIOS is I need to change the HyperVisor
settings for my AMD-based Foxconn motherboard for an Android emulator:
o Tutorial Installing Android Studio 4.1.1 on Windows 10 (AMD CPU)
<https://groups.google.com/g/comp.mobile.android/c/g3ymz5CPsIk>
o Win+R > msinfo32
Windows version: Windows 10, 10.0, version 2004, build: 19041
Hardware: NY549AA-ABA p6230y, HP-Pavilion, FOXCONN, ALOE
CPU: Authentic AMD AMD Phenom(tm) II X4 810
BIOS Version/Date: American Megatrends Inc. 5.02, 8/31/2009
SMBIOS Version 2.6
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes
Have you ever had a working PC that wouldn't go into the BIOS mode?
o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
How did you resolve that issue?
o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
How did you resolve that issue?
1. The Windows machine boots to POST & then Windows 10 just fine.
2. Once booted to Windows, the USB keyboard & mouse work just fine.
3. But I can't get the PC to respect the BIOS F10 key press.
These are the key presses I know used to work:
o BIOS Menu ===> F10
o BOOT Menu ===> Escape
o DIAG Menu ===> F9
And yes, I'm pressing them (all the time) specifically at POST
o When it says to press "F10" to get into the BIOS.
It's like the keyboard isn't even there...
o The BIOS battery is only a few months old.
The reason I want to access the BIOS is I need to change the HyperVisor
settings for my AMD-based Foxconn motherboard for an Android emulator:
o Tutorial Installing Android Studio 4.1.1 on Windows 10 (AMD CPU)
<https://groups.google.com/g/comp.mobile.android/c/g3ymz5CPsIk>
o Win+R > msinfo32
Windows version: Windows 10, 10.0, version 2004, build: 19041
Hardware: NY549AA-ABA p6230y, HP-Pavilion, FOXCONN, ALOE
CPU: Authentic AMD AMD Phenom(tm) II X4 810
BIOS Version/Date: American Megatrends Inc. 5.02, 8/31/2009
SMBIOS Version 2.6
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes
Have you ever had a working PC that wouldn't go into the BIOS mode?
o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
How did you resolve that issue?
JT
Dec 12, 2020, 9:20:13 PM12/12/20
to
Does this PC's motherboard have PS/2 inputs for keyboard and mouse? (usually green and purple)
I've had older systems that the USB keyboard and mouse were not useable until Windows loaded.
Using a PS/2 style keyboard solved the issue.
Just a thought...
JT
--
David W. Hodgins
Dec 12, 2020, 9:58:48 PM12/12/20
to
On Sat, 12 Dec 2020 20:47:28 -0500, Arlen Holder <arlen_...@newmachines.com> wrote:
> Have you ever had a working PC that wouldn't go into the BIOS mode?
Yes, when using a usb dongle for a wireless keyboard/mouse. Workaround is that
> Have you ever had a working PC that wouldn't go into the BIOS mode?
when I need to access the bios menu is to boot with the dongle unplugged and
a ps/2 keyboard plugged in.
Regards, Dave Hodgins
--
Change dwho...@nomail.afraid.org to davidw...@teksavvy.com for
email replies.
Arlen Holder
Dec 12, 2020, 10:07:32 PM12/12/20
to
On Sun, 13 Dec 2020 02:20:08 +0000 (UTC), JT wrote:
> Using a PS/2 style keyboard solved the issue.
Hi JT,
> Using a PS/2 style keyboard solved the issue.
I don't see any PS/2 inputs, nor do I have the keyboard anyway.
o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg>
Here's what happens with the Genymotion Android 10 Pixel3a emulation:
o <https://i.postimg.cc/QdqTpBsq/cmos02.jpg>
"Your CPU is incompatible with virtualization technologies."
And here's what happens with the VirtualBox virtual machine:
o <https://i.postimg.cc/d1gkqrmJ/cmos03.jpg>
"AMD-V is disabled in the BIOS (or by the host OS)
(VERR_SVM_DISABLED)."
Googling, there's "apparently" a way to force the CMOS to come up
o Apparently by shorting a jumper somewhere (but I'm not sure where).
JT
Dec 12, 2020, 10:37:54 PM12/12/20
to
A pic of the back of the motherboard with all the inputs would be helpful.
JT
--
Arlen Holder
Dec 12, 2020, 11:58:16 PM12/12/20
to
On Sun, 13 Dec 2020 03:37:47 +0000 (UTC), JT wrote:
> What model PC?
The PC make & model was listed in the opening post.
o But never mind. I solved the problem.
What I did was remove everything possible connected to the desktop.
o The only things I left connected were the absolute essentials.
And then, magically, the F10 worked just fine when POST said to tap it.
o Go figure. <https://i.postimg.cc/RhSXCJQn/cmos04.jpg>
> A pic of the back of the motherboard with all the inputs would be helpful.
The strangest thing is this Hyper-crap, which I never understood.
1. Apparently, I have to turn it "ON" in the BIOS
2. But I have to turn it "OFF" in Windows (Turn Windows features on or off)
<https://i.postimg.cc/zD2nHQqQ/cmos05.jpg>
That makes no sense (to me) and, worse, is quite unintuitive (to me).
o But that's the only way I could get Android emulation to work.
<https://i.postimg.cc/hjGjkX9X/cmos06.jpg>
In summary, two things had befuddled me to no end (they made no sense):
A. I couldn't get to the BIOS with "stuff" plugged into the ports, and,
B. You have to turn Hyper-crap ON in BIOS and OFF in Windows,
C. Just so that Android emulation will work (on an AMD CPU).
--
If someone can explain the logic of that circumstance to me, please do.
> What model PC?
The PC make & model was listed in the opening post.
o But never mind. I solved the problem.
What I did was remove everything possible connected to the desktop.
o The only things I left connected were the absolute essentials.
And then, magically, the F10 worked just fine when POST said to tap it.
o Go figure. <https://i.postimg.cc/RhSXCJQn/cmos04.jpg>
> A pic of the back of the motherboard with all the inputs would be helpful.
1. Apparently, I have to turn it "ON" in the BIOS
2. But I have to turn it "OFF" in Windows (Turn Windows features on or off)
<https://i.postimg.cc/zD2nHQqQ/cmos05.jpg>
That makes no sense (to me) and, worse, is quite unintuitive (to me).
o But that's the only way I could get Android emulation to work.
<https://i.postimg.cc/hjGjkX9X/cmos06.jpg>
In summary, two things had befuddled me to no end (they made no sense):
A. I couldn't get to the BIOS with "stuff" plugged into the ports, and,
B. You have to turn Hyper-crap ON in BIOS and OFF in Windows,
C. Just so that Android emulation will work (on an AMD CPU).
--
If someone can explain the logic of that circumstance to me, please do.
Arlen Holder
Dec 12, 2020, 11:58:17 PM12/12/20
to
On Sat, 12 Dec 2020 21:55:31 -0500, David W. Hodgins wrote:
> Yes, when using a usb dongle for a wireless keyboard/mouse. Workaround is that
> when I need to access the bios menu is to boot with the dongle unplugged and
> a ps/2 keyboard plugged in.
Hi David W. Hodgins,
> Yes, when using a usb dongle for a wireless keyboard/mouse. Workaround is that
> when I need to access the bios menu is to boot with the dongle unplugged and
> a ps/2 keyboard plugged in.
I solved the inability to boot to BIOS for a few days using these steps:
1. I turned off all power
2. I removed EVERYTHING that wasn't essential
3. I put the power back
4. I held the power button down for 10 seconds & then once up & down
5. When it booted to POST I tapped the F10 key
6. And I was able to get into the BIOS (for the 1st time in a days trying)
Note: I'm not sure if every step above was needed; but that's what worked!
o <https://i.postimg.cc/RhSXCJQn/cmos04.jpg>
The result was I could turn the virtualization ON in the BIOS.
o And then OFF in Windows (Turn Windows features on or off).
To me, that makes zero logical sense (certainly it's not intuitive)...
o But it worked, so I can move on with my Android "hello world" emulation
<https://i.postimg.cc/NF900ZCY/cmos07.jpg>
--
If someone can explain the logic of what just happened, please do.
Carlos E.R.
Dec 13, 2020, 6:04:06 AM12/13/20
to
On 13/12/2020 02.47, Arlen Holder wrote:
> Have you ever had a working PC that wouldn't go into the BIOS mode?
> o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
Yes.
> Have you ever had a working PC that wouldn't go into the BIOS mode?
> o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
> How did you resolve that issue?
That was one case.
Another was removing any disk, because the machine was in hibernation,
and thus refused to accept enter bios till a real reboot happened. And
the disk said there was an hibernation image.
--
Cheers, Carlos.
Paul
Dec 13, 2020, 7:13:55 AM12/13/20
to
It smacks of software having done it (OS into UEFI).
Both PS/2 and USB keyboards disappeared at the same time,
and could not be used at BIOS level. No other setting
was affected. The settings have a crude checksum mechanism,
and there was no message indicating a problem.
It took Clear CMOS to restore function, so I could
press Del (Asus) and get into the UEFI BIOS setup screen.
Clear CMOS is to be done with all power off. No +5VSB
should be present. Many instructions are missing that detail.
Asus on multiple occasions, had to release a one-page PDF
correction to the user manual about this. If you leave
the power running, the Clear CMOS button can short
out the OR-ing diode on VBAT and burn the diode.
UEFI is just a too-insecure technology. As predicted.
Paul
MajorLanGod
Dec 13, 2020, 2:22:01 PM12/13/20
to
"JT" <J...@spam-me-not.invalid> wrote in
news:rr3too$1pju$1...@gioia.aioe.org:
I have a similar problem on my Ascer Aspire 5 laptop. The manual says
press F2 when booting to get to the BIOS, but I have'nt been able to get
that the work. My workaround? Windows 10 actually has an option to boot
to UEFI Bios in the Recovery-Advanced Startup pages. One of the options
under Advanced Startup is to boot to UEFI. Just make sure everything you
have going is ended and/or closed before going there.
I found out when trying to get the system to leave my keyboard lights on
all the time. Acer turns them off after 10 seconds of inactivity - they
had to do that to get their Energy Plus rating. Due to the number of
complaints, they just upgraded the Bios to give the option to keep them
on all the time WHEN RUNNING ON PLUGGED IN. They will still turn off when
running on battery, and it can't be changed.
news:rr3too$1pju$1...@gioia.aioe.org:
press F2 when booting to get to the BIOS, but I have'nt been able to get
that the work. My workaround? Windows 10 actually has an option to boot
to UEFI Bios in the Recovery-Advanced Startup pages. One of the options
under Advanced Startup is to boot to UEFI. Just make sure everything you
have going is ended and/or closed before going there.
I found out when trying to get the system to leave my keyboard lights on
all the time. Acer turns them off after 10 seconds of inactivity - they
had to do that to get their Energy Plus rating. Due to the number of
complaints, they just upgraded the Bios to give the option to keep them
on all the time WHEN RUNNING ON PLUGGED IN. They will still turn off when
running on battery, and it can't be changed.
Alan Baker
Dec 13, 2020, 2:38:51 PM12/13/20
to
Mark Lloyd
Dec 13, 2020, 3:27:25 PM12/13/20
to
On 12/12/20 7:47 PM, Arlen Holder wrote:
[snip]
> Have you ever had a working PC that wouldn't go into the BIOS mode?
> o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
>
> How did you resolve that issue?
I have an old Dell that seems to have no way to enter setup other than
to physically disconnect the hard drive (so no boot devices are available).
--
12 days until the winter celebration (Fri, Dec 25, 2020 12:00:00 AM for
1 day).
Mark Lloyd
http://notstupid.us/
"Politics is supposed to be the second oldest profession. I have come to
realize that it bears a very close resemblance to the first." -- Ronald
Reagan
[snip]
> Have you ever had a working PC that wouldn't go into the BIOS mode?
> o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
>
> How did you resolve that issue?
to physically disconnect the hard drive (so no boot devices are available).
--
12 days until the winter celebration (Fri, Dec 25, 2020 12:00:00 AM for
1 day).
Mark Lloyd
http://notstupid.us/
"Politics is supposed to be the second oldest profession. I have come to
realize that it bears a very close resemblance to the first." -- Ronald
Reagan
Paul
Dec 13, 2020, 3:43:40 PM12/13/20
to
F2 is one second :-) It takes ninja-like reflexes to get into the BIOS.
As a game, it's more fun than Windows Solitaire.
Paul
Ken Blake
Dec 13, 2020, 6:25:51 PM12/13/20
to
wasn't really meant to be a game. It was meant to be training for use of
the mouse.
--
Ken
Bob F
Dec 14, 2020, 1:28:39 PM12/14/20
to
On 12/13/2020 12:27 PM, Mark Lloyd wrote:
> On 12/12/20 7:47 PM, Arlen Holder wrote:
>
> [snip]
>
>> Have you ever had a working PC that wouldn't go into the BIOS mode?
>> o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
>>
>> How did you resolve that issue?
>
> I have an old Dell that seems to have no way to enter setup other than
> to physically disconnect the hard drive (so no boot devices are available).
>
Dell uses f1 or f2 or something different from the standard del key.
> On 12/12/20 7:47 PM, Arlen Holder wrote:
>
> [snip]
>
>> Have you ever had a working PC that wouldn't go into the BIOS mode?
>> o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
>>
>> How did you resolve that issue?
>
> I have an old Dell that seems to have no way to enter setup other than
> to physically disconnect the hard drive (so no boot devices are available).
>
Arlen Holder
Dec 15, 2020, 7:48:33 AM12/15/20
to
On Sun, 13 Dec 2020 07:13:54 -0500, Paul wrote:
> I had this happen here recently.
SOLVED:
> I had this happen here recently.
Hi Paul,
I apologize for not responding sooner, as I did solve the BIOS problem.
The instant I removed everything from the desktop save for the essentials,
it booted to the BIOS (by pressing the F10 key at POST for my HP Pavilion).
Once I was in the BIOS, I could easily set the AMD-V on.
o <https://i.postimg.cc/RhSXCJQn/cmos04.jpg> Turn on AMD-V in the BIOS
Where, for emulation, that AMD-V in the BIOS was absolutely essential.
Yet, for subsequent emulation purposes... it turns out that, despite what
it says on the net, it doesn't matter whether Hyper-V "stuff" is on or off:
o <https://i.postimg.cc/zD2nHQqQ/cmos05.jpg> Hyper-V doesn't matter
o <https://i.postimg.cc/NF900ZCY/cmos07.jpg> Hyper-V doesn't matter
UPDATE:
This is the BIOS/AMD-V firmware problem I was trying to solve (and did):
o <https://i.postimg.cc/fWSnSJXQ/cmos08.jpg> Emulation fails w/o AMD-V
o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Access CMOS settings
o <https://i.postimg.cc/QdqTpBsq/cmos02.jpg> Genymotion needs AMD-V
o <https://i.postimg.cc/d1gkqrmJ/cmos03.jpg> VirtualBox needs AMD-V
o <https://i.postimg.cc/RhSXCJQn/cmos04.jpg> Turn on AMD-V in the BIOS
o <https://i.postimg.cc/zD2nHQqQ/cmos05.jpg> Hyper-V doesn't matter
o <https://i.postimg.cc/NF900ZCY/cmos07.jpg> Hyper-V doesn't matter
o <https://i.postimg.cc/hjGjkX9X/cmos06.jpg> Genymotion emulation working
This is the Android Studio root problem I was trying to solve:
o <https://i.postimg.cc/1tvysJY1/as01.jpg> code working on phone
o <https://i.postimg.cc/nLRWdFB1/as02.jpg> code working in Genymotion
o <https://i.postimg.cc/65NKJvkt/as03.jpg> Google emulator fails on AMD CPU
o <https://i.postimg.cc/QCQRxf2s/as04.jpg> Google emulator always offline
o <https://i.postimg.cc/qB2fL7zY/as05.jpg> Google emulator always times out
o <https://i.postimg.cc/02vTHqSN/as06.jpg> Hyper-V off doesn't matter
o <https://i.postimg.cc/Fsx2MnbV/as07.jpg> Hyper-V on doesn't matter
Once I figured out the unintuitive step of enabling AMD-V but disabling
Intel Hyper-V in Windows 10, then it was time to add the emulators.
Adding the native Android Studio emulators works fine, but they're slow.
o So below are instructions for also adding faster Genymotion emulators.
After you get your "Hello World" running on your device over USB:
o <https://i.postimg.cc/1tvysJY1/as01.jpg>
It's time to get "Hello World" running in Genymotion Android emulation:
0. For AMD CPUs, you have to turn ON the AMD-V hypervisor in your BIOS
o Win+R > msinfo32
Windows version: Windows 10, 10.0, version 2004, build: 19041
Hardware: NY549AA-ABA p6230y, HP-Pavilion, FOXCONN, ALOE
CPU: Authentic AMD AMD Phenom(tm) II X4 810
BIOS Version/Date: American Megatrends Inc. 5.02, 8/31/2009
SMBIOS Version 2.6
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes <== this is critical!
Windows version: Windows 10, 10.0, version 2004, build: 19041
Hardware: NY549AA-ABA p6230y, HP-Pavilion, FOXCONN, ALOE
CPU: Authentic AMD AMD Phenom(tm) II X4 810
BIOS Version/Date: American Megatrends Inc. 5.02, 8/31/2009
SMBIOS Version 2.6
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Data Execution Protection Yes
Here are the before-and-after screenshots for BIOS enabling of AMD-V:
<https://i.postimg.cc/fWSnSJXQ/cmos08.jpg> Emulation fails w/o AMD-V
<https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Access CMOS settings
<https://i.postimg.cc/QdqTpBsq/cmos02.jpg> Genymotion needs AMD-V
<https://i.postimg.cc/d1gkqrmJ/cmos03.jpg> VirtualBox needs AMD-V
<https://i.postimg.cc/RhSXCJQn/cmos04.jpg> Turn on AMD-V in the BIOS
<https://i.postimg.cc/zD2nHQqQ/cmos05.jpg> Intel-V doesn't matter
<https://i.postimg.cc/NF900ZCY/cmos07.jpg> Hyper-V doesn't matter
<https://i.postimg.cc/hjGjkX9X/cmos06.jpg> Genymotion emulation working
Note: As far as I have tested, it doesn't matter whether the Intel
hypervisor is enabled or disabled in your Windows 10 settings
(even as a zillion articles say you "must" either check or not check)
o Win+R > ms-settings:optionalfeatures > More Windows features
o Turn Windows Features on or off
[_]Core Isolation
[_]Credential Guard
[_]Hyper-V
[_]Virtual Machine Platform <== it doesn't seem to matter if checked
[_]Windows Hypervisor Platform <== doesn't seem to matter if checked
[_]Windows Sandbox
[_]Windows Subsystem for Linux version 2
1. Install & run Genymotion Personal Edition (with VirtualBox)
<https://www.genymotion.com/>
(Follow instructions at the Genymotion web site, which are pretty good.)
2. Once you have Genymotion installed & Android emulation running,
then find your SDK path (if you don't already know it)
AS:Tools > SDK Manager > Android SDK Locations
3. Set ADB in Genymotion to point to that Android SDK path
Genymotion:Settings > ADB
Change from:
(o)Use Genymotion Android Tools (default)
(_)Use custom Android SDK Tools
Change to:
(_)Use Genymotion Android Tools (default)
(o)Use custom Android SDK Tools
[Browse]C:/app/editor/android/sdk
4. In Genymotion, to add a device, press the red "(+)" sign at the top.
Choose any Android device & API to emulate & press "Install"
Once installed, press the Genymotion "Start" button to boot it.
You should get an Android emulation window after a minute or two.
5. Now install the Genymotion plugins into Android Studio:
AS:File > Settings > Plugins > Marketplace > Genymotion > Install
Restart Android Studio to apply changes to plugins.
6. Now point Android Studio to your Genymotion folder
AS:File > Tools > Emulator > Genymotion Plugin >
Select the path to the Genymotion folder
C:\app\editor\android\emu\genymotion
7. Start Genymotion from your taskbar cascade accordion foldout menu
Taskbar > menu > editor > android > genymotion
Start the emulator from inside of Genymotion's installed devices
Wait for the emulator to start in a separate window in Windows.
8. From inside Android Studio, you can now select that emulator.
Then run your code on that emulator.
<https://i.postimg.cc/nLRWdFB1/as02.jpg>
In summary, you now should have the following:
A. Android Studio runs "Hello World" on your phone over USB
<https://i.postimg.cc/1tvysJY1/as01.jpg>
B. Android Studio runs "Hello World" over Google Android emulation:
<https://i.postimg.cc/65NKJvkt/as03.jpg> Google emulator fails
<https://i.postimg.cc/QCQRxf2s/as04.jpg> Google emulator always offline
<https://i.postimg.cc/qB2fL7zY/as05.jpg> Google emulator times out
Note: It's rare for me to "just give up" but for the life of me,
I couldn't get the native AVD Android emulation to do anything
but show up blank on my AMD CPU, and, judging from the references,
many (many) people have the same (unsolved) problem set on AMD.
<https://i.postimg.cc/02vTHqSN/as06.jpg> Hyper-V off doesn't matter
<https://i.postimg.cc/Fsx2MnbV/as07.jpg> Hyper-V on doesn't matter
C. Android Studio runs "Hello World" over Genymotion emulation:
<https://i.postimg.cc/nLRWdFB1/as02.jpg>
Everything above except item "B" was relatively easy; B was impossible.
o <https://stackoverflow.com/questions/20155376/android-stop-emulator-from-command-line>
o <https://stackoverflow.com/questions/3152681/android-emulator-5554-offline>
o <https://stackoverflow.com/questions/59974253/android-studio-problem-timed-out-waiting-for-process-to-appear-on-device>
o <https://stackoverflow.com/questions/62343011/android-studio-waiting-for-all-target-devices-to-come-online-and-black-avd-err>
o <https://stackoverflow.com/questions/62560767/android-emulator-stays-with-black-screen-after-trying-a-lot-of-things-to-fix-it>
o <https://stackoverflow.com/questions/62892194/android-emulator-was-not-loading-in-android-4-0>
(etc., there are many, most unresolved or arbitrarily resolved)
All these exact same concurrent errors exist in all articles:
a. AVD pops up the Android emulator; but it is black & unresponsive.
b. STATUS: Waiting for all target devices to come online
c. ERROR: AVD Manager Timed out after 300seconds waiting for emulator to come online.
d. AS:Tools > Troubleshoot device connections > Rescan devices
Found 1 Android device(s) with possible problems:
emulator-5554 - Device is currently in the offline state
e. Win+R > cmd
c:\> adb devices
List of devices attached
emulator-5554 offline
See also:
o Have you ever had a working PC that wouldn't go into the BIOS mode?
<https://groups.google.com/g/alt.comp.microsoft.windows/c/p5RvsY_M978>
o Can someone please explain the logic of turning AMD-V "ON" in the BIOS, & then turning Intel Hyper-V "OFF" in "Turn Windows features on or off" just to get Android emulation to work on WIndows 10?
<https://groups.google.com/g/alt.comp.microsoft.windows/c/zcSpBmmc6eM>
o Tutorial Installing Android Studio 4.1.1 on Windows 10 (AMD CPU)
<https://groups.google.com/g/comp.mobile.android/c/g3ymz5CPsIk>
<https://groups.google.com/g/comp.mobile.android/c/aW64zYeBtF0>
--
Posted out of the goodness of my heart, to help others, where I can.
Arlen Holder
Dec 15, 2020, 8:20:29 AM12/15/20
to
On Tue, 15 Dec 2020 12:30:22 +0000 (UTC), Arlen Holder wrote:
> <https://i.postimg.cc/zD2nHQqQ/cmos05.jpg> Intel-V doesn't matter
> <https://i.postimg.cc/NF900ZCY/cmos07.jpg> Hyper-V doesn't matter
Ooops.
> <https://i.postimg.cc/zD2nHQqQ/cmos05.jpg> Intel-V doesn't matter
> <https://i.postimg.cc/NF900ZCY/cmos07.jpg> Hyper-V doesn't matter
I forgot to mention why it matters that Hyper-V doesn't seem to matter.
o Genymotion seems to claim that it does matter that Hyper-V be turned off.
But, in my tests, Genymotion Android emulation worked with or without the
Intel Hyper-V turned on or off.
What mattered absolutely was that AMD-V be turned on (in the BIOS).
However, to support my claim that Genymotion says to enable Hyper-V (yet, I
found it didn't seem to matter), here are cites supporting that statement:
o Genymotion Desktop and Hyper-V (Windows 8/8.1/10)
<https://support.genymotion.com/hc/en-us/articles/360002732677>
o "An error has occurred while trying to create a virtualbox host-only
network interface" (Windows)
<https://support.genymotion.com/hc/en-us/articles/360002706697>
o "Your CPU is incompatible with virtualization technologies" error
<https://support.genymotion.com/hc/en-us/articles/360002737597>
o "Unable to start the Virtual Device" error
<https://support.genymotion.com/hc/en-us/articles/360002718198>
o How to disable Memory integrity in Windows 10?
<https://support.genymotion.com/hc/en-us/articles/360009163277>
In summary:
1. AMD-V absolutely must be on for Genymotion or Google Android emulation
2. Intel Hyper-V stuff doesn't seem to matter whether it's on or off.
--
Posted out of the goodness of my heart to help others do this more easily.
Mark Lloyd
Dec 15, 2020, 12:41:34 PM12/15/20
to
On 12/14/20 12:28 PM, Bob F wrote:
[snip]
>> I have an old Dell that seems to have no way to enter setup other than
>> to physically disconnect the hard drive (so no boot devices are
>> available).
>>
>
> Dell uses f1 or f2 or something different from the standard del key.
I always try F1, F2, and ESC.
--
10 days until the winter celebration (Fri, Dec 25, 2020 12:00:00 AM for
"Give a man a fire and he's warm for a day, but set fire to him and he's
warm for the rest of his life." --Terry Pratchett
[snip]
>> I have an old Dell that seems to have no way to enter setup other than
>> to physically disconnect the hard drive (so no boot devices are
>> available).
>>
>
> Dell uses f1 or f2 or something different from the standard del key.
--
10 days until the winter celebration (Fri, Dec 25, 2020 12:00:00 AM for
"Give a man a fire and he's warm for a day, but set fire to him and he's
warm for the rest of his life." --Terry Pratchett
Arlen Holder
Dec 15, 2020, 12:51:08 PM12/15/20
to
On Tue, 15 Dec 2020 11:41:32 -0600, Mark Lloyd wrote:
>> Dell uses f1 or f2 or something different from the standard del key.
>
> I always try F1, F2, and ESC.
On my HP Pavilion, it says, at POST, to press "F10" for BIOS Setup
>> Dell uses f1 or f2 or something different from the standard del key.
>
> I always try F1, F2, and ESC.
o But I'm never sure if it's a "tap tap tap" or "long press" or what
For my HP Pavilion, the Boot Menu is "Escape" & the Diagnostic menu is "F9"
o But again, I'm never sure if it's a "tap tap tap" or "long press" or what
John McGaw
Dec 26, 2020, 9:58:42 AM12/26/20
to
On 12/12/2020 8:47 PM, Arlen Holder wrote:
snip...
dependent upon a particular keyboard connection. In old MBs it was not
uncommon for them to watch for signals from PS2 keyboards only. Any USB
keyboards would be ignored until after the boot and some driver or other
was loaded. I have one more modern MB, a "Genuine Intel" of some sort or
other which ignores input from a wireless keyboard/pad until after boot
even though the KB's adapter is plugged into a USB port. If I plug in a
"real" USB keyboard of any description it will work during boot. Luckily
the MB in question is willing to overlook the missing keyboard and boot anyway.
Oh, and yes, I've had a couple of mystery MBs were I had to play guessing
games about which key and precisely when to press it to achieve BIOS.
--
Bodger's Dictum: Artifical intelligence
can never overcome natural stupidity.
snip...
> Have you ever had a working PC that wouldn't go into the BIOS mode?
> o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
>
> How did you resolve that issue?
>
Yes. More than once. Usually it is a matter of the BIOS mode being
> o <https://i.postimg.cc/GpkgdmxT/cmos01.jpg> Won't go into BIOS
>
> How did you resolve that issue?
>
dependent upon a particular keyboard connection. In old MBs it was not
uncommon for them to watch for signals from PS2 keyboards only. Any USB
keyboards would be ignored until after the boot and some driver or other
was loaded. I have one more modern MB, a "Genuine Intel" of some sort or
other which ignores input from a wireless keyboard/pad until after boot
even though the KB's adapter is plugged into a USB port. If I plug in a
"real" USB keyboard of any description it will work during boot. Luckily
the MB in question is willing to overlook the missing keyboard and boot anyway.
Oh, and yes, I've had a couple of mystery MBs were I had to play guessing
games about which key and precisely when to press it to achieve BIOS.
--
Bodger's Dictum: Artifical intelligence
can never overcome natural stupidity.
knuttle
Dec 26, 2020, 11:01:05 AM12/26/20
to
On 12/26/2020 9:58 AM, John McGaw wrote:
>
> Yes. More than once. Usually it is a matter of the BIOS mode bein
Some years ago you could access the bios form any power icon with a
>
> Yes. More than once. Usually it is a matter of the BIOS mode bein
combination of a control key and the mouse. It has been year and I can
not find my notes for the exact steps.
HOWEVER this also works
Method #2: Use Windows 10’s start menu
As computers have become more technologically advanced than ever, they
boot up in seconds before our eyes. This leaves little room for pressing
any hotkeys and can leave those looking to get into their BIOS settings
puzzled.
For PC users who aren’t able to catch that tiny window to use their
hotkey, this method of entering BIOS can be completed through your
computer settings.
Step 1. Access your Windows settings
Navigate to your Windows start menu and select “Settings” located on the
left panel. You can also access your Windows setting by using Windows
shortcut keys Windows + I.
Step 2. Select “Update & security”
Within this window, you may need to scroll down to find the “Update &
security” button.
Step 3. Select “Recovery"
Step 4. Click “Restart now”
Under “Advanced startup” you will see a “Restart now” button that allows
you to reboot your PC for configuration or restoration.
After your PC boots back up, you will be met with a special menu that
gives you the option to “Use a device,” “Continue,” “Turn off your PC,”
or “Troubleshoot.”
Step 5. Select “Troubleshoot”
Within this window, select “Advanced options” then select “UEFI Firmware
Settings.” This will allow you to enter BIOS on your Windows 10 PC.
Step 6. Confirm your restart
If your PC is running Windows 8.1 or Windows 8, these methods will also
work for your older operating system.
Mark Lloyd
Dec 27, 2020, 6:25:51 PM12/27/20
to
On 12/26/20 8:58 AM, John McGaw wrote:
[snip]
> Yes. More than once. Usually it is a matter of the BIOS mode being
> dependent upon a particular keyboard connection. In old MBs it was not
> uncommon for them to watch for signals from PS2 keyboards only. Any USB
> keyboards would be ignored until after the boot and some driver or other
> was loaded.
Usually, I would prefer USB. However, I used to have some older systems
without USP support in BIOS, and I would use a PS/2 keyboard for those.
IIRC, that was true with the PII-class Celeron with "Y2K compliant"
motherboard.
[snip]
> Oh, and yes, I've had a couple of mystery MBs were I had to play
> guessing games about which key and precisely when to press it to achieve
> BIOS.
Of those I've had, ESC DEL F1 or F2 worked on most so I try all those
keys one after another.
--
Mark Lloyd
http://notstupid.us/
"If fascism ever comes to America, it will be wrapped in the flag and
carrying a cross." -- Upton Sinclair, Huey P. Long, and others.
[snip]
> Yes. More than once. Usually it is a matter of the BIOS mode being
> dependent upon a particular keyboard connection. In old MBs it was not
> uncommon for them to watch for signals from PS2 keyboards only. Any USB
> keyboards would be ignored until after the boot and some driver or other
> was loaded.
without USP support in BIOS, and I would use a PS/2 keyboard for those.
IIRC, that was true with the PII-class Celeron with "Y2K compliant"
motherboard.
[snip]
> Oh, and yes, I've had a couple of mystery MBs were I had to play
> guessing games about which key and precisely when to press it to achieve
> BIOS.
keys one after another.
--
Mark Lloyd
http://notstupid.us/
"If fascism ever comes to America, it will be wrapped in the flag and
carrying a cross." -- Upton Sinclair, Huey P. Long, and others.
Arlen Holder
Dec 28, 2020, 12:13:13 AM12/28/20
to
On Sun, 27 Dec 2020 17:25:49 -0600, Mark Lloyd wrote:
> Usually, I would prefer USB. However, I used to have some older systems
> without USP support in BIOS, and I would use a PS/2 keyboard for those.
> IIRC, that was true with the PII-class Celeron with "Y2K compliant"
> motherboard.
UPDATE:
> Usually, I would prefer USB. However, I used to have some older systems
> without USP support in BIOS, and I would use a PS/2 keyboard for those.
> IIRC, that was true with the PII-class Celeron with "Y2K compliant"
> motherboard.
The solution, strangely enough, was to remove everything from every port
possible, nary even a mouse, with just a mechanical keyboard in place.
Then, after POST, an F10 opened to the BIOS setup where I was able to
enable AMD-V, which then enabled Android emulators to work on Windows
inside of a virtual machine (in my case, inside of VirtualBox).
See also:
o Have you gotten Genymotion freeware to work on an older AMD CPU on Win10?
<https://groups.google.com/forum/#!topic/alt.comp.freeware/AtHp2BtOcxk>
o How to get Genymotion Android emulation to work on an AMD Win10Pro desktop
<https://groups.google.com/d/msg/alt.comp.freeware/AtHp2BtOcxk/lQRxtMuNAgAJ>
--
Posted out of the goodness of my heart, as always, to voluntarily help all.
0 new messages