From owner-freebsd-questions Tue Mar 25 6: 0:45 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C0DB37B401 for ; Tue, 25 Mar 2003 06:00:42 -0800 (PST) Received: from vega.blacktrap.net (vega.blacktrap.net [194.9.222.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6718C43F93 for ; Tue, 25 Mar 2003 06:00:41 -0800 (PST) (envelope-from oli@vega.blacktrap.net) Received: from vega.blacktrap.net (localhost [127.0.0.1]) by vega.blacktrap.net (8.12.6/8.12.6) with ESMTP id h2PE1DDG008356 for ; Tue, 25 Mar 2003 15:01:13 +0100 (CET) (envelope-from oli@vega.blacktrap.net) Received: (from oli@localhost) by vega.blacktrap.net (8.12.6/8.12.6/Submit) id h2PE1DYH008355 for questions@FreeBSD.ORG; Tue, 25 Mar 2003 15:01:13 +0100 (CET) Date: Tue, 25 Mar 2003 15:01:13 +0100 From: Olivier Dony To: FreeBSD-questions Subject: rl(4): autoselect/manual media == no carrier at boot time? Message-ID: <20030325140113.GA7586@vega.blacktrap.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Spam-Status: No, hits=-6.4 required=5.0 tests=USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, that's me again :) rl0: port 0xec00-0xecff mem 0xdfffff00-0xdfffffff irq 10 at device 5.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode ^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ This is my detected NIC. It has always been detecting 100baseTX half-duplex, when I am actually plugged into a cool 100Mbps switch. So after a couple of tests, I decided that full-duplex was going fine and appended "media 100baseTX mediaopt full-duplex" to the ifconfig_rl0 line in my rc.conf, just in case. The card was actually working fine in this mode. Also given that rl(4) isn't so happy with autoselect mode if the proper PHY chip is not present (or something), I thought this would be a good thing. Now it happened that the server rebooted after a kernel panic (this is 5.0, I will be taking *this* subject to -current), but the problem here is that rl(4) detected no carrier : kernel: rl0: flags=8843 mtu 1500 kernel: inet 666.666.222.35 netmask 0xffffff00 broadcast 666.666.222.255 kernel: ether 00:50:fc:97:41:b4 kernel: media: Ethernet 100baseTX kernel: status: no carrier My ISP says that they have not touched the UTP cable. After they rebooted the server again while trying to find why it was down, the same "no carrier" appears in the dmesg, so after a normal boot too. They claim that after this second reboot they unplugged and then plugged back the UTP connection and the NIC's led came to life and the network was up again (and still is, full-duplex). My question is, is it possible that setting the media to 100baseTX could cause problems for carrier detection at boot time? Or is my ISP lying and they unplugged the network just right during the kernel panic and only plugged it back after a while? This doesn't sound likely... I do not feel like rebooting again right now just to see if using autoselect works, I'd rather not have to call them today to fix it once more ;-) Thanks in advance Olivier, always learning more thanks to you! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message