Laptop goes to the BIOS

On 2020-07-20 15:38, Johnny wrote:
I have been there. I hate UEFI.

Done right, it is a charm. Done wrong, well ...

T wrote:
On 2020-07-20 15:34, Paul wrote:
T wrote:
On 2020-07-19 11:46, BugHunter wrote:
I have a 5 year old Laptop Asus A540S here
and when I start it it goes straight to the
BIOS.

Now I have a Live stick with Linux Mint and there
he would like to start up. I can do without
problems on the 2 partitions of the hard disk
look, it all looks healthy.

Any idea what I can still do?



Hi Bug,

I see this all the time. It "typically" (watch the
weasel word) means the bios can't find anything to
boot off of.

Get yourself a W10 install flash drive and boot
off it.

You can create a W10 install flash drive from your
Mint stick. Let me know if you need directions

Go into to maintenance and run the
repair boot thingy:

Windows 10 Won’t Boot? Fix it with Startup Repair and BootRec Commands
By

https://www.groovypost.com/howto/fix...epair-bootrec/


And if it works, you got lucky.

And if you got lucky, DO NOT TEST FATE! Replace your
hard drive. Now is a good excuse to upgrade to
an SSD drive!

There's a different though, between what happens
when no bootable device is detected, and just plain
being thrown into the BIOS.

You bet. Typically, it tells you to insert
a bootable media and press any key. The give
away that the bios sucked was that he could boot
off a Mint stick.

And Bug is discovering, as I am right now, that UEFI
is a bottomless pit of fun. And all it takes is
Canonical designing new shims with new levels of
overreach (MOKutil), to make our lives miserable.

Now I've discovered that when you shutdown an OS,
it doesn't actually shut down. The OS *hands back*
to UEFI. And if UEFI is in a defective mood,
after the OS screen disappears, you will be
faced by a UEFI underline cursor on the screen
and no activity. Now, press the RESET button.
Nothing happens!

Welcome to hell.

Paul

Ha. Been there, done that. Some BIOS'es really
suck. Even worse if the boot sectors get corrupted
on the hard drive. He should run the boot repair
utility off the install media.

The problem is that we all expect the BIOS to work
right. And boot sectors to never get corrupted.
(I back up my boot sector on my host Fedora machines
and I have documentation on how to rebuild them,
if needed. So far so good.)

What typically happens, is you use TestDisk, you gain
access to the ESP, and visually, nothing seems amiss.

Sometimes, there are too many folders in the UEFI storage
area. Occasionally, you do see smart naming in there,
maybe Windows, Ubuntu, and Manjaro have their own folders,
but other times, funny things happen and a folder is
being shared. Maybe Zorin is using the Ubuntu folder.

And the quantity of files, and the filetypes in there,
keep changing. Which files are current and operational ?
Which files are decoys ? Is that a wooden duck floating
in the water, or a really clever real duck ?

These are the side effects and benefits of having yet another
OS living on your computer. an OS that can squeeze you by the
nuts when it wants.

You can only boot repair... if you can boot and repair.
More than one person has come on here, telling you they
can't boot no more. I've had people report just about
complete insanity on their Dell. No amount of powering
off and on, helps. The BIOS won't even scan all storage
types any more (you can't get a CD to boot, nor a USB
stick).

It's fun to say "dude, run your Repair thingy", but the
sad truth is, this only worked in the old days, around
2008. Back then, you could say that, and it would come
to pass. Today, not so much. You can be looking at
functional brickage today, and you need "Houdini at
the computer store" to help.

The one good thing, is my motherboard has an autonomous
BIOS flasher. It can flash upgrade the BIOS chip, when
no CPU is in the socket and no RAM is in the DIMM slots.
It's a microcontroller of its own. And when I get in
trouble some day because of UEFI, that's when I'll be
testing that interface :-/ I sure hope flashing the BIOS
clears the NVRAM at the same time...

Paul

On 2020-07-20 17:21, Paul wrote:
T wrote:
On 2020-07-20 15:34, Paul wrote:
T wrote:
On 2020-07-19 11:46, BugHunter wrote:
I have a 5 year old Laptop Asus A540S here
and when I start it it goes straight to the
BIOS.

Now I have a Live stick with Linux Mint and there
he would like to start up. I can do without
problems on the 2 partitions of the hard disk
look, it all looks healthy.

Any idea what I can still do?



Hi Bug,

I see this all the time.Â* It "typically" (watch the
weasel word) means the bios can't find anything to
boot off of.

Get yourself a W10 install flash drive and boot
off it.

You can create a W10 install flash drive from your
Mint stick.Â* Let me know if you need directions

Go into to maintenance and run the
repair boot thingy:

Windows 10 Won’t Boot? Fix it with Startup Repair and BootRec Commands
By

https://www.groovypost.com/howto/fix...epair-bootrec/


And if it works, you got lucky.

And if you got lucky, DO NOT TEST FATE!Â* Replace your
hard drive.Â* Now is a good excuse to upgrade to
an SSD drive!

There's a different though, between what happens
when no bootable device is detected, and just plain
being thrown into the BIOS.

You bet.Â* Typically, it tells you to insert
a bootable media and press any key.Â* The give
away that the bios sucked was that he could boot
off a Mint stick.

And Bug is discovering, as I am right now, that UEFI
is a bottomless pit of fun. And all it takes is
Canonical designing new shims with new levels of
overreach (MOKutil), to make our lives miserable.

Now I've discovered that when you shutdown an OS,
it doesn't actually shut down. The OS *hands back*
to UEFI. And if UEFI is in a defective mood,
after the OS screen disappears, you will be
faced by a UEFI underline cursor on the screen
and no activity. Now, press the RESET button.
Nothing happens!

Welcome to hell.

Â*Â*Â* Paul

Ha.Â* Been there, done that.Â* Some BIOS'es really
suck.Â* Even worse if the boot sectors get corrupted
on the hard drive.Â* He should run the boot repair
utility off the install media.

The problem is that we all expect the BIOS to work
right.Â* And boot sectors to never get corrupted.
(I back up my boot sector on my host Fedora machines
and I have documentation on how to rebuild them,
if needed.Â* So far so good.)

What typically happens, is you use TestDisk, you gain
access to the ESP, and visually, nothing seems amiss.

Sometimes, there are too many folders in the UEFI storage
area. Occasionally, you do see smart naming in there,
maybe Windows, Ubuntu, and Manjaro have their own folders,
but other times, funny things happen and a folder is
being shared. Maybe Zorin is using the Ubuntu folder.

And the quantity of files, and the filetypes in there,
keep changing. Which files are current and operational ?
Which files are decoys ? Is that a wooden duck floating
in the water, or a really clever real duck ?

These are the side effects and benefits of having yet another
OS living on your computer. an OS that can squeeze you by the
nuts when it wants.

You can only boot repair... if you can boot and repair.
More than one person has come on here, telling you they
can't boot no more. I've had people report just about
complete insanity on their Dell. No amount of powering
off and on, helps. The BIOS won't even scan all storage
types any more (you can't get a CD to boot, nor a USB
stick).

It's fun to say "dude, run your Repair thingy", but the
sad truth is, this only worked in the old days, around
2008. Back then, you could say that, and it would come
to pass. Today, not so much. You can be looking at
functional brickage today, and you need "Houdini at
the computer store" to help.

The one good thing, is my motherboard has an autonomous
BIOS flasher. It can flash upgrade the BIOS chip, when
no CPU is in the socket and no RAM is in the DIMM slots.
It's a microcontroller of its own. And when I get in
trouble some day because of UEFI, that's when I'll be
testing that interface :-/ I sure hope flashing the BIOS
clears the NVRAM at the same time...

Â*Â* Paul


ya, but you have to try the boot repair thingy
anyway, just in case. My customers do not dual
boot.

On my dual legacy/EUFI Fedora flash drive, I reserve
a 1M blank spot at the beginning before insalling
things. Some machines it will boot legacy, some EUFI
but always seems to work one way or another.

Every since I discovered Virtual Machines, I have
thought dual boot was foolish.

BIOS'es can be as buggy as Windows.

T wrote:

ya, but you have to try the boot repair thingy
anyway, just in case. My customers do not dual
boot.

On my dual legacy/EUFI Fedora flash drive, I reserve
a 1M blank spot at the beginning before insalling
things. Some machines it will boot legacy, some EUFI
but always seems to work one way or another.

Every since I discovered Virtual Machines, I have
thought dual boot was foolish.

BIOS'es can be as buggy as Windows.

The reason we multiboot, is to help others when they
get in a bind.

Not because it's a particular good idea.

It also exposes the quality of the boot workmanship,
when one of the distros, time and again, tips stuff over.

Right now, thanks to Ubuntu, the boot menu comes up on
ttyS0, because I happened to be using ttyS0 when
updates were done. So now the blasted menu thinks
ttyS0 is where it should go.

Paul

Paul wrote:
T wrote:
On 2020-07-19 11:46, BugHunter wrote:
I have a 5 year old Laptop Asus A540S here
and when I start it it goes straight to the
BIOS.

Now I have a Live stick with Linux Mint and there
he would like to start up. I can do without
problems on the 2 partitions of the hard disk
look, it all looks healthy.

Any idea what I can still do?



Hi Bug,

I see this all the time.Â* It "typically" (watch the
weasel word) means the bios can't find anything to
boot off of.

Get yourself a W10 install flash drive and boot
off it.

You can create a W10 install flash drive from your
Mint stick.Â* Let me know if you need directions

Go into to maintenance and run the
repair boot thingy:

Windows 10 Won’t Boot? Fix it with Startup Repair and BootRec Commands
By

https://www.groovypost.com/howto/fix...epair-bootrec/


And if it works, you got lucky.

And if you got lucky, DO NOT TEST FATE!Â* Replace your
hard drive.Â* Now is a good excuse to upgrade to
an SSD drive!

There's a different though, between what happens
when no bootable device is detected, and just plain
being thrown into the BIOS.

And Bug is discovering, as I am right now, that UEFI
is a bottomless pit of fun. And all it takes is
Canonical designing new shims with new levels of
overreach (MOKutil), to make our lives miserable.

Now I've discovered that when you shutdown an OS,
it doesn't actually shut down. The OS *hands back*
to UEFI. And if UEFI is in a defective mood,
after the OS screen disappears, you will be
faced by a UEFI underline cursor on the screen
and no activity. Now, press the RESET button.
Nothing happens!

Welcome to hell.

Well if MS didn't foist this "secure" boot (cough-cough protectionist
BS) onto UEFI we wouldn't have these issues. Linux distros wouldn't have
to fool with shims just to allow people to install the OS of their
choice on *their* computer.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

In article , lid says...

I have a 5 year old Laptop Asus A540S here
and when I start it it goes straight to the
BIOS.

Now I have a Live stick with Linux Mint and there
he would like to start up. I can do without
problems on the 2 partitions of the hard disk
look, it all looks healthy.

Any idea what I can still do?

I'm not sure anyone has quite given you the answer which you need, given my reading of what is
a rather ambiguous post. So here's mine.

I'm guessing the machine was, until recently, running Windows normally. Now, when you boot it
up, it goes to the BIOS ("setup") screens.

If that's the case, then it's likely your disk has some corruption. It may be that the disk is
worn out, in which case you need to avoid doing anything with it until you are ready to recover
any data you need. But it may be that only a small area is corrupt, and that can be repairable
so that Windows can boot again.

If you've already successfully booted from a Linux stick and can see files and folders, then
you should be able to recover data at least.

It's very helpful to get an idea of how "healthy" the disk is. If you can extract the disk,
mount it on another PC/laptop (via a USB3.0 adapter perhaps) then you can download and run a
utility which can assess the "SMART" metrics of your disk. I use Hard Disk Sentinel (paid) but
this is also good, and free for personal use: https://www.passmark.com/products/diskcheckup/.
Speccy (free) can also report SMART metrics. If you can't make sense of them, post here and
someone will interpret them for you.

So you need to decide it it's worth trying to fix your Windows installation, or just recover
data from a deteriorating disk.

To fix the installation, try creating Windows 10 installation media (USB stick) using the
"Media Creation Tool" on another PC. Then boot the laptop from that, and pick "repair your
computer". There are a range of other techniques available if that doesn't work, including
using the "bootrec" command from a command prompt (still within the installation media boot).
If none of those work, then you may be able to restore the partition using the "Testdisk"
utility, but all this is getting farther and farther from what most users are comfortable
doing. But remember, if the disk is far enough gone, you'll only make it harder to recover
data. If the data is particularly valuable, then you should "clone" everything to another disk
before doing anything else, using Acronis True Image or any of a range of similar tools. True
Image can "mount" a clone it has created, giving you immediate access to the files, which is a
useful feature.

If all you want is to recover data, you can try mounting the disk on another system - you may
simply be able to copy the files off. If you're comfortable with Linux, and can boot the
laptop from the USB stick, then once the data is copied to other media you could assess the
disk health and then just reinstall Windows from scratch if the underlying disk is still good.

It's hard to write a "complete" account - it would be a book, not a post. So it's often
sensible to work directly with someone with experience of the many possible issues which can
occur.

I hope that's helpful. Good luck.

--

Phil, London

On 2020-07-21 04:14, Jonathan N. Little wrote:
Paul wrote:
T wrote:
On 2020-07-19 11:46, BugHunter wrote:
I have a 5 year old Laptop Asus A540S here
and when I start it it goes straight to the
BIOS.

Now I have a Live stick with Linux Mint and there
he would like to start up. I can do without
problems on the 2 partitions of the hard disk
look, it all looks healthy.

Any idea what I can still do?



Hi Bug,

I see this all the time.Â* It "typically" (watch the
weasel word) means the bios can't find anything to
boot off of.

Get yourself a W10 install flash drive and boot
off it.

You can create a W10 install flash drive from your
Mint stick.Â* Let me know if you need directions

Go into to maintenance and run the
repair boot thingy:

Windows 10 Won’t Boot? Fix it with Startup Repair and BootRec Commands
By

https://www.groovypost.com/howto/fix...epair-bootrec/


And if it works, you got lucky.

And if you got lucky, DO NOT TEST FATE!Â* Replace your
hard drive.Â* Now is a good excuse to upgrade to
an SSD drive!

There's a different though, between what happens
when no bootable device is detected, and just plain
being thrown into the BIOS.

And Bug is discovering, as I am right now, that UEFI
is a bottomless pit of fun. And all it takes is
Canonical designing new shims with new levels of
overreach (MOKutil), to make our lives miserable.

Now I've discovered that when you shutdown an OS,
it doesn't actually shut down. The OS *hands back*
to UEFI. And if UEFI is in a defective mood,
after the OS screen disappears, you will be
faced by a UEFI underline cursor on the screen
and no activity. Now, press the RESET button.
Nothing happens!

Welcome to hell.

Well if MS didn't foist this "secure" boot (cough-cough protectionist
BS) onto UEFI we wouldn't have these issues. Linux distros wouldn't have
to fool with shims just to allow people to install the OS of their
choice on *their* computer.


The better BIOS'es allow yo to press F11 and
pick which device to boot from.

I do believe "Windows boot manager" is their Secure
Boot, but I could be wrong. The crappier BIOS'es,
you have to go into BIOS and turn off Windows Boot
Manager.

I see no security gain from this silliness and wish
they'd drop it.

On 2020-07-21 3:16 p.m., T wrote:
On 2020-07-21 04:14, Jonathan N. Little wrote:
Paul wrote:
T wrote:
On 2020-07-19 11:46, BugHunter wrote:
I have a 5 year old Laptop Asus A540S here
and when I start it it goes straight to the
BIOS.

Now I have a Live stick with Linux Mint and there
he would like to start up. I can do without
problems on the 2 partitions of the hard disk
look, it all looks healthy.

Any idea what I can still do?



Hi Bug,

I see this all the time.Â* It "typically" (watch the
weasel word) means the bios can't find anything to
boot off of.

Get yourself a W10 install flash drive and boot
off it.

You can create a W10 install flash drive from your
Mint stick.Â* Let me know if you need directions

Go into to maintenance and run the
repair boot thingy:

Windows 10 Won’t Boot? Fix it with Startup Repair and BootRec Commands
By

https://www.groovypost.com/howto/fix...epair-bootrec/



And if it works, you got lucky.

And if you got lucky, DO NOT TEST FATE!Â* Replace your
hard drive.Â* Now is a good excuse to upgrade to
an SSD drive!

There's a different though, between what happens
when no bootable device is detected, and just plain
being thrown into the BIOS.

And Bug is discovering, as I am right now, that UEFI
is a bottomless pit of fun. And all it takes is
Canonical designing new shims with new levels of
overreach (MOKutil), to make our lives miserable.

Now I've discovered that when you shutdown an OS,
it doesn't actually shut down. The OS *hands back*
to UEFI. And if UEFI is in a defective mood,
after the OS screen disappears, you will be
faced by a UEFI underline cursor on the screen
and no activity. Now, press the RESET button.
Nothing happens!

Welcome to hell.

Well if MS didn't foist this "secure" boot (cough-cough protectionist
BS) onto UEFI we wouldn't have these issues. Linux distros wouldn't have
to fool with shims just to allow people to install the OS of their
choice on *their* computer.


The better BIOS'es allow yo to press F11 and
pick which device to boot from.

I do believe "Windows boot manager" is their Secure
Boot, but I could be wrong.Â* The crappier BIOS'es,
you have to go into BIOS and turn off Windows Boot
Manager.

I see no security gain from this silliness and wish
they'd drop it.


I have American Megatrends UEFI bios on both my last years Asus
motherboards and they behave very well although quite complicated, there
are literally dozens and dozens of changeable features so you have to
know what your doing before you start playing around in there.

The Boot Menu key on these boards is F8

Rene

On Tue, 21 Jul 2020 13:16:36 -0700
T wrote:

On 2020-07-21 04:14, Jonathan N. Little wrote:
Paul wrote:
T wrote:
On 2020-07-19 11:46, BugHunter wrote:
I have a 5 year old Laptop Asus A540S here
and when I start it it goes straight to the
BIOS.

Now I have a Live stick with Linux Mint and there
he would like to start up. I can do without
problems on the 2 partitions of the hard disk
look, it all looks healthy.

Any idea what I can still do?



Hi Bug,

I see this all the time.Â* It "typically" (watch the
weasel word) means the bios can't find anything to
boot off of.

Get yourself a W10 install flash drive and boot
off it.

You can create a W10 install flash drive from your
Mint stick.Â* Let me know if you need directions

Go into to maintenance and run the
repair boot thingy:

Windows 10 Won’t Boot? Fix it with Startup Repair and BootRec
Commands By

https://www.groovypost.com/howto/fix...epair-bootrec/


And if it works, you got lucky.

And if you got lucky, DO NOT TEST FATE!Â* Replace your
hard drive.Â* Now is a good excuse to upgrade to
an SSD drive!

There's a different though, between what happens
when no bootable device is detected, and just plain
being thrown into the BIOS.

And Bug is discovering, as I am right now, that UEFI
is a bottomless pit of fun. And all it takes is
Canonical designing new shims with new levels of
overreach (MOKutil), to make our lives miserable.

Now I've discovered that when you shutdown an OS,
it doesn't actually shut down. The OS *hands back*
to UEFI. And if UEFI is in a defective mood,
after the OS screen disappears, you will be
faced by a UEFI underline cursor on the screen
and no activity. Now, press the RESET button.
Nothing happens!

Welcome to hell.

Well if MS didn't foist this "secure" boot (cough-cough
protectionist BS) onto UEFI we wouldn't have these issues. Linux
distros wouldn't have to fool with shims just to allow people to
install the OS of their choice on *their* computer.


The better BIOS'es allow yo to press F11 and
pick which device to boot from.

I do believe "Windows boot manager" is their Secure
Boot, but I could be wrong. The crappier BIOS'es,
you have to go into BIOS and turn off Windows Boot
Manager.

I see no security gain from this silliness and wish
they'd drop it.


I think it should be illegal.

When I bought this computer, I thought I wouldn't be able to install
Linux Mint on it.

I disabled secure boot, I thought, but that wasn't enough.

I had to go back and disable the Secure Boot key.

That didn't work either. I did some searching and found out I also had
to disable MS UEFI CA key. That worked.

Also, I have to press the Esc key when starting up, and the UEFI
firmware settings show up in the Grub menu.

T wrote:

I do believe "Windows boot manager" is their Secure
Boot, but I could be wrong

Yes you are incorrect, it would be easy if it was in the "Windows boot
manager" but it is not, it is in the firmware on the motherboard. This
makes simply wiping the drive and installing Linux not that simple.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Jonathan N. Little wrote:
T wrote:
I do believe "Windows boot manager" is their Secure
Boot, but I could be wrong

Yes you are incorrect, it would be easy if it was in the "Windows boot
manager" but it is not, it is in the firmware on the motherboard. This
makes simply wiping the drive and installing Linux not that simple.


My BIOS has an "Other OS" setting, which is the
setting I use so I can multi-boot Win7 and Win10
using GPT/UEFI.

Windows 7 does not support Secure Boot, and that's
why the "Other OS" setting is necessary.

But now, the Ubuntu foolishness is complaining and
dropping me into the UEFI shell, which I don't appreciate.
That setting, which I use, should have worked with
everything, because it disables Secure Boot. You
can be tortured multiple times with MOKutil, so it's
not like whatever passes for any "user choice" makes
a difference.

I've not heard of a "convenience setting", to tell
Ubuntu what to do.

And somehow, my boot menu now shows up on ttyS0, not
on the main screen. Again, a side effect of whatever
Ubuntu has been up to on the last kernel update.

I'm still able to run the machine, just barely.
I select an OS using putty at the moment, using
this machine.

Paul

BugHunter wrote:
I have a 5 year old Laptop Asus A540S here
and when I start it it goes straight to the
BIOS.

Now I have a Live stick with Linux Mint and there
he would like to start up. I can do without
problems on the 2 partitions of the hard disk
look, it all looks healthy.

Any idea what I can still do?


OK, I can find a stanza here. An example of
being dropped into shell, then booting.

My Asus user manual, shows there is a "Launch UEFI Shell from filesystem device"
in the Exit menu item. That will give you a shell. I would hope that
control-alt-delete will plop you out of the shell, if it gets
boring in there, but you'll only end up back in the BIOS again
until something changes.

https://wiki.archlinux.org/index.php...ware_Interface

If the shell does not list the partitions, the "map" command
may show them to you. That's how you will know there is an fs0:
partition available. You don't even know for sure, that this
is the correct identifier. The "listing" process they use here,
is all part of verifying what you expect to find in there. On
a multiboot hard drive, the EFI folder will have Microsoft, Ubuntu,
other distros folders. This particular device in their example,
does not have the same arrangement as my hard drive does.

Shell ls fs0:
EFI\
grub\

Shell ls fs0:EFI\
GRUB\

Shell ls fs0:EFI\GRUB\
grubx64.efi

Shell fs0:EFI\GRUB\grubx64.efi
Starting fs0:EFI\GRUB\grubx64.efi...

That's an example of manually loading boot materials.

If EFIVARS have been damaged, that can cause the drop to shell.
If the NVRAM has lost the EFI environment strings, that might
account for the behavior. And it has to be a guess, because
I am *not* "****ing up my BIOS for science" :-/ MOKutils,
any materials in the BIOS are *off limits*. I'm not
bricking a very expensive computer for some value of "fun".

Paul

On 2020-07-21 15:34, Paul wrote:
Jonathan N. Little wrote:
T wrote:
I do believe "Windows boot manager" is their Secure
Boot, but I could be wrong

Yes you are incorrect, it would be easy if it was in the "Windows boot
manager" but it is not, it is in the firmware on the motherboard. This
makes simply wiping the drive and installing Linux not that simple.


My BIOS has an "Other OS" setting, which is the
setting I use so I can multi-boot Win7 and Win10
using GPT/UEFI.

Windows 7 does not support Secure Boot, and that's
why the "Other OS" setting is necessary.

But now, the Ubuntu foolishness is complaining and
dropping me into the UEFI shell, which I don't appreciate.
That setting, which I use, should have worked with
everything, because it disables Secure Boot. You
can be tortured multiple times with MOKutil, so it's
not like whatever passes for any "user choice" makes
a difference.

I've not heard of a "convenience setting", to tell
Ubuntu what to do.

And somehow, my boot menu now shows up on ttyS0, not
on the main screen. Again, a side effect of whatever
Ubuntu has been up to on the last kernel update.

I'm still able to run the machine, just barely.
I select an OS using putty at the moment, using
this machine.

Â*Â* Paul

I use and almost exclusively sell Supermicro motherboards.
At times their BIOS needs a little work. But they always
boot either Linux or Windows just fine.

On Sun, 19 Jul 2020 20:20:00 +0100, ? Good Guy ?
wrote:

You have reached here because you are not using the correct Newsreader
such as Mozilla Thunderbird that is configured to read HTML posts.
Please use Thunderbird or just stand there and whistle for people to
come to your rescue.

HTML posts are not permitted in this newsgroup.

On Sun, 19 Jul 2020 21:25:38 +0200, BugHunter
wrote:

Corvid schreef op Zo 19 Jul 2020 om 12:15:
On 07/19/2020 11:46 AM, BugHunter wrote:
I have a 5 year old Laptop Asus A540S here and when I start it it
goes straight to the BIOS.

Linightz figured out his keyboard was causing the same problem.

https://rog.asus.com/forum/showthread.php?40888-Automatically-go-into-BIOS-every-time-start-up

Autoimmune disorder - your laptop is rejecting its own keyboard.

Now I have a Live stick with Linux Mint and there he would like to
start up. I can do without problems on the 2 partitions of the hard
disk look, it all looks healthy.

Any idea what I can still do?

Plug in another keyboard.


But in Linux Mint it works perfectly? Is it not
possible the Hard Drive is corrupt?

I was given a Dell Insperon that would not boot to the desktop.
Turned out to be a faulty keyboard.
I had to disconnect the inbuilt keyboard to use a USB keyboard.