You are not logged in.
sorry for long story. Trying to build USB boot print server using SAMBA for Home Area Network. Have Intel 82577 chipset on network card. Unable to get drivers to load so no networking; no "get-install" options. I downloaded intel drivers but I needed MAKE.EXE to compile...couldn't find on Slitaz USB install. Downloaded make.exe from internet (cygwin I think) and when booted to Slitaz MAKE didn't seem to work when run up against any Makefile files. Went back to SliTaz and built a flavor file with make and samba but now I dont know what to do with it. Ran tazlito and it extracted into correct directory but now what? Is there an easy way to simply add an application to the USB distro? I dont want to re-ISO just tell current install about additional files. I can download using windows to store on local drive then boot to Slitaz to access if thats the easiest. Thank you in advance.
Nevermind. Didn't realize there was a Packages area on Slitaz site where I could download the tazpkg files directly.
Both slitaz stable(2.6.30.6) and cooking(2.6.37) have in-kernel support for e1000e driver which supports Intel(R) PRO/1000 PCI-Express Gigabit Ethernet.
http://cateee.net/lkddb/web-lkddb/E1000E.html
root@slitaz:~# zcat /proc/config.gz | grep -i e1000e
CONFIG_E1000E=y
I compile e1000e-1.9.5.tar.gz on stable(2.6.30.6)
Perhaps because support for e1000e is in-kernel loading the kernel module for e1000e fails:
root@slitaz:/home/tux# modprobe e1000e
insmod: cannot insert '/lib/modules/2.6.30.6-slitaz/kernel/drivers/net/e1000e/e1000e.ko': invalid parameters
modprobe: failed to load module e1000e: No such file or directory
tail -f /var/log/messages reports when trying to load:
user.err kernel:e1000e: module is already loaded
In order to use the e1000e module the kernel would have to be recompiled removing the e1000e in-kernel support.
I suggest looking at /var/log/messages for error messages related to e1000e or eth0
The in-kernel driver should recognize your card and output some debug info.
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]