similar to: [PATCH 0/1] lss16 parser

On 11/2/14, Ady <ady-sf at hotmail.com> wrote: > > FWIW, Utopic uses 6.03-pre18, not the final release (although, the > lss16 problem is present in both). > > About the lss16 issue, we all would welcome patches, really. Any > volunteers? > > @Barry, see http://www.syslinux.org/archives/2014-October/022734.html > Ady, Thanks very much for the information. My

> Hi, > I have just joined the list. > > I am the original creator of Puppy Linux, now letting other guys take > the reins, and I am working on a fork of Puppy called Quirky Linux, > where I try various experimental ideas. > > Up until now, in Puppy and all offshoots, we have used syslinux 4.05 or older. > > Over the last few days I have been testing 6.03 (using

>From: Ady <ady-sf at hotmail.com> >To: syslinux at zytor.com >Subject: Re: [syslinux] lss broken when upgraded 4.05 to 6.03 >Message-ID: <BLU436-SMTP134329F24C9A85B97FF55BF8B990 at phx.gbl> >Content-Type: text/plain; charset="US-ASCII" > > >> On 11/2/14, Ady <ady-sf at hotmail.com> wrote: >> > >> > FWIW, Utopic uses

Hi, I have just joined the list. I am the original creator of Puppy Linux, now letting other guys take the reins, and I am working on a fork of Puppy called Quirky Linux, where I try various experimental ideas. Up until now, in Puppy and all offshoots, we have used syslinux 4.05 or older. Over the last few days I have been testing 6.03 (using the binary DEBs from Ubuntu 14.10 Utopic Unicorn),

On 08/23/2015 12:33 AM, Patrick Masotta via Syslinux wrote: > >>>> > Unfortunately, > that other code is a massive single patch and would be hard to review > since it would be difficult to bisect should a bug be introduced. I > will try to split the other patch into logical parts and submit as time > permits. > <<< > > Yes I know;

Dear gentlemen, this is just a marginal quirk... I've been using a graphical logo at the pxelinux prompt in our LAN for many years. It's always been the same LSS16 picture, and it's always been working fine. I've been using pxelinux 3.53 until recently. Right now I'm in the process of introducing "UEFI netboot" into our LAN, and also the diskless boot into

G'day, I created a file to add mime-type detection for lss16 images... All you need to do is put it (unzipped) in /usr/share/mime/packages (or your equivalent) and run: update-mime-database -V /usr/share/mime Then you can just associate lss images with Mtpaint, to make life easier... Note: - I didn't know about the name (lss vs. lss16), so I just went by what the "file"

Good Evening: We've been using SysLinux in our admin class in college as part of a KickStart package designed to overcome multiple-use constraints in our computer lab (just pop the floppy in and suck the OS out of the server...). I have attempted to find out about the LSS16 file format you mentioned as part of your discussion of the DISPLAY format. We'd just love to use a cute

> I've been using a graphical logo at the pxelinux prompt in our LAN for > many years. It's always been the same LSS16 picture, and it's always > been working fine. I've been using pxelinux 3.53 until recently. Right > now I'm in the process of introducing "UEFI netboot" into our LAN, and > also the diskless boot into Debian would make use of some

Hi, the display of LSS16 files from a DISPLAY file (as documented in http://www.syslinux.org/wiki/index.php/SYSLINUX#Display_graphic_from_filename:) seems heavily broken since syslinux has been converted from assembler to C. I already discovered one bug in core/include/graphics.h (and core/graphics.c): the pointer VGAFilePtr is of type uint16_t*, but should be plain char*. This bug causes the

> Hi, > > the display of LSS16 files from a DISPLAY file (as documented in > http://www.syslinux.org/wiki/index.php/SYSLINUX#Display_graphic_from_filename:) > seems heavily broken since syslinux has been converted from assembler to > C. I already discovered one bug in core/include/graphics.h (and > core/graphics.c): the pointer VGAFilePtr is of type uint16_t*, but > should

On Sat, 2015-08-22 at 00:56 -0700, Patrick Masotta wrote: > Please take a moment and see what the quoted code does; it'll save you lot of time. I wrote my versions before I knew about the other code. Unfortunately, that other code is a massive single patch and would be hard to review since it would be difficult to bisect should a bug be introduced. I will try to split the other patch

I have used syslinux 4.0x and earlier for many years, with Puppy Linux and more recently Quirky Linux. Though, my knowledge of all the capabilities of syslinux remains rudimentary. I am new to UEFI. I recently got my hands on a win8.1 laptop, 64-bit system, and decided to tackle booting Quirky on it, from a USB stick. I turned off Secure Boot. I wrote /usr/share/syslinux/gptmbr.bin to the flash

>>> > Please take a moment and see what the quoted code does; it'll save you lot of time. I wrote my versions before I knew about the other code.? <<< Yes, but you published your patches after you knew about it. >>> Unfortunately, that other code is a massive single patch and would be hard to review since it would be difficult to bisect should a bug be

https://bugs.freedesktop.org/show_bug.cgi?id=28095 --- Comment #15 from Brent <bzipitidoo at hotmail.com> --- Yes, someone else said that hardware was unusual. But Nouveau did work with it, at elast somewhat, in the later 2.6 kernels. If it helps at all, the Diamond Viper V550 video card reports a version of 1.93E during POST. Tried older versions of Puppy Linux, and ran into other

> I have used syslinux 4.0x and earlier for many years, with Puppy Linux > and more recently Quirky Linux. Though, my knowledge of all the > capabilities of syslinux remains rudimentary. > > I am new to UEFI. I recently got my hands on a win8.1 laptop, 64-bit > system, and decided to tackle booting Quirky on it, from a USB stick. > > I turned off Secure Boot. > > I

Ady, Thanks for taking the time to respond to my lengthy post. Here are my answers: On 11/5/14, Ady <ady-sf at hotmail.com> wrote: > >> I have used syslinux 4.0x and earlier for many years, with Puppy Linux >> and more recently Quirky Linux. Though, my knowledge of all the >> capabilities of syslinux remains rudimentary. >> >> I am new to UEFI. I recently

https://bugs.freedesktop.org/show_bug.cgi?id=28095 --- Comment #16 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to Brent from comment #15) > Tried the debug boot parameters you suggested, with Slacko Puppy and Tahr > Puppy but they had no effect. There is no debug subdirectory in > /proc/sys/kernel. No doubt the stock Puppy kernel does not have debugging >

https://bugs.freedesktop.org/show_bug.cgi?id=28095 --- Comment #19 from Brent <bzipitidoo at hotmail.com> --- Been trying to track down the oldest kernel that shows the corrupted display, but have run into further problems. It seems nouveau with the early 3.x kernels does not work at all on this NV04 video card. I think 3.4 is the first version with nouveau included in the kernel? Have

https://bugs.freedesktop.org/show_bug.cgi?id=28095 --- Comment #20 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to Brent from comment #19) > Been trying to track down the oldest kernel that shows the corrupted > display, but have run into further problems. It seems nouveau with the > early 3.x kernels does not work at all on this NV04 video card. I think 3.4 > is