Newbe Dev Stack

Answer : After more digging found one answer here that is working. http://www.tomsguide.com/answers/id-1973164/change-asus-boot-order.html I just completed a CHAT session with ASUS. It worked!! Here is what they told me: Enter the BIOS setup menu by pressing and holding F2 key when powering on. Switch to “Boot” and set “Launch CSM” to Enabled. Switch to “Security” and set “Secure Boot Control” to Disabled. Press F10 to save and exit. Press and hold ESC key to launch boot menu when the Unit restarts. We now get the following (happy!) screen: And we can get to the Ubuntu Boot Disk: (* 20 mins pass *) And now I am logged in and editing this question from the (successfully) installed ubuntu 15.10 woot! Just solved this problem by DISABLEing the FAST BOOT option in te BOOT tab. And then all the disks are selectable further on that TAB

Answer : The emulator is just slow, there is not much you can do about it. See https://stackoverflow.com/questions/1554099/slow-android-emulator To maximize the accuracy between emulator and real devices, Google emulator uses ARM opcode, a kind of machine language. It must convert from ARM opcode to Intel opcode. That's why it's slow. My computer is 3GB RAM but it's still slow and lagged. The problem seems not to be RAM but CPU. Improving CPU will improve the emulator. To use emulator more effectively, this is my experience: Don't close emulator everytime you run your application. Scale the emulator screen smaller. Disable snapshot (Yes, it's useful but it takes time to close the emulator). Specify a file path for SD card image file. I use only one SD card for many AVDs. If you got any problems in adb, just reset adb, don't close emulator. Open few programs in your operating sytem. If you are using Windows, don't ever close emulator. Do it c...

Answer : yes, We just released a sample Linux VHD that you can boot any computer. You can find more info here: Download and boot your physical PC, also runs as vm - http://www.vmlite.com/index.php/forums/17-vboot/1864-linux-vhd-boot-available-download-and-boot-your-physical-pc-also-runs-as-vm 1 Linux as Real Appliance With VBoot for Linux, you can pre-install and pre-configure Linux OS and its applications, then distribute the resulting virtual disk file in VHD format. The vhd can boot a real computer, with configuration and apps instantly available. This way, operating systems are truly manageable, as simple as files. We call such a Linux VHD to be a real appliance, in the sense that it boots physical computers. It's very easy to setup and boot a computer with a vhd file. You download the vhd file, drop it to Windows or Linux file system, then configure the boot loader, and reboot the computer. 2 Linux as Virtual Appliance The exact same vhd file also runs as a vi...

Answer : You could resolve the error by repeating the steps : Run the installer. Open a shell ( ALT + F2 ). Create the directory cdrom directly on the root of the file system: mkdir /cdrom Note : If you got problems making the directory /cdrom, disable the CD-rom player in BIOS or disconnect the cable Mount the USB as if it is a CD-ROM: mount -t vfat /dev/sdb1 /cdrom Where sdb1 is your USB device. You could carry on installation now After executing mount -t vfat /dev/sdb1 /cdrom , cd into the /cdrom directory and do an ls to see if the files are there. Then press ALT - F1 to go back, continue and re-select "detect CDROM" Source :ubuntu and debian Another layman solution was : when the Window shows CDROM couldn't be mounted , Unplug your USB from system and re insert it wait for mount/ detection (usb LED glow) Hit Continue You could do what I did. Hit escape, type install, hit enter, skip CD drive. If you ...

Answer : You could disable the display manager service with systemctl . For example if your display manager is lightdm then run: sudo systemctl disable lightdm.service This will prevent the service from starting at boot. Edit : I forgot to mention how to start the GUI. It is as simple as starting the systemd service: sudo systemctl start lightdm.service Instead of text use runlevel 3 : GRUB_CMDLINE_LINUX="3" # To remove all the fancy graphics you need to get rid of `splash`. GRUB_CMDLINE_LINUX_DEFAULT=”quiet” # Uncomment to disable graphical terminal (grub-pc only) GRUB_TERMINAL=console Then update-grub and reboot. But you really only need GRUB_CMDLINE_LINUX="3" . For quick test hit ESC during booting to get into the grub boot menu. Then press e and find the line which specifies kernel and add 3 at the end: linux /vmlinuz root=/dev/mapper/ubuntu ro 3 Boot it with CTRL + x Ideally I also want to be able to start GUI by typ...

Answer : When you run Netbootin, it will ask for the distribution that you want to put on the USB, or the ISO itself. In the distribution list, select Ubuntu (either 32 or 64 bit, no, it does not have to be ubuntu, but its just my preference), and download it. Make sure the right drive is selected (the USB that you want to write the data to after the data has been written, shut down your computer, insert the USB, and when you restart, I believe you hit F12 to get to the boot order. Select the USB Follow the ubuntu setup, its pretty straightforward, dont parition anything, just run it as a Live CD (it might be called a live USB, not sure) When you are done with the 'install' See if you can see any of the files on the hard drive, or if Gparted can see the hard drive. If the answer is yes, your HD is probably fine. If not, its probably busted. Please comment back here if there are any issues. The unit has a recovery partition, pretty much all laptops sold now have a r...

Answer : This turned out to be a very interesting question. There are lots of links out there on this topic but they are ambiguous in describing the difference/relationship between the two. Best description I've found of the hard drive configuration for a Windows OS is this one: http://www.ntfs.com/hard-disk-basics.htm. It appears that MBR and Partition Table are in the same sector on a drive. The MBR is "smaller" in that it is the very first thing on the drive, that then uses the partition table to continue the boot process to a specific OS. The two command options effectively fix different links in the boot chain: /fixmbr replaces the information and small executable that reads the partition table to find where the OS may be located. So this exists on any drive that has been formatted and effectively exists to read the next little bit on the hard drive that tells where the/an OS is supposed to be located. In essence, this is not necessarily a Windows-speci...

Answer : This is a common problem in all Lenovo laptops. I also have faced this problem so many times. For solving this please go to the link(link of official Lenovo's support site) and download latest bios setup and install it. It will update your bios and all will be all right. Download bios set for window 8.1 and install it. The manual also is given in PDF format. http://support.lenovo.com/in/hi/products/laptops-and-netbooks/lenovo-g-series-laptops/lenovo-g580-notebook Update: After this again the same problem happens with me but this time I already have latest BIOS version installed in my system and the Lenovo don't allow the installation of same or lower version of the BIOS in existing latest BIOS. So I stuck there and can not do anything. I also approached to the Lenovo service center but they are also helpless they suggest me to change the motherboard which cost me around 10000 INR.

Answer : Disable the hibernation mode and Fast Boot in Windows. Open command prompt as administrator and execute : powercfg /h off Open the legacy version of the Windows Control Panel (not the modern version). Select Energy Settings , enable show hidden settings and uncheck Fast Boot. After having done this - shutdown the computer completely - do NOT reboot. Boot into the BIOS and select Ubuntu as the default operating system to boot. Update : In case there is no Ubuntu entry to be found in the BIOS / UEFI settings, re-install the GRUB boot loader to your Ubuntu installation in EFI mode. Boot from the Ubuntu installation media - open a terminal and execute: sudo mount /dev/sdXXX /mnt sudo mount /dev/sdXX /mnt/boot/efi for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done sudo chroot /mnt grub-install /dev/sdX update-grub Note: sdX = disk | sdXX = efi partition | sdXXX = system partition To identify the partition numbers use G...