On Wed, 2005-11-02 at 17:02 -0500, Brian M. Sperlongano wrote:
> Find reveals that firmware.agent is located as such below.
>
> localhost / # find . -name firmware.agent
> ./usr/portage/sys-apps/hotplug/files/firmware.agent
>
That location looks strange to me. The /usr/portage directory is the
build management directory on a gentoo system. I would have expected
the script to be put in /usr/lib/, or /usr/sbin/ by the ebuild process
that installed it.
I'm still running a 2.4 with an older ivtv (if it runs, don't fix it)
on my gentoo mythbox, so I don't have a hotplug install to compare.
Jon
> The contents of firmware.agent is included below.
>
> The following line is in firmware.agent:
>
> FIRMWARE_DIR=/usr/lib/hotplug/firmware
>
> A check of that directory shows:
>
> localhost / # cd /usr/lib/hotplug/firmware/
> localhost firmware # ls -l
> total 796
> -r--r--r-- 1 root root 262144 Oct 23 00:55 HcwFalcn.rom
> -r--r--r-- 1 root root 14264 Oct 23 00:55 HcwMakoA.ROM
> -rw-r--r-- 1 root root 262144 Oct 23 00:55 ivtv-fw-dec.bin
> -rw-r--r-- 1 root root 262144 Oct 23 00:55 ivtv-fw-enc.bin
> localhost firmware #
>
> So it seems like it otherwise should work, since the firmware files
> are in the right place, but it complains that it can't load the
> firmware through hotplug in the dmesg. Also, when running modprobe
> ivtv, it takes a substantially long time, 30-45 seconds, before
> returning. I'm not sure what the the tveeprom error message means,
> but perhaps it's related?
>
> -Brian
>
> ===BEGIN FIRMWARE.AGENT==
>
> #!/bin/sh
> #
> # Firmware-specific hotplug policy agent.
> #
> # Kernel firmware hotplug params include:
> #
> # ACTION=%s [add or remove]
> # DEVPATH=%s [in 2.5 kernels, /sys/$DEVPATH]
> # FIRMWARE=%s
> #
> # HISTORY:
> #
> # 24-Jul-2003 Initial version of "new" hotplug agent.
> #
> # $Id: firmware.agent,v 1.1 2003/11/13 04:30:20 drobbins Exp $
> #
>
> cd /etc/hotplug
> . hotplug.functions
> # DEBUG=yes export DEBUG
>
> # directory of the firmware files
> FIRMWARE_DIR=/usr/lib/hotplug/firmware
>
> # mountpoint of sysfs
> SYSFS=$(sed -n 's/^.* \([^ ]*\) sysfs .*$/\1/p' /proc/mounts)
>
> # use /proc for 2.4 kernels
> if [ "$SYSFS" = "" ]; then
> SYSFS=/proc
> fi
>
> #
> # What to do with this firmware hotplug event?
> #
> case "$ACTION" in
>
> add)
> if [ ! -e $SYSFS/$DEVPATH/loading ]; then
> sleep 1
> fi
>
> if [ -f $FIRMWARE_DIR/$FIRMWARE ]; then
> echo 1 > $SYSFS/$DEVPATH/loading
> cp $FIRMWARE_DIR/$FIRMWARE $SYSFS/$DEVPATH/data
> echo 0 > $SYSFS/$DEVPATH/loading
> else
> echo -1 > $SYSFS/$DEVPATH/loading
> fi
>
> ;;
>
> remove)
> ;;
>
> *)
> mesg "Firmware '$ACTION' event not supported"
> exit 1
> ;;
>
> esac
>
> ==END FIRMWARE.AGENT==
>
>
> On 11/2/05, Tyler Trafford <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 01, 2005 at 09:52:39PM -0500, Brian M. Sperlongano
> wrote:
> > After several days of trying, I am totally and utterly
> unable to figure out
> > how to work the new hotplug-based firmware loading. I've put
> copies of the
> > firmware files in a whole bunch of different locations
> (listed below). No
> > matter what I try, I can't seem to get the hotplug firmware
> loader to find
> > any of my firmware! Any help? dmesg is located below.
>
> Grabbing the files is handled by the firmware.agent script, do
> a 'locate
> firmware.agent' and see where it looks.
>
> > tveeprom: Encountered bad packet header [ea]. Corrupt or not
> a Hauppauge
> > eeprom.
>
> Something wrong here.
> --
> Tyler Trafford
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
