So I’m using a Gigabyte G5 MD & have been trying for a while to get my USB-C Port to work with no success.
I tried seeing if anything showed up with ‘dmesg -Hw’ & nothing shows up when i plug anything to the USB-C Port. Tried using ‘lsusb’ to find what the port is labeled as but sot sure which as well as ‘lspci -nnk’ cause im not exactly sure where to look. Any help would help
Does
journalctl -b 0 | grep usb
(issued as user “root” in a console) deliver anything useful?
If not open a console and enter
su
journalctl -f
plug an USB-device into your USB-C port, wait a few seconds, then go to the console and press Ctrl+C, copy the complete output since the start of journalctl -f and show it here.
While the device is plugged in do (as “root” in a console)
hwinfo --usb
and show those results as well.
while poking with ‘journalctl -f’ i got “kernel: usb 1-2: Device not responding to setup address.” & “kernel: usb 1-2: device not accepting address 37, error -71”. i want to say this is the USB-C Port but im not sure but it only triggered once & all my other usb ports show different numbers that arent 1-2
UPDATE: i plugged something in while running ‘journalctl -f’ and it was connecting & disconnect constantly
I asked you to show the complete result produced with journalctl -f and more!
Please do not forget:
The only thing I (and others who want to help you with your problem) know about your system is what you present here. We/I cannot look over your shoulder nor can we/I read your mind.
And just one more piece of advice: If you use punctuation and paragraphs to structure your post others (e.g. non-native English-speakers like me) may find it easier to read and understand your post.
As @susejunky already explained this is unreadable. I like to add that you have to use the </> button around the sections of code you copy/paste here. And copy/paste including the line with the command, then there is no need to tell stories like “while poking … i got …”
Hello:
Although there may be connector compatibility and some USB, they are two completely different things (I recommend you look at Intel).
Since thunderbolt has more bandwidth, it can be used to connect PCs, and send HD video.
That is why it is more advisable to see it by pcie, than by a usb hub (even if it is derived from a pcie).
When used in net, it needs to be administered and authorized, for video I don’t think it’s necessary, anyway you can see it with boltctl:
HPOMEN:~ # boltctl monitor
Bolt Version : 0.9
API Daemons: 1
Client API : 1
Security Level: unknown
Auth Mode : enabled
Ready
Greetings .
Thunder… , I think it is activated from bios, and some motherboards have a 2x2 thunder connector, but the one on the box or tower is missing (it does not have a type C connector)
ok, here is the entirety of doing ’ journalctl -f’ openSUSE Paste
i also tried looking for the option in my bios, and its not there.
Hello:
On an Asus, it came to me inc. on a pcie board, the mac (apple), I think they are the ones that integrate it the most (a security problem from a long time ago, affected their computers and also linux).
In comparison, these Dell graphics can give an idea (usb 4.0, for now it is not commercial), but what does integrate thunderbolt is communication.
Thunderbolt networking, is it a difference with usb, does it affect your networking tests? .
What I see, that both are very similar, with clear differences (bandwidth above all), in the Dell graphics, they are clear:
and in the kernel : Thunderbolt — The Linux Kernel documentation
That in case nothing comes out with the usual commands.
Greetings
Hmmm, …
can’t see those messages in what you show on paste.opensuse.org ???
i cant get it to show up again.
Does this mean everything is working as expected now?
no, still nothing, any other suggestions?
You could start with supplying detailed information on the USB-device you plugged in (and which was not recognized by your system).
Do you have any USB-devices which do get recognized when you plug them in?
The results of (after you plugged in the device which gets not recognized)
journalctl -b 0 -p 3
and
hwinfo --usb
(both commands issued as user “root” in a console) might help to analyze your problem further.
Hello:
It is curious, with hwinfo --usb , usb type c does not come out, instead with inxi -xxxJ , if they appear (5Gb and 10Gb speeds), in the x299 manual, they appear as usb type c and intel thunderbolt 3.
I tried to connect a type c of the board to a type c of the monitor and this activates the input as usb type c.
Isn’t there some command that identifies them better?
Maybe lspci , but I have no idea what name it might appear under.
For a long time, some USB devices did not detect them, but others did, an example of this is that I connect an M2 nvme to usb 3.1 or 3.2 and I detect it well:
mikrios:~ # lsusb
Bus 006 Device 002: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
(bus 6 device 2)
From inxi-xxxJ:
Device-1:6-1:2 info: Realtek RTL9210 M.2 NVME Adapter type: mass storage
driver: uas interfaces: 1 rev: 3.2 speed: 10 Gb/s lanes: 1 power: 896mA
chip-ID: 0bda:9210 class-ID: 0806 serial: N/C.
(usb 3.1 gen2 —> 10Gb/s) .
What I did see on the web is that some motherboards may have problems with usb, and they say to enable xHCI, EHCI and IOMMU controller in bios, but I think that’s old and I don’t think it’s part of the problem.
Greetings
Does this tell you anything? Because it looks like that it does see the port from the <3.1 20 Gb/s>
https://paste.opensuse.org/pastes/e2c6550ac693
It does not match what I saw on the web 20Gb/s for a USB 3.2 (if it is a usb 3.1 what I have seen is at a speed of 10Gb/s).
The manual or user guide usually brings that data (summary specifications)
It would be interesting to identify the physical port with the data given by the console, I don’t know if this can show what it is: lsusb -s 1d6b:0003.
In my case and in the manual and physically it is identified as thunderbolt 3 and it was tested with a vna (vector network analyzer, I think it is a usb 2.0) and on the computer those ports correspond to 2 type c and 2 DP connectors (display port ) .
With vna it gave me errors and with M2 to usb 3.2 it was correct (it could be a communication failure, in one of the times and in a port, it came out as a moden).
I will have to study a little more about thunderbolt and differences with usb.
Greetings
sorry for the late reply but here’s what it outputs from that command
I have a Ryzen 4600h HDMI port with a nvidia 1660 ti connected to USB-C .
here with tumbleweed and 4 screens
https://youtu.be/a3DKCin56wA
The issue might be a wrong adapter.
If it works with windows does not mean, it works with Linux.
I tired 20 different adapters.
Some get 4k@60 with windows but only 1080 on Linux.
Some work with Windows, but not Linux.
And some don’t work at all.
you need a USB-C Alternate adapter.
I found a MST DP to 3 HDMI adapter, that works well with Linux.
and you might also try different adapters.