On 7/28/06, Michael Proto <[EMAIL PROTECTED]> wrote:
Don Wilde wrote:
>> Okay, I've gotten it working with all encryption off (raw DHCP). All
the
>> nasty messages went away, so I'll see what's changed in the ifconfig
>> options.
>>
>> ifconfig_iwi0="DHCP ssid rewired channel 11 authmode shared
Don Wilde wrote:
>> Okay, I've gotten it working with all encryption off (raw DHCP). All the
>> nasty messages went away, so I'll see what's changed in the ifconfig
>> options.
>>
>> ifconfig_iwi0="DHCP ssid rewired channel 11 authmode shared weptxkey 1
>> wepmode on wepkey 0x1234567890"
>>
>> Can
On 7/27/06, Don Wilde <[EMAIL PROTECTED]> wrote:
On 7/27/06, Don Wilde <[EMAIL PROTECTED]> wrote:
>
>
> On 7/27/06, Max Laier < [EMAIL PROTECTED]> wrote:
> >
> > [Please don't top-post]
> >
> > On Thursday 27 July 2006 21:01, Don Wilde wrote:
> > > Yes, I have. I just did another CVSup, and whe
On 7/27/06, Don Wilde <[EMAIL PROTECTED]> wrote:
On 7/27/06, Max Laier <[EMAIL PROTECTED]> wrote:
>
> [Please don't top-post]
>
> On Thursday 27 July 2006 21:01, Don Wilde wrote:
> > Yes, I have. I just did another CVSup, and when I recompiled -kmod it
> did
> > indeed put a bunch of .ko files
On 7/27/06, Max Laier <[EMAIL PROTECTED]> wrote:
[Please don't top-post]
On Thursday 27 July 2006 21:01, Don Wilde wrote:
> Yes, I have. I just did another CVSup, and when I recompiled -kmod it
did
> indeed put a bunch of .ko files in /build/modules, but a) I still get a
> whole bunch of Can't
[Please don't top-post]
On Thursday 27 July 2006 21:01, Don Wilde wrote:
> Yes, I have. I just did another CVSup, and when I recompiled -kmod it did
> indeed put a bunch of .ko files in /build/modules, but a) I still get a
> whole bunch of Can't load firmware complaints, and b) it doesn't work. It
> From: "Don Wilde" <[EMAIL PROTECTED]>
> Yes, I have. I just did another CVSup, and when I recompiled -kmod it did
> indeed put a bunch of .ko files in /build/modules, but a) I still get a
> whole bunch of Can't load firmware complaints, and b) it doesn't work. It
> goes through the DISCOVER proce
Yes, I have. I just did another CVSup, and when I recompiled -kmod it did
indeed put a bunch of .ko files in /build/modules, but a) I still get a
whole bunch of Can't load firmware complaints, and b) it doesn't work. It
goes through the DISCOVER process, but doesn't get any offers it recognizes.
I
Have you tried using the firmware from iwi-firmware-kmod, rather than
iwi-firmware. I am using the former on a Thinkpad T42 and it is working ok.
-mark
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
T
*
*> >* I have "device iwi" in my kernel configuration. Should I remove it and
*> >* use a module instead? Or is this supposed to work?
*
This is from the firmware(9) support code. Add "options firmware" and you
should be fine. You will still need to load the firmware blobs as modules,
but that
On Wednesday 12 July 2006 20:07, Bartosz Fabianowski wrote:
> Since the iwi driver has been MFC'd, I cannot build a kernel any more. I
> csupped my src/sys to RELENG_6 a couple of hours ago. Everything
> compiles fine, but when linking the kernel, make barfs:
>
> linking kernel
>
> if_iwi.o(.text+0
On 7/12/06, Bartosz Fabianowski <[EMAIL PROTECTED]> wrote:
Since the iwi driver has been MFC'd, I cannot build a kernel any more. I
csupped my src/sys to RELENG_6 a couple of hours ago. Everything
compiles fine, but when linking the kernel, make barfs:
linking kernel
if_iwi.o(.text+0x29c4): In f
Since the iwi driver has been MFC'd, I cannot build a kernel any more. I
csupped my src/sys to RELENG_6 a couple of hours ago. Everything
compiles fine, but when linking the kernel, make barfs:
linking kernel
if_iwi.o(.text+0x29c4): In function `iwi_getfw':
: undefined reference to `firmware_ge
On Tuesday 11 July 2006 15:04, Michael Butler wrote:
> Max Laier wrote:
> | net/iwi-firmware-kmod, but it needs to be updated to the new
> | __FreeBSD_version
> | Right now it will tell you that you need iwi-firmware instead, which is
> | wrong.
>
> Once the updates have been merged, is this the ri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Max Laier wrote:
| net/iwi-firmware-kmod, but it needs to be updated to the new
__FreeBSD_version
| Right now it will tell you that you need iwi-firmware instead, which is
| wrong.
Once the updates have been merged, is this the right place to start
On Tuesday 11 July 2006 14:35, Mark Andrews wrote:
> > On 7/10/06, Max Laier <[EMAIL PROTECTED]> wrote:
> > > On Monday 10 July 2006 16:40, Vlad GALU wrote:
> > > > Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm
> > > > using 1.36 along with a RELENG_6 tree, since it works bet
> On 7/10/06, Max Laier <[EMAIL PROTECTED]> wrote:
> > On Monday 10 July 2006 16:40, Vlad GALU wrote:
> > > Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm
> > > using 1.36 along with a RELENG_6 tree, since it works better (read: it
> > > works). From the HEAD commit messages
On 7/10/06, Max Laier <[EMAIL PROTECTED]> wrote:
On Monday 10 July 2006 16:40, Vlad GALU wrote:
> Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm
> using 1.36 along with a RELENG_6 tree, since it works better (read: it
> works). From the HEAD commit messages I understand that
On Monday 10 July 2006 16:40, Vlad GALU wrote:
> Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm
> using 1.36 along with a RELENG_6 tree, since it works better (read: it
> works). From the HEAD commit messages I understand that some MFCs
> would've been in order by now. Are the
Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm
using 1.36 along with a RELENG_6 tree, since it works better (read: it
works). From the HEAD commit messages I understand that some MFCs
would've been in order by now. Are there any show-stoppers that push
that schedule ahead ?
-
20 matches
Mail list logo
