On Wed, Jan 7, 2009 at 06:36, Karl Newman <[email protected]> wrote: > I have a dual-tuner analog Hauppauge PVR-500 (basically two PVR-150s in one > card) on Gentoo. Following a kernel upgrade from 2.6.25 to 2.6.26 (or > 2.6.27) using make oldconfig, the ivtv module seemed to load, but watching > Live TV with MythTV, I was unable to change channels. I discovered the > tuner_simple and tuner_types modules were not loaded and in fact were not > even being built. So, I enabled Customize tuner types and selected the > appropriate subitems as modules. They were built and then I could modprobe > ivtv and they would load. However, on a reboot, the ivtv module was > automatically loaded but tuner_simple and tuner_types were not again, with > the same symptom of not being able to change channels. Unloading and > reloading the ivtv module seemed to make it work again. LiveTV worked, but I > had reports that the wrong channel was being recorded for regularly > scheduled recordings. I didn't have time to investigate, but it's possible > the tuner_simple and tuner_types module was loaded for only one of the > PVR-500's tuners. Even having an entry for ivtv and tuner_types and > tuner_simple in /etc/modules/autoload.d/kernel-2.6 to manually modprobe the > modules didn't seem to work. It would properly load the module only when > manually modprobe'd. So I rolled everything back to 2.6.25 for later > investigation.
You should not need to compile as modules for kernel 2.6.26 but it is still recommended to do so. The main reason for this was that ivtv needs to load firmware. Previously (pre 2.6.24 I believe) when ivtv is build in kernel it immeditaly wanted to load the firmware. This failed as no filesystems where loaded yet. Hans fixed this to delay firmware loading untill the device is first acessed. I know gentoo seems to think you need to have CONFIG_VIDEO_HELPER_CHIPS_AUTO *deselected* but this is not true. It was needed before ivtv was merged with mainline kernel. When this is selected it makes sure that all the other needed modules are automatically selected in the kernel config (iow no need to customize tuners config). I think this is the reason why you are having issues with making this work. Also make sure you have CONFIG_KMOD as this makes the dependant modules load automatically when modprobing ivtv. > I looked into the kernel config and also read through the ebuild file for > ivtv-utils (1.3.0) and saw a note that said to build I2C and V4L drivers as > modules or the driver wouldn't work. I went back through the kernel config > and noticed I had a few things compiled into the kernel instead of modules. > I finally changed the top-level I2C and V4L menu options to modules > (CONFIG_VIDEO_DEV=m and CONFIG_I2C=m) and that built everything under them > as modules. After rebooting, all the modules were properly loaded and > channel tuning worked without issue. If ivtv really fails to work with kernel 2.6.26 and having CONFIG_VIDEO_DEV and CONFIG_I2C in kernel I consider it a bug and should be reported to the ivtv developers so they can fix this. Maybe Hans knows about this but I do not remember seeing a report on the ivtv-user or devel list. Hans? Greets Sander _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
