> There is als so a cards parameter in the drivers option : cards=0,1 will > bind the rt_e1000e module to the second interface
>> You can bind a device to or unbind from a driver using the SysFS "bind" >> and "unbind" files. e.g.: >> >> # echo "0000:04:00.0" > /sys/class/net/eth0/device/driver/unbind >> >> Then insmod "rt_e1000e.ko" and it will probe that device. Thank you guys, this definitely solved my problem! In a little more detail, this is what I did: I started up the machine with the e1000e module loaded, and ran: # tree /sys/class/net This lists the ethernet devices, with the corresponding bus id's. Then, I picked the bus id for eth0, and ran: # echo "<bus id> > /sys/class/net/eth0/device/driver/unbind" After this I could load the rt_e1000e module, and it nicely detected rteth0. Happy New Year! Wim -- Wim Meeussen CTO, hiDOF Inc. 650-529-4522 http://hidof.com ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
