Upgrade from 2.1.5 nano to 2.2.1 problem

doktornotor

Anyway I'll try to disable DMA at boot time because currently it is not using it and works:

[2.1.5-RELEASE][admin@firewall.b2]/root(13): atacontrol mode ad2
current mode = PIO4

Because UDMA is disabled by default on nanobsd on 2.1.x, but enabled by default on 2.2.x. Use the 2.2 hints before upgrade.

stenio

Thanks doktornotor,

I created the file /boot/loader.conf.local and this evening I'll try to upgrade again.

[2.1.5-RELEASE][admin@firewall.b2]/root(18): cat /boot/loader.conf.local
hint.ata.0.mode=PIO4
hint.ata.1.mode=PIO4

stenio

Just tried with the hint.ata.1.mode=PIO4 and now it is evev worse:

[…]
(aprobe0:ata1:0:1:0

system locked. :'(

doktornotor

Ditch the card.

stenio

I'm thinking to switch to the hdd version.

Do you know if it is possible to restore the configuration of the nano version on it?

Thanks

doktornotor

Yes, you can do that.

stenio

@doktornotor:

Ditch the card.

Hi, I tried with a new CF card attached to an USB card reader but the error is the same:

(aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ata1:0:1:0): CAM status: Command timeout
(aprobe0:ata1:0:1:0): Retrying command

I'll try with:

hint.atapci.1.msi="0"

I hope it works! :-\

stenio

No way!

I tried with all possibles hint settings, booting from an USB stick, also disabling the internal CF by BIOS but the result is the same.

At this point I think that FreeBSD 10.1 is simply not compatible with my hardware. :'(

EDIT:

I think this is the problem:
http://freebsd.1045724.n5.nabble.com/no-subject-td5952628i20.html

stephenw10

What hardware are you running?
There has been at least one other platform that reports similar errors on 2.2+. There is no solution as yet I'm afraid.
https://forum.pfsense.org/index.php?topic=87364.0

Steve

bval

@stenio:

At this point I think that FreeBSD 10.1 is simply not compatible with my hardware. :'(

EDIT:

I think this is the problem:
http://freebsd.1045724.n5.nabble.com/no-subject-td5952628i20.html

stenio, were you ever able to resolve this? I am running into the exact same issue on a soekris net4801 with the exact same model # of CF card.

Thanks,

Brandon

stenio

@bval:

stenio, were you ever able to resolve this? I am running into the exact same issue on a soekris net4801 with the exact same model # of CF card.

Hi Brandow,
I've just tried with the latest PF 2.2.6 but the problem is still there! :(

stenio

@stephenw10:

What hardware are you running?
There has been at least one other platform that reports similar errors on 2.2+. There is no solution as yet I'm afraid.
https://forum.pfsense.org/index.php?topic=87364.0

Sorry Steve, I missed your post. I'm using a Fabiatech FX5621:
https://forum.pfsense.org/index.php?topic=92279.msg511016#msg511016
https://forum.pfsense.org/index.php?topic=92279.0

Regards,
Stenio

phil.davis

Note for reference: https://forum.pfsense.org/index.php?topic=87364.msg583303#msg583303
No luck with the FW-525B on latest pfSense 2.3-ALPHA that follows FreeBSD 10 development.

stenio

@phil.davis:

Note for reference: https://forum.pfsense.org/index.php?topic=87364.msg583303#msg583303
No luck with the FW-525B on latest pfSense 2.3-ALPHA that follows FreeBSD 10 development.

It seems that the problem will be solved in FreeBSD 11:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199495