Hi, I am currently using a Dell Inspiron15R with 8 GB RAM and an i7 processor. I successfully flashed the Qubes ISO on a USB stick and then tried to install it onto an external hard drive in both UEFI and Legacy mode.
All the steps run smoothly after the first reboot into the drive, which requires me to configure the OS (the one where I can chose to update over the tor network), however after a long installation time the dialog box finally displays Installing Network Drivers before it unexpectedly crashes and then displays a black screen with just a single cursor at the top left corner.
I left my laptop in that state overnight hoping it would reboot but to no avail. No commands work at that point so I had to force my laptop to shut down by long pressing the power button, following which it then booted into the external drive again but ended up giving me the ādracut initqueueā timeout error, because I am guessing that somehow the initial install got corrupted.
I tried to update my network drivers, but they were already up to date. Then I tried by disabling my NIC card in BIOS before the install but it still gives me the same error of a black screen with just a small cursor on the top left corner towards the end of the install.
However, the same issue occurred at the same step with Qubes 4.1 so it really has something to do with setting up sys-net/sys-firewall.
I recently got hacked and they took 40% of my net worth! I believe that I am currently being targeted here because I am in possession of proprietary IP. Solving this issue is really important for me. Thank you for the help.
A while ago I got the same exact symptoms but the issue was I was trying to install it in an external SSD and forgot to disable sys-usb on the setup step. Are trying to do something similar?
Yup, that is exactly what I was trying to do and then it finally worked after unchecking sys-usb!
However, I am still unclear about how to setup sys-usb post install and about how to get it to connect to a mobile hotspot, which is currently not showing up in my WiFi networks.
How many USB controllers do you have? If you have only one it probably wonāt be possible since Qubes itself is being loaded from that USB controller. If you have more than one I think this is possible. Take a look at USB qubes | Qubes OS and pay special attention if youāre using a USB keyboard and mouse.
Also, Iāve propposed a change to the documentation on āinstallation troubleshootingā to mention this case as well since two users have now reported it (you and myself):
Hi - not sure if I should post here or start a new thread - Iāll try here first:
Iām experiencing the same thing - where the installation stalls at the network setup. Iām using a Dell Lattitude E6420.
However, Iām not installing on an external usb drive. Iām doing a regular install on my internal ssd drive.
From researching online, I assumed it was a driver issue with my Qulacom wirless card. And, Iām hesitant to get a different card because Iām not confident that there wonāt be compatibility issues with that one as well.
I do see that the E6420 should work based on the hardware compatibility lists. And, it will install for me if I uncheck everything and go for a custom install. But:
Iām not at the point where I can do a custom install yet.
and
Just because the base setup can install, that doesnāt mean it wont fail again when I try to install the network manually.
So, my question is ā is there a workaround for my installation issue? Is that USB workaround applicable to my situation?
Thanks
You just need to disabled sys-usb during the configuration step of the install. As far as I can tell turning the network card on or off had no major effect for me.
There is a huge difference between the number of ports and the number of
controllers.
You can have a large number of ports off one controller.
You can have one controller per port.
The only way to confirm is to run lspci |grep -i USB - this will show
you the controllers, slot, and type.
Disabling sys-usb during config did not work for me. It still hung up at network config. I think itās compatibility with my network card. Iāll start another thread so as not to hijack your thread.
Thanks
I am sorry to hear that disabling sys-usb didnāt work. However, before I tried the second install with sys-usb disabled I had tried an install with my network card disabled and all of the other options disabled as well just so that I could enter into the login screen. Then in the middle of the install process when the dialogue box was up, I clicked on the configuration menu again and reselected all of the options above sys-usb.
But what I am using now is a fresh install that I performed with the network card and sys-usb disabled. Hope this helps!