Sure! Let's swipe it under the carpet and ship Lucid with broken wifi
stack (yet again)! Sorry...
On Wed, Mar 3, 2010 at 9:11 AM, Chase Douglas
<email address hidden> wrote:
> @Truxpin:
>
> If you still have Windows around, you may want to try booting into it to
> see if you can enable wifi in windows. Maybe the windows driver can
> unblock the hard block somehow? You should also double check your bios,
> as there may be a switch in there for wireless.
>
> --
> ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig wlan0 up
> https://bugs.launchpad.net/bugs/464559
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Sure! Let's swipe it under the carpet and ship Lucid with broken wifi
stack (yet again)! Sorry...
On Wed, Mar 3, 2010 at 9:11 AM, Chase Douglas /bugs.launchpad .net/bugs/ 464559
<email address hidden> wrote:
> @Truxpin:
>
> If you still have Windows around, you may want to try booting into it to
> see if you can enable wifi in windows. Maybe the windows driver can
> unblock the hard block somehow? You should also double check your bios,
> as there may be a switch in there for wireless.
>
> --
> ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig wlan0 up
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>