Date: Tue, 26 Apr 2005 08:51:56 +1000 (EST) From: Neo-Vortex <root@Neo-Vortex.net> To: Bill Paul <wpaul@freebsd.org> Cc: freebsd-hardware@freebsd.org Subject: Re: Too Evil, Too Furious Message-ID: <20050426084243.U87982@Neo-Vortex.net> In-Reply-To: <20050425171528.7EF8B16A4D3@hub.freebsd.org> References: <20050425171528.7EF8B16A4D3@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 25 Apr 2005, Bill Paul wrote: <snip> > The cards that I can't seem to get my hands on are: > > - Marvell wireless -- supposedly D-Link used this on a card called the > DWL-G510, but only on the first revision. The second board revision > uses an Atheros chipset, which is already supported. Unfortunately, aside > from this one PCI card, this chipset tends to only show up as a built-in > component on motherboards or laptops, which makes it hard for me to just > go out and get one. Also in Asus WL-138G (802.11g) cards - if you want i can take a few pictures of the box and card and/or give you exact chipset information from the card (its visible) - unfortunately as the card is not owned by me, i can not loan it to you. :( And no, it dosent have anything saying what HW revision, although only Marvell drivers exist for it... (on the asus website and cd anyway) Although... i might still be able to help (see below) <snip> > If you don't want > to part with your hardware, you can still help by giving me remote access > to a system with the card installed. Note that just giving me a shell > really doesn't help: in order to experiment, I need to be able to load, > test and unload kernel modules, which requires superuser access. The > ideal setup would be to use a serial console, since in some cases it > may be necessary to poke around with the kernel debugger. Don't consider > this unless you have a scratch box lying around that you can afford to > have bounced a few times, because I guarantee you I will crash the thing > a few times before I get it to work. I should be able to set up a shitty p1 test box and stick the card in it if you need... i'll be able to give you serial console access, ssh, etc, the box is yours to do as you wish :) I might need a week or so to get it set up as for i need to salvage a hdd from somewhere and either make up, or buy a nice pretty null-modem cable (to plug into another box - so you can actually access the serial console :P) <snip> > Lastly, if you can't do either of these things, you can still help by > providing some important information. If you have one of these cards, > tell me where you got it! Tell me what manufacturer and model number > it is, but also carefully inspect the box it came in and tell me _ANY_ > identifying markings on it that will help me distinguish it from all > the other cards out there. Very often, card distributors will sell two > different cards with the same part number. (I own no less than 4 cards > called the "LinkSys LNE100TX," all of which have different chipsets on > them.) D-Link and Linksys are some of the worst offenders in this area. > Even worse, most PCI cards now have metal RF shields on them that > cover up the chipsets, which makes it impossible to tell what you're > getting just by looking at the picture on the box. > > Look for hardware revision info. Look for firmware revision info. If > you can provide a URL to the exact card you got from the place you > ordered it, even better. Whatever you do, don't just tell "I have > a D-Link model so-and-so." Instead, tell me "I have a D-Link model > so-and-so that I ordered from the following URL, and the box has > a sticker that says HW rev: B3 FW rev: 2.0." If I have info like this, > I can grab a card off a store shelf when I find the right one. Otherwise, > I can't take the chance on paying for it only to find out later it > uses a chipset I already have. I can get a url from the place it was gotten from (i'll have to ask the man who brought it, but it shouldnt be a problem) - although im in Australia... wich might be a problem... the above idea might work a little better :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050426084243.U87982>