This is the bug report for getting all the new versions of the IPW2100 into portage. Reproducible: Always Steps to Reproduce: 1. emerge ipw2100 2. old version of IPW2100 installed Actual Results: Old version of IPW2100 installed Expected Results: Latest version of IPW2100 installed
Created attachment 31137 [details] IPW2100 0.43 Ebuild All I did was copy over the 0.41 ebuild to the 0.43 ebuild. In order to install this you need to do all in one line FEATURES="-sandbox" emerge ipw2100
I am trying to create the 0.44 ebuild but I am having some troubles doing it. It uses a new firmware(version 1.1) found only at http://ipw2100.sourceforge.net/firmware.php?agree=1&f=ipw2100-fw-1.1.zip the problem is when it goes to get the firmware it cannt get it. The other problem I have is that I can not emerge this without doing FEATURES="-sandbox" emerge ipw2100 as shown in the ebuild for the 0.43 driver. How can I get around this? Thanks
I along with jarealist on the <a href = http://forums.gentoo.org/viewtopic.php?t=172387&highlight=ipw2100>fourms</a> have created a quick and dirty hack. Though after reading through the ipw2100 README agien I improved on it. Here are the set by set instructions 1. dl the ipw2100 0.44 ebuild above 2. dl the firmware from ipw2100.sf.net extract and rezip it as a tgz with only LICENSE and ipw2100-1.1.fw in it. 3. place the tgz in /path/to/portage/distfiles 4. do ebuild ipw2100-0.41.ebuild digest && ebuild ipw2100-0.41.ebuild fetch 5. do FEATURES="-sandbox" emerge ipw2100 6. copy all the the files from the orginal firmware zip file into /usr/lib/hotplug/firmware this will give you everything the driver currently supports It would be nice if this ebuild was all automactic so it fetchs and emerges everything it self w/o all this quick and dirty hacks. If someone could help please post any patches.
Created attachment 31306 [details] IPW2100 0.44 Here are the step by step instructions 1. this ebuild 2. dl the firmware from ipw2100.sf.net extract and rezip it as a tgz with only LICENSE and ipw2100-1.1.fw in it. 3. place the tgz in /path/to/portage/distfiles 4. do ebuild ipw2100-0.41.ebuild digest && ebuild ipw2100-0.41.ebuild fetch 5. do FEATURES="-sandbox" emerge ipw2100 6. copy all the the files from the orginal firmware zip file into /usr/lib/hotplug/firmware this will give you everything the driver currently supports
Created attachment 31480 [details] ipw2100 0.44 ebuild (slightly more automatic) Revised instructions 1. dl this ebuild and copy to your local portage directory 2. dl the firmware from ipw2100.sf.net extract and rezip all files in it as a ipw2100-fw-1.1.tgz 3. place the tgz in /path/to/portage/distfiles 4. do ebuild ipw2100-0.44.ebuild digest && ebuild ipw2100-0.44.ebuild fetch 5. do FEATURES="-sandbox" emerge ipw2100 *Note this version of the ebuild automatically installs all the files of the firmware. **Note somehow the 1.0 firware tgz file was placed on the gentoo mirrors, any ideas of how to make this happen for the 1.1 firmware file?
Scott I just tested the ebuild and it works great. Thanks!
Created attachment 31553 [details] ipw2100-0.44 experimental kmod version here is a second version of the 0.44 ebuild. It uses the kmod eclass. This should eventually allow this ebuild to not require turning off the sandbox. You can see more info about kmod here: bug #32737 bug #40933 http://dev.gentoo.org/~latexer/files/koutput/ http://www.gentoo.org/doc/en/2.6-koutput.xml http://www.gentoo.org/doc/en/2.6-koutput-user.xml But be careful, as I described in bug #51213, you can run into trouble if you follow the preferred directions. The main problem is that ipw2100 requires hostap-driver. The hostap-driver uses the pcmcia.eclass. These 2 dependencies have not been updated in portage to support kmod yet. So if you follow the preferred directions and try the 'koutput' method the hostap-driver won't build. To make it work you need to at least get the pcmcia.eclass and hostap-driver-0.1.3-r1 from: http://dev.gentoo.org/~latexer/files/koutput/
Hey all, Just waiting on the new tarball with the firmware images to propogate to gentoo mirrors before commiting a 0.44 ebuild. To answer a few questions: To get something on our mirrors devs put the files in this one spot on the dev boxes, and it eventually propogates. This is done with the firmare files just because otherwise you have to go through the licence hoops, etc to get it. The license for the firmware fortunately is nice enough to let us do this. As for the kmod stuff, I've just finally finished the whole "graduation" thing, so i'll be dusting off the new koutput/kmod things starting this week. Stupid meatspace causing delays in the *important* things in life. Thanks scott for the updated ebuild using kmod, i'll check it out, and hopefully get it into an updated kmod overlay soon.
Okay, the firmware has started showing up on a few mirrors. I just commited the bump. Please test and report back success/failure so I can eventually mark this closed. If the firmware isn't found, please wait a bit, and try again later or on a different mirror.
Peter, thank you for getting the firmware on the servers but that was only part of the problem. The other part is to get the latest ebuild of the ipw2100 driver(currently 0.44) into portage. It would be great if you could get the new ebuild into portage.
Oh shoot sorry Peter I guess im doing to much at once I guess I read over the part about the 0.44 ebuild going into portage. heh talking to my gf doing homework and programming all at once causes so mistakes. Terribly sorry for the mistake. Thanks agien for getting this into portage. Lee
