From owner-freebsd-net@FreeBSD.ORG Fri Sep 5 14:44:54 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 303BD1065675 for ; Fri, 5 Sep 2008 14:44:54 +0000 (UTC) (envelope-from freebsd-net@dino.sk) Received: from loki.netlab.sk (loki.netlab.sk [84.245.65.11]) by mx1.freebsd.org (Postfix) with ESMTP id B868D8FC18 for ; Fri, 5 Sep 2008 14:44:53 +0000 (UTC) (envelope-from freebsd-net@dino.sk) Received: from via.dino.sk (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by loki.netlab.sk with esmtp; Fri, 05 Sep 2008 16:43:24 +0200 id 0002E010.48C1458C.0000F8C7 From: Milan Obuch To: pyunyh@gmail.com, freebsd-net@freebsd.org Date: Fri, 5 Sep 2008 16:43:51 +0200 User-Agent: KMail/1.9.7 References: <200809050945.09276.freebsd-net@dino.sk> <20080905082322.GA66951@cdnetworks.co.kr> In-Reply-To: <20080905082322.GA66951@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809051643.52950.freebsd-net@dino.sk> Cc: Subject: Re: MSI Wind Notebook's network interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2008 14:44:54 -0000 On Friday 05 September 2008 10:23:22 Pyun YongHyeon wrote: > On Fri, Sep 05, 2008 at 09:45:08AM +0200, Milan Obuch wrote: [ snip ] > > In 7.0-RELEASE wired network interface did not work, but after upgrading > > to 7-STABLE (now 7.1-PRERELEASE) it work with re driver. There is just > > one small uglyness - it's link level address (MAC) is 00:00:00:00:00:00. > > Needless to say, Windows initializes this to 00:1d:92:59:f5:8b. I can > > change it with 'ifconfig re0 ether 00:1d:92:59:f5:8b', but I would > > rather let the driver to find the correct MAC. [ snip ] > > dmesg (part of verbose boot) > > re0: port 0xc000-0xc0ff > > mem 0xffd10000-0xffd10fff,0xffd00000-0xffd0ffff irq 16 at device 0.0 on > > pci1 re0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0xffd10000 > > re0: MSI count : 1 > > re0: Chip rev. 0x34800000 > > re0: MAC rev. 0x00200000 > > miibus0: on re0 > > rlphy0: PHY 1 on miibus0 > > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > re0: bpf attached > > re0: [MPSAFE] > > re0: [FILTER] > > > > When not booting verbose, there is also one line telling > > re0: turning off MSI enable bit. > > re(4) cleared MSI enable bit of configuration register as MSI > wouldn't be used. You can ignore this. > OK, but what surprised me a bit was the fact this line is not present in dmesg when booting verbose. I would expect all lines from normal boot in verbose boot... > > This netbook has also wireless interface, but this one does not get > > detected (or I have no driver for it), in dmesg there is only line > > telling pci2: at device 0.0 (no driver attached) > > > > and relevant part of pciconf -lcv is > > none0@pci0:2:0:0: class=0x028000 card=0x68941462 chip=0x819910ec > > rev=0x22 hdr=0x00 > > vendor = 'Realtek Semiconductor' > > class = network > > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 > > cap 05[50] = MSI supports 1 message, 64 bit > > cap 10[70] = PCI-Express 1 legacy endpoint > > > > While currently I have no urge need for wireless connectivity, in the > > long run I would like to use it. Currently I can't change card (probably > > minipci) as netbook is under warranty, with 'warranty sticker - void if > > tampered' over screw. > > > > If anybody had some idea how to fix MAC address initialization for wired > > Would you try attached patch? > I tried on freshly csup'ped head and it works. Ethernet link address is now correctly set. Great! It looks like a kind of magic at first glance :) > > interface or what driver to use for wireless interface (I will probably > > try NDIS, but my experience in this area is limited and previous > > succesfull try none), I am all ears. Could anybody comment on wireless interface? Regards, Milan