I have tried to install Kali Linux as dual-boot and i also tried the live version.
After the installation i get this on a total black screen:
hub 6-0:1.0: config failed, hub doesn’t have any ports (err -19).
This error occurs early in the boot process and indicates that the Linux kernel cannot configure one of the USB hubs (either internal or external) because it does not detect any available ports. The error code err -19 specifically means that the device or hub was not found or is unavailable.
My PC is a Lenovo LOQ 15ARP9 which uses a modern USB controller, possibly USB 3.2 or USB-C, which the kernel may not correctly recognize and windows 11. I dont know if it has something to do about that.
I have used a new kingston 64gb datatraveler USB flash drive. Im sure it is not a broken usb flash drive and i use balenaETCHER to make the .iso on the flashdrive.
What do i do wrong or what can i do to fix this problem?
Same problem but booting process stops there. I also tried going into recovery mode ( all several kernels) and still freezes. any idea on how to fix it apart of booting from flash drive?
If it will boot from a Live ISO image, and everything works, it would suggest that the drivers and firmware for the USB hub aren’t being installed properly on the hard drive install.
if you choose the option to update kali at install time, then it should install the correct firmware and drivers for your hub and when you reboot it should then work, the update option at install time may not work if you don’t have enough RAM though, in which case you’d probably have to install kali, and then at a reboot, at the grub screen choose the advanced start up and add a kernel parameter to blacklist the usb at start up;
blacklist=usb-storage,uas
once in a working kali install, you should then be able to fix the issue with modprobe.
@Utlagi, there are lots of instances, most of them well discussed at Stack Exchange, of this log appearing when installation fails. Rarely is there a correlation between them.
@Fred and @arisu, have either of you any idea of what, exactly, the cause is, and thus how to deterministically remediate it, and verify that it’s been remediated?
You say you get this ‘after the installation’ does that mean it will boot from the live image and you get to a working Kali desktop?
(I’m presuming you are using the latest Kali ISO image)
If you do, then before you do an install, do an update and upgrade on the live system, it should pull in any needed files and firmware for your devices, and write the updated system to the hard drive when you install. Before you reboot after the install, you could use modprobe and ensure your devices are being seen correctly.
@Fred, actually, I’ve yet to run Kali on my host OS. I can do so, and it’ll likely occur, because it occurs on openSUSE TW 2025 and Fedora 42. Basically, I’ve yet to see an OS that I don’t see it on, but I’ll write a Kali ISO to confirm.
I was under the impression that this is generally inadvisable due to live installations being fragile things, with generally static storage allocations.
Do you know of a relevant tutorial for this? I’ve used the command a few times, but I’m not confident in my ability to ascertain whether I see the correct hardware or not, since what hardware the error refers to isn’t clear to me.
To update a live image before writing it to disk as an installed system is fine, as long as you have enough RAM memory to download the update (say updates took 2 GB for example, and the Live system is already using 4 GB, plus you need some room for the OS to run, so ‘less than 8GB’ would probably hang for example, as it would run out of space.
I think your hardware may be too new and no drivers are available, Fedora is always pretty up to date, and will run on systems where many other Linux versions will not (it is the only Linux OS that will typically install and run ‘out of the box’ on an Intel Based Macbook for example)
If no other Linux distro has worked, then anything based on Debian stable (like Kali) is very unlikely to work either, Debian are quite conservative with their update cadence.
The unstable branch of Debian, ‘might’ have the needed drivers..
add this to your apt sources list to try the repo;
deb https://deb.debian.org/debian/ unstable main contrib non-free
deb-src https://deb.debian.org/debian/ unstable main contrib non-free
@Fred, disabling the virtual USB controller would presumably also disable all dependent hardware, since it’s the controller. The respondent to your cited comment states that.
Good point about the EFI implementation, though – I’ll ask ASRock too, alongside AMD (and Fedora and Kali), then go to the kernel if they direct me there.
And I see the USB ports support always on USB for charging devices, and instant boot when power plugged in to the USB C port. Try disable both and see if it helps?
