Problem booting nanobsd (1.2.3)



  • Hi,

    I'm having some problems with nanobsd installation (version 1.2.3). The "flashing" works like a charm (I think :p) both with dd and physdiskwrite. It writes all the data with no errors and then partially boot.

    It boots and then "hang" on a blinking "_". Not able to connect via putty. Have re-installed a couple of times and also tried hacom's version of nanobsd with vga support, it hangs on the "F1: Pfsense"-moment.

    When using 2.0 nanobsd it boots fine.

    Any clue?



  • When 2.0 works why do you care about 1.2.3?

    pfSense 1.2.3 contains an older version of FreeBSD than is in 2.0. PERHAPS your motherboard includes a chipset that doesn't work with the version of FreeBSD in pfSense 1.2.3.



  • @wallabybob:

    When 2.0 works why do you care about 1.2.3?

    pfSense 1.2.3 contains an older version of FreeBSD than is in 2.0. PERHAPS your motherboard includes a chipset that doesn't work with the version of FreeBSD in pfSense 1.2.3.

    My motherboard is a Intel D945GCLF2 (Atom 330 onboard) with 945GC chipset. Didn't find any particular on google. Well, I'll try install the full version on a harddrive instead to se if it works.

    Why I wan't 1.2.3 is because of multi-wan with same gateways. You will find a small explanation here: http://forum.pfsense.org/index.php/topic,45087.msg237262.html#msg237262

    According to the forums this isn't supported in 2.0.



  • @w00t:

    Why I wan't 1.2.3 is because of multi-wan with same gateways. You will find a small explanation here: http://forum.pfsense.org/index.php/topic,45087.msg237262.html#msg237262

    I don't think the particular problem described in the linked page is specific to pfSense 2.0.x I don't see why you wouldn't also have that on pfSense 1.2.3.

    Did you really have on a pfSense 1.2.3 system 5 WAN interfaces on VLANs sharing the same physical interface all managing to get different IP addresses assigned by the same DHCP server?



  • @wallabybob:

    @w00t:

    Why I wan't 1.2.3 is because of multi-wan with same gateways. You will find a small explanation here: http://forum.pfsense.org/index.php/topic,45087.msg237262.html#msg237262

    I don't think the particular problem described in the linked page is specific to pfSense 2.0.x I don't see why you wouldn't also have that on pfSense 1.2.3.

    Did you really have on a pfSense 1.2.3 system 5 WAN interfaces on VLANs sharing the same physical interface all managing to get different IP addresses assigned by the same DHCP server?

    Oh, no. What I ment was that pfsense 2.0 doesn't support multiwan/loadbalance with mutiple WAN-links with the same gateway (1.2.3 doesn't either according to jimp (http://forum.pfsense.org/index.php/topic,45042.0.html)) tho it actually works just fine in 1.2.3. Thats why I want 1.2.3, the problem described in the other thread regarding vlan and dhcp assignment is the same in 1.2.3 as in 2.0 I guess.

    However, i think I will try to make a similar setup as described in the thread linked above on 2.0 before putting more time with this 1.2.3 nanobsd.. :p But if anyone recognize the situation why it get stuck on a blinking underline that would be great as well ;)



  • Hm, found a 1.2.3 nanobsd with vga-support in jimp's folder at files.pfsense.org. It installed and booted just fine.


Log in to reply