[pfsense embedded 1.2.3rc1] no output on com1, wont boot(?)



  • Hello :)

    I just tried to get pfsense 1.2.3rc1-embedded running from a 128MB SanDisk CF-card with a MSI IM-945GSE-A motherboard.

    Right after the BIOS-post I see this symbol ¦ (with a blinking _ beneath it), but I'm supposed to see a / I've read, and I'm not getting any output on the comports…
    Already checked the (XP HyperTerminal) settings, COM1 9600 8 N 1, that should be correct I believe and yes, I'm using a nullmodem cable ;) (To rule that out too :P)

    Any idea's about what's going wrong?

    With regards,

    Bart Grefte



  • Ah djeez, the heat outside seems to be messing with my head :P
    Why? Well, all comports where disabled in the BIOS….

    Guess what happened when I enabled COM1 ;)
    pfsense started, and could configure the NIC's.
    (Hint to developers: make some errormessages, then it would be easier to figure out what's wrong ;) )

    But now I've got another problem, the webinterface doesn't work.

    Hooked the system up to another computer with a networkcrosscable.
    There is a connection, the computer managed to get an IP with DHCP from the pfsense computer, but can't open the webinterface, page not found.
    And pings don't work either, timeouts, but now I don't know if pfsense is set to not respond to pings...



  • Did you make sure that you dont have an old default route on the "other computer" that's not pointing to the pfSense?



  • @bartgrefte:

    (Hint to developers: make some errormessages, then it would be easier to figure out what's wrong ;) )

    Of course, if you can't connect to the console, how are you going to read the error message?



  • @GruensFroeschli:

    Did you make sure that you dont have an old default route on the "other computer" that's not pointing to the pfSense?

    There aren't any routes on the computers present.

    But just solved the problem, seems that the crosscable I used doesn't work completely with a 100Mb NIC, hooked it up to a Gb NIC, and then I could access the webinterface :)

    @Cry:

    @bartgrefte:

    (Hint to developers: make some errormessages, then it would be easier to figure out what's wrong ;) )

    Of course, if you can't connect to the console, how are you going to read the error message?

    Uhm, good point…
    (Let's just blame the heat for me not thinking straight today ;) )

    edit: can't the bootloader give errors before VGA get's disabled?


Log in to reply