Problem is back. Obviously not a modules file issue. Though I wonder why
removing it worked the first time around?
On May 3, 2014 6:52 PM, "Adam Hicks" wrote:
> It works fine for me when plugged in. Definitely a wireless issue IME.
> On May 3, 2014 6:35 PM, "kylea" wrote:
>
>> I believe this
It works fine for me when plugged in. Definitely a wireless issue IME.
On May 3, 2014 6:35 PM, "kylea" wrote:
> I believe this problem is not a WIFI issue only - unless I have a new
> bug. My experience only started with 14.04 and the issue occurs on Wired
> Connection. Network Manager will not
Ok, took alook inside /etc/pm/config.d/modules and found this line and ONLY
this line:
SUSPEND_MODULES="b43 bcma"
I removed the /modules file and now everything is peachy.
New to this process...what do we do to get Canonical to add this adjustment
to network-manager?
Also, is there any ill effe
I just re-installed network-manager. Took a look in /etc/pm/config.d and
there's no config file. Has this already been updated by you hard working
devs in the package? Or am I missing something?
Thanks for all the work.
On Fri, Apr 25, 2014 at 2:47 PM, punund <1286...@bugs.launchpad.net>
wrot
I never use jupiter on this machine. There is no relation with this problem
for me.
2014-04-25 1:57 GMT+02:00 Adam Hicks :
> I've always used TLP but this issue started before I installed it on this
> machine.
> On Apr 24, 2014 5:55 PM, "justin parker" <1286...@bugs.launchpad.net>
> wrote:
>
> >
I've always used TLP but this issue started before I installed it on this
machine.
On Apr 24, 2014 5:55 PM, "justin parker" <1286...@bugs.launchpad.net> wrote:
> s0m3f00l@Ubuntu-s0m3f00l:~$ sudo apt-get purge jupiter
> [sudo] password for s0m3f00l:
> Reading package lists... Done
> Building depend
OssNass,
NM isn't stuck sleeping. It scans, recognizes the Wifi, tries to connect
but continually fails to do so. Over and over relentlessly.
On Tue, Apr 22, 2014 at 3:24 PM, OssNass wrote:
> I have an Asus X61SL laptop suffering from the same problem and I solved
> like this:
> First use '
I'm not complaining, BTW. Just doing my part in reporting bugs. I've been
using amazing and free software from Canonical for years now and feel that
reporting bugs is the least I can do. *Least*.
I'm sure Ubuntu product managers have a reason for packaging NM as a
default, and for me it worked
To be honest, my fix was to get rid of network manager and use wicd
instead...though some dist-upgrades put network-manager back on and force
me to purge again.
Since I submitted this bug I'll make sure and clarify...I have had Ubuntu
on this MacBook since 12.04 and had no issue with Wifi. It alw
