Ideapad z710 windows 7 wireless issue

Hello. First of all, I would like to say I love how great the products lenovo puts out there.
Second of all, I am frustrated. I just purchased a Lenovo z710 and dualbooted with Windows 7 since Windows 8 was my primary OS (ew).
So I downloaded all of the drivers necessary for the Windows 7 OS, and all of them work...but my wireless.
I am running the 64bit model of 7. I cannot get the wireless driver to work or "install" Much help would be appreciated!!
Solved!
Go to Solution.

There was a long thread on one of the boards here that was about the exact same issue but on a different laptop.
Turned out the problem was UEFI, but they were doing it with an SSD. In there case UEFI had to be updated.
But there is another thread specifically with your exact same issues.
https://forums.lenovo.com/t5/IdeaPad-Y-U-V-Z-and-P-series/ideapad-z710-windows-7-wireless/td-p/12718...
There are some solutions there that may work for you.
As for the company not caring about any software other than windows 8, if you get right down to it, the system worked perfectly well with the supplied OS, it was your choice to downgrade. Did you check to see if this was possible before purchasing the system? I feel the same way as most of you probably do, I like Windows 7 much more than Windows 8. Windows 8.1 is kind of a median version between the two. If you don't have a touch screen, it still is not fun. But Windows 7 mainstream support ends in January and extended support dies in January 2020. That means after January you will have to pay Microsoft to get help with windows. If you look around you will find that ALL manufacturers have either totally stop selling systems with Windows 7 or are pretty close to it. And I can assure you after January they will stop all sales of Windows 7. At that point if there are not drivers for your devices, chances are pretty good there never will be. Very few OEM's continue writing drivers for operating systems that are in the process of being phased out.
Hoov
Microsoft MVP - Consumer Security
SpywareHammer.com

Similar Messages

I have had wireless issues sense Leapord, any fixes yet? its a shame that my wife has to sit in front of our 27 inch imac on a $300 Windows computer to use the web effectively. I have tried all fixes and some work while others don't but all temporary

This Lion wireless issue has become more than just an irritation, so much so, my wife has resorted to sitting in front of a 27 inch imac with a 300 dollar Walmart Windows computer to get the bills paid and use the web. And yes, there is not a fix out there I haven't tried over the last year or so, some worked and some didn't, but all were temporary at best. Same issue with my Macair, I wonder if its a hardware issue, like the video card in my 2006 MBP, it went out after the warrenty and then I found out there was a calss action suit going on over it, unfortunately Apple wouldn't cover it and wanted 7oo bucks to fix it, sold that as parts.
While i really like me Macs, I own three, I may have to bow out and stick with LINUX, that has yet to let me down, anyone know if Mountain will fix this issue? or are we all just waiting for defective WiFi cards to fail at our own expense, PS, got three Macs for sale.

Sounds like you're getting kernel panics, which are usually, but not always, caused by hardware problems, with memory being one of the regular culprits.
First thing I would do is to get our your original OS X disks, insert the first one (should say 'AHT version x.x' in small print on the label - if not, find the one that does), and reboot holding the Alt key down. Choose the Apple hardware test, and when prompted, choose the extended test. If you have either of the TechTool programs, they can do similar testing. Does that identify any hardware issues?
Next, I'd download rember from http://www.kelleycomputing.net/rember/ . This is a memory testing program that you can set to run overnight. Does it come up with any errors? If so, try resetting your memory card(s) by removing and putting back into the computer. Rerun memory test.
This FAQ will provide other details: http://www.thexlab.com/faqs/kernelpanics.html

Macbook Pro (Late 2008) - Windows 7 64-bit, Bootcamp 3.1 - Wireless Issue

Hi Everyone,
I have a Macbook Pro (15-inch, Late 2008) model with Snow Leopard and Windows 7 64-bit dual boot. I have done a search and cannot find any reference to this problem on my hardware.
I have had no issues in Windows 7 when using Bootcamp v3.0. In the last week I have upgraded to Bootcamp v3.1. (completed twice, rolled back in between to prove that the issues was related to the Apple Update)
After I update to v3.1, I have issues with my wireless network. The network cannot resolve the name for any internet address. I can connect to wireless networks (tried multiple networks), all the DHCP settings seem to be retrieved correctly (Gateway, DNS etc) and I can ping local and machines outside my network without an issue provided I use the IP address. (Skype works - which uses direct IPs rather than names I have found over time)
As soon as I use a name for a destination for Web traffic, Mail, pinging (any application), my Macbook Pro cannot resolve the address and just bombs out.
If I connect to a wired network, the machine works perfectly and name resolution on that interface works. If I rollback (using Windows 7 rollback capability) to before the v3.1 Bootcamp is installed, the wireless networking also works perfectly.
I noticed this in the support area at apple:
http://support.apple.com/kb/TS3196
But this refers to wireless issues in Bootcamp drivers prior to v3.1 and on 13 inch Macbook. Wonder if this is a similar issue or related?
Anyone else seen this or point me in the direction of a fix?
Thanks,
Thommo

I'm looking into running Windows 7 64bit on the exact same MBP you have, so I'm curious as to whether or not you've found a solution yet outside of the forums.
Do you think it might be that the bootcamp 3.1 update is only for Windows 7 32bit and not for the 64bit version?

Satellite U500 - Windows 7 64bit (after clean install, wireless issues...)

Good night,
I've just installed windows 7 Professional x64. Now I'm experiencing some wireless issues such as constant breaks on the wireless connection (every 5 minutes more or less). I've tried to install the lastest drivers for the wireless LAN adapter, without success.
By the way, I have a Toshiba Satellite U500.
Any help? :)

It's a U500/00k? Model PSU9MA-00K013.
I havent actualy managed to access windows at all. The install problem has come up "out of the box" so checking any settings is impossible.
It just keeps looping back to the same error message. The only software I have is what came on the hard drive, and an XP istall disc that came with the package. According to the manual, if i use the XP disk it will wipe XP completely.
So frustrated right now.

If you have a Blue Screen / Error due to Wireless issues (B110a), fix in here.

For the original thread created by somebody else, please see here:
http://h30434.www3.hp.com/t5/Printer-All-in-One-Install-and/B110a-network-connection-problem/m-p/319...
Here's a youtube video of what happened to me: http://www.youtube.com/watch?v=adE1kq36ld4
I'm reposting it here so it can hopefully help some of you guys if anybody else stumbles across this. In short, my printer was fresh out of the box and I attempted to connect it to the wireless network. It would throw a blue screen on the LCD with an error of B8126AD6.
I narrowed it down to an issue with DHCP. For some reason the printer connects to the wireless access point but as soon as it tries to get an IP address from the DHCP server it crashes with that blue screen and the error code in the first post above. This look like a massive bug in the printers firmware! For reference my router is a Billion 7401VGPR3 which is acting as my default gateway and DHCP server. I have a Linksys WRT54G as my Access Point for the house.
To solve it, I turned DHCP off on my router and then tried connecting the printer to the wireless network. This time it connects fine but you still can't talk to it because it doesn't have a proper IP address. If it still doesn't connect properly, try turning WPA/WPA2/WEP off on your Access Point. Leave it completely open for a moment until you can reach the web interface (as below).
To fix the IP issue, I then went into the Settings menu on the printer and printed the "HP Network Configuration Page". Note that under the Wireless menu option there are a couple of different "Print Network Test Page" options. I believe it's the 2nd one that I selected. You'll know you have the right one when it prints out the page with the following info:
IPv4 IP Address
Subnet Mask
Hostname
Default Gateway
Primary DNS
etc, etc.
Take note of the IP Address from the printout above and the Subnet Mask. My IP was 169.254.73.5 and subnet mask 255.255.0.0. Now I manually configured my computers IP address to be similar (within the same subnet): 169.254.73.10 with the same subnet mask.
Now you can load up the web interface of the printer using http://169.254.73.5 in my case. (You should also be able to ping the printer at this point too). In here you have a Network tab where you can now manually set the IP Address of the printer. Set the address you want it to be in your network (in my case 192.168.0.3 with a subnet mask of 255.255.255.0 and default gateway 192.168.0.1 and dns server 192.168.0.1).
Once I clicked OK I changed my PC's IP back to normal, and I can now reach the printer on its IP address set above. YAY!
The great thing is, in the web interface you get a million more options to play with. You can manually set the IP address, gateway, DNS, wireless settings such as WPA1/WPA2 AES/TKIP Encryption, WPA Passkey, etc. So if you had to set the Access Point to completely Open, setup the encryption again and put the passkey in here. When I did this I had to go back into the Settings menu on the printer LCD and select "Disable Wireless" then "Enable Wireless" to force it to re-join the network.
Finally I went into the Settings menu again and Updated the software on the printer. I don't know if the new software fixes the bug or not - I haven't tested it (can't be bothered!).
Hopefully this will help some of you guys out there too!
EDIT: I've just stumbled across another couple of posts with similar results to mine:
- http://h30434.www3.hp.com/t5/Printer-networking-and-wireless/How-to-install-Photosmart-B109n-z-on-a-...
- http://forums.techguy.org/networking/627989-hp-6980-printer-wireless-problem.html

Many thanks to gardz for an exhaustive overview on this critical problem with the B110a printer!
I am happy to report that I have managed to set the printer to a static IP and am now able to connect to it wirelessly from my home computers, and also able to use the web apps and ePrint features on the printer. The printer shows the IP address and I am able to use the EWS (Embedded Web Server) to connect to its IP address from my PC's internet browser. The Wireless Network Test Report also showed no problems. I have also completed the Product Update on the printer, and there are no more pending updates now.
However, the core wireless problem is still not satisfactorily resolved.
I get the BSOD and blinking-lights error ("Please turn off printer and then on"), only if I start the printer when Wireless is enabled on the printer. If wireless is disabled prior to printer boot, there is no error.
The workaround I have adopted for now, is to always switch off the printer's wireless, before switching off the printer, and enabling the wireless setting only when I need to print/scan.
Is this happening with anyone else? Why would the printer crash if it boots with wireless enabled? If it is already set to a static IP, why would it still conflict with the DHCP on the router?
My router is perfectly working, it is in the same room as the printer, so the signal strength is good. The printer itself is quite stable except for this crash-after-boot-if-wireless-was-enabled issue on the printer.
I made the mistake of connecting the USB cable to my primary computer before installing the printer drivers, so even the USB option is not working (Windows recognizes the printer as an unknown USB device). If anyone can point me to the printer drivers (inf files), I would be grateful. The CD does not have the driver files in a convenient location. It seems to be embedded within the setup package somewhere.
Gardz and PrintDoc, I hope you can help us out on this one. I know many B110a users are struggling with the wireless issues, so HP needs to release a firmware fix and driver update soon. Wireless ought to work out-of-the-box, as this product is aimed at the SOHO users.

This is a workaround for the MBP wireless issue

There have been many topics on the MBP wireless issues already, but I thought some people might find this workaround helpful.
Firstly, my system is a 2.2Ghz MBP, running 10.4.10, and also airport extreme update 2007-04. I am using an airport express base station. My previous Powerbook never had any wireless problems, so I really couldn't blame the basestation for the MBPs poor wireless.
Warning - The workaround requires a little bit of work in the terminal. A little bit of understanding of how networks work is assumed here as well. So it is probably not for everyone ...
What I have observed - whenever the MBP loses connection, the airport basestation IP and MAC addresses are missing from the ARP table.
- To view the ARP table, type (in a terminal window) arp -a.
So, when the MBP wireless hangs, open up the terminal and type that in.
Do a Cntrl-C if the arp command is hanging and not returning anything.
In normal situations, a list of IP addresses and MAC addresses will show up.
As others have already noted, clicking on the airport icon in the menubar, will magically bring the wireless back to life. When this happens, the ARP table also gets magically populated correctly. Coincidence? I think not!
So, the workaround is to store a PERMANENT entry in the ARP table for the airport basestation IP and MAC address. In my case, I can use the Airport Utility software to confirm what the basestation IP and MAC addresses are (note MAC address = Airport ID in Airport Utility). I found the basestation IP=10.0.1.1 and the MAC=0:11:24:07:d7:f
To create a permanent ARP table entry for my airport basestation, I opened up a terminal window, and did the following -
1) login to my administrator account
2) type in the following command sudo arp -s 10.0.1.1 0:11:24:7:d7:f
3) type in my administrator password to authorise the change
4) type in (to confirm the changes have been made) arp -a
5) logout of my administrator account (from the terminal)
Ever since I did this, my MBP wireless performance has been flawless.
Note, if you shutdown or restart your computer, the arp entry disappears. This is ok for me as I hardly ever power down my MBP. As insurance I have added an account startup item to remind me to do the arp table entry.
This workaround is great for me because I don't have a need to use multiple wireless networks. It might not be practical for people who roam around onto different networks.
Give it a go and see if it works for you.
Message was edited by: michael louey

OK, after some further experimenting, I changed the multicast rate on my airport express. It was set at 6Mbps, and I changed it to 2Mbps.
I have read that the default multicast rate for previous 802.11g versions of Airport basestations is actually 2mbps. Excellent results so far !! I have set up a terminal command to continuously ping my airport router address every 15 sec, and there have been virtually no dropped packets so far over many hours.
ping -i 15 10.0.1.1
Interestingly, in Apple's Airport Admin software in my MBP there is no option to set the rate at less than 6Mbps (!!!!), so I had to use the Windows XP version of Airport admin software to make this change using a windows machine. Using the XP software you can set the muticast rate as low as 1Mbps.
If you are using Apples airport admin software (Tiger and Leopard) and you commit any sort of change in settings, the multicast rate will be re-set at a minimum of 6Mbps. My understanding of the multicast rate is that setting it too high is similar to shrinking the coverage area of the basestation, and limiting access only to clients who can transmit at the required multicast rate.
So my new theory is that the dropouts are caused by the MBP dropping off the airport due to not being able to achieve the set multicast rate. (this could be due to factors such as low signal strength, excessive interference or noise).
If you are using Apples more recent Airport admin software, you are having a minimum 6mbps muticast rate set, and this might be too high for your particular environment.
Just a theory.
(oh yeah, I enabled interference robustness on the MBP and the basestation just for good measure)

Linksys Smart Wi-Fi Device List Not Finding Windows 8 Wireless Adapter

I recently upgraded my Wi-Fi router to an EA3500 and am controlling it using Smart Wi-Fi running on a wired Windows 7 machine.
So far, I have been able to add devices to the network without issue and each of those connections works fine. All, except my TV, have been Windows 7 based machines.  Smart Wi-Fi Device List has been able to "see" each device and I have been able to add them to that list as well.
I am attempting to add a Windows 8 desktop computer to the network which is using a external USB wireless adapter. That computer can see and connect to the network through the EA3500 and the connection seems to work fine. The only issue is that its adapter does not show up in the Device List.
My questions:
1) Does the Device List do anything else besides showing a list of devices I chosen to add to my network?
2) How do I get my Windows 8 wireless adapter to show up in the Device List?
Thanks In Adance!
Solved!
Go to Solution.

MAC devotee wrote:
I would like to chime in here too. I also have the same issue as described on an older Mac desktop. The ethernet port has failed so it connects only via the AirPort wireless. My issue is IMPORTANT because until this devices shows up on the Device List I cannot apply the Parental Controls. Joining Orloldman for an answer... (Thanks!)
Try the following:
1.       Disconnect the computer from the wireless network
2.       Remove wireless network profile on your computer
3.       Reboot the computer and power cycle the router
4.       Reconnect to the wireless network
5.       Check if the computer shows up on the device list.
If it is still not showing, reset and reconfigure the wireless router.

Consumer Notebooks and Windows 8 - Wireless/BT/WWAN & Radio controls

The content in this tread is for Consumer Notebooks that HP has tested with Windows 8 upgrade. Information may be useful for others, but drivers, applications and/or bios references are related to systems HP has tested and are providing updates for and may not work on other systems.
To determine if your specific system is one of those that HP has tested With Windows 8 and to download the instructions guiding you through an upgrade please go here and enter your Product Number
There are certain requirements that must be fulfilled in order for the wireless devices (WLAN/BT, WWAN), the wireless button (enable/disable wireless) and the Airplane Mode feature to all work in sync on Windows 8.
Requirements:
-  Updated Windows 8 BIOS with wireless button support
-  HP Wireless Button Driver
-  Windows 8 drivers for your Wireless, Bluetooth and WWAN devices
If all requirements are not met then you may experience one or more of the behaviors outlined below
- Airplane Mode and Wireless Button does not work interchangeably (if you turn off wireless using Airplane Mode you can’t turn it back on using the wireless button and vice versa)
- The various Wireless Status options may be out of sync (wireless button LED, PC settings – Wireless Status, Airplane Mode, Network status in taskbar)
-  Bluetooth device may not appear under PC Settings and may not work
To ensure your wireless devices are working optimally with Windows 8, follow the below instructions.
Update to BIOS with Windows 8 wireless button support.
Check here for an overview of HP’s Windows 8 BIOS updates, or go to the hp.com drivers download page for your product to download the latest Win8 BIOS
Once the bios has been updated you will have a new unknown device in Device Manager with Hardware Id “ACPI\VEN_HPQ&DEV_6001”
Install the HP Wireless Button driver (SP58720)
Note! The HP Wireless Button Driver will not install if the wireless button device is not present in Device Manager. The Windows 8 BIOS with wireless button support must be installed first.
Install the appropriate Windows 8 Wireless, Bluetooth, and/or WWAN drivers (as applicable for your system)
Qualcomm Atheros AR9000 Series Wireless LAN Driver for Microsoft Windows (SP58498)
Qualcomm Atheros Bluetooth 4.0+HS Driver for Microsoft Windows (SP58499)
Broadcom Wireless LAN Driver for Microsoft Windows 8 (SP58848)
Broadcom Bluetooth Software for Windows 8 (SP59021)
Intel PROSet/Wireless WiMAX Driver for Windows 8 (SP59501)
Intel Wireless Drivers for Microsoft Windows 8 (SP58880)
Intel Centrino Wireless-N 2230
Intel Centrino® Ultimate-N 6300
Intel Centrino Advanced-N 6205
Intel Centrino Advanced-N 6235
Intel Centrino Advanced-N 6250 AGN
Intel Centrino Wireless-N 2200
Intel Centrino Wireless-N 6150
Intel Wireless Drivers for Microsoft Windows 8 (SP59925 - not yet available)
Intel Centrino Wireless-N 1030 802.11 bgn
Intel Centrino Wireless-N 6230 802.11 abgn
Intel Centrino® Wireless-N 1000 802.11 bgn
Intel Bluetooth Driver (SP58416)
Ralink 802.11 Wireless LAN Adapter (SP58374)
Realtek RTL8188CE 802.11b/g/n Wireless LAN Driver for Microsoft Windows (SP59181)
Ericsson Mobile Broadband Drivers (SP57728)
Bluetooth 3.0 Devices
Bluetooth 3.0 devices have in-box driver support in Win8. Systems with Bluetooth 3.0 will work in Windows 8, but you will notice that even with updated BIOS and all other drivers installed the wireless button LED status (indicating if the HW is enabled/disabled) may be out of sync with the wireless system status. This is a limitation.
Although I am an HP employee, I am speaking for myself and not for HP

Hello,
I have a mini 210-1080NR. Due to a software problem I had to reinstall the OS. I now have Win 7 Prof working fine on it. When trying to connect ot the Internet, I get the WLAN module is not present. I tried installing the "SP48755" WLAN driver. It did not work. I also opened the bottom cover, removed the WLAN module and reconnected to reseat and show a new piece of hardare was installed. This did not resolve the issue.
So, in Device Manager, the following problems display :
1 - Network Controller (apparently precents me from connecting to the Internet)
2 - Video Controller (no display issues, except my resolution only goes to 1024.
Per instructions of a Forum HP tech before, I went to the Details tab (first line) for both Network Controller and Video Controller and copied the Hardware IDs:
Network Controller:
PCI\VEN_14E4&DEV_4357&SUBSYS_145E103C&REV_01
PCI\VEN_14E4&DEV_4357&SUBSYS_145E103C
PCI\VEN_14E4&DEV_4357&CC_028000
PCI\VEN_14E4&DEV_4357&CC_0280
Video Controller:
PCI\VEN_8086&DEV_A012&SUBSYS_3660103C&REV_00
PCI\VEN_8086&DEV_A012&SUBSYS_3660103C
PCI\VEN_8086&DEV_A012&CC_038000
PCI\VEN_8086&DEV_A012&CC_0380
I suspect the Video Controller issue will be resolved once I connect to the Internet and update the OS and hardware drivers.
Thanks in advance.

Linksys Wireless Network monitor overrides Windows XP Wireless Zero Configuration

Hello all,
I am currently using the wireless router Verizon sent me and it works fine when using the Windows XP Wireless Zero Configuration tool. Previously I was using a Linksys wireless router and I have the Linksys Wireless Network monitor installed. About half the time when starting up the computer, the Linksys monitor starts up and I have to manually switch to the Windows XP Wireless Zero Configuration tool. This is very irritating and I would like to know if there is a way I can remove the Linksys Monitor and still be able to use the Linksys wireless adapter cards installed in the computer.

I think I know.
#1 http://netsquirrel.com/msconfig/msconfig_xp.html
#2 Very carefully, look through the list in MSConfig.
#3 Disable the Linksys Wireless Network monitor.
Restart the computer as need be.
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Ideapad z710 wifi drivers isues

Hi guys, i just installed Arch on my brand new Lenovo ideapad Z710 yesterday. Today i decided to install NetworkManager (i was using a netctl profile until now) the problem is that when i try to connect to wifi, Network Manager keeps prompting me for the password and never actually connects, i think the problem is with my wireless drivers, cause when i plugged in a wifi adaptor other than the laptop's built in one everything worked like a charm and ethernet also works fine.
Here's some info..
# lspci -k
07:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Wireless-N 7260
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
08:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
Subsystem: Qualcomm Atheros Device 1091
Kernel driver in use: alx
Kernel modules: alx
# dmesg | grep iwlwifi
[ 2.522232] iwlwifi 0000:07:00.0: loaded firmware version 25.15.12.0 op_mode iwlmvm
[ 2.931503] iwlwifi 0000:07:00.0: Detected Intel(R) Wireless N 7260, REV=0x144
[ 2.931561] iwlwifi 0000:07:00.0: L1 Disabled - LTR Enabled
[ 2.931796] iwlwifi 0000:07:00.0: L1 Disabled - LTR Enabled
[ 3.248693] iwlwifi 0000:07:00.0 wlp7s0: renamed from wlan0
[ 3.886600] iwlwifi 0000:07:00.0: L1 Disabled - LTR Enabled
[ 3.886836] iwlwifi 0000:07:00.0: L1 Disabled - LTR Enabled
[ 5.030367] iwlwifi 0000:07:00.0 wlp7s0: disabling HT/VHT due to WEP/TKIP use
[ 5.030368] iwlwifi 0000:07:00.0 wlp7s0: disabling HT as WMM/QoS is not supported by the AP
[ 5.030370] iwlwifi 0000:07:00.0 wlp7s0: disabling VHT as WMM/QoS is not supported by the AP

I want to thank you for your answer!
Well, I installed Bodhi-Linux which is a derivate of Ubuntu 12.04 LTS.
For info:
When I switched to console, I noticed that tty4 is not possible to be accessed. In Midnight Commander (it's a small prog, like Norton Commander, for the terminal) F4 will call the nano-editor, this does not work. It's a bios bug, I think the scan code can be remapped.
Bumblebee is for using the Intel-graphics and the Nvidia-graphics, my Z710 has got Optimus. On Bodhi this works, but after reboot the bumblebee daemon have to be started by root in a terminal. Surely a modul problem, could be solved by blacklisting some modules.
Secured Boot is an option for the UEFI-system (booting) which only allows certified bootloader to be booted. A few distros could handle this by using "shim".
I will go with KALI-Linux (debian based), because of the newer kernel, 3.12.x instad of 3.8.x.
LENOVO IDEAPAD Z710 59403383,i7-4700MQ,8 GB DDR3-RAM,1.920 x 1.080 Pixel,NVIDIA® GeForce® GT 740M,Hybrid (1 TB S-ATA + 8GB SSD)

Lenovo Ideapad flex 15d computer power issues

My Ideapad Flex recently developed two issues.
Problem 1: When the computer goes to sleep (via start menu, closing the lid, or being inactive) the hardware turns off completely. In Windows 8.1's event viewer there are two errors that state that power failed unexpectedly.
This has occured with the power adapter connected, and without. It also occured for Ubuntu 14.04.
Problem 2: The computer (when powered down) only occasionally responds to the power button, and fails to boot when it does. I have found a temporary workaround - resetting the BIOS - however that only works one time per reset.

I just purchased a flex 15D a noticed that upon start up, there's lighting behind the keyboard, and (being new to PC laptops) it took me two nights to figure out that the only way to turn it on is Fn+space.

Grafikhardware Problem Ideapad Z710

Hallo liebe Leute,
ich hab leider keinen Plan ob ich das hier richtig poste, aber ich hab seit zwei Wochen ein Problem mit meinem Lenovo Ideapad Z710. Die unten angezeigte Fehlermeldung ist zum erstenmal aufgetreten aber so eine ähnliche kam aber in den letzten zwei Wochen schön öfter, darin stand das: "Grafikhardware wurde für die Anwendung Adobe Plu Flash Player blockiert. Dies ist aber nur beim gebrauch von Youtube und Facebook aufgetreten. Danach konnte man die Anwendung nur mehr schliesen und es funktionierte nichts mehr.
Bitte um Lösungen.

Hallo David4,
vielen Dank für deine Anfrage und willkommen im LENOVO-Forum.
Wurde irgendein Update durchgeführt (bsp. Treiber-Update der GK oder Windows-Update)??
Hast du den GK-Treiber mal deinstalliert und neu installiert...? Siehe unsere HP:
http://support.lenovo.com/de/de/products/laptops-and-netbooks/ideapad-z-series-laptops/ideapad-z710-...
DirectX-Version überprüft bzw. wurde hier ein Update getätigt?
Im LENOVO Energy Management mal alles Einstellungen auf Höchstleistung stellen.
Gruß,
Marcel
→ Wenn Du eine Lösung auf Deine Frage erhalten hast, markiere diese bitte als gelöst - Hilfreiche Beiträge verdienen Kudos. Zögere nicht Kudos zu vergeben.

THis Wireless Issue is a Head Scratcher

As some know, I bought 2 Macbooks in Dec '06 and was experiencing all sorts of wireless issues early on. Dropped connections, SLOW transfer speeds while networked to my Imac, etc.
At some point Netgear released new firmware for the 824, and all seemed right in the wireless world for at least 2 months.
No issues with OS updates or airport updates, it seemed.
Al of a sudden last week, I went back to the extremely slow speed when networked from the macbook (wireless) to the iMac G4 800 (wired) and nothing so far will fix it.
The wireless transfer happens in 500K packets and a 4 meg file takes 4 minutes to transfer. Yet if I plug in the ethernet cable to the macbook - it works as it should.
What I can't figure out is what happened to make this annoying issue return out of the blue.
I am also back to slow page loads via Safari and page hangs.
Of course I have rebooted the router -
I can't figure out why for at least 2 months everything worked perfectly after months of sub par wireless performance and then back to **** - with everything back to sub par except not dropping connection anymore.
Thoughts?

I think the first thing I'd check for is if some source of interference returned after a few months of absence. I have a 2.4 GHz cordless phone that will nuke my 2.4 GHz WiFi connections - but only sometimes - when the phone happens to pick a channel that coincides with my WiFi. It could well be that a phone in your neighbor's house gets on your channel, and if the the phone doesn't experience any trouble may sit on your WiFi channel for a long time. In my case, my Panasonic phone bothers the WiFi, but the WiFi never bothers the phone.
The other thing you might want to look for is how many IP packets are being discarded by your Mac's network interface. You can do that my opening a terminal window and doing "netstat -s | more" The -s option gets you a rather extensive list of Ethernet statistics. What you want to look for is anything related to retransmitted packets. If you are experiencing more than a 1% IP packet loss, Ethernet performance can degrade rather ungracefully. (Note, I'm talking about layer 3 and above IP packets). It isn't unusual for 15-20% frame loss at layer 2 in the WiFi connecdtion.
There are a lot of variables here, and it is difficult to give you an answer that would be a one-step magic pill. There could be several problems at once. The best test would be: does one computer have lousy web page load times over WiFi, but the other computer has quick web access.
If both computers are having problems loading web pages, then there is something wrong with the router and/or WiFi interference. If just one computer has poor performance, then you need to look at the software on that computer.
Best wishes for finding it.
Bill

No Wireless Issues - Post Your Router

There is a "Wireless Issues - Post Your Router" thread, so this one will take a look at all routers that do NOT have any issues at all with any model of MacBook Pro. Unfortunately I can't add to it personally since Airport won't connect to my Linksys WRT54G intermittently. I was looking at the DLink DI-634M, so if anyone has any experience with that one, please post that as well.

Linksys WRT54GX4... A great router that supports 4 Windows XP systems (3 desktops and 1 laptop) and 1 Macbook Pro. Since I've had my MBP, I've had no connectivity problems whatsoever...
MBP (2.0Ghz) Mac OS X (10.4.6) Also running WinXP Pro on MBP...
MBP (2.0Ghz) Mac OS X (10.4.6) Also running WinXP Pro on MBP...

New MacBook Pro 13 i5 Wireless Issues.

I got the new MacBook Pro i5 2.3 the day it came out. So maybe a week and half ago.
I`m having intermittent wireless issues. I have done some testing and even replaced my older AirPort Base Station with the new Dual-Band one, but still seeing a drops from the network. I have a ping going to my router and to the ABSE. I tried changing the channel and using 5GHZ or 2.4GHZ. I also have a AirPort express and seen similar results. I tried reseting the PRAM, repairing permission, I did not reinstall the OS but I dont see how this would help. I think there is a hardware issue with the wireless card/antenna.
I did upgrade RAM and HDD was changed to SSD (intel G2 SSD). There are no other issues, machine is fast, no lock ups. Other devices on the network do not seem to drop any connections (ATV, ATV2, iPhone4, iPad etc..)
The network drop outs are short but are noticeable and if a ping is going I can see the drops
*-- 192.168.1.1 ping statistics ---*
*1527 packets transmitted, 1505 packets received, 1.4% packet loss*
*round-trip min/avg/max/stddev = 0.779/12.203/396.084/42.274 ms*
Any help is appreciated as I`m really frustrated but this issue.

Here are some of the pings.
+*64 bytes from 192.168.1.3: icmp_seq=2190 ttl=255 time=1.138 ms*+
+*Request timeout for icmp_seq 2191*+
+*Request timeout for icmp_seq 2192*+
+*64 bytes from 192.168.1.3: icmp_seq=2193 ttl=255 time=1.701 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2194 ttl=255 time=1.653 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2195 ttl=255 time=1.723 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2196 ttl=255 time=1.470 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2197 ttl=255 time=1.435 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2198 ttl=255 time=1.217 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2199 ttl=255 time=1.115 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2200 ttl=255 time=1.433 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2201 ttl=255 time=1.002 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2202 ttl=255 time=1.057 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2203 ttl=255 time=1.222 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2204 ttl=255 time=0.769 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2205 ttl=255 time=0.821 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2206 ttl=255 time=0.723 ms*+
+*Request timeout for icmp_seq 2207*+
+*64 bytes from 192.168.1.3: icmp_seq=2208 ttl=255 time=54.892 ms*+
+*Request timeout for icmp_seq 2209*+
+*Request timeout for icmp_seq 2210*+
+*64 bytes from 192.168.1.3: icmp_seq=2211 ttl=255 time=1.313 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2212 ttl=255 time=0.936 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2213 ttl=255 time=1.839 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2214 ttl=255 time=0.879 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2215 ttl=255 time=63.446 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2216 ttl=255 time=24.384 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2217 ttl=255 time=105.923 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2218 ttl=255 time=41.322 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2219 ttl=255 time=1.853 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2220 ttl=255 time=0.811 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2221 ttl=255 time=0.721 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2222 ttl=255 time=0.791 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2223 ttl=255 time=3.816 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2224 ttl=255 time=1.052 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2225 ttl=255 time=0.688 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2226 ttl=255 time=89.272 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2227 ttl=255 time=49.459 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2228 ttl=255 time=15.891 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2229 ttl=255 time=0.745 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2230 ttl=255 time=0.724 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2231 ttl=255 time=0.680 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2232 ttl=255 time=1.950 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2233 ttl=255 time=0.600 ms*+
+*Request timeout for icmp_seq 2234*+
+*64 bytes from 192.168.1.3: icmp_seq=2235 ttl=255 time=0.725 ms*+

Ideapad z710 windows 7 wireless issue

Similar Messages

Maybe you are looking for