From owner-freebsd-drivers@FreeBSD.ORG Mon Jan 19 10:16:54 2009 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F2F3106566B for ; Mon, 19 Jan 2009 10:16:54 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id EC24C8FC19 for ; Mon, 19 Jan 2009 10:16:53 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2667685rvf.43 for ; Mon, 19 Jan 2009 02:16:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:mail-followup-to:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent:organization :x-operation-sytem; bh=KuZ454ulc+5B7YBeyUK52D2sUeNyddQe0nenAolxuVI=; b=tcImwmwB1QpTt+iBwpzeOLgxv6fFyDPZVJPfTc7ZkcWrNgbwqVUrDabLY49ZPiKT9U GcXV+F3nnihvBzI5rSCZok9+GNRP9oiiPDfGBTFrK9/qnKSuzvhsux44MLmUjABhImMc Rx0JmuU6Jsb1XlZD//H59q9TDMzoSarUk9U3U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent:organization :x-operation-sytem; b=DdWCAzZxA8O0yW2fYZelB2lvmOrT8Ke84aXbcDMNhWolLOXZKw000VYxSzgDIJCThP R3n1IcmyV9w2izNA5zLZoUGOeJA9B6qQn0gkTm79GGI4xyKwie1rUBKAt3cPH1ePrxFS N9tFPhxsVsVYqGHO/XfsGw7gJY2+LmczHoK8o= Received: by 10.140.163.3 with SMTP id l3mr1682151rve.226.1232360213617; Mon, 19 Jan 2009 02:16:53 -0800 (PST) Received: from freebsd.weongyo.org ([211.53.35.67]) by mx.google.com with ESMTPS id l31sm9709417rvb.2.2009.01.19.02.16.51 (version=SSLv3 cipher=RC4-MD5); Mon, 19 Jan 2009 02:16:52 -0800 (PST) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Mon, 19 Jan 2009 19:16:23 +0900 From: Weongyo Jeong Date: Mon, 19 Jan 2009 19:16:23 +0900 To: Jim Andersson Message-ID: <20090119101623.GC81329@freebsd.weongyo.org> Mail-Followup-To: Jim Andersson , freebsd-drivers@freebsd.org References: <20090116040425.GB66457@freebsd.weongyo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: freebsd-drivers@freebsd.org Subject: Re: 8187SE driver X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Weongyo Jeong List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 10:16:54 -0000 On Sat, Jan 17, 2009 at 04:16:43PM +0100, Jim Andersson wrote: > > > From: weongyo.jeong@gmail.com > > Date: Fri, 16 Jan 2009 13:04:26 +0900 > > To: freebsddog@hotmail.com > > CC: freebsd-drivers@freebsd.org > > Subject: Re: 8187SE driver > > > > On Thu, Jan 15, 2009 at 11:48:32AM +0100, Jim Andersson wrote: > > > > > > Hi! > > > > > > Is there any chance of getting my wireless card running in CURRENT. Linux says it�s a Realtek 8187SE wireless network card. I have seen some driver for other 8187 cards, is it possible to force such driver to try identify the card? > > > > > > > > > Here is the output of pciconf -lv in my FreeBSD CURRENT:none1@pci0:1:0:0: class=0x028000 card=0x819910ec chip=0x819910ec rev=0x22 hdr=0x00vendor = 'Realtek Semiconductor'class = network > > > > I think a thing you can try is that, NDISulator using ndis(4). AFAIK > > there's no support for 8187SE driver until now. > > > > regards, > > Weongyo Jeong > > > > I tried ndisulator but it didn´t work. I used the INF and the SYS file for Windows Xp. I even tried including a cat file. > Although one thing changed, the card is no longer listed when i type pciconf -lv. Dunno if that´s good or bad? It looks it's a bad news. Could you please show me dmesg's ouput and steps you followed? regards, Weongyo Jeong From owner-freebsd-drivers@FreeBSD.ORG Sat Jan 24 06:04:30 2009 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4BBA106566B for ; Sat, 24 Jan 2009 06:04:30 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-71-117-207-61.ptldor.fios.verizon.net [71.117.207.61]) by mx1.freebsd.org (Postfix) with ESMTP id 53A418FC13 for ; Sat, 24 Jan 2009 06:04:29 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 9AFC9B64F; Fri, 23 Jan 2009 21:41:26 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id FAA21539; Sat, 24 Jan 2009 05:23:26 GMT Message-Id: <200901240523.FAA21539@sopwith.solgatos.com> To: freebsd-drivers@freebsd.org, freebsd-hardware@freebsd.org Date: Fri, 23 Jan 2009 21:23:26 +0000 From: Dieter Cc: Subject: Dealing with Seagate's problematic 7200.11 firmware. X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 06:04:31 -0000 Most of you have read about the problems with Seagate's 7200.11 disks. For those of you that haven't, the firmware on many of these drives is buggy, and can "brick" the drive when powering up or rebooting the system. Thus far, Seagate's response has been less than wonderful. We need a FLOSS solution. Goals: 1) Ability to read the number of log entries. 2) Ability to change the number of log entries. 3) Ability to install new firmware from Unix. We need for this to work with any flavor of Unix, on any CPU arch, without reboot or power cycle. We need for this to work on one drive without affecting other drives. I don't expect to be able to write FLOSS firmware for the drives, so this isn't listed as a goal. If you think you can, please feel free. The problem: "IF the drive is powered down when there are 320 entries in this journal or log, then when it is powered back up, the drive errors out on init and won't boot properly - to the point that it won't even report it's information to the BIOS." Maxtorman, slashdot discussion [2] If Maxtorman is correct, then once the drive has been operating awhile, we have a 1 in 320 chance that the circular log is at entry 320. We want to be able to find out how many log entries the disk currently has, and we want to be able to change the number of log entries away from 320, while we wait for Seagate to get its act together and release firmware that works properly. Since Seagate's solution will require attaching the drive to an x86 system and booting a FreeDOS ISO from CD, if the log is at 320 that boot will brick the drive. There are other firmware problems with the 7200.11 series, but this is the biggie. Once Seagate releases working firmware, we want to be able to install it from Unix, on any CPU arch. Seagate's release can only install on x86 using FreeDOS. *ATA Commands that may be useful: command name command code in hex page [1] pdf page [1] Read Log Ext 0x2F 27 33 S.M.A.R.T. Read Log Sector 0xB0 / 0xD5 28,34 34,40 S.M.A.R.T. Write Log Sector 0xB0 / 0xD6 28,34 34.40 Write Log Extended 0x3F 28 34 Download Microcode 0x92 27 33 Questions: Is Maxtorman correct about the 320 log entries? Are the commands listed above the ones we need? What is the difference between the "Log Extended" and the S.M.A.R.T. Log Sector? Is "Microcode" the same as "firmware"? (Seagate uses the term firmware elsewhere in the manual, but I don't find any sort of "write firmware" command.) Where can we get more detailed info about these commands and how to use them? References: [1] Seagate Barracuda 7200.11 Serial ATA Product Manual rev C August 2008 http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%207200.11/100507013c.pdf [2] http://it.slashdot.org/article.pl?sid=09/01/21/0052236