EA6500 Firmware 1.1.27 (Build 142736) Feedback Thread

Cisco Consumer Products
Product:                  EA6500
Classification:         Firmware Release History
IMPORTANT:
- The safest way to perform the firmware upgrade is to use a wired computer via web UI or Cisco Connect Setup tool.
- DO NOT power cycle the Router during the firmware upgrade process.
===========================================================================
Release Date: Oct. 12, 2012
Firmware version: 1.1.27 (Build 142736)
- Improved WAN to Wi-Fi throughput when the device is configured as a bridge device.
- Fixed IOT issue whereas the device can’t obtain IP address when it is connected behind certain cable modems.
===========================================================================
Release Date:           September 12, 2012
Firmware version:       1.1.27 (Build 141816)
- Add application feature access without Smart Linksys Wi-Fi account
- Bug fixes
===========================================================================
Release Date:           August 3, 2012
Firmware version:       1.1.26 (Build 140196)
- Initial release

camattin wrote:
Here is my experience with this firmware release thus far:
- Internet connectivity was broken after the FW installation. I had to do a factory reset in order to restore internet connectivity.
- Multiple times I keep getting the "Router is not connected" popup window, even though I am hardwired to the router. This has to be the most frustrating bug of all - when hardwired there is no way I couldn't be connected to the router.
Given that first issue above, it makes me so very glad I've disabled automatic firmware upgrades. If it had done this update while I was sleeping, I would have been even more frustrated than I already am at this router.
Since I'm still w/in my return period for this router, I do plan on doing some more shopping for its replacement. A router should not require as much "work" as this one has.
When you got the error "router is not connected" did you check if the leds were okay or on at the back panel of the router? My experience so far with installing or upgrading the firmware is to reset the device first before doing so. That is the work around I have always tried and works for me all the time. Have you tried by the way the Smart Wi-fi software for this router?

Similar Messages

E1500 Firmware 1.0.03 (Build 14) Feedback Thread

New firmware for E1500 has been released.
Release Date: Mar 1, 2012
Last Firmware Version: 1.0.03
Firmware 1.0.03 (build 14)
- Added control to the browser-based GUI, so that a user can manually enable/disable Wi-Fi Protected Setup.
- Resolved interoperability issue with ISP DHCP server that mandates client identifier option (option 61).
- Resolved issue with sending broadcast DHCP renewal message. The correct behavior is sending unicast message.
- Allow value of 255 in the 4th octet of L2TP server IP address.
Post your feedback here. Thanks.

Hey Cisco! Would have been nice to report here that you have created a new firmware version 10.0.04 that is supposed to resolve this issue! It's only been out there since 10 days. Who the H'$% looks at the firmware downloads when we've been disussing the issue in this forum!
Please upgrade your level of communication skills!
Nonetheless thanks for solving the issue.
Karel

E1200 v2 Firmware 2.0.02 (Build 3) Feedback Thread

New firmware for E1200 v2 has been released.
Release Date: Mar 2, 2012
Last Firmware Version: 2.0.02
Note: This firmware is only compatible with hardware version 2 (v2), but not with hardware version 1 (v1).
Firmware 2.0.02 (build 3)
- Added control to the browser-based GUI, so that a user can manually enable/disable Wi-Fi Protected Setup.
- Resolved interoperability issue with ISP DHCP server that mandates client identifier option (option 61).
- Resolved issue with sending broadcast DHCP renewal message. The correct behavior is sending unicast message.
- Allow value of 255 in the 4th octet of L2TP server IP address.
Post your feedback here. Thanks.

I'm not sure which firmware this bug was introduced, but my current router (e1200) is running on firmware 2.0.02. My problem is slow download speeds on my wireless N devices when WMM is enabled. When WMM is enabled, I'm getting download speeds of .5 MBPS. When I disable WMM, my download speeds jump to 20mbps. I have noticed this issue on the following wireless devices.
iPhone 4s running latest Apple OS
Acer a500 tablet running latest version of ice cream sandwich.
Asus (pce-n10) wireless-N network adapter running on windows 7 (64bit)
My upload speeds are not effected just download speeds.

E3200 Firmware 1.0.04 (build 1) Feedback Thread

Last Release Date: May 17, 2012
Last Firmware version: 1.0.04 (build 1)
- Resolved interoperability issue with ISP DHCP server that mandates client identifier option (option 61).
- Resolved issue with sending broadcast DHCP renewal message. The correct behavior is sending unicast message.
- Resolved issue with accessing browser-based GUI via HTTPS using Internet Explorer and Firefox.
- Resolved DHCPv6 binding issue.
- Added MTU option in router advertisement.
Please post your experience or feedback with new firmware here!

djec64 wrote:
Hello,
Just bought this router and update the firmware. 2 points.
Not being able to connect a USB printer for MAC OSX is a show stopper. I will return it and take another brand if a solution is not provided shortly.
So far I am not impressed by the speed. No improvement in range over Belkin 300N
Regards.
What specific version of Mac? Is that the Lion? Are you setting up virtual USB printer using the latest version of Cisco Connect?

EA2700 Firmware 1.1.40 Build 162751 Dropping Wireless Clients

Hello,
We have noticed on several EA2700 units that the recent 1.1.40 update has caused wireless clients to be disconnected en-masse periodically.
It does not seem to be related to client devices, as we have one "All Apple" environment where iPhones are simultaneously disconnected (but wired computers are fine) and a separate environment where the same thing is happening with only Samsung tablets and handhelds.
Rolling back to the previous firmware (1.1.39 Build 145204) is an option in the Troubleshooting section of the device, but in order for it to work properly you have to do the following:
a) Login to the Connectivity section and turn-off the Auto-Update feature
b) Login to the Troubleshooting section and use the rollback feature to previous firmware
c) Using a paperclip for 30 seconds (all lights flash), reset to factory settings. (192.168.1.1 on LAN port with Internet disconnected)
d) Login and reconfigure your settings (Wireless SSID and Passwords)
If you do not perform the hard factory reset using the reset button on the bottom after downgrading the firmware, you will be able to see the SSID but not connect any devices. We believe this is due to the new "wireless drivers" that were upgraded as per the changelog in the 1.1.40 firmware, and are probably also responsible for the bug with wireless devices disconnecting.
We engaged with the live chat to give them a heads up on the issue but didn't seem to get anything but a script to solve typical wireless issues; Hopefully this post is helpful and catches the eyes of Linksys engineers. We have a lot of these devices in use, and so far have rolled back about 10 of them so far. Unfortunately when you only loose wireless for a few minutes every hour or so, people don't notice too quickly. Those with multiple wireless devices and wired connections seem to figure it out.
The fact that all devices seem to disconnect at once suggest the 1.1.40 is having resource issues (running out of memory causing WPA services to restart), or suffering from some sort of other kernel/device driver issue related to the upgrade. Without debug logs we don't have a smoking gun, but the observations seem indicative of a problem.
We chose the EA line for our customers because the autoupdate allows us to often upgrade out of bugs with certain wireless clients, but in this case we upgraded into a bug affecting all clients.

Good news,
Since we have a number of devices still under warranty, we have been able to engage Belkin/Linksys'sCustomer Assistance Team (CAT), the next level of support from the email/Chat/phone queues.
Following disclosure of a number of scenarios and additional problem description details we were engaged by the product Sustainment Engineering team. We provided more details, reproduction steps and example configurations.
Although we still don't have our hands on a 1.1.39 build to mitigate risk of not being able to roll-back if a 1.1.41 does not resolve the problem, it seems likely that the engineering team is going to have a closer look and get this resolved.
One recommendation, that we have not yet tried that came out of all the discussions, was to manually apply the firmware from the website. I don't expect much to change, as I am pretty sure they would employ a simple MD5SUM check.
Although we have rolled back a number of these so far with 100% resolution (using the process described), it is only about 5-10% of the devices configured to auto-upgrade that have been reported as having a problem so far, so there is still a good chance that not every device is affected, though we have been able to reproduce this easily, and all of our devices share identical configurations except for SSID information.
The EA2700 is good value when it works. Lots of resources, 64MB RAM and 64MB FLASH, decent Broadcom Gigabit PHY and Dual Spatial Radios on a very compatible Broadcom Wireless chipset make it a great little AP bridge for 700-1000 sq ft. MDUs where we provide 80 Mbps service which it can handle in that environment at 40Hz.

Feedback Thread: Firmware MU02 for M550

Please use this thread to provide any feedback for firmware MU02 for M550.
Firmware revision MU02 for the Crucial M550 (all form factors) is now available. This firmware update applies to the M550 SSD (all form factors), and should not be applied to any other Crucial SSD model.
Visit this page to download the firmware update: http://www.crucial.com/support/firmware.aspx
Release Date: 01/8/2015
Firmware for the M550 (all form factors) is being updated from version MU01 to MU02. The M550 is updateable to this new firmware starting from previous versions using tools provided by Micron.
This update will be mandatory cut-in for new product built in Micron factories, and is an OPTIONAL update for any drive in the field. For end users, it is recommended if the user is experiencing or wishes to prevent an issue related to the following items.
Version MU02 includes the following changes:
Improved stability, Efficiency, and Performance during power state transitions
Improved handling of environments with unstable power supplies
Improved handling of environments with SATA interface signal integrity issues
Improved response time for SMART read commands
Corrected error handling NCQ Trim Commands
Corrected reporting of SMART Attribute 5
Additional details can be found in the firmware guide.

Hejsana wrote:
Hi everybody! Just downloaded MU02 Update, create a bootable CD from the ISO file, tried to boot my MacBook Pro 17" Mid 2010 with the created CD. After loading it automatically started programming... After some time I got the following message: "Firmware Update on /dev/sda failed with status 13... Device Name: /dev/sdaFirmware Update on /dev/sda Failed!CMD_STATUS: Command aborted by the driveSTATUS_CODE: 13Your system will now return to normal operation following a reboot" I thought that the CD is damaged. Took another CD and created another bootable CD. Got the same error. Am I doing something wrong? Thanks in advance for your suggestions...I haven't tried this as I'm using a different model of Macbook Pro and I'm not running a M550. But it seems that Crucial have made a major change from previous firmware updates for M4 and M500 SSDs. In the past they used a SYSLINUX/ISOLINUX bootloader which in turn used memdisk to load a FreeDOS image which contained FreeDOS and the actual firmware updater. This meant that if the CDROM installer didn't work, or the Mac didn't have a CDROM, there were no other options. This method never worked properly for EFI booting from USB in a Mac, although some "hacks" were suggested in forum posts that worked for some people. However it seems that now Crucial are using a different method.If we take a look at /boot/isolinux/isolinux.cfg DEFAULT sd
LABEL sd
KERNEL /boot/vmlinuz
INITRD /boot/core.gz
APPEND quiet base loglevel=3 waitusb=10 superuser rssd-fw-update rssd-fwdir=/opt/firmware rssd-model=M550This means it loads an actual linux kernel - vmlinuz. Now it should be possible to modify isolinux.cfg to change the kernel arguments to work better with the actual Mac hardware or any other hardware that is supported by linux. It should be possible to build a EFI bootable USB updater that loads the same kernel and firmware, but we can modify that with all the correct parameters for the Mac. Unfortunately I don't have the same model Mac or the same SSD, so while I might have a look at making the EFI bootable installer, I can't test the complete firmware update process.

EA6500 Firmware Ver 1.1.40

I have a EA6500 with firmware version 1.1.28. I've been trying to upgrade to firmware version 1.1.40 but three-quarters the way through the installation of the firmware upgrade, the system stops and says "the firmware update did not complete successfully. Please try again later." "We've encountered an unexpected error, please visit the technical support site." This has happened many times over many days. I visited the technical support site but cannot find any documentation on the error I'm receiving. Can anyone help?

Hi gorbie,
Firmware version 1.1.40 (build 153731) is for the Linksys EA6500 V2. If your router doesn't say any hardware version on it then that means you have the version 1 of the EA6500.
Help, learn and share

Feedback Thread: Firmware MU02 for BX100

Please use this thread to provide any feedback for firmware MU02 for BX100.
Firmware revision MU02 for the Crucial BX100 (all form factors) is now available. This firmware update applies to the BX100 SSD (all form factors), and should not be applied to any other Crucial SSD model.
Visit this page to download the firmware update: http://www.crucial.com/support/firmware.aspx
Release Date: 04/14/2015
Firmware for the BX100 (all form factors) is being updated from version MU01 to MU02. The BX100 is updateable to this new firmware starting from previous versions using tools provided by Micron.
This update will be mandatory cut-in for new product built in Micron factories, and is an OPTIONAL update for any drive in the field. For end users, it is recommended if the user is experiencing or wishes to prevent an issue related to the following items.
Version MU02 includes the following changes:
•Improved Device Sleep and Slumber transitions.
•Corrected SMART attribute threshold values.
•Improved general reliability and stability.
Additional details can be found in the firmware guide

I think that right now there are 3 ways firmware update can theoretically be done:
1. Online update through Crucial Storage Executive - the proper firmware file is downloaded by Storage Executive from Crucial/micron server
2. With Bootable ISO image provided by Crucial < the one you can download from firmware download page
3. Manual Firmware Update through Crucial Storage Executive - you load the .zip file with firmware update package
I believe that the problem with "3" is that Crucial does not provide .zip files with firmware update packages. The .zip files we can download contains bootable ISO images, not the firmware update packages. Because of that you are probably right that this option should be removed from Storage Executive's UI.
I think that, technically, within the same firmware revision, updating with the firmware package would be the same as an online update where the firmware file is downloaded by Storage Executive from micron server.
If the Storage Executive didnt' work for you I would suggest trying manual Bootable ISO, take a look at post #6.

Feedback Thread: Firmware MU02 for MX100

Please use this thread to provide any feedback for firmware MU02 for MX100.
Firmware revision MU02 for the Crucial MX100 (all form factors) is now available. This firmware update applies to the MX100 SSD (all form factors), and should not be applied to any other Crucial SSD model.
Visit this page to download the firmware update: http://www.crucial.com/support/firmware.aspx
Release Date: 03/10/2015
Firmware for the MX100 (all form factors) is being updated from version MU01 to MU02. The MX100 is updateable to this new firmware starting from previous versions using tools provided by Micron.
This update will be mandatory cut-in for new product built in Micron factories, and is an OPTIONAL update for any drive in the field. For end users, it is recommended if the user is experiencing or wishes to prevent an issue related to the following items.
Version MU02 includes the following changes:
    Improved stability, Efficiency, and Performance during power state transitions
    Improved handling of environments with unstable power supplies
    Improved handling of environments with SATA interface signal integrity issues
    Improved response time for SMART read commands
    Corrected error handling NCQ Trim Commands
    Corrected reporting of SMART Attribute 5
Additional details can be found in the firmware guide.

Will this firmware be available soon in the Crucial Storage Executive program? When I do a check firmware upgrade, it tells me I am on the latest firmware and do not see any downloads for JUST the firmware update file that i can then install manually via Storage Executive. I have the latest Crucial Storage Executive program installed and a 256GB MX100 on MU01. Also on a nitpicky note, there should be an Close, X in the upper right of the Storage Excecutive program for closing the program; having to close via right-click and close on taskbar or ALT+F4 is not very good software design practices.

EA6500 firmware question

Hi, where can i get the 1.1.28.147876 firmware for EA6500?

@varlex Hi! The firmware that you're looking for can be downloaded through the Linksys support site. You may refer to this link: http://support.linksys.com/en-us/gplcodecenter?gplsku=#EA6350. Look for the model number and you should see it. Hope this will help you.

Feedback Thread: Firmware MU05 for the M500

Please use this thread to provide any feedback for firmware MU05 for the M500.
Firmware revision MU05 for the Crucial M500 (all form factors) is now available. This firmware update applies to the M500 SSD (all form factors), and should not be applied to any other Crucial SSD model.
Visit this page to download the firmware update: http://www.crucial.com/support/firmware.aspx
Release Date: 03/25/2014
Firmware for the M500 (all form factors) is being updated from version MU03 to MU05. The M500 is updateable to this new firmware starting from previous versions using tools provided by Micron.
This update will be mandatory cut-in for new product built in Micron factories, and is an OPTIONAL update for any drive in the field. For end users, it is recommended if the user is experiencing or wishes to prevent an issue related to the following items.
Version MU05 includes the following changes:
Improved Drive latency performance in applications with SMART polling
Improved Compatibility with 3rd party encryption management software
Corrected Reporting of SMART attribute 196 and 183
Increased thermal throttling response on 960GB Capacity for greater reliability
Corrected Upgrade issues experienced on MU03 by some customers
Numerous Bug fixes and stability improvements
Additional details can be found in the firmware guide

Hello, in case of the Intel X79 chipset, which has a SATA controller of the C600 workstation chipset integrated it is impossible to install the firmware ...with my PCIe Addon-Card with USB3 (Renesas) / SATA6 (Marvell) it is impossible, too; I don't use Win7 so I must use the .iso for update ... any suggestion please; does onybody know why the SSD after only 1 day shows a HD tune like this: what has happened, I installed it, made a partition and copies about 100 GB of my virtual machines; and had them run for about 16 hours:- one is only a private WINS server (WinNT 4.0)- one is my private DNS server (2.5 GByte vmdk)- one is my sixxs tunnel provider (4 GByte vmdk)- one is my personal old proxy (squid 2.5) (10 GByte vmdk)- one is my personal new ssl-bump proxy (squid 3.3) (8 GByte vmdk)- one is my personal mail server (Postfix/Cyrus) (16 GByte vmdk)and a few more but not every did run at all ... [ speed doesn't really matter, because this SSD is connected not at the onboard SATA controller - X79/C600; I connected it on a PCIe Addon controller that has additional external USB 3 ports (Renesas) and additional SATA 6 ports (Marvell) ]the firmware update was done on another PC with Intel Z77 chipset; but next time I'd would like to do this without the need of another PC .- the support of the Marvell controller would be fine; Thanks,Walter

Flex and Flash Builder Beta Feedback Survey

Hey guys,
Please take 15 minutes to give feedback on the beta releases here. Your input is greatly appreciated. Please also pass this along to other individuals who might be using the betas.
Kind regards,
Vera

Hi Glenn,
I updated the link yesterday afternoon, but for some folks it seems to still be going to the old survey. I'll put a redirect on the old survey, but please try going to the survey here.
Vera

My Cloud Firmware 4.01.04.422 Feedback

WD is pleased to announce the update release of My Cloud Firmware Release 4.01.04-422.
Please follow the instructions when doing the update.
Please feel free to post your questions and experiences in this thread.
Important:
Before updating to the latest firmware, it is recommended that you’ve installed the most recent updates and service pack on your computer.
For Windows®, go to the Start menu and select Windows Update
For Mac®, go to the Apple® menu and select Software Update
Resolved Issues:
Resolved issue of inability to stream audio files after updating to iTunes 12.1
Resolved issue of POODLE (CVE-2014-3566) SSLv3 security vulnerability
Resolved stability issue when attaching a USB drive that contains previously created Time Machine backups
Resolved issue of Safepoint instability

doylecolmdoyle wrote:
My device was auto-updated to the latest firmware (has been doing so since I purchased about 2 years ago) and I now have the issue of the capacity of the device not displaying on the dashboard and also my cloud access dropped and I cant connect from external networks....
Why release firmware that is going to cause issues.... I had this capacity issues before and the previous firmware seem to fix this problem but now its back... well done WD!
Hi doylecolmdoyle,
We have passed this along to support.

RE6500 Time Incorrect After Firmware 1.0.03 Build 6, Une 10, 2015 Update

Since performing the above update to my RE6500, the time now starts out on Wed, Dec 31, 1969, and begins counting upwards from there. Any thoughts on how to fix this?

Try to reset the extender and reconfigure its settings. Then reboot the extender to refresh the connection.

Feedback Thread for MX200

Please use this thread to provide any feedback for firmware MU02 for MX200.
Firmware revision MU02 for the Crucial MX200 (all form factors) is now available. This firmware update applies to the MX200 SSD (all form factors), and should not be applied to any other Crucial SSD model.
Visit this page to download the firmware update: http://www.crucial.com/support/firmware.aspx
Release Date: 07/14/2015
Improved Read Performance on small address spans
Improved Random Write performance on transfers not aligned to 4KB address boundaries
Improved Acceleration Capacity Recovery after TRIM and SANITIZE commands
Added Informative SMART thresholds for Attributes 202 and 5
Added Support for READ DMA BUFFER, WRITE DMA BUFFER, and DOWNLOAD MICROCODE DMA Commands
Bug Fixes and Stability Improvements
Additional details can be found in the firmware guide

Before degradation: EventDataBootTsVersion 2
BootStartTime 2015-07-20T10:44:16.763282500Z
BootEndTime 2015-07-20T10:45:55.602469800Z
SystemBootInstance 65
UserBootInstance 62
BootTime 24652
MainPathBootTime 9352
BootKernelInitTime 27
BootDriverInitTime 367
BootDevicesInitTime 1394
BootPrefetchInitTime 0
BootPrefetchBytes 0
BootAutoChkTime 0
BootSmssInitTime 3050
BootCriticalServicesInitTime 244
BootUserProfileProcessingTime 171
BootMachineProfileProcessingTime 452
BootExplorerInitTime 2946
BootNumStartupApps 26
BootPostBootTime 15300
BootIsRebootAfterInstall false
BootRootCauseStepImprovementBits 0
BootRootCauseGradualImprovementBits 0
BootRootCauseStepDegradationBits 0
BootRootCauseGradualDegradationBits 0
BootIsDegradation false
BootIsStepDegradation false
BootIsGradualDegradation false
BootImprovementDelta 0
BootDegradationDelta 0
BootIsRootCauseIdentified false
OSLoaderDuration 443
BootPNPInitStartTimeMS 27
BootPNPInitDuration 1608
OtherKernelInitDuration 134
SystemPNPInitStartTimeMS 1736
SystemPNPInitDuration 239
SessionInitStartTimeMS 1982
Session0InitDuration 1623
Session1InitDuration 94
SessionInitOtherDuration 1333
WinLogonStartTimeMS 5033
OtherLogonInitActivityDuration 750
UserLogonWaitDuration 323 And after:
BootTsVersion 2
BootStartTime 2015-07-20T11:50:56.903944300Z
BootEndTime 2015-07-20T11:53:55.942009700Z
SystemBootInstance 66
UserBootInstance 63
BootTime 112728
MainPathBootTime 90228
BootKernelInitTime 27
BootDriverInitTime 365
BootDevicesInitTime 1914
BootPrefetchInitTime 0
BootPrefetchBytes 0
BootAutoChkTime 0
BootSmssInitTime 3074
BootCriticalServicesInitTime 89
BootUserProfileProcessingTime 169
BootMachineProfileProcessingTime 386
BootExplorerInitTime 83554
BootNumStartupApps 27
BootPostBootTime 22500
BootIsRebootAfterInstall false
BootRootCauseStepImprovementBits 0
BootRootCauseGradualImprovementBits 0
BootRootCauseStepDegradationBits 0
BootRootCauseGradualDegradationBits 0
BootIsDegradation false
BootIsStepDegradation false
BootIsGradualDegradation false
BootImprovementDelta 0
BootDegradationDelta 0
BootIsRootCauseIdentified false
OSLoaderDuration 445
BootPNPInitStartTimeMS 27
BootPNPInitDuration 2119
OtherKernelInitDuration 155
SystemPNPInitStartTimeMS 2269
SystemPNPInitDuration 240
SessionInitStartTimeMS 2515
Session0InitDuration 1621
Session1InitDuration 95
SessionInitOtherDuration 1356
WinLogonStartTimeMS 5589
OtherLogonInitActivityDuration 528
UserLogonWaitDuration 256
The problem seems to be BootExplorerInitTime . I would reinstall Win 8.1 but the next week I hope to change my pc to Windows 10 so I will wait and see if this can be fixed on this way.
Thanks a lot bogdan.
Best regards.

EA6500 Firmware 1.1.27 (Build 142736) Feedback Thread

Similar Messages

Maybe you are looking for