AverTV super 007 nie widzi karty
: 24 cze 2008, 21:30
Witam
Nie znalazłem na forum jeszcze rozwiązania, ani nic odpowiedniego.
Karta jak w tytule, problem polega na tym, że na początku system coś widział, ale nie chciał współdziałać.
Komendy:
nie skutkowały.
Postąpiłem zgodznie z instrukcją:
Później zmieniłem firmware na:
ftp://ftp.pbone.net/mirror/plf.zarb.org ... noarch.rpm
I dalej to samo.
HELP!!
Nie znalazłem na forum jeszcze rozwiązania, ani nic odpowiedniego.
Karta jak w tytule, problem polega na tym, że na początku system coś widział, ale nie chciał współdziałać.
Komendy:
Kod: Zaznacz cały
rmmod saa7134
rmmod saa7134-alsa Postąpiłem zgodznie z instrukcją:
Po tych operacjach całkowicie przestało widzieć kartę, chyba. W katalogu /dev nie ma jej już, a dmesg wypluwa coś takiegoFor successful setup:
These are intended for a non-expert, follow_the_dots user.
Physically install your card and connect an antenna to it.
Uninstall MythTV if present and restart your computer to ensure no MythTV daemons are running
Although the core hardware for this card is common to this card and it does appear to be recognised with the current apt version of video4linux (v4l), it is actually not recognised properly and will not work with it.
You will NOT need to edit /etc/modules so undo any edits that you have made for this card
You will not need to worry about autodetection which you may see mentioned on other websites.
You WILL be using the latest v4l direct from the developers, i.e. non-packaged.
You will also need some development tools installed on your box. I already had mine installed but you could begin by
Code:
sudo apt-get install kernel-package
to pull in the core tools you will likely need.
(This section based on the instructions at http://linuxtv.org/v4lwiki/index.php...from_Mercurial)
Mercurial is a distributed version control system that you will need to install in order to get the latest code. You will also need the source for your running kernel. I don't know if the kernel headers are sufficient, I installed the full source. Be aware that you will need to unzip the (full) source installed by apt before you can use it here. I do this byKod: Zaznacz cały
sudo apt-get install mercurial
to get a root file browser and then unzip in /usr/src/.Kod: Zaznacz cały
alt+f2 kdesu konqueror
Create a working directory somewhere to compile your code and open a terminal there
Retrieve v4l-dvb sources
Change into the v4l-dvb directory:Kod: Zaznacz cały
hg clone http://linuxtv.org/hg/v4l-dvb
(This section based on the instructions at http://lists.zerezo.com/video4linux/msg19205.html)Kod: Zaznacz cały
cd v4l-dvb
Here you need to edit one of the files you downloaded with Mercurial manually:
Open your-working-directory/v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c with a text editor and insert the following section. There are a number of card definitions already there so you can see how one follows another in the list. Be very careful to paste this section into the file just after another definition so that it follows the same pattern and doesn't disrupt or interrupt the other definitions or other text before or after it. It doesn't matter where you put it in the file, I put mine between the first and the second definitions.
Now you are ready to compile the modules (driver) for your card:Kod: Zaznacz cały
[SAA7134_BOARD_PHILIPS_TIGER_S] = { .name = "Philips Tiger - S Reference design", .audio_clock = 0x00187de7, .tuner_type = TUNER_PHILIPS_TDA8290, .radio_type = UNSET, .tuner_addr = ADDR_UNSET, .radio_addr = ADDR_UNSET, .tuner_config = 2, .mpeg = SAA7134_MPEG_DVB, .gpiomask = 0x0200000, .inputs = {{ .name = name_tv, .vmux = 1, .amux = TV, .tv = 1, .gpio = 0x0200000, },{ .name = name_comp1, .vmux = 3, .amux = LINE1, },{ .name = name_svideo, .vmux = 8, .amux = LINE1, }}, .radio = { .name = name_radio, .amux = TV, .gpio = 0x0000000, }, },
Then install them. This is a manual install which sidesteps the apt packaging system. This will install the modules for the current running kernel only.Kod: Zaznacz cały
sudo make
You are almost ready but the card still needs firmware in order to work. I am not so familiar with firmware loading in Ubuntu and so I put my firmwares in two places. The files aren't big so this shouldn't matter.Kod: Zaznacz cały
sudo make install
(This section based on the instructions at http://linuxtv.org/wiki/index.php/AV...VB-T_Super_007)
Download http://technotrend-online.com/downlo...28_11_2006.zip and unzip it.
Locate the file TT_PCI_2.19h_28_11_2006/software/OEM/PCI/App/ttlcdacc.dll Yes, this looks like a windows binary and rename it to dvb-fe-tda10046.fw Move this to /lib/firmware and link or copy to /lib/firmware/your-current-kernel.
I also added all the files from http://www.linuxtv.org/downloads/firmware/ to /lib/fimware/ and /lib/firmware/my-current-kernel but this is probably unneccessary.
Make sure that you have all needed DVB utilities installed
Reboot your computer to ensure all needed modules are loaded for your card.Kod: Zaznacz cały
sudo apt-get install dvb-utils
Kod: Zaznacz cały
[ 20.132000] saa7134: disagrees about version of symbol videobuf_streamoff
[ 20.132000] saa7134: Unknown symbol videobuf_streamoff
[ 20.132000] saa7134: disagrees about version of symbol videobuf_poll_stream
[ 20.132000] saa7134: Unknown symbol videobuf_poll_stream
[ 20.132000] saa7134: disagrees about version of symbol videobuf_read_stop
[ 20.132000] saa7134: Unknown symbol videobuf_read_stop
[ 20.132000] saa7134: Unknown symbol videobuf_dma_free
[ 20.132000] saa7134: disagrees about version of symbol videobuf_reqbufs
[ 20.132000] saa7134: Unknown symbol videobuf_reqbufs
[ 20.132000] saa7134: disagrees about version of symbol videobuf_waiton
[ 20.132000] saa7134: Unknown symbol videobuf_waiton
[ 20.132000] saa7134: disagrees about version of symbol videobuf_dqbuf
[ 20.132000] saa7134: Unknown symbol videobuf_dqbuf
[ 20.132000] saa7134: disagrees about version of symbol v4l2_video_std_construct
[ 20.132000] saa7134: Unknown symbol v4l2_video_std_construct
[ 20.132000] saa7134: Unknown symbol videobuf_queue_init
[ 20.132000] saa7134: disagrees about version of symbol v4l2_type_names
[ 20.132000] saa7134: Unknown symbol v4l2_type_names
[ 20.132000] saa7134: disagrees about version of symbol v4l2_field_names
[ 20.132000] saa7134: Unknown symbol v4l2_field_names
[ 20.132000] saa7134: Unknown symbol videobuf_dma_unmap
[ 20.132000] saa7134: disagrees about version of symbol videobuf_read_stream
[ 20.132000] saa7134: Unknown symbol videobuf_read_stream
[ 20.132000] saa7134: disagrees about version of symbol videobuf_querybuf
[ 20.132000] saa7134: Unknown symbol videobuf_querybuf
[ 20.132000] saa7134: disagrees about version of symbol video_unregister_device
[ 20.132000] saa7134: Unknown symbol video_unregister_device
[ 20.132000] saa7134: disagrees about version of symbol videobuf_qbuf
[ 20.132000] saa7134: Unknown symbol videobuf_qbuf
[ 20.132000] saa7134: disagrees about version of symbol video_device_alloc
[ 20.132000] saa7134: Unknown symbol video_device_alloc
[ 20.132000] saa7134: disagrees about version of symbol videobuf_read_one
[ 20.132000] saa7134: Unknown symbol videobuf_read_one
[ 20.132000] saa7134: disagrees about version of symbol video_register_device
[ 20.132000] saa7134: Unknown symbol video_register_device
[ 20.132000] saa7134: disagrees about version of symbol videobuf_iolock
[ 20.132000] saa7134: Unknown symbol videobuf_iolock
[ 20.132000] saa7134: disagrees about version of symbol videobuf_streamon
[ 20.132000] saa7134: Unknown symbol videobuf_streamon
[ 20.132000] saa7134: disagrees about version of symbol video_device_release
[ 20.132000] saa7134: Unknown symbol video_device_release
[ 20.132000] saa7134: disagrees about version of symbol videobuf_mmap_mapper
[ 20.132000] saa7134: Unknown symbol videobuf_mmap_mapper
[ 20.132000] saa7134: disagrees about version of symbol videobuf_mmap_free
[ 20.132000] saa7134: Unknown symbol videobuf_mmap_free
ftp://ftp.pbone.net/mirror/plf.zarb.org ... noarch.rpm
I dalej to samo.
HELP!!
