Search Results

Search found 17 results on 1 pages for 'e6410'.

Page 1/1 | 1 

• Latitude E6410 - Screen flickering on Windows 8

  - by Martin

  On Windows 8, my Latitude E6410 screen (1440x900 - 60Hz - NVidia NVS3100M) is flickering. If I turn off the laptop for 30 minutes and turn it back on, there's no flickering but it eventually start again after 10-15 minutes. The flickering seems more present at the top and bottom of the screen. I already updated the graphic card drivers, bios, etc. Nothing seems to fix the issue. To prove that it isn't a hardware issue, when I reinstalled Windows 7 I couldn't reproduce the issue. Any idea what could cause this?

  Read the article

• Laptop monitor stopped working and can't be re-enabled on a Dell Latitude E6410

  - by xektrum

  I'm using Ubuntu 12.04 (upgraded from 11.10), everything seemed to work fine until today when my laptop monitor suddenly stopped working. Here are the facts: My laptop is a Dell Latitude E6410, Intel graphics. External Monitor is attached through a docking station. Everything worked fine for about 6-7 month, then upgraded to 12.04 Issue started today after a week of upgrade. I think the issue started after I ran CounterStrike 1.6, both monitors blinked and then only the attached monitor which is connected to a docking station continued to work I thought at first that was a transient issue but then I've rebooted, removed the battery but the same happens. Laptop Monitor and external monitor work fine up to login screen, but after I login it goes black Whenever I try to re-enable laptop monitor from Display Manager I get errors: The selected configuration for displays could not be applied could not set the configuration for CRTC 63 Not sure what technical details are required but here are some: $ xrandr Screen 0: minimum 320 x 200, current 3120 x 1050, maximum 8192 x 8192 eDP1 connected (normal left inverted right x axis y axis) 1440x900 60.0 + 40.0 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 60.0*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) $ tail /var/log/Xorg.0.log [ 8367.132] (WW) intel(0): flip queue failed: Device or resource busy [ 8367.132] (WW) intel(0): Page flip failed: Device or resource busy [ 8367.174] (WW) intel(0): flip queue failed: Device or resource busy [ 8367.174] (WW) intel(0): Page flip failed: Device or resource busy [ 8367.174] (WW) intel(0): flip queue failed: Device or resource busy [ 8367.174] (WW) intel(0): Page flip failed: Device or resource busy [ 8367.265] (WW) intel(0): flip queue failed: Device or resource busy [ 8367.265] (WW) intel(0): Page flip failed: Device or resource busy [ 8367.265] (WW) intel(0): flip queue failed: Device or resource busy [ 8367.265] (WW) intel(0): Page flip failed: Device or resource busy I'm using gnome-shell, and the only ways I've been able to get both display working have been: 1) Booting with laptop disconnected from docking and then re attach external with VGA instead of DVI, but only worked for a session. 2) Removing xserver-xorg-video-intel, but then I gnome-shell is gone as well as dri I would appreciate any suggestions. Regards, ============================= WORKAROUND FOUND ============================= So I have tried few things and here is what worked: I've installed a newer version of xserver-xorg-video-intel (2.19 vs 2.17) from ppa:xorg-edgers/ppa, it didn't work at first, it was only showing low graphics mode, so I tried with a different linux-image 3.0.0-19-generic-pae instead of 3.2.0-24-generic-pae, which I believe is 12.04 precise default, then everything started to work again, Now I've installed 3.4.0-1-generic-pae from same ppa and everything goes flawless so I believe the issue is either with linux-image 3.0.0-19-generic-pae or xserver-xorg-video-intel 2.17. Hope this helps someone in the future. PS: Now xrandr shows multiple modes for my laptop monitor $ xrandr Screen 0: minimum 320 x 200, current 3120 x 1050, maximum 8192 x 8192 eDP1 connected 1440x900+1680+0 (normal left inverted right x axis y axis) 303mm x 189mm 1440x900 60.0*+ 59.9 40.0 1360x768 59.8 60.0 1152x864 60.0 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 60.0*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis)

  Read the article

• How do I turn on bluetooth on a Dell Latitude E6410?

  - by Rob Stevenson-Leggett

  I have recently acquired a Dell Latitude E6410. It's great but I can't get Bluetooth to work. I have enabled bluetooth for the Wireless Switch in the BIOS. However whenever I try and install the bluetooth driver from the CD I get the message: Activate Bluetooth using the Wireless Switch. There is only a cancel button on this dialog. There is no bluetooth icon on any function key and I have tried switching the what I assume to be the Wireless Switch (the switch which controls wireless internet, on the right side of the laptop) to on and off positions to no avail. Does anyone know what the problem is?

  Read the article

• Anyone know how to get dual screens working on a Dell E6410 laptop with Ubuntu 10.04 64 bit?

  - by Curtis

  I've installed the drivers from nVidia. When I go into the NVIDIA X Server Settings application, in the X Server Display Configuration setcion, and click the "Configure" button, "TwinView" is disabled. Also, clicking "Detect Displays" doesn't pick up my monitor (which is connected through a port replicator - keyboard and mouse in that port replicator work fine). Has anyone else seen this? Is this just a limitation of the current nvidia linux drivers?

  Read the article

• Anyone know how to get dual screens working on a Dell E6410 laptop with Ubuntu 10.04 64 bit?

  - by Curtis

  I've installed the drivers from nVidia. When I go into the NVIDIA X Server Settings application, in the X Server Display Configuration setcion, and click the "Configure" button, "TwinView" is disabled. Also, clicking "Detect Displays" doesn't pick up my monitor (which is connected through a port replicator - keyboard and mouse in that port replicator work fine). Has anyone else seen this? Is this just a limitation of the current nvidia linux drivers?

  Read the article

• I have to manually enter the pwd when I login at school and when I come back home with my laptop (DELL E6410)

  - by Bong Paduano

  I didn't have to do this the first 3 months of me going to school. My laptop used to be able to connect to my Home WiFi and school Wifi automatically then after the 3rd month something changed and eversince then I literally have to manually enter each of the Wifi passwords in each location each time I try to connect to their respective WLAN. I tried adding each WiFi networks in the "Manage wireless networks" section in the Network and Sharing Center but everytime I login to one of the location, the created network disappears and I did this more than once. I tried restoring the OS back but to no avail. Can someone please assist me on this issue. I'm not sure if this issue has been addressed in this website but I haven't seen any similar question in here. I appreciate any help anyone may be able to share.

  Read the article

• PCMCIA Does Not Work on Dell Latitude under Windows XP

  - by Rich

  PCMCIA cards do not work on Dell Latitude e5510 under Windows XP. Works fine on Windows 7. Cards are recognized by Device Manager but do not work correctly. For example, CF adapter does not recognize when a card is inserted and network card is unable to obtain an IP address. Other systems that may be affected: Latitude E4310 Latitude E5410 Latitude E5510 Latitude E6410 Latitude E6410 ATG Latitude E6510 Dell Precision Mobile WorkStation M4500

  Read the article

• Choosing a new laptop

  - by chiongms

  I'm looking for a new laptop. I saw few: i) HP ProBook 4321s ii) HP ProBook 6440b iii)Dell Latitude E6410 i found these laptops are still very new..is it? not much comments about them. can anyone help? i doubt how their graphic cards perform compare to each other? ProBook 4321s- Radeon HD4350 ProBook 6440b- Radeon HD4550 Latitude E6410- NVS 3100M most of the time i'll running 3D CAD software, C++ programing...i saw my friend's laptop with radeon HD4350. it's perfectly fulfilling my demand. but i wonder how the other two are? Another thing i doubt is the screen resolution..my current laptop is 1280x800, and i found it comfortable to use. But these two HP only offer 1366x768..will it make any large different? Lastly, is there anyway to estimate how their power consumption is from the spec sheet? well, i would prefer one with longer battery usage time. my current laptop is suck...only last 1 hour even when it's still new..i'm not going to get another like this anymore. Anyone can help me please? Thanks!

  Read the article

• WIFI connection not working

  - by chris verwey

  We have a wireless network that is set to secure, it does show as unsecure on my laptop, and desktop connect to router but no internet access. other computers on the network require password to connect to router and get internet access. Iphone and Ipads connect using password and also have internet access, what can I do to fix it. Laptop = dell e6410 Router = netgear The laptop work on other wireless networks without any problem

  Read the article

• Wine can't find gnome-keyring-pkcs11.so

  - by Jackie

  I am trying to start a program using wine on ubuntu lts 12.04 64 bit When I do this I get the following error message... /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory When I try to symlink the 64 bit libraries, of course I get the following... jackie@jackie-Latitude-E6410:~/tmp/AC$ wine TTG.exe p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: wrong ELF class: ELFCLASS64 wine: Unhandled page fault on read access to 0x00000000 at address (nil) (thread 0009), starting debugger... err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc47aac Is there a package that installs the 32-bit as well as the 64bit? UPDATE: Appears to be a bug in Ubuntu w/ 1.4 https://launchpad.net/~ubuntu-wine/+archive/ppa I used these steps and my application worked http://www.noobslab.com/2012/04/install-wine-152-on-ubuntu.html Not sure exactly why but it appears to ignore the error if you use the 1.5.

  Read the article

• Can't activate "mirror display"

  - by Nemo Peeters

  I have Ubuntu 12.04 on a Dell latitude E6410, I have a problem when using the VGA output I always have dual monitor and can't switch on the "mirror display" toggle under systems setting/displays. It's rather annoying when having to do presentation with a video projector. the option "mirror display" is in light grey and I can"t tick the box. Thanks for those who might have an idea how to resolve this? update: driver is: Intel® Ironlake Mobile x86/MMX/SSE2 card something like this ? description: VGA compatible controller product: Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 02 width: 64 bits clock: 33MHz

  Read the article

• Docking station power adapter is not recognized by my Dell notebook

  - by Soner Gönül

  At this morning, my laptop (Dell Latitude e6410) gave me this error. I didn't do anything, I didn't change anything. And I got this docking station just 2 month ago. I made a little research on the internet but I couldn't find read solution for this situation. Now my docking station is not charging to my laptop. I'm using Windows 7. What should I do in this situation ? Your docking station power adapter is not recognized by your Dell notebook. As a result, your power adapter may not provide sufficient power to run the system, your battery will not charge, your system will run slowly. Please insert a 65 watt Dell approved power adapter.

  Read the article

• What causes Windows Boot to stall?

  - by Nick Berardi

  For about 6 months now I have been having this weird problem where Windows 7 fails to fully boot correctly. What happens is this. Starting Windows shows up on the screen. Then 3 out of 4 times nothing else happens, no Windows Flag animation, just nothing occurs. After 3 or 4 restarts repeating steps 1-2 above, the Windows Flag animation finally shows up and everything works as expected. My question is what is causing this problem in steps 1 and 2? Because I have tried the following with no luck: Error checking and correcting of any disk errors Updating drivers Doing a clean install of Windows 7 My setup is as follows: Windows 7 64-bit Ultimate 8 GB RAM 128 GB Crucial SSD (firmware 0005) Dell Latitude E6410 Intel Wireless and Graphics Other than what I have tried above I am totally out of ideas and looking for some new ones to try.

  Read the article

• Debian 5.0.8 won't detect my ethernet adapter

  - by PaulH

  I'm installing Debian 5.0.8 on a Dell Latitude E6410 using the network install x86 CD. Unfortunately, it won't detect my Ethernet adapter. Specifically, I get the error: No Ethernet card was detected. If you know the name of the driver needed by your Ethernet card, you can select it from the list. lspci shows: 00:19.0 Ethernet controller: Intel Corporation Device 10ea (rev 05) That should correspond to the e100e driver. But, if I select it from the list, the install CD still fails to detect it. Ubuntu 10.10 and Windows 7 are able to use this device with no problem. Does anybody know what I can do to make Debian use my Ethernet adapter? Thanks, PaulH

  Read the article

• Windows 7 x64 wired connection problem. IP, gateway, dns assigned, can't ping. Network detected as "Network"

  - by Emil Lerch

  I am having a problem connecting to a specific wired network with my Latitude E6410 laptop. Other wired networks seem to work fine, but this one does not. I have a coworker with me with the same Intel 82577LM Gigabit Network card, and he can connect just fine. I've updated to the latest Intel drivers (11.8.75.0) and am not using Pro Set. I obtain all DHCP information just fine (IP, netmask, DNS server, default gateway). I cannot ping anything (internal or on the Internet - I tried pinging Google's public DNS servers by IP 8.8.8.8), nor can I get answers to any DNS queries through NS Lookup. Windows troubleshooting says everything is fine, but I can't get DNS responses. I've seen issues like this in the past that were related to link speed/duplex autonegotiaion failures, so I've tried manually setting link speed/duplex to all values one by one with no success. My coworker is using all default settings, so he is just using autonegotiate. Any ideas of other things to try?

  Read the article

• How does one skip "Windows did not shut down successfully" in Win7-64?

  - by XenonofArcticus

  Migrating an app from an expensive and unreliable dedicated embedded x86 box running WinXP-embedded to COTS hardware (Dell E6410 laptop) running normal Win7-64. At this time, it's not feasible to deploy using Windows 7 embedded. The problem is, that the system is still sort of "embedded". The power could shut off at virtually any time without prior warning. We've stripped the OS down and removed the battery capability so that it will power down as desired. The app never writes to the disk, so it's not like we're going to corrupt anything terribly. The system is essentially idle after our app is up and running (with the exception of some computation, graphics, and TCP/IP and serial communications) so the OS enters a pretty stable state rather quickly. After a power-loss however, it rightly complains that Windows did not shut down successfully and presents the user with the Windows Error Recovery text screen. If left alone, it does eventually move on booting just fine, but we'd like to skip that step if possible. WinXP-embedded is designed to do this automatically, so I know it's possible. I've looked at the Kernel Switches but I didn't see anything documented for "Skip Windows Error Recovery". I've also read extensively on the startup process: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/windows-nt-6-boot-process.html I know I can disable the auto chkdsk in the registry, but that's not the same thing either. So, how do I streamline the boot process to not hassle the user about a situation that will be the regular normal situation?

  Read the article

• How does one skip “Windows did not shut down successfully” in Win7-64?

  - by XenonofArcticus

  Migrating an app from an expensive and unreliable dedicated embedded x86 box running WinXP-embedded to COTS hardware (Dell E6410 laptop) running normal Win7-64. At this time, it's not feasible to deploy using Windows 7 embedded. The problem is, that the system is still sort of "embedded". The power could shut off at virtually any time without prior warning. We've stripped the OS down and removed the battery capability so that it will power down as desired. The app never writes to the disk, so it's not like we're going to corrupt anything terribly. The system is essentially idle after our app is up and running (with the exception of some computation, graphics, and TCP/IP and serial communications) so the OS enters a pretty stable state rather quickly. After a power-loss however, it rightly complains that Windows did not shut down successfully and presents the user with the Windows Error Recovery text screen. If left alone, it does eventually move on booting just fine, but we'd like to skip that step if possible. WinXP-embedded is designed to do this automatically, so I know it's possible. I've looked at the Kernel Switches but I didn't see anything documented for "Skip Windows Error Recovery". I've also read extensively on the startup process: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/windows-nt-6-boot-process.html I know I can disable the auto chkdsk in the registry, but that's not the same thing either. So, how do I streamline the boot process to not hassle the user about a situation that will be the regular normal situation?

  Read the article

1