PCEngines alix2c3 (Substitute for WRAP) boot failes

luma

Hello Eweri,

I have to investigate for reboot. It seems working, I can't serial connect at the moment.

Here is the solution for full install (I wrote the last part, Using VirtualBox) :
http://devwiki.pfsense.org/FullInstallOnWRAP

But it's not a good idea on CF! CF don't support too much write cycle! You are warn!

Bye

Sorry Eweri, I forgot you. Same answer : no issue at all with reboot on 1.2RC3 10/26/2007.

Bye

mlabenda

This is my dmesg output

Copyright 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 trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE-p9 #0: Mon Dec 10 04:26:02 EST 2007
sullrich@builder6.pfsense.com:/usr/obj.pfSense/usr/src/sys/pfSense_wrap.6
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Geode(TM) Integrated Processor by AMD PCS (431.65-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2
Features=0x88a93d <fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>AMD Features=0xc0400000 <mmx+,3dnow+,3dnow>real memory = 134217728 (128 MB)
avail memory = 121872384 (116 MB)
pnpbios: Bad PnP BIOS data checksum
wlan: mac acl policy registered
K6-family MTRR support enabled (2 registers)
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
cpu0 on motherboard
pcib0: <host to="" pci="" bridge="">pcibus 0 on motherboard
pci0: <pci bus="">on pcib0
MFGPT bar: f00100006200
pci0: <encrypt decrypt,="" entertainment="" crypto="">at device 1.2 (no driver attached)
vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0
miibus0: <mii bus="">on vr0
ukphy0: <generic ieee="" 802.3u="" media="" interface="">on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:0d:b9:12:9f:84
vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 11 at device 10.0 on pci0
miibus1: <mii bus="">on vr1
ukphy1: <generic ieee="" 802.3u="" media="" interface="">on miibus1
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr1: Ethernet address: 00:0d:b9:12:9f:85
vr2: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1800-0x18ff mem 0xe0080000-0xe00800ff irq 12 at device 11.0 on pci0
miibus2: <mii bus="">on vr2
ukphy2: <generic ieee="" 802.3u="" media="" interface="">on miibus2
ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr2: Ethernet address: 00:0d:b9:12:9f:86
ath0: <atheros 5212="">mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0
ath0: Ethernet address: 00:02:6f:44:30:4b
ath0: mac 10.4 phy 6.1 radio 6.3
isab0: <pci-isa bridge="">port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at device 15.0 on pci0
isa0: <isa bus="">on isab0
atapci0: <generic ata="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0
ata0: <ata 0="" channel="">on atapci0
ata1: <ata 1="" channel="">on atapci0
ohci0: <ohci (generic)="" usb="" controller="">mem 0xefffe000-0xefffefff irq 15 at device 15.4 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: <ohci (generic)="" usb="" controller="">on ohci0
usb0: USB revision 1.0
uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
ehci0: <amd cs5536="" usb="" 2.0="" controller="">mem 0xefffd000-0xefffdfff irq 15 at device 15.5 on pci0
ehci0: [GIANT-LOCKED]
usb1: EHCI version 1.0
usb1: companion controller, 4 ports each: usb0
usb1: <amd cs5536="" usb="" 2.0="" controller="">on ehci0
usb1: USB revision 2.0
uhub1: AMD EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub1: 4 ports with 4 removable, self powered
orm0: <isa option="" rom="">at iomem 0xe0000-0xeafff on isa0
ppc0: parallel port not found.
sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0
sio0: type 16550A, console
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
RTC BIOS diagnostic error 80 <clock_battery>Timecounter "TSC" frequency 431646313 Hz quality 800
Timecounters tick every 10.000 msec
Fast IPsec: Initialized Security Association Processing.
ad0: 967MB <cf 20070131="" card="" 1gb="">at ata0-master PIO4
GEOM_LABEL: Label for provider ad0a is ufs/pfSense.
GEOM_LABEL: Label for provider ad0d is ufs/pfSenseCfg.
Trying to mount root from ufs:/dev/ufs/pfSense

___
/ f \
/ p \/ Sense
\/ \
\/

Welcome to pfSense 1.2-RC3 on the 'embedded' platform…

Setting up embedded specific environment...
done.
Mounting filesystems...
done.
Creating symlinks...
.
.
.
done.
Launching PHP init system...
done.
Initializing...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
done.
Starting device manager (devd)...
done.
Loading configuration...
.
.
.
done.
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...
vr0: link state changed to UP
vr1: link state changed to UP
vr2: link state changed to DOWN
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.
pflog0: promiscuous mode enabled
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.
Starting OpenNTP time client...
done.
Starting CRON...
done.
Executing rc.d items...
Starting /usr/local/etc/rc.d/*.sh...
done.
appending output to nohup.out
Bootup complete

FreeBSD/i386 (pfSense.local) (console)

*** Welcome to pfSense 1.2-RC3-embedded on pfSense ***

LAN* -> vr0 -> 192.168.178.1

WAN* -> vr1 -> 0.0.0.0(DHCP)

OPT1(OPT1) -> vr2 -> NONE

pfSense console setup

0) Logout (SSH only)
1) Assign Interfaces
2) Set LAN IP address
3) Reset webConfigurator password
4) Reset to factory defaults
5) Reboot system
6) Halt system
7) Ping host
8) Shell
9) PFtop
10) Filter Logs
11) Restart webConfigurator
12) pfSense PHP shell
13) Upgrade from console

Enter an option:
vr0: Using force reset command.</cf></clock_battery></isa></amd></amd></ohci></ohci></ata></ata></generic></isa></pci-isa></atheros></generic></mii></via></generic></mii></via></generic></mii></via></encrypt></pci></host></mmx+,3dnow+,3dnow></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>

eweri

@eweri:

Could you test if reboot works, please? My 1.2-RC3 panics during reboot but it reboots. If I use the pfsense-1024-image the cpu got hung during reboot and I have to pull the plug :-(
BTW. You can see the panic at the seriell console, only.

Bye,
eweri

Just reply to my self: Installed tinyBIOS 0.99 today and now I have no reboot issues any more. Going to try the 1024MB image and see if the reboot-hung is gone also.

Bye,
eweri

eweri

@eweri:

Just reply to my self: Installed tinyBIOS 0.99 today and now I have no reboot issues any more. Going to try the 1024MB image and see if the reboot-hung is gone also.

Bad news: it still panics with the pfsense-1024MB-image and got hung until i pull the plug :(

Here is the console output:

pfSense is now shutting down …

Waiting (max 60 seconds) for system process vnlru' to stop...done Waiting (max 60 seconds) for system process bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 0 done
All buffers synced.
Uptime: 4m3s
ukphy0: detached
miibus0: detached
ukphy1: detached
miibus1: detached
ukphy2: detached
miibus2: detached
Rebooting...
Keyboard reset did not work, attempting CPU shutdown
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc3faae10
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc05ef0ae
stack pointer = 0x28:0xc7d44c04
frame pointer = 0x28:0xc7d44c0c
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 1 (init)
trap number = 12
panic: page fault
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc196ed28
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc061add2
stack pointer = 0x28:0xc7d44b1c
frame pointer = 0x28:0xc7d44b4c
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 1 (init)
trap number = 12
panic: page fault
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc196ed28
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc061add2
stack pointer = 0x28:0xc7d44a34
frame pointer = 0x28:0xc7d44a64
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 1 (init)
trap number = 12
panic: page fault
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc196ed28
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc061add2
stack pointer = 0x28:0xc7d4494c
frame pointer = 0x28:0xc7d4497c
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 1 (init)
trap number = 12
panic: page fault
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc196ed28
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc061add2
stack pointer = 0x28:0xc7d44864
frame pointer = 0x28:0xc7d44894
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 1 (init)
trap number = 12
panic: page fault
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc196ed28
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc061add2
stack pointer = 0x28:0xc7d4477c
frame pointer = 0x28:0xc7d447ac
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = kk
Fatal double fault:
eip = 0xc0635d0e
esp = 0xc7d43fe0
ebp = 0xc7d440a8
panic: double fault
Uptime: 4m6s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort

luma

As I can see the 1024 image from http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/embedded/1024/ is pretty old (10/14/07).
Please can you upgrade to lastest snapshot using file http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/updates/pfSense-Embedded-Update-1.2-RC3.tgz? You have to use the upgrade utility provided in the console (option 13) through SSH or serial connection.

My 2 cents…

naughtyusmaximus

Does anyone have any thoughts as to why I might still be getting a kernel panic? I've updated to .99 for the bios. I've installed the full version of pfSense 1.2 rc3 onto a 4GB microdrive.

naughtyusmaximus

I have two ALIX units, and I was able to get it working ok with one of them. But with the oe with 3 LAN ports, 2x USB, and 1X mini-PCI, the error on bootup I get is:

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:0xc06eb66e
stack pointer           = 0x28:0xc0c20b28
frame pointer           = 0x28:0xc0c20b28
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</ehci>

eweri

@luma:

As I can see the 1024 image from http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/embedded/1024/ is pretty old (10/14/07).
Please can you upgrade to lastest snapshot using file http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/updates/pfSense-Embedded-Update-1.2-RC3.tgz? You have to use the upgrade utility provided in the console (option 13) through SSH or serial connection.

My 2 cents…

Update went okay - but no config-menu at the console any more :-( This is what I get at the console:
….
Starting OpenNTP time client...done.
Starting CRON... done.
Executing rc.d items...
Starting /usr/local/etc/rc.d/mdnsresponder.sh...done.
appending output to nohup.out
Bootup complete

and than I can type any thing - no reaction from console.
When I login with ssh I get the console setup ???

I did not test it with the 1024MB image - going to do this next

Bye,
eweri

eweri

@eweri:

and than I can type any thing - no reaction from console.
When I login with ssh I get the console setup ???

problem solved - mv /etc/ttys /etc/ttys_back and cp /etc/ttys_wrap /etc/ttys and reboot :)

eweri

@naughtyusmaximus:

Does anyone have any thoughts as to why I might still be getting a kernel panic? I've updated to .99 for the bios. I've installed the full version of pfSense 1.2 rc3 onto a 4GB microdrive.

Maybe I was a little to quick with "no panics any more" because I had at least one kernel panic at reboot with tinyBIOS 0.99. I upgraded to the latest snapshot (see comment from luma) and rebootet the system 5 or 6 times - no kernel panics until now. :)

Bye,
eweri

luma

@eweri:

[…]
no kernel panics until now. :)

Bye,
eweri

Good to hear that!

Regards

naughtyusmaximus

:( Unfortunately my unit doesn't boot to the point where I can log in at all, so I can't install any updates. Also, I'm trying to use the full installation on this unit (as I have a microdrive for it). Are there any other options for me, or will I have to wait for 1.3?

prossi

Im having a different problem :)

I have been able to install the FreeDOS image on 1 CF Card (128Mb) and booted off that with no problem. From here i have upgraded my BIOS to the latest available (0.99). This worked great:


PC Engines ALIX.2 v0.92
640 KB Base Memory
261120 KB Extended Memory

01F0 Master 848A Flash Card                              
Phys C/H/S 994/8/32 Log C/H/S 994/8/32
FreeDOS kernel build 2036 cvs [version Aug 18 2006 compiled Aug 18 2006]
Kernel compatibility 7.10 - WATCOMC - 80386 CPU required - FAT32 support

(C) Copyright 1995-2006 Pasquale J. Villani and The FreeDOS Project.
All Rights Reserved. This is free software and comes with ABSOLUTELY NO
WARRANTY; you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation;
either version 2, or (at your option) any later version.
C: HD1, Pri[ 1], CHS=    0-1-1, start=     0 MB, size=   124 MB
FreeDOS HIMEM64 3.26 [Aug 25 2006] (c) 1995, Till Gerken 2001-2006 tom ehlert
HIMEM - Always On A20 method used
Kernel: allocated 43 Diskbuffers = 22876 Bytes in HMA

FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
C:\>sb
ALIX flash update (C)2007 PC Engines GmbH
Flash ID = 1 FFFF GPI = FF
Flash ID = 0 9D37 GPI = 01
Reading 512KB flash image alix1.bin................
Compare Erase Program Verify - update OK.
C:\>

PC Engines ALIX.2 v0.99
640 KB Base Memory
261120 KB Extended Memory

I have also written the 1.2RC3 Embedded image to another 128Mb CF card using Physdiskwrite:


C:\pfsesnse>physdiskwrite pfSense-1.2-RC3-Embedded.img.gz

physdiskwrite v0.5.1 by Manuel Kasper <mk@neon1.net>Searching for physical drives...

Information for \\.\PhysicalDrive0:
   Windows:       cyl: 4863
                  tpc: 255
                  spt: 63
   C/H/S:         16383/16/63
   Model:         ST340014AS
   Serial number:             
   Firmware rev.: 8.12

Information for \\.\PhysicalDrive1:
   Windows:       cyl: 15
                  tpc: 255
                  spt: 63

Which disk do you want to write? (0..1) 1
About to overwrite the contents of disk 1 with new data. Proceed? (y/n) y
Found compressed image file
122441728/122441728 bytes written in total</mk@neon1.net>

But when i try to boot off this CF Card i get the follow error:


PC Engines ALIX.2 v0.99
640 KB Base Memory
261120 KB Extended Memory

01F0 Master 848A Flash Card                              
Phys C/H/S 994/8/32 Log C/H/S 994/8/32
Boot error

or this:


PC Engines ALIX.2 v0.99
640 KB Base Memory
261120 KB Extended Memory

01F0 Master 848A Flash Card                              
Phys C/H/S 994/8/32 Log C/H/S 126/32/63
No boot device available, press Enter to continue.

Any ideas?

My next step will be to try dd under linux, incase its a problem with phydiskwrite.

mlabenda

again

i have a 2c2 Alix with Bios 0.99 and it works like a champ (up now since almost 6 days)
I used the latest snapshot (Version number on webgui shows 1.2RC3)
I have a cheap 1GB CF Card and used gunzip -c pfsense.img.gz | dd=of/dev/sdx bs=16k (i'm on linux)
to put the filesystem on the cf card

pfsense is now almost as fast as m0n0wall 1.2.3x and faster than 1.3bx
And i got OpenVPN working

I'm happy

Great work

prossi

Seems like phydiskwrite was the problem.

redid it with dd and it booted without a problem:


     ___
 ___/ f \
/ p \___/ Sense
\___/   \
    \___/

Welcome to pfSense 1.2-RC3 on the 'embedded' platform...

Setting up embedded specific environment... done.
Mounting filesystems... done.
Creating symlinks......done.
Launching PHP init system... done.
Initializing.................. done.
Starting device manager (devd)...done.
Loading configuration......done.

Network interface mismatch -- Running interface assignment option.

Valid interfaces are:

vr0     00:0d:b9:12:78:b8
vr1     00:0d:b9:12:78:b9
vr2     00:0d:b9:12:78:ba
ath0    00:80:48:4f:0c:28

ircman

Hi all!,

I have installed pfsense 1.2-RC3 (not the embedded version) onto a 20gb harddisk and I'm trying to boot it with my Alix2C3,
But i'm getting page fault errors (see below). I was reading on some topics and it seems there is a problem in the EHCI usb driver of Freebsd.
Is there a way to disable usb driver ?


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:0xc06eb66e
stack pointer           = 0x28:0xc0c20b28
frame pointer           = 0x28:0xc0c20b28
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

Regards,

sullrich

Update the ALIX's BIOS. Known problem but has been resolved.

ircman

Hi!,

I;m running the latest 0.99 version from the 10th of december. So looks like its not resolved ?

mezza

@sbyoon.

You're a star. Tried for hours to get BIOS update working with XMODEM. If any one has instructions I'd be extremely grateful for enlightenment.

Ended up downloading your CF image for FreeDOS and the 0.98g update, and just replacing the BIOS files with the 0.99 files.

Thanks,

mezza

naughtyusmaximus

@ircman:

Hi!,

I;m running the latest 0.99 version from the 10th of december. So looks like its not resolved ?

Yep, same here. This issue is not resolved for me either. :(