Kernel not recognizing your hardware? Problems with power management or PCMCIA? What hardware is compatible with Gentoo? See here. (Only for kernels supported by Gentoo.)
Well, it's not that simple. Several modules from the kernel are needed, but the ivtv driver itself is not included in the kernel. It has to be build seperatly and even needs extracts from the windows-firmware to be build. You can use portage to install it and the driver works fine with kernel 2.6. You should take a look at the manuals and How-To's about ivtv (or mythtv as frontend) to see what you need. I know there are also some threads in gentoo-forums about it.
I've emerged ivtv (which I had to unmask from package.mask). Now when I try to load ivtv I get this
localhost root # modprobe ivtv
FATAL: Error inserting ivtv (/lib/modules/2.6.9-epia0/extra/ivtv.ko): Unknown symbol in module, or unknown parameter (see dmesg)
And dmesg gives me this
PCI: Setting latency timer of device 0000:00:11.5 to 64
msp3400: Ignoring new-style parameters in presence of obsolete ones
i2c-core: driver i2c msp3400 driver registered.
saa7115: Ignoring new-style parameters in presence of obsolete ones
i2c-core: driver saa7115 registered.
saa7115: starting probe for adapter ISA main adapter (0x0)
saa7115: starting probe for adapter SMBus Via Pro adapter at 0500 (0x0)
i2c_adapter i2c-1: found normal i2c entry for adapter 1, addr 20<7>i2c_adapter i2c-1: Transaction (pre): CNT=00, CMD=1d, ADD=40, DAT0=50, DAT1=00
i2c_adapter i2c-1: SMBus busy (0x40). Resetting...
i2c_adapter i2c-1: Successfull!
i2c_adapter i2c-1: Error: no response!
i2c_adapter i2c-1: Transaction (post): CNT=00, CMD=1d, ADD=40, DAT0=50, DAT1=00
i2c_adapter i2c-1: found normal i2c entry for adapter 1, addr 21<7>i2c_adapter i2c-1: Transaction (pre): CNT=00, CMD=1d, ADD=42, DAT0=50, DAT1=00
i2c_adapter i2c-1: SMBus busy (0x40). Resetting...
i2c_adapter i2c-1: Successfull!
i2c_adapter i2c-1: Error: no response!
i2c_adapter i2c-1: Transaction (post): CNT=00, CMD=1d, ADD=42, DAT0=50, DAT1=00
ivtv: Unknown symbol video_unregister_device
ivtv: Unknown symbol video_device_alloc
ivtv: Unknown symbol video_register_device
ivtv: Unknown symbol video_usercopy
ivtv: Unknown symbol video_device_release
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Losing too many ticks!
TSC cannot be used as a timesource.
Possible reasons for this are:
You're running with Speedstep,
You don't have DMA enabled for your hard disk (see hdparm),
Incorrect TSC synchronization on an SMP system (see dmesg).
Falling back to a sane timesource now.
ivtv: Unknown symbol video_unregister_device
ivtv: Unknown symbol video_device_alloc
ivtv: Unknown symbol video_register_device
ivtv: Unknown symbol video_usercopy
ivtv: Unknown symbol video_device_release
ivtv: Unknown symbol video_unregister_device
ivtv: Unknown symbol video_device_alloc
ivtv: Unknown symbol video_register_device
ivtv: Unknown symbol video_usercopy
ivtv: Unknown symbol video_device_release
I have lirc working okay. I'm not sure if that matters or not. I'm guessing this has to do with the fact that packge.mask said that it would be a few months until ivtv is ready. Does anyone have any suggestions?
tomm1111 wrote:Follow this guide on kernel config and loading the ivtv drivers.
If you are using 2.6 kernel you need >ivtv-2.x if you are using a 2.4 kernel you need ivtv-0.1.9
I just don't understand where this is coming from - maybe there's an ivtv-devel posting I missed. I'm using 0.1.9-r4 (which is no longer in Portage). I've been using it with gentoo-dev-sources 2.6.5-r1, 2.6.8-r6 and 2.6.9-r6 (currently). It's the best, most stable version I've used with my PVR-350.
So, again, 0.1.9 Works For Me(tm) on the two most recent versions of the kernel. 2.6.6 and 2.6.7 gave me issues, so I stayed at 2.6.5 until 2.6.8-r6 came out. And I'm even using udev!
I had the same issue at one time it was that i compiled V4l and the bt848 drivers into the kernel while they need to be modules or otherwise won't usauly work
- Linux. The choice of a GNU generation.
Like Linux DVR's Check out http://Mythtvtalk.com
Just so everyone knows - I'm now using the (masked) ivtv ebuild, and it works well. The OSD is a bit slower in MythTV, but other than that I've had no problems for three weeks.
Now, if I can only fix qt-mysql after an ill-fated --newuse rebuild tongiht...
NightMonkey wrote:
tomm1111 wrote:Follow this guide on kernel config and loading the ivtv drivers.
If you are using 2.6 kernel you need >ivtv-2.x if you are using a 2.4 kernel you need ivtv-0.1.9
I just don't understand where this is coming from - maybe there's an ivtv-devel posting I missed. I'm using 0.1.9-r4 (which is no longer in Portage). I've been using it with gentoo-dev-sources 2.6.5-r1, 2.6.8-r6 and 2.6.9-r6 (currently). It's the best, most stable version I've used with my PVR-350.
So, again, 0.1.9 Works For Me(tm) on the two most recent versions of the kernel. 2.6.6 and 2.6.7 gave me issues, so I stayed at 2.6.5 until 2.6.8-r6 came out. And I'm even using udev!