7

I have a fresh install of Ubuntu 22.04 on a newly build PC dual booting Windows on a second hard drive. Whenever I boot into my Ubuntu drive, it first reports the error "hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)".

Over the next ~40 seconds, it reports the following error about 3-4 times: "usb 1-7: device descriptor read/64, error -110".

Then once it does this, it finally brings me to the login screen with no more issue. I've confirmed all USB ports (both A and C) are functional on my motherboard. I've also attempted to boot my computer with nothing plugged in other than my monitors via DisplayPort and my speakers via the 3.5mm audio out, but the errors above still showed. My motherboard has been updated to its latest firmware.

Can someone help me figure out how to solve this?

EDIT: Just realized it's probably important to note that my motherboard is an MSI MAG B650 Tomahawk Wifi.

Logan G.
  • 83

3 Answers3

3

I have same problem. Debian kernel 6.1 does not boot with Ryzen 7900 and Asus b650e. "hub does not have ports" was the error and freezes there.

Debian kernel 5.10 boots, but does not detect the igpu properly, can't change screen resolution up.

So I think Ryzen 7000 does not work yet with Debian 11 kernel 6 and iGPU is the problem.

J. Kos
  • 31
2

I had a similar problem with Unbuntu 22.04 on an MAG B650 Tomahawk Wifi (MS-7D75)

Linux kernel 5.19.0-32

A windows install worked just fine. I was able to get it going with the most recent firmware build: 7D75v164(Beta version) https://www.msi.com/Motherboard/MAG-B650-TOMAHAWK-WIFI/support#bios

It's a beta, so be careful, but it worked. The previous version I had on the board when I got it was 7D75v13.

user37234
  • 21
2

I had exactly this error during boot on a fairly new Ubuntu 22.04 installation. It was caused by the kernel update from 5.19.0-41 to 5.19.0-46. I had no GRUB boot menu, and couldn't find any way to interrupt startup to obtain one.

I followed the instructions here to use boot-repair to perform the "Recommended repair", thus setting up a GRUB I could interact with.

I can now manually select 5.19.0-41-generic to boot successfully.

Googling suggests that my problems are related to use of nvidia and that booting with nomodeset may be a work around (see here). I think I'll just see if it persists with the next kernel update before I try any harder.

kikazaru
  • 121
  • I also think that the problem is related to Nvidia. I had the exact same issue but when I swapped out the graphics card for a new AMD Radeon card, the problem was gone. – lvcivs Sep 12 '23 at 11:21
  • Can also confirm problem from nivdia: Forced internal graphics (forced IGFX) and the system booted up normally. – Tenders McChiken Dec 19 '23 at 10:33