4 Aug
2016
4 Aug
'16
6:06 a.m.
I've had some sound problems in MX-15 with VLC and Trinity. The issue
is solved... sort of.
This is a link to the discussion:
http://forum.mepiscommunity.org/viewtopic.php?f=100&t=40197
The short version is:
After I installed KDE Plasma Desktop, the problems cleared up.
Recently, they started again. If I log out of TDE, log into Plasma
Desktop, log out of Plasma, then back into TDE, I have sound again in VLC.
4 Aug
4 Aug
12:56 p.m.
New subject: [trinity-users] MX-15 sound loss in VLC
On Thursday 04 August 2016 02:06:27 Joe wrote:
I've had some sound problems in MX-15 with VLC and
Trinity. The issue
is solved... sort of.
This is a link to the discussion:
http://forum.mepiscommunity.org/viewtopic.php?f=100&t=40197
The short version is:
After I installed KDE Plasma Desktop, the problems cleared up.
Recently, they started again. If I log out of TDE, log into Plasma
Desktop, log out of Plasma, then back into TDE, I have sound again in
VLC.
Maybe this is a good time to add to the confusion. Something in the
environment as tdm is starting shuts off the sound, and it is 100%
repeatable here, running R14.0.4. And despite my best efforts at adding
the fix it command to stuff that either runs as root by init, (rcS) or
as me when I log in, sound is deader than a nail until I find a terminal
and type in the fix it: alsactl restore.
This has existed as a bootup problem for at least a year. I hear the big
thump in the speakers as the driver is loaded way back in the text only
portion of the reboot, which I see because I am an anacronism and always
have a no-splash on the kernel's load line in grub.conf. That thump
tells me the sound should work, so what is it in the tdm load time frame
that mutes it?
Whatever it should be found & killed. With no regrets. SSS theory.
Thanks.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
8:34 p.m.
New subject: [trinity-users] MX-15 sound loss in VLC
On 08/04/2016 08:56 AM, Gene Heskett wrote:
On Thursday 04 August 2016 02:06:27 Joe wrote:
--
Gene,
I'm cross-posting your reply to my thread in the MX-15 Modified forum so
they will know that this is not exclusively a Trinity on MX-15 problem.
Thanks,
-Joe
I've had some sound problems in MX-15 with
VLC and Trinity. The issue
is solved... sort of.
This is a link to the discussion:
http://forum.mepiscommunity.org/viewtopic.php?f=100&t=40197
The short version is:
After I installed KDE Plasma Desktop, the problems cleared up.
Recently, they started again. If I log out of TDE, log into Plasma
Desktop, log out of Plasma, then back into TDE, I have sound again in
VLC.
Maybe this is a good time to add to the confusion. Something in the
environment as tdm is starting shuts off the sound, and it is 100%
repeatable here, running R14.0.4. And despite my best efforts at adding
the fix it command to stuff that either runs as root by init, (rcS) or
as me when I log in, sound is deader than a nail until I find a terminal
and type in the fix it: alsactl restore.
This has existed as a bootup problem for at least a year. I hear the big
thump in the speakers as the driver is loaded way back in the text only
portion of the reboot, which I see because I am an anacronism and always
have a no-splash on the kernel's load line in grub.conf. That thump
tells me the sound should work, so what is it in the tdm load time frame
that mutes it?
Whatever it should be found & killed. With no regrets. SSS theory.
Thanks.
Cheers, Gene Heskett
5 Aug
5 Aug
12:54 a.m.
New subject: [trinity-users] MX-15 sound loss in VLC
On Thursday 04 August 2016 16:34:57 Joe wrote:
On 08/04/2016 08:56 AM, Gene Heskett wrote:
> On Thursday 04 August 2016 02:06:27 Joe wrote:
>> I've had some sound problems in MX-15 with VLC and Trinity. The
>> issue is solved... sort of.
>>
>> This is a link to the discussion:
>>
>> http://forum.mepiscommunity.org/viewtopic.php?f=100&t=40197
>>
>> The short version is:
>> After I installed KDE Plasma Desktop, the problems cleared up.
>> Recently, they started again. If I log out of TDE, log into Plasma
>> Desktop, log out of Plasma, then back into TDE, I have sound again
>> in VLC.
>
> Maybe this is a good time to add to the confusion. Something in the
> environment as tdm is starting shuts off the sound, and it is 100%
> repeatable here, running R14.0.4. And despite my best efforts at
> adding the fix it command to stuff that either runs as root by init,
> (rcS) or as me when I log in, sound is deader than a nail until I
> find a terminal and type in the fix it: alsactl restore.
>
> This has existed as a bootup problem for at least a year. I hear
> the big thump in the speakers as the driver is loaded way back in
> the text only portion of the reboot, which I see because I am an
> anacronism and always have a no-splash on the kernel's load line in
> grub.conf. That thump tells me the sound should work, so what is it
> in the tdm load time frame that mutes it?
>
> Whatever it should be found & killed. With no regrets. SSS theory.
>
> Thanks.
>
> Cheers, Gene Heskett
Joe, please don't put your reply below anybody's sig disconnecter. You
did, and that means I have to copy & paste from your message to this
one. The sig disconnect is a newline,dash,dash,space,newline and no
email agent I know of fails to honor it unless its some winders thing.
Now I'll copy and paste:
Gene,
I'm cross-posting your reply to my thread in the MX-15 Modified forum so
they will know that this is not exclusively a Trinity on MX-15 problem.
Thanks,
-Joe
I never for a millsecond thought it was an MX-15 problem. I've had an
aftermarket card it did it to, and it does it to the motherboard audio
system on this now elderly Asus motherboard. Post away, as I see no
reason to launch a machine code trace on your MX-15, whatever that is.
As for trinity, ISTR I also had problems with kde doing the same thing
before I jerked it out by its hair and put trinity in. And I have lost a
lot less blood annually with trinity than I have with kde for the last 6
or 7 years. I like stability.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
1:07 a.m.
New subject: [trinity-users] MX-15 sound loss in VLC
Gene Heskett composed on 2016-08-04 20:54 (UTC-0400):
MX-15, whatever that is.
It's a somewhat confusingly named Debian and Mepis derived lightweight Linux
distro directed at older computers. See:
http://antix.mepis.org/index.php?title=Main_Page
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
1:35 a.m.
New subject: [trinity-users] MX-15 sound loss in VLC
On Thursday 04 August 2016 21:07:51 Felix Miata wrote:
Gene Heskett composed on 2016-08-04 20:54 (UTC-0400):
Humm, downright purty. But it looks like x is actually well supported
unless thats a wayland preview.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
MX-15, whatever that is.
It's a somewhat confusingly named Debian and Mepis derived lightweight
Linux distro directed at older computers. See:
http://antix.mepis.org/index.php?title=Main_Page 
12:58 a.m.
Gene Heskett wrote:
and type in the fix it: alsactl restore.
perhaps try alsactl store ? It helps.
No issue here with the sound and never had, though this problem was visible
from time to time during the years on different machines after upgrades,
migration to new hardware etc etc. Storing the settings solves it.
This should be called on shutdown/reboot as well same as restore on boot by
the init script AFAIR.
I am not sure if TDE saves the state. My impression is it reads the state
from alsa.
regards
1:24 a.m.
New subject: [trinity-users] Re: MX-15 sound loss in VLC
On Thursday 04 August 2016 20:58:50 deloptes wrote:
Gene Heskett wrote:
Only if you have called up the alsoctl.gui and made it functional.
No use storing defective settings into your home dir.
and type in the fix it: alsactl restore.
perhaps try alsactl store ? It helps. No issue here with the sound and never had, though
this problem was
visible from time to time during the years on different machines after
upgrades, migration to new hardware etc etc. Storing the settings
solves it. This should be called on shutdown/reboot as well same as
restore on boot by the init script AFAIR.
I am not sure if TDE saves the state. My impression is it reads the
state from alsa.
In which case it is reading a defective file in /root since the shutdowen
and init stuff runs as root, whereas if I run the restore from a
terminal, as me, then it reads a good file from my home dir, one that I
previously saved after calling up the gui as me and making it work.
regards
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
9:18 a.m.
Gene Heskett wrote:
On Thursday 04 August 2016 20:58:50 deloptes wrote:
It is neither in user dir not in root dir. It is saved in
/var/lib/alsa/asound.state
regards
Gene Heskett wrote:
Only if you have called up the alsoctl.gui and made it functional.
No use storing defective settings into your home dir.
and type in the fix it: alsactl restore.
perhaps try alsactl store ? It helps. No issue here with the sound and never had,
though this problem was
visible from time to time during the years on different machines after
upgrades, migration to new hardware etc etc. Storing the settings
solves it. This should be called on shutdown/reboot as well same as
restore on boot by the init script AFAIR.
I am not sure if TDE saves the state. My impression is it reads the
state from alsa.
In which case it is reading a defective file in /root since the shutdowen
and init stuff runs as root, whereas if I run the restore from a
terminal, as me, then it reads a good file from my home dir, one that I
previously saved after calling up the gui as me and making it work.
11:02 a.m.
New subject: [trinity-users] Re: Re: MX-15 sound loss in VLC
On Friday 05 August 2016 05:18:10 deloptes wrote:
Gene Heskett wrote:
So it is. Owned by root but world rw. Then why, if root can access it
during the init phase, is it not active for me until I do an alsactl
restore ? Something in starting the x stuff as the usr after the login,
is killing the sound UNTIL the user does a restore. And its a right
PIMA. Just for S & G, I just added an aplay command to be executed by
me, immediately after a line in rc.local that does a theoretical
restore, as me to play the front-center channel id file. I'll see if
that plays when I next reboot. Which is not eminent ATM.
On Thursday 04 August 2016 20:58:50 deloptes
wrote:
It is neither in user dir not in root dir. It is saved in
/var/lib/alsa/asound.state Gene Heskett wrote:
Only if you have called up the alsoctl.gui and made it functional.
No use storing defective settings into your home dir.
and type in the fix it: alsactl restore.
perhaps try alsactl store ? It helps. No issue here with the sound and never had,
though this problem was
visible from time to time during the years on different machines
after upgrades, migration to new hardware etc etc. Storing the
settings solves it. This should be called on shutdown/reboot as
well same as restore on boot by the init script AFAIR.
I am not sure if TDE saves the state. My impression is it reads the
state from alsa.
In which case it is reading a defective file in /root since the
shutdowen and init stuff runs as root, whereas if I run the restore
from a terminal, as me, then it reads a good file from my home dir,
one that I previously saved after calling up the gui as me and
making it work. regards
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
11:12 a.m.
New subject: [trinity-users] Re: Re: MX-15 sound loss in VLC
Am Freitag, 5. August 2016 schrieb Gene Heskett:
On Friday 05 August 2016 05:18:10 deloptes wrote:
Hi Gene!
I have none of these issuse, but I have banned systemd from all linuxcnc-boxes.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
Gene Heskett wrote:
So it is. Owned by root but world rw. Then why, if root can access it
during the init phase, is it not active for me until I do an alsactl
restore ? Something in starting the x stuff as the usr after the login,
is killing the sound UNTIL the user does a restore. And its a right
PIMA. Just for S & G, I just added an aplay command to be executed by
me, immediately after a line in rc.local that does a theoretical
restore, as me to play the front-center channel id file. I'll see if
that plays when I next reboot. Which is not eminent ATM.
On Thursday 04 August 2016 20:58:50 deloptes
wrote:
It is neither in user dir not in root dir. It is saved in
/var/lib/alsa/asound.state Gene Heskett wrote:
> and type in the fix it: alsactl restore.
perhaps try alsactl store ? It helps.
Only if you have called up the alsoctl.gui and made it functional.
No use storing defective settings into your home dir.
No issue here with the sound and never had,
though this problem was
visible from time to time during the years on different machines
after upgrades, migration to new hardware etc etc. Storing the
settings solves it. This should be called on shutdown/reboot as
well same as restore on boot by the init script AFAIR.
I am not sure if TDE saves the state. My impression is it reads the
state from alsa.
In which case it is reading a defective file in /root since the
shutdowen and init stuff runs as root, whereas if I run the restore
from a terminal, as me, then it reads a good file from my home dir,
one that I previously saved after calling up the gui as me and
making it work. regards
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
4:07 p.m.
New subject: [trinity-users] Re: Re: MX-15 sound loss in VLC
On Friday 05 August 2016 07:12:40 Dr. Nikolaus Klepp wrote:
[snip]
Hi Gene!
I have none of these issuse, but I have banned systemd from all
linuxcnc-boxes.
Nik
Hi Nik;
I'm still on wheezy for all 4, going on 5 machines. Is there some hidden
systemd stuff I haven't stumbled over yet?
Yeah, I see a tree of stuff in /etc/systemd/system, but none of that
looks like it would effect alsa. But there is dbus stuff, and I use that
facility heavily on this machine.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
12:35 p.m.
Gene Heskett wrote:
So it is. Owned by root but world rw. Then why, if
root can access it
during the init phase, is it not active for me until I do an alsactl
restore ? Something in starting the x stuff as the usr after the login,
is killing the sound UNTIL the user does a restore. And its a right
PIMA. Just for S & G, I just added an aplay command to be executed by
me, immediately after a line in rc.local that does a theoretical
restore, as me to play the front-center channel id file. I'll see if
that plays when I next reboot. Which is not eminent ATM.
In my opinion the problem is somewhere else. This file is not meant to be
used by user. It is used when alsa framework is initialized. When you do
restore you actually load the settings from this file.
The question is why it is not restoring on boot. You should inspect the
scripts used to start/initialize alsa.
I can't look further ATM. I would actually trace the log files, but the
approach with playing something is also valid, only it will not help
understand why if not working.
BTW I don't have anything in rc.local. I have (jessie)
find /etc/rc* | grep alsa
/etc/rc0.d/K01alsa-utils
/etc/rc6.d/K01alsa-utils
/etc/rcS.d/S21alsa-utils
regards
4:28 p.m.
New subject: [trinity-users] Re: Re: Re: MX-15 sound loss in VLC
On Friday 05 August 2016 08:35:52 deloptes wrote:
Gene Heskett wrote:
Looking at S21alsa-utils, it seems to me that I should see a log msg or
30 from it. I am not, but its appears to mute the system at one point
in the script. WTH is that for? What I see in the last dmesg all comes
from snd_intel, and says that msi has been disabled, whatever the heck
that means. I'm clueless about that.
Thanks.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
So it is. Owned by root but world rw. Then why,
if root can access
it during the init phase, is it not active for me until I do an
alsactl restore ? Something in starting the x stuff as the usr
after the login, is killing the sound UNTIL the user does a restore.
And its a right PIMA. Just for S & G, I just added an aplay command
to be executed by me, immediately after a line in rc.local that does
a theoretical restore, as me to play the front-center channel id
file. I'll see if that plays when I next reboot. Which is not
eminent ATM.
In my opinion the problem is somewhere else. This file is not meant to
be used by user. It is used when alsa framework is initialized. When
you do restore you actually load the settings from this file.
The question is why it is not restoring on boot. You should inspect
the scripts used to start/initialize alsa.
I can't look further ATM. I would actually trace the log files, but
the approach with playing something is also valid, only it will not
help understand why if not working.
BTW I don't have anything in rc.local. I have (jessie)
find /etc/rc* | grep alsa
/etc/rc0.d/K01alsa-utils
/etc/rc6.d/K01alsa-utils
/etc/rcS.d/S21alsa-utils
regards
8:33 p.m.
Gene Heskett wrote:
On Friday 05 August 2016 08:35:52 deloptes wrote:
Hi Gene,
and what happens if you do a /etc/init.d/alsa-utils restart instead of
calling directly alsactl?
this is just an idea for your next reboot.
In fact it is worth reading
/usr/share/doc/alsa-utils/README.Debian
There are some very good ideas where your problem might be.
You could also remove ">/dev/null" from the script and see if alsactl gives
something back
if MSG="$(alsactl -E HOME="$ALSACTLHOME" restore $CARD 2>&1
Gene Heskett wrote:
Looking at S21alsa-utils, it seems to me that I should see a log msg or
30 from it. I am not, but its appears to mute the system at one point
in the script. WTH is that for? What I see in the last dmesg all comes
from snd_intel, and says that msi has been disabled, whatever the heck
that means. I'm clueless about that.
Thanks.
Cheers, Gene Heskett So it is. Owned by root but world rw. Then why,
if root can access
it during the init phase, is it not active for me until I do an
alsactl restore ? Something in starting the x stuff as the usr
after the login, is killing the sound UNTIL the user does a restore.
And its a right PIMA. Just for S & G, I just added an aplay command
to be executed by me, immediately after a line in rc.local that does
a theoretical restore, as me to play the front-center channel id
file. I'll see if that plays when I next reboot. Which is not
eminent ATM.
In my opinion the problem is somewhere else. This file is not meant to
be used by user. It is used when alsa framework is initialized. When
you do restore you actually load the settings from this file.
The question is why it is not restoring on boot. You should inspect
the scripts used to start/initialize alsa.
I can't look further ATM. I would actually trace the log files, but
the approach with playing something is also valid, only it will not
help understand why if not working.
BTW I don't have anything in rc.local. I have (jessie)
find /etc/rc* | grep alsa
/etc/rc0.d/K01alsa-utils
/etc/rc6.d/K01alsa-utils
/etc/rcS.d/S21alsa-utils
regards
/dev/null)" && [ ! "$MSG" ] ;
then
return 0
else
# Retry with the "force" option. This restores more levels
# but it results in much longer error messages.
alsactl -F restore $CARD >/dev/null 2>&1
log_action_cont_msg "warning: 'alsactl -E
HOME="$ALSACTLHOME" restore${CARD:+ $CARD}' failed with error
message '$MSG'"
return 1
fi
and further down there is a function mute_and_zero_levels, but is commented
out.
Check on your side somewhere there.
store_levels "$TARGET_CARD" || EXITSTATUS=1
#mute_and_zero_levels "$TARGET_CARD" || EXITSTATUS=1
BTW MSI stands for Message Signaled Interrupt (there is a driver handling
this)
https://www.kernel.org/doc/Documentation/PCI/MSI-HOWTO.txt
I hope this helps
6 Aug
6 Aug
1:23 a.m.
New subject: [trinity-users] Re: Re: Re: Re: MX-15 sound loss in VLC
On Friday 05 August 2016 16:33:40 deloptes wrote:
Gene Heskett wrote:
It still works after the restart.
On Friday 05 August 2016 08:35:52 deloptes
wrote:
Hi Gene,
and what happens if you do a /etc/init.d/alsa-utils restart instead of
calling directly alsactl?
this is just an idea for your next reboot.
Gene Heskett wrote:
Looking at S21alsa-utils, it seems to me that I should see a log msg
or 30 from it. I am not, but its appears to mute the system at one
point in the script. WTH is that for? What I see in the last dmesg
all comes from snd_intel, and says that msi has been disabled,
whatever the heck that means. I'm clueless about that.
Thanks.
Cheers, Gene Heskett So it is. Owned by root but world rw. Then why,
if root can
access it during the init phase, is it not active for me until I
do an alsactl restore ? Something in starting the x stuff as the
usr after the login, is killing the sound UNTIL the user does a
restore. And its a right PIMA. Just for S & G, I just added an
aplay command to be executed by me, immediately after a line in
rc.local that does a theoretical restore, as me to play the
front-center channel id file. I'll see if that plays when I next
reboot. Which is not eminent ATM.
In my opinion the problem is somewhere else. This file is not meant
to be used by user. It is used when alsa framework is initialized.
When you do restore you actually load the settings from this file.
The question is why it is not restoring on boot. You should inspect
the scripts used to start/initialize alsa.
I can't look further ATM. I would actually trace the log files, but
the approach with playing something is also valid, only it will not
help understand why if not working.
BTW I don't have anything in rc.local. I have (jessie)
find /etc/rc* | grep alsa
/etc/rc0.d/K01alsa-utils
/etc/rc6.d/K01alsa-utils
/etc/rcS.d/S21alsa-utils
regards In fact it is worth reading
/usr/share/doc/alsa-utils/README.Debian
There are some very good ideas where your problem might be.
You could also remove ">/dev/null" from the script and see if alsactl
gives something back
if MSG="$(alsactl -E HOME="$ALSACTLHOME" restore $CARD
2>&1
It might well, when I am awake. Short night last night. Msg marked for
further reading. Thank you.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
/dev/null)" && [ ! "$MSG" ]
; then
return 0
else
# Retry with the "force" option. This restores more
levels # but it results in much longer error messages. alsactl -F
restore $CARD >/dev/null 2>&1
log_action_cont_msg "warning: 'alsactl -E
HOME="$ALSACTLHOME" restore${CARD:+ $CARD}' failed with error
message '$MSG'"
return 1
fi
and further down there is a function mute_and_zero_levels, but is
commented out.
Check on your side somewhere there.
store_levels "$TARGET_CARD" || EXITSTATUS=1
#mute_and_zero_levels "$TARGET_CARD" || EXITSTATUS=1
BTW MSI stands for Message Signaled Interrupt (there is a driver
handling this)
https://www.kernel.org/doc/Documentation/PCI/MSI-HOWTO.txt
I hope this helps
2826
days inactive
2828
days old
15 comments
5 participants
participants (5)
-
deloptes -
Dr. Nikolaus Klepp -
Felix Miata -
Gene Heskett -
Joe