Displaying 20 results from an estimated 10000 matches similar to: "vesamenu fullscreen efi boot"
2014 Jan 16
4
vesamenu fullscreen efi boot
This is for a USB boot image where I won't have advance knowledge of
the different screen resolutions it boots on
On Thu, Jan 16, 2014 at 5:15 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Thu, Jan 16, 2014 at 5:46 PM, Aaron McSorley <a at aaronmcsorley.com> wrote:
>> When I boot to efi my splash screen is tiled, how do I make it not
>> tile? Optimally I'd
2014 Jan 16
0
vesamenu fullscreen efi boot
> This is for a USB boot image where I won't have advance knowledge of
> the different screen resolutions it boots on
>
> On Thu, Jan 16, 2014 at 5:15 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> > On Thu, Jan 16, 2014 at 5:46 PM, Aaron McSorley <a at aaronmcsorley.com> wrote:
> >> When I boot to efi my splash screen is tiled, how do I make it not
2014 Jan 16
0
vesamenu fullscreen efi boot
On Thu, Jan 16, 2014 at 5:46 PM, Aaron McSorley <a at aaronmcsorley.com> wrote:
> When I boot to efi my splash screen is tiled, how do I make it not
> tile? Optimally I'd like it to expand the image to the size of the
> screen, is that possible?
To my knowledge, there is no stretch functionality. Your best bet is
to match your image size to the screen size.
--
-Gene
2014 Jan 17
1
vesamenu fullscreen efi boot
I'm no C expert but, I'd like to play with this, could you give me
some pointers to which code to look at so I can try to hack something
together?
On Thu, Jan 16, 2014 at 6:34 PM, H. Peter Anvin <hpa at zytor.com> wrote:
> On 01/16/2014 03:19 PM, Aaron McSorley wrote:
>> This is for a USB boot image where I won't have advance knowledge of
>> the different screen
2014 Jan 17
0
vesamenu fullscreen efi boot
On 01/16/2014 03:19 PM, Aaron McSorley wrote:
> This is for a USB boot image where I won't have advance knowledge of
> the different screen resolutions it boots on
I have been meaning to add the ability to add splash screens of
different resolutions, as well as give some ability how to position it,
but I have not had time and is unlikely to find time.
It would make a good project for
2014 Jan 17
2
where is the latest git source
I cloned from git://git.zytor.com/syslinux/syslinux.git but this looks
like 4.07, I expected something closer to a 6.xx, do I need to switch
to another branch or something?
2009 Jun 10
1
[Nouveau-cvs] xf86-video-nv: Branch 'master' - 2 commits
I just realised that this mode of tiling is quite different from the
one i observed, this one is linear inside the tile, not recursively
tiled.
Also, one optimisation that you can do without fixing the xserver
(which should be done anyway), is to set pread and pwrite to the
linear passthrough functions if none of the currently prepared pixmaps
are tiled.
Maarten.
2010 Mar 28
2
vesamenu requirement
Dear listener
I'm having problem trying to setup a 640x480 image background with latest
syslinux...
the system start correctly but graphics is not shown at all... only text is
visible...
are there minimum requirements for a graphic extlinux background ?
CPU is a Vortex86Sx (with no math processor) at 300MHz, 128MB RAM
video card is a XGI Volari Z9s with 32MB RAM
is there a way to
2010 Jun 25
1
Trying to tile wireframe plots (using lattice package)
Hi all,
I'm trying to print a number of wireframe plots (generated using the
lattice package), and I want them to appear in a two-by two matrix along
with some other (standard) plots. In other words I am trying to create a
subplot or tiled plot that works for wireframes.
I've tried the methods discussed in:
http://tolstoy.newcastle.edu.au/R/e2/help/07/07/21238.html
but while they work
2008 Aug 03
7
[Bug 16978] New: "tile offscreen pixmaps" causing graphics corruption on NV50?
http://bugs.freedesktop.org/show_bug.cgi?id=16978
Summary: "tile offscreen pixmaps" causing graphics corruption on
NV50?
Product: xorg
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2013 May 20
2
[LLVMdev] Polly issue
Hi,
When I test "matmul" in the polly directory, I get the following
performance data:
//===============================
--> 12. Compare the runtime of the executables
time ./matmul.normalopt.exe
0:23.53 real, 23.48 user, 0.00 sys
time ./matmul.polly.interchanged.exe
0:22.86 real, 22.82 user, 0.01 sys
time ./matmul.polly.interchanged+tiled.exe
0:22.87 real, 22.83 user, 0.00 sys
2009 Mar 08
4
[PATCH 1/5] nv50: implement wfb
- Only for sufficiently new xserver's and exa_driver_pixmaps.
---
src/nouveau_exa.c | 217 +++++++++++++++++++++++++++++++++++++++++++++++++++--
src/nv_driver.c | 51 +++++++++++--
src/nv_proto.h | 4 +
src/nv_type.h | 12 +++-
4 files changed, 267 insertions(+), 17 deletions(-)
diff --git a/src/nouveau_exa.c b/src/nouveau_exa.c
index 93fc3c5..074a226 100644
---
2018 Dec 13
2
efi config hang
@Carl,
I'll repeat what I said in my prior email: you don't have to keep
looking, we already achieved what you want (considering that you are
willing to "disregard" the screen problems and similar issues, at least
for now, according to your own emails).
In short:
1_ Re-read my email from 2018Dec05:
www.syslinux.org/archives/2018-December/026247.html
where I posted
2014 Apr 26
0
efi vesamenu 6.03-pre
This is a bug report about Syslinux 6.03-pre11 in EFI.
To Syslinux EFI developers; the results can be replicated in real
hardware.
I apologize for the length of the email; I am describing the steps
necessary to reproduce the confusing behaviors the best I can.
I have been experimenting with VBox and Syslinux EFI32.
In EFI, the default screen resolution for [vesa]menu.c32 is not 640 x
480
2013 Sep 04
1
[PATCH] drm/nouveau: do not move buffers when not needed
Op 04-09-13 03:24, Ben Skeggs schreef:
> On Mon, Jul 15, 2013 at 6:39 PM, Maarten Lankhorst
> <maarten.lankhorst at canonical.com> wrote:
>> Op 15-07-13 08:05, Ben Skeggs schreef:
>>> On Fri, Jul 12, 2013 at 10:45 PM, Maarten Lankhorst
>>> <maarten.lankhorst at canonical.com> wrote:
>>>> I have no idea what this bogus restriction on placement
2008 Feb 15
1
vesamenu.c32 + include + CLI woes
Hi all,
In June 2007 Jerry Nelson started a thread on this mailing list about a problem he was seeing. The thread was http://syslinux.zytor.com/archives/2007-June/008673.html
After several hours of searching through the list, I am still convinced that his problem was never solved and is very valid. I recently moved from the old syslinux config options model (all labels in 1 default config file)
2018 Dec 06
2
efi config hang
works with legacy, hangs with efi.
where works is:
No DEFAULT or UI configuration directive found!
but enter and ^v make things happen
hangs is: nothing happens, no response from keyboard, have to reboot.
note:
config prompt.cfg
prompt.cfg does not exist, but I would expect similar behaviour
between efi and legacy.
test is:
starting with blank image, mkfs, mount it...
+ cp
2019 Sep 29
3
vesamenu.c32 and EFI
Hello!
I've been attempting to add EFI support to a linux live distro (slax),
it's built on a syslinux bootloader.
I can get EFI to work using menu.c32 on syslinux 6.03; however ideally
we'd like the VESA menu as well.
When we use the vesamenu.c32 and libcom32.c32 from 6.03 we end up with a
blank screen and the machine
seems to hang. I've tried adding MENU RESOLUTION based on
2018 Dec 07
2
efi config hang
On Thu, Dec 6, 2018 at 5:14 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote:
>
>
> > works with legacy, hangs with efi.
> >
> > where works is:
> > No DEFAULT or UI configuration directive found!
> > but enter and ^v make things happen
> >
> > hangs is: nothing happens, no response from keyboard, have to reboot.
> >
> > note:
2019 Jan 29
2
[PATCH] drm/nouveau: mark expected switch fall-through
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warning:
drivers/gpu/drm/nouveau/nouveau_bo.c:1434:53: warning: this statement may fall through [-Wimplicit-fallthrough=]
Warning level 3 was used: -Wimplicit-fallthrough=3
This patch is part of the ongoing efforts to enabling
-Wimplicit-fallthrough.