Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I am attempting to install a wireless NIC into a Linux box and connect to the net. SuSE Linux 8.1 does not recognize the NIC. I have discovered that the NIC requires the tulip.o module that is not on the box. I was able to find tulip.c and instructions for compiling and using the module. The problem that I have is the step in the instructions that instruct me to enter
When I enter this command, I receive a message that 'make' is not a valid command. I am signed on as root when I enter this command in the console. Does SuSE Linux 8.1 use another command instead of 'make'?
Well SuSE 8.1 has the tulip module included in the distro, i have a linksys net card that uses that module. just do a
modprobe tulip (as root)
and the driver should load, if for some reason u or something else the module got deleted, or someting else, email me and i can send you the module, i have that distro in my home computer, just make sure the kernel u are using is the 2.4.19-4GB, i think the email appears on the members profile if not just tell me.
Thanks to everyone for your help so far. Unfortunately it has been to no avail. Here are the results for each recommended course of action (along with the exact syntax of the original error message received).
When I enter make, the exact syntax of the error is:
bash: make: command not found
So I tried all recommendations received so far. Here are all the results:
Nothing happened. I was immediately returned to a blank prompt and the console was waiting for the next command.
Same thing. Nothing happened - just returned to the normal prompt.
gcc -save-temps tulip.c
bash: gcc: command not found
bash: nmake: command not found
(I had high hopes for this one because the NIC that I have installed is a linksys card.) However this was the longest error message received. It went like this:
/lib/modules/2.4.19-4GB/kernel/drivers/net/tulip/tulip.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19-4GB/kernel/drivers/net/tulip/tulip.o: insmod /lib/modules/2.4.19-4GB/kernel/drivers/net/tulip/tulip.o failed
/lib/modules/2.4.19-4GB/kernel/drivers/net/tulip/tulip.o: insmod tulip failed
To be honest I'm really beginning to get frustrated. This is my first experience with Linux and it is not going well. I was hoping that I would be able to kick Microsoft off my desktop. However, after a week of trying to get connected to the network with linux, I'm almost ready to give up and return to Windows - yuk.
Don't get frustrated just yet. You just have to learn what's going on, and how things work.
First of all, the reason make and gmake and nmake, etc dont' work is because you haven't installed a "development platform." Whether you chose not to because you didn't think you needed it, or if it just didn't get installed -- you'll need it to compile anything.
The long error message you received from the "modprobe tulip" command simply means one of two things:
1) the tulip driver is not actually the one you need to use
2) there is another network card module already loaded that's preventing tulip from loading.
You can use the command "lsmod" to see what modules are loaded into your kernel right now.
Why don't you post the results of
and I'll get back to you on this It's not as complicated as it seems, just have a little patience and the will to learn a bit about the workings.
I've dumped MS... You can too buddy.
The card is a model WMP11 v2.7. All information that I can find indicates that Linksys cards use the tulip.o module (Linksys support FAQs and various other sources). However, all the documentation refers to wired cards. I couln't find anything that specifically addresses wireless cards. I just thought that I would try the tulip module to see if that would recognize the card. I didn't realize installing one simple driver would be so difficult...live and learn I guess.
To be honest, I don't remember if development tools were installed...or if it was even an option. I installed the Linux almost a year ago. Shortly after installing the OS, I received notice that I would be required to move. Everything was packed up in February and I just got settled in and got everything delivered. When I set up the computers, I figured what the heck, why not set up all the family computers on a home network?
Maybe I just need to wipe out the OS and start from scratch. I just can't believe I have to go to that extreme just to install a NIC. I thought that I could give up re-installing the OS every 6-12 months (just to clean the ash and trash off the system) when I gave up on Windows.
Enough griping...haven't given up hope yet. This is the most help I have been able to find...great support. Here is the output from lsmod:
Thanks for the www.google.com/linux reference. It provided an answer. Unfortunately not the answer I was hoping for. As near as I could tell from what I found, my card uses an unsupported chip set (Broadcom BCM4301). Apparently neither Broadcom nor Linksys provide Linux drivers for this chip set at this time.
I'll just keep conducting periodic searches. Maybe someone will develop and post a driver that works with this chip set.
Thanks for all your support and patience with this newbie.