From owner-freebsd-questions@FreeBSD.ORG Sat Jan 10 14:31:17 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E9CB106564A for ; Sat, 10 Jan 2009 14:31:17 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mx1.freebsd.org (Postfix) with ESMTP id 3785D8FC16 for ; Sat, 10 Jan 2009 14:31:16 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: by qw-out-2122.google.com with SMTP id 9so5784070qwb.7 for ; Sat, 10 Jan 2009 06:31:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=MG4dtWCqV0oDYTUprQCkLaqjTf9Gk2dsryWUI4t+88s=; b=fktzDUQuWdzsf7LXtUXpYxbIsom9siGdklQiGg/lfZkTTR3RBHYF+QuIEumD694MK5 xzAR5KuArNUHDJQchNrXVFJcS2osHI42B7TvDhKuKgWO9j2qHvkWdx/0zBQ2iPnN89Ti CZEd9q8NuR598FkuS6a25DAjW/bbD223r41p8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=cpMnp7MzgCwhPyhwIzpdbmtR/twMu9BM4QLyEEh4ZWapByKUANc+KhtSiX3/w7WzCy k4YhoS7C19PAqMlrl1ELQd7HLKUyogt82ThGPL8Typz2kPDf2uiWCafWVD2XSmHoM54S w+KCnZ7aK428c4qQ9xlvx8vo2frRUoypZMjPM= Received: by 10.214.182.2 with SMTP id e2mr23793066qaf.204.1231597876290; Sat, 10 Jan 2009 06:31:16 -0800 (PST) Received: from ?144.118.51.129? (n2-51-129.dhcp.drexel.edu [144.118.51.129]) by mx.google.com with ESMTPS id 30sm5191914yxk.27.2009.01.10.06.31.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 10 Jan 2009 06:31:14 -0800 (PST) Message-ID: <4968B11F.9030406@gmail.com> Date: Sat, 10 Jan 2009 09:30:55 -0500 From: Glen Barber User-Agent: Thunderbird 2.0.0.12 (X11/20080310) MIME-Version: 1.0 To: Neal Hogan References: <4ad871310901081337h23a2d22fldfee1dbabc9044a2@mail.gmail.com> <4ad871310901081420s3f02fa2drc0571373ec1a1b2f@mail.gmail.com> <4ad871310901090624r702347c9re5ee0c5b6d6908c@mail.gmail.com> <4ad871310901091107g12a7cd62l772c08f5e99add56@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: ndis panic HP pavilion ze4400 won't boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 14:31:17 -0000 Neal Hogan wrote: > > Well, it took me all day, but I did synch-up the source with the kernel. > However, being new to the ways of fBSD I (accidentally) ended up > building the -CURRENT source and kernel (8.0). I tried ndisgen on the > latest driver and it didn't work . . . I'll tell you why in a second. > Lesson learned, I suppose. > I'm a bit uncomfortable dealing with current. I'd rather go back to the > 7.1-RELEASE, which claims to have better ndis support. FYI - I've dual > booted fBSD, and am merely experimenting with it. So, while it may seem > odd that I continue to move between versions, I do have access to other > machines that have more familiar environments (oBSD and XP). > Well, if you are going back to 7.X, I'd start from scratch. If you haven't gotten WiFi working yet, I assume you haven't gotten much else configured on the system. Doing a fresh install will alleviate some headaches, in my opinion. > Now, the *ndisgen path/to/inf path/to/sys* didn't work because it said > that the .inf file was in a different format than it expected. So, I > attempted to convert it to ascii using *iconv -c -f utf-16 -t ascii > path/to/inf > .inf.ascii* and use the new file as the .inf. Again, it > said it was the wrong format. That's when I bailed. So as not to waste > my time with 8.0, because I wish to pursue expermenting on 7.1. Anyway . This could be due to something in -CURRENT. I'm not sure. > . . at this time, I have one more question regarding the driver that > will end up being successfull (hopefully there is one). > > Should I have to manipulate the .inf file? There is the wrong format > issue, mentioned above, and when setting up ndis in the "panicky" > situation, ndisgen claimed that the last line of the .inf file was bad > (I forget the actual teminology used). So, I deleted that line and it Besides `iconv' if needed, no, you shouldn't have to edit anything in the .INF and .SYS files. If they don't work, something else is wrong. > successfully generated the .ko file. It seems odd to me that I would > have to manipulate the driver information so much and that it may the > source of some of my ndis problems. Another way of asking this question > . . . will the successful driver just work (i.e., not need such > manipulations)? > Ideally, yes, it should 'just work'. > Thanks for you patience. > -- Glen Barber