Request if_cas.ko
-
Hello All,
Just curious if the if_cas.ko module will be added to the current builds of pfSense?
I run into the same problem as this poster.http://forum.pfsense.org/index.php/topic,33960.0.html
Our school purchased 4 of the Saturn Gigabit Ethernet DP83065 to be used in two new builds of pfSense-2.0.1 and each of the two servers stalls at installation with 'phy probe failed:6".
I tried the workaround that the poster said did in fact work for his install,but these two machines simply will not go past the phy probe failed" line.
I did try booting these same two machines with 3 versions of KnoppixLive centOS 5 and CentOS 6 and the cards are recognized and works as expected,,so it is not that the mobo is having IRQ problems,or such.I did download even the pfSense-2.1-DEVEL and try to install it,,with the same results as pfSense-2.0.1.
I was to the understanding that these cards would work,,in the latetest snapshots 0f 2.0.1?At this point we will have to get two Intel quad nics to get these up and going.
Thank You,
Barry -
Just curious if the if_cas.ko module will be added to the current builds of pfSense?
I run into the same problem as this poster.http://forum.pfsense.org/index.php/topic,33960.0.html
The linked post suggests the cas driver is now routinely built into the kernel.
Our school purchased 4 of the Saturn Gigabit Ethernet DP83065 to be used in two new builds of pfSense-2.0.1 and each of the two servers stalls at installation with 'phy probe failed:6".
If it is the cas driver reporting phy probe failed:6 then the driver must be built into the kernel. Please post some more context, say at least six line before this report or (probably even better) a screen shot after the stall?
On the evidence presented here I suspect there are two problems:
-
the cas driver can't find a phy for a least one of the NICs it recognises
-
the driver doesn't correctly handle the missing phy situation
-
-
wallabybob,
Thank You for the info. Same as you,I am thinking at this point thte only salvation for this nic's driver is to have it compiled into kernel. The adding the module in the loader.conf surely is NOT doing the trick.
Also, this module,,,if_cas.ko is NOT in the pfSense-2.0.1 iso. I had to manually copy the if_cas.ko from an FreeBSD 8.1 install CD and add to my pfSense-2.0.1 machine then add the ' if_cas_load="YES" line to the /boot loader.conf.As stated in the initial post the if_cas.ko module is NOT in the pfSense-2.1-devel snapshots either?
In regards to lines to post on the bootup process, the only line before the 'phy probe failed: 6 ", is
cas0: NS DP83065 Saturn Gigabit Ethernet
There are no lines after the 'phy probe failed: 6'
At this point the installation goes no further.Thank You,
Barry -
It's worth noting that the cas(4) driver does not claim specifically to support this card.
It supports the 501-6522 which is similar but PCI.
The 501-6378, which I believe you have, is PCI-X.Steve
-
Thank You for the info. Same as you,I am thinking at this point thte only salvation for this nic's driver is to have it compiled into kernel. The adding the module in the loader.conf surely is NOT doing the trick.
It is unlikely that building the driver into the kernel will fix eiher of the problems you reported.
Also, this module,,,if_cas.ko is NOT in the pfSense-2.0.1 iso. I had to manually copy the if_cas.ko from an FreeBSD 8.1 install CD and add to my pfSense-2.0.1 machine then add the ' if_cas_load="YES" line to the /boot loader.conf.
As stated in the initial post the if_cas.ko module is NOT in the pfSense-2.1-devel snapshots either?
Can you try a pfSense-2.1-devel snapshot with the appropriate cas driver from a FreeBSD 8.3 install? It is getting on for two years since FreeBSD 8.1 was released and there have been some cas driver changes related to phys since then.
-
Hello, and thanks for the feedback
here is a short out take from the driver module code:
driver provides support for the Sun Cassini/Cassini+ and National
Semiconductor DP83065 Saturn Gigabit Ethernet controllers found
on-board in Sun UltraSPARC machines and as add-on cards.,,, I have the NS DP83065 , which is the PCI-X model card and appears to be supported by the if_cas.ko.
here is a post by someone else that had a similar problem,with a slightly different twist.
http://forums.freebsd.org/showthread.php?t=24441
Tomorrow when i get to work I will try and get pfSense-2.1-devel re-installed and add in the if_cas.ko module from an 8.3 FreeBSD install cd and report back.
Thank You,
Barry -
Wanted to report for completeness.
Doing an full install of FreeBSD-8.3 the NS DP83065 card is simply detected as 'unknown usXX ethernet'.
System boots up fine.I added the following line to the /boot/loader.conf file
if_cas_load="YES"the NS DP83065 is now ID'd correctly on bootup but ,,,
After which on boot the bootup stops at
'NS DP83065 Saturn Gigabit Ethernet'
'attaching PHYs failed'The bootup process goes no further.
At this point we will have to get a couple Intel 4 port nics it appears.
Thank You,
Barry -
What are the PHYs used on that card?
It's unlikely but it may just be a matter of adding the device IDs to the driver.Steve
-
stephenw10,
how do i determine what the PHYs is of a given card?
I have never run into this scenario I guess?
remember the system will not boot with the card installed…( with the if_cas_load="YES" line in loader.conf
if i take the card out the system boots up as expected.
if I take the line I added to loader.conf,out and boot with card installed. i believe the card information in dmesg will be non-informational?
Were do I add the device ID if I can figure that out?I have found in the past when having to manually add devices there are usually underlying background problems related.
I am game to give this a shot though.
Kind of the chicken or the egg scenario,,:)Thanks again,
Barry -
Well I would start by simply looking at the card. Often there will be a 'one chip solution' on ethernet cards in which there is only one IC with all the components necessary. However that's not always the case especially with more expensive cards.
Here is an example log output from a supported cas(4) card:cas0: <ns dp83065="" saturn="" gigabit="" ethernet="">mem 0x200000-0x3fffff at device 3.0 on pci0 miibus0: <mii bus="">on cas0 nsgphy0: <dp83865 10="" 100="" 1000="" media="" interface="">PHY 1 on miibus0 nsgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow cas0: 16kB RX FIFO, 9kB TX FIFO cas0: Ethernet address: 00:14:4f:26:46:bd cas0: [FILTER]</dp83865></mii></ns>You can see it uses a DP83865 PHY. A separate physical IC. PDF.
Steve
Edit: You should also be able to determine the PHY in use from the Knoppix boot log.
Edit: I see from the user manual that the card uses a combined MAC/PHY so you probably won't be able to tell just by looking at it.
-
Steve,
The card you have listed in your example is the exact pci-x card I have.
Is that output from an pfSense-2.0.1 install?
If so,,then the card I have "should" work?
I never see any lines in regards to the miibus as yours is showing. I have been wondering if this may be part of the card probe failing on my machine?
The only mobo settings that can be changed are the clock frequency on the pci-x slot. I did change this to every possible setting with no changes in results.Thank You,
Barry -
The card you have listed in your example is the exact pci-x card I have.
How can you tell that?
That boot log extract is from FreeBSD 8.2 booting on a Sun Fire V490.
You can see in the log that cas0 is on pci0, a standard 33MHz PCI bus.I suggest booting from your knoppix CD and copy/pasting the boot log.
The cas(4) driver is still active, have you tried one of the new build snapshots based on FreebSD 8.3?
http://forum.pfsense.org/index.php/topic,46459.0.htmlSteve
