Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
this is so frustating. ok, there was a sis900.o.gz in that directory, so i did gzip -d on it, and then it decompressed into sis900.o. then when i do modprobe /lib/modules/2.4.18/kernel/drivers/net/sis900.o it sais modprobe: Can't locate modules /lib/modules/2.4.18/kernel/drivers/net/sis900.o .
i think this will never work
hmm, then i did insmod again, and now theres sis 900 in the list, but does this mean that i have to do insmod everytime i use linux? and by the way, the network still doesnt work
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
the module probably unloaded on boot. when you ran the gzip -d did it leave the original sis900.o.gz intact? if so, remove or delete the extracted file. then then try modprobe again. if modprobe doesn't work, try the insmod, if it loads don't reboot the system. proceed w/trying to configure the network. if you can get the module loaded, then we'll look at getting it to load at every boot. i'm hoping you can get modpbe to work, if you can it should be as simple as adding this
SiS 900/7016 PCI Fast Ethernet
/sbin/modprobe sis900
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
i meant to delete the file you extracted, not the original. i was thinking that modprobe was getting confused because there were 2 files there. we can't tell now. i'm going to have to do some searching to see how to reinstall that module.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
try modprobe sis900 w/out the .o
if that loads then look at post #25 add the info there. you may have to do rmmod sis900.o first if the module is loaded from the previous insmod command, just check what modules are loaded w/ lsmod.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
my apologies for not recognizing that i had a syntax error in the above posts. (leaving in the .o) you threw me for a loop w/the "ok, there was a sis900.o.gz in that directory, so i did gzip -d on it, and then it decompressed into sis900.o." in any event, i'm glad your up and running, don't forget to add the info posted in #25, to save your settings across a reboot. happy slacking.
good luck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.