iB::Topic::Installing Intel e1000e drivers

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » Installing Intel e1000e drivers

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (3) </ 1 2 [3] >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Installing Intel e1000e drivers, Intel 82574L

< Next Oldest | Next Newest >

mikshaw

Group: Members
Posts: 4856
Joined: July 2004

Posted: April 24 2009,10:50

Then I guess maybe it's not an issue with hostname, so it's weirder than I thought.

I have no idea what some of those boot options are...maybe something in there is affecting things.
For all I know there might be a limit to the size of /proc/cmdline. Seems like that would be a bad idea, though.

One thing I'd try is the dmesg command to look for errors.

--------------
http://www.tldp.org/LDP/intro-linux/html/index.html

bartgrefte Offline

Group: Members
Posts: 33
Joined: Jan. 2007

Posted: April 24 2009,18:40

Hmm...

Those bootoptions where all there after installation, not counting the ones I added: host=name, toram, ssh. Mydsl=hda1/mydsl is there as well (in the lilo.conf). But that one got added by the installer.

Before I post both (yes, two) dmesg-files, I solved the backup problem

: I added restore=hda1 to lilo.conf, which wasn't necessary the first several installations I might add...
After I did that, the backup-file (that seemed to have been created successfully the last time I tried) was automatically loaded.

dmesg1 (backup not working)
dmesg2 (backup working)
lilo.conf (Deleted those hd*=scsi options besides hda=scsi, to clear things up a bit.)

And I've set back the hostname I wanted to use, which is completely displayed: BocaDelInfierno

This weekend I'm gonna try the Intel NIC driver again.
Already contacted the guy who made the kernelsources.dsl, thought the problem was related to that.

bartgrefte Offline

Group: Members
Posts: 33
Joined: Jan. 2007

Posted: April 26 2009,17:02

Still can't get the driver working..

Here's some text from the console/terminal that I got after entering the make install command:
http://www.ravenslair.nl/files/makeinstall
First part is missing since the console didn't held on to it...

After that I ran a search, the module isn't where it's supposed to be ("/lib/modules/2.4.31/kernel/drivers/net/e1000e/e1000e.o"
if I'm correct). Instead it seems to be in the src folder of the extracted content of the tar.gz driver file.

So I tried these:
"modprobe /home/dsl/e1000e-0.5.18.3/src/e1000e.o" and "modprobe /ramdisk/home/dsl/e1000e-0.5.18.3/src/e1000e.o"

Both "can't locate module", but it's there! Okay, in the wrong place, but why can't DSL find it even though I entered the full path?