wifi and bluetooth auto start at system startup

[arun-mintuser]

Hi guys,

I have an acer aspire 5560g laptop on a dual boot with linux mint 17 64 bit cinnamon with win 7.

Every time the system starts, i find that the wi-fi and bluetooth are on by default, irrespective of the fact that did switched them off on the last shutdown. They auto start along with the system startup. How do i make them stop doing that, only to want them to work when i want to, naturally to save battery.

Thanks.

[seeley]

Hi arun-mintuser!
At the moment I'm on Mint 13 Cin. / German, but I suppose it is easy to follow my steps.
1. WiFi
Normally you have an Icon on your panel/ system tray; see mine:

panel_wifi.png

the last symbol is the WiFi icon; click on it and choose the last option (preferences, settings?) [NW : Einstellungen]
disable "autom. connect"

2. BT
2.1 Menu / starting programms (starter/ startup applications?) [Menu/ Startprogramme] : disable BT
or
2.2
start BT -> visibility off.

[arun-mintuser]

Hi seely,

nope it's not the same in LM 17. I don't see the options you mention.

[seeley]

1. WiFi>
Click on the last Icon (see my panel)

panelNWC.png

you see>
wired
wireless
Network Settings
Network Connections
If you choose Network Settings>
Networking wireless OFF

wireless.png

2. BT
Menu Bluetooth

BTV.png

Bluetooth / Visibility OFF

[arun-mintuser]

Now i follow, thanks I get it.

But the thing is I have to do this every single time my computer starts up. Wifi and bluetooth just don't stay off, they start up along with the computer; everytime.

Sorry to sound like a beginner, but that is what I am when it comes to computers.

[arun-mintuser]

sorry guys, but the problem still persists.

bluetooth and wifi start up automatically along with system startup. I have to manually shut them doen from panel.

Please help, this is killing the battery and is a lousy distraction from an otherwise beautiful experience.

[arun-mintuser]

hi guys,

i tried adding "rfkill block bluetooth" and "rfkill block wifi" to /etc/rc.local file.

this method works for bluetooth but not for wifi.

i also tried iwconfig for wifi by adding " sudo iwconfig wlan0 down" to /etc/rc.local file. This though stops wifi, but the applet still shows it as on. In my opinion not exactly a perfect solution.

Please help...

[JeremyB]

hi guys,

i tried adding "rfkill block bluetooth" and "rfkill block wifi" to /etc/rc.local file.

this method works for bluetooth but not for wifi.

i also tried iwconfig for wifi by adding " sudo iwconfig wlan0 down" to /etc/rc.local file. This though stops wifi, but the applet still shows it as on. In my opinion not exactly a perfect solution.

Please help...

How about using
rfkill block all

[arun-mintuser]

rfkill bloc all would also block my eth0 connection, dont wanna disturb it. if it ain't broken dont fix it.

any other siggestion?

[JeremyB]

rfkill bloc all would also block my eth0 connection, dont wanna disturb it. if it ain't broken dont fix it.

any other siggestion?

It should only block wireless connections

[arun-mintuser]

thanks jeremy. it worked.

[cyberschelm]

Hello,

Thanks guys, my ever resetting bluetooth was also annoying me, and this fixed it.

I do notice a bit of inconsistent behaviour with putting "rfkill bock all" in /etc/rc.local.

bluetooth: no matter if it was on or off prior to reboot, it will be off after reboot.
wifi: if it is on prior to reboot, it will be on after. If it is off prior to reboot, it will be off after.

When I read the man pages and google pages of "rfkill", I would expect both to be soft blocked on startup.
Is this behaviour as it should be?

I'm on a lenovo thinkpad-T61 running Qiana cinnamon 64.
(with a defective hard block switch that cannot be turned on)

Regards,

Cyberschelm

[JeremyB]

It can vary depending on the modules on the computer. I am fairly sure I saw one module that you could set a parameter for that would disable the rfkill. I am not sure that the command needs to be in rc.local as some of the quick tests I did indicated that the block remained after a restart but I could try some more tests with the 4 laptops I have

[cyberschelm]

cool

Keep in mind tho that I'm quite happy with the way it behaves atm, my prob is solved.
The question was more out of curiosity.

[arun-mintuser]

guys, i am re-opening the thread for support as the problem is back to haunt me again. "rfkill block all" added to /etc/rc.local stops only bluetooth on startup, wifi still starts up automatically. the damn thing just just doesn't stay shut. Please help

[JeremyB]

If you never use wifi and/or bluetooth, we can blacklist the modules that allow them to work

Just post the results of

Code: Select all

lsmod

and then we can see which ones to blacklist

[arun-mintuser]

i do use wifi and bluetooth, i use them to connect my phone and to transfer files...i dont want anything blacklisted to not work for ever, i just dont want them starting up along with the system, is there some service which runs at system startup in which it is written :always on" at startup, or something like that?
the output of ls mod is this..

Code: Select all

Module                  Size  Used by
nvram                  14411  0 
pci_stub               12622  1 
vboxpci                23194  0 
vboxnetadp             25670  0 
vboxnetflt             27613  0 
vboxdrv               339502  3 vboxnetadp,vboxnetflt,vboxpci
rfcomm                 69160  0 
bnep                   19624  2 
binfmt_misc            17468  1 
ath3k                  13318  0 
btusb                  32412  0 
bluetooth             395423  12 bnep,ath3k,btusb,rfcomm
uvcvideo               80885  0 
videobuf2_vmalloc      13216  1 uvcvideo
videobuf2_memops       13362  1 videobuf2_vmalloc
videobuf2_core         40664  1 uvcvideo
videodev              134688  2 uvcvideo,videobuf2_core
acer_wmi               32522  0 
sparse_keymap          13948  1 acer_wmi
kvm_amd                59987  0 
kvm                   451511  1 kvm_amd
joydev                 17381  0 
snd_hda_codec_realtek    61438  1 
serio_raw              13462  0 
ip6t_REJECT            12939  1 
snd_hda_codec_hdmi     46207  1 
xt_hl                  12521  6 
ip6t_rt                13537  3 
nf_conntrack_ipv6      18894  8 
nf_defrag_ipv6         34768  1 nf_conntrack_ipv6
ipt_REJECT             12541  1 
arc4                   12608  2 
xt_LOG                 17717  10 
dm_multipath           22873  0 
scsi_dh                14882  1 dm_multipath
snd_seq_midi           13324  0 
snd_seq_midi_event     14899  1 snd_seq_midi
snd_rawmidi            30144  1 snd_seq_midi
snd_hda_intel          52355  5 
snd_hda_codec         192906  3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep              13602  1 snd_hda_codec
snd_pcm               102099  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_seq                61560  2 snd_seq_midi_event,snd_seq_midi
xt_limit               12711  13 
xt_tcpudp              12884  18 
xt_addrtype            12635  4 
ath9k                 164164  0 
ath9k_common           13551  1 ath9k
nf_conntrack_ipv4      15012  8 
nf_defrag_ipv4         12758  1 nf_conntrack_ipv4
xt_conntrack           12760  16 
k10temp                13126  0 
ath9k_hw              453856  2 ath9k_common,ath9k
snd_seq_device         14497  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_page_alloc         18710  2 snd_pcm,snd_hda_intel
snd_timer              29482  2 snd_pcm,snd_seq
i2c_piix4              22155  0 
ip6table_filter        12815  1 
ath                    28698  3 ath9k_common,ath9k,ath9k_hw
ip6_tables             27025  1 ip6table_filter
mac80211              626489  1 ath9k
fglrx                8815330  100 
nf_conntrack_netbios_ns    12665  0 
nf_conntrack_broadcast    12589  1 nf_conntrack_netbios_ns
nf_nat_ftp             12770  0 
nf_nat                 21798  1 nf_nat_ftp
snd                    69238  21 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_seq_midi
nf_conntrack_ftp       18638  1 nf_nat_ftp
nf_conntrack           96976  8 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_conntrack,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_ipv6
iptable_filter         12810  1 
ip_tables              27239  1 iptable_filter
x_tables               34059  13 ip6table_filter,xt_hl,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ip6t_rt,ipt_REJECT,ip6_tables,xt_addrtype,ip6t_REJECT
cfg80211              484040  3 ath,ath9k,mac80211
amd_iommu_v2           19054  1 fglrx
soundcore              12680  1 snd
mac_hid                13205  0 
parport_pc             32701  0 
ppdev                  17671  0 
lp                     17759  0 
parport                42348  3 lp,ppdev,parport_pc
dm_mirror              22135  0 
dm_region_hash         20862  1 dm_mirror
dm_log                 18411  2 dm_region_hash,dm_mirror
hid_generic            12548  0 
usbhid                 52616  0 
hid                   106148  2 hid_generic,usbhid
psmouse               102222  0 
tg3                   166442  0 
video                  19476  1 acer_wmi
ptp                    18933  1 tg3
sdhci_pci              23172  0 
wmi                    19177  1 acer_wmi
sdhci                  43015  1 sdhci_pci
pps_core               19382  1 ptp
ahci                   25819  3 
libahci                32168  1 ahci

[arun-mintuser]

I have also noted a new development. The wifi led blinks on just as linux starts booting, then switches itself off ( might be rfkill at work), then it switches on again. Must be some service switching wifi on as a boot process.

Please assist.

[JeremyB]

I have also noted a new development. The wifi led blinks on just as linux starts booting, then switches itself off ( might be rfkill at work), then it switches on again. Must be some service switching wifi on as a boot process.

Please assist.

That could mean that something is turning wifi on after rc.local is run
Might have to make a script with the rfkill block all and add it to startup

Unless your rc.local is not set as executable

Code: Select all

chmod +x /etc/rc.local

you might need sudo in front of command

[arun-mintuser]

tried it.

still the same...wifi still boots up along with the system.