Netgate SG-1000 microFirewall

Author Topic: Issues with Installing 2.3.4 on Watchguard X750e  (Read 517 times)

0 Members and 1 Guest are viewing this topic.

Offline Alex1974

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Issues with Installing 2.3.4 on Watchguard X750e
« on: July 04, 2017, 09:08:26 am »
Hello,

I'm issues with Installing 2.3.4 on Watchguard X750e
It hangs around IRQ page

Keep in mind that i made Watchguard fixes already:
hint.ata.0.mode=PIO4
hw.msk.msi_disable=1

any ideas ?

Online chpalmer

  • Hero Member
  • *****
  • Posts: 1746
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #1 on: July 04, 2017, 01:22:18 pm »
Its been a few years since I put together an X-e box but I seem to think if there was a problem reading from the disk/card that it would pause there.

P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11875
  • Karma: +458/-15
    • View Profile
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #2 on: July 04, 2017, 01:47:07 pm »
Yup last thing you see when it fails to boot whatever you have in there.

What are you booting? How did you make those loader fixes if it won't boot?

What BIOS version are you running? What BIOS settings do you have? You should use the 8.1 BIOS for maximum compatibility.

Steve

Offline Alex1974

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #3 on: July 05, 2017, 10:08:59 am »
I flashed the CF with Pfsense 2.3.4 trying to boot from, no luck so far
It hangs at the screenshot i submitted

I do pfsense fixes for Watchguard by mounting the CF to linux machine
and write the following command to /boot/loader.conf.local:
hint.ata.0.mode=PIO4
hw.msk.msi_disable=1

Bios Award 5.1
I have another CF and flashed with FreeBios but also can't boot with it to flash the Bios

IDK what's wrong with it

Can it be, Watchguard secure Bios ?

Yup last thing you see when it fails to boot whatever you have in there.

What are you booting? How did you make those loader fixes if it won't boot?

What BIOS version are you running? What BIOS settings do you have? You should use the 8.1 BIOS for maximum compatibility.

Steve

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11875
  • Karma: +458/-15
    • View Profile
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #4 on: July 06, 2017, 03:30:19 pm »
Ok, if you haven't flashed the BIOS to v8.1 then you'll need to set the CHS settings for whatever card you are booting. However since you're seeing some output there via serial I imagine you must have updated the BIOS no?

What size CF card are you using with 2.3.4 on it? There are some cards that just won't boot whatever you do. The original BIOS is really picky about card geometry.

Steve


Offline Alex1974

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #5 on: July 06, 2017, 03:34:45 pm »
Hi,

Thank you for your reply,

I'm using ScanDisk Ultra CF 4GB 30MS/s, what would be CHS for it? And where exactly to apply it ?

Ok, if you haven't flashed the BIOS to v8.1 then you'll need to set the CHS settings for whatever card you are booting. However since you're seeing some output there via serial I imagine you must have updated the BIOS no?

What size CF card are you using with 2.3.4 on it? There are some cards that just won't boot whatever you do. The original BIOS is really picky about card geometry.

Steve

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11875
  • Karma: +458/-15
    • View Profile
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #6 on: July 12, 2017, 01:19:21 pm »
You would have the BIOS detect the card initially then change the mode to from auto to CHS and change just the H (heads) value to 2. It will report the wrong CF size but should boot anyway.

Those are settings to the primary IDE channel in the BIOS setup which you should be able to get into by hitting 'TAB' since you can see some output.

Really though it would be better to boot from something small enough and flash the 8.1 BIOS which doesn't require that manual work-around.

Steve

Offline Alex1974

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #7 on: July 13, 2017, 09:50:12 am »
Hi,

I think i finally figure it out
It's Specs for the CF card in the bios along peripherals settings
Now, none Pfsense community edition is bootable, the only one work for once was CE for serial edition
But it hanged as of i have to implement the following fix

write the following command to /boot/loader.conf.local:
hint.ata.0.mode=PIO4
hw.msk.msi_disable=1


Well, i can't at all, as they made the File System protected

Any ideas ?

Thanks

You would have the BIOS detect the card initially then change the mode to from auto to CHS and change just the H (heads) value to 2. It will report the wrong CF size but should boot anyway.

Those are settings to the primary IDE channel in the BIOS setup which you should be able to get into by hitting 'TAB' since you can see some output.

Really though it would be better to boot from something small enough and flash the 8.1 BIOS which doesn't require that manual work-around.

Steve

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11875
  • Karma: +458/-15
    • View Profile
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #8 on: July 17, 2017, 06:59:01 am »
You should be using the nanobsd serial image on a CF card there. This one for example: https://atxfiles.pfsense.org/mirror/downloads/pfSense-CE-2.3.4-RELEASE-2g-i386-nanobsd.img.gz

Steve

Offline Alex1974

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Issues with Installing 2.3.4 on Watchguard X750e
« Reply #9 on: July 17, 2017, 03:35:59 pm »