
<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://wiki.sabayonlinux.org/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Finding_right_network_kernel_driver&amp;feed=atom&amp;action=history</id>
		<title>En:HOWTO: Finding right network kernel driver - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Finding_right_network_kernel_driver&amp;feed=atom&amp;action=history"/>
		<link rel="alternate" type="text/html" href="http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Finding_right_network_kernel_driver&amp;action=history"/>
		<updated>2013-05-26T08:54:51Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.19.4</generator>

	<entry>
		<id>http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Finding_right_network_kernel_driver&amp;diff=6301&amp;oldid=prev</id>
		<title>Zambayoni at 19:19, 26 February 2009</title>
		<link rel="alternate" type="text/html" href="http://wiki.sabayonlinux.org/index.php?title=En:HOWTO:_Finding_right_network_kernel_driver&amp;diff=6301&amp;oldid=prev"/>
				<updated>2009-02-26T19:19:24Z</updated>
		
		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{i18n|[[Ca:HOWTO: Finding right network kernel driver|ca]] [[En:HOWTO: Finding right network kernel driver|en]]}}&lt;br /&gt;
&lt;br /&gt;
To find out which modules you must use.. &lt;br /&gt;
the most simple thing to do is cat log file and grep for eth entry's .. &lt;br /&gt;
This will work if your Sabayon linux have already recognized your ethernet card (most cases).&lt;br /&gt;
In this example we look for eth0 and eth1 entry's, so if you have more cards just put at the end&lt;br /&gt;
eth[0,1,2,3,n] n = last ethernet card.&lt;br /&gt;
&lt;br /&gt;
'''cat /var/log/messages|grep eth[0,1]\:'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
&amp;lt;font size=&amp;quot;1&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;br /&amp;gt;Jul 22 07:46:44 mazinga [4294688.198000] e100: eth0: e100_probe: addr 0xd4000000, irq 19, MAC addr 00:06:29:E9:77:40  &amp;lt;br /&amp;gt;Jul 22 07:46:44 mazinga [4294688.213000] eth1: VIA Rhine II at 0x17800,00:11:2f:09:fc:1f, IRQ 20.   &amp;lt;br /&amp;gt;Jul 22 07:46:44 mazinga [4294688.214000] eth1: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1.   &amp;lt;br /&amp;gt;Jul 22 07:46:59 mazinga [4294756.820000] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex&amp;lt;/font&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
from the lines above we can see that wi need to use e100 and VIA Rhine (which uses via_rhine)&amp;lt;br&amp;gt;&lt;br /&gt;
to view all the modules your kernel support do: &lt;br /&gt;
&lt;br /&gt;
'''ls /lib/modules/`uname -r`/kernel/drivers/net'''&lt;br /&gt;
&lt;br /&gt;
and for detailed information about a module (for via_rhine in this case)&lt;br /&gt;
&lt;br /&gt;
'''modinfo via_rhine'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
  &amp;lt;br /&amp;gt;&amp;lt;font size=&amp;quot;1&amp;quot;&amp;gt; filename:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;/lib/modules/2.6.16-reiser4-r3conan/kernel/drivers/net/via-rhine.ko   &amp;lt;br /&amp;gt; author:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;Donald Becker &amp;amp;lt;becker@scyld.com&amp;amp;gt;   &amp;lt;br /&amp;gt; description:&amp;amp;nbsp; &amp;amp;nbsp; VIA Rhine PCI Fast Ethernet driver   &amp;lt;br /&amp;gt; license:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; GPL   &amp;lt;br /&amp;gt; vermagic:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;2.6.16-reiser4-r3conan preempt K7 REGPARM gcc-4.1   &amp;lt;br /&amp;gt; depends:   &amp;lt;br /&amp;gt; alias:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; pci:v00001106d00003043sv*sd*bc*sc*i*   &amp;lt;br /&amp;gt; alias:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; pci:v00001106d00003065sv*sd*bc*sc*i*   &amp;lt;br /&amp;gt; alias:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; pci:v00001106d00003106sv*sd*bc*sc*i*   &amp;lt;br /&amp;gt; alias:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; pci:v00001106d00003053sv*sd*bc*sc*i*   &amp;lt;br /&amp;gt; parm:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;rx_copybreak:VIA Rhine copy breakpoint for copy-only-tiny-frames (int)   &amp;lt;br /&amp;gt; parm:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;debug:VIA Rhine debug level (0-7) (int)   &amp;lt;br /&amp;gt; parm:&amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;max_interrupt_work:VIA Rhine maximum events handled per interrupt (int) &amp;lt;/font&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
in case you don't have running modules in your distro then you could try&lt;br /&gt;
&lt;br /&gt;
'''lspci | grep Ethernet'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
&amp;lt;font size=&amp;quot;2&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;br /&amp;gt; 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78 )   &amp;lt;br /&amp;gt; 00:13.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08 ) &amp;lt;/font&amp;gt; &lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And google for modules which support your card &lt;br /&gt;
&lt;br /&gt;
If you do have multiple ethernet cards, good practice is to put aliases into&lt;br /&gt;
&amp;lt;strong&amp;gt;/etc/modules.d/aliases&amp;lt;/strong&amp;gt; ,so in this particular case it would look like&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;font size=&amp;quot;1&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;br /&amp;gt; alias eth0 e100  &amp;lt;br /&amp;gt; alias eth1 via_rhine&amp;lt;/font&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
This will prevent swapping eth0 and eth1 which occur because of some bugs in coldplug/udev, as&lt;br /&gt;
the first driver which get loaded becomes eth0, and we don't want that. We need to know exactly&lt;br /&gt;
which card is eth0 and eth1 to configure our network.&lt;br /&gt;
&lt;br /&gt;
[[Category:Networking|Finding right network kernel driverEn]]&lt;/div&gt;</summary>
		<author><name>Zambayoni</name></author>	</entry>

	</feed>