The work around for rtl8180 is to add a junk char after the end of the essid
see bug 78255. I think bug 78037 and related bug 104414 are not
duplicates of this one.
On 4/16/07, Patrick <email address hidden> wrote:
> A question... which driver are you people using?
>
> I think a few kernels ago, rt2x00 drivers were intruduced. I don't know
> if they are still there and if they are default.. check it: sudo lsmod |
> grep rt2500. If rt2500pci appears, you're using the rt2x00 project
> ones.. I had no luck. Blacklist them and use the rt2500.ko modules (the
> legacy, which works fine)
>
> --
> many cards need to be downed for changing essid
> https://bugs.launchpad.net/bugs/78037
> You received this bug notification because you are a direct subscriber
> of the bug.
>
The work around for rtl8180 is to add a junk char after the end of the essid
see bug 78255. I think bug 78037 and related bug 104414 are not
duplicates of this one.
On 4/16/07, Patrick <email address hidden> wrote: /bugs.launchpad .net/bugs/ 78037
> A question... which driver are you people using?
>
> I think a few kernels ago, rt2x00 drivers were intruduced. I don't know
> if they are still there and if they are default.. check it: sudo lsmod |
> grep rt2500. If rt2500pci appears, you're using the rt2x00 project
> ones.. I had no luck. Blacklist them and use the rt2500.ko modules (the
> legacy, which works fine)
>
> --
> many cards need to be downed for changing essid
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>