I am trying to find an older mother board with two PCI slots to use a Digium TDM400P and a Digium TE122. I found one. It is an older Acer Board with a Celeron: https://youtu.be/dojWx0V_tPk
I made a boot USB with the latest beta ISO on it and it gets to 83 percent and locks up. It does this on PUB, FOG, UPG, OST, or INT install.
So far I have tried a different SATA drive, Different CPU, Different RAM. I have played with the BIOS setting and I downloaded the 12.8 installer, I was using 12.10
It does the same thing. Any Ideas where I can go from here. If not I will just have to try version 16.
Yes I have installed it many times previously on newer hardware, and VM. I need a motherboard that has multiple PCI slots for this install. It is hard to find hardware with real PCI that isn’t old.
I found a Core 2 Duo E8400 and installed it. It is still doing the same thing. I though maybe it was just not compatible with the single core of the 420
Uhhhh… have you tried with a quad-core (or better) CPU with DDR3 (or better) RAM? (6GB min, perhaps?), basically the base requirements that’d be needed to run Windows 10? Though now it might be closer to 11 (without the TPM nonsense) considering that FPBX 17 is ONLY meant to run on a UEFI system, but ya never know
EDIT: Celerons, I’m pretty sure they gave away in cereal boxes
Specifically the FreePBX v17 ISO is geared for UEFI, and RAID setups won’t work right without it, yes.
But if you did install vanilla Debian 12 in non-UEFI mode, then you separately ran the FreePBX 17 shell installer later on, it should work fine. (But YMMV with RAID in that case.)
I found a Digium TE121 card that is PCI express, from an old customer that gave me there freepbx server when they went out of business. I had a newer Gigabyte AMD FM2 board given to me by a customer updating to Win11. It had one Regular PCI slot for the TDM400P and two PCI express slots. I installed it on that board without issue. On the old board, I even tried a modified XEON (Modified to Socket 775), is was still no go. I tried burning a CD and installing from that and still no go. I even tried FreePBX 16 and still a no go with that (different error though). But I am good now, I have a solution! And I am happy.
It depends on the environment. Here’s a few thoughts that you might consider from last month’s Sizzling FreePBX 17 webinar – starting at the 9m25s mark:
