USB audio device not detected in Tiny Core Linux - lsusb doesn't show sound card

[G]

Hi,

**Description:**
I have a persistent issue with USB audio device not being detected in Tiny Core Linux. The device works in Windows (on dual-boot), but after Windows hibernation, Linux doesn't see it.

**System:**
- Tiny Core Linux x86
- Dual boot with Windows (hibernated)
- BIOS: American Megatrends 2.0.1205

**Symptoms:**
- `lsusb` shows only mouse and keyboard, no audio device
- `cat /proc/asound/cards` returns "no soundcards"
- ALSA modules loaded successfully (`snd_usb_audio`, `snd_hda_intel`)
- USB reset scripts don't help
- Device makes physical "click" sound when connecting

**Commands output:**

Code: [Select]

$ lsusb
Bus 002 Device 004: ID 1a2c:4c82 China Resource Semico Co., Ltd
Bus 002 Device 003: ID 0000:3825 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Code: [Select]

$ dmesg | grep -i "usb\|audio"
usbcore: registered new interface driver snd-usb-audio
usbcore: deregistering interface driver snd-usb-audio(cyclic registration/deregistration)


 I do not have dual-boot access to the original Windows installation. The Windows bootloader was damaged previously, so I cannot boot into
 Windows to check how the audio device was configured there (e.g., for exact model names or if it worked there). I am troubleshooting this solely from within Tiny Core.

thanks

[Rich]

Hi G

Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:

[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]

It will appear like this in your post:

Code: [Select]

[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.

[Rich]

Hi G
Based on your situation, I think you should first look into how to repair your Windows bootloader.
It sounds like hibernation may have disabled some hardware paths.

Just for fun, run this command:

Code: [Select]

dmesg > dmesg.txtThen attach the  dmesg.txt  file to your next post. I'm curious to see what else pops up.

[G]

Here

[G]

note:Windows is on sda1, the bootloader is accessible and sda2, the system itself is not accessible tcl on sda3, I still need Windows, it cannot be deleted and there is no access to it, as I already said, because part of the bootloader is formatted and faulty

[gadget42]

don't have any experience with windows but DDG only spit out these two results during a search for "repair windows 11 bootloader"(including quotation marks)

https://www.ubackup.com/windows-11/repair-windows-11-bootloader-3707-gc.html

https://www.weetechsolution.com/blog/how-to-repair-and-troubleshoot-windows-11-bootloader-issues

[Rich]

Hi G
I'm afraid I didn't see anything in your dmesg that looked like it might help.