Does someone have Netgate SG-2100 internal slot?

doronl15

@stephenw10 Hi,
i've got my SG2100 back after RMA procedure...
However, i'm now afraid to do the move to 2.5.0 Beta from the GUI.
do you have a site where i can download an iso image of aarch64 2.5.0?

Doron.

doronl15

@doronl15 Hi Stepen,
It happened again :(
I upgraded from 2.4.5_1 to 2.5.0 DEVEL via the web gui and again the system stop booting in uboot stage.
Do you happen to have an iso image so I can try to upgrade from USB stick?

Doron

stephenw10

Let me see what I can do.

There is a know issue upgrading right now but if you replace the uboot envs, as I assume you did before, it will boot correctly and continue into the 2.5 upgrade. I just did exactly that on a test device here.

Steve

doronl15

@stephenw10 Hi,
Are you sure if I fix uboot environment it will boot to 2.5?
Can you please send me the correct uboot environment parameter to change?

stephenw10

These are the commands I used to restore the correct uboot envs from the default values you will have now:

setenv boot_file efi/boot/bootaa64.efi
setenv bootcmd 'run setLED; run mmcboot; run scsiboot; run usbboot; run net;'
setenv bootfile efi/boot/bootaa64.efi
setenv dmi_board_mfg Silicom
setenv dmi_board_name 80500-0205-G00
setenv dmi_board_serial 1925200071
setenv dmi_board_ver R301
setenv dmi_chassis_mfg Silicom
setenv dmi_chassis_serial 1925200071
setenv dmi_chassis_ver R301
setenv dmi_sys_mfg Silicom
setenv dmi_sys_name SG-2100
setenv dmi_sys_serial 1925200071
setenv dmi_sys_ver R301
setenv dtb_name armada-3720-sg2100.dtb
setenv efi_8be4df61-93ca-11d2-aa0d-00e098032b8c_OsIndicationsSupported {ro,boot}(blob)0000000000000000
setenv efi_cfee69ad-a0de-47a9-93a8-f63106f8ae99_Boot1Path {boot,run}(blob)2f005c006500660069005c0062006f006f0074005c0062006f006f00740061006100360034002e006500660069000000
setenv eth1addr 00:E0:ED:BC:2E:7A
setenv ethaddr 00:E0:ED:BC:2E:79
setenv fileaddr 1000000
setenv filesize 60000
setenv mmcboot 'mmc rescan; setenv load_dev mmc; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi;'
setenv net 'dhcp; tftp ${fdt_addr_r} ${dtb_name}; tftp ${kernel_addr_r} loader.efi; fdt addr ${fdt_addr_r}; fdt set / sn ${dmi_sys_serial}; bootefi ${kernel_addr_r} ${fdt_addr_r};'
setenv netgateid 72da527ea24be8b9a7e6
setenv pfsenseboot 'load ${load_dev} 0:2 ${fdt_addr_r} ${dtb_name}; load ${load_dev} 0:1 ${kernel_addr_r} ${boot_file}; fdt addr ${fdt_addr_r}; fdt set / sn ${dmi_sys_serial}; bootefi ${kernel_addr_r} ${fdt_addr_r};'
setenv scsiboot 'scsi reset; setenv load_dev scsi; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi;'
setenv setLED 'i2c dev 1; i2c reset; i2c mw 67 ff 0; i2c mw 67 0 1; i2c mw 67 f 20; i2c mw 67 3 40; i2c mw 67 26 0; i2c mw 67 10 0;'
setenv usbboot 'usb reset; setenv load_dev usb; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi;'
saveenv

You should run printenv there first to make sure those values are all missing or different. They will be if you saw the Bad CRC error in uboot which causes it to load the defaults.
You will need substitute your own serial number, Netgate device ID and MAC address.
The MAC shown on the label is the ethaddr value.

Steve

doronl15

Thanks Steve!
If it works then apparently the 1st time I sent the unit for repair was for nothing.
I keep you posted if I make it work.

Doron

doronl15

Hi Steve,
I've managed to fix the uboot CRC and now the system can boot correctly.
Thank you!
As you said the ralink 3090 is identified but does not work properly.
Do you have a list of verified wifi cards that work ok with 2.5.0 beta?

Doron.

stephenw10

Ah, good news and bad then.

What sort of errors are you seeing? How is it not working?

The only card I know to work in the SG-2100 currently (I have tested personally) is the Compex WLE200NX.

Steve

doronl15

Hi Steve,
well I grab a WLE200NX I see in ebay at 16$
the error I get with the relink is :

the wireless SSID is seen but cant be connected.
an error in the terminal when I enable the interface:

WAN (wan) -> mvneta0 ->
LAN (lan) -> mvneta1 -> v4: 192.168.0.1/24
WLAN (opt1) -> ral0_wlan0 -> v4: 192.168.2.1/24

Logout (SSH only) 9) pfTop
Assign Interfaces 10) Filter Logs
Set interface(s) IP address 11) Restart webConfigurator
Reset webConfigurator password 12) PHP shell + pfSense tools
Reset to factory defaults 13) Update from console
Reboot system 14) Enable Secure Shell (sshd)
Halt system 15) Restore recent configuration
Ping host 16) Restart PHP-FPM
Shell

Enter an option: ral0: can't map mbuf (error 27)
ral0: need multicast update callback
ral0: can't map mbuf (error 27)
ral0: can't map mbuf (error 27)
ral0: can't map mbuf (error 27)
ral0: can't map mbuf (error 27)
ral0: can't map mbuf (error 27)
ral0: can't map mbuf (error 27)

stephenw10

Ah, OK that's pretty much what I was seeing on the RT2700E too so probably affecting all ral devices in arm64. https://redmine.pfsense.org/issues/11021#note-4

I'll open a new bug to track that but it probably won't see any active fix unless something comes from upstream. That hardware is very old and slow at this point.

The WLE200NX is much faster and at least supports 802.11n correctly.

Steve

stephenw10

Just to track it: https://redmine.pfsense.org/issues/11093