From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 3 23:27:16 2005 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90CA616A41F for ; Thu, 3 Nov 2005 23:27:16 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out6.blueyonder.co.uk (smtp-out6.blueyonder.co.uk [195.188.213.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07FB643D45 for ; Thu, 3 Nov 2005 23:27:15 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.253.228] ([82.41.253.228]) by smtp-out6.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Thu, 3 Nov 2005 23:28:05 +0000 Message-ID: <436A9CD1.60409@dial.pipex.com> Date: Thu, 03 Nov 2005 23:27:13 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20051030 X-Accept-Language: en-us, pl MIME-Version: 1.0 To: Mikhail Teterin References: <200511020530.jA25UjWc002228@corbulon.video-collage.com> <4368CA46.40209@dial.pipex.com> <200511031519.54854.mi+mx@aldan.algebra.com> In-Reply-To: <200511031519.54854.mi+mx@aldan.algebra.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Nov 2005 23:28:05.0624 (UTC) FILETIME=[3DE52780:01C5E0CE] Cc: hardware@freebsd.org Subject: Re: skc0: unknown media type: 0x0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 23:27:16 -0000 Mikhail Teterin wrote: >>What do you have in /etc/rc.conf especially regarding ifconfig_sk0? A >>bad change there could easily results in the problem not showing up >>until a reboot. >> >> > >The interface-detection fails during boot -- long before anything in rc.conf >comes into play. It used to say: > > sk0: on skc0 > >It now says: > > skc0: unknown media type: 0x0 > > From the source code, the driver is trying to read the media type setting from the eeprom and failing to get anything it understands. This looks like only the second bit of info that is looked at from the eeprom, and the first bit wouldn't give an error if it too was returning 0x0. This is just my quick reading of the code, though! I would definitely be starting to think that adding the memory triggered a hardware problem, perhaps static, or something physical. Presumably you don't have another OS installed on the machine ( Windows or Linux) because if it too couldn't see the ethernet that would be a strong indicator of hardware problems. --Alex