# Netrunner Live 2016.1 hangs at boot before GUI
**URL:** https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024
**Category:** Rolling 2016.01
**Created:** [June 26, 2016, 2:55pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024 "2016-06-26T14:55:55Z")
**Posts on this page:** 10
**Page:** 2
### Author:  [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [June 27, 2016, 3:42pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/21 "2016-06-27T15:42:08Z")
OK, now we are getting somewhere, In legacy (bios) mode the live media uses syslinux, in EFI boot mode it uses grub.
Can you get to at least a vt (CTRL+ALT+F2) on boot so we can find out which modules are not loading?
```auto
systemctl status systemd-modules-load
```
---
### Author:  [@Avonidas](https://support.blue-systems.com/u/Avonidas)
#### Post date: [June 27, 2016, 3:54pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/22 "2016-06-27T15:54:41Z")
> [@AJSlye](#):
>
> OK, now we are getting somewhere, In legacy (bios) mode the live media uses syslinux, in EFI boot mode it uses grub.
> Can you get to at least a vt (CTRL+ALT+F2) on boot so we can find out which modules are not loading?
>
> ```auto
> systemctl status systemd-modules-load
> ```
I can get to a VT… but I can’t get a prompt. ☹ It just shows that “start job is running” message in all VTs.
I’ll try legacy.
---
### Author:  [@Avonidas](https://support.blue-systems.com/u/Avonidas)
#### Post date: [June 27, 2016, 3:56pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/23 "2016-06-27T15:56:17Z")
Nope, same with legacy. I can’t get to a prompt.
---
### Author:  [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [June 27, 2016, 4:04pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/24 "2016-06-27T16:04:00Z")
I hate to ask, but did you check the md5sum on the ISO file?
How did you burn the media (ie. what application did you use)?
Like arch and many other hybrid ISO files, these ISO’s are NOT compatible with Unetbootin or similar utilities that extract the ISO to an already existing filesystem (fat16, fat32, etc.). These ISO’s require that they are written to the media in raw mode, keeping the ISO 9660 filesystem in tact.
---
### Author:  [@Avonidas](https://support.blue-systems.com/u/Avonidas)
#### Post date: [June 27, 2016, 4:15pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/25 "2016-06-27T16:15:16Z")
> [@AJSlye](#):
>
> I hate to ask, but did you check the md5sum on the ISO file?
> How did you burn the media (ie. what application did you use)?
> Like arch and many other hybrid ISO files, these ISO’s are NOT compatible with Unetbootin or similar utilities that extract the ISO to an already existing filesystem (fat16, fat32, etc.). These ISO’s require that they are written to the media in raw mode, keeping the ISO 9660 filesystem in tact.
i) Yes, I checked the md5sum
ii) I have tried both with USB Creator and with dd, the results are the same.
---
### Author:  [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [June 27, 2016, 4:29pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/26 "2016-06-27T16:29:01Z")
I just checked the Manjaro forums and others are reporting the same skylake issue, even with the 16.06 install medias.
---
### Author:  [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [June 27, 2016, 4:47pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/27 "2016-06-27T16:47:47Z")
Update: In UEFI boot try adding nolapic to the boot parameters, in BIOS mode F4 \> No Local Apic.
---
### Author:  [@Avonidas](https://support.blue-systems.com/u/Avonidas)
#### Post date: [June 28, 2016, 8:58am UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/28 "2016-06-28T08:58:27Z")
> [@AJSlye](#):
>
> Update: In UEFI boot try adding nolapic to the boot parameters, in BIOS mode F4 \> No Local Apic.
Tried it with BIOS and UEFI, free/nonfree. No luck :s
Should I change any other boot parameters?
---
### Author:  [@Avonidas](https://support.blue-systems.com/u/Avonidas)
#### Post date: [June 29, 2016, 7:58pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/29 "2016-06-29T19:58:08Z")
So, I have been trying Manjaro 2016.06, with various boot parameter combinations, still no luck.
The one thing I have established is that it _is_ possible to boot into GUI by disabling KMS for nouveau (it worked in KaOS), but in Netrunner and Manjaro I keep getting this “FAILED to start load kernel modules” message at boot.
I’m not sure how to proceed. Could it simply be that KaOS has a newer kernel? Is there any way to “patch” the Netrunner ISO so that I can work around this frustrating issue?
---
### Author:  [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [June 29, 2016, 10:41pm UTC](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024/30 "2016-06-29T22:41:32Z")
KaOS only has the latest release kernel available, and a more up to date release of Xorg.
Manjaro has multiple kernel versions available, and ship their ISO’s with the latest LTS kernel.
They also have been holding back xorg to maintain compatibility with the catalyst drivers.
KaOS 2016.06 = Linux kernel 4.6.2 + xorg-server 1.18.3
Manjaro 16.06 = Linux kernel 4.4.12 + xorg-server 1.17.4
[Previous page](https://support.blue-systems.com/t/netrunner-live-2016-1-hangs-at-boot-before-gui/4024.md?page=1)