I'll try that. Are you able to play videos when pulseaudio is not loaded "correctly"?
There must be something wrong with the startup if it works OK during quite many boots and then suddenly stops totally.
Also I tried to compare OK boot log to Not OK boot log. There are quite lot of differences. I hope Matan can say something about that.
[EDIT]: pulseaudio in /etc/modules did'nt help. Right from 1st boot after v45 update no audio.
If I try to play any audio- or videofile error message is "Media cannot be played. Format is not supported"
really? where?
i took a look at your logs, and other than differences in the sequence of some entries, they appear to be the same.
You are right, I should have said differences in sequence. Should there be differences between bootups? Is that normal? I really don't know. V45 just won't work with my HW...
I'll try that. Are you able to play videos when pulseaudio is not loaded "correctly"?
There must be something wrong with the startup if it works OK during quite many boots and then suddenly stops totally.
Also I tried to compare OK boot log to Not OK boot log. There are quite lot of differences. I hope Matan can say something about that.
no
nothing works 4me
it always says:
unsupported media .......
i think uboot is the devil
can it be, that uboot starts to fast?
and when its to fast it drops some modules!?
is it possible to make 2 release of kernel-power?
one with uboot one with stock nolo bootloader
that would be best
but then i will miss the tux on startup and the post output like on the pc
You are right, I should have said differences in sequence. Should there be differences between bootups? Is that normal?
yes, it's normal that not every boot is the same
sometimes a device is faster or slower than usual, for whatever reason. nothing to worry about, and probably not the reason for your problems with pulseaudio... the audio device (alsa) gets initialized fine in both logs.
what does
Code:
initctl list pulseaudio
as root say? if it's listed but not running, you could try debugging the event.d script. the command
Code:
initctl start pulseaudio
starts the daemon, maybe its output will give you a clue to the error.
if "initctl list pulseaudio" comes back empty ("no jobs matching"), your event.d scripts are messed up...
good to know that it works now, although i'd rather try to determine why the FLAC symlink is incorrect or doesn't work instead of just copying the file... i still have that symlink and never had a problem...
anyhow, just remember that your rootfs just grew by 300 kB
