View previous topic :: View next topic |
Author |
Message |
foxicatko n00b
Joined: 15 Mar 2008 Posts: 14
|
Posted: Tue Mar 31, 2009 9:31 pm Post subject: udev doesn't create device files for A828 |
|
|
Hi,
I guess I'm missing something stupid here. I've got a AVerTV Hybrid Volar HX usb stick and I can't get it to work. Following some guides I noticed that udev wasn't creating /dev/dvb/* device files when I plugged the stick in but rather files like Code: | /dev/usbdev7.5_ep00
/dev/usbdev7.5_ep01
/dev/usbdev7.5_ep81
/dev/usbdev7.5_ep82 |
Following /usr/src/linux/Documentation/dvb/udev.txt I created files /etc/udev/rules.d/dvb.rules and /etc/udev/scripts/dvb.sh:
dvb.rules:
Code: |
#KERNEL=="dvb*", PROGRAM="/etc/udev/scripts/dvb.sh %k", NAME="%c"
ATTR{idVendor}=="07ca", ATTR{idProduct}=="a827", PROGRAM="/etc/udev/scripts/dvb.sh %k", NAME="%c", GROUP="video"
|
The commented-out line is was the first attempt, after which I tried to write my own rule with no luck. I'm not sure when exactly was the first rule meant to match as it seemed to execute my logging rule Code: | KERNEL=="*", PROGRAM="/root/log.sh" | after a module with a dvb* prefix had been inserted into the kernel.
dvb.sh:
Code: |
#!/bin/sh
echo `date` $1 >> /tmp/udev.txt
/bin/echo $1 | /bin/sed -e 's,dvb\([0-9]\)\.\([^0-9]*\)\([0-9]\),dvb/adapter\1/\2\3,'
|
The echo here is a notification that the rule key matches and the script is executed. It's not.
I can't see why the recommended rule nor my own rule wouldn't match. The device is correctly detected by the kernel when it's plugged in as dmesg indicates:
Code: | usb usb7: usb resume
ehci_hcd 0000:00:1d.7: resume root hub
hub 7-0:1.0: hub_resume
ehci_hcd 0000:00:1d.7: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT
hub 7-0:1.0: port 2: status 0501 change 0001
hub 7-0:1.0: state 7 ports 6 chg 0004 evt 0000
hub 7-0:1.0: port 2, status 0501, change 0000, 480 Mb/s
ehci_hcd 0000:00:1d.7: port 2 high speed
ehci_hcd 0000:00:1d.7: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 7-2: new high speed USB device using ehci_hcd and address 7
ehci_hcd 0000:00:1d.7: port 2 high speed
ehci_hcd 0000:00:1d.7: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 7-2: default language 0x0409
usb 7-2: uevent
usb 7-2: usb_probe_device
usb 7-2: configuration #1 chosen from 1 choice
usb 7-2: adding 7-2:1.0 (config #1, interface 0)
usb 7-2:1.0: uevent
drivers/usb/core/inode.c: creating file '007'
usb 7-2: New USB device found, idVendor=07ca, idProduct=a827
usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 7-2: Product: AVerTV
usb 7-2: Manufacturer: AVerMedia
usb 7-2: SerialNumber: 301357900268
|
I've even tried to pass the udev-created files (/dev/usbdev7.X-epYZ) to mplayer but with no luck there either.
Code: |
foxicatko /etc/udev $ mplayer -tv driver=v4l2:device=/dev/usbdev7.7_ep00 tv://
MPlayer SVN-r28450-4.1.2 (C) 2000-2009 MPlayer Team
CPU: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (Family: 6, Model: 15, Stepping: 13)
Playing tv://
Detected TV file format!
Selected driver: v4l2
name: Video 4 Linux 2 input
author: Martin Olschewski <olschewski@zpr.uni-koeln.de>
comment: first try, more to come ;-)
v4l2: unable to open '/dev/usbdev7.7_ep00': Permission denied
v4l2: ioctl set mute failed: Bad file descriptor
v4l2: 0 frames successfully processed, 0 frames dropped.
Ending... (End of file)
|
I suppose it's usbdev7.7-* here because i've tried plugging the stick in and out to get output for this post.
I'll happily post more info when requested.
Thanks for all help. |
|
Back to top |
|
|
poly_poly-man Advocate
Joined: 06 Dec 2006 Posts: 2477 Location: RIT, NY, US
|
Posted: Tue Mar 31, 2009 10:47 pm Post subject: |
|
|
you sure you have the right drivers? _________________ iVBORw0KGgoAAAANSUhEUgAAA
avatar: new version of logo - see topic 838248. Potentially still a WiP. |
|
Back to top |
|
|
foxicatko n00b
Joined: 15 Mar 2008 Posts: 14
|
Posted: Wed Apr 01, 2009 6:05 am Post subject: |
|
|
I've got the 0.25beta from this site: http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=31&tab=APDriver
I've tried it with 0.21beta to avail either. Driver installation works beautifully until an audio test upon which it tries to tune to a TV channel and play render sound through my soundcard but fails with "No tuner devices found".
Googling around makes me feel like I'm the only one with this problem, since other's problems have been solved with previous driver releases which imo means that the problem is somewhere between the chair and udev or .config. :-/ |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|