First time here, hope i’m in the right section.
I installed Qubes 4.2.3 on a flash drive and had to use kernel latest i’m guessing because of some of my hardware but everything went good. I have tested, like and wish to install in a more permanent setting.
I have a several TB Hdd and set it to run on kernel latest, it finishes setup and i tic reboot, remove installation media and everything comes up. Put in the Passphrase all good. Make all settings and account and tic finish setting up.
This is where i have the problem, it gets all the VM’s done and when it gets to setting up network about 20-30 seconds in it locks everything up.
I have reinstalled from scratch 3 separate times with the same conclusion.
Any help would be greatly appreciated.
If that allows you to boot, go to the device settings of sys-usb and remove all controllers, and add them one by one. Restart sys-usb for each controller you add, until you find the one that crash the system.
That is how I fixed the issue with my motherboard.
Alternatively, disabling Wi-Fi and BT in the BIOS also solves the issues for me, which only works if you don’t want to use them
More detailed information is required, please. E.g:
Mainboard: Supermicro X10SLM±F (hw specs here)
BIOS: coreboot with seabios payload
CPU: Xeon E3-1265 v3
RAM: 2x 16GB DDR3 ECC (Samsung)
Graphics: integrated GPU
Networking: one of the onboard NICs (here: 1 Intel® i210AT)
Storage: 2 1TB HDDs (connected via SATA ports 1&2, AHCI mode, LPM/ALPM disabled)
Flash Drive: SanDisk USB3 32GB
I started with a USB 3 flash drive attached to external port 1 (USB 3) connected via the original headers and everything went on fine. Had to choose kernel-latest though and changed some $BIOSSETTINGS
Then I went over to try the HDDs. I combined the two disks in a LVM group as described here:
The disks got connected and were found as [$LOGFILE | $TERMINALOUTPUT] suggests …
etc. etc. etc.
Startup crashes can be caused by almost anything from bad RAM, misconfigured or bad storage controller implementation, bad NIC (aka Realtek) to misconfigured or bad software …
Mother Board: B650M-A AX ll (HW specs Here
Bios: (Can’t seem to find How to info for retrieving BIOS info in Qubes)
CPU: Ryzen 9-7900 (HW Specs Here)
Graphics: MSI - RTX -(1080?)
Networking: (Can’t seem to find How to info for retrieving NIC info in Qubes)
Storage: (1x) 1-TB M.2 nvme (?Mfg.) (2x) 8-TB WD-Purp Hdd Connected on SATA 1&2
Flash Drive successfully installed Qubes on: Sandisk Ultra 3.0
Flash Drive (Installation Media): 32-Gb - Just shows “Product Code”? (Generic cheap but install Media worked fine installing to USB just not PC)
I hope this is enough info or i will have to open another thread to find out how to get more info, i am a mediocre user at best and this is all new to me.
For collecting information/details, can you try to open a dom0 terminal and run:
sudo dmidecode -t bios
sudo lscpi
sudo lspci -v
The last will give a lot of details (for devices), so maybe you just want to locate the network device IDs (the XX:YY.Z in front of a line) with lspci and then run
sudo lspci -v -d XX:YY.Z
for those.
If you have sys-usb running, you can open a terminal in sys-usb and run