portupgraded iwi-firmware to iwi-firmware-2.4_7 earlier today, but rebooting machine resulted in loss of wifi functionality. iwicontrol no longer worked. Here are the details of installed (built-in) hardware: iwi0@pci2:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class = network Attempts to resinstall results in the following: - Attempts to use make install clean: # make install clean ===> iwi-firmware-2.4_7 is configured with iwi(4) support which you don't need. *** Error code 1 Stop in /usr/ports/net/iwi-firmware. # Attempts to use pkg_add: - # pkg_add -r iwi-firmware Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/iwi-firmware.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/iwi-firmware.tbz' by URL # Fix: Don't know How-To-Repeat: cvsup ports tree portupgrade from iwi-firmware-2.4_2 to 2.4_7 reboot <Lose wifi / iwicontrol cmd functionality> Attempt to restore by either make install clean or pkg_add
Responsible Changed From-To: freebsd-ports-bugs->flz Over to maintainer
State Changed From-To: open->closed Duplicate PR, use make rmconfig && make config and unselect the DRIVER option.
Hello, On Thu, 01 Jun 2006, Florent Thoumie wrote: > Synopsis: portupgrade of iwi-firmware breaks installed firmware. Now make install fails with iwi-firmware-2.4_7 is configured with iwi(4) support which you don't need. > > State-Changed-From-To: open->closed > State-Changed-By: flz > State-Changed-When: Thu Jun 1 18:22:52 UTC 2006 > State-Changed-Why: > Duplicate PR, use make rmconfig && make config and unselect the DRIVER > option. Thanks for the response. This is almost the same procedure you provided last time which resulted in the firmware being blasted off the machine, hence my submitting this PR. Literally as soon as the operation was completed. I was no longer able to use iwicontrol - kept getting command not found. What was not provided before, I believe is the step to "make rmconfig". The only way to recover network access was to reconfigure the wired lan. I then tried to deinstall / reinstall the port, hoping to then get 2.4.7 that way, but found that running make deinstall failed with the msg that iwi-firmware-2.4.2 was not installed. Is this what your procedure is intended to do? Anyway, even attempting to pkg-add iwi-firmware only then resulted in installing the same iwi-firmware-2.4.2 (this is after a fresh cvsup of the ports tree) that I originally, and still have as of this time. So can I (humbly) ask that you (at least in the pkg-mesg?) provide the exact procedure / steps that one needs to use in order to update from iwi-firmware-2.4.2 to iwi-firmware-2.4.7, please? Regards, Stacey > > http://www.freebsd.org/cgi/query-pr.cgi?pr=98110
On Thu, 2006-06-01 at 19:52 +0100, Stacey Roberts wrote: > Hello, > > On Thu, 01 Jun 2006, Florent Thoumie wrote: > > > Synopsis: portupgrade of iwi-firmware breaks installed firmware. Now make install fails with iwi-firmware-2.4_7 is configured with iwi(4) support which you don't need. > > > > State-Changed-From-To: open->closed > > State-Changed-By: flz > > State-Changed-When: Thu Jun 1 18:22:52 UTC 2006 > > State-Changed-Why: > > Duplicate PR, use make rmconfig && make config and unselect the DRIVER > > option. > > Thanks for the response. > > This is almost the same procedure you provided last time which resulted in the firmware > being blasted off the machine, hence my submitting this PR. Literally as soon as the > operation was completed. I was no longer able to use iwicontrol - kept getting command > not found. > > What was not provided before, I believe is the step to "make rmconfig". > > The only way to recover network access was to reconfigure the wired lan. I then tried to > deinstall / reinstall the port, hoping to then get 2.4.7 that way, but found that > running make deinstall failed with the msg that iwi-firmware-2.4.2 was not installed. Is > this what your procedure is intended to do? iwicontrol can't be found because it's no longer necessary, the firmware should be loaded from the filesystem (/boot) automatically. > Anyway, even attempting to pkg-add iwi-firmware only then resulted in installing the > same iwi-firmware-2.4.2 (this is after a fresh cvsup of the ports tree) that I > originally, and still have as of this time. pkg_add doesn't use the ports tree. If you do pkg_add -r, it will try to fetch a package, otherwise it will look for the given package name in the current directory. > So can I (humbly) ask that you (at least in the pkg-mesg?) provide the exact procedure / > steps that one needs to use in order to update from iwi-firmware-2.4.2 to > iwi-firmware-2.4.7, please? The upgrade from 2.4_2 to 2.4_7 has nothing to do with your problem. I think you upgraded from FreeBSD 5.x to FreeBSD 6.x which caused your problem (port configured on 5.x and reinstalled on 6.x). If it's not the case, I'm quite confused by the error you're reporting to me. -- Florent Thoumie flz@FreeBSD.org FreeBSD Committer
Hello, On Thu, 01 Jun 2006, Florent Thoumie wrote: > On Thu, 2006-06-01 at 19:52 +0100, Stacey Roberts wrote: > > Hello, > > > > On Thu, 01 Jun 2006, Florent Thoumie wrote: > > > > > Synopsis: portupgrade of iwi-firmware breaks installed firmware. Now make install fails with iwi-firmware-2.4_7 is configured with iwi(4) support which you don't need. > > > > > > State-Changed-From-To: open->closed > > > State-Changed-By: flz > > > State-Changed-When: Thu Jun 1 18:22:52 UTC 2006 > > > State-Changed-Why: > > > Duplicate PR, use make rmconfig && make config and unselect the DRIVER > > > option. > > > > Thanks for the response. > > > > This is almost the same procedure you provided last time which resulted in the firmware > > being blasted off the machine, hence my submitting this PR. Literally as soon as the > > operation was completed. I was no longer able to use iwicontrol - kept getting command > > not found. > > > > What was not provided before, I believe is the step to "make rmconfig". > > > > The only way to recover network access was to reconfigure the wired lan. I then tried to > > deinstall / reinstall the port, hoping to then get 2.4.7 that way, but found that > > running make deinstall failed with the msg that iwi-firmware-2.4.2 was not installed. Is > > this what your procedure is intended to do? > > iwicontrol can't be found because it's no longer necessary, the firmware > should be loaded from the filesystem (/boot) automatically. Err., maybe I should say this again? I literally no longer had a functioning wireless card after following the advice you provided. As I said, the only way I could get any network access was to configure the LAN card. Also, on reboot, there was the message "Please install firmware" that flashed by on the screen during boot up. So I don't quite understand what it means when you say "iwicontrol can't be found because it's no longer necessary, the firmware should be loaded from the filesystem (/boot) automatically." Sorry if I'm missing something really obvious, here. > > > Anyway, even attempting to pkg-add iwi-firmware only then resulted in installing the > > same iwi-firmware-2.4.2 (this is after a fresh cvsup of the ports tree) that I > > originally, and still have as of this time. > > pkg_add doesn't use the ports tree. If you do pkg_add -r, it will try to > fetch a package, otherwise it will look for the given package name in > the current directory. > > > So can I (humbly) ask that you (at least in the pkg-mesg?) provide the exact procedure / > > steps that one needs to use in order to update from iwi-firmware-2.4.2 to > > iwi-firmware-2.4.7, please? > > The upgrade from 2.4_2 to 2.4_7 has nothing to do with your problem. I > think you upgraded from FreeBSD 5.x to FreeBSD 6.x which caused your > problem (port configured on 5.x and reinstalled on 6.x). If it's not the > case, I'm quite confused by the error you're reporting to me. Well., that's two of us - This notebook was originally installed with FreeBSD-6.1, then updated to Stable only a couple of days before. That aside, you've not actually indicated what *is* the procedure required to portupgrade to iwi-firmware-2.4.7. Or, is this a separate issue for which I need to submit another question for? Please don't take this the wrong way, I'm only interested in finding out how this is *supposed* to be done here. If you recall, it was my wanting to portupgrade to iwi-firmware-2.4.7 that was the reason for my first post (PR98086) on this, to begin with. Regards, Stacey > -- > Florent Thoumie > flz@FreeBSD.org > FreeBSD Committer
On Thu, 2006-06-01 at 20:45 +0100, Stacey Roberts wrote: > Hello, > > On Thu, 01 Jun 2006, Florent Thoumie wrote: > > > On Thu, 2006-06-01 at 19:52 +0100, Stacey Roberts wrote: > > > Hello, > > > > > > On Thu, 01 Jun 2006, Florent Thoumie wrote: > > > > > > > Synopsis: portupgrade of iwi-firmware breaks installed firmware. Now make install fails with iwi-firmware-2.4_7 is configured with iwi(4) support which you don't need. > > > > > > > > State-Changed-From-To: open->closed > > > > State-Changed-By: flz > > > > State-Changed-When: Thu Jun 1 18:22:52 UTC 2006 > > > > State-Changed-Why: > > > > Duplicate PR, use make rmconfig && make config and unselect the DRIVER > > > > option. > > > > > > Thanks for the response. > > > > > > This is almost the same procedure you provided last time which resulted in the firmware > > > being blasted off the machine, hence my submitting this PR. Literally as soon as the > > > operation was completed. I was no longer able to use iwicontrol - kept getting command > > > not found. > > > > > > What was not provided before, I believe is the step to "make rmconfig". > > > > > > The only way to recover network access was to reconfigure the wired lan. I then tried to > > > deinstall / reinstall the port, hoping to then get 2.4.7 that way, but found that > > > running make deinstall failed with the msg that iwi-firmware-2.4.2 was not installed. Is > > > this what your procedure is intended to do? > > > > iwicontrol can't be found because it's no longer necessary, the firmware > > should be loaded from the filesystem (/boot) automatically. > > Err., maybe I should say this again? I literally no longer had a functioning wireless > card after following the advice you provided. As I said, the only way I could get any > network access was to configure the LAN card. > > Also, on reboot, there was the message "Please install firmware" that flashed by on the > screen during boot up. So I don't quite understand what it means when you say > "iwicontrol can't be found because it's no longer necessary, the firmware > should be loaded from the filesystem (/boot) automatically." > > Sorry if I'm missing something really obvious, here. > > > > > > Anyway, even attempting to pkg-add iwi-firmware only then resulted in installing the > > > same iwi-firmware-2.4.2 (this is after a fresh cvsup of the ports tree) that I > > > originally, and still have as of this time. > > > > pkg_add doesn't use the ports tree. If you do pkg_add -r, it will try to > > fetch a package, otherwise it will look for the given package name in > > the current directory. > > > > > So can I (humbly) ask that you (at least in the pkg-mesg?) provide the exact procedure / > > > steps that one needs to use in order to update from iwi-firmware-2.4.2 to > > > iwi-firmware-2.4.7, please? > > > > The upgrade from 2.4_2 to 2.4_7 has nothing to do with your problem. I > > think you upgraded from FreeBSD 5.x to FreeBSD 6.x which caused your > > problem (port configured on 5.x and reinstalled on 6.x). If it's not the > > case, I'm quite confused by the error you're reporting to me. > > Well., that's two of us - This notebook was originally installed with FreeBSD-6.1, then > updated to Stable only a couple of days before. > > That aside, you've not actually indicated what *is* the procedure required to > portupgrade to iwi-firmware-2.4.7. Or, is this a separate issue for which I need to > submit another question for? > > Please don't take this the wrong way, I'm only interested in finding out how this is > *supposed* to be done here. If you recall, it was my wanting to portupgrade to > iwi-firmware-2.4.7 that was the reason for my first post (PR98086) on this, to begin > with. If you finally succeeded in installing iwi-firmware by unselecting MODULE and CONTROL options (make rmconfig && make config), try `pkg_info -Lx iwi-firmware | grep /boot`. If it shows any .fw files installed then you should be done. -- Florent Thoumie flz@FreeBSD.org FreeBSD Committer
Hello, On Thu, 01 Jun 2006, Florent Thoumie wrote: > On Thu, 2006-06-01 at 20:45 +0100, Stacey Roberts wrote: > > Hello, > > > > On Thu, 01 Jun 2006, Florent Thoumie wrote: > > > > > On Thu, 2006-06-01 at 19:52 +0100, Stacey Roberts wrote: > > > > Hello, > > > > > > > > On Thu, 01 Jun 2006, Florent Thoumie wrote: > > > > > > > > > Synopsis: portupgrade of iwi-firmware breaks installed firmware. Now make install fails with iwi-firmware-2.4_7 is configured with iwi(4) support which you don't need. > > > > > > > > > > State-Changed-From-To: open->closed > > > > > State-Changed-By: flz > > > > > State-Changed-When: Thu Jun 1 18:22:52 UTC 2006 > > > > > State-Changed-Why: > > > > > Duplicate PR, use make rmconfig && make config and unselect the DRIVER > > > > > option. > > > > > > > > Thanks for the response. > > > > > > > > This is almost the same procedure you provided last time which resulted in the firmware > > > > being blasted off the machine, hence my submitting this PR. Literally as soon as the > > > > operation was completed. I was no longer able to use iwicontrol - kept getting command > > > > not found. > > > > > > > > What was not provided before, I believe is the step to "make rmconfig". > > > > > > > > The only way to recover network access was to reconfigure the wired lan. I then tried to > > > > deinstall / reinstall the port, hoping to then get 2.4.7 that way, but found that > > > > running make deinstall failed with the msg that iwi-firmware-2.4.2 was not installed. Is > > > > this what your procedure is intended to do? > > > > > > iwicontrol can't be found because it's no longer necessary, the firmware > > > should be loaded from the filesystem (/boot) automatically. > > > > Err., maybe I should say this again? I literally no longer had a functioning wireless > > card after following the advice you provided. As I said, the only way I could get any > > network access was to configure the LAN card. > > > > Also, on reboot, there was the message "Please install firmware" that flashed by on the > > screen during boot up. So I don't quite understand what it means when you say > > "iwicontrol can't be found because it's no longer necessary, the firmware > > should be loaded from the filesystem (/boot) automatically." > > > > Sorry if I'm missing something really obvious, here. > > > > > > > > > Anyway, even attempting to pkg-add iwi-firmware only then resulted in installing the > > > > same iwi-firmware-2.4.2 (this is after a fresh cvsup of the ports tree) that I > > > > originally, and still have as of this time. > > > > > > pkg_add doesn't use the ports tree. If you do pkg_add -r, it will try to > > > fetch a package, otherwise it will look for the given package name in > > > the current directory. > > > > > > > So can I (humbly) ask that you (at least in the pkg-mesg?) provide the exact procedure / > > > > steps that one needs to use in order to update from iwi-firmware-2.4.2 to > > > > iwi-firmware-2.4.7, please? > > > > > > The upgrade from 2.4_2 to 2.4_7 has nothing to do with your problem. I > > > think you upgraded from FreeBSD 5.x to FreeBSD 6.x which caused your > > > problem (port configured on 5.x and reinstalled on 6.x). If it's not the > > > case, I'm quite confused by the error you're reporting to me. > > > > Well., that's two of us - This notebook was originally installed with FreeBSD-6.1, then > > updated to Stable only a couple of days before. > > > > That aside, you've not actually indicated what *is* the procedure required to > > portupgrade to iwi-firmware-2.4.7. Or, is this a separate issue for which I need to > > submit another question for? > > > > Please don't take this the wrong way, I'm only interested in finding out how this is > > *supposed* to be done here. If you recall, it was my wanting to portupgrade to > > iwi-firmware-2.4.7 that was the reason for my first post (PR98086) on this, to begin > > with. > > If you finally succeeded in installing iwi-firmware by unselecting > MODULE and CONTROL options (make rmconfig && make config), try `pkg_info > -Lx iwi-firmware | grep /boot`. If it shows any .fw files installed then > you should be done. > Thanks for the response. I'm really sorry if I did not make this clear in any of my previous posts today, but I am *exactly* where I was immediately before encountering the issues that made me submit PR98086 - I've currently got the original iwi-firmware-2.4.2 port installed. I have just today, updated my ports tree, and pkg_version tells me that there is a new version available (iwi-firmware-2.4.7) to upgrade to. Can I simply use "portupgrade -R iwi-firmware-2.4.2"? If this is *not* the way to upgrade from iwi-firmware-2.4.2 to iwi-firmware-2.4.7, then can you let me know what that procedure is, please? From the responses you've provided to me since filing that PR, all that I've been told, is as of today: - cd /usr/ports/net/iwi-firmware make rmconfig && make config Are you actually telling me that the above cmd is *the* way to upgrade from iwi-firmware-2.4.2 to iwi-firmware-2.4.7? Thanks, Regards, Stacey > -- > Florent Thoumie > flz@FreeBSD.org > FreeBSD Committer