P5Q Premium keeps hanging on install/startup -> How to force no ACPI?

[David24]

Hello, i've tried out pfsense in school a while back and decided to use it home now since im about to swap ISP.
The box is a Asus P5Q-Premium, E8200 and 8Gb mem    http://uk.asus.com/product.aspx?P_ID=QPhR6dGjcvkYnazE

Also i've had bunch of other errors… I will update asap with more messages...

It ALWAYS hangs just after asking if i want to setup VLANs now y/n

acd0 failure - read_big hardware error asc=0x3e ascq=0x02     ( which also is the CD/DVD so i assume its no worries ) it also runs in pio4, seams odd..?
Then it goes on like nothing happened after a bunch of those error messages.
Next odd is, Just after showing the welcome to PFsense 1.2.3-RELEASE
uhub5: device problem (TIMEOUT), disabling port2

This can be avoided doing boot without ACPI, second selection in the freebsd menu. How do i access loader.conf i keep getting it read only? To force hint.acpi.0.disabled="1"

Maybe you got another solution that can still have my ACPI in place?

[wallabybob]

Unless you have the embedded version of pfSense (nanoBSD based) you should be able to edit (by vi ) /boot/loader.conf from the shell.

How are you trying to edit the file and what is reported?

Here's what I see on my pfSense 1.2.3 box:

uname -a

FreeBSD pfsense.example.org 7.2-RELEASE-p5 FreeBSD 7.2-RELEASE-p5 #0: Sun Dec  6 22:57:48 EST 2009    sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.7  i386

vi /boot/loader.conf

Actually, you would be better off putting those sort of changes in /boot/loader.conf.local which should remain unchanged over upgrades.

I suspect motherboard is a fairly recently released model.  Its possible pfSense 2.0 BETA would work better on that board. The developers still consider 2.0 BETA to be not yet production ready but a number of people have reported satisfactory experiences with it.

[David24]

No, i have been running the cd install.

uname -a brings
FreeBSD pfSense.local 7.2-RELEASE-p5 FreeBSD 7.2-RELEASE-p5 #0: Sun Dec 6 23:20:31 EST 2009 sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.7 i386

I've pushed the line into the config.local, i had suspended vi thats why i had file lock. The mainboard is not new by any means… Tho, i also was unable to find drivers for 2 of 3 sata chipset on the board.
Also i noticed, it caps at 4 GB mem, What uses more/less memory I will be routing 10 x 100/100 Wans trought it. Probably ill go for loadbalancing and static firewall, allowing none, but a few ports.

Thanks, either way i will read up some on 2.0 it might have some benefits i might use.

[wallabybob]

The maximum amount of RAM you can use with the "i386" kernels is about 3GB. To use more you will need to use an "amd64" kernel which is not available until pfSense 2.0.

[David24]

Yeah, thanks… I just read a while in the 2.0 part of forum... Ill stay at 1.2.3 cause untill load balancing seams stable, but i will update asap since i want the 64bit adressing space...

Thanks for the quick replies ill be back if i need further assistance... when i need further assistance! x)

awesome piece of software tho... Torrenting in 2mb/s at the old connection with 2-3k states dont even bring 1% cpu usage...