On 01/09/05 12:48, Jonas Meurer wrote:
On 07/01/2005 Michael T. Dean wrote:Don't manually load them (see below). It was good for testing, but now you've given enough information to explain what was happening, so it's no longer necessary (and likely to cause more problems than it solves)...
One or more modules is failing to load. It seems there's a problem with your tveeprom module--which may be caused by manually loading the module.i've also tried to load ivtv directly, what caused several other modules
to be loaded, namely i2c_core, i2c_algo_bit, tveeprom, tuner, saa7115,
saa7127 and msp3400.
That explains why tveeprom wasn't loading correctly--the bttv module (which your modprobe.conf said to load upon access of char-major-81) was loading eeprom before ivtv was able to load tveeprom--exactly as the error message stated.ok, up to now these conffiles hadMake sure your mod{ules,probe}.conf contains only:
# ivtv modules setup
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-81 bttv
Now that you've corrected your modprobe.conf, make sure you load ivtv by issuing the command, "modprobe ivtv" and nothing else.
Actually, that command belongs inside modprobe.conf. It will not execute properly from the command line (as you see below). It simply says to install ivtv-fb after installing ivtv. If you're not using the TV out, don't put it in there.i changed this now to your two lines.
afterwards i tested you command:
# install ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobeand if you want to load the ivtv framebuffer when you load ivtv,
install ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobe ivtv-fb
And then use *only* "modprobe ivtv" (do not insmod) to load the driver.
# ivtv-fb
install: unrecognized option `--ignore-install'
Try `install --help' for more information.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.2.0 (rc3b) loading
ivtv: Linux version: 2.6.9-amd64 preempt gcc-3.3
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv: Autodetected WinTV PVR 350 card
ivtv: Found an iTVC15 based chip
ACPI: PCI interrupt 0000:00:07.0[A] -> GSI 18 (level, low) -> IRQ 18
ivtv: VIA PCI device: 0x3188 vendor: 0x1106
tveeprom: Hauppauge: model = 48139, rev = K257, serial# = 7672850
tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38)
tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17)
tveeprom: audio_processor = CS5331 (type = 9)
Notice no module loading problems.
May be because you're using a Via motherboard. If it's something older than the KT-400 (and all the other 400-series) motherboards (especially the 266's and 133's), that's almost definitely going to be a problem. Although it's getting better (thanks to Chris), I still think the $40 I spent on a cheap SiS-based motherboard was the best $40 I spent. I couldn't run for more than 15 minutes (on a good day--average was less than 5) without a hard system lock.ivtv: i2c attach [client=tveeprom[0],ok] ivtv: Tuner Type 38, Tuner formats 0x00400e17, Radio: yes, Model 0x00ad2557, Revision 0x00000001 ivtv: PAL tuner detected ivtv: SECAM tuner detected ivtv: Radio detected tuner: Ignoring new-style parameters in presence of obsolete ones tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv: i2c attach [client=(tuner unset),ok] saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) saa7115: detecting saa7115 client on address 0x42 saa7115: writing init values ivtv: i2c attach [client=saa7115[0],ok] saa7115: status: (1E) 0x40, (1F) 0xc0 saa7127: video encoder driver version V 0.3 loaded saa7127: Selecting NTSC video Standard saa7127: Selecting S-Video+Composite saa7127: Turn WSS off saa7127: Widescreen Mode 4:3 Full Format saa7127: Selecting Normal Encoder Input saa7127: Enable Video Output ivtv: i2c attach [client=saa7127[0],ok] msp34xx: ivtv version msp34xx: init: chip=MSP3418W-B3, has NICAM support, simple (D) mode, simpler (G) no-thread mode msp34xx: $Id$ compiled on: Jan 6 2005 15:59:46 ivtv: i2c attach [client=MSP3418W-B3,ok] ivtv: Encoder revision: 0x02050032 ivtv: Encoder Firmware is buggy, use version 0x02040011 ivtv: Decoder revision: 0x02020023 ivtv: Configuring WinTV PVR 350 card with 9 streams ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total ivtv: Registered v4l2 device, streamtype 0 minor 0 ivtv: Create DMA stream 1 ivtv: Registered v4l2 device, streamtype 1 minor 32 ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total ivtv: Registered v4l2 device, streamtype 2 minor 224 ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total ivtv: Registered v4l2 device, streamtype 3 minor 24 ivtv: Create stream 4 ivtv: Registered v4l2 device, streamtype 4 minor 64 ivtv: Create DMA stream 5 using 16 65536 byte buffers 1048576 kbytes total ivtv: Registered v4l2 device, streamtype 5 minor 16 ivtv: Create stream 6 using 1024 2048 byte buffers 262144 kbytes total ivtv: Registered v4l2 device, streamtype 6 minor 228 ivtv: Create stream 7 ivtv: Registered v4l2 device, streamtype 7 minor 232 ivtv: Create DMA stream 8 ivtv: Registered v4l2 device, streamtype 8 minor 48 ivtv: Setting Tuner 38 ivtv: ivtv_enc_thread: pid = 5441, itv = 0xffffffffa00491a0 ivtv: ivtv_dec_thread: pid = 5442, itv = 0xffffffffa00491a0 tuner: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by ivtv i2c driver #0 ivtv: Setting audio matrix to input 3, output 1 ivtv: Switching standard to PAL. saa7115: decoder set norm PAL saa7115: set audio: 0x01 saa7127: Setting Encoder Video Standard saa7127: Set PAL Video Mode saa7127: Selecting PAL video Standard ivtv: Initialized WinTV PVR 350, card #0 ivtv: ==================== END INIT IVTV ==================== ivtv-osd: Framebuffer module loaded (attached to ivtv card id 0) ivtv-osd: Framebuffer is at decoder-relative address 0x00510000 and has 1704960 bytes. ivtv-osd: screen coords: [0 0] -> [720 576] ivtv-osd: original global alpha = 208 ivtv-osd: current OSD state = 39 ivtv-osd: new global alpha = 208 (1 255 0) ivtv-osd: framebuffer at 0xc9510000, mapped to 0xffffff0003010000, size 1620k ivtv-osd: mode is 720x576x32, linelength=2880 ivtv-osd: fb2: iTVC15 TV out frame buffer device
anyway, the test command 'cat /dev/video0 > my.mpg' still crashes my whole system. it gives endless output, but it's to fast to read and not possible to restore, as machine needs to be rebooted immediately.
is there a possibility, that kernel 2.6.10 and ivtv 0.3.2a do better
work?
As of now, you have your hardware configured correctly (with the possible exception of the tda9887 option--which would not affect stability, only tuning capability), so if you stick with the Via MB, you may be in for a long difficult journey trying to make it work. IMHO, $40 (or even $100) for a new motherboard is far less expensive than the time you'll spend trying to make the system work.
BTW, using the PVR-350's TV out on a Via makes an unstable system even less stable. If you're not using it, don't install ivtv-fb (i.e. leave the line above out of modprobe.conf).
HTH, and good luck with the MB.
Mike
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Ivtv-users mailing list Ivtv-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-users
