Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Dell SC440

    Scheduled Pinned Locked Moved Hardware
    15 Posts 4 Posters 9.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      fastcon68
      last edited by

      The Onboard Interface is enabled.  I connected a network cable to that interface.  It came up at a GB.  I still could not see it under PFSense.  However by connecting that interface I could ping from the firewall back to workstations on the network.  Workstations on the network could no longer get out on the internet or recieve DHCP addresses from the firewall.

      I have two broadcom adapters (1 on-board; 1 -pci - x), I can only see one of the two.  The on-board is unaccessible.  I removed the dual intel 100 mb adapter from the server.

      It was almost like the on-board and the pci-x card where on the same ireq or using the same resource.

      RC

      1 Reply Last reply Reply Quote 0
      • F
        fastcon68
        last edited by

        How can I upgrade from 6.2 to 6.3 without a system reinstall.

        RC

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          The Onboard Interface is enabled.  I connected a network cable to that interface.  It came up at a GB.

          How did you tell it came up at a GB? ifconfig?

          I still could not see it under PFSense.

          Where did you go looking for the interface? ifconfig command to pfSense shell? pfSense web gui? Have you run into the problem I described at http://forum.pfsense.org/index.php/topic,9101.0.html

          However by connecting that interface I could ping from the firewall back to workstations on the network.

          Well, something has seen that interface and initialised it. I presume you mean the ping reported a response. In that case the onboard interface has been assigned an IP address so its been configured.

          Workstations on the network could no longer get out on the internet or recieve DHCP addresses from the firewall.

          I have two broadcom adapters (1 on-board; 1 -pci - x), I can only see one of the two.  The on-board is unaccessible.  I removed the dual intel 100 mb adapter from the server.

          You say the onboard NIC is unaccessible BUT you also appear to say the onboard interface sees a ping response which also means it has been initialised and configured with an IP address so it must be "significantly accessible" even if its not accessible in the way you expect.

          It was almost like the on-board and the pci-x card where on the same ireq or using the same resource.

          PCI devices are intended to be able to share IRQs.

          The dmesg shows a Broadcom NIC and a RealTek NIC as well as two Intel fxp NICs. Where does the RealTek come from - you haven't previously mentioned it?  The dmesg shows 4 NICs: bge0 (a Broadcom), re0 (a RealTek),
          fxp0 and fxp1 (Intel 10/100 NICS). If this is the right number of NICs then maybe you haven't seen the 2nd Broadcom because its actually a RealTek?

          1 Reply Last reply Reply Quote 0
          • F
            fastcon68
            last edited by

            Currently have a total of 5 adapters.

            listed Here in order:
            onboard - non fuctional
            pci-x - broadcomm GB (conection to DSL modem)
            dual port intel - removed from configuration(was using for testing but decided to remove
            realtek - GB adapter connection LAN

            If I remove the pci-x adapter and leave the realtek adapter the pc only see's one adapter.

            pfsense is awesome.  I have been having no issue but would love to get the system down to minimum needed hardware.  Even concidering using the onboard power off and power on controls so that I can save on utilities.
            RC

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              you can upgrade to 6.3 with the upgrade file here.
              http://cvs.pfsense.org/~sullrich/testing_images/6/FreeBSD_RELENG_6_3/pfSense_RELENG_1_2/

              1 Reply Last reply Reply Quote 0
              • F
                fastcon68
                last edited by

                I just got 6.3 and the installed and up and running.  It looks good.  I now have a total of 5 possible interfaces.  I have 3 interfaces diasabled.  I am running on the two broadcom adapters.  They seem to be running great.

                Still running some tests.  Snort and DSPAM are not running correctly, still working on those issues.

                Over all it looks real good.
                RC

                1 Reply Last reply Reply Quote 0
                • F
                  fastcon68
                  last edited by

                  here is the dmesg from 6.3.
                  RC

                  $ dmesg
                  Copyright © 1992-2008 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 is a registered trademark of The FreeBSD Foundation.
                  FreeBSD 6.3-RELEASE-p1 #0: Wed Apr  9 23:49:10 EDT 2008
                      sullrich@freebsd6-esx.geekgod.com:/usr/obj.pfSense/usr/src/sys/pfSense_SMP.6
                  Timecounter "i8254" frequency 1193182 Hz quality 0
                  CPU: Intel(R) Pentium(R) D CPU 3.00GHz (2992.52-MHz 686-class CPU)
                    Origin = "GenuineIntel"  Id = 0xf65  Stepping = 5
                    Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0xe49d <sse3,rsvd2,mon,ds_cpl,est,cnxt-id,cx16,xtpr,pdcm>AMD Features=0x20100000 <nx,lm>AMD Features2=0x1 <lahf>Cores per package: 2
                  real memory  = 1072152576 (1022 MB)
                  avail memory = 1035771904 (987 MB)
                  ACPI APIC Table: <dell  b8k =""  ="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
                  cpu0 (BSP): APIC ID:  0
                  cpu1 (AP): APIC ID:  1
                  ioapic0: Changing APIC ID to 8
                  ioapic0 <version 2.0="">irqs 0-23 on motherboard
                  lapic0: Forcing LINT1 to edge trigger
                  wlan: mac acl policy registered
                  kbd1 at kbdmux0
                  ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
                  hptrr: HPT RocketRAID controller driver v1.1 (Apr  9 2008 23:48:48)
                  acpi0: <dell b8k =""  ="">on motherboard
                  acpi0: Power Button (fixed)
                  Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
                  acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
                  acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
                  Timecounter "HPET" frequency 14318180 Hz quality 900
                  cpu0: <acpi cpu="">on acpi0
                  cpu1: <acpi cpu="">on acpi0
                  acpi_button0: <power button="">on acpi0
                  pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
                  pci0: <acpi pci="" bus="">on pcib0
                  pcib1: <acpi pci-pci="" bridge="">irq 16 at device 1.0 on pci0
                  pci1: <acpi pci="" bus="">on pcib1
                  pcib2: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
                  pci2: <acpi pci="" bus="">on pcib2
                  pcib3: <acpi pci-pci="" bridge="">irq 16 at device 28.4 on pci0
                  pci3: <acpi pci="" bus="">on pcib3
                  bge0: <broadcom bcm5750="" c1,="" asic="" rev.="" 0x4201="">mem 0xefcf0000-0xefcfffff irq 16 at device 0.0 on pci3
                  miibus0: <mii bus="">on bge0
                  brgphy0: <bcm5750 10="" 100="" 1000basetx="" phy="">on miibus0
                  brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
                  bge0: Ethernet address: 00:10:18:2d:d8:3d
                  pcib4: <acpi pci-pci="" bridge="">irq 17 at device 28.5 on pci0
                  pci4: <acpi pci="" bus="">on pcib4
                  bge1: <broadcom 5787="" bcm5754="" a2,="" asic="" rev.="" 0xb002="">mem 0xefbf0000-0xefbfffff irq 17 at device 0.0 on pci4
                  miibus1: <mii bus="">on bge1
                  brgphy1: <bcm5787 10="" 100="" 1000basetx="" phy="">on miibus1
                  brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
                  bge1: Ethernet address: 00:1a:a0:24:fa:80
                  uhci0: <uhci (generic)="" usb="" controller="">port 0xff80-0xff9f irq 21 at device 29.0 on pci0
                  uhci0: [GIANT-LOCKED]
                  usb0: <uhci (generic)="" usb="" controller="">on uhci0
                  usb0: USB revision 1.0
                  uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
                  uhub0: 2 ports with 2 removable, self powered
                  uhci1: <uhci (generic)="" usb="" controller="">port 0xff60-0xff7f irq 22 at device 29.1 on pci0
                  uhci1: [GIANT-LOCKED]
                  usb1: <uhci (generic)="" usb="" controller="">on uhci1
                  usb1: USB revision 1.0
                  uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
                  uhub1: 2 ports with 2 removable, self powered
                  uhci2: <uhci (generic)="" usb="" controller="">port 0xff40-0xff5f irq 18 at device 29.2 on pci0
                  uhci2: [GIANT-LOCKED]
                  usb2: <uhci (generic)="" usb="" controller="">on uhci2
                  usb2: USB revision 1.0
                  uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
                  uhub2: 2 ports with 2 removable, self powered
                  uhci3: <uhci (generic)="" usb="" controller="">port 0xff20-0xff3f irq 23 at device 29.3 on pci0
                  uhci3: [GIANT-LOCKED]
                  usb3: <uhci (generic)="" usb="" controller="">on uhci3
                  usb3: USB revision 1.0
                  uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
                  uhub3: 2 ports with 2 removable, self powered
                  ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">mem 0xff980800-0xff980bff irq 21 at device 29.7 on pci0
                  ehci0: [GIANT-LOCKED]
                  usb4: waiting for BIOS to give up control
                  usb4: EHCI version 1.0
                  usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
                  usb4: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">on ehci0
                  usb4: USB revision 2.0
                  uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
                  uhub4: 8 ports with 8 removable, self powered
                  pcib5: <acpi pci-pci="" bridge="">at device 30.0 on pci0
                  pci5: <acpi pci="" bus="">on pcib5
                  pcib6: <pci-pci bridge="">at device 2.0 on pci5
                  pci6: <pci bus="">on pcib6
                  fxp0: <intel 100="" 82558="" pro="" ethernet="">port 0xccc0-0xccdf mem 0xe8001000-0xe8001fff,0xef600000-0xef6fffff irq 18 at device 4.0 on pci6
                  miibus2: <mii bus="">on fxp0
                  inphy0: <i82555 10="" 100="" media="" interface="">on miibus2
                  inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
                  fxp0: Ethernet address: 00:03:47:96:fd:20
                  fxp1: <intel 100="" 82558="" pro="" ethernet="">port 0xcce0-0xccff mem 0xe8000000-0xe8000fff,0xef700000-0xef7fffff irq 19 at device 5.0 on pci6
                  miibus3: <mii bus="">on fxp1
                  inphy1: <i82555 10="" 100="" media="" interface="">on miibus3
                  inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
                  fxp1: Ethernet address: 00:03:47:96:fd:21
                  re0: <realtek 8169s="" single-chip="" gigabit="" ethernet="">port 0xd800-0xd8ff mem 0xef9eff00-0xef9effff irq 16 at device 4.0 on pci5
                  miibus4: <mii bus="">on re0
                  rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface="">on miibus4
                  rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
                  re0: Ethernet address: 00:18:e7:15:f2:f1
                  re0: [FAST]
                  pci5: <display, vga="">at device 7.0 (no driver attached)
                  isab0: <pci-isa bridge="">at device 31.0 on pci0
                  isa0: <isa bus="">on isab0
                  atapci0: <intel ich7="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 16 at device 31.1 on pci0
                  ata0: <ata 0="" channel="">on atapci0
                  ata1: <ata 1="" channel="">on atapci0
                  atapci1: <intel ich7="" sata300="" controller="">port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf mem 0xeffffc00-0xefffffff irq 20 at device 31.2 on pci0
                  ata2: <ata 0="" channel="">on atapci1
                  ata3: <ata 1="" channel="">on atapci1
                  pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
                  speaker0: <pc speaker="">port 0x61 on acpi0
                  sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
                  sio0: type 16550A
                  pmtimer0 on isa0
                  orm0: <isa option="" roms="">at iomem 0xc0000-0xc8fff,0xc9000-0xcafff,0xcb000-0xcbfff on isa0
                  atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
                  atkbd0: <at keyboard="">irq 1 on atkbdc0
                  kbd0 at atkbd0
                  atkbd0: [GIANT-LOCKED]
                  ppc0: parallel port not found.
                  sc0: <system console="">at flags 0x100 on isa0
                  sc0: VGA <16 virtual consoles, flags=0x300>
                  sio1: configured irq 3 not in bitmap of probed irqs 0
                  sio1: port may not be enabled
                  vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
                  ukbd0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 2, iclass 3/1
                  kbd2 at ukbd0
                  Timecounters tick every 1.000 msec
                  Fast IPsec: Initialized Security Association Processing.
                  hptrr: no controller detected.
                  ad0: 38204MB <samsung sp0411n="" tw100-08="">at ata0-master UDMA100
                  acd0: CDROM <pbds cd-rom="" dh-48n1p="" ad11="">at ata0-slave UDMA33
                  lapic1: Forcing LINT1 to edge trigger
                  SMP: AP CPU #1 Launched!
                  Trying to mount root from ufs:/dev/ad0s1a
                  WARNING: / was not properly dismounted
                  WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck
                  WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck
                  bge0: link state changed to UP
                  bge1: link state changed to UP
                  fxp0: link state changed to DOWN
                  fxp1: link state changed to DOWN
                  re0: link state changed to DOWN
                  bge1: link state changed to DOWN
                  bge0: link state changed to DOWN
                  bge1: link state changed to UP
                  bge0: link state changed to UP
                  pflog0: promiscuous mode enabled
                  bge0: link state changed to DOWN
                  bge0: link state changed to UP
                  bge0: link state changed to DOWN
                  bge1: link state changed to DOWN
                  bge0: link state changed to UP
                  bge1: link state changed to UP
                  bge1: link state changed to DOWN
                  bge1: link state changed to UP
                  WARNING: pseudo-random number generator used for IPsec processing</pbds></samsung></generic></system></at></keyboard></isa></pc></serial></ata></ata></intel></ata></ata></intel></isa></pci-isa></display,></rtl8169s></mii></realtek></i82555></mii></intel></i82555></mii></intel></pci></pci-pci></acpi></acpi></intel></intel></uhci></uhci></uhci></uhci></uhci></uhci></uhci></uhci></bcm5787></mii></broadcom></acpi></acpi></bcm5750></mii></broadcom></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></power></acpi></acpi></high></dell></version></dell ></lahf></nx,lm></sse3,rsvd2,mon,ds_cpl,est,cnxt-id,cx16,xtpr,pdcm></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>

                  1 Reply Last reply Reply Quote 0
                  • W
                    wallabybob
                    last edited by

                    Pleased you have things working.

                    In the FreeBSD 6.2 dmseg output I was looking for something like the line

                    pci4: <network, ethernet="">at device 0.0 (no driver attached)</network,>

                    but unfortunately my eyes passed right over it yesterday and went straight to it today.  :( This line says there is a PCI ethernet controller that no driver in the kernel recognises as a device it can control. Now that you have run the FreeBSD 6.3 based version its clear this was the Broadcom 5754 which was not supported in FreeBSD 6.2.

                    1 Reply Last reply Reply Quote 0
                    • D
                      David_W
                      last edited by

                      This is all as expected. There was an attempt to support the BCM5754 in FreeBSD 6.2, but it was realised relatively late in the process that the support wasn't complete and it needed to be yanked. FreeBSD 6.2-RELEASE won't recognise a BCM5754 at all.

                      Later on, full support for the BCM5754 was committed - as can be seen in FreeBSD 6.3. It's good to know that you've got the controller going now.

                      1 Reply Last reply Reply Quote 0
                      • F
                        fastcon68
                        last edited by

                        Seems to finally be working.  The performance seems to be good.  One thing to note,  I had snort working but it stopped, under 6.2 release 1.2.  I ran for a couple of hours on 6.3 and now has stopped.  The snort release is 2.7.0.1_4.

                        Overall it seems to be a very stable release.
                        RC

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.