What's new

Need Help, Wireless showing Disabled

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Kaz

Occasional Visitor
I am having problem from this morning with my wireless connectivity it shows as disabled, However I cant turn back, Can someone help me please.
I have firmware version 384.5
Asus-wrt- Merlin


Found solution:
It kind of weird, I went to Wireless>Professional Setting Under Enable Radio, it was turned off. I would like to know what happened, is it possible by taking a look at the log
 

Attachments

  • Professional_Setting.jpg
    Professional_Setting.jpg
    66.5 KB · Views: 138
Last edited:
I managed to find the log
Feb 13 19:00:15 syslogd started: BusyBox v1.25.1
Feb 13 19:00:15 kernel: klogd started: BusyBox v1.25.1 (2018-05-12 21:53:16 EDT)
Feb 13 19:00:15 kernel: Linux version 2.6.36.4brcmarm (merlin@ubuntu-dev) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Sat May 12 22:03:28 EDT 2018
Feb 13 19:00:15 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f
Feb 13 19:00:15 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Feb 13 19:00:15 kernel: Machine: Northstar Prototype
Feb 13 19:00:15 kernel: Ignoring unrecognised tag 0x00000000
Feb 13 19:00:15 kernel: bootconsole [earlycon0] enabled
Feb 13 19:00:15 kernel: Memory policy: ECC disabled, Data cache writealloc
Feb 13 19:00:15 kernel: MPCORE found at 19020000
Feb 13 19:00:15 kernel: PERCPU: Embedded 7 pages/cpu @c8215000 s5472 r8192 d15008 u65536
Feb 13 19:00:15 kernel: pcpu-alloc: s5472 r8192 d15008 u65536 alloc=16*4096
Feb 13 19:00:15 kernel: pcpu-alloc: [0] 0 [0] 1
Feb 13 19:00:15 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60416
Feb 13 19:00:15 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
Feb 13 19:00:15 kernel: PID hash table entries: 1024 (order: 0, 4096 bytes)
Feb 13 19:00:15 kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Feb 13 19:00:15 kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Feb 13 19:00:15 kernel: Memory: 128MB 128MB = 256MB total
Feb 13 19:00:15 kernel: Memory: 255488k/255488k available, 6656k reserved, 0K highmem
Feb 13 19:00:15 kernel: Virtual kernel memory layout:
Feb 13 19:00:15 kernel: vector : 0xffff0000 - 0xffff1000 ( 4 kB)
Feb 13 19:00:15 kernel: fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
Feb 13 19:00:15 kernel: DMA : 0xf7e00000 - 0xffe00000 ( 128 MB)
Feb 13 19:00:15 kernel: vmalloc : 0xd0800000 - 0xf0000000 ( 504 MB)
Feb 13 19:00:15 kernel: lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
Feb 13 19:00:15 kernel: modules : 0xbf000000 - 0xc0000000 ( 16 MB)
Feb 13 19:00:15 kernel: .init : 0xc0008000 - 0xc003d000 ( 212 kB)
Feb 13 19:00:15 kernel: .text : 0xc003d000 - 0xc03aa000 (3508 kB)
Feb 13 19:00:15 kernel: .data : 0xc03c2000 - 0xc03e52e0 ( 141 kB)
Feb 13 19:00:15 kernel: SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Feb 13 19:00:15 kernel: * Invalid signature of oopsbuf: FF-FF-FF-FF-FF-FF-FF-FF (len 4294967295)
Feb 13 19:00:15 kernel: Hierarchical RCU implementation.
Feb 13 19:00:15 kernel: RCU-based detection of stalled CPUs is disabled.
Feb 13 19:00:15 kernel: Verbose stalled-CPUs detection is disabled.
Feb 13 19:00:15 kernel: NR_IRQS:256
Feb 13 19:00:15 kernel: MPCORE GIC init
Feb 13 19:00:15 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06 ignored.
Feb 13 19:00:15 kernel: MPCORE Global Timer Clock 400000000Hz
Feb 13 19:00:15 kernel: Calibrating delay loop... 1599.07 BogoMIPS (lpj=7995392)
Feb 13 19:00:15 kernel: pid_max: default: 32768 minimum: 301
Feb 13 19:00:15 kernel: Mount-cache hash table entries: 512
Feb 13 19:00:15 kernel: CPU: Testing write buffer coherency: ok
Feb 13 19:00:15 kernel: MPCORE Private timer setup CPU0
Feb 13 19:00:15 kernel: Calibrating local timer... 399.884MHz.
Feb 13 19:00:15 kernel: L310: cache controller enabled 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x7a130000
Feb 13 19:00:15 kernel: CPU1: Booted secondary processor
Feb 13 19:00:15 kernel: MPCORE Private timer setup CPU1
Feb 13 19:00:15 kernel: Brought up 2 CPUs
Feb 13 19:00:15 kernel: SMP: Total of 2 processors activated (3198.15 BogoMIPS).
Feb 13 19:00:15 kernel: devtmpfs: initialized
Feb 13 19:00:15 kernel: atomic64 test passed
Feb 13 19:00:15 kernel: NET: Registered protocol family 16
Feb 13 19:00:15 kernel: Found a AMD NAND flash:
Feb 13 19:00:15 kernel: Total size: 128MB
Feb 13 19:00:15 kernel: Block size: 128KB
Feb 13 19:00:15 kernel: Page Size: 2048B
Feb 13 19:00:15 kernel: OOB Size: 64B
Feb 13 19:00:15 kernel: Sector size: 512B
Feb 13 19:00:15 kernel: Spare size: 16B
Feb 13 19:00:15 kernel: ECC level: 8 (8-bit)
Feb 13 19:00:15 kernel: Device ID: 0x 1 0xf1 0x80 0x1d 0x 1 0xf1
Feb 13 19:00:15 kernel: CCA UART Clock Config: Sel=1 Ovr=1 Div=48
Feb 13 19:00:15 kernel: CCA UART Clock rate 100000000Hz
Feb 13 19:00:15 kernel: bio: create slab <bio-0> at 0
Feb 13 19:00:15 kernel: Switching to clocksource mpcore_gtimer
Feb 13 19:00:15 kernel: NET: Registered protocol family 2
Feb 13 19:00:15 kernel: IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
Feb 13 19:00:15 kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Feb 13 19:00:15 kernel: TCP bind hash table entries: 8192 (order: 4, 98304 bytes)
Feb 13 19:00:15 kernel: TCP: Hash tables configured (established 8192 bind 8192)
Feb 13 19:00:15 kernel: TCP reno registered
Feb 13 19:00:15 kernel: UDP hash table entries: 128 (order: 0, 4096 bytes)
Feb 13 19:00:15 kernel: UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
Feb 13 19:00:15 kernel: NET: Registered protocol family 1
Feb 13 19:00:15 kernel: PCI: no core
Feb 13 19:00:15 kernel: PCI: no core
Feb 13 19:00:15 kernel: PCI: scanning bus 0
Feb 13 19:00:15 kernel: PCI: Fixing up bus 0
Feb 13 19:00:15 kernel: PCIE1 link=1
Feb 13 19:00:15 kernel: PCIE1 switching to GEN2
Feb 13 19:00:15 kernel: PCIE1 link=1
Feb 13 19:00:15 kernel: PCI: Fixing up bus 0
Feb 13 19:00:15 kernel: PCI: bus0: Fast back to back transfers disabled
Feb 13 19:00:15 kernel: PCI: Fixing up bus 1
Feb 13 19:00:15 kernel: PCI: bus1: Fast back to back transfers disabled
Feb 13 19:00:15 kernel: pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
Feb 13 19:00:15 kernel: pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
Feb 13 19:00:15 kernel: pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff]
Feb 13 19:00:15 kernel: pci 0001:00:00.0: PCI bridge to [bus 01-01]
Feb 13 19:00:15 kernel: pci 0001:00:00.0: bridge window [io disabled]
Feb 13 19:00:15 kernel: pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff]
Feb 13 19:00:15 kernel: pci 0001:00:00.0: bridge window [mem pref disabled]
Feb 13 19:00:15 kernel: PCIE2 link=1
Feb 13 19:00:15 kernel: PCIE2 switching to GEN2
Feb 13 19:00:15 kernel: PCIE2 link=1
Feb 13 19:00:15 kernel: PCI: Fixing up bus 0
Feb 13 19:00:15 kernel: PCI: bus0: Fast back to back transfers disabled
Feb 13 19:00:15 kernel: PCI: Fixing up bus 2
Feb 13 19:00:15 kernel: PCI: bus2: Fast back to back transfers disabled
Feb 13 19:00:15 kernel: pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
Feb 13 19:00:15 kernel: pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]
Feb 13 19:00:15 kernel: pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff]
Feb 13 19:00:15 kernel: wl_module_init: igs set to 0x0
Feb 13 19:00:15 kernel: wl_module_init: txworkq set to 0x0
Feb 13 19:00:15 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
Feb 13 19:00:15 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
 
Possible the WPS button was pushed. That can turn off the WIFI.
Might be a good idea for you to upgrade your firmware
 
Thanks for the quick reply, I would like to know from looking at the log, was there something
 
What router are we talking about here? Yes, that firmware should have been put out to pasture a long time ago.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top