You are not logged in.
Hi,
I've noticed a curious behavior in my system, it seems that if I left my PC switched off for hours (more than 5 hours) and I switch it on my internal audio card (I have a Gigabyte Z170X motherboard with Realtek ALC1150) is recognized correctly but it is reported as busy. The issue disappear (almost the time that I tried) if I restart the system.
speaker-test 1.1.2
Playback device is front:PCH
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Playback open error: -16,Device or resource busy
This is the my /proc/asound/cards:
~ [ cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf540000 irq 139
1 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xdf080000 irq 17
2 [Launchpad ]: USB-Audio - Launchpad
Novation DMS Ltd Launchpad at usb-0000:00:14.0-9.4.1, low speed
3 [FaderPort ]: USB-Audio - FaderPort
PreSonus FaderPort at usb-0000:00:14.0-9.3, full speed
4 [USB ]: USB-Audio - Scarlett 2i2 USB
Focusrite Scarlett 2i2 USB at usb-0000:00:14.0-9.1, high speed
5 [U0x46d0x81b ]: USB-Audio - USB Device 0x46d:0x81b
USB Device 0x46d:0x81b at usb-0000:00:14.0-9.4.4, high speed
And this is what I have in my /etc/modprobe.d/alsa.conf in order to avoid the my USB audio card (Focusrite 2i2) is selected as default card:
options snd_hda_intel position_fix=0
options snd_usb_audio index=4
I have also tried to find something in the dmesg dump, but it seems to be ok (despite an "invalied ELD data"):
~ [ dmesg | grep snd
[ 3.818425] snd_hda_intel 0000:01:00.1: Disabling MSI
[ 3.818432] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[ 3.829821] snd_hda_codec_realtek hdaudioC0D0: ALC1150: SKU not ready 0x00000000
[ 3.830327] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1150: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[ 3.830329] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 3.830331] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[ 3.830332] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 3.830334] snd_hda_codec_realtek hdaudioC0D0: dig-out=0x11/0x1e
[ 3.830335] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 3.830337] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19
[ 3.830338] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18
[ 3.830340] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
[ 4.724431] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 1
[ 5.048237] usbcore: registered new interface driver snd-usb-audio
Any suggestion?
Thank you.
Last edited by killkrt (2016-08-30 17:34:06)
Offline
Why do you use position_fix=0? If it isn't strictly necessary you probably shouldn't use it, you should use index=0 to make it the default card. a device could also be busy because an application is blocking it, what is in you
sudo fuser -v /dev/snd/*
at that point
Offline
Hi,
So, at the moment my sound card is busy again and this is the dump that I get:
sudo fuser -v /dev/snd/*
USER PID ACCESS COMMAND
/dev/snd/controlC0: root 355 F.... timidity
/dev/snd/controlC1: killkrt 683 F.... pulseaudio
/dev/snd/controlC4: killkrt 683 F.... pulseaudio
/dev/snd/controlC5: killkrt 683 F.... pulseaudio
/dev/snd/pcmC0D0p: root 355 F...m timidity
/dev/snd/seq: root 355 F.... timidity
/dev/snd/timer: root 355 f.... timidity
P.S.:
I have already replaced position_fix with position as @V1del suggested me.
Offline
Same situation today...
USER PID ACCESS COMMAND
/dev/snd/controlC0: root 349 F.... timidity
/dev/snd/controlC1: killkrt 602 F.... pulseaudio
/dev/snd/controlC4: killkrt 602 F.... pulseaudio
/dev/snd/controlC5: killkrt 602 F.... pulseaudio
/dev/snd/pcmC0D0p: root 349 F...m timidity
/dev/snd/pcmC1D7p: killkrt 602 F...m pulseaudio
/dev/snd/seq: root 349 F.... timidity
/dev/snd/timer: root 349 f.... timidity
And this are the process 349 and 602:
root 349 0.0 0.1 168684 19444 ? SLs 10:17 0:00 /usr/bin/timidity -iA
killkrt 602 0.1 0.0 836020 12448 ? S<sl 10:17 0:00 /usr/bin/pulseaudio --daemonize=no
Offline
Disable the timidity service, set it up as an user service and make it point to your default ALSA device to have it cooperate with pulseaudio. Alternatively you could use fluidsynth which has native pulseaudio support, but even this you should set up as an user service instead of the system wide one
Offline
Thank you for your reply.
So I disabled the system timidity service and made a copy in my ~/.config/systemd/user/ and enabled it using:
systemctl --user enable timidity.service
But I got this error:
Failed to connect to bus: No such file or directory
I have already tried to google about, and it seems that it could be due to a missing environment variable (XDG_RUNTIME_DIR), but in my case is set correctly.
I have one question more: how I can make it point to default ALSA devices?
That means that I have to put in my service something like this:
ExecStart=/usr/bin/timidity -iA -Os
Or maybe I have to use the -Od option?
Thank you.
Last edited by killkrt (2016-08-28 17:46:31)
Offline
Provided you have installed pulseaudio-alsa and aren't using any other conflicting configuration , the line as you posted should work. However the error message suggests your user session is broken, how do you log in? What do
loginctl session-status
loginctl show-session
give as output.
Offline
So these are the outputs that you requested:
loginctl session-status
Could not get properties: No such device or address
loginctl show-session
EnableWallMessages=no
NAutoVTs=6
KillUserProcesses=no
RebootToFirmwareSetup=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key
DelayInhibited=sleep
InhibitDelayMaxUSec=5s
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
HandleLidSwitchDocked=ignore
HoldoffTimeoutUSec=30s
IdleAction=ignore
IdleActionUSec=30min
PreparingForShutdown=no
PreparingForSleep=no
Docked=no
RemoveIPC=yes
RuntimeDirectorySize=1676959744
InhibitorsMax=8192
NCurrentInhibitors=3
SessionsMax=8192
NCurrentSessions=1
UserTasksMax=10813
Please note that yesterday when I made a pacman update I have been asked to replace the libdbus with core/dbus and I answered yes since I read it was safe, I don't know if it could be related, but maybe it's worth to be mentioned.
Thank you again for your support!
Offline
Please remove [?] from your title.
Last edited by alex.theoto (2016-08-30 17:27:29)
Offline
You don't have a proper session, how do you login? Are you using an unmaintained displaymanager like SLiM by any chance?
Offline
I am using LXDM and my session file (in /etc/lxdm/lxdm.conf) seems to be ok, it's just the default file where I've changed the session variable in order to point to /usr/bin/budgie-desktop.
Offline