|
I'm trying to
get the flyvideo 3100 working with bytesex saa7134 drivers....
i'm getting the following errors (pasted below)... its saying "no such device" ... is this coming from the driver not finding the card at all, or is it a problem with the driver installation? Somewhere on the manufacturers site I was reading that the 3100 is the "low profile" version of the 3000. ("The FlyVideo 3100 is the low profile version of the FlyVideo 3000. It has all the features the FlyVideo 3000 has and is designed for the emerging slim case PCs. " from http://www.lifeview.com.tw/eng/pro_fly_3100.html) ... The chips are the same, but that in it of itself is interesting. The NTSC card is saa7130 chipset, and the PAL the 34. The bytesex drivers support the 3000 (which is sa31733/34) as well as the 2000 (which is saa7130). With that said, it seems as though the 2000 or 3000 drivers should work for 3100 (or at least, if not, in the generic form they should?). I tried and this seems to not be the case, but I'm not sure if its really the drivers or if the drivers are just improperly installed. Also, the "low profile" version 3100 has only a standard RF tuner input and one composite, the 3000 has 2 more. So, I edited the saa7134-cards.c to add another struct for the 3100 (as card 16), and also tried adding the 3100 to a "special" case scenario down further in the code that was there for the 2000 and 3000. Then, I defined it in the .h as the 16 position. In addition to trying card=16, i tried 0-15 as well, but nothing changed as far as the "no such device error" ... I tried the driver without adding in this special struct (I copied the 3000 and removed the inputs 3100 doesnt have) and just using the 3000 card number, but no luck there either. I added 4 lines to modules.conf (alias char-major 81 videodev, alias char-major-81-0, saa7134 options saa7134 tuner=37, options tuner type=37) to see if that changed anything. The output below is after the additional struct and the additoinal data in modules.conf. Also, I only realized that the chipset of the 3100
was actually closer to that of the 2000 card just now. I suppose I could
copy that struct and make it 3100 (though, the audio on 3100 is closer to the
3000's--stereo & also there is an fm tuner input). But, I don't think
that its failing because of that anyway.
Anyone have any ideas/suggestions? Thanks, Dane Kantner [root@localhost saa7134-0.2.7]# modprobe -d -v saa7134 card=16 /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7134.o.gz: init_module: No such device modprobe: insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7134.o.gz failed modprobe: insmod saa7134 failed [root@localhost saa7134-0.2.7]# the full debug and verbose output is: ============================================= Module v4l1-compat kname v4l1-compat objkey v4l1-compat names: v4l1-compat mode: NORMAL Module matching v4l1-compat: /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/v4l1-compat.o.gz ============================================= ============================================= Module v4l2-common kname v4l2-common objkey v4l2-common names: v4l2-common mode: NORMAL Module matching v4l2-common: /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/v4l2-common.o.gz ============================================= ============================================= Module i2c-core kname i2c-core objkey i2c-core names: i2c-core mode: NORMAL Module matching i2c-core: /lib/modules/2.4.21-0.13mdk/kernel/drivers/i2c/i2c-core.o.gz ============================================= ============================================= Module video-buf kname video-buf objkey video-buf names: video-buf mode: NORMAL Module matching video-buf: /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/video-buf.o.gz ============================================= ============================================= Module soundcore kname soundcore objkey soundcore names: soundcore mode: NORMAL Module matching soundcore: /lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/soundcore.o.gz ============================================= ============================================= Module videodev kname videodev objkey videodev names: videodev mode: NORMAL Module matching videodev: /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/videodev.o.gz ============================================= ============================================= Module saa7134 kname saa7134 objkey saa7134 names: saa7134 options: tuner=37 mode: NORMAL Module matching saa7134: /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7134.o.gz ============================================= /sbin/insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/v4l1-compat.o.gz /sbin/insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/v4l2-common.o.gz /sbin/insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/i2c/i2c-core.o.gz /sbin/insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/video-buf.o.gz /sbin/insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/videodev.o.gz /sbin/insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7134.o.gz tuner=37 card=16 Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg # delete videodev # delete video-buf # delete i2c-core # delete v4l2-common # delete v4l1-compat |
