Community Forum

0 votes
Hello world !

First, I want to introduce myself on this forum. This is my first post. I already enjoy this fantastic community and this forum, I found a lot of good thing about Clear OS.

I'm 22. I'm in the marvelous world of IT since I can read. I'm doing this as professional since 3 years. I dont know everything but I'm a good learner. :side:

I'm using linux since early years of college. The first installation I done is with debian and a netvista 400. It took me about 1 week only for having my sound card functionnal. Well, this is a short story about me....I also appreciate video game on pc. I'm playing a lot Battlefield :BC 2 now.

I have a little question about hardware support on COS 5.2 sp1. I have a brand new LENOVO Thinkcenter M81 . (Type 7518b1f) . The computer is a compact and silent workstation, who is perfect as a cheap and reliable gateway.

I need to use it as a router with 2 wan and 1 lan interface. I already have one in my office, with only one wan interface. I just put 2 DFE-538TX to make it work.

The problem is that the onboard network card is not working.....and I only have 2 PCI port and one pci-e port. The hardware report told me : Ethernet controller: Intel Corporation Unknown device 1502.

The chipset is .

So, I guess I need to install the right driver to make it work.......But I dont know how. I guess again that I need to tell my system where to take the file and I need to install it with the console.

Is there anyone who can introduce me to «COS way» to install driver?

Thank you very much !

(English is not my main language, be cool please.... :lol: )
Tuesday, August 09 2011, 08:19 PM
Share this post:
Responses (16)
  • Accepted Answer

    Wednesday, September 21 2011, 03:27 PM - #Permalink
    0 votes
    Once again - big thanks to Tim for maintaining that repo - saved me a bunch of time this AM! I owe you some beers when I see you Tim....

    00:19.0 Ethernet controller: Intel Corporation Unknown device 1502 (rev 05)
    03:00.0 Ethernet controller: Intel Corporation Unknown device 1526 (rev 01)
    03:00.1 Ethernet controller: Intel Corporation Unknown device 1526 (rev 01)
    05:00.0 Ethernet controller: Intel Corporation Unknown device 1526 (rev 01)
    05:00.1 Ethernet controller: Intel Corporation Unknown device 1526 (rev 01)
    08:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

    The reply is currently minimized Show
  • Accepted Answer

    Thursday, August 11 2011, 08:36 PM - #Permalink
    0 votes
    I have not changed anything, at first I installed two DFE-538TX. In the first system startup, the first thing I saw is that eth0 and eth1 who is respectively the 2 d-link (via-rhine). Later, I asked why I did not see 3 interface and that's where I post on this forum. I cloned the file from the ETH1 to produce a configuration file for eth2, which is actually the e1000e. You told me to name it eth0, but I ignored this detail because it is currently the eth0 interface of the via-rhine (d-link) and is fully functional.

    Indeed, I can redo the configuration with the other mac address like you suggest. I'll keep you in touch, i'm working late tonight, I'll be back tomorrow.

    Thank you very much Nick !!!!!!!!
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, August 11 2011, 06:39 PM - #Permalink
    0 votes
    I don't know what you've done but you've switched your e1000e adaptor from eth0 to eth2. Can you check if you have an /etc/sysconfig/network-scripts/ifcfg-eth2? If you don't, please clone the eth1 or eth0 one. Then change DEVICE to eth2 and fix the HWADDR to what you have just posted. Make sure that HWADDR is not listed in the other ifcfg-ethX files. Also, because you have 2 adaptors the same you should fix the HWADDR for each of those so they do not swap when rebooting. For working interfaces you can see the MAC address with "ifconfig | grep HWa". Then it is probably best to reboot (although it is a bit of a sledgehammer).
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, August 11 2011, 03:21 PM - #Permalink
    0 votes
    I don't know If it can change anything, but my mac address refer to . It's a foxconn network adapter working with an intel82579LM.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, August 11 2011, 03:12 PM - #Permalink
    0 votes
    Yes I done the nicks instructions. After a reboot, I have eth2 appeared in my configuration ip but it doesnt work.

    ifup eth2 : give me : «The e1000e device is not present, eth2 initialization will be delayed»

    grep eth /etc/modprobe.conf:

    alias eth0 via-rhine
    alias eth1 via-rhine
    alias eth2 e1000e

    modinfo e1000e :
    filename: /lib/modules/2.6.18-194.8.1.v5PAE/extra/e1000e/e1000e.ko
    version: 1.4.4-NAPI
    license: GPL
    description: Intel(R) PRO/1000 Network Driver
    author: Intel Corporation, <>
    srcversion: 773F7AD95ACF1AF6252A58E
    alias: pci:v00008086d00001503sv*sd*bc*sc*i*
    alias: pci:v00008086d00001502sv*sd*bc*sc*i*
    alias: pci:v00008086d000010F0sv*sd*bc*sc*i*
    alias: pci:v00008086d000010EFsv*sd*bc*sc*i*
    alias: pci:v00008086d000010EBsv*sd*bc*sc*i*
    alias: pci:v00008086d000010EAsv*sd*bc*sc*i*
    alias: pci:v00008086d00001525sv*sd*bc*sc*i*
    alias: pci:v00008086d000010DFsv*sd*bc*sc*i*
    alias: pci:v00008086d000010DEsv*sd*bc*sc*i*
    alias: pci:v00008086d000010CEsv*sd*bc*sc*i*
    alias: pci:v00008086d000010CDsv*sd*bc*sc*i*
    alias: pci:v00008086d000010CCsv*sd*bc*sc*i*
    alias: pci:v00008086d000010CBsv*sd*bc*sc*i*
    alias: pci:v00008086d000010F5sv*sd*bc*sc*i*
    alias: pci:v00008086d000010BFsv*sd*bc*sc*i*
    alias: pci:v00008086d000010E5sv*sd*bc*sc*i*
    alias: pci:v00008086d0000294Csv*sd*bc*sc*i*
    alias: pci:v00008086d000010BDsv*sd*bc*sc*i*
    alias: pci:v00008086d000010C3sv*sd*bc*sc*i*
    alias: pci:v00008086d000010C2sv*sd*bc*sc*i*
    alias: pci:v00008086d000010C0sv*sd*bc*sc*i*
    alias: pci:v00008086d00001501sv*sd*bc*sc*i*
    alias: pci:v00008086d00001049sv*sd*bc*sc*i*
    alias: pci:v00008086d0000104Dsv*sd*bc*sc*i*
    alias: pci:v00008086d0000104Bsv*sd*bc*sc*i*
    alias: pci:v00008086d0000104Asv*sd*bc*sc*i*
    alias: pci:v00008086d000010C4sv*sd*bc*sc*i*
    alias: pci:v00008086d000010C5sv*sd*bc*sc*i*
    alias: pci:v00008086d0000104Csv*sd*bc*sc*i*
    alias: pci:v00008086d000010BBsv*sd*bc*sc*i*
    alias: pci:v00008086d00001098sv*sd*bc*sc*i*
    alias: pci:v00008086d000010BAsv*sd*bc*sc*i*
    alias: pci:v00008086d00001096sv*sd*bc*sc*i*
    alias: pci:v00008086d0000150Csv*sd*bc*sc*i*
    alias: pci:v00008086d000010F6sv*sd*bc*sc*i*
    alias: pci:v00008086d000010D3sv*sd*bc*sc*i*
    alias: pci:v00008086d0000109Asv*sd*bc*sc*i*
    alias: pci:v00008086d0000108Csv*sd*bc*sc*i*
    alias: pci:v00008086d0000108Bsv*sd*bc*sc*i*
    alias: pci:v00008086d0000107Fsv*sd*bc*sc*i*
    alias: pci:v00008086d0000107Esv*sd*bc*sc*i*
    alias: pci:v00008086d0000107Dsv*sd*bc*sc*i*
    alias: pci:v00008086d000010B9sv*sd*bc*sc*i*
    alias: pci:v00008086d000010D5sv*sd*bc*sc*i*
    alias: pci:v00008086d000010DAsv*sd*bc*sc*i*
    alias: pci:v00008086d000010D9sv*sd*bc*sc*i*
    alias: pci:v00008086d00001060sv*sd*bc*sc*i*
    alias: pci:v00008086d000010A5sv*sd*bc*sc*i*
    alias: pci:v00008086d000010BCsv*sd*bc*sc*i*
    alias: pci:v00008086d000010A4sv*sd*bc*sc*i*
    alias: pci:v00008086d0000105Fsv*sd*bc*sc*i*
    alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
    depends: 8021q
    vermagic: 2.6.18-194.8.1.v5PAE SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1
    parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
    parm: TxIntDelay:Transmit Interrupt Delay (array of int)
    parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
    parm: RxIntDelay:Receive Interrupt Delay (array of int)
    parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
    parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
    parm: IntMode:Interrupt Mode (array of int)
    parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
    parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of in t)
    parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)
    parm: EEE:Enable/disable on parts that support the feature (array of i nt)
    parm: Node:[ROUTING] Node to allocate memory on, default -1 (array of int)
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 10 2011, 10:06 PM - #Permalink
    0 votes
    OK so driver kmod-e1000e supports 8086:1502 (entry 00:19.0 on your list above)

    Did you do Nick's instructions? you should then be able to configure the NIC as normal

    If so and it still doesn't work, can you post the output of 'modinfo e1000e'
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 10 2011, 09:51 PM - #Permalink
    0 votes
    00:00.0 0600: 8086:0100 (rev 09)
    00:02.0 0300: 8086:0102 (rev 09)
    00:16.0 0780: 8086:1c3a (rev 04)
    00:16.3 0700: 8086:1c3d (rev 04)
    00:19.0 0200: 8086:1502 (rev 05)
    00:1a.0 0c03: 8086:1c2d (rev 05)
    00:1b.0 0403: 8086:1c20 (rev 05)
    00:1d.0 0c03: 8086:1c26 (rev 05)
    00:1e.0 0604: 8086:244e (rev a5)
    00:1f.0 0601: 8086:1c4c (rev 05)
    00:1f.2 0106: 8086:1c02 (rev 05)
    00:1f.3 0c05: 8086:1c22 (rev 05)
    01:00.0 0200: 1106:3106 (rev 86)
    01:01.0 0200: 1106:3106 (rev 86)
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 10 2011, 09:07 PM - #Permalink
    0 votes
    The unknown device listing from lspci is actually harmless, it usually means that their isn't a corresponding entry for that ID in /usr/share/hwdata/pci.ids

    What does matter is that that the device ID matches the one(s) supported by the e1000e module. Can you post the output of 'lspci -n' (maybe fairly long output)

    This PCI.ids file can be manually updated to reflect the actual name of your NIC by replacing it with the file from here - but this won't make any difference to its functionality however.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 10 2011, 08:10 PM - #Permalink
    0 votes
    I'm not sure what to do here. You could configure your other VIA-Rhine device by adding "alias eth2 via-rhine" to /etc/modprobe.conf but this won't help the intel device. Try a
    depmod -a
    modprobe e1000e
    ifup eth0

    If you are missing a /etc/sysconfig/network-scripts/ifcfg-eth0 you could try cloning the ifcfg-eth1 one, removing the MAC address if it is there or replacing it with the correct value, and changing the DEVICE to eth0. Then do an "ifup eth0".
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 10 2011, 07:01 PM - #Permalink
    0 votes
    I found on the forum that F. van Tour was able to install his intel 82579V . Mine is 82579LM . I dont think theres a big difference, the product have been launch at the same date and they are on the same product description on the intel website.,com_kunena/Itemid,232/catid,24/func,view/id,30308/
    The reply is currently minimized Show
Your Reply