{"action":"created","issue":{"url":"https://api.github.com/repos/01org/thunderbolt-software-user-space/issues/8","repository_url":"https://api.github.com/repos/01org/thunderbolt-software-user-space","labels_url":"https://api.github.com/repos/01org/thunderbolt-software-user-space/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/01org/thunderbolt-software-user-space/issues/8/comments","events_url":"https://api.github.com/repos/01org/thunderbolt-software-user-space/issues/8/events","html_url":"https://github.com/01org/thunderbolt-software-user-space/issues/8","id":203521304,"number":8,"title":"Ubuntu Xenial installation","user":{"login":"philippelabat","id":1538854,"avatar_url":"https://avatars.githubusercontent.com/u/1538854?v=3","gravatar_id":"","url":"https://api.github.com/users/philippelabat","html_url":"https://github.com/philippelabat","followers_url":"https://api.github.com/users/philippelabat/followers","following_url":"https://api.github.com/users/philippelabat/following{/other_user}","gists_url":"https://api.github.com/users/philippelabat/gists{/gist_id}","starred_url":"https://api.github.com/users/philippelabat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/philippelabat/subscriptions","organizations_url":"https://api.github.com/users/philippelabat/orgs","repos_url":"https://api.github.com/users/philippelabat/repos","events_url":"https://api.github.com/users/philippelabat/events{/privacy}","received_events_url":"https://api.github.com/users/philippelabat/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-01-26T23:36:24Z","updated_at":"2017-01-27T14:54:49Z","closed_at":null,"body":"Hello everybody,\r\n\r\nSo i was following this thread in the kernel mailing list for a while now! I've tried yesterday to pull the mainline kernel (using these instructions: http://askubuntu.com/a/724909), applied the patches needed for ubuntu (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5/) and applied the Thunderbolt Patch V9 found in the mailing list (https://lkml.org/lkml/2016/11/9/341).\r\n\r\nAfter an hour, everything was ready. I installed the new kernel and started following procedures to install the daemon & CLI tools. This is what i get:\r\n\r\n```\r\n-- reload systemd done\r\nCMake Warning at /home/phil/thunderbolt-software-user-space/ThunderboltService/Linux/post_install_script.cmake:46 (message):\r\n  start thunderbolt daemon failed\r\n\r\n  Result - 1\r\n\r\n  Output -\r\n\r\n  Error - Job for thunderbolt.service failed because the control process\r\n  exited with error code.\r\n\r\n  See \"systemctl status thunderbolt.service\" and \"journalctl -xe\" for\r\n  details.\r\n```\r\n\r\n```\r\nJan 26 18:30:18 Jarvis systemd[1]: thunderbolt.service: Start request repeated too quickly.\r\nJan 26 18:30:18 Jarvis systemd[1]: Failed to start Thunderbolt Manager.\r\n-- Subject: Unit thunderbolt.service has failed\r\n-- Defined-By: systemd\r\n-- Support: http://www.ubuntu.com/support\r\n--\r\n-- Unit thunderbolt.service has failed.\r\n--\r\n-- The result is failed.\r\nJan 26 18:30:18 Jarvis systemd[1]: thunderbolt.service: Unit entered failed state.\r\nJan 26 18:30:18 Jarvis systemd[1]: thunderbolt.service: Failed with result 'start-limit-hit'.\r\nJan 26 18:31:21 Jarvis sudo[10423]:     phil : TTY=pts/5 ; PWD=/home/phil/thunderbolt-software-user-space/libtbtfwu-build ; USER=root ; COMMAND=/usr/bin\r\nJan 26 18:31:21 Jarvis sudo[10423]: pam_unix(sudo:session): session opened for user root by phil(uid=0)\r\nJan 26 18:31:21 Jarvis sudo[10423]: pam_unix(sudo:session): session closed for user root\r\nJan 26 18:31:47 Jarvis systemd[1]: sys-module-thunderbolt.device: Job sys-module-thunderbolt.device/start timed out.\r\nJan 26 18:31:47 Jarvis systemd[1]: Timed out waiting for device sys-module-thunderbolt.device.\r\n-- Subject: Unit sys-module-thunderbolt.device has failed\r\n-- Defined-By: systemd\r\n-- Support: http://www.ubuntu.com/support\r\n--\r\n-- Unit sys-module-thunderbolt.device has failed.\r\n--\r\n-- The result is timeout.\r\nJan 26 18:31:47 Jarvis systemd[1]: sys-module-thunderbolt.device: Job sys-module-thunderbolt.device/start failed with result 'timeout'.\r\nJan 26 18:31:49 Jarvis sudo[10623]:     phil : TTY=pts/5 ; PWD=/home/phil/thunderbolt-software-user-space/tbtfwucli-build ; USER=root ; COMMAND=/usr/bin\r\nJan 26 18:31:49 Jarvis sudo[10623]: pam_unix(sudo:session): session opened for user root by phil(uid=0)\r\nJan 26 18:31:49 Jarvis sudo[10623]: pam_unix(sudo:session): session closed for user root\r\nJan 26 18:32:10 Jarvis tbtfwucli[10644]: [1485473530195] ERR: Daemon communication failure while getting controller list: The name com.Intel.Thunderbolt\r\nlines 1718-1747/1747 (END)\r\n```\r\n\r\nI am starting to wonder if the Thunderbolt kernel patch got applied properly, is there any ways of making sure it was?\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/01org/thunderbolt-software-user-space/issues/comments/275683467","html_url":"https://github.com/01org/thunderbolt-software-user-space/issues/8#issuecomment-275683467","issue_url":"https://api.github.com/repos/01org/thunderbolt-software-user-space/issues/8","id":275683467,"user":{"login":"philippelabat","id":1538854,"avatar_url":"https://avatars.githubusercontent.com/u/1538854?v=3","gravatar_id":"","url":"https://api.github.com/users/philippelabat","html_url":"https://github.com/philippelabat","followers_url":"https://api.github.com/users/philippelabat/followers","following_url":"https://api.github.com/users/philippelabat/following{/other_user}","gists_url":"https://api.github.com/users/philippelabat/gists{/gist_id}","starred_url":"https://api.github.com/users/philippelabat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/philippelabat/subscriptions","organizations_url":"https://api.github.com/users/philippelabat/orgs","repos_url":"https://api.github.com/users/philippelabat/repos","events_url":"https://api.github.com/users/philippelabat/events{/privacy}","received_events_url":"https://api.github.com/users/philippelabat/received_events","type":"User","site_admin":false},"created_at":"2017-01-27T14:54:49Z","updated_at":"2017-01-27T14:54:49Z","body":"So `lsmod | grep thunderbolt` is returning nothing so i guess i screwed up the installation of the kernel patch on the ubuntu kernel.\r\n\r\nHere is my setup: ```\r\nMotherboard:  GIGABYTE GA-Z270X-UD5\r\nCPU:  Intel Core i5-7500 3.4 GHz LGA 1151\r\nOS: Ubuntu 16.10 (Kernel 4.10)\r\n```\r\n\r\n```phil@Jarvis:~$ lspci | grep \"Thunderbolt\"\r\n07:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)\r\n08:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)\r\n08:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)\r\n08:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)\r\n09:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02)```\r\n\r\nWhat i am trying to achieve here is the following: My Mac Pro is linked to a TB2 - TB3 adapter, which is connected to the Ubuntu machine. My goal is to establish a link for File Transfer.\r\n\r\nFurther more: ```phil@Jarvis:/lib/modules/4.10.0-rc5-thunderbolt/kernel/drivers/thunderbolt$ sudo insmod thunderbolt.ko\r\ninsmod: ERROR: could not insert module thunderbolt.ko: Function not implemented```"}}
{"actor":{"display_login":"philippelabat"}}