Now it gets weird:
Even though the HDA Intel device is selected (the default soundcard on the motherboard), the sound is actually coming from the rubix...
I'm puzzled...
Regards,
Rody
Well, my previous message seems to have been a lucky fluke, after reboot it was no longer possible to use the usb sound card.
I tried setting the usb card as the default device system-wide by creating /etc/asound.conf, but then the tde soundserver keeps crashing every few seconds.
I tried installing pipewire but that dos not seem to make any difference and it does not seem to be used by tde?
Is tde even capable of using usb cards?
The system is on a multiboot pc with a linux mint 19 install using xfce. On that setup, the card is working without problems...
Rody
Op zaterdag 21 juni 2025, schreef Rody via tde-users:
Now it gets weird:
Even though the HDA Intel device is selected (the default soundcard on the motherboard), the sound is actually coming from the rubix...
I'm puzzled...
Regards,
Rody ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
Rody via tde-users wrote:
The system is on a multiboot pc with a linux mint 19 install using xfce. On that setup, the card is working without problems...
make sure the usb sound driver is set correctly as second device
$ cat /etc/modprobe.d/alsa-base.conf options snd_hda_intel index=0 options snd-usb-audio index=1
my experience shows that some devices get stuck if you suspend or hibernate the other OS (windows)
Op zaterdag 21 juni 2025, schreef deloptes via tde-users:
Rody via tde-users wrote:
The system is on a multiboot pc with a linux mint 19 install using xfce. On that setup, the card is working without problems...
make sure the usb sound driver is set correctly as second device
$ cat /etc/modprobe.d/alsa-base.conf options snd_hda_intel index=0 options snd-usb-audio index=1
my experience shows that some devices get stuck if you suspend or hibernate the other OS (windows)
Thanks,
I tried that, it still doesn't make a difference. Alsamixer on the other hand lets me select the correct device and combined with other alsa info it tells me that alsa does not seem to be the problem here. Kmix just doesn't want to show me the usb device somehow. This audio device (roland rubix) does not have any controls but even that does not stop mint linux from using it anyway. Maybe this usb audio device needs a special alsa configuration that ubuntu provides, but debian/devuan do not? I don't know.
Regards,
Rody
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
On Saturday 21 June 2025 13:43:31 Rody via tde-users wrote:
Is tde even capable of using usb cards?
Correct me if I am wrong, but the DE is not responsible for the sound setup, it's the system (the DE may provide tools for setting up the sound system, though).
As for the question itself, the answer is yes, I use one (StarTech.com 7.1 USB External Sound Card with SPDIF Digital Audio is its name and it is seen as a CM106 like sound device).
The sound setup is make by Pulse Audio however (MX-Linux here).
Thierry
Rody via tde-users wrote:
Is tde even capable of using usb cards?
don't use USB sound card, but have a USB webcam with mic. arecord -l **** List of CAPTURE Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: CX20642 Analog [CX20642 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 2: CX20642 Alt Analog [CX20642 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Webcam [Philips SPC 1000NC Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
you can try
pavucontrol
(debian package has same name)
On Sat, 21 Jun 2025 23:39:52 +0200 deloptes via tde-users users@trinitydesktop.org wrote:
you can try
pavucontrol
IIRC, pavucontrol is for PulseAudio, whille OP specified they were using pipewire, I think.
I'd probably try making the USB card the 0th ALSA card, blacklisting the kernel modules for all other sound hardware temporarily, and see if that solves the problem. HDMI audio can be weird and refuse to play nice with other audio hardware (had that problem with a laptop recently).
E. Liddell
E. Liddell via tde-users wrote:
IIRC, pavucontrol is for PulseAudio, whille OP specified they were using pipewire, I think.
Sorry, I missed this and wanted to ask if pipewire is installed. I don't understand why someone would need pipewire. It is always the same loop. Someone starts a project, it's getting adopted while still not fully working and when it starts working (I mean PA) there is a new project that is not fully working.
The question now is - does it work without pipewire?
On Sunday 22 June 2025 09:10:45 deloptes via tde-users wrote:
It is always the same loop. Someone starts a project, it's getting adopted while still not fully working and when it starts working (I mean PA) there is a new project that is not fully working.
This brings another question: why do people - who want a working system, not a test system - install beta grade software when there is something working available (and then complain)?
I don't oppose Wayland or pipewire (as examples), but I'll stick to X and PulseAudio (or alsa) until it's really ready (at least on systems I want to work).
There is a tendency to believe that newer is better that most of us here don't share, otherwise we probably would not be using TDE.
Thierry
Just to clarify: I tried installing pipewire to see if it makes any difference. Pipewire is installed but according to ps aux, it's not running. So a dead end there. If I can do it without pulse or pipewire, I will by default.
The current situation is however that kmix won't allow me to choose the rubix usb audio (because it isn't listed there). Mixxx on the other hand DOES use the rubix usb card/box, just like alsamixer is able to see the rubix while kmix does not.
As suggested by E. Liddell, it's possible the Nvidia hdmi audio is acting up, however I've only had such problems on MS Win systems, not on linux so far.
If installing pulse could solve this problem, I could try that. The fact is that the linux mint systems that work without problems with this rubix usb box also use pulse.
Rody
Op zondag 22 juni 2025, schreef Thierry de Coulon via tde-users:
On Sunday 22 June 2025 09:10:45 deloptes via tde-users wrote:
It is always the same loop. Someone starts a project, it's getting adopted while still not fully working and when it starts working (I mean PA) there is a new project that is not fully working.
This brings another question: why do people - who want a working system, not a test system - install beta grade software when there is something working available (and then complain)?
I don't oppose Wayland or pipewire (as examples), but I'll stick to X and PulseAudio (or alsa) until it's really ready (at least on systems I want to work).
There is a tendency to believe that newer is better that most of us here don't share, otherwise we probably would not be using TDE.
Thierry ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
Rody via tde-users wrote:
If installing pulse could solve this problem, I could try that. The fact is that the linux mint systems that work without problems with this rubix usb box also use pulse.
Install pulseaudio and pavucontrol and report back.
KMix is reading the system devices (AFAIK), so it must be something down the system path that is preventing kmix to list the device It could be also that a patch is needed in kmix for some reason, but we do not have any details.
On 6/22/25 13:05, deloptes via tde-users wrote:
Rody via tde-users wrote: [...] Install pulseaudio and pavucontrol and report back.
KMix is reading the system devices (AFAIK), so it must be something down the system path that is preventing kmix to list the device It could be also that a patch is needed in kmix for some reason, but we do not have any details.
And those details seem to be so well hidden from us users that we have NDI how/what to troubleshoot when it doesn't work. Why the secrecy? straces output is so copious that many can't find (or recognize) the error when we do use it. Please, give us the tools.
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto... .
Cheers, Gene Heskett, CET.
gene heskett via tde-users wrote:
Hi Gene, I'm glad to see you here again, hopefully still in good health, respectively good for your age.
And those details seem to be so well hidden from us users that we have NDI how/what to troubleshoot when it doesn't work. Why the secrecy? straces output is so copious that many can't find (or recognize) the error when we do use it. Please, give us the tools.
I guess it is because no one cares. It is something I dislike in FOSS. Especially in the early years when KDE3 was developed there were no standards for documenting, design and requirements. It is hard to find out what developers were doing. It is amazing that it actually works especially compared to modern software, it works sometimes even better :-)
On 6/22/25 16:01, deloptes via tde-users wrote:
gene heskett via tde-users wrote:
Hi Gene, I'm glad to see you here again, hopefully still in good health, respectively good for your age.
And I wish the same for you. Although I don't recall, if its even been told, the diff in the length of our trails thru this thing called time.
I think I'm doing fairly good although long term health problem abound, as they do for most at my age of 90. Sugar=heart attacks and pacemakers, and back damage dating back to my 20's are the main problems. My 3rd squeeze, a school teacher, I had for 31yrs passed nearly 5 years ago so I'm sick of my own cooking. My machining is more wood than metal these days and I discovered 3d printers about 7 years ago, so have rebuilt some of them to be 10x faster and much more capable of hi temp plastics than OOTB. I design stuff in OpenSCAD for them. Out of the 11 kids I either married or fathered, I still have 4 boys, 3 are well established, the rest were CP or MD which cuts life short. MD children made it to about 30. I made 2 girls that have passed from the big C. Dee left me her 403 so money isn't a problem. Real Estate is paid in full 20+ years ago.
Whats going on with you? All good I hope.
Cheers, Gene Heskett, CET.
Rody via tde-users wrote:
The current situation is however that kmix won't allow me to choose the rubix usb audio (because it isn't listed there). Mixxx on the other hand DOES use the rubix usb card/box, just like alsamixer is able to see the rubix while kmix does not.
Can you answer two questions
1. is the USB snd card plugged in when you boot into TDE? (and windows or whatever other system was not hibernated)
2. What is the content of /dev/snd/
for example here it is
# find /dev/snd/ /dev/snd/ /dev/snd/by-id /dev/snd/by-id/usb-Philips_CE_Philips_SPC_1000NC_Webcam-02 /dev/snd/by-path /dev/snd/by-path/pci-0000:00:1a.0-usb-0:1.5:1.2 /dev/snd/by-path/pci-0000:00:1b.0 /dev/snd/controlC1 /dev/snd/pcmC1D0c /dev/snd/controlC0 /dev/snd/hwC0D3 /dev/snd/hwC0D2 /dev/snd/pcmC0D8p /dev/snd/pcmC0D7p /dev/snd/pcmC0D3p /dev/snd/pcmC0D2c /dev/snd/pcmC0D0c /dev/snd/pcmC0D0p /dev/snd/seq /dev/snd/timer
Dne ne 22. června 2025 22:00:59 deloptes via tde-users napsal(a):
Rody via tde-users wrote:
The current situation is however that kmix won't allow me to choose the rubix usb audio (because it isn't listed there). Mixxx on the other hand DOES use the rubix usb card/box, just like alsamixer is able to see the rubix while kmix does not.
Can you answer two questions
- is the USB snd card plugged in when you boot into TDE? (and windows
or whatever other system was not hibernated)
- What is the content of /dev/snd/
for example here it is
# find /dev/snd/ /dev/snd/ /dev/snd/by-id /dev/snd/by-id/usb-Philips_CE_Philips_SPC_1000NC_Webcam-02 /dev/snd/by-path /dev/snd/by-path/pci-0000:00:1a.0-usb-0:1.5:1.2 /dev/snd/by-path/pci-0000:00:1b.0 /dev/snd/controlC1 /dev/snd/pcmC1D0c /dev/snd/controlC0 /dev/snd/hwC0D3 /dev/snd/hwC0D2 /dev/snd/pcmC0D8p /dev/snd/pcmC0D7p /dev/snd/pcmC0D3p /dev/snd/pcmC0D2c /dev/snd/pcmC0D0c /dev/snd/pcmC0D0p /dev/snd/seq /dev/snd/timer
Note 1. is very important. Currently kmix does not track changes in sound cards. So if the usb card is not present when kmix starts, it will not notice it afterwards. You need to quit kmix and start it again manually.
Cheers Slávek --
Op zondag 22 juni 2025, schreef deloptes via tde-users:
Rody via tde-users wrote:
The current situation is however that kmix won't allow me to choose the rubix usb audio (because it isn't listed there). Mixxx on the other hand DOES use the rubix usb card/box, just like alsamixer is able to see the rubix while kmix does not.
Can you answer two questions
- is the USB snd card plugged in when you boot into TDE? (and windows or
whatever other system was not hibernated)
The usb sound card (roland rubix) is always plugged in. I reserve 1 pc for my weekly radio stream using mixxx, although any linux pc with mixxx installed can take over in case of trouble (which has never happened in 5 years) thanks to the universal nfs paths to my music library.
I never use sleep or hibernate (on linux), I only use the screensaver and the blankscreen that comes after it, just like I did 20 years ago. And windows is never left running as it requires a reboot to start linux via grub.
- What is the content of /dev/snd/
for example here it is
# find /dev/snd/ /dev/snd/ /dev/snd/by-id /dev/snd/by-id/usb-Philips_CE_Philips_SPC_1000NC_Webcam-02 /dev/snd/by-path /dev/snd/by-path/pci-0000:00:1a.0-usb-0:1.5:1.2 /dev/snd/by-path/pci-0000:00:1b.0 /dev/snd/controlC1 /dev/snd/pcmC1D0c /dev/snd/controlC0 /dev/snd/hwC0D3 /dev/snd/hwC0D2 /dev/snd/pcmC0D8p /dev/snd/pcmC0D7p /dev/snd/pcmC0D3p /dev/snd/pcmC0D2c /dev/snd/pcmC0D0c /dev/snd/pcmC0D0p /dev/snd/seq /dev/snd/timer
Here's mine:
find /dev/snd
/dev/snd /dev/snd/by-path /dev/snd/by-path/pci-0000:00:1b.0 /dev/snd/by-path/pci-0000:01:00.1 /dev/snd/by-path/pci-0000:00:1a.0-usb-0:1.5:1.0 /dev/snd/by-id /dev/snd/by-id/usb-Roland_Rubix24-00 /dev/snd/controlC1 /dev/snd/hwC1D0 /dev/snd/pcmC1D2c /dev/snd/pcmC1D0c /dev/snd/pcmC1D0p /dev/snd/controlC2 /dev/snd/hwC2D0 /dev/snd/pcmC2D9p /dev/snd/pcmC2D8p /dev/snd/pcmC2D7p /dev/snd/pcmC2D3p /dev/snd/controlC0 /dev/snd/midiC0D0 /dev/snd/pcmC0D0c /dev/snd/pcmC0D0p /dev/snd/seq /dev/snd/timer
This looks ok to me but maybe I'm missing something?
Regards,
Rody
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
Anno domini 2025 Mon, 23 Jun 12:01:38 +0200 Rody via tde-users scripsit:
Op zondag 22 juni 2025, schreef deloptes via tde-users:
Rody via tde-users wrote:
The current situation is however that kmix won't allow me to choose the rubix usb audio (because it isn't listed there). Mixxx on the other hand DOES use the rubix usb card/box, just like alsamixer is able to see the rubix while kmix does not.
Can you answer two questions
- is the USB snd card plugged in when you boot into TDE? (and windows or
whatever other system was not hibernated)
The usb sound card (roland rubix) is always plugged in. I reserve 1 pc for my weekly radio stream using mixxx, although any linux pc with mixxx installed can take over in case of trouble (which has never happened in 5 years) thanks to the universal nfs paths to my music library.
I never use sleep or hibernate (on linux), I only use the screensaver and the blankscreen that comes after it, just like I did 20 years ago. And windows is never left running as it requires a reboot to start linux via grub.
It might be that your soundcard comes up after kmix is started. As kmix does not update its list of soundcards you wnd up with a list withoute the "late" soundcards. So, could you restart kmix after you have confirmed that alsamixer sees the card? If the kmix then sees the card you'd need just a little udev hacking, if not ...
Nik
- What is the content of /dev/snd/
for example here it is
# find /dev/snd/ /dev/snd/ /dev/snd/by-id /dev/snd/by-id/usb-Philips_CE_Philips_SPC_1000NC_Webcam-02 /dev/snd/by-path /dev/snd/by-path/pci-0000:00:1a.0-usb-0:1.5:1.2 /dev/snd/by-path/pci-0000:00:1b.0 /dev/snd/controlC1 /dev/snd/pcmC1D0c /dev/snd/controlC0 /dev/snd/hwC0D3 /dev/snd/hwC0D2 /dev/snd/pcmC0D8p /dev/snd/pcmC0D7p /dev/snd/pcmC0D3p /dev/snd/pcmC0D2c /dev/snd/pcmC0D0c /dev/snd/pcmC0D0p /dev/snd/seq /dev/snd/timer
Here's mine:
find /dev/snd
/dev/snd /dev/snd/by-path /dev/snd/by-path/pci-0000:00:1b.0 /dev/snd/by-path/pci-0000:01:00.1 /dev/snd/by-path/pci-0000:00:1a.0-usb-0:1.5:1.0 /dev/snd/by-id /dev/snd/by-id/usb-Roland_Rubix24-00 /dev/snd/controlC1 /dev/snd/hwC1D0 /dev/snd/pcmC1D2c /dev/snd/pcmC1D0c /dev/snd/pcmC1D0p /dev/snd/controlC2 /dev/snd/hwC2D0 /dev/snd/pcmC2D9p /dev/snd/pcmC2D8p /dev/snd/pcmC2D7p /dev/snd/pcmC2D3p /dev/snd/controlC0 /dev/snd/midiC0D0 /dev/snd/pcmC0D0c /dev/snd/pcmC0D0p /dev/snd/seq /dev/snd/timer
This looks ok to me but maybe I'm missing something?
Regards,
Rody
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
Rody via tde-users wrote:
This looks ok to me but maybe I'm missing something?
yes, indeed it looks ok at first glance
you can enable kmix in tdedebugdialog, login again or reboot or unplug and plug the usb card again and restart kmix and see if there is something related in .xsession-errors
Sorry for the long delay, but I was hit by a nasty pain in the back and could hardly walk for several days. I'm slowly getting back on my feet now, and I can answer some of the questions left open.
Op maandag 23 juni 2025, schreef deloptes via tde-users:
Rody via tde-users wrote:
This looks ok to me but maybe I'm missing something?
yes, indeed it looks ok at first glance
you can enable kmix in tdedebugdialog, login again or reboot or unplug and plug the usb card again and restart kmix and see if there is something related in .xsession-errors
Did that but I couldn't find anything related to usb audio or kmix in .xsession-errors.
It might be that your soundcard comes up after kmix is started. As kmix does not update its list of soundcards you wnd up with a list withoute the "late" soundcards. So, could you restart kmix after you have confirmed that alsamixer sees the card? If the kmix then sees the card you'd need just a little udev hacking, if not ...
I tested if that was the case, but closing down kmix and restarting it did not make any difference.
The weird thing is that the rubix soundcard would sometimes just work after logging in although kmix would still have the HDA Intel card selected and the only other option was the HDA Nvidia. The Roland Rubix was still not listed. It's as if both the HDA Intel and the Roland Rubix (usb audio) were "fighting" for the first place in that list, but kmix never listed the roland rubix. But this scenario was very dicey, sometimes it would work, but most of the time it did not and audio came from the HDA Intel still.
Install pulseaudio and pavucontrol and report back.
Did that and after a restart the Rubix card just worked. Pulse was automatically detected and selected by default by kmix and pulse had automatically selected the roland rubix. No more diceyness anymore...
KMix is reading the system devices (AFAIK), so it must be something down the system path that is preventing kmix to list the device It could be also that a patch is needed in kmix for some reason, but we do not have any details.
I would be happy to provide more details about this, just let me know what could be useful.
Regards,
Rody
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
Rody via tde-users wrote:
Did that and after a restart the Rubix card just worked. Pulse was automatically detected and selected by default by kmix and pulse had automatically selected the roland rubix. No more diceyness anymore...
So now it works after pulseaudio is properly installed?
KMix is reading the system devices (AFAIK), so it must be something down the system path that is preventing kmix to list the device It could be also that a patch is needed in kmix for some reason, but we do not have any details.
I would be happy to provide more details about this, just let me know what could be useful.
Perhaps make a screenshot or more screenshots, so that we see how it looks like in kmix now.
What I do not understand, if you see the card or not in kmix.
The attachments show what kmix looks like now that pulse is installed. For the rubix it is normal that the volumeslider is set (fixed) to 100% as the volumecontrols are on the rubix box itself.
Regards,
Rody
Op zaterdag 28 juni 2025, schreef deloptes via tde-users:
Rody via tde-users wrote:
Did that and after a restart the Rubix card just worked. Pulse was automatically detected and selected by default by kmix and pulse had automatically selected the roland rubix. No more diceyness anymore...
So now it works after pulseaudio is properly installed?
KMix is reading the system devices (AFAIK), so it must be something down the system path that is preventing kmix to list the device It could be also that a patch is needed in kmix for some reason, but we do not have any details.
I would be happy to provide more details about this, just let me know what could be useful.
Perhaps make a screenshot or more screenshots, so that we see how it looks like in kmix now.
What I do not understand, if you see the card or not in kmix.
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
Rody via tde-users wrote:
The attachments show what kmix looks like now that pulse is installed. For the rubix it is normal that the volumeslider is set (fixed) to 100% as the volumecontrols are on the rubix box itself.
Nice
so it works via pulseaudio, correct?
and when you install pavucontrol do you see the card there?
may be check the boot or system log, how it is being initialized.
I don't have usb snd card, but the usb webcam looks like this, where you also see the initialization of the snd driver
[ 12.488125] videodev: Linux video capture interface: v2.00 [ 12.528705] usb 1-1.5: Found UVC 1.00 device Philips SPC 1000NC Webcam (0471:0332) [ 12.537723] snd_hda_intel 0000:00:1b.0: enabling device (0140 -> 0142) [ 12.543947] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 12.571965] input: Philips SPC 1000NC Webcam as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input8
Op zondag 29 juni 2025, schreef deloptes via tde-users:
Rody via tde-users wrote:
The attachments show what kmix looks like now that pulse is installed. For the rubix it is normal that the volumeslider is set (fixed) to 100% as the volumecontrols are on the rubix box itself.
Nice
so it works via pulseaudio, correct?
and when you install pavucontrol do you see the card there?
Yes, see attached file
may be check the boot or system log, how it is being initialized.
I don't have usb snd card, but the usb webcam looks like this, where you also see the initialization of the snd driver
[ 12.488125] videodev: Linux video capture interface: v2.00 [ 12.528705] usb 1-1.5: Found UVC 1.00 device Philips SPC 1000NC Webcam (0471:0332) [ 12.537723] snd_hda_intel 0000:00:1b.0: enabling device (0140 -> 0142) [ 12.543947] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 12.571965] input: Philips SPC 1000NC Webcam as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input8
I found the following lines in syslog for the roland rubix audio card:
2025-06-29T02:26:24.343353+02:00 HP-63 kernel: [ 1.415894] usb 2-1: new high-speed USB device number 2 using xhci_hcd 2025-06-29T02:26:24.343381+02:00 HP-63 kernel: [ 1.564509] usb 2-1: New USB device found, idVendor=0582, idProduct=01e0, bcdDevice=11.1f 2025-06-29T02:26:24.343385+02:00 HP-63 kernel: [ 1.564515] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 2025-06-29T02:26:24.343386+02:00 HP-63 kernel: [ 1.564517] usb 2-1: Product: Rubix24 2025-06-29T02:26:24.343386+02:00 HP-63 kernel: [ 1.564518] usb 2-1: Manufacturer: Roland
However, no lines containing 'enabling device' are present in syslog (before and after installing nvidia driver).
Lines containing 'bound' were found for one device before installing the nvidia driver:
2025-06-20T02:05:18.674541+02:00 HP-63 kernel: [ 4.660744] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])
Afterward no lines containing 'bound' were found.
Lines containing 'input:' are found for mouse, keyboard, power button, pc speaker, nvidia card and hda intel card but not for the roland rubix usb card.
Regards,
Rody
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
Rody via tde-users wrote:
Lines containing 'bound' were found for one device before installing the nvidia driver:
2025-06-20T02:05:18.674541+02:00 HP-63 kernel: [ 4.660744] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])
I do not know the intel driver, but you can try disabling nvidea in the bios (if possible) and see what happens
Here in the logs later it looks like (conexant is the built in intel card). At the end it initializes the HDMI (also built in)
[ 12.599980] snd_hda_codec_conexant hdaudioC0D2: CX20642: BIOS auto-probing. [ 12.601848] snd_hda_codec_conexant hdaudioC0D2: autoconfig for CX20642: line_outs=1 (0x1c/0x0/0x0/0x0/0x0) type:line [ 12.601854] snd_hda_codec_conexant hdaudioC0D2: speaker_outs=1 (0x1f/0x0/0x0/0x0/0x0) [ 12.601856] snd_hda_codec_conexant hdaudioC0D2: hp_outs=1 (0x19/0x0/0x0/0x0/0x0) [ 12.601858] snd_hda_codec_conexant hdaudioC0D2: mono: mono_out=0x0 [ 12.601859] snd_hda_codec_conexant hdaudioC0D2: inputs: [ 12.601861] snd_hda_codec_conexant hdaudioC0D2: Mic=0x1a [ 12.601862] snd_hda_codec_conexant hdaudioC0D2: Line=0x1d
[ 12.620315] usb 1-1.5: [2] FU [Mic Capture Volume] ch = 1, val = 4608/7168/1 [ 12.620478] usbcore: registered new interface driver snd-usb-audio [ 12.631592] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9 [ 12.631648] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10 [ 12.631694] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11 [ 12.631731] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12 [ 12.631771] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13 [ 12.631807] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14 [ 12.631841] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15 [ 12.631874] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
-
deloptes -
Dr. Nikolaus Klepp -
E. Liddell -
gene heskett -
Rody -
Slávek Banko -
Thierry de Coulon