Re: iwi(4) in RELENG_6
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 anybody spot it off the top? By removing the hardwired 'channel 11 authmode shared' from both sides, I have been able to connect successfully with WEP authentication. Just a note (and someone please correct me if I'm wrong), but setting the channel in the client's ifconfig statement is invalid in BSS mode-- it will pull the appropriate channel from the AP during the association. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 weptxkey 1 wepmode on wepkey 0x1234567890 Can anybody spot it off the top? By removing the hardwired 'channel 11 authmode shared' from both sides, I have been able to connect successfully with WEP authentication. Just a note (and someone please correct me if I'm wrong), but setting the channel in the client's ifconfig statement is invalid in BSS mode-- it will pull the appropriate channel from the AP during the association. -Proto It used to work that way, so somebody must have updated the coding. Thanks, Michael, for the input. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: 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 To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 process, but doesn't get any offers it recognizes. I've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. That is, indeed, a drag. b) is bad. We are using different hardware, which I guess could be a factor. When I can boot this thing under FreeBSD (work intervenes at present) I'll post what iwi-firmware-kmod put where. -mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
[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 goes through the DISCOVER process, but doesn't get any offers it recognizes. I've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. Just to get the facts straight and assembled in one place: You are running a somewhat recent RELENG_6, have net/iwi-firmware-kmod installed and device iwi and options firmware built into your kernel? When do you get the Can't load firmware messages? What does kldstat [-v] say before and after that point? Can you try kldload iwi_bss before and see if that gets you up and running? On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: 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. -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpi7UJEn3h0i.pgp Description: PGP signature
Re: iwi(4) in RELENG_6
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 load firmware complaints, and b) it doesn't work. It goes through the DISCOVER process, but doesn't get any offers it recognizes. I've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. Just to get the facts straight and assembled in one place: You are running a somewhat recent RELENG_6, have net/iwi-firmware-kmod installed and device iwi and options firmware built into your kernel? When do you get the Can't load firmware messages? What does kldstat [-v] say before and after that point? Can you try kldload iwi_bss before and see if that gets you up and running? On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: 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. Hi, Max - I did so, and it appears that the module is already loaded. It seems that the problems occur because my system is also trying to load the old firmware somehow. A more disturbing issue is that my rc.conf seems to be being read twice. I see the kldstat reports (with my echo commands) being printed four times instead of the two I'm requesting. Attached are my rc.conf and dmesg. rc.cnf Description: Binary data dmesg.iwi Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 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've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. Just to get the facts straight and assembled in one place: You are running a somewhat recent RELENG_6, have net/iwi-firmware-kmod installed and device iwi and options firmware built into your kernel? When do you get the Can't load firmware messages? What does kldstat [-v] say before and after that point? Can you try kldload iwi_bss before and see if that gets you up and running? On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: 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. Hi, Max - I did so, and it appears that the module is already loaded. It seems that the problems occur because my system is also trying to load the old firmware somehow. A more disturbing issue is that my rc.conf seems to be being read twice. I see the kldstat reports (with my echo commands) being printed four times instead of the two I'm requesting. Attached are my rc.conf and dmesg. 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 anybody spot it off the top? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 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've tried this both with an open DHCP and also with my parameters wired in. Hardware notes: Dell 6100 Inspiron with 2200G iwi. I have heard from another gent who has a 2200G pci card and is having the same problem with STABLE. This all was working two weeks ago. Just to get the facts straight and assembled in one place: You are running a somewhat recent RELENG_6, have net/iwi-firmware-kmod installed and device iwi and options firmware built into your kernel? When do you get the Can't load firmware messages? What does kldstat [-v] say before and after that point? Can you try kldload iwi_bss before and see if that gets you up and running? On 7/27/06, Mark Willson [EMAIL PROTECTED] wrote: 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. Hi, Max - I did so, and it appears that the module is already loaded. It seems that the problems occur because my system is also trying to load the old firmware somehow. A more disturbing issue is that my rc.conf seems to be being read twice. I see the kldstat reports (with my echo commands) being printed four times instead of the two I'm requesting. Attached are my rc.conf and dmesg. 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 anybody spot it off the top? By removing the hardwired 'channel 11 authmode shared' from both sides, I have been able to connect successfully with WEP authentication. Thanks for all your suggestions, guys! :D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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_get' if_iwi.o(.text+0x29d3): In function `iwi_getfw': : undefined reference to `firmware_get' if_iwi.o(.text+0x2a1d): In function `iwi_put_fw': : undefined reference to `firmware_put' if_iwi.o(.text+0x49a5): In function `iwi_init_locked': : undefined reference to `firmware_get' I have device iwi in my kernel configuration. Should I remove it and use a module instead? Or is this supposed to work? - Bartosz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 function `iwi_getfw': : undefined reference to `firmware_get' if_iwi.o(.text+0x29d3): In function `iwi_getfw': : undefined reference to `firmware_get' if_iwi.o(.text+0x2a1d): In function `iwi_put_fw': : undefined reference to `firmware_put' if_iwi.o(.text+0x49a5): In function `iwi_init_locked': : undefined reference to `firmware_get' I have device iwi in my kernel configuration. Should I remove it and use a module instead? Or is this supposed to work? You need to add device firmware to your kernel configuration file as well. This driver uses the new firmware(9) framework. - Bartosz -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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+0x29c4): In function `iwi_getfw': : undefined reference to `firmware_get' if_iwi.o(.text+0x29d3): In function `iwi_getfw': : undefined reference to `firmware_get' if_iwi.o(.text+0x2a1d): In function `iwi_put_fw': : undefined reference to `firmware_put' if_iwi.o(.text+0x49a5): In function `iwi_init_locked': : undefined reference to `firmware_get' 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's another story. -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpM3oBmnzNnn.pgp Description: PGP signature
Re: iwi(4) in RELENG_6
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 some MFCs would've been in order by now. Are there any show-stoppers that push that schedule ahead ? no. The only thing that bugs me a bit, is that the change will break POLA for people using the old version. I have yet to hear from somebody using that successfully, though. I will get on MFCing it later today. Thanks, Max! Which of the iwi ports should be used now on RELENG6 now that this has been MFC'd. net/iwi-firmware-kmod or net/iwi-firmware? -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 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 ? no. The only thing that bugs me a bit, is that the change will break POLA for people using the old version. I have yet to hear from somebody using that successfully, though. I will get on MFCing it later today. Thanks, Max! Which of the iwi ports should be used now on RELENG6 now that this has been MFC'd. net/iwi-firmware-kmod or net/iwi-firmware? 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. -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpfs4vIylCCL.pgp Description: PGP signature
Re: iwi(4) in RELENG_6
-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 with adding 3945ABG? I have u-code but haven't had time enough to look at the driver to date .. I'd really like to get my (dual-core) T-2400 Toshiba on the air ;-) Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEs6HhRaBvd7/LHU4RAjSbAKDH9RLecpVurq99qUVY51/0V3t3SwCg5RHO Ctmsu5sZ1ZqdweeCb8eJcJE= =YwOf -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 right place to start with adding 3945ABG? I have u-code but haven't had time enough to look at the driver to date .. I'd really like to get my (dual-core) T-2400 Toshiba on the air ;-) The 3945ABG is a completely different kind of animal and needs a separate driver. There is one in OpenBSD called wpi(4), but I'm unaware of the state of that undertaking. From what I hear, ndis doesn't work for those cards either, but it might make sense to confirm that and possibly look into fixing ndis-support as a first line of support. I don't have 3945ABG hardware. -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpJgIckOKMW3.pgp Description: PGP signature
iwi(4) in RELENG_6
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 ? -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi(4) in RELENG_6
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 there any show-stoppers that push that schedule ahead ? no. The only thing that bugs me a bit, is that the change will break POLA for people using the old version. I have yet to hear from somebody using that successfully, though. I will get on MFCing it later today. -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgp3dTcOo1C4r.pgp Description: PGP signature
Re: iwi(4) in RELENG_6
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 some MFCs would've been in order by now. Are there any show-stoppers that push that schedule ahead ? no. The only thing that bugs me a bit, is that the change will break POLA for people using the old version. I have yet to hear from somebody using that successfully, though. I will get on MFCing it later today. Thanks, Max! -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
