[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: weired problem, systemd?



On Wednesday, August 6, 2014 8:40:02 PM UTC+5:30, Hans wrote:
> Hello list,

> I am looking for some strange problem. Please let me describe:

> I installed pulseaudio, and everything worked fine, sound was running well, 
> everything could be configured with pavucontrol. So far so well. But, 
> after reboot, sound is gone, and no more devices are seen. 

> Restarting of pulseaudio via /etc/init.d/pulseaudio restart did not work.

> However: Doing dpkg-reconfigure pulseaudio let it work again.

> I do not think, it is a problem with pulseaudio, mybe with systemd? 

> The same problem occurs with another package -> eeepc-acpi-scripts

> /etc/init.d/eeepc-acpi-scripts restart does not work, but dpkg-reconfigure 
> eeepc-acpi-scriptzs does.

> Same as in pulseaudio - it is working until next reboot.

> Do you have any clues, what is happening and what is the difference between 
> dpkg-reconfigure and /etc/init.d/* restart in relationship of starting 
> prcoesses?

I had a supposedly unrelated problem -- after an upgrade, ADSL network
connection stopped working:

https://lists.debian.org/debian-user/2014/08/msg00004.html

[Sorry cant find the start of that thread]

My conclusion was that some kernel modules (in my case pppoe and related)
that used to be loaded (modprobe-d) have stopped being auto-modprobe-d.

So you can look for a (band-aid) solution by checking what if any modules
are added by dpkg-reconfigure [diff output of lsmod before and after maybe??]


Reply to: