New answers tagged

0

When I hold down the shift key, the screen freezes, and when I let up, it goes again to the login screen asking for a password.


0

@Jokerdino: Why did you delete my answer? I have the same problem and there is still no solution as nobody has written any way we could try out! So, ahm, I kindly ask you to let this topic in an active status. Thank you.


0

sudo apt-get install --reinstall linux-image-3.19.0-25-generic In general, you can find out what package owns a file with dpkg -S /path/to/file and reinstall if needed.


0

The main reason this could be happening is because the ISO is not loaded. Other reasons why this may be happening is because the ISO may be corrupted, damaged, or not finished downloading. This is one of the problems with Google Chrome, it will say finished but not really finished and you get a partial ISO. Try downloading with Windows, or with Safari. ...


0

I had the same problem and all I had to do was to try with different isos from windows because the older versions are known to fail. Finally i download the last version from Microsoft website and the machine worked fine.


0

I guess you have installed ubuntu in the Wrong partition(which is C: drive). To confirm: Boot your ubuntu os and search for directory which have folders below.(perflog, Program files, Users, Windows) If no, you need to install windows Operating system again. if yes, start your ubuntu os and follow this ...


0

F2 key method Turn the computer on. If you see an invitation to press the F2 key to enter Setup, do so. The Setup (BIOS) screen will appear. If this method does not work, repeat it, but hold F2. F12 key method Turn the computer on. If you see an invitation to press the F12 key, do so. Boot options will appear along with the ability to enter Setup. Using ...


0

or EFI LUKS 2.1. EXT4 / 2.2. SWAP if necessary 2.3. EXT4 /home if necessary etc.


0

Do you have the recovery disk(USB) for Windows 10? I will suggest do a fresh install of both the O/S. First recover the system and install(recover) Windows 10. Then create partitions for Ubuntu from Windows only(using disk management tool). Make sure secure boot is completed disabled in BIOS. If windows 10 is installed in EFI mode, make sure that Ubutnu is ...


0

To access files on Windows, you can mount your Windows partition with read-only privilege. eg. sudo mkdir /media/windows sudo mount -t ntfs-3g -o ro /dev/sda3 /media/windows This works for me on my Windows 10 & Ubuntu 15.10 dual booting system. To enter into Windows 10, you should check your boot sequences in bios settings by selecting Windows UEFI ...


2

Repair GRUB boot loader with a built-in tool. Boot from the Ubuntu installation media. Select Try Ubuntu without installing. On Live desktop open a terminal. Execute these commands : sudo mount /dev/sd** /mnt sudo grub-install --boot-directory=/mnt/boot /dev/sd* Note : sd* = disk | sd** = system partition Use GParted to identify the partition ...


0

Right click your ubuntu-*.iso > Open with Disk Image writer Choose your usb drive and click Start Restoring... and follow the instruction.


0

The problem, as it says, that there's no device drivers found. The GNU/Linux (e.g. Ubuntu) installation disc works fine because by default there's a bunch of drivers. This is one of differences between how GNU/Linux distros and Windows are shipped. For more obvious example, imagine you just installed Windows and Ubuntu. If you would look for you GPU device ...


0

do sudo fdisk -l edit your question to include the output :)


0

I have changed my hard disk, because of this annoying task. I am using SSD now and everything works out. Maybe this is not a solution to my problem, but I would say that this is a workaround. Also I have already posted in the comments above I have changed I have change inside BIOS from legacy to UEFI.


0

Thanks all :) I solved this problem by using an original DVD of Ubuntu 14.04 lts. and now i have some doubt about Nvidia Quadro K2100M if it's working or not?


-1

Have you tried this, and enter bios and set to legacy boot, and then from boot enter command line, and enter this: test hd1 badram hd1 dump hd1 and then use set secondary=hd1 and it might work fine this way.


-1

I have had Manjaro linux 15.12 XFCE (kernel 4.1) running on my gt72s for 2 months now nearly perfectly. I get freezing if I try to boot with linux kernel 4.3 or 4.4 (killer wifi network driver support added from 4.3~) But I don't need wifi currently so I can wait it out. I suggest you try Manjaro, super fast and beautiful distro and this machine is a beast ...


1

Not sure what computer brand you are using, but instead of hitting F12 for boot options try using F2 (or what ever option gets you into CMOS) and right arrow over to the "boot" tab. Here you can choose which drive to boot from (the Linux drive or the Windows Drive). Select the drive you want to boot from, hit F10 to save changes and reboot. Also try ...


0

The way you have done your booting was absolutely wrong. Try installing grub on your hard-drive. Use a live ubuntu usb to solve the problems of booting. If you want to have a fresh start so that u don't have to face any problems in future. i.e., safest way to install operating systems. here was a good video explaining how to boot in safest way. click ...


2

You've got the lot: Logical volumes, overlapping partitions, unknown file systems, ... So: the best thing you can do right now is to stop using your hard disk! Then boot from an Ubuntu 15.10 Live DVD and: (increasing numbers means increasing difficulty and less of your data will be recovered) Restore your latest full system back-up. If you don't have a ...


1

I had the same issue, and I deleted all known files, and directories, but still kept getting the pop up messages. I finally ran across this link : https://forums.virtualbox.org/viewtopic.php?t=7839 The info that worked were the first 2 lines of these Sudo Commands, the rest were all ready done manually by me. sudo find /etc -name "vboxadd" -exec rm {} \; ...


0

This error occurs because the BIOS incorrectly reports the ExtIntA I/O APIC input is cascaded from the 8259A (Programmable Interrupt Timer) as the timer interrupt input. There is a kernel workaround, I believe booting with the kernel parameter "noapic" may help. So, when the LiveCD image first boots, hit F6 and a pop-up menu will appear; select the ...


1

I found out eventually. Edit /boot/grub/grub.cfg Find ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'Windows 10 (loader) (on /dev/sdXX)' After chainloader +1 Write ntldr /bootmgr It did the trick and fixes the shit. Thanks all for your hints.


-1

I had come against this problem before. I usually use Rufus for USB images and when I create a bootable disk using ISO images for Ubuntu Server, it breaks at mounting CD/ROM device stage but when I change it to DD Image it works.Hope it helps. Rufus DD Image Option


1

Ubuntu Desktop edition requires (I cite the 2 main elements): 700 MHz processor 512 MiB RAM Toshiba Satellite C650 fulfills these requirements largely. So yes, you can install Ubuntu on it. And since you run Windows 8.1, surely you can run Ubuntu too on it. For your second question, the simple answer is no, your pre-installed system won't be erased: ...


0

I solved the problem by reinstalling windows 10 MBR on the the first hard drive using a usb drive. The I installed grub on the second hard drive (where Ubuntu is) and I put it as first in the boot order. Grub is now able to recognize the window partition and everything works fine.


0

Never mind. Seems as if it was the Universal-USB-Installer's fault. Tried Unetbootin and it works now.


0

The error disappeared. I think was due Ubuntu software update. tomas@tomasCompaq:~$ cat /proc/version Linux version 3.13.0-76-generic (buildd@lgw01-21) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #120-Ubuntu SMP Mon Jan 18 15:59:10 UTC 2016 tomas@tomasCompaq:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty ...


0

If efibootmgr is creating an entry like you describe (VenHw(99E275E7-75AO-4B37)), then that sounds like a bug in either efibootmgr or the firmware. That said, consider the efibootmgr command you specified: efibootmgr -c -d /dev/nvme0n1 -p 1 -l /EFI/refind/refind_x64.efi -L "rEFInd" There are two things that are unusual about this: Disk device -- Most ...


0

I strongly suspect, but do not know for certain, that you've installed Ubuntu in BIOS/CSM/legacy mode, and that you've got an EFI/UEFI-mode Windows installation. Such dual-mode installations always complicate matters, and should be avoided. Unfortunately, avoiding them takes some general EFI know-how that is, as yet, not as common as it needs to be. Another ...


5

Boot into Windows, open command prompt as administrator and execute: powercfg /h off Open Windows Control Panel -> Power Settings and uncheck Fast startup. In case it is not visible, enable show hidden settings. Shutdown the machine completely - do NOT reboot. Now you should be able to boot from Ubuntu DVD.


-1

you should reinstall your desktop. prees ctrl+alt+f1 or some Fi (i<7) login with your user and pass. if you use uinty write here : sudo apt-get install --reinstall ubuntu-desktop if use Gnome : sudo apt-get install --reinstall ubuntu-gnome-desktop


0

had same problem, finaly after 2 hours of bruteforcing removing various user files restarting ..., came to solution went to older kernel that helped to boot plasma then opened drivers section and disabled nvidia driver (using X.Org X.server) restarted to newest kernel and things now ok. hardware: GeForce GT 540M


-1

You need to edit the refind.conf file and change the path back to PciRoot. Write down the entire description of the device, so you can enter it in the conf file. Just make sure to pick the correct PciRoot ;)


0

I have something similar. I never see grub. However, if I get the BIOS boot menu, I can choose either Windows or Linux. You may also need to disable safeboot in the BIOS. When your machine first comes on it should tell you which key to press to get BIOS settings. F10, F12, del or something.


-1

There is a section of your HHD that is the boot area. The information in there will dictate the boot steps. If you installed Ubuntu along with Windows then you need to install GRUB from ubuntu to the boot manager. That will handle our chioce of win or ubuntu. You will need to boot the live disk and either fully reinstall or install grub from there. Open a ...


0

for sure that is not a problem of available space. Seems that for some reason your installation image is not correct. The message on the bottom says, that installer cannot find /dev/sdc device containing installation image. You mentioned about 2 SDDs in RAID mode. My guess is following: hardware RAID under windows is recognized as single drive (which is ...


0

I've had problems with initially installing Ubuntu on my Toshiba, but it is possible. Try disabling the secure boot option in your BIOS, and if that doesn't work try switching to CSM boot mode, that should work.


0

After reading the comments it seems to me that there is a disconnect in understanding. Follow the steps below which should result in a clean install. Create your bootable USB using Rufus Reboot the pc, and boot the USB drive Ensure that you have a wired internet connection Uncheck third party apps and software (as this slows down the install greatly) Allow ...


0

Unfortunately there is not a way to do this, that I have found. I have installed many, many versions of Ubuntu on various computers. You will need a CD, or USB to do this. You cannot start an install of an OS while working in an OS due to the r/w process. You will have to boot from an external device like CD or USB. If you get your hands on a USB stick I ...


0

As an alternative to waiting, add the boot parameter nomodeset to grub during boot. This can be done by pressing e on the grub menu entry and then inserting nomodeset on the Linux line. This seems to be a problem caused by the most recent kernel and Nouveau, not Ubuntu.


2

Seems like the package python-gtk2 was missing. I installed it: sudo apt-get install python-gtk2 That explains the difference in Python's sys.path (/usr/lib/python2.7/dist-packages/gtk-2.0 was missing). But on the other machine where the entry was present, according to aptitude why, the package was only installed as dependency of ...


0

Finally I was lucky. After some trials and boot-repairs (e.g like the description in Recovering GRUB after installing Windows 7?) I found out that the problem was caused by the version of the kernel. On grub menu I selected advanced options where there was the choice between the 3.19.0-25-generic version which did not work (and was the same as the default ...


0

This solution worked for me https://help.ubuntu.com/community/Boot-Repair 1) Launch ubuntu on the live USB 2) follow the procedure to install Boot-Repair 3) Restart and your system will boot 4) From terminal update, upgrade and dist-upgrade and reboot 5) repeat 4) id you find some issue


0

The problem in your case is that the in the pic shown above your 289.09GB HDD is of MBR (Master Boot record)partition style which only supports upto 4 primary partitions (i.e blue partitions) . If you want more than 4 partitions then you have to create an extended partition such that the total HDD has 3 primary and 1 extended partition. Then from that ...


0

Using the standard installation process https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/ with the Ubuntu compiled image for the Nexus 4 is not an option for you?


1

I had this issue, and my efi partition was full. I think this caused the issue because installation always stopped at that drive, and displayed the initramfs prompt as stated in this issue. I tried many of the fixes on this page and many other pages. It took days to figure out which fix would work. I finally created a USB boot drive on my WIN 10 machine ...


-1

in case YUMI doesn't work - try universal usb installer it worked for me always from Windows. Please double check your .iso file whether it has been downloaded properly or not?


0

A couple different problems and solutions here. Problems with Windows holding on to the cache and nvme drive were solved by disabling fast startup on Windows per recommendation 3 here. Fixed booting problem caused by Nouveau and nvidia by pressing e during the grub menu and adding nomodeset to the end of the Linux line. System boots properly now and as ...



Top 50 recent answers are included