Still working on getting my PVR 350 running under 10.0RC1 After a new instalation I started all over again and I now get the error that the device /dev/video0 is not available. What must I use in RC1 or what must I do to add /dev/video0? houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Am Thursday 22 September 2005 04:03 schrieb houghi:
Still working on getting my PVR 350 running under 10.0RC1
After a new instalation I started all over again and I now get the error that the device /dev/video0 is not available.
What must I use in RC1 or what must I do to add /dev/video0?
I don't tried ivtv so far with 10.0 on my computer at home ... When the device is not available the driver is maybe not loaded proper ... check the if the modules load, check messages, check if you have the right firmware, iirc there is also a debug option when you load the modules manually. -- with kind regards, ---------------------------------------------------------------------- Martin Lasarsch, Subsystems SUSE LINUX GmbH, Maxfeldstr. 5 90409 Nuremberg martin.lasarsch@suse.de ---------------------------------------------------------------------- simply change to www.suse.de
On Thu, Sep 22, 2005 at 11:55:01AM +0200, Martin Lasarsch wrote:
that the device /dev/video0 is not available.
What must I use in RC1 or what must I do to add /dev/video0?
I don't tried ivtv so far with 10.0 on my computer at home ...
When the device is not available the driver is maybe not loaded proper ...
Strange. I DO have /dev/video0 on my 9.1 and no ivtv or anything else. I thought that it was made with the instalation of the OS. Also I have tried compiling ivtv myself and have used the ivtv rpm that comes with SUSE. I would asume that the SUSE ivtv would load properly.
check the if the modules load, check messages, check if you have the right firmware, iirc there is also a debug option when you load the modules manually.
Any idea how to enable that option? I will look at the rest. I just want to be sure I am doing nothing wrong before I file a bugreport. houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Am Thursday 22 September 2005 13:05 schrieb houghi:
On Thu, Sep 22, 2005 at 11:55:01AM +0200, Martin Lasarsch wrote:
that the device /dev/video0 is not available.
What must I use in RC1 or what must I do to add /dev/video0?
I don't tried ivtv so far with 10.0 on my computer at home ...
When the device is not available the driver is maybe not loaded proper ...
Strange. I DO have /dev/video0 on my 9.1 and no ivtv or anything else. I thought that it was made with the instalation of the OS. Also I have tried compiling ivtv myself and have used the ivtv rpm that comes with SUSE. I would asume that the SUSE ivtv would load properly.
check the if the modules load, check messages, check if you have the right firmware, iirc there is also a debug option when you load the modules manually.
Any idea how to enable that option? I will look at the rest. I just want to be sure I am doing nothing wrong before I file a bugreport.
try modprobe ivtv ivtv_debug=255 when its not loaded. I hope i can test it on the weekend on my system with 10.0 ... -- with kind regards, ---------------------------------------------------------------------- Martin Lasarsch, Subsystems SUSE LINUX GmbH, Maxfeldstr. 5 90409 Nuremberg martin.lasarsch@suse.de ---------------------------------------------------------------------- simply change to www.suse.de
On Thu, Sep 22, 2005 at 01:26:41PM +0200, Martin Lasarsch wrote:
try modprobe ivtv ivtv_debug=255 when its not loaded.
I hope i can test it on the weekend on my system with 10.0 ...
OK, I did look at the messages (should have done that from the beginning) and I got: <snip all that worked> Sep 22 13:19:49 linux kernel: ivtv: requesting ivtv-fw-enc.bin from hotplug Sep 22 13:19:49 linux kernel: ivtv: firmware load failed Sep 22 13:19:49 linux kernel: ivtv: failed loading encoder firmware Sep 22 13:19:49 linux kernel: ivtv: Error loading firmware -3! Sep 22 13:19:49 linux kernel: ivtv: Error -3 initializing firmware. Sep 22 13:19:49 linux kernel: ivtv: Error -12 on initialization Sep 22 13:19:49 linux kernel: ivtv-iTVC15_16_mpg2_encoder_card: probe of \ 0000:00:0d.0 failed with error -12 I looked a bit around and found that ivtv-fw-enc.bin was in /lib/modules/. I looked more around and found that somebody solved it by putting in in /lib/firmware, so I moved it (not copied it) and now I got: <snip all that worked> Sep 22 14:12:53 linux kernel: ivtv: requesting ivtv-fw-enc.bin from hotplug Sep 22 14:12:53 linux kernel: ivtv: firmware loaded Sep 22 14:12:53 linux kernel: ivtv: requesting ivtv-fw-dec.bin from hotplug Sep 22 14:12:53 linux kernel: ivtv: firmware load failed Sep 22 14:12:53 linux kernel: ivtv: failed loading decoder firmware Sep 22 14:12:53 linux kernel: ivtv: Error loading firmware -1! Sep 22 14:12:53 linux kernel: ivtv: Error -1 initializing firmware. Sep 22 14:12:53 linux kernel: ivtv: Error -12 on initialization Sep 22 14:12:53 linux kernel: ivtv-iTVC15_16_mpg2_encoder_card: probe of \ 0000:00:0d.0 failed with error -12 As you can see it still is looking somewhere on the wrong place. No idea where it is actually looking, because I then would put ivtv-fw-enc.bin in that place I will also do the mknod -m 666 ... to make the /dev/video0 and see what happens. So close and yet so far. :-) houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
On Thu, Sep 22, 2005 at 02:48:11PM +0200, houghi wrote:
<snip all that worked> Sep 22 14:12:53 linux kernel: ivtv: requesting ivtv-fw-enc.bin from hotplug Sep 22 14:12:53 linux kernel: ivtv: firmware loaded Sep 22 14:12:53 linux kernel: ivtv: requesting ivtv-fw-dec.bin from hotplug
OK. I should learn to read. ivtv-fw-enc.bin is not the same as ivtv-fw-dec.bin
I will also do the mknod -m 666 ... to make the /dev/video0 and see what happens. So close and yet so far. :-)
OK that worked. I am able to get ./ptune-ui.pl running. I also get snow with `mplayer /dev/video0`. Nothing but snow. Sigh. Yes, I tried a lot of channels. houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
On Thu, Sep 22, 2005 at 03:35:51PM +0200, houghi wrote:
On Thu, Sep 22, 2005 at 02:48:11PM +0200, houghi wrote:
<snip all that worked> Sep 22 14:12:53 linux kernel: ivtv: requesting ivtv-fw-enc.bin from hotplug Sep 22 14:12:53 linux kernel: ivtv: firmware loaded Sep 22 14:12:53 linux kernel: ivtv: requesting ivtv-fw-dec.bin from hotplug
OK. I should learn to read. ivtv-fw-enc.bin is not the same as ivtv-fw-dec.bin
Sorry about replying to my own posting. The solution is to put the two files in /lib/firmware houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Am Thursday 22 September 2005 15:35 schrieb houghi:
On Thu, Sep 22, 2005 at 02:48:11PM +0200, houghi wrote:
<snip all that worked> Sep 22 14:12:53 linux kernel: ivtv: requesting ivtv-fw-enc.bin from hotplug Sep 22 14:12:53 linux kernel: ivtv: firmware loaded Sep 22 14:12:53 linux kernel: ivtv: requesting ivtv-fw-dec.bin from hotplug
OK. I should learn to read. ivtv-fw-enc.bin is not the same as ivtv-fw-dec.bin
I will also do the mknod -m 666 ... to make the /dev/video0 and see what happens. So close and yet so far. :-)
OK that worked. I am able to get ./ptune-ui.pl running. I also get snow with `mplayer /dev/video0`. Nothing but snow. Sigh. Yes, I tried a lot of channels.
check the ivtv wiki ... check if you have the right tuner setting. Try to find a channel list for your provider, google is your friend. this was my tuner setting (pal, cable): modprobe ivtv ivtv_debug=1 ivtv_pal=1 tuner=5 (i'm not sure if ivtv_pal is still a valid option, they change a lot in the driver ...) If you have a PVR card with video in you can also try to use an external video source to see if its working (you have to change the tuner setting). -- with kind regards, ---------------------------------------------------------------------- Martin Lasarsch, Subsystems SUSE LINUX GmbH, Maxfeldstr. 5 90409 Nuremberg martin.lasarsch@suse.de ---------------------------------------------------------------------- simply change to www.suse.de
On Thu, Sep 22, 2005 at 03:55:54PM +0200, Martin Lasarsch wrote:
check the ivtv wiki ... check if you have the right tuner setting.
I looked at the wiki and they said to do `modprobe tveeprom` and then look with dmesg. There I see nothing happening. However when I `modprobe ivtv` I see: tveeprom: Hauppauge: model = 48139, rev = J352, serial# = 7250735 tveeprom: tuner = Microtune 4049 FM5 (idx = 52, type = 45) tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio_processor = CS5331 (type = 9) I have absolutely no idea wether this is the correct tuner setting or not.
Try to find a channel list for your provider, google is your friend.
I found something extremely outdated. Tried it with ./ptune-ui.pl and still only snow
this was my tuner setting (pal, cable):
modprobe ivtv ivtv_debug=1 ivtv_pal=1 tuner=5 (i'm not sure if ivtv_pal is still a valid option, they change a lot in the driver ...)
Nothing.
If you have a PVR card with video in you can also try to use an external video source to see if its working (you have to change the tuner setting).
Sounds interesting, but I have NO idea what tuner setting it should be. This getting really frustrating, especialy since I am trying this for already a few months. Why can't somebody just make a RPM that I can install and it works? I have read a LOT of howto's and none of them seem to cut it for me, probably because I have NO idea what I am doing and just blindly follow orders. Double frustrating, because I decided to buy a Haupauge, because it looked like it was the easiest to get to work. Till now wasted money. houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
On Fri, Sep 23, 2005 at 02:48:59AM +0200, houghi wrote:
On Thu, Sep 22, 2005 at 03:55:54PM +0200, Martin Lasarsch wrote:
check the ivtv wiki ... check if you have the right tuner setting.
I looked at the wiki and they said to do `modprobe tveeprom` and then look with dmesg. There I see nothing happening. However when I `modprobe ivtv` I see: tveeprom: Hauppauge: model = 48139, rev = J352, serial# = 7250735 tveeprom: tuner = Microtune 4049 FM5 (idx = 52, type = 45) tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio_processor = CS5331 (type = 9)
I have absolutely no idea wether this is the correct tuner setting or not.
Try to find a channel list for your provider, google is your friend.
I found something extremely outdated. Tried it with ./ptune-ui.pl and still only snow
I am not giving up easily. :-) I have now put online what I have done step by step. The moment I run `modprobe ivtv` I get a lot of `APIC error on CPU0: 40(40)` in /var/log/messages. What I have done and what mplayer tells me can be seen on: http://houghi.org/script/haupauge.txt It would be great if someone with an Haupauge PVR 250 or 350 could test this with RC1 to see if I am on the right track. As you can see I have written it in such a way that it can be put into a script very easily and I indend to put the script and all the files needed in one big zip, so installing it (at least till step 12) is very easy. Still no idea if the default tuner is correct. I could not find the answer on the ivtv wiki. :-( houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Am Samstag, 24. September 2005 03:32 schrieb houghi:
On Fri, Sep 23, 2005 at 02:48:59AM +0200, houghi wrote:
On Thu, Sep 22, 2005 at 03:55:54PM +0200, Martin Lasarsch wrote:
check the ivtv wiki ... check if you have the right tuner setting. I have absolutely no idea wether this is the correct tuner setting or not. I am not giving up easily. :-) I have now put online what I have done step by step. The moment I run `modprobe ivtv` I get a lot of `APIC error on CPU0: 40(40)` in /var/log/messages.
Hi houghi, did you try "noapic" at the boot prompt? Anyway, I have a "Haupauge WinTV Nova CI PCI" and it only works, if I remove all tuners that are autoloaded by rcdvb, and load the correct tuner (stv0299) only. Also SuSE's rcdvb tryed to load the "budget..."-Modules, but it did not manage load them (Maybe the wrong order?) So I disable dvb in the runlevel editor and use my own script: #!/bin/bash # starts my DVB-S card # sorry: unload only partially supported # mdc BUDGET="budget budget_patch budget_ci budget_av budget_core" DVB="dvb_ttpci saa7146_vv saa7146 videodev v4l2_common v4l1_compat video_buf ttpci_eeprom firmware_class dvb_core" case $1 in start) for m in $DVB $BUDGET do modprobe $m done modprobe stv0299 ;; stop) rmmod stv0299 for m in $BUDGET $DVB do rmmod $m done ;; esac Not nice, but works for me. -- mdc
On Sat, Sep 24, 2005 at 02:36:54PM +0200, meister@netz00.com wrote:
did you try "noapic" at the boot prompt?
I did now. And I just start from a complete clean instalation each time I try something. No idea if that had any influence on anything. Also no idea where the errors come from.
Anyway, I have a "Haupauge WinTV Nova CI PCI" and it only works, if I remove all tuners that are autoloaded by rcdvb, and load the correct tuner (stv0299) only.
Here I get stuck. What is the correct tuner? WiKi tells me to do `modprobe tveeprom` and then check ou dmesg. Very nice, but completely useless if you have no clue where to look. I have just been able to get picture on my screen. I connected my video recorder with a cable (No idea what it is called) and got a picture. No sound yet and it was very slow at some times, but still, at least I know the card works. I used mplayer /dev/video0, so not yet fully tested. Becaue I start from zeror, I need to do the same things all the time and it gets very easy to forget things. So after a fresh instalation I just run the following script: http://houghi.org/script/pvr350 Needs some finetuning, but it works for me. Still no clue how to get TV. Once that is solved, I will put the script with the files online, wich should make it easier then reading 50 manuals and bothering all of you. ;-) Mmm. It might even become my first SUSE rpm project. :-) (Don't hold your breath on that last one) houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Am Samstag, 24. September 2005 17:13 schrieb houghi:
On Sat, Sep 24, 2005 at 02:36:54PM +0200, meister@netz00.com wrote: Here I get stuck. What is the correct tuner? WiKi tells me to do `modprobe tveeprom` and then check ou dmesg. Very nice, but completely useless if you have no clue where to look.
Hi houghi, try to grep it in the modules
tveeprom: Hauppauge: model = 48139, rev = J352, serial# = 7250735 tveeprom: tuner = Microtune 4049 FM5 (idx = 52, type = 45) tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio_processor = CS5331 (type = 9)
fgrep -i Microtune /lib/modules/`uname -r`/* fgrep -i Microtune /lib/modules/`uname -r`/*/* fgrep -i Microtune /lib/modules/`uname -r`/*/*/* ... -- mdc
On Sun, Sep 25, 2005 at 02:49:35PM +0200, meister@netz00.com wrote:
Am Samstag, 24. September 2005 17:13 schrieb houghi:
On Sat, Sep 24, 2005 at 02:36:54PM +0200, meister@netz00.com wrote: Here I get stuck. What is the correct tuner? WiKi tells me to do `modprobe tveeprom` and then check ou dmesg. Very nice, but completely useless if you have no clue where to look.
Hi houghi,
try to grep it in the modules
tveeprom: Hauppauge: model = 48139, rev = J352, serial# = 7250735 tveeprom: tuner = Microtune 4049 FM5 (idx = 52, type = 45) tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio_processor = CS5331 (type = 9)
fgrep -i Microtune /lib/modules/`uname -r`/* fgrep -i Microtune /lib/modules/`uname -r`/*/* fgrep -i Microtune /lib/modules/`uname -r`/*/*/*
Did it from 9.1 in the correct diretory without the use of uname. Below the details of the fgrep. What must I do with the information? [01:29:47] [~] root@penne : fgrep -i Microtune /media/root/lib/modules/2.6.13-8-smp/* grep: /media/root/lib/modules/2.6.13-8-smp/build: No such file or directory /media/root/lib/modules/2.6.13-8-smp/modules.symbols:alias symbol:dvb_pll_microtune_4042 dvb_pll grep: /media/root/lib/modules/2.6.13-8-smp/source: No such file or directory [01:29:57] [~] root@penne : fgrep -i Microtune /media/root/lib/modules/2.6.13-8-smp/*/* Binary file /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tuner.ko matches Binary file /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tveeprom.ko matches Binary file /media/root/lib/modules/2.6.13-8-smp/ivtv/tuner.ko matches Binary file /media/root/lib/modules/2.6.13-8-smp/ivtv/tveeprom.ko matches [01:30:02] [~] root@penne : fgrep -i Microtune /media/root/lib/modules/2.6.13-8-smp/*/*/* [01:30:07] [~] root@penne : houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Am Montag, 26. September 2005 01:32 schrieb houghi:
On Sun, Sep 25, 2005 at 02:49:35PM +0200, meister@netz00.com wrote:
On Sat, Sep 24, 2005 at 02:36:54PM +0200, meister@netz00.com wrote: Here I get stuck. What is the correct tuner? WiKi tells me to do `modprobe tveeprom` and then check ou dmesg. Very nice, but completely useless if you have no clue where to look.
Am Samstag, 24. September 2005 17:13 schrieb houghi: try to grep it in the modules Did it from 9.1 in the correct diretory without the use of uname. Below the details of the fgrep. What must I do with the information? root@penne : fgrep -i Microtune /media/root/lib/modules/2.6.13-8-smp/*/* Binary file /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tuner.ko matches Binary file /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tveeprom.ko matches Binary file /media/root/lib/modules/2.6.13-8-smp/ivtv/tuner.ko matches Binary file /media/root/lib/modules/2.6.13-8-smp/ivtv/tveeprom.ko matches [01:30:02] [~]
well ivtv-tuner.ko is the "driver" for your tuner. You have to load it via modprobe. Do a strings /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tuner.ko and check for "param" to see if it takes some arguments. As I can see you have a smp-kernel. Did you try to use a nonsmp (=default) kernel? Sometimes some modules have problems with smp... -- mdc
On Mon, Sep 26, 2005 at 02:17:22PM +0200, meister@netz00.com wrote:
well ivtv-tuner.ko is the "driver" for your tuner. You have to load it via modprobe. Do a strings /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tuner.ko and check for "param" to see if it takes some arguments.
houghi@penne : strings /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tuner.ko|grep param mt2032: frequency parameters out of range: %d %d %d %d param_array_get dparam_get_short param_array_set @param_set_short
As I can see you have a smp-kernel. Did you try to use a nonsmp (=default) kernel? Sometimes some modules have problems with smp...
No, I have not. That is the standard instalation I get when installing. houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Am Montag, 26. September 2005 22:21 schrieb houghi:
On Mon, Sep 26, 2005 at 02:17:22PM +0200, meister@netz00.com wrote:
well ivtv-tuner.ko is the "driver" for your tuner. You have to load it via modprobe. Do a strings /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tuner.ko and check for "param" to see if it takes some arguments.
Hi houghi,
houghi@penne : strings /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tuner.ko|grep param mt2032: frequency parameters out of range: %d %d %d %d param_array_get dparam_get_short param_array_set @param_set_short
seems it takes no params.
As I can see you have a smp-kernel. Did you try to use a nonsmp (=default) kernel? Sometimes some modules have problems with smp...
No, I have not. That is the standard instalation I get when installing.
Do you really have more than one cpu? Try the nonsmp kernel to see whether it works or not. -- mdc
On Mon, Sep 26, 2005 at 11:14:38PM +0200, meister@netz00.com wrote:
houghi@penne : strings /media/root/lib/modules/2.6.13-8-smp/extra/ivtv-tuner.ko|grep param mt2032: frequency parameters out of range: %d %d %d %d param_array_get dparam_get_short param_array_set @param_set_short
seems it takes no params.
So, must I do anything special?
Do you really have more than one cpu? Try the nonsmp kernel to see whether it works or not.
All the same. houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Am Donnerstag, 22. September 2005 13:05 schrieb houghi:
On Thu, Sep 22, 2005 at 11:55:01AM +0200, Martin Lasarsch wrote:
that the device /dev/video0 is not available. What must I use in RC1 or what must I do to add /dev/video0?
mknod -m 666 /dev/video0 c 81 0 -- mdc
participants (3)
-
houghi
-
Martin Lasarsch
-
meister@netz00.com