The PC is Windows. I wanted the ubuntu environment, I put the ubuntu iso file on the USB. After that, if I try to restart and start ubuntu, I get an error like the following.
Like this error
The details of the error are the two statements below.(initramfs) Unable to find a medium containing a live file system[figure ex.) 135.392108] usb 3-4: device descriptor ewad / all, error -110I tried variously, but it was useless. (I tried BIOS etc. but it was useless.What I want to do is to have Ubuntu portable on the USB. However, I want to prevent any Windows from being broken.I do not know the meaning of 2.0 / 3.0 on the USB drive side and socket side.The one that I use is USB 3.0.Ubuntu version is 18.04.2. The iso. file was loaded with Universal-USB-installer.I tried both UEFI and LEGACY mode with BOOT on the BIOS screen, but it was useless.
Related
Now, the only working operating system is Windows 10. When I go to my Pc in windows, I don't even see my hhd. Is there anyway to save this mess? I tried to unplug my ssd and see if ubuntu shows but nothing.
You probaly go two problems here, the first one is:
the only working operating system is Windows 10.
You probably just replace the default boot drive with the drive where Windows is installed, in this case, you will need to change the boot order, and place the HHD where ubuntu is installed as the first option on the boot order list, (this guide can give you some idea of how to do it. ) after this you will probably see the grub system selector page when your PC starts.
Now to the second problem:
When I go to my Pc in windows, I don't even see my hhd.
The reason that Ubuntu drive doesn't show up is that Windows and Ubuntu use different types of file system technology. Windows uses NFTS and Linux (Ubuntu, Debian, etc) uses EXT4, Windows doesn't support EXT4. To see the Ubuntu drive on Windows, you will need to divide the Ubuntu drive into two partitions, one EXT4 for Ubuntu and another one in NFTS.
I created an small embedded WinUSB device which offers 2 bulk endpoints. This device can communicate with Linux and with Windows10 without installing driver, or a .inf file.
Now we want to use the same API with a embedded Linux. The USB-Gadget mode offers Serial CDC/ACM and RNDIS-Ethernet and many more.
I was able to create a USB-Gadget with the gadgetfs which had only bulk ep. I could communicate with Linux and Windows host. The USB-Device had /dev/ttyGS0 to communicate. But in Windows I had to install WinUSB driver manually.
I work with yocto to create embedded kernel.
I added some line of code here: /linux-imx/drivers/usb/gadget/legacy/serial.c , f_serial.c, u_serial.h to add additional variable os_desc and parameter use_winusb. But the resulting g_serial still creates a COM-Port in Windows10 or a no WinUSB device. For our device we need WinUSB-Device only.
The RNDIS Gadget does has WinUSB support. So I tried to create a own USB-Gadget device with https://github.com/libusbgx/libusbgx. But if I use the USBG_F_SERIAL function type then it can't create WinUSB. See error:
Error setting function OS desc
Error: USBG_ERROR_NOT_FOUND : Not found (file or directory removed)
If I use USBG_F_RNDIS, it works, and with manipulated USB descriptor it'll recognized by Windows as WinUSB device. But Linux implement's it as USB-ETH ethernet device. The USB-Device get's no /dev/ttyGS0 serial connection to communicate.
I'm reading the Linux kernel driver source now, to find the position, where I can simply ann this WinUSB os-descriptor stuff into the USBG_F_SERIAL type. But I think it'll take month to get through.
Any solution would be ok. Patch for the Linux driver sources g_serial or how to configure a USB-Gadgetfs would be great. Any hint, where to put additional code would also be fine.
I wanted to change the kernel, but fortunately found this:
https://blog.soutade.fr/post/2016/07/create-your-own-usb-gadget-with-gadgetfs.html
This code made it easy to add WinUSB features.
Source of modified Version for WinUSB: https://github.com/rundekugel/gadgetfsd/tree/WinUSB
I have DELL inspiron 7560 which has pre installed with windows. I want to dual boot it with Ubuntu. I have created a booatable device. But on startup it is not showing USB drive to install Ubuntu.
What tool/utility did you use to create the bootable USB?
If you did use Rufus to create your USB, after setting up the USB and clicking "START", select "Write in DD Image Mode" instead of "Write in ISO Image Mode".
I have found that writing in ISO Image Mode tends to make bootable Linux USB's to not appear or work properly.
Computers nowadays use UEFI by default, so make sure that your bootable USB is formatted as GPT. Otherwise if you create a bootable USB with MBR instead of GPT, it may not be visible.
Make sure that you are going into either the F12 boot menu in the BIOS, or set the boot order priority in the BIOS, or else you won't be able to boot from the USB drive.
Is it possible to deploy Windows 10 IoT (Rasp Pi image) as a Virtual Machine using VirtualBox or VMWare Player?
I need for a testing lab a network of three to five Windows 10 IoT devices. A virtual cluster would be perfect. My Google- and Bing-based research failed.
The problem could be either the non-ISO disk image file format or the non-x86 architecture of the operating system, couldn't it?
The easiest way I found is downloading Windows 10 IoT Core for MinnowBoard MAX
(here: http://go.microsoft.com/fwlink/?LinkId=691712). This MinnowBoard is x86-based and the image comes in a .iso file. I know the OP was specific about being a Rasp Pi image, but I don't really see the difference if we're just trying to use a hypervisor. Afterwards, you may just follow this tutorial: http://www.newventuresoftware.com/blog/running-windows-10-iot-core-in-a-virtual-machine
It's very simple and straight-forward, and it works with VirtualBox.
Based on #makoshichi's links here's the steps that worked for me:
Download MinnowBoard MAX IoT Core from microsoft, and install
Run ImgMount tool as Admin to mount "C:\Program Files (x86)\Microsoft IoT\FFU\MinnowBoardMax\flash.ffu"
Detach the VHD from Disk Management (in Computer Management), move the resultant .vhd file (that it informs you of on detach) to a location of your choice
Create, but don't launch, a new Virtual Machine in VirtualBox (expert mode) as Windows 32-bit, using an "existing virtual hard disk file" - the one you just moved
Goto device Settings->System and click Enable EFI (special OSes only)
Goto device Settings->Network and select Bridged Adapater
That's it - Run your virtual machine and be a happy Thing of the Internet, or something like that.
This is my short version of this wonderful post by Yavor Ivanov.
The QEMU emulator may do it, it will boot the image file directly. you may need to expand the ffu with dism first.
You don't have to fully install w10 preview: just boot the W10 real or virtual DVD and select to open a cmd box, from there you can run the updated dism command.iot w10 have no (direct) GUI, you must talk to the device via winrm and powershell
There is a good startup for you on
sourceforge
fc
https://github.com/0xabu/qemu/tree/raspi is a working way to run Windows 10 IoT on Qemu. It fully emulates a RPi2, except USB
Hi you could use the Raspberry Pi Simulator https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-raspberry-pi-web-simulator-get-started
Like the question says: can you put some files on a usb, that run when you plug it in to your computer? maybe make a mini OS that you launch from bios? I have to be able to run an exe program from it, so it would need to basicly be able to run windows, just without logging in, kinda like how you can with ubuntu on a usb with wine configured.
Yes, but BIOS needs to support this:
BIOS must be UEFI
BIOS boot manager should try to load from USB before HDD/SSD.
Such applications are called UEFI (shell) applications and can be created via EDK II.
These apllications run at ring 0 on Intel architecture.