Is there an IRQ guru on this list?

I'd hate to waste a mouse to fix this problem... Nevertheless I'm
going to connect one right now and see if it also fixes my problem...

Hope to hear from someone who knows how to fix the IRQ settings later,
Regards,
Pieter

On 1/31/06, Craig Orsinger <[EMAIL PROTECTED]> wrote:
> I was having a similar problem - no output from video0, sometimes
> got a "can't open device" message, etc. Turns out, like yours,
> my IVTV card was on IRQ 12. This is also the IRQ used by a PS2
> mouse. When I have a PS2 mouse connected to my system, it works
> fine, and when I don't, I have problems. I've been meaning to
> write this up, but it wasn't an emergency. I have an old, largely
> nonfunctional mouse I can plug into this computer.
>
> BTW, I'm using a PVR150.
>
> To confirm this might be the problem, cat out the /proc/interrupts
> file. It will look like this if things aren't working:
>
>            CPU0
>   0:    3860537          XT-PIC  timer
>   1:          8          XT-PIC  i8042
>   2:          0          XT-PIC  cascade
>   3:          0          XT-PIC  ohci_hcd:usb3
>   4:        185          XT-PIC  ohci_hcd:usb2
>   5:          2          XT-PIC  ohci1394
>   7:          2          XT-PIC  ehci_hcd:usb1
>   8:          1          XT-PIC  rtc
>   9:          0          XT-PIC  acpi
>  11:        431          XT-PIC  SiS SI7012, eth0
>  12:          0          XT-PIC  ivtv0
>  14:       6091          XT-PIC  ide0
>  15:      92332          XT-PIC  ide1
> NMI:          0
> ERR:          0
>
> Note the lack of interrupts on IRQ 12, where the ivtv0 device
> is. Sometimes there'd be three interrupts rather than zero. If
> your IVTV card's IRQ line is working, you should see hundreds
> of interrupts in a very short time of capturing video data.
> Kinda like how the two ideX devices look.
>
> If there are few or no interrupts, try plugging a PS2 mouse in
> and see if that fixes it. I don't know what gets hung up without
> the mouse. I tried many different ways of telling the kernel to
> ignore the mouse device, re-route IRQs, and anything else that
> looked hopeful. Nothing worked, except plugging that junker
> mouse into the PS2 port.
>
> HTH.
>
> On Tue, 2006-01-31 at 00:49 -0800, Mik Rose wrote:
> > Nick Rosier wrote:
> > > On 1/31/06, Mik Rose <[EMAIL PROTECTED]> wrote:
> > >
> > > >  Keith C wrote:
> > > >  On Jan 29, 2006, at 11:14 PM, Mik Rose wrote:
> > > >
> > > >
> > > >
> > > >  Hi there people...
> > > >
> > > > I have loaded all the ivtv related softwares and drivers/firwmare via
> > > > yum but I do not have a /dev/video* device.
> > > >
> > > > Can anyone suggest some steps that I can take to trouble shoot this
> > > > problem?
> > > > I am on FC4
> > > > /mr
> > > >
> > > >
> > > >  modprobe ivtv and then post the relevant section of your dmesg, along
> > > > with any module options from modprobe.conf.
> > > >
> > > > Keith C
> > > >
> > > > _______________________________________________
> > > > ivtv-users mailing list
> > > > [email protected]
> > > > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> > > >
> > > >
> > > >  I modprobed ivtv as root and there was no result.
> > > >
> > > >  dmesg result;
> > > >  Linux video capture interface: v1.00
> > > >  ivtv: no version for "struct_module" found: kernel tainted.
> > > >  ivtv:  ==================== START INIT IVTV ====================
> > > >  ivtv:  version 0.4.2 (tagged release) loading
> > > >  ivtv:  Linux version: 2.6.14-1.1656_FC4 686 REGPARM 4KSTACKS gcc-4.0
> > > >  ivtv:  In case of problems please include the debug info between
> > > >  ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
> > > >  ivtv:  any module options, when mailing the ivtv-users mailinglist.
> > > >  ivtv0: Autodetected WinTV PVR 250 card (cx23416 based)
> > > >  PCI: Found IRQ 12 for device 0000:00:09.0
> > > >  ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> > > >  tveeprom: ivtv version
> > > >  tveeprom: Hauppauge: model = 32552, rev = B123, serial# = 7164106
> > > >  tveeprom: tuner = Philips FM1236 (idx = 23, type = 2)
> > > >  tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
> > > >  tveeprom: audio processor = MSP4448 (type = 1b)
> > > >  tveeprom: decoder processor = SAA7115 (type = 13)
> > > >  ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
> > > >  tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
> > > >  ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
> > > >  saa7115 1-0021: ivtv driver
> > > >  saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> > > >  ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
> > > >  msp3400 1-0040: ivtv driver
> > > >  msp3400 1-0040: chip=MSP4448G-A2 +nicam +simple +simpler +radio
> > > > mode=simpler
> > > >  ivtv0: i2c attach to card #0 ok [client=MSP4448G-A2, addr=40]
> > > >  msp3400 1-0040: msp34xxg daemon started
> > > >  ivtv0: unable to open firmware v4l-cx2341x-enc.fw
> > > >  ivtv0: did you put the firmware in the hotplug firmware directory?
> > > >  ivtv0 warning: failed loading encoder firmware
> > > >  ivtv0 warning: Error loading firmware -3!
> > > >  ivtv0: Error -3 initializing firmware.
> > > >  ivtv0: Error -12 on initialization
> > > >  ivtv: probe of 0000:00:09.0 failed with error -12
> > > >  ivtv:  ====================  END INIT IVTV  ====================
> > > >
> > > >
> > > >
> > > >  modprob.conf;
> > > >
> > > >  alias eth0 3c59x
> > > >  alias eth1 e100
> > > >  alias snd-card-0 snd-via82xx
> > > >  options snd-card-0 index=0
> > > >  options snd-via82xx index=0
> > > >  remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; 
> > > > };
> > > > /sbin/modprobe -r --ignore-remove snd-via82xx
> > > >  alias tveeprom tveeprom-ivtv
> > > >  alias tuner tuner-ivtv
> > > >  alias tda9887 tda9887-ivtv
> > > >  alias msp3400 msp3400-ivtv
> > > >
> > > >
> > > >
> > > >  So I would assume that it has something to do with the firmware driver?
> > > >
> > >
> > > Have a look at the Wiki:
> > >
> > > http://ivtvdriver.org/index.php/Firmware
> > >
> > > N.
> > >
> > >
> > Thats funn,  as soon as I sent that message.  I released that it must
> > be the firmware that was the issue.  So I googled the message from
> > dmesg and came up to the same page you usggested...
> >
> > Now I have a video lnked to video0 as well as a video23 and 32 ...
> >
> > Off the bat I tried to test it with Tv Tiem Televisin viewer, but it
> > says that it can't open the device  video0...
> >
> > I was going to try and install Myth Tv but I get a yum error;
> > --> Populating transaction set with selected packages. Please wait.
> > ---> Downloading header for mythtv-suite to pack into transaction set.
> > http://dl.atrpms.net/fc4-i386/atrpms/stable/RPMS/mythtv-suite-0.18.1-56.at.i386.rpm:
> >  [Errno 4] IOError: HTTP Error 404: Date: Tue, 31 Jan 2006 08:46:03 GMT
> > Server: Apache/2.0.54 (Fedora)
> > Content-Length: 339
> > Connection: close
> > Content-Type: text/html; charset=iso-8859-1
> > Trying other mirror.
> > Error: failure: RPMS/mythtv-suite-0.18.1-56.at.i386.rpm from atrpms:
> > [Errno 256] No more mirrors to try.
> >
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to