linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dustin Lang <dalang@cs.ubc.ca>
To: Isidoro Reyes de Zuloaga <isidoro@qassessorament.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: netgear MA111 v2
Date: Fri, 19 Nov 2004 15:36:47 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.60.0411191523260.2564@bigrock.cs.ubc.ca> (raw)
In-Reply-To: <200411192231.49831.isidoro@qassessorament.net>


Hi,

Disclaimer: I'm not an expert here, just someone with a working 
wireless-USB device on linux-ppc.

>From a brief web search, it looks like the support for SiS162 is not 
great.  If a (good) driver doesn't exist, you're just out of luck, unless 
you want to try to find specs for the chipset and then write something 
yourself (or wait for someone else to do it).  If you can, take it back 
and buy a different adapter.  There are several USB wireless devices that 
work well.  Look on the web for someone reporting that a given device 
works, and make sure you get exactly the right revision.  I have a Linksys 
WUSB 11 (I forget which rev) and it works great.

Cheers,
dstn

> Hi!
> I just bought the wireless usb adapter of netgear. I bought this model because
> i read arround that i was working fine with linux. The problem now is that i
> bought the v2 model, with a sis chipset.
> Does anyone know how to fix this, or what to do.
> I downloaded the wlan-ng drivers, i compile them....
> Just wanna know some ideas.
> thanks in advance.
> isidoro
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>

      reply	other threads:[~2004-11-20  1:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 21:31 netgear MA111 v2 Isidoro Reyes de Zuloaga
2004-11-19 23:36 ` Dustin Lang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.60.0411191523260.2564@bigrock.cs.ubc.ca \
    --to=dalang@cs.ubc.ca \
    --cc=isidoro@qassessorament.net \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).