MSI Wind Notebook's network interfaces

Pyun YongHyeon pyunyh at gmail.com
Sat Sep 6 00:46:40 UTC 2008


On Fri, Sep 05, 2008 at 04:43:51PM +0200, Milan Obuch wrote:
 > 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: <RealTek 8101E/8102E/8102EL PCIe 10/100baseTX> 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: <MII bus> on re0
 > >  > rlphy0: <RTL8201L 10/100 media interface> 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...
 > 

That MSI information is stored in EEPROM. So you wouldn't see the
message again if MSI enable bit was already cleard. Since re(4)
clears the bit subsequent booting wouldn't touch the MSI enable bit
in EEPROM.

 > >  > 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: <network> at device 0.0 (no driver attached)
 > >  >
 > >  > and relevant part of pciconf -lcv is
 > >  > none0 at 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 :)
 > 

I've commited the patch to HEAD(r182808).

Thanks for your testing!
-- 
Regards,
Pyun YongHyeon


More information about the freebsd-net mailing list