search for: initrdg

...util.c32 > ? ??? vesamenu.c32 > ??? disk.lbl > ??? exithelp.cfg > ??? f10.txt > ??? f1.txt > ??? f2.txt > ??? f3.txt > ??? f4.txt > ??? f5.txt > ??? f6.txt > ??? f7.txt > ??? f8.txt > ??? f9.txt > ??? g2ldr > ??? g2ldr.mbr > ??? gtk.cfg > ??? initrdg.gz > ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys > ??? linux > ??? menu.cfg > ??? NvVars > ??? prompt.cfg > ??? rqgtk.cfg > ??? rqspkgtk.cfg > ??? rqtxt.cfg > ??? setup.exe > ??? spkgtk.cfg > ??? splash.png > ??? stdmenu.cfg > ??? syslinux.cfg >...

> > > > You should be able to see the effects of the DISPLAY directive when > > testing the floppy image I sent you, because it starts with the boot > > prompt, not with a menu. > > I see the effects, both good and bad. I'm having trouble knowing how > bad the bad is. How about comparing it with the current behaviour in BIOS mode? > I'm not

...vesa.c32 ? ??? vesainfo.c32 ? ??? vesamenu.c32 ? ??? vpdtest.c32 ? ??? whichsys.c32 ? ??? zzjson.c32 ??? exithelp.cfg ??? f10.txt ??? f1.txt ??? f2.txt ??? f3.txt ??? f4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? g2ldr ??? g2ldr.mbr ??? gtk.cfg ??? initrdg.gz ??? initrd.gz ??? ldlinux.c32 ??? ldlinux.sys ??? libcom32.c32 ??? libutil.c32 ??? linux ??? menu.cfg ??? NvVars ??? prompt.cfg ??? rqgtk.cfg ??? rqspkgtk.cfg ??? rqtxt.cfg ??? setup.exe ??? spkgtk.cfg ??? splash.png ??? stdmenu.cfg ??? syslinux.cfg ??? txt.cfg ??? vesamenu.c32 ??? win32-loader....

....cfg ??? adtxt.cfg ??? boot ? ??? syslinux ? ??? libcom32.c32 ? ??? libutil.c32 ? ??? vesamenu.c32 ??? disk.lbl ??? exithelp.cfg ??? f10.txt ??? f1.txt ??? f2.txt ??? f3.txt ??? f4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? g2ldr ??? g2ldr.mbr ??? gtk.cfg ??? initrdg.gz ??? initrd.gz ??? ldlinux.c32 ??? ldlinux.sys ??? linux ??? menu.cfg ??? NvVars ??? prompt.cfg ??? rqgtk.cfg ??? rqspkgtk.cfg ??? rqtxt.cfg ??? setup.exe ??? spkgtk.cfg ??? splash.png ??? stdmenu.cfg ??? syslinux.cfg ??? txt.cfg ??? win32-loader.ini except that PATH into the bios files is a pro...

...help.cfg > > ??? f10.txt > > ??? f1.txt > > ??? f2.txt > > ??? f3.txt > > ??? f4.txt > > ??? f5.txt > > ??? f6.txt > > ??? f7.txt > > ??? f8.txt > > ??? f9.txt > > ??? g2ldr > > ??? g2ldr.mbr > > ??? gtk.cfg > > ??? initrdg.gz > > ??? initrd.gz > > ??? ldlinux.c32 > > ??? ldlinux.sys > > ??? linux > > ??? menu.cfg > > ??? NvVars > > ??? prompt.cfg > > ??? rqgtk.cfg > > ??? rqspkgtk.cfg > > ??? rqtxt.cfg > > ??? setup.exe > > ??? spkgtk.cfg > &g...

...help.cfg > > ??? f10.txt > > ??? f1.txt > > ??? f2.txt > > ??? f3.txt > > ??? f4.txt > > ??? f5.txt > > ??? f6.txt > > ??? f7.txt > > ??? f8.txt > > ??? f9.txt > > ??? g2ldr > > ??? g2ldr.mbr > > ??? gtk.cfg > > ??? initrdg.gz > > ??? initrd.gz > > ??? ldlinux.c32 > > ??? ldlinux.sys > > ??? libcom32.c32 > > ??? libutil.c32 > > ??? linux > > ??? menu.cfg > > ??? NvVars > > ??? prompt.cfg > > ??? rqgtk.cfg > > ??? rqspkgtk.cfg > > ??? rqtxt.cfg &gt...

...gt; ? ??? whichsys.c32 > ? ??? zzjson.c32 > ??? exithelp.cfg > ??? f10.txt > ??? f1.txt > ??? f2.txt > ??? f3.txt > ??? f4.txt > ??? f5.txt > ??? f6.txt > ??? f7.txt > ??? f8.txt > ??? f9.txt > ??? g2ldr > ??? g2ldr.mbr > ??? gtk.cfg > ??? initrdg.gz > ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys > ??? libcom32.c32 > ??? libutil.c32 > ??? linux > ??? menu.cfg > ??? NvVars > ??? prompt.cfg > ??? rqgtk.cfg > ??? rqspkgtk.cfg > ??? rqtxt.cfg > ??? setup.exe > ??? spkgtk.cfg > ??? splash.png >...

I want to eufi boot this image: http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz there is a bug against it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913523 I'd like to fix the resulting usb stick for my use, and also fix it in a way that can be used to fix the upstream bug. I'm trying to follow the guids