| View previous topic :: View next topic |
| Author |
Message |
musv
Advocate
Joined: 01 Dec 2002
Posts: 3337
Location: de
|
 Posted: Tue Dec 18, 2007 6:46 pm Post subject: /dev/video0 invalid argument |
 |
|
Hi,
since kernel-2.6.23 I have some trouble to get my tv-card working. It's an ordinary WinTV-PCI FM Stereo. And I guess until 2.6.23-r1 it worked perfectly.
| dmesg: | Linux video capture interface: v2.00
bttv: driver version 0.9.17 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 0000:01:08.0, irq: 5, latency: 32, mmio: 0xc8000000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00ffffdb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
tveeprom 0-0050: Hauppauge model 61344, rev D421, serial# 5088363
tveeprom 0-0050: tuner model is Philips FM1216 (idx 21, type 5)
tveeprom 0-0050: TV standards PAL(B/G) (eeprom 0x04)
tveeprom 0-0050: audio processor is MSP3415 (idx 6)
tveeprom 0-0050: has radio
bttv0: Hauppauge eeprom indicates model#61344
bttv0: tuner type=5
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: registered device radio0
bttv0: PLL: 28636363 => 35468950 .. ok |
| lspci: | 01:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
01:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) |
| la /dev/v4l/video0: | total 0
drwxr-xr-x 2 root root 100 Dec 18 17:53 .
drwxr-xr-x 12 root root 14840 Dec 18 17:55 ..
crw-rw---- 1 root video 81, 64 Dec 18 17:53 radio0
crw-rw---- 1 root video 81, 224 Dec 18 17:53 vbi0
crw-rw---- 1 root video 171, 16 Dec 18 17:53 video0 |
| cat /proc/config.gz: | CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_TVAUDIO=y
CONFIG_VIDEO_TDA7432=y
CONFIG_VIDEO_TDA9875=y
CONFIG_VIDEO_MSP3400=y
# CONFIG_VIDEO_VIVI is not set
CONFIG_VIDEO_BT848=y
CONFIG_VIDEO_SAA6588=y
|
So, everything seems fine. The card is recognized - I think - correctly. There's a device and a symlink to /dev/video0. But when I start tvtime I get the following error message:
Not a video4linux device
Cannot open capture device /dev/video0
With Kernel 2.6.23-r1 I had the same problem sometimes. I just restartet udev and it worked again. But curiously udevstart doesn't exist anymore (Version: udev-117). And reloading the udev-rules doesn't help. Any ideas? |
|
| Back to top |
|
 |
musv
Advocate
Joined: 01 Dec 2002
Posts: 3337
Location: de
|
| Posted: Sat Dec 22, 2007 9:25 am Post subject: |
|
|
| bump |
|
| Back to top |
|
|
MostAwesomeDude
Guru
Joined: 12 Aug 2007
Posts: 373
|
| Posted: Sat Dec 22, 2007 11:17 am Post subject: |
|
|
| Seems obvious, but are you a member of the video group? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54308
Location: 56N 3W
|
| Posted: Sat Dec 22, 2007 11:30 am Post subject: |
|
|
musv,
/dev/video0 should be a symbolic link to /dev/v4l/video0 created by udev.
Is the link there ?
Can you point tvtime directly to /dev/v4l/video0 ?
Some apps don't like symlinks.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
musv
Advocate
Joined: 01 Dec 2002
Posts: 3337
Location: de
|
| Posted: Sat Dec 22, 2007 11:58 am Post subject: |
|
|
| MostAwesomeDude wrote: | | Seems obvious, but are you a member of the video group? |
Yes, I'm in the video group. Also it doesn't work when I start tvtime as root.
| NeddySeagoon wrote: | | musv, /dev/video0 should be a symbolic link to /dev/v4l/video0 created by udev. Is the link there ? |
/dev/video0 is a symbolic link to /dev/v4l/video0.
| NeddySeagoon wrote: | | Can you point tvtime directly to /dev/v4l/video0? Some apps don't like symlinks. |
Yes there's an option to point tvtime directly to /dev/v4l/video0. But it doesn't work too. Same error message.
I suggest they changed something in the kernel options of the 2.6.23-kernels. Because I didn't change anything of udev or tvtime config. |
|
| Back to top |
|
|
musv
Advocate
Joined: 01 Dec 2002
Posts: 3337
Location: de
|
| Posted: Sat Dec 22, 2007 1:35 pm Post subject: |
|
|
Ok, only for going sure I tried different kernels.
Installed are:- gentoo-sources-2.6.21-r4
- 2.6.23-r1
- 2.6.23-r4
With 2.6.22 I had only problems.
In none of the 2.6.23 I can watch tv. But in 2.6.21-r4 it works completely perfect. |
|
| Back to top |
|
|
mjs222
n00b
Joined: 26 Dec 2007
Posts: 3
|
| Posted: Wed Dec 26, 2007 5:42 am Post subject: |
|
|
Anyone come up with a solution to this? I'm having the same problem after installing 2.6.23 (from 2.6.22-R6). My capture card is a saa7134, which I noticed was changed only slightly in 2.6.23. I also noticed the usual tuner messages aren't appearing anymore when the saa7133 driver is loaded...
input: saa7134 IR (V-Stream Studio TV as /class/input/input6
saa7133[0]: Huh, no eeprom present (err=-5)?
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
I'd expect to see:
tuner 0-004b: chip found @ 0x96 (saa7133[0])
tuner 0-004b: setting tuner address to 61
tuner 0-004b: type set to tda8290+75a
tuner 0-004b: setting tuner address to 61
tuner 0-004b: type set to tda8290+75a
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0 |
|
| Back to top |
|
|
mjs222
n00b
Joined: 26 Dec 2007
Posts: 3
|
| Posted: Thu Dec 27, 2007 5:06 am Post subject: |
|
|
I reconfigured and rebuilt my kernel and the "tuner" messages are showing up, but still no picture. I'm guessing the problem was unrelated.
Does anyone know how to turn on additional debugging for this? Why would /dev/video0 return invalid argument? Is there something else misconfigured? |
|
| Back to top |
|
|
mjs222
n00b
Joined: 26 Dec 2007
Posts: 3
|
| Posted: Thu Dec 27, 2007 5:42 am Post subject: |
|
|
| I take that back..I think I was onto it. With the new configuration I noticed "tuner" is now is lsmod where it wasn't before. I was definitely missing something in my new .config. Rebuilding with: make oldconfig brought in what I was missing. |
|
| Back to top |
|
|
musv
Advocate
Joined: 01 Dec 2002
Posts: 3337
Location: de
|
| Posted: Thu Feb 21, 2008 9:10 pm Post subject: |
|
|
*bump*
Also in 2.6.24 my tv card doesn't work. See my bug-report: https://bugs.gentoo.org/show_bug.cgi?id=203889
I'm nearly thinking, that they changed something in the config. So that I need to change something in the Kernel config.
Is there nobody with an old Hauppauge WinTV with the same problem? |
|
| Back to top |
|
|
musv
Advocate
Joined: 01 Dec 2002
Posts: 3337
Location: de
|
| Posted: Sun Feb 24, 2008 4:46 pm Post subject: |
|
|
Ok, it's working now again. Since 2.6.23 they changed obviously something in the driver design.
I used to compile the bttv driver directly into the kernel. Since 2.6.23 that doesn't seem to work anymore. You have to compile the bttv driver as a module.
Additionally: If the sound isn't working you probably forgot to select simple audio and msp34xx in the section of the helper chips. |
|
| Back to top |
|
|
|
Multimedia
