SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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've installed Suse 9.3 Pro on my desktop. It's a dell 8400 with sATA hard drive configuration. I have a Broadcom NetExtreme Gigabit Ethernet PCI-Express card (only network card in my system). When I installed SuSE, everything was peachy except my Ethernet. I have no Idea what the problem is. I've got the Ethernet plugged into my wireless router (D-Link DI-624) and all works fine in Windows and Knoppix 3.8.1.
I had Knoppix installed on my hard drive, but since SuSE 9.3 also had the 2.6.11 Kernel, I decided to use that. Unfortunately though, something isn't working correctly. When I use YaST to view the network cards, it shows my Card as not configured. I clicked configure and entered my network settings (DHCP, default, default, default). Tried ifup eth0 and the card is not seen. ifconfig only sees lo. What do I need to do?
as far as I can tell, that's for wireless cards. The information I'm requesting is on an Ethernet LAN Card. If there is something else I need to do to make ethernet work under ndiswrapper, let me know because I didn't find anything on the sourceforge page that would help. Also, if this is the case, why does the card work when I install Knoppix 3.8.1 without ndiswrapper? Plus, there are linux drivers for broadcom 57xx cards on the broadcom site. There are other options, but the problem is, I don't know linux well enough to use them. What I'm really looking for is someone who can point me to a page that will explain what I need to do or has had the same problem and can explain it themselves.
Thank you for your input, but I don't think giving such a definitive answer is a good thing. Anyone else who has this problem may assume you are right and spend hours or days trying to get ndiswrapper to work when they could have tried something else. You are also telling people who might be able to help me that you've solved my problem so they don't need to respond, which is not the case.
I really do appreciate the recommendation. I'm printing out the information from sourceforge.net right now. I didn't mean to be so forceful earlier, I've been working on a lot of other things. But, I think there are other solutions out their besides ndiswrapper. I'll see if I can get ndiswrapper to work, but if anyone else out there has something else that would help I would appreciate that as well.
Once again. Sorry about that last post, It was arrogant and unintentionally rude. There was probably a more tactful way to ask for alternative solutions to my problem without using ndiswrapper.