Make install: Unable to determine COMPILER_TYPE error.

[cowala]

I know WakeOnLan (WOL) works because I just tested it on windows, but when I shutdown FreeNas the ethernet lights are off.
I managed to mount a flash drive in shell and extract the latest intel i210 ethernet driver but I can't install it.
Some compiler problem. I couldn't find enough information about setting the compiler type.
I'm still at the bottom of Linux learning curve... please provide ample information.

[root@freenas /usr/New_Eth_Driver]# ls
drvr igb.4.gz src
[root@freenas /usr/New_Eth_Driver]# make install
make: don't know how to make install. Stop

make: stopped in /usr/New_Eth_Driver
[root@freenas /usr/New_Eth_Driver]# make install igb.4.gz
make: don't know how to make install. Stop

make: stopped in /usr/New_Eth_Driver
[root@freenas /usr/New_Eth_Driver]# cd src
[root@freenas /usr/New_Eth_Driver/src]# ls
Makefile e1000_api.h e1000_i210.h e1000_manage.h e1000_nvm.h e1000_phy.h if_igb.c
e1000_82575.c e1000_defines.h e1000_mac.c e1000_mbx.c e1000_osdep.c e1000_regs.h if_igb.h
e1000_82575.h e1000_hw.h e1000_mac.h e1000_mbx.h e1000_osdep.h e1000_vf.c igb.4
e1000_api.c e1000_i210.c e1000_manage.c e1000_nvm.c e1000_phy.c e1000_vf.h
[root@freenas /usr/New_Eth_Driver/src]# make install
make: "/usr/share/mk/bsd.compiler.mk" line 39: Unable to determine compiler type for cc. Consider setting COMPILER_TYPE.

 

[Jailer]

I'm still at the bottom of Linux learning curve... please provide ample information.

Well that's good because FreeNAS is based on FreeBSD not Linux.

The i210 driver is already supported by FreeBSD and has been for some time. A list of your hardware might help in diagnosis.

 

[joeschmuck]

I'm still at the bottom of Linux learning curve... please provide ample information.

FreeNAS is BSD, not Linux. They are different.

I just tested it on windows, but when I shutdown FreeNas the ethernet lights are off.

FreeNAS is not Windows. You are better off with doing an internet serach on something like "freenas wol".

 

[cowala]

Hello guys, I did a lot of research on wol for the past week or so but I am getting no where. I reached to my own conclusion about installing the latest ethernet driver. Which hardware exactly should I post? I put everything in my signature.

 

[Jailer]

This may sound like a silly question but is WOL enabled in the BIOS?

 

[cowala]

This may sound like a silly question but is WOL enabled in the BIOS?

Yes, I just tested WOL packet on a windows drive and it worked. I unplugged the drive and plugged the FreeNAS usb, let it boot and shutdown but the lights are OFF.

 

[cowala]

ifconfig output:
I don't see any WOL in the options

Code:

igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500	
		options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS
UM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>								
		ether 38:dx:xx:xx:xx:xx										  
		inet 192.168.50.50 netmask 0xffffff00 broadcast 192.168.50.255		
		nd6 options=9<PERFORMNUD,IFDISABLED>									
		media: Ethernet autoselect (1000baseT <full-duplex>)					
		status: active														
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500	
		options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS
UM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>								
		ether 38:dx:xx:xx:xx:xx											
		inet 192.168.100.4 netmask 0xffffff00 broadcast 192.168.100.255		
		nd6 options=9<PERFORMNUD,IFDISABLED>									
		media: Ethernet autoselect											
		status: no carrier													
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384			
		options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>				
		inet6 ::1 prefixlen 128												
		inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3							
		inet 127.0.0.1 netmask 0xff000000									
		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

 

[joeschmuck]

Yes, I just tested WOL packet on a windows drive and it worked. I unplugged the drive and plugged the FreeNAS usb, let it boot and shutdown but the lights are OFF.

I just want to make sure that I fully understand what you are saying...

You took a windows drive, booted up the board, then you powered off the computer as in Shutdown, not one of the Sleep states? What were the status of the LAN Led's while powered off under Windows?

 

[cowala]

I just want to make sure that I fully understand what you are saying...

You took a windows drive, booted up the board, then you powered off the computer as in Shutdown, not one of the Sleep states? What were the status of the LAN Led's while powered off under Windows?

dude, I don't really remember which light was on but I think it was a solid green. If you want I can do it again?
The important thing is that it worked. I even tested unplugging the power cable until all the motherboard light died, then I plugged the power cable again and was able to WOL. This means that the BIOS is set up correctly.

I removed the windows drive and booted the FreeNAS usb... shutdown... no LAN lights and no WOL.

EDIT: I forgot to mention that I had to install the latest windows drivers before I got it to work with windows.

 

[joeschmuck]

So what were the WOL options in the BIOS?

 

[SweetAndLow]

Google search freenas wol?

You don't as drivers to freenas so don't go down that rabbit hole.

I don't think I have seen a post of someone getting wol too ever work correctly with freenas. Most people just leave it running all the time since it probably better for the system, less wear and tear.

Sent from my Nexus 5X using Tapatalk

 

[Jailer]

Seems to be a FreeBSD issue after a little searching.

 

[cowala]

So what were the WOL options in the BIOS?

dude the BIOS is doing what it is supposed to do. It works with win 10. The problem is with FN. Unless there is something specific that happens between the BIOS and FN during shutdown... the BIOS is and will be innocent until proven guilty.

Google search freenas wol?
You don't as drivers to freenas so don't go down that rabbit hole.

This is my first FN and I didn't put any data on the system yet so this is my chance to tweak and fiddle now while I have the chance.

I don't think I have seen a post of someone getting wol too ever work correctly with freenas. Most people just leave it running all the time since it probably better for the system, less wear and tear.

This should be an offsite backup and it will be powered on once every 1+ month. No use keeping it running all the time.
I have a long CAT5e cable from the hardware to my daily machine... I need to plug the cable, do a manual backup and unplug it again.
Getting WOL will be very convenient.

Seems to be a FreeBSD issue after a little searching.

This is why I'm trying to manually update the driver. It worked with win10 and I hope it will work with FreeBSD.
Any help on the Compiler_Type?

 

[joeschmuck]

But you should be able to turn it on via the dedicated management connection, but that is not WOL.

 

[cowala]

But you should be able to turn it on via the dedicated management connection, but that is not WOL.

It just worked using a NON-dedicated management connection with win10 after a driver update
EDIT: I just had an idea... I'll try to wak FN from the dedicated management connection.
EDIT: FN can't see the management port :\

 

[joeschmuck]

dude the BIOS is doing what it is supposed to do. It works with win 10. The problem is with FN. Unless there is something specific that happens between the BIOS and FN during shutdown... the BIOS is and will be innocent until proven guilty.

Dude, I was asking for the options. Lets say you have three options: Disabled, Software, BIOS (or similar). Maybe a change to "BIOS" would allow you to make it work. Of course you might have two options "Disable, Enable". This is why I asked.

I didn't realize you were going to use it at a remote worksite so thinking outside the box, you could set up a VPN and set up a link to go directly to the dedicated management port and then power it on remotely. If WOL isn't supported for your setup then that may be the only option. And if you think about it, you would probably want this setup anyway so you could troubleshoot any issues such as the system fails to power up or FreeNAS hangs, you could rebuild it remotely.

 

[Jailer]

This is why I'm trying to manually update the driver. It worked with win10 and I hope it will work with FreeBSD.
Any help on the Compiler_Type?

As @SweetAndLow said you don't want to be doing this. Besides any changes you make will be overwritten the next time you update.

Your best bet would be to submit a feature request to have this added to FreeNAS.

 

[cowala]

Dude, I was asking for the options. Lets say you have three options: Disabled, Software, BIOS (or similar). Maybe a change to "BIOS" would allow you to make it work. Of course you might have two options "Disable, Enable". This is why I asked.

Okay... sound reasonable... I've been through the BIOS and the only options available were:
Wake on PCIE set to ENABLED.
Some other options about S3 and S5 states. Unchanged by me.

if you think about it, you would probably want this setup anyway so you could troubleshoot any issues such as the system fails to power up or FreeNAS hangs, you could rebuild it remotely.

Interesting option but I need to spend a lot of time learning about management port and software. I only need to get it to run for now. If maintenance is required I can get to it anytime later as it is just a backup with mirrors.

As @SweetAndLow said you don't want to be doing this. Besides any changes you make will be overwritten the next time you update.

Your best bet would be to submit a feature request to have this added to FreeNAS.

I don't plan to update if I got it to run stable. Submitting a request will take a lot of time. I need it to run now.
I tried to squeeze any chance I had to try and test it over the past week and it got me nowhere.
Any help on the COMPILER_TYPE? Why isn't Intel's own driver created for FreeBSD running on FreeBSD???