Giter Club home page Giter Club logo

wubiuefi's Introduction

WubiUEFI

Introduction

Wubi is the Windows Ubuntu Installer. Wubi installs Ubuntu inside a file within a windows partition, and thus it does not require CD burning or dedicated partitions, yet the installation is a dual boot setup identical to a normal installation.

For more information see: https://github.com/hakuna-m/wubiuefi/wiki

Compiling

Make Command Description
make Builds wubi.exe, note that the first time you run it, you will have to install python inside of Wine, this is performed automatically, just confirm all the default choices in the installation screens that will appear.
make runpy Runs wubi under wine directly from source
make runbin Builds wubi and runs the packaged binary under wine
make wubizip Creates a special zip file conatining python.exe and non byte compiled python files that is convenient for debugging purposes. Inside of Windows, unzip the archive, then run python.exe main.py --verbose
make pot Generates a gettext template (/po/wubi.pot)
make check_wine Creates the Wine environment if it doesn't exist.
make check_winboot Creates the environment for building and signing boot loaders if it doesn't exist.
make winboot Creates the boot loader files (old version)
make winboot2 Creates the boot loader files (new version)
make clean Removes built files
make distclean Removes built files and environment

Code overview

  • /src/winui : Thin ctypes wrapper around win32 native graphical user interface
  • /src/pylauncher : Makes python code into an executable, the Python script is examined and all the dependencies are added to an LZMA archive, then an executable header is concatenated to the archive that decompresses it and runs the script using the Python DLL
  • /src/wubi : The main Wubi application, the code is split between backend and frontend, where each runs in its own thread. The two interact via a tasklist object, where the frontend usually runs a tasklist which is a set of backend tasks. Backends and Frontends are platform specific. For now only the Windows platform is supported.
  • /data : Settings for Wubi branding and customization
  • /po : Translations
  • /bin : Other binary files required at runtime (will be compiled at a later stage)

Wubi tasks

Wubi performs the following tasks:

  • Fetches information about the running system which will be used during installation
  • Checks that the minimum installation requirements are met
  • Retrieves required user information via a GUI
  • Looks for available local CDs and ISO files
  • Downloads the ISO if one is required, using Bittorrent and an HTTP download manager
  • Checks the ISO/CD MD5 sums and the MD5 signature
  • Extracts the kernel and initrd from the ISO
  • Adds a new boot entry to the existing windows bootloader
  • Prepares a preseed file to be used during the Linux-side installation
  • Allocates space for the virtual disk files

The actual installation is performed within Linux after rebooting the machine.

Customization

  • Edit the files in data as appropriate and build your image
  • You will need to provide an ISO that is similar to the Ubuntu ISO and in particular it must have .disk/info formatted like .disk/info in the Ubuntu ISO
  • You must provide a webserver with metalink file, metalink file MD5 checksums and signatures for the MD5 sums
  • Add your signing key to data/trustedkeys.gpg
  • Replace the generated dummy keys in .key with your signing keys for Secure Boot
  • On the Linux side, the distribution must be capable of booting and rebooting off a loop file, perform an automatic installation and accept the special boot parameters that indicate the local preseed file and ISO image to boot from.

License

GPL v2. See LICENSE

wubiuefi's People

Contributors

agoru avatar cjwatson avatar hakuna-m avatar notautomne avatar smartboyhw avatar stgraber avatar superm1 avatar xnox avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

wubiuefi's Issues

wubi1604r309

Kubuntu is not working. it only shows the glowing Kubuntu icon then computer restarts again.

Lubuntu 16.10 fails because of missing packages on desktop ISOs

Lubuntu 16.10 desktop ISOs do not contain /pool with additional deb packages. If you compare
lubuntu-16.10-desktop-amd64.list and ubuntu-16.10-desktop-amd64.list e.g.

/pool/main/g/grub2/grub-efi-amd64_2.02~beta2-36ubuntu11_amd64.deb and
/pool/main/l/lupin/lupin-support_0.57_amd64.deb do not exist.

So installation without internet connection fails on EFI systems because of missing EFI GRUB packages. This is a general Lubuntu issue.

But if you try it with internet connection, it seems to work but unfortunately, lupin-support package with GRUB configuration for Wubi is also not installed.

So booting into new installation doesn't work and additionally GRUB boot loader is installed on the wrong place.

As workaround we will add package lupin-support to Wubiuefi file with the soon coming next release 1610r316.

Please add grub.cfg "i915.modeset=0" to boot Cherry-Trail devices

Hi.

Thank you for your "Wubi for Ubuntu".
There is no bug.

I have many ATOM Tablet device.
But Cherry-Trail Tablet (about UEFI 32bit devices) is blackscreen and no boot GUI when boot on Ubuntu and any Linux distributions.
I think "Cherry-Trail devices” is needed "i915.modeset=0" in front of "quiet" in grub.cfg.
And I am playing Wubi for Ubuntu 16.10 on GPD-WIN now.
Please add "i915.modeset=0" in grub.cfg.

Thank you!

references
http://linuxiumcomau.blogspot.com/2016/10/running-ubuntu-on-intel-bay-trail-and.html

Mytweet
https://twitter.com/kapper1224/status/800267910333665281

Budgie

As Ubuntu Budgie is official we should also suppport the predecessor Budgie-Remix.

Currently, Budgie-Remix 16.10 fails with:

DEBUG  Distro:   parsing info from str=budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)

ERROR  Distro: 'NoneType' object has no attribute 'group'
DEBUG  Distro: could not get info None  

The reason is a missing subversion between "Budgie-remix" - and amd64. e.g. Ubuntu has Release as subversion:

DEBUG  Distro:   parsing info from str=Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
DEBUG  Distro:   parsed info={'name': 'Ubuntu', 'subversion': 'Release', 'version': '16.10', 'build': '20161012.2', 'codename': 'Yakkety Yak', 'arch': 'amd64'}

can't install ubuntu-32bit using wubiuefi

I have a laptop with emmc storage and micro sd card inserted. I tried to install ubuntu 32bit, iso file using wubiuefi tool but it failed to boot again just showing the grub shell right after rebooting. I don't know well about grub shell commands so I stopped here and I reboot my laptop with power key pressed. wubiuefi's version was the latest release version, 16.10.xx. Why only grub shell appeared on the screen without showing window boot manager? I already know the wubiuefi tool is unoffical.

Doesn't work with windows 10

Hello, I've successfully downloaded wubiuefi which downloaded the image and then i restarted my machine which succesfully entered in ubuntu to finish the installation... BUT afterwards there is no option to enter to Ubuntu... I'm using windows 10, I dunno what to do...

make for 17.04 fails because of new shim files

make for 1704r320 works with 16.10 but fails with 17.04

The reason is that the shim files for 17.04 have been changed:

  • /usr/lib/shim/shim.efi.signed -> /usr/lib/shim/shimx64.efi.signed
  • /usr/lib/shim/MokManager.efi.signed -> /usr/lib/shim/mmx64.efi.signed
  • /usr/lib/shim/fallback.efi.signed -> /usr/lib/shim/fbx64.efi.signed

To do:

  • make should also work for 17.04
  • wubi.exe for 17.04 should contain the new files

No root partition defined: Ubuntu 15.10 on Lenovo Yoga 2

I used both ver. 1510r302 and 1510r306 and they both give me this error. The wiki only talks about the solution but doesn't actually say what is supposed to be done to fix it. How am I supposed to work around this problem? There isn't enough information for me to fix this problem anywhere.

EFI error when run wubi1604r303

Hi,

I'm trying to use wubi1604r303 with kubuntu 16.04.
After setup, I got error

04-03 19:47 DEBUG TaskList: ## Finished choose_disk_sizes
04-03 19:47 DEBUG TaskList: ## Running create_preseed...
04-03 19:47 DEBUG TaskList: ## Finished create_preseed
04-03 19:47 DEBUG TaskList: ## Running modify_bootloader...
04-03 19:47 DEBUG TaskList: New task modify_bcd
04-03 19:47 DEBUG TaskList: ### Running modify_bcd...
04-03 19:47 DEBUG WindowsBackend: modify_bcd Drive(C: hd 59739.8125 mb free ntfs)
04-03 19:47 DEBUG WindowsBackend: EFI boot
04-03 19:47 ERROR TaskList: substring not found
Traceback (most recent call last):
File "\lib\wubi\backends\common\tasklist.py", line 197, in call
File "\lib\wubi\backends\win32\backend.py", line 805, in modify_bcd
File "\lib\wubi\backends\win32\backend.py", line 577, in modify_EFI_folder
ValueError: substring not found
04-03 19:47 DEBUG TaskList: # Cancelling tasklist
04-03 19:47 DEBUG TaskList: New task modify_bcd
04-03 19:47 ERROR root: substring not found
Traceback (most recent call last):
File "\lib\wubi\application.py", line 58, in run
File "\lib\wubi\application.py", line 132, in select_task
File "\lib\wubi\application.py", line 158, in run_installer
File "\lib\wubi\backends\common\tasklist.py", line 197, in call
File "\lib\wubi\backends\win32\backend.py", line 805, in modify_bcd
File "\lib\wubi\backends\win32\backend.py", line 577, in modify_EFI_folder
ValueError: substring not found
04-03 19:47 DEBUG TaskList: New task modify_bcd
04-03 19:47 DEBUG TaskList: ## Finished modify_bootloader
04-03 19:47 DEBUG TaskList: # Finished tasklist

I'm using Dell vostro 5560 with ssd 120GB for windows ( efi partition here )
and HDD 1TB for install wubi folder here.
HDD not have efi partition.

thanks you!

Boot drops to a (initramfs) prompts/busybox

Hi,

I have installed Ubuntu 16.10 using wubi1610r319.exe and was installed successfully. I used the os for almost 7 days and then on boot drops to a busybox. I installed ubuntu almost five times but the issue persists.

My Hardware and Operating System Configuration:

  • Model: Dell Latitude E5470
  • CPU: Core i7
  • Storage: SSD 500 GB
  • RAM: 16GB DDR4

Please do help. Let me know in case if you need further information.

Thanking you,
Prakash

I got stuck with the installation of 16.04.2,16.10,17.04

16042_stuck

I attempted to install Lubuntu 16.04.2, 16.10, 17.04 at Wubi.
In 16.04.2, I stacked at the image, nothing happened after this.

For 16.10 and 17.04, I went up to the screen of the installer.
However, after the installer starts up, on the slideshow screen,
"I am creating an ext4 file system for / on partition 1 in the loopback (loop 2)"
(Japanese errors are translated by Google translation)
As it was displayed, it stopped moving.
Since the mouse and keyboard are alive, I was able to restart with Ctrl + Alt + Del.

How do I solve this?
Model: Inspiron mini 9
CPU: Atom N 270
RAM: 2 GB
SSD: 64 GB
OS: Windows 8.1 32bit
High-speed startup is turned off.
(I am Japanese. I am not good at English, I use Google Translate.)

Hint: "blk_update_request: I/O error, dev loop0, sector xxxxxxxx" + freezing system (SSD) workaround?

Hi everybody,

I have a rather old system.
Mobo: Gigabyte model: G41M-ES2L
Dual core Pentium E5400 (-MCP-)
RAM: 4GB
SATA: 3Gb/s (aka SATA II)

I use a SSD as 1st HDD:
SanDisk_SDSSDA12 size: 120.0GB (SATA III)

My "host" for Wubi-UEFI (ubuntu 16.04 64bit) is Windows 7 (NTFS).

Everything works fine. Love it!
But I often had a lot of random freezes (Mouse, Keyboard, Graphics - all dead).
Then I had to restart my system with the SysReq+Alt "R - E - I - S - U - B" keyphrase... (after enabling it first - in ubuntu it is disabled by default...)

dmesg always showed a lot (!) of rows with something like this:
blk_update_request: I/O error, dev loop0, sector xxxxxxxx
(xxxxxxxx = a random number...)

I read a lot of answers on the internet. One was saying that my SATA III SSD could (!) have problems with my old and slower SATA II connectors.
Look here

As a workaround it said:

(...)

  • paste the following command hit enter, enter your password

sudo gedit /etc/default/grub

  • find the following line (maybe there's allready something added inside the quotation marks)

GRUB_CMDLINE_LINUX=""

  • and add libata.force=noncq so it looks like this

GRUB_CMDLINE_LINUX="libata.force=noncq"

  • To apply the changes, exit the editor and paste the following line, hit enter, enter your password:

sudo update-grub

(...)

  • Explanation: What you actually do here is to change how your ssd is accessed. Switching off ncq can take the 'pressure' off the ssd a bit, but also makes it a bit slower. Sometimes this helps if you are experiencing freeze issues, sometimes not (other options underneath)
    (...)

I had to change that specific line on my wubi installation into:

GRUB_CMDLINE_LINUX="rootflags=sync libata.force=noncq"

What can I say. After rebooting there were no (or at least very seldom) error messages with "blk_update_request" any more. And (until now) no freezes.
Maybe this could be a hint for some people having this kind of problems too.

Greetings.
Ando

Ubuntu GNOME 16.10

I have installed Ubuntu GNOME with wubiuefi 1610r319 on Windows 10.
After rebooting to Ubuntu GNOME there is the Completing the Ubuntu installation. For more installation boot options, press 'ESC' now... screen.

When the timer ends or i press escape and pick any of the options my screen gets black and nothing happens.

Windows is hibernated, refused to mount

It states that mounting /dev/sda2 is not permitted.
Computer is always rebooted the usual way. Not suspended/hibernated.

What have I tried:

  1. reinstall
  2. run chkdsk /r and /f
  3. disabled safe boot and quick boot
  4. mounting /sda2 to /media/$dir

Don't know how to mount it. It says that I should try to mount it using 'ro' (read-only?) tag but I cannot write bash commands whilst in that screen. (/bin/sh not found)

error wubi1604r305.exe

Ubuntu 12.04.5 LTS (Precise Pangolin) this is good

1

Ubuntu 16.04 LTS "Xenial Xerus" This is an error wubi1604r305.exe

2

wubi-16.04-rev300.log
(((((((((((((((((((
04-19 22:54 DEBUG TaskList: ### Finished check_iso
04-19 22:54 DEBUG CommonBackend: Could not find any ISO or CD, downloading one now
04-19 22:54 DEBUG TaskList: New task download
04-19 22:54 DEBUG TaskList: ### Running download...
04-19 22:54 DEBUG btdownloader: downloading http://cdimage.ubuntu.com/daily-live/current/xenial-desktop-amd64.iso.torrent > C:\ubuntu\install\xenial-desktop-amd64.iso
04-19 22:54 ERROR TaskList: problem getting response info - HTTP Error 404: Not Found
Traceback (most recent call last):
File "\lib\wubi\backends\common\tasklist.py", line 197, in call
File "\lib\wubi\backends\common\btdownloader.py", line 78, in download
File "\lib\bittorrent\download.py", line 129, in download
File "\lib\wubi\backends\common\btdownloader.py", line 69, in error_callback
DownloadError: problem getting response info - HTTP Error 404: Not Found
04-19 22:54 ERROR TaskList: Non fatal error problem getting response info - HTTP Error 404: Not Found in task download
04-19 22:54 DEBUG TaskList: ### Finished download
04-19 22:54 DEBUG TaskList: New task download
04-19 22:54 DEBUG TaskList: ### Running download...
04-19 22:54 DEBUG downloader: downloading http://cdimage.ubuntu.com/daily-live/current/xenial-desktop-amd64.iso > C:\ubuntu\install\xenial-desktop-amd64.iso
04-19 22:54 DEBUG downloader: Download start filename=C:\ubuntu\install\xenial-desktop-amd64.iso, url=http://cdimage.ubuntu.com/daily-live/current/xenial-desktop-amd64.iso, basename=xenial-desktop-amd64.iso, length=1474953216, text=None
04-19 23:20 DEBUG TaskList: ### Finished download
04-19 23:20 DEBUG downloader: download finished (read 1474953216 bytes)
04-19 23:20 DEBUG TaskList: New task check_iso
04-19 23:20 DEBUG TaskList: ### Running check_iso...
04-19 23:20 DEBUG CommonBackend: Checking C:\ubuntu\install\xenial-desktop-amd64.iso
04-19 23:20 DEBUG Distro: checking Ubuntu ISO C:\ubuntu\install\xenial-desktop-amd64.iso
04-19 23:20 DEBUG WindowsBackend: extracting .disk\info from C:\ubuntu\install\xenial-desktop-amd64.iso
04-19 23:20 DEBUG Distro: parsing info from str=Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
04-19 23:20 DEBUG Distro: parsed info={'name': 'Ubuntu', 'subversion': 'Release', 'version': '16.04', 'build': '20160417.1', 'codename': 'Xenial Xerus', 'arch': 'amd64'}
04-19 23:20 INFO Distro: Found a valid iso for Ubuntu: C:\ubuntu\install\xenial-desktop-amd64.iso
04-19 23:20 DEBUG TaskList: New task get_file_md5
04-19 23:20 DEBUG TaskList: #### Running get_file_md5...
04-19 23:21 DEBUG TaskList: #### Finished get_file_md5
04-19 23:21 ERROR CommonBackend: Invalid md5 for ISO C:\ubuntu\install\xenial-desktop-amd64.iso (d2c082c976f35605a1e53e067c5e69d4 != 014d6dcdcc9c694158601c1cd1577c6b)
None
04-19 23:21 DEBUG TaskList: ### Finished check_iso
04-19 23:21 ERROR TaskList: Could not retrieve the required installation files
Traceback (most recent call last):
File "\lib\wubi\backends\common\tasklist.py", line 197, in call
File "\lib\wubi\backends\common\backend.py", line 600, in get_iso
Exception: Could not retrieve the required installation files
04-19 23:21 DEBUG TaskList: # Cancelling tasklist
04-19 23:21 ERROR root: Could not retrieve the required installation files
Traceback (most recent call last):
File "\lib\wubi\application.py", line 58, in run
File "\lib\wubi\application.py", line 132, in select_task
File "\lib\wubi\application.py", line 158, in run_installer
File "\lib\wubi\backends\common\tasklist.py", line 197, in call
File "\lib\wubi\backends\common\backend.py", line 600, in get_iso
Exception: Could not retrieve the required installation files
04-19 23:21 DEBUG TaskList: # Finished tasklist
)))))))))))))))))))))))))

Logitech g35 microphone not working

I just installed ubuntu I got everything working but when I joined discord my mic wasn't working I went into sound settings input and nothing was getting picked up any help?

How to use a pre-downloaded iso ?

I have downloaded an ISO from the official download in ubuntu site so I don't need to redownload it, Any way to manually set the ISO ?

Thanks.

Make script tries to download from a 404 link

Just trying to run make :

--2016-08-28 15:01:01-- http://mock.googlecode.com/files/mock-0.3.1.zip
Résolution de mock.googlecode.com (mock.googlecode.com)… 74.125.71.82, 2a00:1450:400c:c0b::52
Connexion à mock.googlecode.com (mock.googlecode.com)|74.125.71.82|:80… connecté.
requête HTTP transmise, en attente de la réponse… 404 Not Found
2016-08-28 15:01:02 erreur 404 : Not Found.

Possible solution :

The package grub UEFI couldnt be installed in /target/

First of all let me thank for your efforts to make an UEFI install of Ubuntu on computers with a 32 bit boot loader possible.

I got from my daughter an ODYS TRENDBOOK 14 inch and I love it. However the hardware and firmware (32 bit bootloader and an 64 bit system) makes it hard to install Ubuntu ion the machine.

ISSUE No. 1
I tried the wubi 16.10, 16.04.2 wubi.exe to install it on my C-drive. Everything goes well. When rebooting as requested, the system tells me "EFI requested map not found and ESRT header not in XXX map. Then the ubuntu install process starts until grub should be installed. Then I receive the message "grub-efi-ia32couldnt be installed in /target/. Without bootloader the installed system will not start (All the messages are translated by me from German, so it is not exactly the the english wording)". When acknowledging the message I receive the next message that the installer is crashed. Now another message pops up "Loop-mounted file system already present. The selected (partition 3 of /var/lib/partman/devices/=dev=mmcblk1) already contains the following file system images: /ubuntu/disks/root.disk Pls uninstall these before trying again. After acknowledging all messages the system boots into a kind of live system.

Issue No. 2
I also tried to use the installer of the live system to install ubuntu on my SD card. Everything went well until the requested reboot, which ended at a grub rescue prompt.

Pls advice what to do. Wubi installation would be fine to me as well as an install alongside to windows.

As I am not a native english speaker, pls advice me in the most simple way. Also I am not a computer expert.

best regards

Hilmar

[Errno 13] Permission denied: 'D:\\...\\vmlinuz'

I try to install Ubuntu on 32-bit Windows XP by:

  • placing 32-bit desktop DVD ISO next to wubi.exe (in two ways - with network on and off),
  • letting WUBI to download proper ISO,
    but every time I get the following error (please find the logs as an attachment):
    ERROR root: [Errno 13] Permission denied: 'D:\ubuntu\install\boot\vmlinuz' Traceback (most recent call last):

Could you please help me with this?

Best regards

wubi-16.10-rev317.log.txt
wubi-16.10-rev318.log.txt

WUBI 14.04.4 won't run on Windows 7

Hello,

I have Windows 7 SP1 64 Ultimate UEFI:
Wersja 6.1.7601 Service Pack 1 Kompilacja 7601

I downloaded Xubuntu 14.04.4 ISO from:
http://cdimage.ubuntu.com/xubuntu/releases/14.04/release/xubuntu-14.04.4-desktop-amd64.iso

then downloaded Wubi for Ubuntu 14.04.4 (rev.304) from:
https://github.com/hakuna-m/wubiuefi/releases/tag/14044r304 (wubi14044r306.exe)

Both the ISO and WUBI are placed in the same folder.

When run WUBI binary...nothing happens - it even won't run, nothing shows up on the screen (even when run as administrator), just circle of cursor is rotating for a few seconds and then dissappears.

I remember a few month ago, on my old computer with Windows XP SP3 32 Pro, I successfully installed Xubuntu / Ubuntu / Lubuntu 14.04 in WIndows XP using WUBI, now after I switched to a new PC & OS, WUBI won't even run.

[Edited]
OK. I workarounded the issue after asking uncle Google for a phrase "wubi wont run" - I found someone's answer saying something about checking WUBI log files in some Windows TEMP folder (I didn't even know that WUBI creates the log file), so the log says WUBI was scanning & checking all my PC's partitions for any ISO files and failed on some ISO file with

Error: D:\x.iso: Can not open file as archive

After I changed extension name "iso" to "ixo" (thereby making WUBI skip this file), WUBI finally runs.

I wonder why WUBI scans all my partiitons for all ISOS, instead of just simply loading the proper ISO file located in the same folder...

The second thing is , even omitting the above, why does it fail on some bad ISO, instead of just skipping the bad ISO?

make: errors on Ubuntu 16.04

I installed the source code of Wubiuefi on a fresh installed Ubuntu 16.04 with the following commands:

sudo apt-get install git
git clone https://github.com/hakuna-m/wubiuefi.git
cd wubiuefi
make

After downloading and installing some programs like Wine, Python, 7-Zip etc, I got the following error message:

make[1]: Entering directory '/home/hakunamatata/wubiuefi/build/pylauncher'
i586-mingw32msvc-gcc  -c -Os -Wall -m32 -march=i386 -D_SZ_FILE_SIZE_32 deletedir.c
sh: 1: i586-mingw32msvc-gcc: not found
Makefile:93: recipe for target 'deletedir.o' failed
make[1]: *** [deletedir.o] Error 127
make[1]: Leaving directory '/home/hakunamatata/wubiuefi/build/pylauncher'
Makefile:65: recipe for target 'pylauncher' failed
make: *** [pylauncher] Error 2

Unfortunately, Ubuntu 16.04 has no package mingw32 in its repository, so I downloaded and installed this and dependent packages from here

After that I tried to continue with
make
and I got:

sbsign --key .key/*.key --cert .key/*.crt --output build/winboot/EFI/grubx64.efi build/winboot/EFI/grubx64.efi
warning: overwriting existing signature
Segmentation fault (core dumped)
Makefile:75: recipe for target 'winboot2' failed
make: *** [winboot2] Error 139

I found a bug report. This error occurs only sometimes. Finally I could build a wubi.exe.

So, I will create a new version which should install mingw32 automatically on Ubuntu 16.04, too. The sbsign bug should be fixed by the maintenance team.

How does lupin works?

Which files responsible for the loopback booting? An initramfs script which has named lupin seems to be responsible for first time use only

Resume failed download instead of requiring uninstallation first

I was trying to give it a try (for the first time). However I got the message box saying

---------------------------
Xubuntu Installer
---------------------------
An error occurred:

Socket Error: [Errno 10054] An existing connection was forcibly closed by the remote host

For more information, please see the log file: c:\users\mlt~1.des\appdata\local\temp\wubi-16.10-rev314.log
---------------------------
OK   
---------------------------

The content of the log is available on hastebin. So perhaps the internet connection got dropped (though why log says download finished ❓😕).
When I restart the installer, it asks me to uninstall whatever is there and start all over (I tried twice).

It would be nice if download was resumed where it left off.... if it was a download issue.

P.S. I was using the latest available binary from Releases.

missing translation for "remaining time"

"Remaining time approximately" is still in English even if you don't select English as your preferred language. e.g. if you select German:
remainingtime
A German translation exists in file de.po. For other languages there are also translations in their language files. But it is the only translation with possible plural forms. i.e plural forms don't work.

I'll fix it for the next release.

busybox after initramfs-tools update

I received a bug report that some users got a busybox prompt after initramfs updates on Ubuntu 16.04.

I updated initramfs-tools from 0.122ubuntu6 to 0.122ubuntu7 and I could reproduce that issue. It was possible to change ro -> rw in Grub as a workaround.

Meanwhile I found a solution. If you type
sudo update-initramfs -u
the initramfs patch is copied to the current initrd.img file and all things work as before.

It seems that in some cases an additional update is needed. But IMHO mainly it is an issue of versions under development. It doesn't affect a fresh install or an upgrade because every kernel update also triggers an additional initramfs update.

grubia32.efi [ grub ia32.efi signed package failed to install into target]

I am new to Ubuntu/Linux. I have battled with the installation of a dual boot with Windows 10 and Ubuntu. I have downloaded the latest beta version for ubuntu 16 wubiuefi installer. I had many failures untill I finally managed to open the boot menu and selected "Graphical safe mode" from the menu. It started the installation with a few problems.

My mouse and keyboard did not work.Plus the touchscreen was disabled. I figured after the installation and a reboot, the drivers would work and I could use the mouse and keyboard again.
But I didn't even get that far.

I received an error [grub ia32.efi signed package failed to install into target].

I am on a pre-installed Windows 8 upgraded to Windows 10 on a Samsung 500T ATIV .

Error installing ubuntu 16.04 wubi16.04r310 with windows 10 64-bit release 14366

Hello dear Hakuna, it's a new issue-i had a dual boot windows 10/ubuntu configuration installed via wubi16.04r309 .But when installed latest windows release 14366 in slow channel, after restarting to go in to ubuntu give me this error:
https://goo.gl/photos/R3agVVUfVuh6ekgu5
I will try reinstalling twice with wubi 16.04310 and 310-2 but gave this error again!New windows release broke alongside ubuntu installation, and after that couldn't install again!

User can choose install folder name?

I see in 1604r310-2 you change some name of default wubi install.
Can you add input for advanced user can choose name of folder install?

I think this is best for multi install.

Thanks you!

How to use local iso image without download

I already downloaded ubuntu-16.04.1-desktop-amd64.iso in the same directory with wubi installer.
Although wubi downloaded iso image without it.

I think the image directory is C:\ubuntu\install, so I tried to copy it before and after run installer but both methods are failed.

So how can I force to use the downloaded iso image?

Dell Laptop RAID mode

Try r319 on Dell Latitude 7270 (win10/nvme/raid mode/UEFI/secure boot)
Can't boot into ubuntu, initramfs prompt and error message: "Could not find the iso /ubuntu/installer/installation.iso"

attempt:

  1. switch RAID to ACHI
  2. switch UEFI to legacy

option 1 or 2, it's fine to finish installation, but affect win10 boot

About this intel's fake RAID mode, could I just copy installation.iso into root.disk and delete it after installation? Or should I need RAID driver/something else?

Missing ubuntu entry in Windows 10 Boot Manager

I just installed Ubuntu Mate on my Windows 10 Pro 14393 (Anniversary Edition). Wubi install failed first time after downloading the iso (couldn't extract). I then repeated another time by mounting iso in explorer and installation went fine, it rebooted and installed ubuntu. But now I don't see Ubuntu in the Windows boot manager, laptop boot directly into Windows, bcdedit /enum doesn't show anything for ubuntu, just Windows boot manager and Windows 10.

I am using an UEFI system, without secure boot, and GPT partition table.

can I add the entry with bcdedit manually? what command should I run?

Ubuntu boots to Grub menu after Wubi Ubuntu wubi16041r311

I installed Wubi from your wubi16041r311 file. I rebooted liked it asked. It loaded into Ubuntu to finish the install. I was even able to open Firefox and browse the internet while it finished installing files. Then It restarted and added Ubuntu to the boot options. When I select Ubuntu to load it says "tryntfs5(hd0.0)
tryntsf5(hd0.1)

No Wubi ldr"

after it shows this, it then boots into a program called "Grub".

What do I do to get it to load the installed wubi16041r311 ? Is there anything I can do to fix this ? I am using windows 7.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.