nfe internet problems

Pyun YongHyeon pyunyh at gmail.com
Mon Nov 12 02:31:57 PST 2007


On Mon, Nov 12, 2007 at 06:54:53AM +0000, 韓家標 Bill Hacker wrote:
 > Pyun YongHyeon wrote:
 > >On Sun, Nov 11, 2007 at 09:38:59PM -0500, Chuck Robey wrote:
 > > > Pyun YongHyeon wrote:
 > 
 > *trimmed*
 > 
 > > > 
 > > > OK, I just finished getting a verbose boot.  Wouldn't you know it?  The 
 > > > nfe ports aren't even recognized now.  I have them static in the kernel 
 > > > (so they don't need kldloading) but I can offer you no probing info.  I 
 > > > can find the nfe by using kldstat -v, so it's in the kernel (and i 
 > > > checked, an attempt to load it anyhow fails).  I haven't any idea why 
 > > it > would not be probed, it's on the motherboard (an Asus Striker 
 > > Extreme) 
 > >If nfe(4) was loaded successfully and identified ethernet controller
 > >it should have printed some information for the device.(You can check 
 > >it before invoking ifconfig(8)). If it's not detected by nfe(4) I
 > >guess nfe(4) is not guilty for the issue.
 > >It would be even better if you can post the output of "pciconf -lcv".
 > >
 > > > and needs only to have the bios agree to allow it, which it was.  Hmm, 
 > > I > think I will reboot and check the bios again anyhow.  Won't hurt 
 > > > anything, I guess.
 > > > 
 > >
 > >Your BIOS may have a ASF option for ethernet. Try toggling the option.
 > >
 > 
 > Side issue, but perhaps related (BIOS?) - the Asus P5K with Alantec NIC 
 > doesn't load any driver in probes *either*, but at least reports somthing 
 > is there;
 > 
 > Extracts:
 > 
 > (an older 7-CURRENT from September ISO);
 > 
 > pcib4: <ACPI PCI-PCI bridge> irq 16 at device 28.5 on pci0
 > pci2: <ACPI PCI bus> on pcib4
 > pci2: <network, ethernet> at device 0.0 (no driver attached)
 > 
 > ..
 > 
 > (8-CURRENT form 17 OCtober)
 > 
 > pcib4: <ACPI PCI-PCI bridge> irq 16 at device 28.5 on pci0
 > pci2: <ACPI PCI bus> on pcib4
 > pci2: <network, ethernet> at device 0.0 (no driver attached)
 > 

Show me the "pciconf -lcv" output.

 > That the OP's scan has gone totally 'blind' to the nfe suggests it might be 
 > a good idea to physically reset the MB BIOS by jumper, then start over.
 > 
 > Gigabyte (often!), and Asus, (sometimes) get their BIOS knickers in a knot 
 > after many soft changes and go into unplanned states.
 > 
 > Bill

-- 
Regards,
Pyun YongHyeon


More information about the freebsd-current mailing list