similar to: Blank screen at startup (conflict with VESA VGA)

It simplifies nouveau code by removal of detection which region to pass to kick vesafb/efifb. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Eric Anholt <eric at anholt.net> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Thomas Hellstrom <thellstrom at vmware.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc:

Howdy, y'all I just got a GTX460 and I'm having a bit of trouble getting it running. In particular, when I modprobe "nouveau," the display goes black (but doesn't enter power saving, so there's a signal of some sort). After doing some searching, I found http://nouveau.freedesktop.org/wiki/KernelModeSetting If I unbind the nouveaufb driver, the console starts

fb_do_apertures_overlap is returning wrong value when one aperture is completely whithin the other. Add generic ranges_overlap macro (probably kernel.h candidate) and use it here. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc: Andrew Morton <akpm at linux-foundation.org> ---

Hi again, I got a new dmesg log with the debug parameters, but I guess I could not isolate VESA. I blacklisted it at /etc/modprobe.d/blacklist.conf but comparing those logs I see no difference... Is it possible to isolate VESA somehow without removing it? The new logs are here, I'm posting full content because I'm not sure what information is more relevant...

Greetings one and all. I'm a unix newbe....so deal with me here. I have a .iso copy of syslinux 1.67 (which actually might be ISOlinux??) that I boot from CD (ramdisk version...no HD needed)... but my version doesnt have the mkdosfs utility on it. I was looking for an executable that would work with this version... can someone point me toward such an animal??? :Pat

On 11/17/2014 12:55 AM, Didier Spaier wrote: > > So one more question: why can one boot with a GRUB EFI bootloader > but not with the SYSLINUX bootloader, using the same kernel? > > More accurately, I know why: because of the aforementioned patch, but > then, why is this test needed in SYSLINUX only? > Because Grub boots the kernel in a "hostile" way (not using

Hi, On 22/03/2016 22:03, Thomas Schmitt via Syslinux wrote: ... > Didier Spaier wrote: ... >> There is also goofiboot (fork of gummiboot) and even efi-stub > > Do you know an example of them booting out of an ISO ? > > It would be helpful for a neutral description in the isohybrid wiki > if it was not only GRUB2 that can be shown as tested. Yes, Solus ISOs. They are

https://bugs.freedesktop.org/show_bug.cgi?id=84706 Bug ID: 84706 Summary: [NV94] HDMI Connected, but TV reports "no signal" Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hi, Le 18/06/2020 ? 22:24, Tom Huibregtse via Syslinux a ?crit?: > I am a UEFI/BIOS developer. We UEFI PXE boot dozens of times per night. We have run into this error more than a couple of times. We have also done thousands of UEFI PXE boots with debug statements to prove that the patch works. <snip> As far as I can tell, the development of Syslinux has stalled since more than one

On 11/18/2014 10:20 AM, Didier Spaier wrote: > > On 18/11/2014 18:55, H. Peter Anvin wrote: >> On 11/17/2014 12:55 AM, Didier Spaier wrote: >>> So one more question: why can one boot with a GRUB EFI bootloader >>> but not with the SYSLINUX bootloader, using the same kernel? >>> >>> More accurately, I know why: because of the aforementioned patch,

> On 01/06/2016 00:28, H. Peter Anvin via Syslinux wrote: > > There seem to be a bunch of bug fixes in the 6.04 branch that people > > really need. Do we know of any current regressions? Otherwise we > > really ought to just push the button... > > I am a user of syslinux 4.0.7 to boot installers on BIOS aka Legacy. > > Knowing that 4.0.7 has been released on

On 16/04/2014 23:46, H. Peter Anvin wrote: > On 04/16/2014 02:15 PM, Didier Spaier wrote: >> Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 >> (to make a bootable USB stick) fails like this: >> >> Error converting to codepage 850 Invalid argument >> Cannot initialize 'S:' >> Bad target s:/ldlinux.sys >>

Precis: I?m trying to debug a problem with CentOS7 failing to install from an ISO written to a USB pendrive ? anyone got suggestions? What works ? installing on a modern, ?standard PC?; the pendrive image boots and installs as I expect What does not work ? same pendrive booting in an ATCA blade. What I?ve tried is? 1. Boot the standard CentOS7 minimal image. This seems to start but then

Test, test one two, test > > > > Thanks in advance, > > > > Prof S W Damle > > I don't know whether Pete Batard (RUFUS' developer) have read your > messages. And this message is to see if the "reply to list mungling" is gone. (Check the E-mail headers ( this message was/is a "reply to list" )) Groeten Geert Stappers

Hi all, I have requested tests of this USB installer: http://slint.fr/testing/slint64-14.1_syslinux.6.03.img in both BIOS and UEFI modes. A test in UEFI mode: http://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/#post5270515 leaded to this message: "Cannot relocate kernel, bailing out" That leaded me to this post in the ML:

On 18/11/2014 18:55, H. Peter Anvin wrote: > On 11/17/2014 12:55 AM, Didier Spaier wrote: >> So one more question: why can one boot with a GRUB EFI bootloader >> but not with the SYSLINUX bootloader, using the same kernel? >> >> More accurately, I know why: because of the aforementioned patch, but >> then, why is this test needed in SYSLINUX only? >> >

Hi, Ady wrote: > I very much doubt that there is any ISO image, publicly > available or not, that can boot optical media in UEFI mode by means of > Syslinux for EFI as of today. I hope this status will change at some > point. > [...] > I doubt that syslinux.efi (renamed as "EFI/BOOT/BOOT<arch>.EFI") > is capable of booting optical media in UEFI mode at

Hi there. Slackware's installer, that I am internationalizing, makes use of ISOLINUX. I want to give instructions to users in other languages than US English, e.g. which code to type to see installation messages in their native language. So my question are: (1) Which character encodings can be used in message.txt and f1.txt through f1O.txt? (2) Is UTF-8 allowed? (3) I'm guessing that

On 6 June 2015 at 14:03, Didier Spaier via Syslinux <syslinux at zytor.com> wrote: > > > On 06/06/2015 12:19, Stoppa, Igor via Syslinux wrote: > >> So I'd like to not put all the kernels/initrds in it, because when I >> update one of the OSes, I would also have to update the corresponding >> kernel in the EFI partition. > > > IIRC this is not

Hi, Ady wrote: > http://www.syslinux.org/archives/2015-October/024526.html I still have it in my mailbox: ADY4UEFI.IMG in ADY4UEFI.ZIP. The test results are the same as with Didier's partition image. Wrapped in an ISO and presented as -cdrom it reboots in cycles. Presented as -hda it boots as naked disk image and as part of a GPT enhanced ISO 9660. > the wiki page needs