Discussion stats
Announcements

Top Contributors
Reply
Highlighted

Re: R7000 Firmware Bug 1.0.6.28

To Netgear. Please offer a separate firmware for people who have ARLO. So the people who don't and don't want to own it have the option

of keeping their network Fresh and speedy. It seems like adding this has only degraded peoples moral and their home network.

Also keeping the processing power that they had as well. I know you can turn it off but the size of the firmware for that added little bit of (insert your own term for

R HO here). Please also fix the problem that people who run Kaspersky security can't access their Admin Panel's and have to disable just to get to it.

Sorry for the rant. Good day to you.

Message 26 of 74
Highlighted
Luminary

Re: R7000 Firmware Bug 1.0.6.28

It's really sad that Netgear seems to prefer to stay so quiet and silent while there are so many posts about this router and this firmware. People will start to mistrust Netgear if that continues...

Message 27 of 74
Highlighted

Re: R7000 Firmware Bug 1.0.6.28

I think this is a NETGEAR SCAM!!! I received this email as well, and went through Genie to find and apply the firmware update.  Immediately, I start having problems with my 2.4GHz network.  When I call in, I'm told they can't help me diagnose whether this is a HW problem (still under warranty) unless I have a support contract.  Minimum $50 one-day contract.  Grudgingly, I took the one-time contract because he said that if they found it to be a HW problem, they would not charge me the $50 and send me a replacement.  What do they do, but go find a previous working firmware release and install that after a factory reset.  And they are still charing me the $50.  So, this is how you generate revenue now?  Phony firmware which generates support contracts and calls?  I bet the email only went to those people who did not have an existing support contract.  Netgear had better make this right or I will make sure everyone knows what a dirty practice this is.

Message 28 of 74
Highlighted
Aspirant

Re: R7000 Firmware Bug 1.0.6.28

I got this wonderful notification from Netgear that a new firmware was available that fixed critial issues. Great! Now I have no connectivity for the 2.4Ghz network. Thanks Netgear for crashing my network and web server accessibility. One of the suggestions was to disable the guest network, which seemed to resolve the issue. But, now I do not have a way for guests or clients to connect without giving access to internal network. What a crap experience this is.

Message 29 of 74
Highlighted
NETGEAR Moderator

Re: R7000 Firmware Bug 1.0.6.28

Hi All,

 

If you are having issues with 2.4Ghz with the latest firmware and doing factory reset did not work, you may revert to firmware version v1.0.4.30.

 

You can download it in the link below:

 

http://downloadcenter.netgear.com/en/product/R7000#searchResults

Message 30 of 74
Highlighted
Aspirant

Re: R7000 Firmware Bug 1.0.6.28

Actually I found that doing the factory reset installed version 1.0.5.48_1.1.79, which resolved the home network connection problem to the 2.4 GHz band for my wife's laptop and my wireless printer.  Until we receive a notice that the bugs have been fixed in version 1.0.6.28_1.1.83, my advice is to stay away, especially if you have a complex WLAN setup.  In that instance, be sure to document everything in writing before doing any firmware update, as another post indicated that backing up your current settings will NOT restore properly.  So, in this instance, what's the point of even having the backup option, if a person can't restore their settings?

Message 31 of 74
Highlighted
Prodigy

Re: R7000 Firmware Bug 1.0.6.28

As I have said before just copy your settings down, I have quite a complicated setup, but I wrote a text file with all the settings, then I just open it up before accessing the routers setup page after an update and reset and copy and paste all my settings back in. Takes no time at all.

Message 32 of 74
Highlighted
Tutor

Re: R7000 Firmware Bug 1.0.6.28

James,

 

I noticed R7000 firmware versions 1.0.5.48 and 1.0.6.28 are no longer available for download.

 

Why?

Message 33 of 74
Highlighted
Aspirant

Re: R7000 Firmware Bug 1.0.6.28

I'm having the same issue with my recently flashed R7000.  Looks like the 2.4Ghz channel is dropping connections and won't seem to work again unless I perform a router reboot.  Would appear to be a bug with the latest firmware update: 1.0.6.28_1.1.83.  Can someone with Netgear look into this ASAP?  Seeing all the other people on here reporting the same issue should warrant a fix or at least a roll back to a previously released version.

Message 34 of 74
Highlighted
Virtuoso

Re: R7000 Firmware Bug 1.0.6.28

Netgear is aware of the issue and has pulled that release. If a hard reset to factory defaults and manual reconfigure does not help you, then downgrade to 1.0.4.30.

 

Message 35 of 74
Highlighted
Aspirant

Re: R7000 Firmware Bug 1.0.6.28

This is a problem.. Ever since I upgraded to the latest firmware (which it said for security reasons) I CONSTANTLY drop my wireless to all my devices. Can they solve this please....

Message 36 of 74
Highlighted
Prodigy

Re: R7000 Firmware Bug 1.0.6.28

Here you go. Another Beta firmware.

V1.0.6.40_1.1.90

Message 37 of 74
Highlighted
Tutor

Re: R7000 Firmware Bug 1.0.6.28

This beta firmware causes a kernel panic and endless reboots in my R7000:

 

> fileSize = 28954682
.........................................................................................................................................................................................................................................................................................................................................................................................................................................................killall: bftpd: no process killed
killall: smbd: no process killed
killall: nmbd: no process killed
killall: ntfs-3g: no process killed

Writing 28954624 bytes to /dev/mtd2.
done.

Doing nvram commit by pid 10890 !
Restarting system.
Digital core power voltage set to 1.0V
Decompressing...done
Digital core power voltage set to 1.0V

SHMOO VER 1.13

PKID07DC06011801080000000000001A103F01000000

S300001C3
00001270


RDLYW0 00000004

RDENW0 00000032

RDQSW0

    0000000000111111111122222222223333333333444444444455555555556666
    0123456789012345678901234567890123456789012345678901234567890123
 00 -----+++++++++++++++++++++++++X++++++++++++++++++++++++---------
 01 --------+++++++++++++++++++++++++X++++++++++++++++++++++++------
 02 -------+++++++++++++++++++++++X++++++++++++++++++++++-----------
 03 -----++++++++++++++++++++++++X++++++++++++++++++++++++----------
 04 ---+++++++++++++++++++++++X++++++++++++++++++++++---------------
 05 -----+++++++++++++++++++++++++X++++++++++++++++++++++++---------
 06 ---+++++++++++++++++++++++X+++++++++++++++++++++++--------------
 07 ---------++++++++++++++++++++++++X+++++++++++++++++++++++-------
 08 --+++++++++++++++++++++++X+++++++++++++++++++++++---------------
 09 ---------++++++++++++++++++++++++X+++++++++++++++++++++++-------
 10 ----++++++++++++++++++++++++X++++++++++++++++++++++++-----------
 11 ---------++++++++++++++++++++++++X++++++++++++++++++++++++------
 12 --+++++++++++++++++++++++++X++++++++++++++++++++++++------------
 13 --------+++++++++++++++++++++++X+++++++++++++++++++++++---------
 14 ----+++++++++++++++++++++++++X++++++++++++++++++++++++----------
 15 ---------++++++++++++++++++++++++X++++++++++++++++++++++++------


PW0

    0000000000111111111122222222223333333333444444444455555555556666
    0123456789012345678901234567890123456789012345678901234567890123
 00 ----+++++++++++++++++++++++++X+++++++++++++++++++++++++---------
 01 ------++++++++++++++++++++++++++X+++++++++++++++++++++++++------
 02 -----++++++++++++++++++++++++X++++++++++++++++++++++++----------
 03 ---+++++++++++++++++++++++++X+++++++++++++++++++++++++----------
 04 +++++++++++++++++++++++++X++++++++++++++++++++++++--------------
 05 ---++++++++++++++++++++++++++X+++++++++++++++++++++++++---------
 06 +++++++++++++++++++++++++X++++++++++++++++++++++++--------------
 07 -----++++++++++++++++++++++++++X+++++++++++++++++++++++++-------
 08 -+++++++++++++++++++++++++X++++++++++++++++++++++++-------------
 09 --------+++++++++++++++++++++++++X+++++++++++++++++++++++++-----
 10 ---+++++++++++++++++++++++++X++++++++++++++++++++++++-----------
 11 --------+++++++++++++++++++++++++X+++++++++++++++++++++++++-----
 12 --+++++++++++++++++++++++++X++++++++++++++++++++++++------------
 13 --------++++++++++++++++++++++++X+++++++++++++++++++++++--------
 14 ---++++++++++++++++++++++++++X++++++++++++++++++++++++++--------
 15 ---------+++++++++++++++++++++++++X+++++++++++++++++++++++++----


NW0

    0000000000111111111122222222223333333333444444444455555555556666
    0123456789012345678901234567890123456789012345678901234567890123
 00 ------+++++++++++++++++++++++++X++++++++++++++++++++++++--------
 01 --------+++++++++++++++++++++++++X+++++++++++++++++++++++++-----
 02 -------++++++++++++++++++++++++X++++++++++++++++++++++++--------
 03 -----++++++++++++++++++++++++X++++++++++++++++++++++++----------
 04 --++++++++++++++++++++++++X++++++++++++++++++++++++-------------
 05 -----+++++++++++++++++++++++++X+++++++++++++++++++++++++--------
 06 ----+++++++++++++++++++++++X++++++++++++++++++++++--------------
 07 ---------+++++++++++++++++++++++++X++++++++++++++++++++++++-----
 08 --+++++++++++++++++++++++X+++++++++++++++++++++++---------------
 09 --------++++++++++++++++++++++++X++++++++++++++++++++++++-------
 10 ----++++++++++++++++++++++++X++++++++++++++++++++++++-----------
 11 ---------++++++++++++++++++++++++X++++++++++++++++++++++++------
 12 --+++++++++++++++++++++++++X++++++++++++++++++++++++------------
 13 --------+++++++++++++++++++++++X+++++++++++++++++++++++---------
 14 ----+++++++++++++++++++++++++X++++++++++++++++++++++++----------
 15 --------+++++++++++++++++++++++++X++++++++++++++++++++++++------


WRDQW0

    0000000000111111111122222222223333333333444444444455555555556666
    0123456789012345678901234567890123456789012345678901234567890123
 00 +++++++++++++++++++++++X++++++++++++++++++++++-------++++++++++-
 01 ++++++++++++++++++++++++X+++++++++++++++++++++++-------++++++++-
 02 ++++++++++++++++++++++X++++++++++++++++++++++-------+++++++++++-
 03 ++++++++++++++++++++++X++++++++++++++++++++++--------++++++++++-
 04 ++++++++++++++++++++X++++++++++++++++++++------------++++++++++-
 05 +++++++++++++++++++++++X++++++++++++++++++++++------+++++++++++-
 06 +++++++++++++++++++++X++++++++++++++++++++---------++++++++++++-
 07 +++++++++++++++++++++++X+++++++++++++++++++++++------++++++++++-
 08 ++++++++++++++++++++++X++++++++++++++++++++++--------++++++++++-
 09 ++++++++++++++++++++++++X+++++++++++++++++++++++---------++++++-
 10 +++++++++++++++++++++++X++++++++++++++++++++++-------++++++++++-
 11 --+++++++++++++++++++++++X++++++++++++++++++++++----------+++++-
 12 +++++++++++++++++++++++X++++++++++++++++++++++------+++++++++++-
 13 -+++++++++++++++++++++++X+++++++++++++++++++++++---------++++++-
 14 ++++++++++++++++++++++++X+++++++++++++++++++++++-------++++++++-
 15 --+++++++++++++++++++++++X++++++++++++++++++++++----------+++++-


WRDMW0 00000022
WRDMW0 00000023


ADDR

    0000000000111111111122222222223333333333444444444455555555556666
    0123456789012345678901234567890123456789012345678901234567890123
 00 ++++++++++++++++++S++++++++++++X++++++++++++++++++++++++++++++++

Decompressing...done


CFE for Foxconn Router R7000 version: v1.0.21
Build Date: Wed Aug  7 19:11:17 CST 2013
Init Arena
Init Devs.
Boot up from NAND flash...
Bootcode Boot partition size = 524288(0x80000)
DDR Clock: 800 MHz
Info: DDR frequency set from clkfreq=1000,*800*
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.15.1 (r407936)
CPU type 0x0: 1000MHz
Tot mem: 262144 KBytes

Device eth0:  hwaddr E4-F4-C6-03-58-36, ipaddr 192.168.1.1, mask 255.255.255.0
        gateway not set, nameserver not set
Checking crc...Loader:raw Filesys:raw Dev:nflash0.os File: OptionsSmiley Sadnull)
Loading: ..... 5405952 bytes read
Entry at 0x00008000
Closing network.
Starting program at 0x00008000
[    2.040000] console [ttyS0] enabled, bootconsole disabled
[    2.050000] serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117) is a 16550
[    2.060000] brd: module loaded
[    2.070000] loop: module loaded
[    2.070000] pflash: found no supported devices
[    2.080000] bcmsflash: found no supported devices
[    2.670000] Boot partition size = 524288(0x80000)
[    2.670000] lookup_nflash_rootfs_offset: offset = 0x200000
[    2.680000] nflash: squash filesystem with lzma found at block 32
[    2.680000] Creating 17 MTD partitions on "nflash":
[    2.690000] 0x000000000000-0x000000080000 : "boot"
[    2.690000] 0x000000080000-0x000000200000 : "nvram"
[    2.700000] 0x000000200000-0x000002200000 : "linux"
[    2.710000] 0x00000041c3d8-0x000002200000 : "rootfs"
[    2.710000] 0x000002200000-0x000002240000 : "board_data"
[    2.720000] 0x000002240000-0x000002280000 : "POT1"
[    2.720000] 0x000002280000-0x0000022c0000 : "POT2"
[    2.730000] 0x0000022c0000-0x000002340000 : "T_Meter1"
[    2.740000] 0x000002340000-0x0000023c0000 : "T_Meter2"
[    2.740000] 0x0000023c0000-0x000002400000 : "ML1"
[    2.750000] 0x000002400000-0x000002440000 : "ML2"
[    2.750000] 0x000002440000-0x000002480000 : "ML3"
[    2.760000] 0x000002480000-0x0000024c0000 : "ML4"
[    2.760000] 0x0000024c0000-0x000002500000 : "ML5"
[    2.770000] 0x000002500000-0x000002540000 : "ML6"
[    2.780000] 0x000002540000-0x000002580000 : "ML7"
[    2.780000] 0x000002580000-0x0000025c0000 : "QoSRule"
[    2.790000] PPP generic driver version 2.4.2
[    2.790000] PPP MPPE Compression module registered
[    2.800000] NET: Registered protocol family 24
[    2.800000] PPPoL2TP kernel driver, V0.17
[    2.810000] tun: Universal TUN/TAP device driver, 1.6
[    2.810000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    2.820000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.830000] ehci_hcd 0000:00:0b.1: EHCI Host Controller
[    2.840000] ehci_hcd 0000:00:0b.1: new USB bus registered, assigned bus number 1
[    2.880000] ehci_hcd 0000:00:0b.1: irq 111, io mem 0x18021000
[    2.900000] ehci_hcd 0000:00:0b.1: USB 0.0 started, EHCI 1.00
[    2.900000] match id
[    2.900000] hub 1-0:1.0: USB hub found
[    2.910000] hub 1-0:1.0: 2 ports detected
[    2.910000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.920000] ohci_hcd 0000:00:0b.0: OHCI Host Controller
[    2.920000] ohci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 2
[    2.930000] ohci_hcd 0000:00:0b.0: irq 111, io mem 0x18022000
[    3.000000] match id
[    3.000000] hub 2-0:1.0: USB hub found
[    3.010000] hub 2-0:1.0: 2 ports detected
[    3.020000] xhci_hcd 0000:00:0c.0: xHCI Host Controller
[    3.020000] xhci_hcd 0000:00:0c.0: new USB bus registered, assigned bus number 3
[    3.030000] xhci_hcd 0000:00:0c.0: irq 112, io mem 0x18023000
[    3.040000] xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
[    3.040000] xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
[    3.050000] usb usb3: No SuperSpeed endpoint companion for config 1  interface 0 altsetting 0 ep 129: using minimum values
[    3.060000] xHCI xhci_add_endpoint called for root hub
[    3.070000] xHCI xhci_check_bandwidth called for root hub
[    3.070000] match id
[    3.070000] hub 3-0:1.0: USB hub found
[    3.080000] hub 3-0:1.0: 1 port detected
[    3.080000] usbcore: registered new interface driver cdc_acm
[    3.090000] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[    3.100000] usbcore: registered new interface driver usblp
[    3.100000] csw_retry 100
[    3.110000] Initializing USB Mass Storage driver...
[    3.110000] usbcore: registered new interface driver usb-storage
[    3.120000] USB Mass Storage support registered.
[    3.120000] usbcore: registered new interface driver usbserial
[    3.130000] USB Serial support registered for generic
[    3.130000] match id
[    3.130000] match id
[    3.140000] match id
[    3.140000] usbcore: registered new interface driver usbserial_generic
[    3.150000] usbserial: USB Serial Driver core
[    3.150000] USB Serial support registered for GSM modem (1-port)
[    3.160000] match id
[    3.160000] usbcore: registered new interface driver option
[    3.160000] option: v0.7.2:USB Driver for GSM modems
[    3.170000] USB Serial support registered for Sierra USB modem
[    3.170000] usbcore: registered new interface driver sierra
[    3.180000] sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems
[    3.190000] u32 classifier
[    3.190000]     Actions configured
[    3.190000] IPv4 over IPv4 tunneling driver
[    3.200000] GRE over IPv4 tunneling driver
[    3.200000] ip_tables: (C) 2000-2006 Netfilter Core Team
[    3.210000] TCP cubic registered
[    3.210000] NET: Registered protocol family 10
[    3.220000] lo: Disabled Privacy Extensions
[    3.220000] tunl0: Disabled Privacy Extensions
[    3.230000] IPv6 over IPv4 tunneling driver
[    3.230000] sit0: Disabled Privacy Extensions
[    3.240000] ip6tnl0: Disabled Privacy Extensions
[    3.240000] NET: Registered protocol family 17
[    3.240000] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
[    3.250000] All bugs added by David S. Miller <davem@redhat.com>
[    3.270000] Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
[    3.280000] NAND device: Manufacturer ID: 0xc2, Chip ID: 0xf1 (Unknown NAND 128MiB 3,3V 8-bit)
[    3.290000] Spare area=64 eccbytes 56, ecc bytes located at:
[    3.300000]  2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
[    3.310000] Available 7 bytes at (off,len):
[    3.320000] (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0)
[    3.320000] Scanning device for bad blocks
[    3.630000] Options: NO_AUTOINCR,NO_READRDY,
[    3.640000] Creating 2 MTD partitions on "brcmnand":
[    3.640000] 0x000002600000-0x000007b00000 : "brcmnand"
[    3.650000] 0x000007b00000-0x000008000000 : "OpenVPN"
[    3.660000] SQUASHFS error: Xattrs in filesystem, these will be ignored
[    3.670000] SQUASHFS error: squashfs_read_data failed to read block 0x1979314
[    3.670000] SQUASHFS error: Unable to read metadata cache entry [1979314]
[    3.680000] SQUASHFS error: Unable to read inode 0x3b141a77
[    3.690000] VFS: Cannot open root device "mtdblock3" or unknown-block(31,3)
[    3.690000] Please append a correct "root=" boot option; here are the available partitions:
[    3.700000] 1f00             512 mtdblock0 (driver?)
[    3.710000] 1f01            1536 mtdblock1 (driver?)
[    3.710000] 1f02           32768 mtdblock2 (driver?)
[    3.720000] 1f03           30607 mtdblock3 (driver?)
[    3.720000] 1f04             256 mtdblock4 (driver?)
[    3.730000] 1f05             256 mtdblock5 (driver?)
[    3.730000] 1f06             256 mtdblock6 (driver?)
[    3.740000] 1f07             512 mtdblock7 (driver?)
[    3.740000] 1f08             512 mtdblock8 (driver?)
[    3.750000] 1f09             256 mtdblock9 (driver?)
[    3.750000] 1f0a             256 mtdblock10 (driver?)
[    3.760000] 1f0b             256 mtdblock11 (driver?)
[    3.760000] 1f0c             256 mtdblock12 (driver?)
[    3.770000] 1f0d             256 mtdblock13 (driver?)
[    3.770000] 1f0e             256 mtdblock14 (driver?)
[    3.780000] 1f0f             256 mtdblock15 (driver?)
[    3.780000] 1f10             256 mtdblock16 (driver?)
[    3.790000] 1f11           87040 mtdblock17 (driver?)
[    3.790000] 1f12            5120 mtdblock18 (driver?)
[    3.800000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)
[    3.810000] [<c0047250>] (unwind_backtrace+0x0/0xe4) from [<c03d499c>] (panic+0x68/0x194)
[    3.810000] [<c03d499c>] (panic+0x68/0x194) from [<c0009404>] (mount_block_root+0x238/0x288)
[    3.820000] [<c0009404>] (mount_block_root+0x238/0x288) from [<c0009700>] (prepare_namespace+0x160/0x1c0)
[    3.830000] [<c0009700>] (prepare_namespace+0x160/0x1c0) from [<c0009078>] (kernel_init+0x1c8/0x218)
[    3.840000] [<c0009078>] (kernel_init+0x1c8/0x218) from [<c0041b58>] (kernel_thread_exit+0x0/0x8)
[    3.850000] CPU1: stopping
[    3.850000] [<c0047250>] (unwind_backtrace+0x0/0xe4) from [<c00402f0>] (do_IPI+0xfc/0x180)
[    3.850000] [<c00402f0>] (do_IPI+0xfc/0x180) from [<c04bf8a8>] (__irq_svc+0x48/0xe8)
[    3.850000] Exception stack(0xcf83df98 to 0xcf83dfe0)
[    3.850000] df80:                                                       c05129a4 00000000
[    3.850000] dfa0: cf83dfe0 00000000 cf83c000 c050ebc8 c05300a8 c0530220 80000000 413fc090
[    3.850000] dfc0: 0000001f 00000000 c0563cd8 cf83dfe0 c0041bb0 c0041bb4 60000013 ffffffff
[    3.850000] [<c04bf8a8>] (__irq_svc+0x48/0xe8) from [<c0041bb4>] (default_idle+0x24/0x28)
[    3.850000] [<c0041bb4>] (default_idle+0x24/0x28) from [<c0041d1c>] (cpu_idle+0x40/0x94)
[    3.850000] [<c0041d1c>] (cpu_idle+0x40/0x94) from [<80008138>] (0x80008138)
[    4.080000] NVRAM LOG 16384 4537 20921
[    4.240000] Rebooting in 3 seconds..Digital core power voltage set to 1.0V

 

 

Message 38 of 74
Highlighted
Prodigy

Re: R7000 Firmware Bug 1.0.6.28

where is the panic error?

Message 39 of 74
Highlighted
Tutor

Re: R7000 Firmware Bug 1.0.6.28

[    3.800000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)

Message 40 of 74
Highlighted
Tutor

Re: R7000 Firmware Bug 1.0.6.28

Comparing the console output of firmware version 1.0.4.30 to firmware version 1.0.6.40 shows new drivers added for a wireless modem. Why?

 

[    3.080000] usbcore: registered new interface driver cdc_acm
[    3.090000] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters

 

[    3.140000] usbcore: registered new interface driver usbserial_generic
[    3.150000] usbserial: USB Serial Driver core
[    3.150000] USB Serial support registered for GSM modem (1-port)

 

[    3.160000] usbcore: registered new interface driver option
[    3.160000] option: v0.7.2:USB Driver for GSM modems
[    3.170000] USB Serial support registered for Sierra USB modem
[    3.170000] usbcore: registered new interface driver sierra
[    3.180000] sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems

Message 41 of 74
Highlighted
Star

Re: R7000 Firmware Bug 1.0.6.28

I'm running the latest BETA firmware with no problems, (V1.0.6.40_1.1.90)  As far as the new drivers are concerned, I dont care why they are using them, all I can say is thank you Netgear.  Now my android devices are able to connect reliably to the router and pull data as they should.  With v10430 all of my phones were extremely slow to receive any data and in most cases would appear to completely stall forcing me to disconnect from my WIFI when doing simple updates like facebook status, reading the news etc...  

 

BE FORWARNED, I GAVE UP ON USING MY R7000 AS ANYTHING BUT AN ACCESS POINT.  So yes, this beta works great for me in AP mode only.  I have not tested using the full router functionality.

 

 

Message 42 of 74
Highlighted
NETGEAR Employee Retired

Re: R7000 Firmware Bug 1.0.6.28

@JoeHanson Register your device and contact support.

ElaineM
NETGEAR Community Team
Message 43 of 74
Highlighted
Aspirant

Re: R7000 Firmware Bug 1.0.6.28

I upgraded from 1.0.4.30 to 1.0.6.28_1.1.83 back in late January. Since that time, I've tried all the settings but my 2.4 main network can't be used by any device. The 2.4Ghz guest network is fine as are both 5Ghz networks. 

 

Finally I got sick of it and downgraded back to 1.0.4.30 and all is well again. 

 

Netgear, this is really disappointing. You are usually much better than this. It's not like it's particularly easy to post here yet there are 5 pages of people with this problem. I wonder how many separate customers with issues each post here represents? I won't be upgrading again anytime soon, that's for sure.

Message 44 of 74
Highlighted
NETGEAR Employee Retired

Re: R7000 Firmware Bug

@nhoover We apologize for any inconvenience this may have caused you. Our engineers are aware and the fix is on the works. The firmware will be released soon.

ElaineM
NETGEAR Community Team
Message 45 of 74
Highlighted

Re: R7000 Firmware Bug

Will the release automatically invoke the Arlo function, or will there be an option to leave it off without having to drill down to find it?  This should be a user choice option for those of us who do not have any Arlo devices.

Message 46 of 74
Highlighted
NETGEAR Employee Retired

Re: R7000 Firmware Bug

There will be an option to disable the Arlo function for users who does not have Arlo devices.

ElaineM
NETGEAR Community Team
Message 47 of 74
Highlighted
Tutor

Re: R7000 Firmware Bug

That right there is a big part of the problem. One of the big complaints is that this should be opt-in, not opt-out. Why enable a feature by default when more than half of the user base won't use it or disable it immediately?

Message 48 of 74
Highlighted
NETGEAR Employee Retired

Re: R7000 Firmware Bug

I apologize but that should have been enable/disable.

 

However, let me see if I can get a word from our engineering department as to whether how it will be implemented by default.

ElaineM
NETGEAR Community Team
Message 49 of 74
Highlighted
NETGEAR Employee Retired

Re: R7000 Firmware Bug

Our marketing and engineers have been given this request and they are looking into implementing it in future firmware releases.

ElaineM
NETGEAR Community Team
Message 50 of 74