Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am trying to install ubuntu 14.04.2 LTE. I have a lunovo ideapad with windows 8. I have followed all necessary steps flawlessly, and even factory reset my laptop to make this smoother. I get this error when trying to boot and install ubuntu. I also get it if i try to run ubuntu without installing. Also I tried re-downloading ubuntu, and remounting on my usb with the universal usb installer.
Is this error due to my computer, or the ubs/unbuntu? There was another option in the boot menu. It was check disk for error. I do not know if it was checking disk as in the iso disk or my hard drive, but a ubuntu lunch screen appeared and it was looking into some ubuntu files (on the usb), when it was done it said there was 2 errors. It did not say what kind or if it repaired it , or how to repair it. It only gave me the option to exit, then lunovo boot screen appeared and it stayed in a attempting to repair loop for quite a awhile so I gave up on that and shut down.
I would ask this in ask ubuntu, but I do not have enough "respect points" to upload an image.
Major respect to anyone who can help me out, I have been to get ubuntu for 2 days now, and I hit a dead end.
This error message can appears in those cases:
1. Your hardware it not compatible, usually ACPI issue. Try to boot with additional options: "noapic" and/or "acpi=off". You should be able to set parameters in "Other options" [F6 key].
2. Your RAM is broken. Check it in "Test memory" option.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 11 months ago.
Improve this question
I'm using parallels an an m1 macbook pro and the virtualization of ubuntu 20.04 worked perfectly fine until today. I can't launch it and it tells me that "Image BSS overlaps adjacent EFI memory region".
Does someone know how to fix it ?
I also can't create a new virtual machine since it prints the same error when I try to launch the new one.
Booting into an older version of the Kernel allowed me to safely access the VM after this happened to me. Although I also was running out of disk and needed to increase the amount of disk space allocated to the virtual machine.
I believe the latest version of the Ubuntu 20.04 kernel may not work on Parallels for now. Specifically linux-image-5.13.0-35-generic gave me trouble and booting into linux-image-5.13.0-30-generic worked fine.
The steps I took were
Attempt to boot into VM. It should hang at Parallels error: "Image BSS overlaps adjacent EFI memory region"
Go to Actions > Stop
Attempt to boot into the VM once again, at this point it should allow you to select Advanced options for Ubuntu. Select this.
In this screen select an older kernel version to boot into. I didn't have to boot into Recovery Mode.
Uninstall the breaking kernel. I just did sudo apt-get purge linux-image-5.13.0-35-generic.
It should be noted that I had older kernel versions available. If you've also deleted older kernel version preemptively, then I'm not sure what can be done.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I made a mistake during the installation of Debian 11. My plan was to run Debian next to Win10 by using Grub2 but installed Debian high secure LVM which overwrote my notebook's complete Harddisk. I am completely new to Linux so as you can imagine I struggle hard because I only have a "DOS-style-Terminal". The Debian 11 .iso ist only 3xx mb large and I wonder if i am able to install Gnome from the given Terminal. Some sources mentioned Gnome could be part of the .iso .Is it true? Do I have a chance to process? If not I concidered to add a folder on the bootable USB stick, add something like "gnome.deb" and try to progress this way. I dont have internet in my Asus Vivobook model M712D because of missing"RTW88......" which makes my situation even worse but can access the internet by my Smartphone. In the end I want to install vscode to progress at www.freecodecamp.org using Debian instead of Kali for advanced Linux learning and future operations. I am sure this is a topic to discuss, I cant imagine I am the only one struggling on this issue. Many Windows user gets prevented from using linux by this issue .
The small size of the image indicates that you probably used the Network Install image. This minimal image does not feature desktop environments. Your options are:
Download an image that features a desktop environment (complete installation image, see here) and reinstall Debian using this image.
Install the desktop environment yourself. To do that, you could try sudo apt-get update && sudo apt-get install task-gnome-desktop. This, however requires an internet connection.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have Fedora 11 installed on VirtualBox. By accident some files in /var directory were damaged or removed(I don't know what exactly). Now when trying to run Fedora, it goes untill choosing the user and freezes. No reaction at mouse and keyboard clicks. Does anyone have any suppositions how to run it, or at least how to retrieve files from virtual machine? I booted it to the terminal where I updated all what is possible - gnome, etc...But still no result.
It's impossible to know what happened without knowing what got removed. However, a great way to get your files out is using scp. Good examples for this can be found here.
Alternatively, if you've installed the Virtualbox Guest Additions you can use a USB drive to retrieve your files. There's a pretty good tutorial on how to get your USB drive working on VBox here.
If you want my best guess as to what's wrong, something in your /var relating to your GUI got removed, as from what I understand you can still boot to your command line. My suggestion would be to get what you need off the machine using the above tools and get a fresh install.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Being Belgian, all laptops come with windowsTM pre-installed. Ingnorantly, I bought on thinking I would be able to install (K)ubuntu. I found out the UEFI is just microsoft's way to prevent you doing this. It stops you booting from USB or CD, it does not allow installing Linux or anything.
I tried the F2/F10 options and settings, I disengaged the security options, disabled secure boot, changed boot order, I tried changing HD with compatible laptop and running OS, tried to bang it against my head, nothing lets me install Linux, it just says:"no bootable device found"
UEFI dual booting Linux and Windows is big tangled mess. I've pulled it off with Ubuntu and Fedora, but after a lot of effort. There are a lot of important variables here. I'm more likely to be able to offer a solution with the following info:
Which media are you using – USB or optical?
How did you create the media? (e.g. Pendrive, Rawwrite, etc.)
Which laptop manufacturer? (This is surprisingly relevant)
Also, it will help us all in the long run if we get more insight into the specific UEFIs and start documenting this issue more thoroughly. UEFIs are embedded software typically written by third-party companies like Insyde. You can find yours by installing a Windows system detailer like Speccy or HWInfo64. See the attached screenshot from Speccy. This info is unlikely to help here and now, but it will help us long-term: I'm looking to create a repository for these UEFI boot issues if someone hasn't done so already.
Try installing Fedora 22. There is a UEFI trampoline to get passed this hurdle. If I had a UEFI machine I'd have tested this answer; it is theoretical at best.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Installed Mint on a brand new Lenovo Z585 Ideapad alongside the pre-installed Windows 8. Everything seemed to go fine, until the reboot, which simply dumped me at a Grub prompt.
I tried the usual ls investigations, but my Mint partition (/dev/sda9) returns an error along the lines of "invalid file name ''." - sorry I can't be more precise right now.
I've booted back into the LiveCD and run boot-repair, which generated the following summary - http://paste2.org/Owy3XNpH.
os-prober recognises my Windows installs (the real install and the recovery thinger), but no Mint.
As far as I can see, browsing the partition through the live cd, the install itself is fine, but I'm more than willing to be corrected. Can anyone help?
Adding the answer in case others have this problem.
Turns out that SecureBoot was in the Security section of the Bios, and not in the Boot section, where I was looking for it.
Disabling it and running boot-repair fixed the problem.
No boot loader is installed in the MBR of /dev/sda
http://wiredrevolution.com/system-administration/install-the-grub-boot-loader-to-the-mbr