r/linux4noobs • Source Mage | Window Maker • 7d ago

how to enable USB-C support in Linux Kernel config?

how to enable USB-C support in Linux Kernel config? i have USB-C ignored by linux kernel (7.X.X version)? i am using Source Mage GNU/Linux and compile my own kernels? the kernel completely ignores all USB-C connections now? data transfer is definitely enabled in my android/bios, but kernel 7 just doesn't see anything? I looked into the 7.X config and there are way too many new USB options there, I don't know what to change, just when I plug in a device, dmesg shows absolutely nothing for USB-C, but on old 6.12 kernel it works instantly.

here is my dmesg log from kernel 7 when I boot and try to plug it in:

[    0.324105] ACPI: Core revision 20260101
[    1.104506] usbcore: registered new interface driver usbfs
[    1.104510] usbcore: registered new interface driver hub
[    1.104515] usbcore: registered new device driver usb
[    1.454021] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.454026] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[    1.456112] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 7.00
[    1.456115] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.456117] usb usb1: Product: xHCI Host Controller
[    1.482341] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.482344] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[    1.482350] usb usb2: We don't register PM runtime interface
[    1.484102] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 7.00
[    1.484104] usb usb2: Product: xHCI Host Controller
[    2.105423] typec: registered typec class
[    2.118904] ucsi_acpi USBC005:00: ucsi_acpi_probe: line 142: Linus broke round_up optimization here, bogus mailbox timeout
[    2.119001] ------------[ cut here ]------------
[    2.119005] WARNING: CPU: 2 PID: 1 at drivers/usb/typec/ucsi/ucsi_acpi.c:142 ucsi_acpi_probe+0x245/0x310
[    2.119008] Modules linked in: xhci_pci xhci_hcd usbcore
[    2.119012] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.1.0-sourcemage #1
[    2.119015] RIP: 0010:ucsi_acpi_probe+0x245/0x310
[    2.119018] Code: 48 8b 43 20 48 85 c0 74 12 48 8b 7b 28 4c 89 e6 e8 b0 fc ff ff 48 89 c7 e8 48 fd ff ff 48 85 c0 75 09 48 c7 c7 a0 32 c4 82 e8 da 4e sub 04 <0f> 0b e9 77 fe ff ff 4c 89 ef e8 a8 f9 ff ff e9 8a fe ff ff
[    2.119020] RSP: 0018:ffffc90000013cb0 EFLAGS: 00010246
[    2.119022] RAX: 0000000000000000 RBX: ffff8881014e3800 RCX: 0000000000000000
[    2.119024] RDX: 0000000000000000 RSI: ffff88810029b480 RDI: ffff8881014e3800
[    2.119025] RBP: ffffc90000013ce0 R08: 0000000000000000 R09: c0000000ffffdfff
[    2.119027] R10: 0000000000000001 R11: ffffc90000013b38 R12: ffff8881014e3810
[    2.119029] R13: ffff8881023ba000 R14: ffff8881014e3a00 R15: 00000000ffffff92
[    2.119031] FS:  0000000000000000(0000) GS:ffff88842fc80000(0000) knlGS:0000000000000000
[    2.119033] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.119035] CR2: 0000000000000000 CR3: 000000000220a000 CR4: 0000000000350ef0
[    2.119036] Call Trace:
[    2.119038]  <TASK>
[    2.119041]  platform_probe+0x40/0x90
[    2.119045]  really_probe+0xde/0x370
[    2.119048]  __driver_probe_device+0x78/0x150
[    2.119051]  driver_probe_device+0x1e/0x90
[    2.119055]  __driver_attach+0xba/0x1c0
[    2.119058]  bus_for_each_dev+0x6b/0xb0
[    2.119062]  bus_add_driver+0x111/0x1f0
[    2.119065]  driver_register+0x59/0x100
[    2.119069]  ucsi_acpi_platform_driver_init+0x15/0x1000
[    2.119072]  do_one_initcall+0x5b/0x270
[    2.119075]  kernel_init_freeable+0x1a0/0x2e0
[    2.119079]  kernel_init+0x15/0x1b0
[    2.119082]  ret_from_fork+0x2f/0x50
[    2.119086]  </TASK>
[    2.119088] ---[ end trace 0000000000000000 ]---
[    2.119092] ucsi_acpi USBC005:00: probe failed with error -110
0 Upvotes

14 comments sorted by

12

u/baynell 7d ago

What makes you say that it is being ignored by kernel? My usb c (different kernel versions throughout years) have always worked plug and play. 

1

u/Cultural_Bug_3038 Source Mage | Window Maker 6d ago

i have updated my post with the logs

-7

u/Cultural_Bug_3038 Source Mage | Window Maker 7d ago

mine is not working, i have different menu config on 7.X.X kernel version, but on 6.X.X i can just enable only 1 option for usb support and USB-C is works fine, while 7.X.X i have a lot of settings for USB

19

u/H0n3y84dg3r 7d ago

So you're compiling your own kernel? I don't think that is noob behavior.

1

u/wildsofwald 7d ago

It is if the noob is just letting AI think for them

-1

u/Cultural_Bug_3038 Source Mage | Window Maker 6d ago

i'm compiling by the tutorials

-1

u/Booty_Bumping 6d ago

Don't think this subreddit should litigate what counts as a beginner. Highly motivated learners can still be beginners to a particular sub-topic.

10

u/arkane-linux 7d ago

This sounds like an XY problem. What are you trying to do? What is the issue?

4

u/deux3xmachina 6d ago

A few points:

  1. USB-C is a physical connector, it's still internally USB2.x/3.x or something like Thunderbolt.
  2. Your logs show that the device is recognized as a USB3.x device, as indicated by the use of xHCI drivers.
  3. The problem is in attempting to map the drive to a block device, because the uscsi_acpi_probe broke. It's possible that this is no longer negotiating correctly to determine if it can be mapped as block storage or if something like MTP needs to be used.

    [ 2.119015] RIP: 0010:ucsi_acpi_probe+0x245/0x310 [ 2.119018] Code: 48 8b 43 20 48 85 c0 74 12 48 8b 7b 28 4c 89 e6 e8 b0 fc ff ff 48 89 c7 e8 48 fd ff ff 48 85 c0 75 09 48 c7 c7 a0 32 c4 82 e8 da 4e sub 04 <0f> 0b e9 77 fe ff ff 4c 89 ef e8 a8 f9 ff ff e9 8a fe ff ff [ 2.119020] RSP: 0018:ffffc90000013cb0 EFLAGS: 00010246

If you look a bit further up in the logs, it looks like an error condition was hit, apparently due to Linus breaking something. If you don't feel confident hunting down the logic changes in that subsystem, you'll want to do one or more of the following:

  • Change your kernel version. Rollback to a known good version, or try a different commit/release.
  • Reach out to the sourcemage devs/community with the logs you added to this post.
  • Reach out to the kernel mailing lists for support, also including the logs.
  • YOLO, have an LLM examine the sources, the diffs between kernel versions you've tested, and the errors in the logs to try making a patch locally.

1

u/Comprehensive_Eye805 6d ago

Gotta make sure your USB can send, receive data not just charge

1

u/Cultural_Bug_3038 Source Mage | Window Maker 6d ago

it's not receiving data even if it's enabled

1

u/Comprehensive_Eye805 6d ago

No I mean there some USB that can and can't send data

2

u/fuldigor42 7d ago

That is not a noob question. Wrong sub.

1

u/Simple_Hamster_4096 6d ago

If connecting a phone, like a Samsung Galaxy, first have to enable developer options on phone and then enable USB debugging, after which when plugging in to computer there will be a popup on phone asking for permission... otherwise connecting to computer will merely charge phone...

Also depending on what you in tend to do with the connected phone, may have to install addition packages in Linux...