Never mind! I used the following to rebuild the module and it works now: $ make INSTALL_MOD_DIR=pvrusb2 -C /lib/modules/2.6.33.2/build M=/private/shared/Installs/pvrusb2-mci-20100424/driver CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_24XXX=y CONFIG_VIDEO_PVRUSB2_SYSFS=y CONFIG_VIDEO_PVRUSB2_DEBUGIFC=y CONFIG_VIDEO_ADV_DEBUG=y modules
And the garbage is gone! Have done few modprobe followed by modprobe -r. Looks good! -devsk ________________________________ From: devsk <[email protected]> To: Communications nexus for pvrusb2 driver <[email protected]> Sent: Sat, April 24, 2010 2:04:18 PM Subject: Re: [pvrusb2] New driver snapshot: pvrusb2-mci-20100424 Mike, I downloaded and went into driver directory and did a make. It build the driver correctly for 2.6.33.2 kernel but when I modprobe, I get the following unknown symbols. Do you know why that happens? Do I need to build some other stuff from this tar? [13824.873000] pvrusb2: Unknown symbol dvb_dmxdev_init [13824.874000] pvrusb2: Unknown symbol dvb_register_adapter [13824.874000] pvrusb2: Unknown symbol dvb_dmx_release [13824.874000] pvrusb2: Unknown symbol dvb_net_init .... -devsk ________________________________ From: Mike Isely <[email protected]> To: [email protected] Sent: Sat, April 24, 2010 1:43:55 PM Subject: [pvrusb2] New driver snapshot: pvrusb2-mci-20100424 A new pvrusb2 driver snapshot is available. The changes are: (+) Fix kernel oops caused by touching deleted memory after unregistration. This bug was introduced when we had started using video_device_node_name() to generate the device name. Rearranged the code a bit to let video_device_node_name() to do its thing before we actually unregister the device. (+) Implement ability to mark support for specific devices as being experimental. The Terratec Grabster AV400 is one such device (note that it isn't yet listed in any of the pvrusb2 documentation either). (+) Avoid use of stack-allocated memory for USB buffer I/O. The pvrusb2 driver has been doing this without issue for years; only now has this apparently become a problem in the Linux kernel. With the 2.6.34 kernel, stack-based USB buffers generate nasty messages to the kernel log. (+) Fix operation of RF tuner with Gotview hardware. This bug was introduced back when the driver implemented the sub-device model of module control. The root cause was that the tda9887 module needs to be explicitly loaded with the new model (with the old model it was automatic), and I had missed with this the Gotview device definition. As usual, the pvrusb2 web site can be found at: http://www.isely.net/pvrusb2/pvrusb2.html -Mike -- Mike Isely isely @ isely (dot) net PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8 _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
