Watchguard Help
-
Still sounds like video re-direct to me.
This particular unit doesn't have a second com port does it?
-
No, just the one in the front, standard serial. Man if they would have just put a VGA and USB under the lid….
-
Thanks for the tips but still no luck. :'(
Here is the odd part - Since flashing the bios, I can no longer boot from my 32mb CF drive with FreeDOS. I get the same problem, no console output.
I have tried swapping back and forth from 9600, 115200. I have tried 5 cables, 3 pcs now, 2 CF cards, and a 40gb ide 5400rpm hdd. Nothing just " pfSemse B7, Loading OS …
Did flashing the bios brick it? I dont think so as i can get to the bios all day long and change settings etc. I just can no longer connect once it starts to boot.
do you still have your original wathguard boot CF? if not just follow the link to get the backup & see if it can boot from that.
i doubt it could've bricked the bios
-
I read this assuming your system had past BIOS and was starting to load.. Dont pay any attention to the LCD.. It will say the same thing even once pfSense is fully booted.
Get into BIOS and see if you can set your system video emulation to VT100.
-
No, this unit did not come with a CF, it came with a 40gb IDE 5400rpm 2.5hdd. Sorry I dont see your link.
Thanks,
-
I read this assuming your system had past BIOS and was starting to load.. Dont pay any attention to the LCD.. It will say the same thing even once pfSense is fully booted.
Get into BIOS and see if you can set your system video emulation to VT100.
Thanks for the tip, but i do not see VT100 anywhere in the bios only this:
Console Redirection Enabled | |
| Baud Rate [115200] | |
| Agent Connect via [NULL] | |
| Agent wait time(sec) [3] | |
| Agent after boot [Enabled] | |
| Report No FDD For WIN 95 [No] | |
| Small Logo(EPA) Show [Disabled] V | |Here is where it hangs:
Phoenix - AwardBIOS v6.00PG, An Energy Star Ally
Copyright (C) 1984-2003, Phoenix Technologies, LTD**** BIOS Ver.ETAC0017 mod V1.7 comconsole on com1 115200 ****
Main Processor : Genuine Intel(R) processor 1.30GHz(100x13.0)
Memory Testing : 2088960K OK + 8M shared memoryIDE Channel 0 Master : TS32GCF400 20160322
IDE Channel 0 Slave : None
Phoenix Technologies, LTD
System Configurations
+==============================================================================+
| CPU Type : Genuine Intel(R) processor Base Memory : 640K |
| CPU ID/uco: 0695/45 Extended Memory :2087936K |
| CPU Clock : 1.30GHz Cache Memory : 512K |
|–----------------------------------------------------------------------------|
| Pri. Master Disk : CHS,PIO 4,32021MB Display Type : EGA/VGA |
| Pri. Slave Disk : None Serial Port(s) : 3F8 2F8 |
| Sec. Master Disk : None Parallel Port(s) : None |
| Sec. Slave Disk : None DDR2 at Bank(s) : 0 2 |
+==============================================================================+PCI device listing ...
Bus No. Device No. Func No. Vendor/Device Class Device Class IRQ0 2 0 8086 2592 0300 Display Cntrlr 5
0 29 0 8086 2658 0C03 USB 1.0/1.1 UHCI Cntrlr 7
0 29 1 8086 2659 0C03 USB 1.0/1.1 UHCI Cntrlr 11
0 29 2 8086 265A 0C03 USB 1.0/1.1 UHCI Cntrlr 10
0 29 3 8086 265B 0C03 USB 1.0/1.1 UHCI Cntrlr 5
0 29 7 8086 265C 0C03 USB 2.0 EHCI Cntrlr 7
0 31 1 8086 266F 0101 IDE Cntrlr 14
1 4 0 177D 0003 1000 ACPI Controllerntrlr 9 -
How long have you waited for anything to happen?
-
Left it "booting os" while we went to lunch today. No change.
I have tried:
Booting from old Cisco CF 32mb with freedos with 115200, 8,N,1 also 9600, 8,N,1
Booting from brand new Transcend CF 32GB flashed with 4GB i386 Embedded Nano, Serial 2.3.2 Release with 115200, 8,N,1 and 9600, 8,N,1
40GB IDE 2.5 HDD (put in laptop, loaded 2.3.2 from CD, enabled serial console during install, then swapped over to the watchguard
I have also tried not connecting the console cable till after the mem check.All of these produce the exact same result. Posts, checks mem ok, detects drives fine, then hangs after PCI device listing…
This is all i get in the console:Phoenix - AwardBIOS v6.00PG, An Energy Star Ally
Copyright (C) 1984-2003, Phoenix Technologies, LTD**** BIOS Ver.ETAC0017 mod V1.7 comconsole on com1 115200 ****
Main Processor : Genuine Intel(R) processor 1.30GHz(100x13.0)
Memory Testing : 2088960K OK + 8M shared memoryIDE Channel 0 Master : TOSHIBA THNCF032MBA 2.00
IDE Channel 0 Slave : None
Phoenix Technologies, LTD
System Configurations
+==============================================================================+
| CPU Type : Genuine Intel(R) processor Base Memory : 640K |
| CPU ID/uco: 0695/45 Extended Memory :2087936K |CPU Clock : 1.30GHz Cache Memory : 512K Pri. Master Disk : CHS,PIO 2, 32MB Display Type : EGA/VGA Pri. Slave Disk : None Serial Port(s) : 3F8 2F8 Sec. Master Disk : None Parallel Port(s) : 378 Sec. Slave Disk : None DDR2 at Bank(s) : 0 2 +==============================================================================+ PCI device listing ...
Bus No. Device No. Func No. Vendor/Device Class Device Class IRQ0 2 0 8086 2592 0300 Display Cntrlr 5
0 29 0 8086 2658 0C03 USB 1.0/1.1 UHCI Cntrlr 9
0 29 1 8086 2659 0C03 USB 1.0/1.1 UHCI Cntrlr 11
0 29 2 8086 265A 0C03 USB 1.0/1.1 UHCI Cntrlr 10
0 29 3 8086 265B 0C03 USB 1.0/1.1 UHCI Cntrlr 5
0 29 7 8086 265C 0C03 USB 2.0 EHCI Cntrlr 9
0 31 3 8086 266A 0C05 SMBus Cntrlr 11
1 0 0 11AB 4320 0200 Network Cntrlr 5
1 1 0 11AB 4320 0200 Network Cntrlr 12
1 2 0 11AB 4320 0200 Network Cntrlr 10
1 3 0 11AB 4320 0200 Network Cntrlr 11
1 4 0 177D 0003 1000 En/Decryption Cntrlr 11 -
You should be using the v8.1 BIOS which I modded from the SSL BIOS. It's newer and can boot any size CF card and most HD without messing about with CHS settings.
See: https://forum.pfsense.org/index.php?topic=20095.msg383842#msg383842
You will need to copy that to your CF card and be able to boot it though. I would clear the CMOS if you have not already done so. Then go into the BIOS and have it auto detect your 32MB card. It should boot that.
Steve
-
Thanks Stephen, I was hoping you would reply.
I have re imaged my 32mb CF with the FreeDOSBios2.img, copied over the XEBIOS_81.bin. Cleared the CMOS. I still have the same result.
I can get to the bios just fine, it detects anything I have put in it (including the IDE drive) just fine, it just wont boot…
I have another CF (4GB ) coming in the mail here today I can try but I really dont think that will change anything here.Any other ideas you all have would be most welcome.
Thanks!
-
That's the same CF card and Freedos image that you used to flash the v7 image originally?
And it not getting to the 3 beeps?
To boot that card I would expect to have to have the BIOS values at their defaults, IDE channels set to auto. And it might not boot the first time after a cmos clear. It will boot and complain about a checksum error but should detect the card and boot correctly on the second attempt.
Can you confirm the CF is bootable in anything else? Not many people have CF bootable stuff to hand any longer. ;)
Steve
-
Correct. Old Cisco 32MB i had laying around. My SSL 100 did not have CF card installed from factory. It had a 40GB IDE 2.5 (that went bad).
No, triple beep, ever. Just the 1 beep when it first powers up.
Phoenix - AwardBIOS CMOS Setup Utility
IDE Channel 0 Master
+=====================================================+========================+
| IDE HDD Auto-Detection [Press Enter]
| IDE Channel 0 Master [Auto]
| Access Mode [Auto]
| Capacity 32 MB
| Cylinder 496
| Head 4
| Precomp 0
| Landing Zone 495
| Sector 32I used this card with the default setting originally to flash the bios. I have another Transcend 32 GB CF here that gives me the same results. Also in the mail and should be here today a 4GB to try (just in case)
I dont have any other devices that use CF at the moment (other than my card reader).Thanks for your time!
-
I just got brand new 4GB SanDisk Ultra in from Amazon. Same deal…
Cant say we didnt try -
Hmm, well if that card worked the first time I can't really see any reason it would not work again.
You wrote the image to it a second time? Or just copied the bios image onto the card directly?
I would have to try flashing the card again to be sure. Maybe use a different flashing program or write 0s to it first to sure it's clean.
Steve
-
I just got brand new 4GB SanDisk Ultra in from Amazon. Same deal…
Cant say we didnt tryif you're using windows try this tool. i had better success using this than rufus & win32imager (both are great but it dont work for me this time)
http://m0n0.ch/wall/physdiskwrite.php
-
I want to thank you all for taking the time to help me and for sharing your knowledge!
I have come to the conclusion that this motherboard is toast. I have taken all 3 of those CF cards and stuck them in the reader and booted my laptop off them just fine. Putting them back into the WG SSL100, fails to boot anything.
I have learned a lot from this and have purchased a XTM5 (on its way here now!!) I am certain I will have much better results. I have my CF ready to go as well as more RAM and dual core proc. Cant wait to share my results next week with you all!
Thanks again!
-
You will like the XTM5 better anyhow. :)
-
I won't disagree there. The XTM5 is much nicer. Of course you could have bought our hardware… ;)
It could be an entirely coincidental hardware failure but it seems unlikely. Very strange. I would not expect it to boot into the BIOS if it was a failure. :-\
Steve
-
This looks like the x-core-e? Which is the same motherboard in X550e, X750e and X1250e? If you see it boot and then stuck, most likely the baud rate has changed during boot. As I recall freedos uses a different buad rate (9600) from the default bios buad rate (115200). Have you tried changing buad rate on your viewing computer after booting. Also when freedos has completed loading, it should make two beeps.
I had a couple of these x750e and I remember Watchguard's default buad rate is 115200 (same as pfSense) this would allow you to see the bios boot and then see pfsense boot. freedos baud rate is 9600. So you change to 9600 and you'll need to press "Enter" key multiple times to get the freedos console.
I think there is a feature, when you reboot the unit too many times it'll default to baud rate of 9600 for a one time boot. It'll work at this buad rate until you reboot. This allows idiots like me to at least see the system boot once, and then see freedos prompt. Believe me, I had my fair share of experience with the x-core-e series. Also note that these primitive console com were buggy and sometimes you get weird characters even when you are on the correct buad rate, make sure you have good ground on your serial connection and hit "Enter" key multiple times.
I think your motherboard is working. Once you get freedos prompt showing, move on to getting pfSense on the CF card.
-
Yah, I remember now. So when I had the v81 bios flashed and freeDos on compact flash. I would keep my computer com baud rate at 9600 and boot it watchguard unit. I wouldn't see the bios boot, but after a while hit "enter" key a couple of time and the freeDos prompt appears.
Once I had pfSense on a compact flash. I keep my computer com baud rate at 115200 and I could see bios boot then pfSense boot.