Date: Fri, 04 Feb 2005 15:18:29 -0500 From: "julesg@newebmail.com" <julesg@newebmail.com> To: "Carsten Zimmermann" <carp@hacksocke.de> Cc: freebsd-mobile@freebsd.org Subject: Fwd: NDISulator and Dell wireless 1350 MiniPCI Message-ID: <WorldClient-F200502041518.AA18290032@newebmail.com>
next in thread | raw e-mail | index | archive | help
(Peter, see bottom text of note.) Yes, this is absolutely critical for me too (unless I run windoz,) and please -- not that! Recently, I bit the bullet and deleted my windoz partition from my drive. So until I get my 1350 "truemobile" aircard working (under FreeBSD 5.2.1, for me, anyway) I have no laptop-ethernet mobility. The Dell 1150 has a few other problems too wrt FreeBSD -- at least under 5.2.1. But the biggest problem is the lack of support for the most common air-card. I am not a driver-coder but I am willing to test and help out as I can; And I am an AI person and I think "we" (this group of folks,) could probably build an AI tool that would run under FreeBSD and do a lot more to experimentally build (ie., cut and try) drivers and related components for FreeBSD. Such a tool would need several to be able to do several things: First, to recover from freeze's (because they are common in developing drivers.) Second, to read existing assembler files, C source, hint assignments, and *maybe* script files -- not sure if the last is feasible; But 20 years I had a career writing AI tools to read, manipulate, and re-write one assembler language to another, and assembler to C. I used symbolic tools (MuSimp, MuMath, as well as other stuff, homemade,) to represent models of blocks (where a code block had one entry and one exit, and a data block was a basic data-element definition.) All this was done in BCPL, as I started doing this before C became popular. Anyway, I can't write my own drivers for my laptop, but I would be interested in participating in a group project to attempt to build an mechanical tool-set to help with this work. --jg -----Original Message----- From: "Carsten Zimmermann" <carp@hacksocke.de> To: freebsd-mobile@freebsd.org Date: Fri, 4 Feb 2005 17:18:20 +0100 (CET) Subject: NDISulator and Dell wireless 1350 MiniPCI Hi there, I can hardly imagine that this problem hasn't been (discussed|solved) before, but as google showed up with nothing, I'll go this way... I have aquired a Dell Insprion 1150 with a Dell wireless 1350 MiniPCI 11g card. I have compiled and loaded the ndis.ko and also the if_ndis.ko. The driver loads successfully and the interface ndis0 appears. However, I cannot change any ifconfig values through ifconfig. The interface ndis0 ignores every setting. `sysctl -a |grep ndis0` returns no entries, so changing preferences via sysctl is also not possible. I used the recent Dell drivers from their website (R83097.EXE), expanded the selfextracting archive through wine and found two(!) *.inf and *.sys files. I don't exactly know which drivers to chose, there were subdirs called "AR" and "IR" with same contents (well they do differ in filesize). I tried both drivers. The *.inf file is a utf-16 little endian file, as file(1) told me. `iconv -f UTF-16LE -t ASCII` couldn't convert, so what I did was deleting the blurb of UTF-16 locale strings out of the file and conversion went to a success. I don't know if this might have caused the problem I am encountering. Has anyone some hints or succes stories for me? Thanks a lot! - Carsten -- Carsten Zimmermann // GERMANY // PGP: http://hacksocke.de/public_key.asc _______________________________________________ freebsd-mobile@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-mobile To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?WorldClient-F200502041518.AA18290032>