Hello Everyone!

I recently set up a bootable USB with Linux, two different versions, Fedora and Ubuntu (I will be sharing the errors I'm getting while installing Ubuntu) and am at the starting point of the installation where I cannot progress any further.

After successfully booting onto the USB and choosing "Install Ubuntu" https://ibb.co/dBc1LK I get the following Errors: https://ibb.co/d9AVfK. The interesting part about his is that after a few minutes of waiting, screen will turn to what seems to be a loading screen for Ubuntu https://ibb.co/c0kr4e which also, after a few minutes, turns into a list of new errors https://ibb.co/fMJuPe
where nothing else happens.
I don't think I'm doing something wrong since creating a bootable USB is pretty straight forward and I only get to choose one option before the OS installation.
Any help clearing this situation out is much appreciated and I apologize if the structure of my post is in any way confusing or wrong, this being the first time I'm posting for help on the glorious Internet.

My laptop configuration:
CPU - Intel Core i7-8750H
GPU - NVIDIA GeForce GTX 1060 Max-Q (8GB GDDR5)
RAM - 16GB DDR4, 2666 MHz.
OS - Windows 10 Home

If there's any other info I should add, I'll happily do so!
Many thanks!

On the first screen there is an option to "Check disk for defects." Give that a try and get back to us.

You don't mention how you set up the bootable USB, or whether you used a Windows, Mac, or Linux computer to set it up, so I will refer you to these instructions (in case you tried something different before, and now want to try the officially supported method): https://tutorials.ubuntu.com/tutoria...-you-install#0

Thanks a lot for your reply!

I looked over the link you sent me, useful content but even if I choose the option to "Try Ubuntu before installing" I will get the same errors as mentioned above.

For Fedora, I used the "Fedora media writer" application that comes with the OS, which is a tool that creates a bootable USB automatically with the downloaded operating system. For Ubuntu, initially I made the USB bootable through Command Prompt (unsuccessful) after which I used Rufus (successfully this time) and created a bootable USB with Ubuntu.

I tried using, like you suggested "Check disk for defects" option, followed by the same errors as mentioned above.
First i've got this list of error:https://ibb.co/iqLQhz after which the Ubuntu loading screen appeared and least, I've got this error: https://ibb.co/ebQEaK

Again, thanks a lot for your reply and hope this info helps! Let me know if you need to know anything else!

Update!
I've used the same USB on a different laptop and everything works perfectly fine. However, I'm still unable to install Ubuntu on the original laptop.

People sometimes get this error when using usb3 ports rather than usb2. The fact that the drive works on another machine suggests that you might have this problem.

I don't think your acpi errors are significant. They probably just indicate that your bios is using careless syntax

1 members found this post helpful.

Visually scanning through several screen images of text error messages was not easy but at first glance I'm getting the impression there are lots of 'ACPI exceptions' and 'errors' -- and this is being seen during an attempted Ubuntu installation?

I have never before experienced this when installing Bodhi or Mint, and since I was curious, I put the errors into a DDG search (terms: acpi error exception during linux installation) and while I didn't examine the contents, one Subject line that appeared in the results -- looked promising:

[SOLVED] Install Ubuntu,ACPI problem

I leave it to the OP to take a look and determine if this addresses his problem? If not, the other 'hits' in the same DDG search could be helpful.

After your suggestion I've tried all the available USB ports left on the laptop where installation was unsuccessful but unfortunately with no luck.



Thanks a lot for the time put into finding a solution for my problem! Although I've read in a few places already that disabling the ACPI might help in this situation, I came across no way of disabling it from the BIOS. I will continue searching ways of turning ACPI off and if instalation will be succesfull I'll gladly share.

What about giving the manufacturer, name and model number of your laptop? Was this somewhere else in your original post?

Sure! It's a Dell G7 model number 7588.
Had in mind specifying this, I don't know why I didn't.

The only option I've found for disabling the ACPI was from Windows (by disabling Microsoft ACPI-Compliant Control Method Mattery under "Device Manager") but sadly, the outcome did not favor any positive results.

You can easily disable acpi in Linux by booting with the kernel command line option "acpi=off". However that is not a good long-term solution because acpi does so many useful jobs, from managing hot-plugged devices to powering off the computer after shutdown. It's better, if you have a fatal acpi problem, to find out which acpi operation is causing it so that you can switch this off selectively.

Here is a guide to troubleshooting acpi that I suggested for another post.
https://www.linuxquestions.org/quest...-a-4175637608/

If the problem is not fatal (i.e. you can boot but are getting a lot of acpi error messages), I would ignore it. You see, the bios's internal acpi drivers are written in a special acpi programming language and then compiled into binary. There are two compilers in common use, one published by Intel and the other by Microsoft. The Intel compiler follows the international standard but the Microsoft compiler doesn't. Consequently these internal acpi programs are often full of syntax errors which the compiler hasn't picked up. The Linux kernel's acpi drivers follow the international standard so they complain about all these errors, but can usually work around them.

You're evidently training up to become a world expert on ACPI, hazel :-).

2007-2009 seems to have been a bad time to buy a laptop purely because of acpi. Yours gave you hell, as did mine (Now recently and fortunately deceased).

I had to read up on it when Bigboy suddenly stopped booting! At first, since it was always the acpi driver that crashed, I thought it must have something to do with the acpi errors that earlier kernels had consistently reported, so I taught myself a bit of asl in the hope of correcting them. I did finally manage to do that, but it didn't make any difference to the panics at boot because that turned out to be a memory mapping problem and only incidentally to do with acpi.
Littleboy is my laptop. Bigboy is a traditional desktop tower which I bought second-hand. I've had it for several years and it never gave me any trouble until this business blew up.

Oh, Littleboy & Bigboy; You won't get marks for originality of hostnames. I've had some horrors in my time too. But I have a past in Electronic Repair, and rules 1 & 2 of that game are: I fear you offended on rule #2 with Bigboy. I would have bought something rather than what you went through.

But it was a very interesting experience and I learned a lot from it. I'm retired and have plenty of time for exploration. Also I was raised to be very wary of spending money unnecessarily. A decent new computer costs two or three hundred pounds. And I tend to grow fond of computers when I have used them for a long time. Now something works when it didn't work before. I don't think this makes me a hacker, but it's surely part of what makes Linux intriguing -- that you can usually fix things when they go wrong.