Successful Install on Watchguard Firebox X700!
-
I bought today an X700 firebox, flashed latest nightly on a 4GB CF, and inserted on Firebox.
Firebox booted correctly into pfSense, followed the setup and assigned two NICs, and then continue booting until "Bootup complete" message, and beeper play pfSense ring. And nothing …. serial terminal don't respond, no welcome string, no main menu, no Control+C response, nothing ....
Only way is switching off the Firefox.
What I'm doing wrong ?
Edit: I already tried with differents nightlies, with equal results. Tried different NIC configurations, with LAN cables pluged and unplugged ... Nothing. Already tried the "hint.acpi.0.disabled=1". Nothing.
(sorry for my bad english)
Thanks!
I have the same issue, but even tho the console was useless the webgui was up on the LAN port.
I have since taken a break from working on the Firebox, waiting on my 512 RAM, 1.4Gz Celeron and 4GB microdrive to arrive.
But, it's the first run. I have no chance to assign an IP address to the LAN port. So, how can I access the webgui without an IP address ?
Edit: pfSense 1.2.3 works perfectly. So, problem is with 2.0-BETA5.
Thanks.
Were there ANY bios changes?
Also, if it helps, I had to chose "revert to factory settings" in the pfSense console menu. I then restored certain parts of my config. A fresh install might be worth trying if this is not one.
-
I'm running both Dec 18th Beta4 and Jan 13th Beta5.
I am using a 1GB image on a 4GB card though. Mostly because it's takes so long to write the card in my reader but there could be a difference. Image corrupted somehow? Some 4GB cards aren't actually big enough for the 4GB image.Steve
no joy just tried pfSense-2.0-BETA5-1g-i386-20110113-0349-nanobsd.img fresh install
used dd to image to 4gig cf still get the "bootup compluete" halt in console
still get[2.0-BETA5][root@pfSense.localdomain]/lib(7): /etc/rc.conf_mount_rw
[2.0-BETA5][root@pfSense.localdomain]/lib(8): ln -s libc.so.7 libc.so.6
ln: libc.so.6: Read-only file system -
ok just to test i tried upgrading from 1.2.3 to todays 2.0 build to see if it was the act of upgrading vs fresh that caused it to work and i can confirm it's not still getting "Bootup Complete" and read-only error
-
So re seating the CPU got the firebox working!
Unfortunately, now when I try to run the laptop drive, it says boot error on the console. I tried connecting the laptop drive in both directions to the PATA cable. One way it says boot error, the other way i just get a blank screen on the lcd but nothing shows up in the terminal.
I am using a serial to USB adapter to try and connect to it on my laptop – do I need the special firebox console cable?
Thanks for your help.
No, it's a standard console cable.
The exact type is a DB9 Null Modem F/F Console Cable I believe.
Appreciate the info; turns out the serial to USB sold by radioshack is not a null modem cable; so i ended up having to buy the serial to usb cable, a gender converter, and a null modem adapter (i.e. about $70 in cables or the same price i paid for the firebox!) all from radioshack – the problem with impatience!
I did get it working; now time to upgrade the box with some new fans and get openvpn working with the crypto card!
I searched the thread for quiet fans, and the one link posted for overclockers UK does not work; does anyone have any model numbers for quiet fans? I'd rather not make holes in the box, so would prefer fans that fit the current formation
Thanks for all the help!
-
I searched the thread for quiet fans, and the one link posted for overclockers UK does not work; does anyone have any model numbers for quiet fans? I'd rather not make holes in the box, so would prefer fans that fit the current formation
For my each of my fireboxes I used three Scythe 40 mm Fan Mini Kaze fans (SY124010L) as replacements for the three fans in the back and a larger Papst 60 mm Fan (612FL) as the cpu cooler.
The Scythes have a different connector, so I had to reuse the original firebox cables.
The Papst really isn't meant to be used the way I'm using them, but I cut out a part in the side of the fan, in effect creating the same airflow as the original firebox cpu fan.
Also, the circumference of the Papst is 5 mm larger than the original fan, which actually helps circulation.Both my fireboxes have been functioning for about six months while being cooled in this fashion with no problems even under somewhat heavy load.
dB pressure per firebox has gone from ±71.3 to ±44.2 after replacing the fans. -
For my each of my fireboxes I used three Scythe 40 mm Fan Mini Kaze fans (SY124010L) as replacements for the three fans in the back and a larger Papst 60 mm Fan (612FL) as the cpu cooler.
got any pictures of the new fans?
-
got any pictures of the new fans?
As it so happens, I took pictures when I was installing the new fans in Firebox 01.
-
-
new fans installed! soooo much better!
Temp.= 46.0, 127.0, 80.0; Rot.= 0, 4623, 0
Vcore = 1.47, 3.34; Volt. = 3.28, 4.92, 11.61, -3.17, -6.12 -
new fans installed! soooo much better!
Temp.= 46.0, 127.0, 80.0; Rot.= 0, 4623, 0
Vcore = 1.47, 3.34; Volt. = 3.28, 4.92, 11.61, -3.17, -6.12What command do you run to get that info?
-
What command do you run to get that info?
first install mbm
if your running embedded u need to make it rw first/etc/rc.conf_mount_rw pkg_add -r mbmon /etc/rc.conf_mount_ro
then run this to display stats
/usr/local/bin/mbmon -I
it will just loop and keep displaying until you hit
-
looks good!
i can pick up the same 40mm local for 4.95 so i think i will do this and find a nice 60 for the cpu.also what app is that on ur iphone?
Thank you, I must say that I'm quite pleased with the way this mod turned out.
The app I'm using to measure sound pressure is called SPL meter
Note that it's likely that a 60 won't fit exactly (as it will be somewhat too large), and that you'll have to use some tricks to seat it properly. -
ya i used a 60 as well but a 50 would fit a little better for anyone else looking (if you can find one my shop didn't carry any)
-
ya i used a 60 as well but a 50 would fit a little better for anyone else looking (if you can find one my shop didn't carry any)
I'm getting a Firebox sometime next week and just wondering if the connectors/cable on the 60mm was the same or does it need to be replaced?
Sleeps
-
I'm getting a Firebox sometime next and just wondering if the connectors/cable on the 60mm was the same or does it need to be replaced?
Sleeps
ya it's just a 3 pin standard mb fan connecter so it will just plug in. the rear fans will need some work if you decide to change them, my fans came with adapters so i cut the adapters and the cords from the stock fans to make custom adapters so i can try different fans latter.
the 60mm over hangs a little but will work mine is only being held on by 1 screw but it's quite tight and the internal temp dropped with MUCH less noise -
I'm getting a Firebox sometime next and just wondering if the connectors/cable on the 60mm was the same or does it need to be replaced?
Sleeps
ya it's just a 3 pin standard mb fan connecter so it will just plug in. the rear fans will need some work if you decide to change them, my fans came with adapters so i cut the adapters and the cords from the stock fans to make custom adapters so i can try different fans latter.
the 60mm over hangs a little but will work mine is only being held on by 1 screw but it's quite tight and the internal temp dropped with MUCH less noiseJust purchased Fractal Design 50mm Silent Series Cooling Fan and 3 Scyche Mini Kaze 40mm fans.
-
Just purchased Fractal Design 50mm Silent Series Cooling Fan and 3 Scyche Mini Kaze 40mm fans.
Keep us posted!
-
just tried todays build and "/etc/rc.conf_mount_rw" still does not seem to change the disk to read/write :-\
-
Just managed to install latest build on Firebox x700.
How ever there's that problem with Bootup complete with embedded kernel.
I could also not reach the firebox by webgui.
What I did later was to reinstall using one cpu kernel on my other PC.
After that I enabled console in webgui and switched disks.
I managed to get past Bootup complete at first try on firebox.
NIC's working good and able to access webgui.
How ever after rebooting the device the problem with lockup at Bootup complete still persist when using serial-cable.
I can how ever use the firebox since my NIC's working good with this kernel.Sorry for the confusing post, my native language is not english.
I just wanted to post this so more people can work on getting this version working good on firebox. -
Just managed to install latest build on Firebox x700.
How ever there's that problem with Bootup complete with embedded kernel.
I could also not reach the firebox by webgui.
What I did later was to reinstall using one cpu kernel on my other PC.
After that I enabled console in webgui and switched disks.
I managed to get past Bootup complete at first try on firebox.
NIC's working good and able to access webgui.
How ever after rebooting the device the problem with lockup at Bootup complete still persist when using serial-cable.
I can how ever use the firebox since my NIC's working good with this kernel.Sorry for the confusing post, my native language is not english.
I just wanted to post this so more people can work on getting this version working good on firebox.I have the same issue with 2.0
it always stops at bootup complete. if you need access to the console you need to use ssh. not sure why it stops there but it does :(
1.2.3 boots correctly
also it seems on any of the newer embedded builds the command to change the filesystem to read/write dosen't work for some reason.other than that 2.0 is great! cant wait for the 2.0 book to come out… u know after 2.0 comes out ;D