On 11/22/10, Paul B Mahol wrote:
> On 11/22/10, Alberto Villa wrote:
>> On Wednesday 17 November 2010 10:57:34 Paul B Mahol wrote:
>>> Please use ndis5 branch. master branch is in heavy development.
>>> CURRENT branch just blindly (and badly) track code on FreeBSD
>> CURRENT.
>>
>> ok. unfortunat
On 11/22/10, Alberto Villa wrote:
> On Wednesday 17 November 2010 10:57:34 Paul B Mahol wrote:
>> Please use ndis5 branch. master branch is in heavy development.
>> CURRENT branch just blindly (and badly) track code on FreeBSD
> CURRENT.
>
> ok. unfortunately in this test i made an error and just
On Wednesday 17 November 2010 10:57:34 Paul B Mahol wrote:
> Please use ndis5 branch. master branch is in heavy development.
> CURRENT branch just blindly (and badly) track code on FreeBSD
CURRENT.
ok. unfortunately in this test i made an error and just saw that...
`--> git status
# On branch ndi
On 11/17/10, Alberto Villa wrote:
> On Mon, Nov 15, 2010 at 2:41 PM, Paul B Mahol wrote:
>> Feel free to test code at:
>>
>> gitorious.org/NDISulator
>> github.com/richardpl/NDISulator
>>
>> The code is developed on CURRENT. But with small changes it can be
>> compiled on STABLE too.
>
> thanks!
On Mon, Nov 15, 2010 at 2:41 PM, Paul B Mahol wrote:
> Feel free to test code at:
>
> gitorious.org/NDISulator
> github.com/richardpl/NDISulator
>
> The code is developed on CURRENT. But with small changes it can be
> compiled on STABLE too.
thanks!
i've applied a checkout of last night to curren
On 11/15/10, Alberto Villa wrote:
> On Wed, Oct 27, 2010 at 3:36 PM, Paul B Mahol wrote:
>> Currently amd64 is broken with some/most drivers. Drivers appears to
>> use fpu registers.
>> I dunno how it ever worked, probably original developer(s) never
>> encountered drivers which use fpu registers
On Wed, Oct 27, 2010 at 3:36 PM, Paul B Mahol wrote:
> Currently amd64 is broken with some/most drivers. Drivers appears to
> use fpu registers.
> I dunno how it ever worked, probably original developer(s) never
> encountered drivers which use fpu registers.
>
> I will probably fix amd64 support i
El día Friday, October 29, 2010 a las 07:07:18AM +, Paul B Mahol escribió:
> On Fri, Oct 29, 2010 at 6:34 AM, Scot Hetzel wrote:
> > On Fri, Oct 29, 2010 at 12:59 AM, Matthias Apitz wrote:
> >> I booted the 8-CURRENT this morning, loaded the module with kldload(8) and
> >> wlan0 came up by i
On Fri, Oct 29, 2010 at 6:34 AM, Scot Hetzel wrote:
> On Fri, Oct 29, 2010 at 12:59 AM, Matthias Apitz wrote:
>> I booted the 8-CURRENT this morning, loaded the module with kldload(8) and
>> wlan0 came up by its own (I did not realized this yesterday). I have in
>> rc.conf:
>>
>> wlans_ndis0="wla
On Fri, Oct 29, 2010 at 12:59 AM, Matthias Apitz wrote:
> I booted the 8-CURRENT this morning, loaded the module with kldload(8) and
> wlan0 came up by its own (I did not realized this yesterday). I have in
> rc.conf:
>
> wlans_ndis0="wlan0"
> ifconfig_wlan0="WPA DHCP"
>
> wpa_supplicant(8) starte
El día Thursday, October 28, 2010 a las 12:07:10PM +, Paul B Mahol escribió:
> > # ifconfig ndis0 192.168.2.200
> >
> > All this is with a 8-CURRENT kernel/system as of May 2009. I will now build
> > a
> > USB key from HEAD and will continue testing.
> >
>
> On 9/8 CURRENT you create wlanX wi
On Thu, Oct 28, 2010 at 4:37 PM, Scot Hetzel wrote:
> When you get the Windows NDIS driver from the computer manufacture,
> you are ensured that your card is supported by that version of the
> driver. If you download the Windows NDIS driver from another source,
> that driver may not include suppo
On Wed, Oct 27, 2010 at 5:12 PM, Scot Hetzel wrote:
> You just need to download the driver from the manufacture of your computer.
i downloaded some from acer and dell, until i found one from hp
(actually, more than one -
http://h10025.www1.hp.com/ewfrf/wc/searchResults?tmp_qt=broadcom+wireless&lc
On Thu, Oct 28, 2010 at 1:06 AM, Matthias Apitz wrote:
> El día Wednesday, October 27, 2010 a las 12:12:09PM -0500, Scot Hetzel
> escribió:
>
>> > Where did you get your bcmwl5 driver? If you downloaded it from Acer,
>> > it should work. If you downloaded it from anywhere else then this
>> > mi
El día Thursday, October 28, 2010 a las 12:07:10PM +, Paul B Mahol escribió:
> > # dhclient ndis0
> > ifconfig: ioctl (SIOCAIFADDR): Invalid argument
> > ndis0: not found
> >
> > and the same is with
> >
> > # ifconfig ndis0 192.168.2.200
> >
> > All this is with a 8-CURRENT kernel/system as o
On 10/28/10, Matthias Apitz wrote:
> El dia Wednesday, October 27, 2010 a las 12:07:51PM -0500, Scot Hetzel
> escribio:
>
>> On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa wrote:
>> > On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol wrote:
>> >> NDISulator does not support 6.X NDIS API. You will ne
El día Wednesday, October 27, 2010 a las 12:07:51PM -0500, Scot Hetzel escribió:
> On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa wrote:
> > On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol wrote:
> >> NDISulator does not support 6.X NDIS API. You will need to find bcmwl5
> >> driver. Note 5 vs 6 i
El día Wednesday, October 27, 2010 a las 12:12:09PM -0500, Scot Hetzel escribió:
> > Where did you get your bcmwl5 driver? If you downloaded it from Acer,
> > it should work. If you downloaded it from anywhere else then this
> > might be why it didn't work for you.
> >
>
> Just noticed that you
El día Wednesday, October 27, 2010 a las 05:10:32PM +, Alberto Villa
escribió:
> On Wed, Oct 27, 2010 at 5:07 PM, Scot Hetzel wrote:
> > Where did you get your bcmwl5 driver? If you downloaded it from Acer,
> > it should work. If you downloaded it from anywhere else then this
> > might be
On Wed, Oct 27, 2010 at 12:07 PM, Scot Hetzel wrote:
> On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa wrote:
>> On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol wrote:
>>> NDISulator does not support 6.X NDIS API. You will need to find bcmwl5
>>> driver. Note 5 vs 6 in driver name.
>>> Editing inf
On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa wrote:
> On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol wrote:
>> NDISulator does not support 6.X NDIS API. You will need to find bcmwl5
>> driver. Note 5 vs 6 in driver name.
>> Editing inf files will give you nothing.
>
> i've tried that driver, but
On 10/27/10, Alberto Villa wrote:
> On Tue, Oct 26, 2010 at 2:09 PM, Paul B Mahol wrote:
>>> i've tried ndis without success...
>>
>> Sharing you experience would help (if you are not on amd64).
>
> i'm on i386 at the moment, but i'll switch to amd64 as soon as i
> decide what to do (keep freebsd
On Tue, Oct 26, 2010 at 2:09 PM, Paul B Mahol wrote:
>> i've tried ndis without success...
>
> Sharing you experience would help (if you are not on amd64).
i'm on i386 at the moment, but i'll switch to amd64 as soon as i
decide what to do (keep freebsd natively or virtualize it under
windows... i
On 10/26/10, Alberto Villa wrote:
> On Mon, Oct 25, 2010 at 1:07 AM, Matthias Apitz wrote:
>> I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN
>> today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the
>> above chip is still not supported. I am wrong?
>
> i have
On Mon, Oct 25, 2010 at 1:07 AM, Matthias Apitz wrote:
> I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN
> today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the
> above chip is still not supported. I am wrong?
i have the same problem with a BCM43225. there is
25 matches
Mail list logo
