updated today to kernel-desktop-3.14.0-1.1.g79de0a7.x86_64 and
after running and closing down tvtime (tvtime-1.0.2-260.1.3.x86_64) the following message occurred
when trying to restart it again,
“saa7134: Device of resource busy
Cannot open capture device /dev/video0”
this problem was not noticed with the kernel-desktop-3.13 series kernels
tvtime starts ok again after reboot but the situation is the same trying a logout & login
A780GM-m1<2014Apr01><23:34><~> sudo umount /dev/video0
root’s password:
umount: /dev/video0: not mounted
A780GM-m1<2014Apr01><23:34><~>
also has no effect
is there a simple remedy? is a bug report needed?
this was also noticed with the rc8-1 kernel and KDE 4.12.3
cheers
today’s status
A780GM-m1 Kernel: 3.14.0-1.g79de0a7-desktop x86_64 (64 bit)
Desktop: KDE 4.12.4 Distro: openSUSE 13.1 (Bottle)
Mobo: ASRock model: A780GM-LE, Quad core AMD Phenom II X4 940
A780GM-m1<2014Apr01><23:34><~> sudo umount /dev/video0
root's password:
umount: /dev/video0: not mounted
A780GM-m1<2014Apr01><23:34><~>
also has no effect
That won’t work. It is a device node, not a mountable partition. You could try reloading the driver with
modprobe -r saa7134
modprobe saa7134
Is the capture device PCI-based card or a USB device?
is a bug report needed?
Perhaps, but you probably need to get a better handle on what isn’t working first.
Why do you have /etc/modprobe.conf? You should remove that.
But better post its content first to check if it’s important/necessary.
Maybe tvtime is not quitting correctly? Have a look in the process list (Ctrl+ESC in KDE) if it is still running and kill it.
It should work then again if this is the issue.
On 04/02/2014 04:26 PM, keellambert wrote:
> when it is stopped. first instance, it disappears from the process list
> and
> does not return until after its started again on reboot
>
> so its assumed tvtime is not closing down all associated processes
> correctly
> with kernel 3.14 but I’m not able to find anything which indicates this
For me, tvtime shuts down correctly. I use it hundreds of times between reboots;
however, I do not start it on boot. In addition, mine is used with a USB tuner.
I suspect a problem with the saa1734 driver in 3.14. The proper way to determine
what is causing the problem this would be to obtain the mainline kernel from the
git repo and bisect the error. If you are not willing to try this, then report
the bug on linux-kernel@vger.kernel.org and linux-media@vger.kernel.org. That
will get the attention of the developers.
BTW, there are no explicit changes to saa1734 with kernel 3.14. That makes it
seem that it was some other change that is causing the problem.