Pfsense Install on Nokia IP390
-
Indeed, pfSense uses a custom kernel and I would expect IPSO does also. The base FreeBSD versions are probably different. I'd be amazed if it was compatible.
Steve
-
Hmm.. Alright. The only reason why I wanted to use the IPSO kernel was because the warning light on the unit remains on which indicates an internal voltage error. The unit runs fine, so I can assume the warning is false, but it would be nice to get that working properly
-
Try booting IPSO: if the LED goes off you're OK, and it's likely a IPSO userland utility that controls it. If it stays on, you have some more investigation to do. Of course, wire cutters or black tape could fix the problem too …
-
Since that same indicator can show over temperature it's probably driven from the board rather than the psu which is good. It's probably driven from the SuperIO chip where the voltage and temperature sensors are connected.
There maybe some options in the BIOS to change the indicator behaviour otherwise you could probably tweak it manually with a utility and a script.Steve
-
Hmm, alright.
Yeah, booting into IPSO turns the warning indicators off, so the unit is fine.
Alright, thank you. I don't think I can actually change the bios settings, or at least not from the console. How would I go about getting a utility / script working?
-
Can you access the bios at all? It may be at 115,200 on the serial console.
It's not straight forward doing it from software. It will probably require a lot of trial and error and educated guesses. See my own effort here: https://forum.pfsense.org/index.php?topic=32013.0
The first thing would be to try to determine how the led is connected to the board. Then gather as much info about the board as you can. In particular the superio chip and the north/south bridge chipset. If it's not made by nokia who made it etc.Steve
-
Hi Steve,
Uh, I can't say I know what you're talking about, sorry. The serial console connection is currently set to 9600 bps, 8 data bits, No parity and 1 stop bit.
The following image shows the assembly behind the console ports and status LEDs:
The large chip in the foreground is an Intel nhe3600esb I/O controller. the status LEDs connect through a sister board, which connects to the motherboard by a ribbon cable just behind the I/O controller.
Seems like in your attempts with a similar circumstance required digging through the kernel. I'll take a look at that in a minute or so, once I can find a program which can read it :/
-
The proximity to the ICH chip (6300esb) would have me guessing it's controlled by one of the GPIO pins on that. That was where I found the control on the earlier firebox models. The only issue is that I don't think the 6300 had a flashing mode. :-\ There are lot of components on that daughter board considering it's only got 3 leds on it. Flashing could be done there.
Steve
-
Hmm. The daughter board actually governs 4 LEDs, as, from left to right, you have: System activity indicator (green), System warning (Yellow !), System On/Off (Nokia logo, illumunated blue) and the system fault indicator (Red X ). I've worked out that 5 of the LEDs on the daughter board govern the system On/Off light alone.
Here's a picture of the daughter board taken off:
There's a few chips on here, any ideas? My initial thoughts were that they were voltage regulators, but I'm pretty sure the System fault indicator is ran from the BIOS, which might explain the chip on the top right of the board. That would also explain why the fault indicator is working properly.
-
I agree there's probably some voltage or current regulation. The outputs from the ICH are probably not capable of sinking enough current to drive the LEDs directly so instead there are transistors for each LED (Q1, Q2 etc) and a line driver/buffer (the 7407 IC). The other large device, labelled 10-16L, is a capacitor perhaps to filter switching spikes. I like that there's a mystery space for an LED, CR9, that Nokia decided not to use for whatever reason. :)
Do the 4 LEDs come on as soon as you power on the box? Do they vary at all during boot?
The BIOS setup in embedded hardware like these boxes is often available on the serial console via 'console redirection'. It's usually at a baud rate of 115200bps. To access it you often have to press TAB because you can't send DEL over serial. Interestingly it looks like that box has two BIOS ROM chips.
Edit: Maybe on the other serial port, AUX, perhaps.
Steve
-
You're correct. The board has support for 2 BIOS chips, but only the right one is populated with a BIOS chip. According to the stickers on the MB, the BIOS is an American Megatrends AMI BIOS 786Q.
As for accessing the BIOS, I'll give that baud rate a try tomorrow. How will I know when I'm in the BIOS? Will it print text like the normal 9600 baud rate does?
I believe that the LED for CR9 Might be for and LED for the IP560. I don't exactly know what that LED would be, but I would imagine that Nokia use the same status LED boards across most of their IP series products to save money.
-
Searching for info on the IP390 there are a number of people who have posted IPSO boot logs and it includes the memory count. That is before the bootloader so it's coming from the BIOS. It's in the same log at the same baud rate so I would suggest whatever baud rate IPSO uses should be good for accessing the BIOS setup. If you're seeing the memory count you're probably good, try pressing TAB. Of course Nokia could have it all shut down deliberately to stop access but they haven't forced only signed boot images for instance.
Steve
-
Just for reference the IP530 uses the SuperIO chip to control those LEDs:
http://www.coreboot.org/Board:nokia/ip530#Front_LEDs
Does not mean the IP390 does though. ;)Steve
-
Alright, I just managed to get into the BIOS by pressing tab after the memory test had completed.
It came up with a message:American Megatrends AMBIOS (version #) Press ~~ to enter setup.~~It wouldn't allow me to enter text on that screen.
Here's pictures of the BIOS:
http://s26.postimg.org/j5bb13bi1/bios1.png
http://s26.postimg.org/mq76kbg1l/bios2.png
Here's inside the SuperIO menu:
http://s26.postimg.org/j7v6nxf5l/bios2_5.png
http://s26.postimg.org/fpj6rje9l/bios3.png
http://s26.postimg.org/41p4wzp4p/bios4.png
http://s26.postimg.org/cl8iuqxh5/bios5.png
http://s26.postimg.org/f3u7vfj7d/bios6.pngThat's all of it. There doesn't appear to be any options for the status LEDs on the front panel.. Any ideas?
Sidenote: I should have said the IP690, not IP530. The IP690 is the model up from the 390.
-
It was worth looking, only one of the Watchguard boxes had a custom bios menu for the led. If it is connected to the ICH it's worth looking in the southbridge setup menu.
I assume that the yellow warning led comes on as soon as you power up the box and then just stays on?Steve
-
Here's a picture of the southbridge menu:
Yeah. On boot the only LED which does not switch on is the System fault. All the other LEDs, System activity (Is meant to be on), System warning (Should not be on) And System Power (Should be on) Are all on.
-
Any chance something shows up as /dev/led* or /dev/gpio*? If one or both show up under IPSO, but not pfSense, that could be a big clue.
-
Hmm. I see what you're getting at, but how can I check if /dev/led* or /dev/gpio* show up under IPSO? What command should I enter?
-
Hmm. I see what you're getting at, but how can I check if /dev/led* or /dev/gpio* show up under IPSO? What command should I enter?
Do you get a shell prompt on the serial console with IPSO? If not, try the AUX port, which is set up for remote management via modem. Or try to ssh into the unit.
For pfSense, you can use the shell on the serial console, or ssh in to the unit. Choose '8' from the menu, then use 'ls' command:
*** Welcome to pfSense 2.2-ALPHA-pfSense (amd64) on pfsense *** WAN (wan) -> bge1 -> v4/DHCP4: xx.yyy.zzz.12/20 LAN (lan) -> bge0 -> v4: 192.168.2.128/24 OPT1 (opt1) -> bge1_vlan2 -> v4: 192.168.100.5/32 0) Logout (SSH only) 8) Shell 1) Assign Interfaces 9) pfTop 2) Set interface(s) IP address 10) Filter Logs 3) Reset webConfigurator password 11) Restart webConfigurator 4) Reset to factory defaults 12) pfSense Developer Shell 5) Reboot system 13) Upgrade from console 6) Halt system 14) Disable Secure Shell (sshd) 7) Ping host 15) Restore recent configuration Enter an option: [2.2-ALPHA][root@pfsense.localdomain]/var/log(1): ls -l /dev/gpio* /dev/led* ls: No match.The ls command would be the same in either IPSO or pf Sense.
-
I'm getting no output on the AUX port under pfSense, and the console port gets to "bootup complete" and won't accept further input. I'll try to ssh to pfSense in a minute.
