Closed irkonik closed 9 years ago
hirschmann
commented
9 years ago Comment out (or remove) the following line from nbfc\Core\StagWare.FanControl.Service\StagWare.FanControl.Service.csproj:
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\WCF\Microsoft.VisualStudio.ServiceModel.targets" />
Then try to build it again.
irkonik
commented
9 years ago Build succeeded.
Warnings:
/home/manjaro/nbfc/Windows/Setup/NbfcSetup/NbfcSetup.wixproj: warning : Could not find project file /usr/lib/mono/xbuild/Microsoft/WiX/v3.x/Wix.targets, to import. Ignoring.
/home/manjaro/nbfc/Windows/Setup/NbfcBootstrapper/NbfcBootstrapper.wixproj: warning : Could not find project file /usr/lib/mono/xbuild/Microsoft/WiX/v3.x/Wix.targets, to import. Ignoring.
/home/manjaro/nbfc/Windows/Setup/DriverSetupWixAction/DriverSetupWixAction.csproj: warning : Could not find project file /usr/lib/mono/xbuild/Microsoft/WiX/v3.x/Wix.CA.targets, to import. Ignoring.
3 Warning(s)
0 Error(s)
Time Elapsed 00:00:06.6866950I'll try it now :+1:
hirschmann
commented
9 years ago I decided to skip WCF config validation on build, because it is not really neccessary: 113b4c1e65b8f85f851ad4d47c26959b3732b40f
irkonik
commented
9 years ago Not necessary to reopen, just some new stuff after updating the files More Warnings:
Build succeeded.
Warnings:
/home/manjaro/nbfc/Windows/Setup/NbfcSetup/NbfcSetup.wixproj: warning : Could not find project file /usr/lib/mono/xbuild/Microsoft/WiX/v3.x/Wix.targets, to import. Ignoring.
/home/manjaro/nbfc/Windows/Setup/NbfcBootstrapper/NbfcBootstrapper.wixproj: warning : Could not find project file /usr/lib/mono/xbuild/Microsoft/WiX/v3.x/Wix.targets, to import. Ignoring.
/home/manjaro/nbfc/Windows/Setup/DriverSetupWixAction/DriverSetupWixAction.csproj: warning : Could not find project file /usr/lib/mono/xbuild/Microsoft/WiX/v3.x/Wix.CA.targets, to import. Ignoring.
/home/manjaro/nbfc/NoteBookFanControl.sln (Build) ->
(Build target) ->
/home/manjaro/nbfc/Core/Plugins/OpenHardwareMonitor/OpenHardwareMonitorLib.csproj (default targets) ->
/usr/lib/mono/4.5/Microsoft.CSharp.targets (CoreCompile target) ->
Hardware/Ring0.cs(35,11): warning CS0414: The private field `OpenHardwareMonitor.Hardware.Ring0.IOCTL_OLS_GET_REFCOUNT' is assigned but its value is never used
Hardware/Ring0.cs(37,11): warning CS0414: The private field `OpenHardwareMonitor.Hardware.Ring0.IOCTL_OLS_GET_DRIVER_VERSION' is assigned but its value is never used
Hardware/LPC/LMSensors.cs(107,22): warning CS0414: The private field `OpenHardwareMonitor.Hardware.LPC.LMSensors.LMChip.path' is assigned but its value is never used
Hardware/SMBIOS.cs(22,34): warning CS0414: The private field `OpenHardwareMonitor.Hardware.SMBIOS.table' is assigned but its value is never used
Hardware/Mainboard/SuperIOHardware.cs(40,28): warning CS0414: The private field `OpenHardwareMonitor.Hardware.Mainboard.SuperIOHardware.mutex' is assigned but its value is never used
8 Warning(s)
0 Error(s)Also, if I use
$ mono nbfc.exe load "something something"
it says:
connection refused
I tried "something\ something", also with the file extension, but it just does not accept anything.
Might not be a problem with the task above, since the service process does not keep running, as I can't find
start-nbfcservice.sh in my running tasks.
If there are logs, where do I find them?
hirschmann
commented
9 years ago You can ignore those warnings. All the stuff in nbfc/Windows (Setup, GUI) cannot be built on Linux and is excluded in the 'ReleaseLinux' build configuration anyway. The unused private fields will in fact be used if you run the code on Windows.
connection refused means the service is not running (note to self: write more meaningful error messages :wink:).
nbfc.exe load expects the config file name without extension.
start-nbfcservice.sh runs NbfcService.exe via mono-service, so you have to search for NbfcService.
mono-service logs to var/log/syslog.
irkonik
commented
9 years ago # start-nbfcservice.sh seems to crash pretty much instantaneously, since I can't find anything at all, even if I try $ sudo ./start-nbfcservice.sh && ps -A > ps_nbfc.txt && gedit ps_nbfc.txt
The only process remotely related to this would be "mono", which dies pretty much the moment after this.
Since I run systemd I don't have a syslog there :wink: $ journalctl shows a ton of info, but nothing related to mono or nbfc in any kind, which is really odd.
:panda_face: I really need to get into C#
EDIT: Okay, start-nbfcservice.sh is "wrong", as in it says: mono-service -m:NbfcService -l:/root/nbfcservice-lock "$(dirname -- "$0")/NbfcService.exe". If I execute it by hand, so sudo mono-service -m:NbfcService -l:/root/nbfcservice-lock "/home/manjaro/nbfc/Linux/bin/ReleaseLinux/NbfcService.exe" then it works, then I also can use the
mono nbfc.exe set command, the profiles not so much, but I gotta look into it.
hirschmann
commented
9 years ago I guess you didn't use the start-nbfcservice.sh in the ReleaseLinux folder, but the one in /home/manjaro/nbfc/Linux?!
Also ps -A does not list NbfcService, because it is not attached to a terminal.
Try ps -ax | grep NbfcService instead.
irkonik
commented
9 years ago Ah, shite, I never looked at the script properly, my bad. Obviously I should use the script in the proper directory.
The only way the process starts is if I type it by hand or "hard code" the path to the exe, which shouldn't be necessary, since you use "$(dirname -- "$0")/NbfcService.exe".
It's really really weird.
What makes it even weirder is, that the service now doesn't stay alive at all. Before the last reboot, I was able to set a value via set, but now it always says Connection refused.
Edit: [manjaro@manjaro ReleaseLinux]$ ps -ax | grep NbfcService 4584 pts/1 S+ 0:00 grep --color=tty -d skip NbfcService
Weird.
I have build errors, too afraid to try it :laughing: Log below
Thank you! :+1: