The prism54 ebuild places the isl3890 firmware in /usr/lib/hotplug/firmware; however, hotplug-20040920 and and later looks for firmware in /lib/firmware. Verified workaround: symlink the firmware into /lib/firmware for now. Reference bug #64869 for more info on the hotplug change. Reproducible: Always Steps to Reproduce: 1. emerge prism54 2. emerge =hotplug-20040920 3. modprobe prism54 4. ifconfig the wireless interface 5. check dmesg Actual Results: ifconfig fails with error. dmesg shows error loading firmware. From dmesg: ====================================== eth1: islpci_open() eth1: resetting device... eth1: uploading firmware... prism54: request_firmware() failed for 'isl3890' eth1: could not upload firmware ('isl3890') Expected Results: ifconfig should complete successfully. Portage 2.0.51_rc9 (default-x86-2004.2, gcc-3.4.2, glibc-2.3.4.20041006-r0, 2.6.8-gentoo-r8 i686) ================================================================= System uname: 2.6.8-gentoo-r8 i686 AMD Athlon(tm) processor Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-tbird -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-tbird -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache distlocks fixpackages sandbox userpriv usersandbox" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://open-systems.ufl.edu/mirrors/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi alsa apm arts avi berkdb bitmap-fonts cdr crypt cups encode f77 famflac foomaticdb freetds gd gdbm gif gnome gpm gtk gtk2 hardenedphp imlib innodbjpeg kde libg++ libwww mad maildir mikmod mmx motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png pnp ppds python qt quicktime readline sambascanner sdl slang spell ssl svga tcltk tcpd tiff truetype unicode usb videos wifi x86 xinerama xml xml2 xmms xosd xprint xv zlib"
I'm in fact probably going to remove that ebuild soon. If you need to use a prism54 driven card, I suggest using a 2.6 kernel, as the driver is included in those kernels. The ebuild for prism54 is very old at this point.
*** Bug 70151 has been marked as a duplicate of this bug. ***
Afaik the firmware is distributed seperately from the driver, so would it really be a good idea to remove the ebuild completely? einfo's about building the module in the kernel and installing the firmware would still justify an ebuild imho
This bug also affects ipw2100, which also installs its firmware to /usr/lib/hotplug/firmware. The same fix (i.e. symlinking /lib/firmware) fixed it for me.
This has long been fixed in the ipw2100.
What is the status of this bug report? Do we need to remove net-wireless/prism54 and add a net-wireless/prism54-firmware ebuild instead? At the moment prism54.org is unreachable.
Created attachment 47217 [details] prism54-firmware-1.ebuild ebuild based on net-wireless/prism54. I'm not sure about the DEPEND value..
Created attachment 47219 [details] prism54-firmware-1.ebuild removed unnecessary line in ebuild.
I think it is the best way to remove the firmware from net-wireless/prism54 and add RDEPEND="net-wireless/prism54-firmware" to that ebuild. this avoids that both packages install the firmware.
Created attachment 47225 [details] prism54-firmware-1.ebuild change RDEPEND to hotplug version, which uses /lib/firmware/
oh sorry, I did not see that one before, prism54-firmware is now in the tree, thank you for writing an ebuild for it.
The net-wireless/prism54 ebuild, which this bug is about, still installs firmware to /usr/lib/hotplug/firmware. Reopening bug.
net-wireless/prism54 should just install no firmware and have RDEPEND="net-wireless/prism54-firmware" in it's ebuild? Markus
Correct.
The same problem affects the atmel driver in the kernel. Firmware is saved in /usr/lib/hotplug/firmware, while the hotplug scripts search for it in /lib/firmware. I had hard time figuring out what is going on without being able to check the forums :). My workaround is to symlink from /lib/firmware, and it works. Should I file a new bug or is it enough to leave it here? I am runnning a stable x86 system: Kernel : gentoo-dev-sources-2.6.10-r6 hotplug : 20040923 udev : 045 baselayout: 1.9.4-r6
in atmel-firmware I use /lib/firmware and the old prism54 is out of portage, what atmel driver do you use?
This is actually a good question. I verified that I do not have atmel-firmware emerged but I do have loads of firmware in /usr/lib/hotplug/firmware. It may well be that I got it myself and simply forgot about it... In such case I am sorry to spam the bug. Can it be that the kernel has firmware included nowadays?
