Date: Wed, 5 Sep 2012 08:53:46 +0200 From: Brian Stivala <brianstivala@gmail.com> To: Matthew Seaman <matthew@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: FreeBsd modules Message-ID: <CAL8FXqyqJk2RE4M4K8wmyae7LC2ztpxFqepXjT7MjL3znfRczQ@mail.gmail.com> In-Reply-To: <5046640E.10806@FreeBSD.org> References: <CAL8FXqxh7M0CXrsRy-kKkCFTgf70wWjp1Mq3UXtVmg3aFmDfZA@mail.gmail.com> <5046640E.10806@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Matthew,
Thanks for your reply,
This is my Pciconf and the /var/log/dmesg.boot. As you can see the ethernet
card is there but it is not recognisable in PFSense. The only functional
nics are FXP0 and FXP1 the onboard chipset.
[2.0.1-RELEASE][root@pfSense.localdomain]/root(1): pciconf -l -v
hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x00000000 chip=3D0x7192808=
6
rev=3D0x03 hdr=3D0x00
class =3D bridge
subclass =3D HOST-PCI
fxp0@pci0:0:5:0: class=3D0x020000 card=3D0x00000000 chip=3D0x1209808=
6
rev=3D0x09 hdr=3D0x00
class =3D network
subclass =3D ethernet
fxp1@pci0:0:6:0: class=3D0x020000 card=3D0x00000000 chip=3D0x1209808=
6
rev=3D0x09 hdr=3D0x00
class =3D network
subclass =3D ethernet
isab0@pci0:0:7:0: class=3D0x060100 card=3D0x00000000 chip=3D0x7110808=
6
rev=3D0x02 hdr=3D0x00
class =3D bridge
subclass =3D PCI-ISA
atapci0@pci0:0:7:1: class=3D0x010180 card=3D0x00000000 chip=3D0x7111808=
6
rev=3D0x01 hdr=3D0x00
class =3D mass storage
subclass =3D ATA
uhci0@pci0:0:7:2: class=3D0x0c0300 card=3D0x00000000 chip=3D0x7112808=
6
rev=3D0x01 hdr=3D0x00
class =3D serial bus
subclass =3D USB
piix0@pci0:0:7:3: class=3D0x068000 card=3D0x00000000 chip=3D0x7113808=
6
rev=3D0x02 hdr=3D0x00
class =3D bridge
none0@pci0:0:8:0: class=3D0x0b4000 card=3D0x00000000 chip=3D0x000613a=
3
rev=3D0x01 hdr=3D0x00
class =3D processor
none1@pci0:0:9:0: class=3D0x020000 card=3D0x00000000 chip=3D0x0201161=
7
rev=3D0x00 hdr=3D0x00
class =3D network
subclass =3D ethernet
[2.0.1-RELEASE][root@pfSense.localdomain]/root/var(5): cat
/var/log/dmesg.boot
Copyright (c) 1992-2010 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 8.1-RELEASE-p6 #0: Mon Dec 12 18:59:41 EST 2011
root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc=
/src/sys/pfSense_wrap.8.i386
i386
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Pentium III (847.74-MHz 686-class CPU)
Origin =3D "GenuineIntel" Id =3D 0x68a Family =3D 6 Model =3D 8 Stepp=
ing =3D 10
Features=3D0x387f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CM=
OV,PAT,PSE36,PN,MMX,FXSR,SSE>
real memory =3D 268435456 (256 MB)
avail memory =3D 243433472 (232 MB)
netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device pollin=
g
wlan: mac acl policy registered
ipw_bss: You need to read the LICENSE file in
/usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=3D1
in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0710010, 0) error 1
ipw_ibss: You need to read the LICENSE file in
/usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=3D=
1
in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc07100b0, 0) error 1
wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
wpi: If you agree with the license, set legal.intel_wpi.license_ack=3D1 in
/boot/loader.conf.
module_register_init: MOD_LOAD (wpi_fw, 0xc0883050, 0) error 1
ipw_monitor: You need to read the LICENSE file in
/usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set
legal.intel_ipw.license_ack=3D1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc0710150, 0) error 1
ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309)
ACPI: Table initialisation failed: AE_NOT_FOUND
ACPI: Try disabling either ACPI or apic support.
cryptosoft0: <software crypto> on motherboard
padlock0: No ACE support.
pcib0: <Intel 82443BX host to PCI bridge (AGP disabled)> pcibus 0 on
motherboard
pci0: <PCI bus> on pcib0
fxp0: <Intel 82559ER Embedded 10/100 Ethernet> port 0xfc00-0xfc3f mem
0xc0000000-0xc0000fff,0xc0020000-0xc003ffff irq 9 at device 5.0 on pci0
fxp0: Enabling Rx lock-up workaround
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> PHY 1 on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: [ITHREAD]
fxp1: <Intel 82559ER Embedded 10/100 Ethernet> port 0xf800-0xf83f mem
0xc0040000-0xc0040fff,0xc0060000-0xc007ffff irq 6 at device 6.0 on pci0
fxp1: Enabling Rx lock-up workaround
miibus1: <MII bus> on fxp1
inphy1: <i82555 10/100 media interface> PHY 1 on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: [ITHREAD]
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf400-0xf40f at device 7.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xf000-0xf01f irq 11
at device 7.2 on pci0
uhci0: [ITHREAD]
usbus0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
piix0: <PIIX Timecounter> port 0x10a0-0x10af at device 7.3 on pci0
Timecounter "PIIX" frequency 3579545 Hz quality 0
pci0: <processor> at device 8.0 (no driver attached)
pci0: <network, ethernet> at device 9.0 (no driver attached)
cpu0 on motherboard
atrtc0: <AT Real Time Clock> at port 0x70 irq 8 on isa0
uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
uart0: [FILTER]
uart0: console (9600,n,8,1)
uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
uart1: [FILTER]
RTC BIOS diagnostic error 42<ROM_cksum>
Timecounter "TSC" frequency 847739306 Hz quality 800
Timecounters tick every 10.000 msec
IPsec: Initialized Security Association Processing.
usbus0: 12Mbps Full Speed USB v1.0
ad0: 1967MB <CF Card Ver1.27> at ata0-master PIO4
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
Root mount waiting for: usbus0
uhub0: 2 ports with 2 removable, self powered
Trying to mount root from ufs:/dev/ufs/pfsense0
Invalid time in real time clock.
Check and reset the date immediately!
Regards,
Brian Stivala
On Tue, Sep 4, 2012 at 10:26 PM, Matthew Seaman <matthew@freebsd.org> wrote=
:
> On 04/09/2012 19:33, Brian Stivala wrote:
> > I have a watchguard firewall v80 which I=92ve decided to amend it to
> PFSense
> > based on freebsd. So far I=92ve installed PFSense and everything is wor=
king
> > accordingly. This firewall has 2x onboard nic cards and a PCI quad nic,
> as
> > per attached photo.
>
> Unfortunately the list management software ate your photo, but never
> mind. Your verbal description is sufficient.
>
> > The onboard nics can be recognized however the PCI card is not being
> > recognised, and the strange thing is that both onboard and the PCI uses
> the
> > same chipset Intel 82559er Ethernet. How can I amend changes in freebsd
> > modules so that the PCI card can be recognised.
>
> There may be a good reason for your quad card not being recognised, or
> it might just be a bug.
>
> If you run:
>
> % pciconf -lv
>
> You should be able to pick out your unrecognised device. If you ask
> again on freebsd-net@freebsd.org and include relevant sections from
> the pciconf output, you should get to the attention of some of the guys
> that write network drivers.
>
> > Usually in other distros modules can be located in /etc/module however =
I
> > cannot find where the modules are located in freebsd.
>
> Verb Sap. Calling FreeBSD a 'distro' is definitely non-U. We generally
> consider penguins a bit fishy round here...
>
> If you want to locate the kernel modules for various hardware, look in
> /boot/kernel. NIC modules will generally have a name beginning 'if_'.
>
> If you want to see what modules have been loaded into the kernel, then
> run:
>
> % kldstat
>
> There's also 'kldload' and 'kldunload' but they aren't going to help you
> for this problem. PCI devices are discovered when the kernel probes the
> bus at boot time: if the kernel hasn't already assigned a driver for the
> device, then there isn't one available.
>
> > Can I have some assistance.
>
> Keeps asking good questions and you'll get useful answers.
>
> Cheers,
>
> Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil.
> PGP: http://www.infracaninophile.co.uk/pgpkey
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAL8FXqyqJk2RE4M4K8wmyae7LC2ztpxFqepXjT7MjL3znfRczQ>