I've created a udev rule which works quite well for this card. It is
attached. It depends on the firmware being saved in /lib/firmware/<kernel
version>/ as prism2-pm010102.hex and prism2-rf010804.hex.
At present this works for me. I don't know how many cards out there need
the same firmware files and depend on prism2_srec, but rules could be
created for them fairly easily following the same pattern.
I do not know if there is a better way to get `uname -r` into udev than how
I'm doing it. It did not appear to be one of the ENV{} variables...
-Philip
On 10/10/07, Philip Barton <[EMAIL PROTECTED]> wrote:
>
> There is a firmware loading script for hostap which can be viewed here:
>
> http://pyramid.metrix.net/svn/Pyramid/dist/sbin/hostap_fw_load
>
> As I understand, this came as an example with the source prior to the
> hostap driver being included with the kernel sources. prism2_srec is still
> the utility that is used when fw_primary and fw_secondary are specified in
> /etc/network/interfaces, I believe.
>
> I hope this information is of some use... Every time I switch my wireless
> to roaming mode, my /etc/network/interfaces entries for fw_primary and
> fw_secondary are deleted. It's quite a pain!
>
> Is this something that can be implemented with udev rules?
>
> -Philip
>
> On 9/18/07, Philip Barton <[EMAIL PROTECTED]> wrote:
> >
> > Martin, I hope I can provide some useful information to you!
> >
> > * Is this associated with a particular kernel module?
> > >
> > Yes! hostap_cs.ko is the module in question.
> >
> > * I wouldn't like to modify /etc/network/interfaces, because that would
> > > make the setup incompatible with network-manager. Usually they should
> > > be
> > > put into /lib/firmware/<kernel version>/, and the kernel module should
> > > load them automatically. If that works, it would be much preferable.
> > > If
> > > it doesn't work, I can also do the modification of the interfaces
> > > file.
> > >
> > I understand... I have no clue how the firmware is being handled by
> > hostap_cs, though, or if it is even handling the firmware! What I do know
> > is that there are many revisions of the firmware, and any of them can be
> > used with varying degrees of stability. Since every firmware version has
> > its version number in its filename, I have no idea whether hostap_cs is
> > looking for a default firmware filename before using the filenames specified
> > in /etc/network/interfaces.
> >
> > Despite lacking a default filename, I went ahead and put the firmware
> > files I had been using in /lib/firmware/<kernel-version>/, rebooted, and...
> > nothing. I will do some digging within hostap and hostap_cs for more info.
> >
> > Thanks!
> >
> > -Philip Barton
> >
> > On 9/18/07, Martin Pitt < [EMAIL PROTECTED] > wrote:
> > >
> > > Thank you for that information, but I need some more, I'm afraid:
> > >
> > > * Is this associated with a particular kernel module?
> > >
> > > * I wouldn't like to modify /etc/network/interfaces, because that
> > > would
> > > make the setup incompatible with network-manager. Usually they should
> > > be
> > > put into /lib/firmware/<kernel version>/, and the kernel module should
> > > load them automatically. If that works, it would be much preferable.
> > > If
> > > it doesn't work, I can also do the modification of the interfaces
> > > file.
> > >
> > > --
> > > info regarding firmware for DWL-650 Rev. P1
> > > https://bugs.launchpad.net/bugs/123292
> > > You received this bug notification because you are a direct subscriber
> > >
> > > of the bug.
> > >
> >
> >
>
--
info regarding firmware for DWL-650 Rev. P1
https://bugs.launchpad.net/bugs/123292
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
