The drivers for these two features are integrated and thus there will not be a module file: I am suggesting you do not need to build a kernel, but if you did, then you’d start with either a “_defconfig” or “/proc/config.gz” (after editing CONFIG_LOCALVERSION), and this would already have both the ACM and RTL drivers selected (sometimes in integrated format, and in some cases in module format). Note that Realtek (RTL) drivers are used for the wired ethernet, and are rather commonly used in Linux, and so it doesn’t hurt to just leave these in place. Regardless, it looks like the modules are already there and not in need of creation. Without this anything in module format will fail. When you run the command “uname -r”, do you see “4.9.140-tegra”? Modules are searched for at “/lib/modules/$(uname -r)/kernel/”, and if you’ve modified the kernel Image, then this has to be set correctly through CONFIG_LOCALVERSION="-tegra". So I went to /lib/modules/4.9.140-tegra/kernel/drivers/net/wireless/realtekbut there’s multiple libraries rtl818x rtl8xxxu rtlwifiand in each is. Scripts/Makefile.build:649: recipe for target 'drivers/net' failed Scripts/Makefile.build:649: recipe for target 'drivers/net/wireless' failed
Scripts/Makefile.build:509: recipe for target 'drivers/net/wireless/built-in.o' failed Rtw_mp.c:(.text+0x292d0): multiple definition of `issue_probereq_p2p'ĭrivers/net/wireless/realtek/rtl8812au/built-in.o:rtw_mp.c:(.text+0x282cc): first defined here Rtw_mp.c:(.text+0x1162c4): multiple definition of `phydm_clear_kfree_to_rf_8198f'ĭrivers/net/wireless/realtek/rtl8812au/built-in.o:rtw_mp.c:(.text+0x10adc8): first defined hereĭrivers/net/wireless/realtek/rtl8814au/built-in.o: In function `issue_probereq_p2p': Rtw_mp.c:(.text+0x3823c): multiple definition of `survey_done_set_ch_bw'ĭrivers/net/wireless/realtek/rtl8812au/built-in.o:rtw_mp.c:(.text+0x37630): first defined hereĭrivers/net/wireless/realtek/rtl8814au/built-in.o: In function `phydm_clear_kfree_to_rf_8198f': Make: *** Error 2 realĐm26.202sĪnd then this error: drivers/net/wireless/realtek/rtl8814au/built-in.o: In function `survey_done_set_ch_bw': Makefile:1104: recipe for target 'drivers' failed Then I ran makeKernel.shbut got these errors: It asked if I wanted to use a certain realtek wifi related driver/card (can’t get the specific line anyone), I tried to indicate Yes but it wouldn’t take it so I put M. I specified my L4t target (32.2.0) and ran the script. I proceeded to rebuild the 4.9 kernel, and found another guide from Jetsonhacks.
Thanks for the help I run zcat /proc/config.gz | grep ACM I get: Sometimes the expected file name is changed by udev, so if the device special file is missing, you might want to insmod while monitoring “dmesg -follow” to see if a rename has occurred. Note: When the module is inserted, and if the hardware is detected, then this will create the file in “/dev/”.
#Usb cdc acm driver install
You only need a module, but I always advise that you try building a full kernel once just for sanity checking (the configuration matters, and you are more likely to find out about bad configurations from a full kernel build…but only install the module with a file copy, don’t bother installing the full kernel). If your release is R32.3.1 (the latest release, verify with “head -n 1 /etc/nv_tegra_release”), then downloading full kernel source using source_sync.sh would use tag “ tegra-l4t-r32.3.1”. …however, the tag used for “source_sync.sh” will need to be adjusted for your release. This is also for an older kernel (to compile natively on a Jetson), but details shouldn’t be much different:
#Usb cdc acm driver Pc
Official documents explain cross compile of a kernel from a host PC (and kernel modules), but you can do a native compile from the Jetson and not worry about cross compilers. The official documentation for your particular L4T release gives that information, but you can also ask here since some of the details may not always be clear. Learning to build a kernel module without a script seems complicated at first, but in reality is not as bad as it looks, and is worth knowing. The problem is that the article you saw has custom scripts for the older kernel. What do you see on your running system from “ zcat /proc/config.gz | grep ACM” (these are various ACM features the kernel was or was not configured for)?Īctual procedure for building a 4.9 kernel shouldn’t be much different than building for a 4.4 kernel.
0 kommentar(er)
