Firebox x1250e crash after upgrading
-
I think you can use the XEBIOS_81.bin bios, but stephen is the person who can tell you exactly what the difference is.
-
I forgot to enable the ACPI menu in the bios on version 8. Enabling it didn't seem to justify an entire version jump so I added a .1.
Although in the boot screen I think it says 0.81 any way. ::)Versions 1-7, many of which never made it beyond my test box, were based on the code extracted from the x750e (and similar) models. Verison 8 was from code extracted from the SSL model which is equivalent to the X550e in hardware terms but crucially boots from a HD rather than CF.
XEBIOS_81.BIN is the file to use. I didn't link to it for a while because not that many people had tested it but I've yet to here any bad reports so it should be considered the default option at this point.
Steve
-
Flashed XEBIOS_8.BIN,
(E17HDD) MOD V0.8 console on com1 115200. Stephenw10 10/12/13
hit ESC during boot to get the loader prompt and entered:
set vfs.root.mountfrom=ufs:/dev/ad0s1a
set hw.ata.ata_dma="1"Then entered boot and enter to start the boot up.
I still get after the above:
cpu0 on motherboard
est0: <enhanced speedstep="" frequency="" control="">on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 612102906001029
device_attach: est0 attach returned 6
p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
pmtimer0 on isa0
gpioapu0: Environment returned (null)Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0da8cf0
stack pointer = 0x28:0xc2420c28
frame pointer = 0x28:0xc2420c34
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
[ thread pid 0 tid 100000 ]
Stopped at strncmp+0x20: movzbl 0(%esi),%ebx
db></cpu></enhanced> -
I am adding the 81 BIOS to my flash card now and will flash that then enter:
set vfs.root.mountfrom=ufs:/dev/ad0s1a
set hw.ata.ata_dma="1"Then enter boot and enter to start the boot up.
What am I doing wrong here?
-
I found some other boot.config files, but while in the loader prompt i cant find a boot.config.local
loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local"
-
Did you reset the CMOS after flashing the BIOS? Are the IDE parameters now set to auto?
I don't actually think that would make any difference since it's obviously find the drive and booting from it.
One of the bigger changes going to 2.2 is the new drivers for ATA devices:
https://doc.pfsense.org/index.php/UpgradeGuide#Disk_Driver_Changes
I suspect your install is trying to use swap space in a location that no longer exists, on ad0 as opposed to ada0. For other mounted drives/slices there are aliases to link to the new names but perhaps not with the swap slice. Can you access the filesystem table at /etc/fstab? What are it's contents?Steve
-
Ill check tonight when I have the device in front of me
-
-
Are you sure your HD is mounted as ad0s1a
because I see you entered this line:```
set vfs.root.mountfrom=ufs:/dev/ad0s1abut your HD in the fstab file is ada0s1a so the mountpount should be:``` set vfs.root.mountfrom=ufs:/dev/ada0s1a -
If you type dmesg in console you can see the boot messages and find out the name of your HD.
-
Not if you never get to a console. ;)
There should be aliases in place to take care of anything that still points at ad0 as opposed to ada0. I speculated that perhaps that isn't working for swap.There is a thread that collates all the reports of this error, lets try and keep all info there:
https://forum.pfsense.org/index.php?topic=87542.0Steve
-
Didn't know about the aliases :)
I just modified the fstab file
-
No reason to know, it should 'just work'. ;)
Did you update to BIOS 8_1 to make this load do you think?
Steve
-
I got Bios_81 on mine yes, and the HD settings are set to auto.
The only thing i had to change is the fstab file or when booting, testing it with set vfs.root.mountfrom=ufs:/dev/adxxxxxx -
I think it's the swapper process trying to use DMA and failing. On my box I had to enable UDMA for the IDE channel I was using, did you have to make that change?
Also:
@unknown001:Also enable ACPI function and IDE primary slave UDMA is now "auto" mode. No longer crashing
Steve
-
yes i also did those steps
-
Ok this is an ACPI problem, it must be enabled:
https://forum.pfsense.org/index.php?topic=87542.msg484384#msg484384Steve
-
I am a little lost on what I should try next….
-
The HDD is being detected as stephenw10 stated since it starts the boot process but ends with that kernel panic info I posted with a trace after.
-
You need to enable ACPI in the BIOS or at least check it's enabled. It could potentially be something else but that will definitely cause the panic you're seeing.
Steve
