Date: Wed, 18 Jan 2023 11:45:21 +0000 From: Gary Jennejohn <garyj@gmx.de> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: TP-LINK USB no carrier after speed test Message-ID: <20230118124521.250366ef@ernst.home> In-Reply-To: <CP6P284MB1900180AA335B633D2222B7CCBC69@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> References: <CP6P284MB1900F16EDAEAF1CB485BC372CB499@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> <9c370afb-1931-f977-16a9-4915a82ec773@selasky.org> <CP5P284MB19020B7054012F9140E9D8F2CB489@CP5P284MB1902.BRAP284.PROD.OUTLOOK.COM> <CP6P284MB19005F8AF0CF964D011E8EA7CB4A9@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> <fd261e3f-ed98-1c48-2af2-943520acbf13@selasky.org> <5bf98c30-c00f-7e7a-3a3d-c0bd5862fb97@selasky.org> <CP6P284MB1900A6E8ECDB4CFF78323904CB529@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> <d863a8ec-edfd-73bc-c772-216830e0d7d5@FreeBSD.org> <1f11b131-7031-60db-4331-d95159c5b373@selasky.org> <bc90f83d-511d-d31f-d9f7-0aaf82ecba4a@FreeBSD.org> <4f8778a0-0c47-ff47-f954-ba4e8d9fc5e1@selasky.org> <CP6P284MB19006894C8DA481BD73A3F1BCB559@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> <93745237-5a3c-b81b-36d3-3c883bc4f2d3@selasky.org> <37d15b0a-0cc1-0830-98a9-c7e19b7a7ef5@selasky.org> <CP6P284MB1900180AA335B633D2222B7CCBC69@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Jan 2023 19:58:54 -0300 (-03) Ivan Quitschal <tezeka@hotmail.com> wrote: > On Tue, 27 Sep 2022, Hans Petter Selasky wrote: > > > > > FYI: There is some experimental thunderbolt support at: > > > > https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgi= thub.com%2Fhselasky%2Fusb4&data=3D05%7C01%7C%7C14c86eee9f5d492c41d508d= aa0b49bdb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637998994857157968%= 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW= wiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3D%2FOnIO3esoAmi1FSPkHRYpHCHkcN= 6U2rO9WhaimdaVbk%3D&reserved=3D0 > > > > But I'm not sure if it supports the hardware you've got. > > > > --HPS > > > > > Hi Hans > > i just told you early today that the problem was solved by sticking it i= nto USB > 2.0, well i was wrong. problem came back just like before > > I see Alexander also has the same XHCI that i have here > > xhci0@pci0:0:20:0: class=3D0x0c0330 rev=3D0x20 hdr=3D0x00 vendor=3D0x80= 86 device=3D0xa0ed > subvendor=3D0x1028 subdevice=3D0x0ab0 > vendor =3D 'Intel Corporation' > device =3D 'Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller' > class =3D serial bus > subclass =3D USB > > > maybe this tiger lake support is the problem? > > > I have checked your git repository above, how could i test it here ? wha= t dirs am i supposed to copy to my /usr/src ? > > thank you > That information is in the README.md: This implements a basic kernel driver and userland tool for USB4 and Thunderbolt3. The relevant code is in the following locations: sys/dev/thunderbolt sys/modules/thunderbolt usr.sbin/tbtconfig So, you need the contents of those directories. You'll have to build a module under sys/modules/thunderbolt, which should result in a tb.ko file, which will have to be loaded using kldload. You also have to go into /usr/src/usr.sbin/tbtconfig and build that binary. There's a manpage there. It's not clear from the content of README.md whether Hans has added thunderbolt to the files under /sys/conf. =2D- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230118124521.250366ef>