|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
I don't like Linksys :(
I recently called them today inquiring about a certain wireless-N adapter I was interested in purchasing, but I wanted it to be compatible with OpenBSD so I asked about the chipset it was using, and the outsourced reps on the other line didn't even know what a chipset was. I heard them conversating (with their superiors I guess) in a different language and came back to tell me that this particular wireless adapter did not have any chips. What? The latest representative I spoke with I was getting impatient after an hour and a half, so I kindly asked her if she could forward me/transfer my call to maybe a more knowledgable higher tier support, and I was hung up on!!! |
|
|||
I posted in their forums and they deleted my post:
Quote:
|
|
||||
Quote:
Picking one embedded 802.11n chip I have with a netbook: Quote:
|
|
|||
You are asking the wrong questions to the wrong people. Most of the world is not familiar with OpenBSD, & expecting it will simply give you ulcers.
Business orients itself towards populations which are likely to buy their products & services in large quantities. Hence, they will have some familiarity with Windows & possibly Linux. Anything else is a fluke. Business provides technical support in order to cover very basic needs. Support does not generate revenue, so the most minimal effort will be expended on setting up the necessary infrastructure or hiring knowledgeable people. Look at it another way. You can likely buy a corded telephone from any vendor & expect that once it is plugged in, basic service can be attained. This is because the standards are well established, & everyone knows what they are. Wired telephone service is a mature industry. Wireless isn't mature, so focusing on standards is even more important. When dealing with wireless with the *BSD family, look at the manpage for whatever device you have (which can be determined in dmesg(8) output after the device is connected...). A general list of drivers can be found from apropros(1): http://www.openbsd.org/cgi-bin/man.c...=1&format=html After studying the manpage for whatever device you have (as also suggested by jggimi...), you will have a better idea about what standards to look for in third-party products. It is also common within the manpages to state what specific commercial cards have been known to work. Lastly, to minimize getting bit by buying hardware that ends up not being supported, only buy from vendors where it is very clear what the return policy is, & make sure you return items within the timeframe specified. |
|
|||
Quote:
All you've done is annoyed and insulted some random people trying to make a meager living. Instead of contacting Linksys/Cisco (..you probably didn't buy it from them directly), deal with the company you intend on purchasing the card from. Inquire about their refund/return policy, buy it.. and then just try it out for yourself. |
|
|||
The main reason why I attempted to ask them was because in my previous history with them, I had bought two of the exact same wireless adapters (at different points in time), same model, same version number, yet they both ended up having different chipsets! This was very surprising to me. I guess I got lucky on one while a while later (not too far ahead in time) it was something totally different. So I am paranoid that in the span between months I do research, that they will suddenly begin to manufacture the very card I am researching and about to buy with a different chipset...
|
|
|||
Quote:
Case in point, I bought an HP netbook based on information found on misc@ stating that all components were known to work (including wireless). dmesg(8) was attached. I ended up buying the same model, but wireless doesn't work, & my dmesg(8) output shows that my system was six months newer. Componentry can & does change throughout the lifecycle of a product line. It is all based on the manufacturer's suppliers & where they find better deals. |
|
|||
In addition to the man pages I find google and an online vendor catalog to be helpful.
My usual plan of attack is to browse the open box section at New Egg and enter the wireless N adapter model number into google followed by "linux" Almost invariably someone has tried the adapter and if semi-knowlegable will post the chipset. I have even been alerted that the manufacturer had changed the chipset while retaining the same model number. When purchasing I try to speak to a sales person and tell them that I want a particular version with a particular chipset and get assurances that I can make the return without a restocking fee if it does not have the desired chipset. The other tactic I use is to buy locally and have a sales person open the box to look directly at the chipset. In general RAlink and the older atheros drivers work well and I usually hunt for one those chipsets. Last edited by shep; 20th March 2010 at 03:04 AM. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Is a Linksys WRT54G wireless card compatible with OBSD? | guitarscn | OpenBSD General | 7 | 24th February 2009 03:01 AM |