Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Jan 2009 09:30:55 -0500
From:      Glen Barber <glen.j.barber@gmail.com>
To:        Neal Hogan <nealhogan@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: ndis panic HP pavilion ze4400 won't boot
Message-ID:  <4968B11F.9030406@gmail.com>
In-Reply-To: <ab7b49bc0901100509g3d439e87q77a35be5482afe4b@mail.gmail.com>
References:  <ab7b49bc0901080837q7df5c835i1c8f1a01d200a146@mail.gmail.com>	 <4ad871310901081337h23a2d22fldfee1dbabc9044a2@mail.gmail.com>	 <ab7b49bc0901081359u63628a78l6b014102e50e9d9e@mail.gmail.com>	 <4ad871310901081420s3f02fa2drc0571373ec1a1b2f@mail.gmail.com>	 <ab7b49bc0901090618j2e76d380xef56d224212d8a62@mail.gmail.com>	 <4ad871310901090624r702347c9re5ee0c5b6d6908c@mail.gmail.com>	 <ab7b49bc0901091014w6d18f5f7yb9c7c64d853bca1b@mail.gmail.com>	 <4ad871310901091107g12a7cd62l772c08f5e99add56@mail.gmail.com> <ab7b49bc0901100509g3d439e87q77a35be5482afe4b@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4968B11F.9030406>