Jump to content

1,165 posts in this topic

Recommended Posts

Well, after a reboot, it doesnt work.. I have tried with and without caches to no result. I have other versions of OSX installed and I tried and it also didnt work....

I dont understand.. Here goes the screenshot as proof:

 

post-1517295-0-25935900-1456506840_thumb.png

 

I attach here my current IOREG

 

kosakgroove IOREG.zip

 

By looking at current IOREG, compared to the one I submitted when it was working, the SMCD device seems unchanged.... :(

 

 

post-1517295-0-00623700-1456506976_thumb.png

 

Could you guys give me some help?

Share this post


Link to post
Share on other sites
Advertisement

OMG! Thanks so much @legot28 thanks to your modification of the Info plist of my FakeSMC, more precisely the FNum key, and some other little tweaks in my DSDT, fan readings work great in my Asus Laptop hehe

 

post-1517295-0-67608400-1456602242_thumb.png

 

I got no other words than Thank you thank you thank you! :D

 

Share this post


Link to post
Share on other sites

Not working for me. Only disk is showing. Oo

Have you extracted with Pacifist the HWmonitor app and installed FakeSMC that came with it + Acpi , Cpu, Gpu and LPC sensors kexts?

 

Enviado desde mi XT1068 mediante Tapatalk

Share this post


Link to post
Share on other sites

JuniorGump must have forgotten to install the FakeSMC plugins (the ACPI/CPU/GPU/LPC sensors kexts). They either go alongside FakeSMC in its directory (/E/E or /L/E or /S/L/E depending on your own installation) or within a subfolder called PlugIns of the FakeSMC kext itself.

Share this post


Link to post
Share on other sites

Have you extracted with Pacifist the HWmonitor app and installed FakeSMC that came with it + Acpi , Cpu, Gpu and LPC sensors kexts?

 

Enviado desde mi XT1068 mediante Tapatalk

 

 

JuniorGump must have forgotten to install the FakeSMC plugins (the ACPI/CPU/GPU/LPC sensors kexts). They either go alongside FakeSMC in its directory (/E/E or /L/E or /S/L/E depending on your own installation) or within a subfolder called PlugIns of the FakeSMC kext itself.

 

Fakesmc on EFI and the rest on /S/L/E = Not work

All on EFI = Not work

Share this post


Link to post
Share on other sites

In all my hacks i haave Fake SMC and Sensor kexts in the same folder which is /System/Library/Extensions i believe that is the right way.. Only older versions of HWMonitor required the plugins to be inside fakesmc..

 

Enviado desde mi XT1068 mediante Tapatalk

Share this post


Link to post
Share on other sites

FakeSMC and its associated sensors will of course work/load/get cached from /S/L/E but the same will apply if they're placed in /L/E and/or if the sensors are manually placed in a created PlugIns subfolder of FakeSMC itself. That's how I use and run FakeSMC on all my Hacks.

 

@JuniorGump: what version of FakeSMc are you using? Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder?

Share this post


Link to post
Share on other sites

FakeSMC and its associated sensors will of course work/load/get cached from /S/L/E but the same will apply if they're placed in /L/E and/or if the sensors are manually placed in a created PlugIns subfolder of FakeSMC itself. That's how I use and run FakeSMC on all my Hacks.

 

@JuniorGump: what version of FakeSMc are you using? Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder?

please which version use you of clover?

Share this post


Link to post
Share on other sites

FakeSMC and its associated sensors will of course work/load/get cached from /S/L/E but the same will apply if they're placed in /L/E and/or if the sensors are manually placed in a created PlugIns subfolder of FakeSMC itself. That's how I use and run FakeSMC on all my Hacks.

 

@JuniorGump: what version of FakeSMc are you using? Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder?

 

>what version of FakeSMc are you using?

 

R: 3.4.1

 

6.16.1372

 

>Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder

 

Nops.

 

please which version use you of clover?

 

3424

 

@

@

 

I created the folder "PlugIns" within the Fakesmc kext and now worked. Thank you so much guys! :thumbsup_anim:

Share this post


Link to post
Share on other sites

Hello PPL

 

i have a skylake Asus notebook > http://www.insanelymac.com/forum/topic/312181-el-capitan-on-asus-x556ub-unresolved-problems/

 

and i can't to take working cpu sensors. everytime goes on kernel panic.

i have see other skylake notebooks and working,and i try these Fakesmc and sensors. all other sensors "working"

the cpu always goes on kernel panic... Any Idea about ?

Share this post


Link to post
Share on other sites

Hello PPL

 

i have a skylake Asus notebook > http://www.insanelymac.com/forum/topic/312181-el-capitan-on-asus-x556ub-unresolved-problems/

 

and i can't to take working cpu sensors. everytime goes on kernel panic.

i have see other skylake notebooks and working,and i try these Fakesmc and sensors. all other sensors "working"

the cpu always goes on kernel panic... Any Idea about ?

Might be lacking native power management as well as an adequate SkyLake SMBIOS. Without that you are doomed to crashes and instability.

Share this post


Link to post
Share on other sites

I hate to double-post, but I think this thread is more appropriate for my questions:

 

How to tell if ACPISensors is installed?  I installed it using the pkg, but it doesn't show in kextstat.  I do see LPCSensors and GPUSensors there.

 

Four out of five fans show the wrong speed, and CPU heatsink temp never changes.  Maybe this would be fixed by using ACPISensors?

 

Should I report this issue on GitHub?

Share this post


Link to post
Share on other sites

Since few versions back I can no longer auto update. It gives message thast new version exists, downloads & on install instantly gives error:

 

"An error occurred while relaunching HWMonitor, but the new version will be available next time you run HWMonitor."

 

New version is NOT available on next restart, as the same happens again

 

Manual upgrade works fine.

Share this post


Link to post
Share on other sites

All on EFI = Not work

 

Absolutely NOT the case. I have all kext in 10.10 folder on EFI next to FakeSMC & loads/works fine (with Clover)

FakeSMC and its associated sensors will of course work/load/get cached from /S/L/E but the same will apply if they're placed in /L/E and/or if the sensors are manually placed in a created PlugIns subfolder of FakeSMC itself. That's how I use and run FakeSMC on all my Hacks.

 

@JuniorGump: what version of FakeSMc are you using? Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder?

 

Plugin subfolder must be created inside Contents folder

Share this post


Link to post
Share on other sites

HWmonitor.app ,FAKESMC.kext and plugins  version 6.23.1417 is out !

 

http://www.hwsensors.com/content/01-releases/43-release-1417/HWSensors.6.23.1417.pkg

 

·  CPUSensors: Support for more Skylake models

·  Feature  GPUSensors: Initial Pascal support

·  Feature  HWMonitor: Use monospaced font in status bar (Thanks to MrMage for suggestion)

·  Bug Fix  Fixed installer issues

 

:thumbsup_anim:

Share this post


Link to post
Share on other sites

How is there Pascal support?  I still haven't seen any OS X Nvidia drivers for Pascal.

All I found is here from the author Natan Zalkin  : ( the word "initial" has a sense though ...) perhaps he took the preliminary information from LINUX/FREEBSD drivers ?

 

https://github.com/kozlek/HWSensors/commit/51937f7234c8e20c037326f7c4afe8ded5a10489

Share this post


Link to post
Share on other sites

@ROBASEFR, don't waste your time. Obviously Llamafilm cannot make the difference between graphics support for a dGPU at OS level and support for a piece of hardware for monitoring purposes at a sensor/driver level. Not quite the same thing... But I guess he has not understood yet that Kozlek's FakeSMC PlugIns play no part in graphics acceleration/support for GPUs. And as you quite rightly highlighted, the word "initial" was not used for nothing.

Share this post


Link to post
Share on other sites

Sorry I have a really dumb question.

 

How do I install this program?

 

I've run the .pkg installer, rebooted, and all I get the HWMonitor app is disk temp.

 

I have a Gigabyte GA-Z170X-UD3 and a i7-6700K. I used clover to make the install

 

Thanks

Share this post


Link to post
Share on other sites

Sorry I have a really dumb question.

 

How do I install this program?

 

I've run the .pkg installer, rebooted, and all I get the HWMonitor app is disk temp.

 

I have a Gigabyte GA-Z170X-UD3 and a i7-6700K. I used clover to make the install

 

Thanks

 

As already else where explained in this topic: For Clover use

 

First : Uninstall all the kexts (FakeSMC+ 4 sensors kexts)  from S/L/E !

 

  1. Extract the .pkg with Pacifist in a new folder ( Then you get: HWMonitor.app;FakeSMC.kext and 4 sensors kexts (Acpi, Cpu, Gpu and LPC) )
  2. Create a  "PlugIns" subfolder inside FakeSMC.kext/Contents
  3. Copy the 4 sensors.kexts inside that folder
  4. Copy the "New" FakeSMC.kext inside the EFI/CLOVER/KEXTS/10.12
  5. reboot

Good luck

Share this post


Link to post
Share on other sites

Hello there,

I have a question, I can't read fans (shows as "-").

I don't know what to do. I tried with LPC Sensors, and it says unsupported chip, and I don't know ACPI programming.

The LPC chip is, as says boot log:

 

SuperIODevice: [Fatal] found unsupported chip! ITE sequence ID=0x8613, Winbond sequence ID=0xffff

 

Thanks in advance

Share this post


Link to post
Share on other sites

Hello there,

I have a question, I can't read fans (shows as "-").

I don't know what to do. I tried with LPC Sensors, and it says unsupported chip, and I don't know ACPI programming.

The LPC chip is, as says boot log:

 

SuperIODevice: [Fatal] found unsupported chip! ITE sequence ID=0x8613, Winbond sequence ID=0xffff

 

Thanks in advance

Install OpenHardwareMonitor on windows. It will tell you the model number of your SuperIO chip.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By miliuco
      Install macOS 10.15 Catalina on Gigabyte P55-USB3 with Radeon RX 580 graphics card using a USB device created with the createinstallmedia command and Clover as bootloader. Instructions to install macOS 10.14 Mojave on this computer are almost identical, replacing Catalina app with Mojave, so this article is suitable for both versions of macOS. The Gigabyte P55-USB3 motherboard (and some others from the same brand with the P55 / H55 chipset) have made it easy to build a hackintosh and install macOS since 10 years ago. Although it is an old motherboard, the behavior with Mojave or Catalina is very good after changing the classic hard drive (HDD) for a solid state drive (SSD).

      Components of the hackintosh
      Gigabyte GA-P55-USB3 motherboard: P55 chipset, 1156 socket, ALC892 audio, Gigabit RTL8111D network, DDR3 RAM Intel Core i5-750 processor for socket 1156: 4 cores, 8MB cache, clock rate 2.66 GHz Fenvi FV-T919 wireless + Bluetooth card: PCI-Express, wifi is ac type, detected by macOS as Airport and Apple Bluetooth Radeon RX 580 8 GB graphics card: works OOB but with a few details to be considered, it has its own article.  
      Previous requirements
      Install macOS Catalina app in /Applications folder USB flash drive with at least 16GB prepared from Disk Utility with MBR partition scheme and formatted as Mac Os Plus (on older Gigabyte boards like mine, USB sticks partitioned with GUID scheme instead of MBR usually hang the system when booting) Recent version of Clover (I have used r5117) Recent versions of Lilu (at least 1.4.4) and WhateverGreen (at least 1.3.9) to fine-tune the behavior of the graphics card Recent version of RealtekRTL8111 (I have used 2.2.2) FaceSMC version 6.26-322 (newer versions disable automatic mounting of USB devices on my system).  
      Create install USB
      Run this command from Terminal (assuming the target device is called USB):
      Bash: sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USB /Applications/Install\ macOS\ Catalina.app
      Clover must be installed on the USB memory, I choose the following options:
      Bootloader > Install boot0af on the MBR CloverEFi > CloverEFI 64-bit SATA BIOS Drivers, 64 bit > Recommended drivers > FSInject + SMCHelper + XhciDxe BIOS Drivers, 64 bit > File System drivers > ApfsDriverLoader Install RC scripts on selected volume Optional RC scripts > Disable sleep proxy client.  
      You have to copy 4 kexts to the EFI/CLOVER/kexts/Other folder of the USB device: FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2. Regarding the config.plist file, the most significant is:
      Boot > kext-dev-mode = 1 in Boot arguments GUI > Theme embedded, EmbeddedThemeType Dark, Screen Resolution 1920x1080, Preboot in Hide Volume Graphics > blank, nothing is checked except if foxbox solution is used to have more than 2 connectors enabled RT Variables > 0x28 in BooterConfig and 0x67 in CsrActiveConfig SMBios > iMac14,2 Sytem Parameters> Yes in Inject Kexts and check Inject System ID.  
      Install macOS Catalina

      Boot from the USB device and choose Install macOS from Install macOS Catalina. The installation program runs until the PC restarts. Here choose Install macOS from HDD (the name of the volume you are installing macOS on). With RX 580 graphics card, the screen goes black in this second phase of the installation, it is a phase in which the user has nothing to do until the PC is restarted so you can let it work until the Clover menu again. You have to choose Boot macOS from HDDto boot the installed system from the hard disk, the screen is recovered and you can configure the account and the initial options. From this moment the screen works fine.

      In summary:
      Boot from USB > Clover menu > Install macOS from Install macOS Catalina > screen works fine Boot from USB > Clover menu > Install macOS from HDD > black screen Boot from USB > Clover menu > Boot macOS from HDD > screen works fine.  
      Install Clover and kexts on the hard drive

      Clover needs to be installed on the disk where we just installed macOS. Options are the same as when installing it on the USB memory. You also have to copy the 4 kexts (FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2) into the EFI/CLOVER/kexts/Other folder on the EFI partition of the disk. And review the config.plist file remembering the comments for the USB.

      If everything goes well, the computer starts from the hard disk with a running copy of macOS Catalina.
       
       

    • By Slice
      The thread splitted from HWSensors3.
       
      Tools to testing Radeon state.
      Load RadeonPCI.kext  
      RadeonPCI.kext.zip
       
      How to load
      sudo chown -R root:wheel ~/Downloads/RadeonPCI.kext sudo chmod -R 755 ~/Downloads/RadeonPCI.kext sudo kextutil -v ~/Downloads/RadeonPCI.kext and use RadeonDump utility
      RadeonDump1.zip
       
      Commands to see temperature
      Polaris
      ./RadeonDump1 -n 6b0,c0300014
      SeaIsaland
      ./RadeonDump1 -n 200,c0300014
       
      Old families
      ./RadeonDump1 -r 714,7f4
       
      Other possible methods to find a register for temperature
      ./RadeonDump1 -n 6b0,c0300e0c
      ./RadeonDump1 -n 6b0,1c5
      ./RadeonDump -n 6b0,d8200ca4
      ./RadeonDump -r 59800,59810
      ./RadeonDump -r 678,680

       
       
       
      01.12.2017
      Latest solution RadeonMonitor.kext here
      works for RX 460,480,580
      not works for HD7790, R9 290X?
       
      06.12.2017
      Here works also with HD7790, R9 290X
       
      14.12.2017
      Support VEGA here
       
      13.12.2017
      Version for test modern cards
      RadeonPCI5.kext.zip
       
      06.04.2020
      Version for Catalina
      RadeonPCI5-v2.kext.zip
    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
    • By Slice
      Guys,
      Don't mix 6.18 and 3.41.
       
      There are three different projects for monitoring temperatures, voltages, fans speed and other hardware parameters:
      Initially it was FakeSMC with plugins for producing SMC keys for hardware parameters for different hardware. But sometimes ago Kozlek separated own version of FakeSMC and producing new set of plugins while I stay with good working version 3. So..
      1. FakeSMC v3 with Hardware Sensors3  which I still supported.
      2. FakeSMC v6 (rev1800) by Kozlek and supported by Rehabman. AFAIK both are abandoned and the project is not supported. Or may be maintained by coauthors.
      3. New VirtualSMC by vit9696 with own set of sensors kexts. It depends on Lilu.kext. The project is in active development.
      All three project have incompatible interfaces sensors<->SMC so they are incompatible with each other.
       
      There are applications for monitoring hardware parameters and they commonly depends on these projects.
      1. iStat, iStatMenu, iStatPro compatible with real Macs because they use SMC keys just like those presents in real Macs.
      2. HWMonitorSMC by Navi (initial codes from Kozlek)  used in my HWSensors3.
      3. HWMonitor by Kozlek with graphics like in IntelPowerGadget used in his HWSensors version.
      4. HWMonitorSMC2 by Vector_Sigma tends to be universal supporting all project. It also may use sensors information produces by Apple graphics and by IntelPowerGadget.
       
      Let us discuss here differences and common ideas for this projects.
       
×