Howto boot a 1.2.3 nano image on embedded ??

blastkiller

anyone got a solution how to boot from wrap ? i can´t get it to work

thanks

bplein

I am having the same issues with pfSense-1.2.3-2g-20090820-1453-nanobsd.img.gz (latest 2GB image as of today).

Brand new Alix board to replace my WRAP. My old WRAP image on a 256MB card works fine. The ALIX came with BIOS 0.99. First try with the above image ends up showing #### on keystrokes. I tried upgrading the BIOS to 0.99h, and it seemed to go fine, but it still shows 0.99 when I boot. And it still fails to boot the pfSense-1.2.3-2g-20090820-1453-nanobsd.img.gz image.

I will go back and try an older image, but I don't want to play CF-imaging-dude all night.

Any ideas?

gloomrider

@bplein:

I am having the same issues with pfSense-1.2.3-2g-20090820-1453-nanobsd.img.gz (latest 2GB image as of today).

Brand new Alix board to replace my WRAP. My old WRAP image on a 256MB card works fine. The ALIX came with BIOS 0.99. First try with the above image ends up showing #### on keystrokes. I tried upgrading the BIOS to 0.99h, and it seemed to go fine, but it still shows 0.99 when I boot. And it still fails to boot the pfSense-1.2.3-2g-20090820-1453-nanobsd.img.gz image.

I will go back and try an older image, but I don't want to play CF-imaging-dude all night.

Any ideas?

Based on your description, it would seem your BIOS update failed. Mine clearly shows v0.99h:


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

01F0 Master 848A SanDisk SDCFH2-002G                     
Phys C/H/S 3970/16/63 Log C/H/S 992/64/63                

1   FreeBSD
2   FreeBSD

Boot:   2 
//bboooott..ccoonnffiigg::  --DD

bplein

You are right!

I didn't follow all of the BIOS upgrade instructions. I uploaded the 512K .img file, you are supposed to upload the smaller .upd file.

It now works.

Thanks!

cmb

@blastkiller:

anyone got a solution how to boot from wrap ?

It doesn't work on WRAP right now.

orangepeelbeef

I have the same issue on the WRAP. Latest bios 1.11 all I get are hash marks after the boot prompt :(
I tried the pfSense-1.2.3-2g-20090820-1453-nanobsd.img.gz as well as the latest 2.0-alpha-alpha and both of them do the same thing.

PC Engines WRAP.2B/2C v1.11
640 KB Base Memory
130048 KB Extended Memory

01F0 Master 044A CF2GHS
Phys C/H/S 3949/16/63 Log C/H/S 987/64/63

1 FreeBSD
2 FreeBSD

Boot: 1 ####################################################

cmb

@orangepeelbeef:

I have the same issue on the WRAP.

See the post above yours.

@cmb:

@blastkiller:

anyone got a solution how to boot from wrap ?

It doesn't work on WRAP right now.

spindizzy

I'm having the same problem - for a bit more info, see this thread:

http://forum.pfsense.org/index.php?topic=18302

specifically reply number 4. I'm going to give disabling packet mode a try as suggested above.

Edit - which worked beautifully. Thanks jimp.

orangepeelbeef

Durrrr… there is a page 2. Sorry. I read somewhere the nopacket thing was put into future images, is that not the case? With the nopacket change will it work on WRAP or still no?

@cmb:

@orangepeelbeef:

I have the same issue on the WRAP.

See the post above yours.

@cmb:

@blastkiller:

anyone got a solution how to boot from wrap ?

It doesn't work on WRAP right now.

jimp

@orangepeelbeef:

Durrrr… there is a page 2. Sorry. I read somewhere the nopacket thing was put into future images, is that not the case? With the nopacket change will it work on WRAP or still no?

Read the rest of my post here:
http://forum.pfsense.org/index.php/topic,18302.msg94911.html#msg94911
The gist of it is:
ALIX needs packet mode to work on slice #1 and slice #2.
WRAP needs nopacket, and even then only works on slice #1.

So the images can't be set to nopacket, or it breaks updates on ALIX, and it can't be set to packet and work on WRAP.

cmb/sullrich are working with PC engines to see if a BIOS update can be made for the WRAP which will resolve this, otherwise I'm not sure what will happen.