Pyun YongHyeon wrote: > 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. > OK, like I said to begin with (look above) the nfe0/1 didn't probe. I've done more investigation, and believe it or not, the nfe0/1 doesn't print any probe message when I was in verbose booting mode. I rebooted 4 times, and did check the BIOS, the ports were definitely active. What's more puzzling is that, when I gave up trying to get a verbose boot with the nfe0/1 in there, and booted non-verbosely, it probed immediately, and here's what printed (I have excerpted the nfe section): nfe0: <NVIDIA nForce MCP55 Networking Adapter> port 0xfb00-0xfb07 mem 0xefffd000-0xefffdfff,0xefffc000-0xefffc0ff,0xefff b000-0xefffb00f irq 20 at device 17.0 on pci0 miibus1: <MII bus> on nfe0 e1000phy0: <Marvell 88E1116 Gigabit PHY> PHY 19 on miibus1 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: Ethernet address: 00:1b:fc:a0:90:4c nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe1: <NVIDIA nForce MCP55 Networking Adapter> port 0xfa00-0xfa07 mem 0xefffa000-0xefffafff,0xefff9000-0xefff90ff,0xefff 8000-0xefff800f irq 21 at device 18.0 on pci0 miibus2: <MII bus> on nfe1 e1000phy1: <Marvell 88E1116 Gigabit PHY> PHY 19 on miibus2 e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe1: Ethernet address: 00:1b:fc:a0:97:89 nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] nfe1: [FILTER] pciconf -l -cv yielded: nfe0_at_pci0:0:17:0: class=0x068000 card=0xcb841043 chip=0x037310de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 Ethernet' class = bridge cap 01[44] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 11[70] = MSI-X supports 8 messages in maps 0x18 and 0x1c enabled cap 05[50] = MSI supports 8 messages, 64 bit, vector masks cap 08[6c] = HT MSI fixed address window enabled at 0xfee00000 nfe1_at_pci0:0:18:0: class=0x068000 card=0xcb841043 chip=0x037310de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'MCP55 Ethernet' class = bridge cap 01[44] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 11[70] = MSI-X supports 8 messages in maps 0x18 and 0x1c enabled cap 05[50] = MSI supports 8 messages, 64 bit, vector masks cap 08[6c] = HT MSI fixed address window enabled at 0xfee00000 I have one other odd problem, it's that no probe messages whatever print during booting, so I had to pick up the demsg later on. The last thing I see during booting is the first spinner character, usually "|", and the next thing I see is "Login;", nothing inbetween whatever. Any idea why my booting has gone totally silent on me?Received on Mon Nov 12 2007 - 19:33:02 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:22 UTC