Boot problem on 3 diffenert PC with pfsense 1.2.2



  • Good day!

    I have tried to boot pfsense 1.2.2 on 3 PCs. On all 3 cases it boots but did not see the Ethernet cards (only plip0). On one PC (P4 desktop) I have 2 EthCards. EthCards are working correctly on Linux (Ubuntu & Mandriva) and Win. So I can’t do anything with this. I tried to change configs from bios, it didn't help. Also I tried boot and work on VM and it works correctly, I have able to work on pfsense from web interface.
    Looks like it work only on VM (SunBox).

    What can you suggest to try? What can I change or reconfigure?
    Thanks in advance…



  • What kind of NICs are these?
    Just because they work under Linux doesn't mean they work under pfSense (which is FreeBSD).
    Did you take a look at the hardware compatibility list?
    http://www.freebsd.org/releases/7.2R/hardware.html



  • Yes, my EthCards are exists in hardware compatibility list. They are Realtek RTL8139/810X Family PCI Fast Ethernet NIC, they should be recognized by interface named "re" according to h.c. list. Anyway I did another experiment. I mount the pfsense 1.2.2 on other PC with onboard LAN and it saw the LAN card named "rl", I think it is OK. After that I did the same thing with one of my cards on same PC and it saw only the onboard LAN, it didn’t saw my card again.
    I think the problem is in drivers. But it should be supported according to h.c. list.
    Anyway I have the driver (tgz) for mentioned cards for freeBCD platform.
    Can I install somehow or how can I use drivers during boot of pfsense 1.2.2.

    Thanks for answers.



  • Try 1.2.3RC3, the driver support is better than 1.2.2.



  • If I recall correctly, pfSense 1.2.2 is based on FreeBSD 6.x so the FreeBSD 7.2 hardware compatibility list won't be all that useful.



  • I was try the boot with 1.2.3 RC3, didn't help. The EthCards still does not recognize.
    Please let me now how can I dump the log of startup maybe it could help us to resolve the issue.



  • Out of your three unspecified PCs and unspecified number of unspecified ethernet cards, can you get a combination (possibly using an on board LAN interface) with two LAN interfaces recognised by pfSense? If so, you should be able to configure it and get to the shell prompt and then connect via the web GUI, then from the Diagnostic Menu click on Command and then in the command box type dmesg and post the resulting output as a reply. Thats the startup output. Use pfSense 1.2.3 RC3 to get the most up to date hardware support.

    Alternatively, on the same box, boot the linux system of choice and post the output of the shell command pciconf -l here. That will list the PCI devices on the system which might be helpful.

    If the motherboard (in the case of onboard devices) or the NIC card is "too new" (including a "new" variant of a currently supported device) there might not be a FreeBSD driver for it or the driver might not yet have had sufficient testing to shake out "startup bugs". Also be aware that over the life of a particular model some suppliers change the chipset and don't change the model number. This seems to be particularly true of wireless devices where I think there is one D-LInk model that could have one of 4 different chipsets each from a different manufacturer. There are a number of suppliers (including Netgear, Linksys and Belkin) who have adopted this practice.



  • Here are device parameters of my computer with 2 LAN. I took them from Everest under xp.
    I don't see any devices which can conflict with each other. Please, note here if you see such one.
    So the pfsense should be easy installed on this machine. But it can't because it doesn't recognize the LAN cards.
    Also, how can I use drivers of Ethernet cards for freeBSD? I have them but I don't know how to use them.
    Does anyone install the driver of LAN during boot from CD? Thanks


    Motherboard:  
      CPU Type   Intel Pentium 4, 1513 MHz (15 x 101)  
      Motherboard Name   Asus P4SDR-VM (3 PCI, 2 SDR DIMM, Audio, Video)  
      Motherboard Chipset   SiS 650GL  
      System Memory   480 MB (PC133 SDRAM)  
      DIMM1:    256 MB PC133 SDRAM (3.0-3-3-6 @ 133 MHz) (2.0-2-2-5 @ 100 MHz)  
      DIMM2: Kingston 2MX64PC133CL3 168P   256 MB PC133 SDRAM (3.0-3-3-6 @ 133 MHz) (2.0-2-2-5 @ 100 MHz)  
      BIOS Type   Award Medallion (08/09/02)  
      Communication Port   Communications Port (COM1)  
      Communication Port   ECP Printer Port (LPT1)

    Storage:  
      IDE Controller   SiS PCI IDE UDMA Controller  
      Disk Drive   Maxtor 6E040L0 (40 GB, 7200 RPM, Ultra-ATA/133)  
      Optical Drive   LITEON CD-ROM LTN526 (52x CD-ROM)  
      SMART Hard Disks Status   OK

    Network:  
      Network Adapter   Realtek RTL8139/810X Family PCI Fast Ethernet NIC  
      Network Adapter   RTL8139D PCI Fast Ethernet Adapter

    DMI:  
      DMI BIOS Vendor   Award Software, Inc.  
      DMI BIOS Version   ASUS P4SDR-VM ACPI BIOS Revision 1006  .  
      DMI Motherboard Product   P4SDR-VM  
      DMI Motherboard Version   REV 1.xx  
      DMI Chassis Type   Tower  
      DMI Total / Free Memory Sockets   2 / 0



  • @uterator:

    I took them from Everest under xp.

    I don't know what that means. What's Everest?

    @uterator:

    Also, how can I use drivers of Ethernet cards for freeBSD? I have them but I don't know how to use them.
    Does anyone install the driver of LAN during boot from CD?

    pfSense device drivers are built into the pfSense kernel. This is different to most Linux distributions where the device drivers are typically distributed as kernel modules which are loaded "on demand".

    I would expect your NICs to be recognised by the re or rl driver.  Its possible the driver(s) detected an error when attempting to attach to the NICs and hence made the NICs unavailable.

    Can you post the startup output?



  • @wallabybob:

    I don't know what that means. What's Everest?

    Everest is a system diagnostic soft for PC.

    @wallabybob:

    Its possible the driver(s) detected an error when attempting to attach to the NICs and hence made the NICs unavailable.

    I agree with you because at start up I can see that some parts were not loaded successfully. I wrote that I can't take log of start up.

    Actually my PC hasn't onboard LAN for opening the web page how I understand I should have 2 working LAN but that is what I want.
    I figure out that I can't take startup output without web page on other PC and as the problem in not in drivers (they are exists in h.c list) only the thing that I can do it is take the snapshots from the screen and find the devices which can't be loaded successfully.
    I will take the texts of not loaded parts how much I can. I think there is a some thing not supporting device on my PC which I cant figure out. I will wrote you when I will find something important.
    Thanks a lot.



  • You said you have seen the problem on a PC with onboard "re" LAN.

    Suggestion:

    Put your cards on that PC. Install or boot pfSense. At interface configuration time specify you want to use VLANs and configure two VLANs, one for WAN and one for WAN. At the later prompt specify option 8 to get a shell prompt. Then type

    dmesg | more

    which will display the startup output a screenfull at a time. Use a digital camera (or phone) to capture the who startup output and post it somewhere we can look at it.

    I suggest using pfSense 1.2.3-RC3 or one of the RC3 snapshot builds to get the most up to date hardware support.

    Here's an example of sartup output showing an attach failure which resulted in the device not being available. (This is to give you an idea of what to look for.)

    re0: <realtek 8168="" 8168b="" 8168c="" 8168cp="" 8168d="" 8111b="" 8111c="" 8111cp="" pcie="" gigabit="" ethernet="">port 0xd800-0xd8ff mem 0xf7eff000-0xf7efffff,0xf7ee0000-0xf7eeffff irq 18 at device 0.0 on pci4
    re0: Chip rev. 0x3c000000
    re0: MAC rev. 0x00400000
    re0: PHY write failed
    re0: PHY write failed
    re0: MII without any phy!
    device_attach: re0 attach returned 6</realtek>

    I believe in this case the problem was fixed in a later version of pfSense.


Log in to reply