PCEngines alix2c3 (Substitute for WRAP) boot failes

Clown

The new alix2c3 (alix2c3 = 3 LAN / 1 miniPCI / LX800 / USB) doesn't work with the pfsense1.2RC2 WRAP image. After booting up I get the following error message (see below). With the m0n0wall it works, but I have to change the interface as they are named new vr0..2 instead of sis0..2 (WRAP)…

Enter a number: PC Engines ALIX.2 v0.98b
640 KB Base Memory
261120 KB Extended Memory

01F0 Master 848A
Phys C/H/S 1002/8/32 Log C/H/S 1002/8/32
€€€€<xê{—íöïàûòöû¿ûÿÿûöñ ààss÷ù¥óüüóóüüóóüüóóüüóóüüóóüúóóüüóóúúóóüüóóúüóóúúóóüüó ="" <br="">óüúóóüüóóúþ/boot/kernel/kernel text=0x4b5a14 data=0x908d4+0x42658 |

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]…
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered tradema
FreeBSD 6.2-RELEASE-p7 #0: Fri Aug 17 18:16:30 EDT 2007 Base Memory
261120 KB Extended Memor
sullrich@builder6.pfsense.com:/usr/obj.pfSense/usr/src/sys/pfSense_wrap.6
Phys C/H/S 1002/8/32 Log C/H/S 1002/8/32
Timecounter "i8254" frequency 1193182 Hz quality 02006 compiled Aug 18 2006]
CPU: Geode(TM) Integrated Processor by AMD PCS (498.05-MHz 586-class CPU) - WATCOMC - 80386 CPU required - FAT32 support
Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2Copyright 1995-2006 Pasquale J. Villani and The Fre
Features=0x88a93d<fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>All Rights Reserved. This is free software and comes wi
AMD Features=0xc0400000<mmx+,3dnow+,3dnow>W
real memory = 268435456 (256 MB)nd/or modify it under the terms o
avail memory = 253272064 (241 MB)
pnpbios: Bad PnP BIOS da
C: HD1, Pri[ 1], CHS= 0-1-1, start=
cpu0 on motherboardB
pcib0: <host to="" pci="" bridge="">pcibus 0 on motherboardS HIMEM64 3.26 [Aug 25 2006] 1995, Till Gerken
pci0: <pci bus="">on pcib0
pci0: <encrypt decrypt,="" entertainment="" crypto="">at device 1.2 (no driver attached)d
Kernel: allocated 43 Diskbuffers = 22876 Byte

vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1000-0x10ff mem 0xe0000000-0xe04-pre2 XMS_Swap [Aug 28 2006 00:29:00]
0000ff irq 10 at device 9.0 on pci02 v0.98b
miibus0: <mii bus="">on vr0
261120 KB Ex
ukphy0: <generic ieee="" 802.3u="" media="" interfacemaster="" 848a="" cf="" 128m ="" ="" <br="">(9) 9600 baud (2
vr0: Ethernet address: 00:0d:b9:12:73:acd (1) 115200 baud
vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1400-0x14ff mem 0xe0040000-0xe0
(W) HDD wait
(S) HDD slave
R Se
0400ff irq 11 at device 10.0 on pci0
(E) Etherboot enable
miibus1: <mii bus="">on vr1load
(Q)
ukphy1: <generic ieee="" 802.3u="" media="" interface="">on miibus1C Engines ALIX.2 v0.98b
640 KB B
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

01F0 Master 848A CF 128MB
vr1: Ethernet address: 00:0d:b9:12:73:ad002/8/32
vr2: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1800-0x18ff mem 0xe0080000-0xe0

0800ff irq 12 at device 11.0
Kernel: allocated 43 Diskbuffers = 22876 Bytes in HMA
e 15.4 on pci0
ohci0: [GIANT-LOCKED]Com version 0.84-pre2
usb0: OHCI version 1.0, legacy support
usb0: <ohci (generic)="" usb="" controller="">on ohci0rive C has no label
usb0: USB revision 1.0ber is 6D58-002C
uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
ehci0: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xefffd000-0xefffdfff irq 15 at d
evice 15.5 on pci0
ehci0: [GIANT-LOCKED]
usb1: EHCI version 1.0
usb1: wrong number of companions (1 != 2)
usb1: companion controller, 4 ports each:

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x2c
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06304ce
stack pointer = 0x28:0xc0c20bac
frame pointer = 0x28:0xc0c20bac
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)
trap number = 12
panic: page fault
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting…
Keyboard reset did not work, attempting CPU shutdown</ehci></ohci></via></generic></mii></via></generic></mii></via></encrypt></pci></host></mmx+,3dnow+,3dnow></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx></xê{—íöïàûòöû¿ûÿÿûöñ ààss÷ù¥óüüóóüüóóüüóóüüóóüüóóüúóóüüóóúúóóüüóóúüóóúúóóüüó >

GoldServe

Suspect USB. Can you disable USB??

Clown

No, in the "bios" I can only configurate the serial port.

luma

Hi!

I have just received exactly the same Alix as you. Just mounted, just new (30 mn ago) :)

It seems that we have the same bios version (0.98b), but I'm running 1.2RC3.

The box doesn't fail on USB like you but after on starting DHCP service. I'm trying to find a solution.

Maybe could you try to use the lastest 1.2RC3 snapshot and confirm?

Regards

PS : did you receive chocolate from Switzerland too? :)

jahonix

This might be the latest snapshot itself!
Another user seems to have the same issue:
http://forum.pfsense.org/index.php/topic,6736.0/topicseen.html
He only mentions a PC running pfSense which is unlikely to be an ALIX

Wait for one of the developers to look into this - or try an older snapshot.

luma

Here is part of my boot process without WAN port attached. Same result with it plugged.

No error message. With my PC set up (static IP), I can ping LAN port before DHCP is started. After no way.

Updating configuration...done.
Cleaning backup cache...done.
Setting up extended sysctls...done.
Syncing user passwords...done.
Starting Secure Shell Services...done.
Setting timezone...done.
Starting syslog...done.
Configuring LAN interface...done.
Configuring WAN interface...done.
Configuring OPT interfaces...done.
Configuring CARP interfaces...done.
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
Syncing system time before startup...done.
Configuring firewall......done.
Starting webConfigurator...done.
Starting DHCP service...done.
Starting DNS forwarder...done.
Setting up microcode and tx/rx offloading...done.
Starting FTP helpers...done.
Generating RRD graphs...route: writing to routing socket: No such process
done.
Starting DHCP service...done.

cmb

Clown: You need to use 1.2RC3, it's the first version that works on ALIX.
http://snapshots.pfsense.org/FreeBSD6/RELENG_1_2/

luma: Any BIOS newer than 0.92 has introduced BIOS bug(s) that cause boot failures. PC Engines is working on a fix, right now the only BIOS version that will work is 0.92.

Clown

@luma:

PS : did you receive chocolate from Switzerland too? :)

I'm swiss, so I can buy chocolate by miself ;D

cmb: So I need also to downgrade the bios to version 0.92?

Clown

With pfsense1.2RC3 it's working. But what bios version do I have, I thought it's 0.98b???

Clown

It's not realy working, pfsense come's up at console then I have to set the new names for the network interfaces (vr0..2). After setting this I get the following errors on console:

–--
Configuring WAN interface...done.
Configuring OPT interfaces...done.
Configuring CARP interfaces...done.
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
route: writing to routing socket: No such process
Syncing system time before startup...done.
Configuring firewall......done.
Starting webConfigurator...done.
Starting DHCP service...done.
Starting DNS forwarder...done.
Setting up microcode and tx/rx offloading...done.
Starting FTP helpers...done.
Generating RRD graphs...route: writing to routing socket: No such process
done.
Starting DHCP service...done.

After that nothing workes, the network interfaces don't work, neither I don't get a console menu.

luma

Clown : we have the same error…

cmb : I'm now trying to downgrade Bios version. I have now problem with creating a bootable Freedos image on 1GB CF...

luma

Downgraded to bios 0.92
pfSense 1.2RC3 (11/07/2007)

Works great!!! :D

EarlBacid

Where can I get the 0.92 BIOS?

luma

http://www.pcengines.ch/alix2.htm

I managed to get the 128MB FreeDos image running on my 1GB CF using WinImage. I don't really know how, because I tried too much things too much time… ??? Sorry

Clown

With 0.92 pfsense comes up, but still is very slow on booting because of error messages…

luma

Which errors messages?

If they are :

route: writing to routing socket: No such process

plug your WAN port! Example : with no battery on Alix, pfSense tries to sync date/time on Internet.

Regards

Clown

Yes, that was it :-\ - stupid me…

Anyone knows whats wrong with the 0.98b bios together with pfsense? m0n0wall and AskoziaPBX are working fine together with the 0.98b firmware.

Changelog of the alix bios:

ALIX tinyBIOS revision history
------------------------------

v0.98b	11/1/07

	- fix UART initialization

v0.98	10/31/07

	- skip DLL status check

v0.97	10/26/07

	- back to 400 MHz DRAM clock for ALIX.3*2

v0.96	10/25/07

	- always do HDD wait if enabled

v0.95	10/24/07

	- use 333 MHz DRAM clock for ALIX.3*2

v0.94	10/23/07

	- force MFGPT timer reset (undocumented MSR 5140002B per
	  workaround in AMD Linux driver)

	- fixed a bug in PCI BIOS find device function

	- auto detect DRAM clock to set correct refresh interval

v0.93	10/21/07

	- added port 92 reset support

	- added 19200 baud option

v0.92	10/3/07

	- added HDD wait option, adds some delay to allow detection of
	  conventional HDDs.

	- disable CS5536 diverse device power management to avoid MFGPT /
	  interrupt issues.

	- MFGPT issues: please observe AMD CS5536 data book section 5.16.3,
	  incorrect initialization sequence can HANG the system.

v0.90	9/25/07

	- Remapped audio and USB interrupts to offload regular PCI interrupts.

	- IRQ7 is no longer directed to the LPC bus, used as a default
	  interrupt for MFGPT high resolution timer.

	- Implemented BIOS setup. Press S during memory test to enter.

	- Added UMB (upper memory block) support.

ALIX / tinyBIOS quirks
----------------------

A20 gate

	A20 gate is always "open", prefer performance over support for
	broken legacy code.

HDD master / slave

	To reduce boot time, slave drives are not detected by default.
	Change the option in setup if required.

HDD wait

	Hard disk drives need more time to wake up, enable HDD wait in
	setup if necessary.

LPT IRQ

	IRQ7 is intentionally unmapped to allow use for MFGPT high speed
	timer.

RTC wake-up

	One customer reported strange behavior on ALIX.1C, set wake-up
	time to 999999 if problems occur.

UMB

	To support UMB (upper memory block), unused shadow RAM between
	C000 and E000 is left read/writeable.

Open issues
-----------

Boot device selection

	nice to have...

HDD support

	tinyBIOS does not include large HDD support (> about 40 GB) yet.

PCI boot ROMs

	Not handled correctly by tinyBIOS.

PCI bridges

	tinyBIOS bridge support is questionable, if in doubt send PCI dump +
	maybe sample hardware to PC Engines.

Port 92 restart

	Needs SMI emulation.

PXE boot

	Module added, but interferes with "S" setup key. Be persistent
	to enter setup. Shift-Tab cannot be entered through serial console,
	need to change to different PXE module without menu.

VGA

	ALIX.1C tinyBIOS does not support video.

Flash layout for ALIX						pd 070921
---------------------

The layout is controlled by the batch files used to build the BIOS,
for example lx3.bat.

00000 - 0FFFF	Config block (only first few bytes used, but the flash device
		has 64KB erase blocks)

10000 - 3FFFF	unused

40000 - 47FFF	unused / video BIOS (future use)

48000 - 5FFFF	unused

60000 - 6FFFF	PXE BIOS

70000 - 77FFF	SMI module

78000 - 78FFF	unused, space for runtime copy of config block

79000 - 7FFFF	tinyBIOS core

Memory layout for ALIX
----------------------

00000 - 9FFFF	RW	base 640K RAM

A0000 - BFFFF	-	unused / VGA memory

C0000 - C7FFF	RO	unused / video BIOS

C8000 - DFFFF	-	unused

E0000 - EFFFF	RW	PXE BIOS

F0000 - F7FFF	RW	SMI module

F8000 - F8FFF	RO	runtime copy of config block

F9000 - FFFFF	RO	tinyBIOS core

PCI Interrupt map
-----------------

Please note that ALIX.2A / ALIX.3A boards have a different mapping, please
use the correct files for these boards.

PCI dev	AD line	Int map		Description

00	..	-		unused

08	AD11	INTA		Geode LX host bridge (crypto)

10..40	12..18 	-		unused

48	AD19	INTB		LAN1 (right)

50	AD20	INTC		LAN2 (middle)

58	AD21	INTD		LAN3 (left)

60	AD22	INTA, INTB	miniPCI 1

68	AD23	-		unused

70	AD24	INTC, INTD	miniPCI2

78	AD25	INTA .. INTD	Geode CS5536

80..F8	..	-		unused

Interrupt map
-------------

IRQ0	timer
IRQ1	KBD (LPC)
IRQ2	cascade
IRQ3	COM1 serial (internal / LPC)
IRQ4	COM2 serial (LPC)
IRQ5	audio (CS5536)
IRQ6	FDC (LPC)
IRQ7	spare, used for MFGPT high resolution timer

IRQ8	RTC
IRQ9	PCI INTA
IRQ10	PCI INTB
IRQ11	PCI INTC
IRQ12	PCI INTD
IRQ13	floating point
IRQ14	IDE HDD
IRQ15	USB (CS5536)

dirom

Hello,

Can anyone explain me how to downgrade the bios to 0.92 ?
Can i use the freedos image from pcengines.ch on any 128mb compact flash or does only the cf128al have a geometry of 1002/8/32? ???

i have many 128mb cf cards here, but will they work with the freedos image without any modifications?

Thanks in advance

EarlBacid

ok, now I have the problem that I don't have a CF Card with this phys.

Does anybody know how I can use this FreeDOS (or another) image with a larger CF Card?

Everytime I tried to boot from my 512 MB CF Card I got the error "Invalid or damaged Bootable partition".
Th CF card itsels seems to work with the image, it readable with windows so I can put the BIOS file on it.

luma

Please try with WinImage. I add success with it. But I don't have any howto ready. And I don't really remember :) Sorry