Thinking that the hardware could be the issue, I took the CF card out of a working wrap and dropped it into the suspect board and it booted just fine, telling me that it appeared to be either a bad load on the CF card or the card itself. I a little nervous loading the new software onto the working card, basically stranding me wothout a working system.
sorry for the confusion. I think I'm going to go down and buy me another CF Card. Barry P.S. how does one go about 'reformatting' a CF Card to an 'out-of-box status' using XP after it's been used in a BSD environment? Is it as simple as reformatting it through the Windows format commands? -----Original message----- From: Bill Marquette [EMAIL PROTECTED] Date: Tue, 8 Nov 2005 16:46:01 -0600 To: support@pfsense.com Subject: Re: [pfSense Support] Boot issues with .90 and .92 > It's very possible if your CF is going bad. I thought you said you'd > tried a different card though? > > --Bill > > On 11/8/05, Barry Kiesz <[EMAIL PROTECTED]> wrote: > > Yep that was you... I appreciate all the help that night... > > > > Quick question for you/everybody. Could this be a problem with my CF car> > > d? > > The reason I say this is that I attempted to load and run .86.4 and got t> > > he > > error now. It's really getting out of hand <GRIN>! Too many variables > > floating around. > > > > I'm going to re-group and try it again. > > > > > > Barry > > > > > -----Original Message----- > > > From: Holger Bauer [mailto:[EMAIL PROTECTED] > > > Sent: Monday, November 07, 2005 2:30 PM > > > To: support@pfsense.com > > > Subject: AW: [pfSense Support] Boot issues with .90 and .92 > > > > > > My IRC/forum nick is hoba. > > > > > > > -----Ursprüngliche Nachricht----- > > > > Von: Barry Kiesz [mailto:[EMAIL PROTECTED] > > > > Gesendet: Montag, 7. November 2005 21:11 > > > > An: support@pfsense.com > > > > Betreff: RE: [pfSense Support] Boot issues with .90 and .92 > > > > > > > > > > > > This what I have and was able to reproduce this on 2 wrap > > > boxes (same > > > > CF card though). I popped the CF card that had a pre.90 > > > image on it > > > > and it booted on both wrap boards. > > > > > > > > WRAP.1E v1.09 > > > > 640 KB Base Memory > > > > 130048 KB Extended Memory > > > > 512MB Kinston CF card > > > > pfSense-Embedded-0.92.img.bin.gz > > > > C:\Wrap>physdiskwrite.exe > > > > physdiskwrite v0.5 by Manuel Kasper <[EMAIL PROTECTED]> > > > > > > > > Could it be a format issue on my CF card? Not knowing a whole lot > > > > about these, I'm just grabbing at straws > > > > > > > > Thanks for any help.. > > > > > > > > > > > > Barry > > > > > > > > P.S. Holger, What's you nic on the IRC channel?... 'Cause I > > > think you > > > > were the one helping me out last week. > > > > > > > > > -----Original Message----- > > > > > From: Holger Bauer [mailto:[EMAIL PROTECTED] > > > > > Sent: Monday, November 07, 2005 1:56 PM > > > > > To: support@pfsense.com > > > > > Subject: AW: [pfSense Support] Boot issues with .90 and .92 > > > > > > > > > > I have been using all versions of pfsense at my wrap with > > > 4 nics (3 > > > > > on board, 1 atheros). I noticed random reboots on applying wlan > > > > > settings with pre .90 versions. This stopped with .90 and > > > never came > > > > > back. Actually I have been running .90, .90a, .92 (which > > > was pulled > > > > > due some issues) and I'm pretesting 0.93 atm (which is the first > > > > > release with the new > > > > > freebsd6 release files). 0.93 runs pretty smooth and even > > > got faster > > > > > (webgui feels faster, +3 mbit throghput wan to lan). I > > > can confirm > > > > > the stability issues with wireless for pre .90 versions > > > but I never > > > > > had installationproblems or stability issues without > > > using wireless. > > > > > I'm running off from a 256 MB cf with the unmodified 128 MB image > > > > > written to it. > > > > > Just in case you didn't notice or haven't followed it, there is a > > > > > tutorial for seting up the wrap at > > > > > http://pfsense.com/index.php?id=36 .. I don't know if this is > > > > > helping you to get further, but I know quite a lot of > > > users from the > > > > > forums or the irc-channel using wraps without issues, even with > > > > > wireless nics (and I have 3 wrapsystems running 24/7 with > > > real live > > > > > conditions, 2 with wireless nics). > > > > > If you still don't get it running please reply with bios > > > versions. > > > > > Maybe this only pops up with a special bios version? I > > > have plenty > > > > > of wraps to test with (beginning from 1D to 1E > > > hardwarereleases and > > > > > I'm about to order 10 more wraps tomorrow which should > > > have latest > > > > > hardwarerelease and bios versions when they arrive. > > > > > > > > > > If someone is reading this and has a working wrap install please > > > > > reply with "it's working for me with pfsense 0.xx, wrap 1x, Bios > > > > > 1.0x. Also add if you are using a wireless nic or not (which > > > > > shouldn't prevent boot but it's nice to know;-) Maybe > > > we'll find a > > > > > matrix what systems are affected (if it's something like that and > > > > > there really is a bug with it). > > > > > > > > > > > > > > > Holger > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > > > > > Von: Barry Kiesz [mailto:[EMAIL PROTECTED] > > > > > > Gesendet: Montag, 7. November 2005 18:30 > > > > > > An: support@pfsense.com > > > > > > Betreff: [pfSense Support] Boot issues with .90 and .92 > > > > > > > > > > > > > > > > > > This is most likely a newbie issue, but here goes.. This is > > > > > > actually a two part question/issue! > > > > > > > > > > > > 1. For the past week I 've been trying to install a > > > fresh copy of > > > > > > Pfsense onto my wrap board. I'm able to install and boot .88 > > > > just fine. I > > > > > > attempted to overwrite the image on on 512MB CF card > > > with .90 and > > > > > > first gave the error messages (didn't save them) and ended on > > > > > > Boot prompt command. I attempted to install again after > > > > > > downloading a fresh copy off of the mirrors and then it > > > would get > > > > > > to this, sit there for a while and > > > > > then reboot: > > > > > > > > > > > > WRAP.1E v1.09 > > > > > > > > > > > > Wisp-Router.com > > > > > > Your Full Time Professionals > > > > > > > > > > > > 640 KB Base Memory > > > > > > 130048 KB Extended Memory > > > > > > > > > > > > 01F0 Master 848A SAMSUNG CF/ATA > > > > > > Phys C/H/S 999/16/63 Log C/H/S 499/32/63 > > > > > > - > > > > > > > > > > > > > > > > > > > > > > > > So then I took a little break and waited for .92 to > > > come out and > > > > > > now I get this and it just hangs there > > > > > > > > > > > > WRAP.1E v1.09 > > > > > > > > > > > > Wisp-Router.com > > > > > > Your Full Time Professionals > > > > > > > > > > > > 640 KB Base Memory > > > > > > 130048 KB Extended Memory > > > > > > > > > > > > 01F0 Master 848A SAMSUNG CF/ATA > > > > > > Phys C/H/S 999/16/63 Log C/H/S 499/32/63 Copyright (c) > > > 1992-2005 > > > > > > 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 6.0-RELEASE #0: Fri Nov 4 02:53:05 UTC 2005 > > > > > > > > > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/pfSense_wrap.6 > > > > > > > > > > > > > > > > > > Fatal trap 1: privileged instruction fault while in kernel mode > > > > > > instruction pointer = 0x20:0xc086588c > > > > > > stack pointer = 0x28:0xc0c20d20 > > > > > > frame pointer = 0x28:0xc0c20d68 > > > > > > 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 () > > > > > > trap number = 1 > > > > > > panic: privileged instruction fault > > > > > > Uptime: 1s > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > #2 question and the reason for the upgrade. I've been > > > having DHCP > > > > > > issues with pfsense. I've tried m0n0wall and don't > > > seem to have > > > > > > any issues. I really need to use pfsense for 2 reasons. First > > > > > > the intferface is great and two, I have an Atheros chipset on > > > > > > wirless card. Once I get this back on up I'll pay more > > > attention > > > > > > to the log files to see what my problem is... As I've tried > > > > > > different PCs throughout this process. > > > > > > > > > > > > > > > > > > Any help would be appreciated!! > > > > > > \ > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Barry > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] For > > > > > > additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > ____________ > > > > > Virus checked by G DATA AntiVirusKit > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] For > > > > > additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] For > > > additional > > > > commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > ____________ > > > Virus checked by G DATA AntiVirusKit > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] For > > > additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
