I recently bought a Dell Inspiron 15R SE with Windows 8 (64 bit) pre-installed (UEFI supported). I want to install Ubuntu in dual boot with Windows 8. I tried to follow all these instruction and these instructions too. So, I set Secure Boot to "off" into BIOS and I disable Fast Startup as described here. I created a bootable USB key for Ubuntu (Ubuntu 13.10 64bits international Edition) with Unetbootin. The problem is I am unable to boot from the USB key. The computer tries to boot into infinite loop (when the USB key is plugged in, the computer starts and the Dell logo appears. The little blue progress bar is growing normally. When it is complete, the computer restarts and does the same thing). I also tried to boot from USB with "Legacy Boot" option instead of UEFI. In this case, the computer freezes at Dell logo. Of course, I tried to boot from my USB key on an other computer having normal BIOS and it works perfectly. Have you ideas about what I need to do to be able to boot from USB?

What I have tried: With UEFI Boot mode: "Intel speed step": Disabled Windows 8 FastStartup: Disabled Using bootable USB key for Ubuntu (Ubuntu 13.10 64bits international Edition) with either Unetbootin or Linux dd utility. Result : Unable to boot from the USB key. The computer tries to boot into infinite loop. With "Legacy Boot" option: Result: Unable to boot from the USB key. The computer freezes at Dell logo. If I press F12, the computer freezes instantaneously. boot dual-boot system-installation uefi I had the same problem with my new Samsung Ativ 9. The following changes to BIOS helped: (For Samsung F2 entered BIOS) Advanced: Fast boot mode to disabled Boot: Secure Boot to Disabled Boot: OS Mode Select left at UEFI OS (To allow Windows alongside) Boot: Boot device priority -> set USB HDD at top I also had to turn off fast boot option under control panel under Windows 8 On my ThinkPad Ubuntu 14.04 went into the infinite loop, Ubuntu 15.04 did not.

proper shutdown in Windows After installing Ubuntu, only boot to Windows was possible: boot Ubuntu from live and install + run boot-repair. This way grub is the first thing that comes up. Windows boot loader can be skipped with EasyBCD and in Linux grub-customizer to clean up the grub menu. See my page on installing Linux on EFI systems. In particular, you may be having problems because you used unetbootin -- the Ubuntu installer should work fine if copied to a USB flash drive via the Linux dd command or equivalent tools in Windows. Boston Terrier For Sale WashingtonMore complex programs, like unetbootin, were designed with BIOS-mode booting in mind. Essex House Condominiums Salem MaFurthermore, EFIs vary greatly, making it impossible for developers of such tools to test on a wide enough variety of systems. Cats For Sale Georgetown Tx

Such tools can therefore sometimes create USB flash drives that are unbootable in EFI mode. I do not recommend installing in BIOS/CSM/legacy mode except as a last resort. Doing so will require you to install an EFI-mode boot loader after the fact, which is extra work that can itself cause confusion and complications. (I can't count the number of questions I've seen from people who need help with this.) That said, on rare occasion it is necessary to install in BIOS/CSM/legacy mode and deal with the EFI boot loader installation issues, or even re-install Windows in BIOS/CSM/legacy mode to work around particularly buggy EFIs. I had similar problem with Dell XPS 13 but with Ubuntu 12.04 64 bit. While trying to boot from USB it was going in an infinite loop as you mentioned. I had Legacy boot option as default. I then changed to UEFI mode which had only Network option in it. I then added a boot option and selected the USB file system location. Saved the BIOS and rebooted it worked fine!

On my version of UEFI on an ASUS VIVOPC The boot order cannot be changed from UEFI, and there fore I could not force a boot from my USB drive. However, after disabling secure boot, and enabling CSM legacy I pressed F8 upon start up and was able to select my USB drive and boot. In Windows 8, open the settings charms by pressing Windows+I keys. At the bottom, you’ll see the option of Change PC settings. Then you need to go to General PC settings and select Advanced startup and then click on Restart now. It actually won’t restart right after it, but it will provide some option that you will see on next boot. You should to choose Use a device. In Use a device menu select EFI USB Device and your computer will start to boot from the flash-drive.Browse other questions tagged boot dual-boot system-installation uefi or ask your own question.If your question isn't answered here, please post on the forum. PJRC does monitor the forum and every attempt is made to answer customer questions.

You must post code or details needed to reproduce the problem. Just a few minutes to compose a detailed question usually results in much better help. The Teensy Quick Reference: Code Examples, Tips and Tricks list has a list useful resources and solutions for many common projects. Many cell phones are sold withThey have only 2 wires for power, but are missing the 2 data wires. Try another USB cable, ideally one known to work for USB. #2: No COM Port or Serial Device Seen: Teensy uses HID protocol for uploading,Brand new Teensy boards are shipped with the LED blink example compiled to appear as RawHID. You must program Teensy at least once from Arduino. port (Windows) or Serial Device (Mac, Linux) appears only after Teensy beginsRegular Arduino boards are always serial. and supports many protocols. To use serial, make sure the Tools > USB Type menu is set to "Serial", and understand Teensy only becomes a serial device when it runs your program built with this setting.

#3: Dead (usually overheating) Main Chip: More than 4 volts applied to the 3.3V power pin instantly kills a Teensy LC or 3.2. Be extremely careful if connecting circuits to Teensy using both VIN(5V) & 3.3V pins, or when using any external powerLoose wires between Teensy and other electonics accidentally touching are the most common way Teensy fails. Just a few extra minutes to cover exposed leads and mechanically secure loose wires, especially if they can easily unplug from a solderless breadboard, can save you from an unpleasant and costly "learning experience". Some USB hubs have trouble handling the rapid sequence of connect/disconnect events when programming Teensy. fine, but the few that do not can cause very strange problems. If you experience trouble, always try connecting Teensy directly with a quality Teensy Loader 1.07 is the first version to support Teensy 3.0. You can check the version using Help > About. Version 1.07 is part of the

automatically runs when you click Upload or Verify in Arduino. When a brand new Teensy has never been recognized by Teensy Loader, A previously working board may seem to be dead, but the problem may simply be code on your Teensy which confuses your PC's USB port. Of course, verify that your USB port and cable are working properly, perhaps with a different USB device. On Windows systems, "strange" problems are occasionally reported, where Windows will not detect new devices. It does not seem to be unique toCreating a new user account sometimes solves the problem. the cable into different USB ports can also help. Rebooting is always a goodThe best approach is to try on a Mac or Linux machine, or a differentTeensy is NOT natively a serial device. Arduino boards appear as a serial device for all programmingArduino remains connected as a serial device whileTeensy is a native USB device. Arduino does not apply to Teensy! During programming, Teensy appears as a HID device.

When Teensy reboots, electrically your computer sees Teensy disconnect, as if the cable were physically unplugged. When Teensy begins running your program, the USB is disconnected. The fast and slow LED blink examples do not enable the USB port. When programs do use USB, type of device Teensy becomes depends on the codeYour computer will see a new USB device connect when your program begin using the USB port. In Arduino, the device type is controlled by the Tools > USB Type menu. In C language, the USB code you use determine the type of device. program only responds to specific C programs. While troubleshooting, you must look for the type of device which your program implements. TODO: list of C code and Teensyduino device types, VID/PID numbers for each. The pushbutton lets you to manually put Teensy into programming mode. With Arduino, this happens automatically when you click Upload. But if your code disables the USB port, or disables interrupts,

or enters a deep sleep mode which stop the CPU, Teensy can not respond to the Every Teensy is made with a physical pushbutton to allow recovery from a The pushbutton does NOT reset Teensy to restart your application. Teensy is connected to your computer, and Teensy Loader is running and configured for automatic mode (the default when used with Arduino), pressing the button will enter programming mode. Teensy Loader will quickly reprogram and restart your Teensy. your application is due to Teensy Loader's "auto" mode, not only the pushbutton. You have a counterfeit board. PJRC has never made any Teensy with a greenIf you purchased using Ebay and Paypal, we recommend you immediately begin a dispute on Paypal's website. Do not bother contacting the seller. have already scammed many other people with defective boards, but they simply doA dispute on Paypal is the only way you will recover your money. sooner you file the dispute, the better your odds of receiving a refund.

recommend waiting to leave negative feedback until after Paypal returns your money. On Teensy 2.0, the compiler places string constants in RAM. If you have have many, RAM can run out quickly. In Arduino, you can use F() to cause strings used with print() to avoid using RAM. In C language, usually PSTR() is used, and special functions which access flash memory must be called. Often they have a "_P" suffix. Large data tables or arrays can also cause trouble. If data is constant, PROGMEM and pgm_read_byte() can be used. Teensy LC, 3.0, 3.1 do not have this problem. Variables defined with "const" are placed only in flash memory, but can be accessed normally. 8 bit AVR-based boards require these special steps to prevent strings and read-only variables from consuming limited RAM. On Windows, even if the has run correctly, sometimes Windows will retain old information in its registry and fail to load the driver. The Device Manager will show "USB Serial" with an error,

instead of "USB Serial (Communication Class, Abstract Control Model)" with a COM These actions usually can cause Windows to re-detect the device and begin using When "USB Serial" changes to "USB Serial (Communication Class, Abstract Control Model)" and a COM port number is shown, you can access your program on Teensy using that COM port. If there is no "USB Serial" at all, please rememober Teensy only becomes a Serial device when programmed to do so. See "No Serial Port While Programming" above. Windows "Code 43" is a mystery. Other devices, even Apple iPod, haveThe solution seem to be be This code 43 error is a mystery. It might be related to laptops enteringIf you have any insight, please contact us! Pieter Rautenbach found a case where programming the wrong HEX file (compiled for a different chip) causes error 43. On Windows, if multiple monitors are used and then only a single monitor is later used (eg, a laptop used at a docking station), the Teensy Loader

may attempt to appear on the missing monitor. The Teensy Loader appears in the Windows Task Bar, but not on the screen. Additional info from Gilbert Hersschens: The AVR toolchains provided by Gentoo and Arch are broken. compile .hex files which simply do not work! Starting with version 1.0.1, Arduino downloading from www.arduino.cc has a known-good toolchain. If running avr-gcc with a makefile, download Arduino 1.0.1 and set your $PATH to access the toolchain in On some Linux systems, USB Serial is detected very slowly. detects the device quickly (usually seen with "tail -f /var/log/messages"), but the device files do not appear for a very long time. On Ubuntu 9.10 (and maybe other systems), when using a serial device type, the kernel assigns a new number each time, /dev/ttyACM0, /dev/ttyACM1, /dev/ttyACM2, etc. This is caused by the Gnome Modem Manager, which holds the port in (as far as the kerel is concerned) use even after you have reset the Teensy and the port no longer exists.