Adam: I removed bttv.ko, but the error on cx88xx and cx8800 persist after deleting bttv.ko. I'll try moving to 0.3 to see if that changes anything.
FYI, I'm on FC4 with a single PVR-350 pulling rpms from Axel's ATRPMs site. George P.S. Here are the errors from just *below* the ivtv section of /var/log/messages Jul 21 15:02:57 localhost kernel: ivtv: Initialized WinTV PVR 350, card #0 Jul 21 15:02:57 localhost kernel: ivtv: ==================== END INIT IVTV ==================== Jul 21 15:02:57 localhost kernel: ivtv: ivtv_enc_thread: pid = 1199, itv = 0xd0a487a0 Jul 21 15:02:57 localhost kernel: ivtv: ivtv_dec_thread: pid = 1200, itv = 0xd0a487a0 Jul 21 15:02:57 localhost kernel: ivtv-osd: Framebuffer module loaded (attached to ivtv card id 0) Jul 21 15:02:57 localhost kernel: ivtv-osd: Framebuffer is at decoder-relative address 0x00510000 and has 1704960 bytes. Jul 21 15:02:57 localhost kernel: ivtv-osd: screen coords: [0 0] -> [720 480] Jul 21 15:02:57 localhost kernel: ivtv-osd: original global alpha = 208 Jul 21 15:02:57 localhost kernel: ivtv-osd: current OSD state = 39 Jul 21 15:02:57 localhost kernel: ivtv-osd: new global alpha = 208 (1 255 0) Jul 21 15:02:57 localhost kernel: ivtv-osd: framebuffer at 0xf5510000, mapped to 0xd1c90000, size 1350k Jul 21 15:02:57 localhost kernel: ivtv-osd: mode is 720x480x32, linelength=2880 Jul 21 15:02:57 localhost kernel: Console: switching to colour frame buffer device 90x30 Jul 21 15:02:57 localhost kernel: ivtv-osd: fb0: iTVC15 TV out frame buffer device Jul 21 15:02:57 localhost kernel: lirc_dev: IR Remote Control driver registered, at major 61 Jul 21 15:02:57 localhost kernel: cx88xx: Unknown symbol tveeprom_read Jul 21 15:02:57 localhost kernel: cx88xx: Unknown symbol tveeprom_hauppauge_analog Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_reset Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_call_i2c_clients Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_wakeup Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_risc_stopper Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_print_irqbits Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_set_scale Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_shutdown Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_vdev_init Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_core_put Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_audio_thread Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_core_irq Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_core_get Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_get_stereo Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_set_tvnorm Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_vid_irqs Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_risc_buffer Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_set_stereo Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_sram_channels Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_set_tvaudio Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_sram_channel_dump Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_sram_channel_setup Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_print_ioctl Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_free_buffer Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_boards Jul 21 15:02:57 localhost kernel: cx8800: Unknown symbol cx88_newstation Jul 21 15:02:57 localhost kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR) Jul 21 15:02:57 localhost kernel: ivtv: i2c attach [client=Hauppauge IR,ok] On 7/21/05, Adam Forsyth <[EMAIL PROTECTED]> wrote: > Yup, delete bttv.ko and run depmod. Should fix it. Although I'm using > 0.3 not 0.2, the log messages concerning bttv are the same. I'd still > reccomend going to 0.3 though as well. > > > On 7/21/05, George Galt <[EMAIL PROTECTED]> wrote: > > All: > > > > This is my first posting to the list, so I appologize if I tread on > > any established conventions. I've had several successful MythTV > > boxes, but this one -- an upgrade of an existing, functioning box -- > > has me puzzled. I keep getting messages about bttv/cx88x and tveeprom > > in the messages log file. Searching the list and google seems to only > > return issues when someone is using version 0.3+ of the ivtv driver, > > I'm using 0.2(rc3j) with kernel 2.6-12 on Fedora Core 4. > > > > Log file below. The actual messages are just after the IVTV section. > > > > I noted in this post from Adam Forsyth > > (http://www.gossamer-threads.com/lists/ivtv/devel/22177?search_string=Unknown%20symbol%20tveeprom_read;#22177) > > that he suggested deleting a file (apparently bttv, but I'm not sure). > > Has this approach worked for anyone? > > > > Does anyone have any suggestions -- even where to start? Should I > > simply move to the latest version 0.3? > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&opclick > _______________________________________________ > ivtv-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
