Thanks Sanders for your reply. Sorry if I wasn't clear enough in my previous posts--I can't provide most of the information requested since ivtv isn't even getting loaded--it errors out before it gets to the START INIT IVTV part:
One thing I forgot to include is the actual console error: FATAL: Error inserting ivtv (/lib/modules/2.6.18.2-34 -default/kernel/drivers/media/video/ivtv/ivtv.ko): Unknown symbol in module, or unknown parameter (see dmesg) And /var/log/messages reports: Dec 29 08:05:28 linux kernel: ivtv: Unknown parameter `tda9887'
It does not lock up when ivtv is loaded since ivtv never gets loaded. I do not believe Suse provides the ivtv module. I had stated before that this was a clean Suse 10.2 install, but now that I think about it, it was an upgrade from Suse 10.2 RC1 which was an upgrade from Suse 10.2 beta 2. Hmm... maybe there's some left over files, but I doubt they would be from ivtv 0.4. I do know that the ivtv.ko it references above is definitely the one I just compiled. I believe the above answers questions 1-7 except 5. I'm assuming that the modules are in the right place because of the above console error. One thing you said: [And the error "ivtv: Unknown parameter `tda9887'" proves you still have this option set] gives me something to go on. Let me grep for tda9887 and see if it shows up in a second file. Thanks! -S On 12/29/06, Sander Sweers <[EMAIL PROTECTED]> wrote:
Shermann Min wrote: > Tobias, > > Yes, something seems to have changed with 10.2. As for my tuner type > (it's a > PVR-250, by the way), I had to add > > options ivtv tda9887=0 tuner=39 > > to /etc/modprobe.d/tv when I was using 10.0. See > http://www.mjmwired.net/kernel/Documentation/video4linux/CARDLIST.tuner And the error "ivtv: Unknown parameter `tda9887'" proves you still have this option set. There is no option by this name anymore in 0.8. And start providing the info from the asking for help link I gave earlier. If you do not provide the info people can only guess and make assumptions as to what could be the problem. 1: Does it lockup when ivtv is loaded? 2: Is the module at all loaded 3: Does Suse also provide the ivtv module? If so try that one or make sure it is NOT installed. 4: Did you do an upgrade from 10.0? If so there might be old ivtv 0.4 modules so make sure they are deleted. 5: Are the modules installed in the correct module directory? 6: Provide the init ivtv message from dmesg. If you do not have this ivtv never got loaded. dmesg | tac | sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p; /= START INIT IVTV =/q' | tac 7: Do you get an error when you "modprobe ivtv"? If so provide the error message and look in dmesg for more info. Greets Sander _______________________________________________ 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
