Make: Leaving directory ‘/usr/src/kernels/linux-4.18-rc1’ Make: Target ‘_modpost’ not remade because of errors. Make: Target ‘modules’ not remade because of errors.ĮRROR: An error occurred while performing the step: “Checking to see whether the nvidia kernel module was successfully built”. kernel /usr/bin/make -k -j8 NV_KERNEL_MODULES='nvidia' NV_EXCLUDE_KERNEL_MODULES='' SYSSRC='/lib/modules/4.18.0-rc1-maverick/source' SYSOUT='/lib/modules/4.18.0-rc1-maverick/build' failed with the following output: See /var/log/nvidia-installer.log for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at Includes new parameter ALLOW_ECHO_FRAMES that allows the reception of self-sent messages Please see the file ‘/var/log/nvidia-installer.log’ for details. #Impulse rc driver fixer an error o download# Includes new parameter PCAN_DEVICE_PART_NUMBER to get the part number of a PCAN hardware (a.k.a.New set of samples in console mode in all supported programming languages (except Java).The function CAN_InitializeFD returned a wrong error code when the channel was already in use by PCAN-View, but with a different bit rate as the requested one.The function CAN_Initialize returned a wrong error code when the channel to be initialized was already connected by PCAN-View as 'FD' channel.The functions CAN_GetValue and CAN_SetValue returned a wrong error code when the channel used was wrong or PCAN_NONEBUS.The function 'CAN_LookUpChannel' returned a wrong error code when the buffer for the channel handle was NULL.The function 'CAN_GetErrorText' returned PCAN_ERROR_OK when the language code passed to the function was invalid or not found.#Impulse rc driver fixer an error o download#.#Impulse rc driver fixer an error o code#.Or maybe even see about using Betaflight if I can get my baro sensor to work. When I can find something definite on what the latest firmware I can flash on Rev 5, I'll reflash with the latest. But had enough for one day and just reflashed FC with Cleanflight 1.14.0.

So flashed the Betaflight firmware but when setting FC up, notice my baro was gone. Then in recovering old ground I discovered.' '.but the installer didn't work so I went to Device Manager, did an 'Update Drivers' and manual selected the folder with the 'Serial Enumeration' and VOILA.FC talks to PC. I downloaded and installed the 'STM32' drivers.again. But no matter how many times I ran Zadig and ImpulseRC and several other apps, just could not get the FC to talk to my PC.

I had originally installed this.'CP210x_Windows_Drivers' and thought I was good. But just could not connect with any of the configurators.

First, it's not got the MultiWii firmware, it actually had Cleanflight 1.11.0. What a nightmare trying to figure out why it wouldn't connect.