Page 1 of 1

Wired internet, wizard, e1000e module doesn't find hardware.

Posted: Tue 04 Jul 2017, 03:59
by Glennsparky
Internet wizard loads the e1000e module but no hardware is found. However, I217-V ethernet controller (0200) Intel (8086:15b8) definetely uses the e1000e module. I entered whatever this is at the prompt "dmesg | grep -e eth0", but i don't know what to do with "Loading kernal module for a network device with CAP_SYS_Module (deprecated). Use CAP_NET_ADMIN and alias netdev-eth0 instead." Thanks for any help.

Posted: Tue 04 Jul 2017, 07:16
by cthisbear
Specs:

http://www.outletpc.com/fu5227-asrock-z ... dmi-s.html

:::::

Looks like your network hardware is...LAN Chipset: Intel I219-V

willix had a solution on the Linux Mint forum.

https://forums.linuxmint.com/viewtopic.php?t=209410

which had these 2 sites mentioned...

https://www.intel.com/content/www/us/en ... 05480.html

http://aslab.com/support/kb/231.html

and a download link...

which he states is to be downloaded to a usb drive

and also (yes it's a i218 'cause no i219)

https://downloadcenter.intel.com/produc ... on-I218-LM

Perhaps our network gurus will assist now that I have located some answers.

So number one....hang in there.

Also if someone posts a solution whether good or bad,
post back your results for others.

Welcome to Puppy.

Chris.

Posted: Tue 04 Jul 2017, 11:35
by rcrsn51
[Edit] No reply after three days. Message deleted.

Re: Wired internet, wizard, e1000e module doesn't find hardware.

Posted: Sun 06 Aug 2017, 08:02
by RickGT351
Glennsparky wrote:Internet wizard loads the e1000e module but no hardware is found. However, I217-V ethernet controller (0200) Intel (8086:15b8) definetely uses the e1000e module. I entered whatever this is at the prompt "dmesg | grep -e eth0", but i don't know what to do with "Loading kernal module for a network device with CAP_SYS_Module (deprecated). Use CAP_NET_ADMIN and alias netdev-eth0 instead." Thanks for any help.
If you boot off the cd with "pfix=ram" can the puppy find your internet? If so, copy the file zdrv_tahr64_6.0.5.sfs from the cd to /mnt/home, configure the boot manager to load it at boot. That's how I fixed mine with tahrpup64

Posted: Sun 06 Aug 2017, 08:20
by RickGT351
I am having the same issue with Precise 5.7.1 and this ethernet card. I followed the instructions on the Intel link https://www.intel.com/content/www/us/en ... 05480.html above. Here's what happened

Code: Select all

# cd /usr/lib/src
# ls
e1000e-3.3.5.3
# cd e1000e-3.3.5.3/
# ls
COPYING  e1000e.7  e1000e.spec  pci.updates  README  src  SUMS
# cd src
# make install
Makefile:67: *** Kernel header files not in any of the expected locations.
Makefile:68: *** Install the appropriate kernel development package, e.g.
Makefile:69: *** kernel-devel, for building kernel modules and try again.  Stop.
# 
So then I went further down the instructions to Load The Module and got this

Code: Select all

# modprobe e1000e insmod e1000e
FATAL: Error inserting e1000e (/lib/modules/3.9.11/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko): Invalid argument
# modprobe e1000e insmod /lib/modules/3.9.11/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
FATAL: Error inserting e1000e (/lib/modules/3.9.11/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko): Invalid argument
# 
I checked whether the file was there and it is.
What do I do now? BTW if this should be a separate post, please let me know

Posted: Sun 06 Aug 2017, 14:27
by ally
just got myself a new lenovo x230 laptop and no ethernet working, had the same trouble with the compile

lots of puppies later followed by a windows install (ball ache - didn't see graphics, sound, wireless etc. etc!!) turns out the ethernet chip is dead

bugger...

:)

ah yes

Posted: Sun 06 Aug 2017, 19:14
by Limbomusic
I bought a lenovo ideapad last year. The built-in camera lasted 5 days. Then it was gone/invisible/broken. Sometimes they have TOO cheap components in their (cheapest) PCs. Other than that its been really good. (ssd drive makes all the difference)

Oh and the 3.x kernels didnt have wifi drivers and the 4.1.11 kernel was buggy as hell on pup-tahr - but the later kernel 4.9.13 / 30 works flawlessly.

:-)