Search:

~$ echo "options asus-nb-wmi wapf=4" | sudo tee /etc/modprobe.d/asus-nb-wmi.conf
[sudo] password for weword:
options asus-nb-wmi wapf=4

no difference, I'm afraid, after re-booting (after which...

~$ lsmod | grep blue; uname -a
bluetooth 520192 29 bnep,btbcm,btrtl,btusb,rfcomm,btintel
Linux UX301 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64...

here you go (can't see any results):

~$ rfkill list all
1: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
2: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
3:...

same result at rfkill list all after re-booting + bluetooth still unresponsive (even "show bluetooth status in taskbar" doesn't work).

actually...

~$ rfkill list all
1: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
2: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN

thanks for getting back to me on this.

rfkill unblock all doesn't produce any result.

~$ rfkill list all
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
1: asus-wlan: Wireless LAN...

don't know if it's too late to update this thread...anyway, here it goes:

if you Ctrl-F "To achieve that effect, just add blacklist asus-nb-wmi to /etc/modprobe.d/blacklist.conf" at...

thanks for the info grahammechanical

i've now noticed that they don't always appear - only after using the pc for a while (whether I re-boot or shut down).

the "acpi_osi= " is there because...

hello there,

I recently re-installed Ubuntu 16.04 - and couldn't shut it down. The splash screen looked all right. I've just re-installed it twice (no dual OS, only Ubuntu) on the an Asus UX301LA...

just wanted to report on a new development:

bluetooth now works on the following kernel


$ dpkg --list | grep linux-image
ii linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1...

Tried just now and chose "S":

Please choose (S/V/K/I/C): S
weword@UX301 ~ $

supposedly the report was sent? do you mean the report I posted at...

bug report submitted - hope there's a solution somewhere. Thanks very much for your help.

OK, I shut down and started the PC with the wifi disabled.

This seems to confirm that slight difference in terms of behaviour I mentioned earlier: the bluetooth icon in the taskbar "lits up",...

Resetting the Bios to defaults didn't help. I had a look inside the Asus and - as far as I can see - it's quite difficult to remove the wireless card (it probably entails cutting some wires and then...

you mean physically remove it? I wouldn't know where to start from/haven't got any tool/no pc repair shop near where i live...

can i simply reinstall the wifi? (how?)

sorry I'm confused :) I...

Thanks Jeremy31. Here's the output:


~$ lspci -nnk | grep -iA2 net; lsusb; lsmod | grep blue; dmesg | egrep -i 'blue|firm'
02:00.0 Network controller [0280]: Intel Corporation Wireless 7260...

a very belated thanx tons for suggestions and ideas - was away and couldn't reply sooner.
I'm going to look into gPhoto and Mauricio Jost. Will post feedback when I can.

hello,

can't find specific reference to the following issue - apologies if it's a duplicate:

I've installed Ubuntu 16.04 on a Asus UX301. I can't start bluetooth. Going to...

bump? has anyone come across this problem?

a wild-card scenario: while shutting down, ubuntu disconnect active wifi connections...

could the reason for the hang-up be that ubuntu can't disconnect? that it sends a signal like "disconnect...

so here's a quick update:

i'm now back to 14.04.03 and have tested it last night and today.

half of the time it doesn't shut down and i have to resort to force-shut (power-button).

i...

Thanx matt_symes for the suggestion.
I tried and tried again, and it doesn't seem to make any difference...
Now "downgrading" to 14.04.03 again. Will report on any development shortly.
Thanks...

er....bump? :)

forgotten to add that sudo shutdown now works most of the time (not always, maybe 8 out of 10) and shut down from taskbar works (say) 2 times out of 10.

I never had this issue with Ubuntu 14.04.02 running on a Asus UX301.

it first happened after upgrading to 14.04.03. After tampering with /etc/default/grub/ (and adding acpi=force among other...