• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Wireless card with Suse 9.2

LuckyTaxi

Diamond Member
Just installed Suse 9.2 last night via FTP. I was amazed that it recognized both my wireless cards that i have. I have a DLINK GW-630 and a 3com Officeconnect Wireless 11g card. I set the WEP keys and the SSID but I still dont get any LED lights on the card itself. I have tried both the DLINK and 3com separetly to no avail. With the DLINK, it tells me it cant fetch a DHCP address from my router. Even with a static IP address, I couldnt connect.

With the 3com it said it couldnt find a specific file. BOTH cards are recognized correctly under YAST. No lights are lit and yes the router works fine because my other laptop can access it wirelessly. Is there something I'm missing?
 
1. Have the modules loaded? Do an lsmod to see if the ones you need are loaded.
2. Try to unload the module and then reload it.
3. Try at a command prompt: dhcpcd eth0 or dhcpcd eth1 to get dhcp info

I've got an intel pro wirless b/g built in on my laptop and when I load the ipw2200 module it automatically makes a connection. I then dhcpcd eth1 to get dhcp info and then I'm off to the races (this post is proof of that 🙂 ).
 
It's been a while since I've used Linux (been using Freebsd), but how do I know which modules I need for my wireless card?
 
Try the madwifi driver.

This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

EDIT: That's for the 3com, I can't find any info on the other. What chipset does it use?
 
Originally posted by: n0cmonkey
Try the madwifi driver.

This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

I agree ... I read numerous reviews and they stated their wireless cards "worked out of the box."
I assume they have cards that are supported w/o having to compile stuff, whereas I would have to tinker with mine before it works. Very annoying to me!!!
 
Originally posted by: n0cmonkey
Try the madwifi driver.

This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

EDIT: That's for the 3com, I can't find any info on the other. What chipset does it use?

While I was going through the configuration screens I could've sworn I saw something in reference to "Prism." isnt that a chipset?
 
Originally posted by: lilcam
Originally posted by: n0cmonkey
Try the madwifi driver.

This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

I agree ... I read numerous reviews and they stated their wireless cards "worked out of the box."
I assume they have cards that are supported w/o having to compile stuff, whereas I would have to tinker with mine before it works. Very annoying to me!!!

It's the decentralized development model. It seems that nothing wireless makes it back into the core kernel. I won't use Linux on machines I want to use wireless. I refuse.
 
Originally posted by: lilcam
Originally posted by: n0cmonkey
Try the madwifi driver.

This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

EDIT: That's for the 3com, I can't find any info on the other. What chipset does it use?

While I was going through the configuration screens I could've sworn I saw something in reference to "Prism." isnt that a chipset?

There is a prism chipset. If it's a G card, it's prism54. There is work on an open source driver for that, but I don't know the quality of it. Probably better than the hacks that are the rest of the drivers. :roll:
 
Originally posted by: n0cmonkey
Originally posted by: lilcam
Originally posted by: n0cmonkey
Try the madwifi driver.

This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

EDIT: That's for the 3com, I can't find any info on the other. What chipset does it use?

While I was going through the configuration screens I could've sworn I saw something in reference to "Prism." isnt that a chipset?

There is a prism chipset. If it's a G card, it's prism54. There is work on an open source driver for that, but I don't know the quality of it. Probably better than the hacks that are the rest of the drivers. :roll:

Yea it's a 3Com OfficeConnect Wireless 11g PC Card.

I really want to use either Linux or FreeBSD, but if it requires me having to do A LOT of configuration just to get my wireless working, then I want no part of it. What do you suggest to use if i want wireless? I might try Fedora just to see if that'll work a little better.
 
Originally posted by: lilcam
Originally posted by: n0cmonkey
Originally posted by: lilcam
Originally posted by: n0cmonkey
Try the madwifi driver.

This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

EDIT: That's for the 3com, I can't find any info on the other. What chipset does it use?

While I was going through the configuration screens I could've sworn I saw something in reference to "Prism." isnt that a chipset?

There is a prism chipset. If it's a G card, it's prism54. There is work on an open source driver for that, but I don't know the quality of it. Probably better than the hacks that are the rest of the drivers. :roll:

Yea it's a 3Com OfficeConnect Wireless 11g PC Card.

I really want to use either Linux or FreeBSD, but if it requires me having to do A LOT of configuration just to get my wireless working, then I want no part of it. What do you suggest to use if i want wireless? I might try Fedora just to see if that'll work a little better.

I'm pretty sure the 3com is atheros chipset, which should be supported by madwifi. OpenBSD supports 1 3com atheros card (3Com 3CRPAG175 AR5212 CardBus a/b/g), but I'm not sure if it's the one you have or not. I can't find mention of the dlink at all...
 
I think if you boot using an OpenBSD disc, you might get some good information out of the dmesg. There are ways to get that info in Linux (pciinfo or something), but I don't know them off hand.
 
Originally posted by: n0cmonkey
If I was in the market for a new notebook I'd skip the powerbook and go for the iBook. :Q

Why's that?!?!??!?!

Back to the drawing board for me but I'm still going to try to get it working.
 
Originally posted by: lilcam
Originally posted by: n0cmonkey
If I was in the market for a new notebook I'd skip the powerbook and go for the iBook. :Q

Why's that?!?!??!?!

Back to the drawing board for me but I'm still going to try to get it working.

I don't see a lot of benefit at the moment of spending more money on the powerbook. The resolution is nice. I don't have a gigabit network, I don't have PCI cards, I don't need the Firewire800, I don't have a DVI monitor...

I do love my powerbook though. 🙂
 
For your DLink card, you need ndiswrapper, and your windows drivers. Do some googling about ndiswrapper to get some help setting it up. I have the same wifi card in my laptop (I'm pretty sure anyway...It uses the Mattell chipset) and it works fine in ubuntu linux. It did not work out of the box though.
 
I am installing Suse 9.2 on my laptop now..

I couldn't get my M$ wireless G card working.. (broadcom chipset, i believe)

Hopefully I have better luck with SUSE, and will try some of the suggestions..

If it does not work, what is a SUPPORTED wireless card.. ( I would assume "B" )

Are there any that work out of the box?
 
Originally posted by: n0cmonkey
Try the madwifi driver.

This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

EDIT: That's for the 3com, I can't find any info on the other. What chipset does it use?

So, for instance, IIRC OpenBSD asked TI to change the licensing on their firmware for the ACX100 chip, and the response was silence.

If you are not allowed to bundle certain parts of a driver with the OS, how the hell are you supposed to make it work out of the box?

If you can't get an ISA (and the entire goddamn point of an ISA is so you don't have to know the freakin' microarchitecture to use the goddamn hardware!) and a license to package firmware required to make the damn thing work, you can't have a complete driver out of the box. It's as simple as that.

As for the MADWIFI driver, Atheros' chip includes a hardware chip that can be controlled by software to broadcast on licensed parts of the spectrum. FCC regulations state that unlicensed products may not allow an end-user to do this. This requires that the HAL be non-open.
 
Having some issues with the ndiswrapper.

Step 7: type in "ndiswrapper -i /path/to/mn720-ankh.inf" This tell ndiswrapper where the .inf and the associated .sys is.

Step 8: type in "ndiswrapper -l" This will display your installed "wrapped" Microsoft drivers.



When i type in ndiswrapper -l I get "Installed ndis drivers: MN720 hardware not present..

Under YaST and network devices, it says Wireless Network card ( PCMCIA _ is configured with DHCP..


Step 9: type "modprobe ndiswrapper" This is uses the modprobe command to load a driver into linux, which points to ndiswrapper as a driver, which in turn is controlling your windows driver for your device.

I get "modprobe config" already contains alias directive" ????

Are my drivers "wrapped" ?

Step 10: type in "iwconfig wlan0 essid [SSID name goes here]" This is the iwconfig command, which displays or sets settings for your wireless extensions. wlan0 is the default if you only have one wireless card.

Error: Set failed on device wlan0; no such device!

-----

Got this from another site..

[/quote] * Install the 64 bit broadcom wifi driver that you downloaded earlier:

ndiswrapper -i netbc564.inf

* check that it got installed okay:

$ ndiswrapper -l
Installed ndis drivers:
netbc564 driver present, hardware present [/quote]

----I get----

Installed ndis drivers: MN720 hardware not present..


I am missing something that I am not getting the hardware recognized..








Stuck!

Help please 😛


 
This is one of the reasons I hate Linux, too many sources, not enough working stuff. Wireless cards should be supported and work out of the box.

Odd, mine works out of the box. Guess that's what you get for using shady hardware.

I assume they have cards that are supported w/o having to compile stuff, whereas I would have to tinker with mine before it works. Very annoying to me!!!

Complain to 3Com then, there's not much any devs can do if they don't have proper docs or firmware to make the cards work.

I think if you boot using an OpenBSD disc, you might get some good information out of the dmesg. There are ways to get that info in Linux (pciinfo or something), but I don't know them off hand.

If it's a PCMCIA card 'cardctl ident' should give some information, but not all manufactures fill it out properly. If it's PCI then 'lspci' will display everything on the PCI bus.

 
Originally posted by: Nothinman
802.11b, it's a Prism2 based Linksys.

It seems like ( from what I've read ) that almos all of the 802.11b cards work..

I am having a hard time with ndiswrapper..

if i check etc/ndiswrapper it shows my MN-720 folder ( Wifi card ) but nothing inside or installed..

Yet a quick check of ndiswrapper -l shows the driver is installed but no hardware found...
 
I've never used ndiswrapper and never will. I sort-of dislike using the binary-only nVidia drivers, I won't even attempt to use binary-only Windows drivers on my system.
 
Back
Top