search for: 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...

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

...ean looking for the next boot device in the bios boot order. The > > screen output says: > > > > Boot from local hdd ... > > Exiting PXE. > > > > And then it reboots. > > I think I had that issue with a first-generation uEFI-based system > (Dell Latitude E6410) that did this on me. > And did You find any solution towards this? > > On Tue, Aug 6, 2013 at 2:17 AM, Jonas Keidel <jonas at jonas-keidel.de> > wrote: > > so further information towards the chain.c32 problem: > > we can't boot from a software raid with this, b...

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 function. [ 1.176456] Linux agpgart...

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

...hought I didn't include USB as part of boot list. It will give me error "Remove any media and restart..." ?So now both HD0 and HD0 0 will work on E5510 as long as you don't stick any USB sticks in it. >> > > That gives me some tests to try Monday. ?I just hope that the E6410 > and E5510 are similar enough in their BIOS. > > This sounds to me that there's a bug in the BIOS (main or the PXE > option ROM; both are integrated to the same chip and same upgrade > application). ?Is the USB stick bootable? ?Have you noticed differing > results with bootab...

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

...tack" in this context? > > So i mean looking for the next boot device in the bios boot order. The > screen output says: > > Boot from local hdd ... > Exiting PXE. > > And then it reboots. I think I had that issue with a first-generation uEFI-based system (Dell Latitude E6410) that did this on me. On Tue, Aug 6, 2013 at 2:17 AM, Jonas Keidel <jonas at jonas-keidel.de> wrote: > so further information towards the chain.c32 problem: > we can't boot from a software raid with this, because if the first hdd is > swapped (and empty), the system normally can...

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

...nouveau at lists.freedesktop.org Reporter: johan.myreen at gmail.com QA Contact: xorg-team at lists.x.org Created attachment 133949 --> https://bugs.freedesktop.org/attachment.cgi?id=133949&action=edit Kernel messages as reported by journalctl -b -1. On a Dell Latitute E6410 laptop with the following display adapter: 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [NVS 3100M] (rev a2) Some time ago (kernel 4.10.0) the kernel drm module stopped working, the display is all messed up after boot and stays so. The first line on the screen says "Starting...

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)

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

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