Bug 71632 - A new net-wireless/prism54 ebuild that will install the current release
|
Bug#:
71632
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: All
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: mobile@gentoo.org
|
Reported By: spr5@email.byu.edu
|
|
Component: Ebuilds
|
|
|
URL:
http://prism54.org
|
|
Summary: A new net-wireless/prism54 ebuild that will install the current release
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2004-11-17 20:14 0000
|
The current prism54 ebuild in portage installs a fairly old cvs (Feb 2004)
version of the driver. This ebuild will install the most recent release version
of the driver (v1.2). It also will check to see if you are running a kernel
with v1.2 built in, and if so will only install the firmware.
The driver can be obtained from:
http://prism54.org/pub/linux/testing/tars/2004-06/prism54-1.2.tar.bz2
I chose to number the ebuild 1.2, though this puts it as older than the current
ebuild, I was not clear what to number it as. I am providing a diff for the
ebuild, rather than the whole ebuild.
There are major improvements in this version of the driver over the current one
in portage, kismet support to name one.
Created an attachment (id=44395) [details]
New diff of ebuild to fix firmware location
This diff changes which version of sys-apps/hotplug the ebuild is dependant on
(now >=sys-apps/hotplug-20040923). Also puts the firmware in the correct place
(/lib/firmware). This puts it up to date with the current hotplug system.
please put the latest prism54 in
I'm not sure if this is the correct place to mention this, but prism54 is down,
and has been down for quite some time. So until it is back up this ebuild isn't
going to work very well.
Maybe we can get an alternative place to host the necessary files?
I have three questions about this ebuild:
1) Is it necessarily desirable not to download the drivers if they're available in the kernel? As I understand it the drivers available at prism54.org are not merged into the kernel tree for a little while, so this would prevent users getting the latest version.
2) prism54-1.2 is listed as unstable at Prism54.org, so it might be argued that prism54-1.1 would be more suitable for the portage tree?
3) In comment 5 jsado staes that "Prism54 is down." I'm not sure what he means by this, because the website http://prism54.org is working fine here now. I've never noticed any problems with the site before, but maybe I missed the outage & they only just fixed it.
Sorry to be so dramatic. As my luck would have it I completely "hit" the
outage. Looking at this page: http://prism54.org/usage/usage_200412.html you
can see that they were down for the end of December, just as I decided to get
my wireless networking set up.
From my point of view, prism54.org was never working for me, and I didn't know
about the #prism54 freenode IRC channel, so I didn't go there and ask what the
problem was. Also, google's cache of the site was from June or July, so I had
no proof that it was up any more recently than that.
In hindsight I guess it makes sense, since I didn't find any forum messages
regarding it's demise. You would think with a site like that going down for a
significant amount of time that you could find someone putting up an
alternative for those who need it.
The -firmware ebuild is in kernel now, the prism54 will go soon in favour of
the in-kernel version.
I like the solution of having a seperate ebuild for the firmware and letting
the user decide if they want a cvs snapshot version. Really gives the
flexibility that I enjoy about Gentoo. That, and it's a cleaner fix than my
ebuild. Oh, did you mean in portage rather than in kernel? If the -firmware
ebuild is in, and we get the newer driver ebuild in, I'd say this bug is taken
care of personally.
Thanks for your work on this
I was having a problem emerging the attached ebuild, such that the module never
actually got installed.
As it were, it seems that there's a typo in prism54-20041223.ebuild, line 19:
MODULE_NAMES="prsim54(net:)"
should be
MODULE_NAMES="prism54(net:)"
Even with that fix, it still doesn't install, because of an error:
>>> Install prism54-20041223 into /var/tmp/portage/prism54-20041223/image/ category net-wireless
* Installing prism54 module
install: cannot stat `prism54.ko': No such file or directory
modinfo: could not find module
/var/tmp/portage/prism54-20041223/work/prism54-cvs20041223/prism54.ko
Created an attachment (id=49069) [details]
An ebuild which seems to properly install prism54.ko
I was able to get the module installed by changing line 19 of
prism54-20041223.ebuild from:
MODULE_NAMES="prism54(net:)"
to
MODULE_NAMES="prism54(net:${S}/ksrc)"
Attached is an ebuild which has this change, and the previous change I
mentioned.
