2.2.6 on Watchguard 550 loops to "found non-ATA66 cable"
-
Hi there.
My Firebox Watchguard x550 Core works with 2.2.4 like a charme.
Now I am trying to install 2.2.6 on a 4GB CF.
I downloaded pfSense-2.2.6-RELEASE-4g-i386-nanobsd-20151221-1450.img image and wrote it into the CF (just like I did time ago using the good working 2.2.4 rel).In annex please find the log file captured from the serial terminal at the 2.2.6 boot, where it can be read the following.
"
ata0: DMA limited to UDMA33, controller found non-ATA66 cable
(ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 6f 7e 77 40 00 00 00 00 01 00
(ada0:ata0:0:0:0): CAM status: Command timeout
(ada0:ata0:0:0:0): Error 5, Retries exhausted
ata0: DMA limited to UDMA33, controller found non-ATA66 cable
…
"
and it loops on these last few rows.Is there anyone who had such a trouble and knows how to fix it?
Or, how to bypass it - if possible - by disabling any "non-ATA66 cable" check?Thanks in advance.
Mauro
P.S. By the way, the console port wakes up at 115000 baud rate. How to change 2.2.6 for 9600?
Scritto_su_Forum_pfSense.txt -
while i doubt that is the issue ….
to fix the non-ata66 issue, perhaps you should replace the flatcable with a ata66/ata100 cable ?
-
Thanks heper.
You are right when you say it is not the issue and this is a strange thing because there is no flatcable at all.
The CF is located inside its slot, that is directly connected to the motherboard. :oI tryed with two CF: Trascend (like the first CF that is good working with 2.2.4) and SanDisk. Same problem on both.
-
Just to clarify my setup here please find a picture of my device:
https://www.dropbox.com/s/mcle80f9ahfvx62/20160116_172142_resized.jpg?dl=0If none has had and fixed this issue I urge the attention of the pfSense software engineers.
This because it could be related to any check performed by pfSense 2.2.6 on the hardware and erroneously failed.
I know that there are many devices out there and that each of them is electronically different, but Watchguard ones are very common and be easily found on Internet.Again thank you heper for your attention.
Mauro
-
If you are not using the ATA/IDE controllers that are freaking out you might try disabling them in the BIOS.
