My two Ubuntu installations have the same set of LTTng modules and tools (they were all built from the same git.lttng.org packages) but different kernels and installation histories. The "clean" machine has kernel linux-virtual (3.2.0-36-virtual), the other one has linux-generic (3.2.0-35-generic). After installing LTTng and rebooting, the clean machine does *not* load the lttng kernel modules, while the other one does. /etc/modules and /etc/modprobe.d are the same, the .ko are present in /lib/modules/<kernel>/extra in both cases. The clean machine's lttng kernel modules can be loaded using modprobe without demur, so there is no problem there.
At first I thought this was because the clean machine had not installed the dkms package yet, but adding it made no difference: the lttng modules do not load. How can I get the clean machine to load the lttng kernel modules at boot time? Daniel U. Thibault R & D pour la défense Canada - Valcartier (RDDC Valcartier) / Defence R&D Canada - Valcartier (DRDC Valcartier) Cyber sécurité pour les missions essentielles (CME) / Mission Critical Cyber Security (MCCS) Protection des systèmes et contremesures (PSC) / Systems Protection & Countermeasures (SPC) 2459 route de la Bravoure Québec, QC G3J 1X5 CANADA Vox : (418) 844-4000 x4245 Fax : (418) 844-4538 NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ> Gouvernement du Canada / Government of Canada <http://www.valcartier.drdc-rddc.gc.ca/> _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
