search for: e6410s

Displaying 13 results from an estimated 13 matches for "e6410s".

Did you mean: e6410
2010 Oct 25
3
Dell E6410
Just recently bought a Dell E6410 with a Intel? HD Graphics with ExpressCard with I7-640m processor. Having some issues getting a graphical env to work. By just the looks of lspci X is wanting to use the VGA Compatable controller: Intel Corp Core Processor Intergrated graphics controller. Everything else is using Intel Corp Series 5/3400 Series Chipset. Has anyone else had any luck getting
2010 Dec 02
0
Dell Latitude E6410 and BIOS drive ordering
I'm posting as an FYI. I was testing BIOS A04 with a UFD (USB Flash Drive) but it probably applies to everything that looks like a USB hard drive. My previous statement was partially incorrect as I did find a scenario to the contrary. I tried with FDD then CD at the top of the list and tried with both just disabled (without reordering first). I tried with the SATA controller in ATA, AHCI
2013 Aug 06
1
Intel DX79TO localboot problem with CentOS
2013/8/6 Gene Cumm <gene.cumm at gmail.com> > On Mon, Aug 5, 2013 at 9:04 AM, Jonas Keidel <jonas at jonas-keidel.de> > wrote: > > 2013/8/5 H. Peter Anvin <hpa at zytor.com> > > > >> On 08/05/2013 05:37 AM, Jonas Keidel wrote: > >> > I have problems with the current syslinux (6.02-pre16) booting CentOS > 6.4 > >> > 64bit via
2017 Sep 30
0
Nouveau nullptr on NVIDIA NVA8
Starting with the drm merge af3c8d98508d37541d4bf57f13a984a7f73a328c for 4.13-rc1, the NVidia NVS3100M display on Dell Latitude E6410 had a nullptr crash on startup. As a result later the suspend2ram was locking up. Traced to a null ptr in nv50_mstm_service(), which seems to be called only from nouveau_connector_hotplug(). Fixed by checking if mstm is not NULL before calling the service
2013 Aug 05
4
Intel DX79TO localboot problem with CentOS
2013/8/5 H. Peter Anvin <hpa at zytor.com> > On 08/05/2013 05:37 AM, Jonas Keidel wrote: > > I have problems with the current syslinux (6.02-pre16) booting CentOS 6.4 > > 64bit via LOCALBOOT 0 with the Intel DX79TO. > > Did it work in previous versions? > As i have written, in every previous syslinux version it didn't work. > > Also in every previous
2010 Dec 02
1
Syslinux Digest, Vol 93, Issue 1
...he LABEL you're probably using) >> >> "keeps coming back to PXE."? ?Do you mean that using "chain.c32 hd0" >> just restarts the PXE boot? ?If so, the BIOS is trying to be smart and >> retry the boot rather than fail. >> >> I have access to E6410s at work that I can try to check Monday. >> >>> So I used append hd0 0 and it worked. >>> >>> Beau >>> >>> **************************** >>> Sent from Beast's BlackBerry BOLD. >>> Have a nice BOLD day! >>> Beau Cockburn...
2011 Jan 27
1
[PATCH][git-pull] memdisk/dskprobe.c
git://git.zytor.com/users/genec/syslinux.git Branch memdiskdbg-for-sha0 This starts with adding another check in two of the disk probes (by Shao; Thank you), expands the debug output, adds an additional check in the third probe and expands/reorders the debug output. At this time, it appears to resolve the MEMDISK issues that Jason Vasquez first noticed. The additional check in the third probe
2013 Aug 06
0
Intel DX79TO localboot problem with CentOS
On Mon, Aug 5, 2013 at 9:04 AM, Jonas Keidel <jonas at jonas-keidel.de> wrote: > 2013/8/5 H. Peter Anvin <hpa at zytor.com> > >> On 08/05/2013 05:37 AM, Jonas Keidel wrote: >> > I have problems with the current syslinux (6.02-pre16) booting CentOS 6.4 >> > 64bit via LOCALBOOT 0 with the Intel DX79TO. >> >> Did it work in previous versions? >
2011 Nov 08
3
Questions re PXELINUX
I have been using PXELINUX for a while and appreciate all you guys are doing! I have a couple of questions re PXELINUX: 1. I am experiencing problems with the LOCALBOOT statement on an IBM x3650. IBM mentions the following: http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5084755 I am using PXELINUX 4.04. Is this problem still attributed to some bug in PXELINUX? Right now I
2017 Sep 03
5
[Bug 102528] New: Display messed up shortly after boot on laptop with GT218M
https://bugs.freedesktop.org/show_bug.cgi?id=102528 Bug ID: 102528 Summary: Display messed up shortly after boot on laptop with GT218M Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium
2010 Nov 24
2
Useful Info about Dell latitude E5510
Hi H. Peter Anvin, I wanted to thank you for sharing information about PXE, I have used this a lot and I wanted to share something that may be important for you and your readers. I have many different Dell model, they all worked well with PXE booting however not for E5510. I noticed that using "LocalBoot -1 or 0" doesn't work well. What I did use for Latitude E5510 (Bios A06)
2014 Jul 23
3
DELL E6510 pxelinux issues
Hello, I have a problem with our DELL E6510 notebooks (BIOS version A05): 1. After the update from syslinux-3.71 to 4.02 LOCALBOOT no longer works. I've read <http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#LOCALBOOT_on_Dell_Latitude_E6400> and neither version works. The behavior differs between the laptop rebooting automatically and getting stuck. I checked all versions
2013 Jan 05
38
[Bug 59057] New: Black screen after resume from s2ram
https://bugs.freedesktop.org/show_bug.cgi?id=59057 Priority: medium Bug ID: 59057 Assignee: nouveau at lists.freedesktop.org Summary: Black screen after resume from s2ram QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: pontus.fuchs at gmail.com