similar to: Problems booting on Intel i9x5 motherboards.

See: http://syslinux.zytor.com/archives/2006-May/006887.html I think I've tracked the problem down a bit more specifically. In edd.S when the kernel calls int 0x13 with %dl=80 [primary disk] & %al=1 [read one sector] and ah set to READ_SECTORS it never returns. However, the following code [which does drive diagnostics] works. mov $0x7E, %al call prtchr movw $0x0000, %ax movb

Hi, Intel has recently open sourced otion compensation code (XvMC) for their i915/i945 integrated graphics chips. See: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=blob;hb=xvmc-i915;f=src/xvmc/I915XvMC.c XvMC API was intended for MPEG{2,4} class of codecs - so it can not be used for Theora as-is. However, could at least some parts of it such as hardware accelerated

I am trying to set up a new 1400x900 widescreen monitor, but I just cannot get it to work correctly. The closest I get is 1400x900, which causes lots of vertical blur bands. I have tried with two different machines with i945 and ATi cards, running CentOS 4 and Ubuntu, always with the same result. My investigations indicate that the monitor reports itself to be "1440x900". It also

Thanks to debugging information from Thomas Mieslinger, I have root-caused the failure of chain.c32 in Syslinux 3.85. I have put out Syslinux 3.86-pre1 and Syslinux 4.00-pre33 which fix the problem. I expect to release a Syslinux 3.86 relatively shortly (ideally in the next two weeks), with bug fixes only. I would like to figure out if there are other bug fixes we can get in in reasonable time,

Hello, I have found what seems to be a wee bit of a bug in the ISOLINUX menu. :) I have chainloaded a second menu as per the example at the very bottom of README.menu. When a menu item is selected in the second menu, <Enter> is pressed, the menu complains that it cannot find an image with the name of the label. So if the label is Image_1, it says it cannot find that. However, if

Does anyone have information on support for Intel D965-based motherboards for CentOS 4 (i386)? I've got a DG965RYCK that fails a CentOS 4.4 install early on (problems scanning the PCI bus). Fedora Core 6 installs just fine. If anyone has any information, or magic boot parameters to try, please let me know. ("Works for me" is OK too). Thanks much. Dave Thompson UW-Madison

Woody Suwalski <woody at suwalski.net> schrieb am 07.03.03 17:57:26: > > Peter, we have met in Cyber space looong time ago, when I was requesting > 10:minor numbers for the Netwinder project.... > > Now I am trying to build a network boot for Xandros distribution. > > I have it working, however I need to do 2 DHCP cycles - 1 happens in > PXE, and then it repeats

Has anyone succeeded in getting lm_sensors to produce useful output for intel D945-based motherboards? According to the lm_sensors site, I need a newer kernel (2.6.16) to read the ICH7 data. I noticed the i2c patches in the kernel source rpm, but no joy. I'd be okay with building my own modules, but haven't found anyone to provide the kernel module source apart from the kernel

Hi! Using the following extlinux.conf serial 0x2f8 57600 0x013 # that is, RTS/CTS flow control on COM2 prompt 1 timeout 100 say Select 'linux' or 'xen'. say Automatically booting 'xen' in 10 seconds. default xen label linux kernel /vmlinuz-2.6.18-6-686 append initrd=/initrd.img-2.6.18-6-686 root=/dev/mapper/xen1-root ro console=tty0 console=ttyS1,57600n8r noresume

Hi, i am looking now at the code which i assume loads the rest of isolinux.bin. The entry point for program execution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated

Hello, I have now spent 30 hours trying to get this working, so it's time to get some professinoal help. :) In a nutshell, I would like to have a sambda AD PDC that authenticates both Windows and Debian. On Linux, I would like to use SSSD. I have followed the steps on the wiki: - https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO -

On Fri, Mar 24, 2017 at 05:38:31PM +0100, Thomas Schmitt via Syslinux wrote: > isohdpfc pushes the CX value to the stack which it gets from INT 13 AH 41. > Quite surely bit 0 of that CX is not set. But bit 2 "Enhanced Disk Drive" > could be set. > https://en.wikipedia.org/wiki/INT_13H > > I understand on David's BIOS after > > andw $1,%cx

Hi, Geert Stappers wrote: > Contact David off-list, he did unsubscribe. Can you tell when he unsubscribed (i.e. which of the messages he got as last one) ? > Martin posted elsewhere in this thread "Thomas, you found the bug" > and provided a patch. Open question is whether the fix helps with David's BIOS. The newest answer from Martin indicates that a failure to read

Hi, given the fact that the conversion has the factor HC*SH = "secpercyl", which is invariant under swapping, there remains as suspect in read_sector_cbios only this division: divb (sectors) There is a suspicious discrepancy in the code: heads = (stack-16) sectors = (stack-18) ... /* here we computer CHS values or just do some dummy computation for EBIOS */ andw $0x3f,

I looked a bit more into the problem of vertex corruption with GART vertex buffers that disappears putting the buffers in VRAM that I'm experiencing on my card. The system I'm seeing this on is a Dell Inspiron 9400 notebook with a GeForce Go 7900 GS on a PCI Express Intel i945 chipset. First, I've looked into the behavior of the nVidia driver: 1. On all NV3x and NV4x traces, and my

Hi, Sorry for asking this again if this have been asked. I searched this mailing list but I can not find the confirmed answer. We tried to use syslinux to boot USB flash drive. The problem is, if we put the kernel and initrd in /casper directory, syslinux failed to boot, it showed us: ------------------ Booting error message: SYSLINUX 3.11 Debian-2007-03-12 EBIOS boot: /casper/vmlinuz1 Could not

Hi, C/H/S addressing and reading of first block seems to be ok in isohdpfd.bin. The main suspect for the failure of the attempt with isohdpfd.bin is the number or content of the blocks read after the first one. But i have no clue why isohdpfc.bin should do better than isohdpfd.bin. They differ just by one instruction (JC = 0x72 versus JMP = 0xEB) which both are performed before the reading and

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

Nice to see the venerable syslinux updated to version 3.35. I did happen to encounter an issue with the latest release though. I performed 'syslinux -f' on a 32MB USB drive and all seemed well...until I tried to boot from it. Error message and drive details below: - - - /error message: SYSLINUX 3.35 2007-01-28 EBIOS Loading Invalid or corrupt kernel image. boot: /bootable USB drive

Thomas Schmitt wrote: > So if we had a MBR which prints the content of the first 512 read bytes > we could tell whether they are block aligned and from which block they > come. Ok. I'll try. Is it the isohdppx or isohdpfx (or both) that is relevant? Meanwhile I have a hacked isohdppx.bin that prints: G if GPT M if MBR <nothing> if no partition info E if EBIOS C if not EBIOS