I'm trying to install 2.03 for the first time, but I can't seem to get anywhere. The first time I boot from the live CD, it gets as far as "fxp0: link state changed to DOWN". The only time I got anywhere beyond that, I chose verbose mode, answered "no" to create a VLAN, auto scanned interfaces, and when prompted to plug in the WAN interface I plugged it into my laptop by mistake… it seemed to assign fxp0 to WAN, and said link state was UP but nothing further, now no matter what option I choose when booting from the CD, no matter what cable is plugged into what NIC (there are three) , it still ends at "fxp0: link state changed to DOWN".
The goal is to replace a Zeroshell setup (which was working on this box) for a hotspot setup… WAN, WLAN, no LAN, captive portal for user authentication.
Here's what I get in verbose mode, with the network cable plugged into what I believe is fxp0:
What media are you using to install? LiveCD? Memstick? Serial Memstick?
LiveCD, as I said in the first post.
OK, the memstick is also technically the "live cd" just in USB form so I wanted to make sure you didn't use the serial memstick or something else that might be redirecting the console output away from the VGA terminal, hiding the boot log/messages.
Can you try a 2.1 snapshot? It could be something in that release that does not like the hardware in one way or another. Especially if it's stopping there just when booting off CD, it wouldn't have any knowledge of your previous configuration attempt.
Trying a different CD (or the memstick if you can boot USB) is also good to try in case there is a bad disk/dirty lens/etc.
OK, gotcha, thanks. I wasn't clear if anything from my previous attempt was getting saved to the hard drive causing the problem. The fact that one time it got farther than all the other attempts seems weird.
What about the "r10: couldn't map interrupt" message just before it hangs? Could that be related?
It may be a little while before I try it again… I just got word (I'm offsite right now) that the Zeroshell problem (which led me to try pfSense) was resolved, a bad gateway issue. I still want to get it working, since there's a lot more support here than on the ZS forums, but the urgency is reduced now.
The rl message may or may not be related, hard to say really. If you have to try it again, jump right to a 2.1 snapshot.