• 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.

-

Usually a double-high beep-beep is good.

A high-low beep-boop is not. To explain the tones, the first high beep means PCMCIA support (kernel modules) were loaded. This is for the PCI adapter.

The second high beep means a card was detected, and its drivers successfully loaded.

To configure your device, you look in /etc/pcmcia ... once the above drivers successfully load, the requisite network scripts are automagically run.

So did you configure any files in /etc/pcmcia ?

I recently successfully configured the DWL-500 under SuSE Linux.

The preferred drivers for the D-Link DWL-650 are the linux-wlan-ng drivers that you download & compile yourself. However, I never got these to work.

I did get the orinoco_cs drivers to work, but only after enabling the new kernel PCMCIA drivers (yenta_socket) instead of the older external drivers.

If the loading of the device driver locks up the PC, pop out the PC card (yes you can hot-swap with the PCI adapter).

If what I've mentioned so far is greek to you, then you have some reading to do. 🙂 Let me know if you have any more questions.

Finally, I replaced the DWL-650 with an orinoco Gold PC card, which is much better performing.
 
Actually it does make sense.

I have not made any config changes since installing the OS, so that's probably the problem. I found a pretty in-depth guide on setting up the DWL-500 and 650, but it's for an ad hoc setup, which probably won't be very useful for me since I use an AP. I suppose I'll just experiment until it works, that's how I learned everything I know (and I mean everything, not just computer stuff 😉)
 
Ad hoc and Infrastructure configurations are very similar.

I think it's a one-line change in the /etc/pcmcia/wireless.opts (orinoco_cs drivers) or /etc/pcmcia/wlan-ng.opts (linux-wlan-ng drivers).

Just like you're trying to do, I basically fussed with it until it worked. Although it wasn't extremely helpful, I read a lot of archived mailing list postings from the wlan-ng mailing list.

Like I said, ironically my solution was to ditch the preferred wlan-ng drivers and use the orinoco_cs drivers.

From my recollection, the wlan-ng drivers would always lock up the PC upon loading (until I popped the PC card out). The orinoco_cs drivers wouldn't load properly until I chose the kernel PCMCIA drivers (aka yenta_socket). Other than these hickups, it was surprisingly easy.
 
So what have you done so far?

If you'd like to give the orinoco_cs drivers a try (they are included out-of-the-box beginning with kernel 2.4.10), then just edit /etc/pcmcia/wireless.opts and /etc/pcmcia/network.opts

Then start the PCMCIA subsystem, and report back what happens. Look at the log file /var/log/messages to see any errors, and work from there.

I'd start without using WEP. Once you get the orinoco_cs drivers working, you can download the latest orinoco_cs (0.10), compile it, and install it.
 
Well, so far I've tried to compile pcmcia_cs and swldpc11_cs, as was suggested by this page, but the build fails shortly after I start it. I would try the drivers you suggested, but the kernel tarballs average 22 megs. That wouldn't be a problem if I had access to my network, but my only connection to the rest of my LAN is a single 3.5" floppy disk.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top