search for: gfxterm

...hough, but you should be able to adapt it easily enough). Since you already have a working BIOS PXE, I'll assume you know how to make that config file. The kernel/initrd lines take HTTP URLs just fine, so that's much faster. Here's what the output of my grub2.pl CGI looks like (I use gfxterm so I can load a larger font that I set up locally in the TFTP root - you should be able to just skip that line): ******************** terminal_input console loadfont /12x26.pf2 insmod gfxterm set gfxmode=auto terminal_output gfxterm set timeout=-1 set timeout=-1 menuentry 'Install Fedora rel...

I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64 bit version using the tutorial at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/ on a Lenovo thinkcentre workstation. When I boot I get a kernel panic. If I boot the Linux kernel that I compiled using the

We have a working PXE setup. I've tried to adapt it to UEFI as per RHEL6 manual, but the client won't boot. Strangely, tcpdump shows that the client tries to download all files via tftp from the dhcp server rather than the tftp server (they are different). next-server is pointing to the tftp server. Any clues?

...vbe insmod vga insmod video_bochs insmod video_cirrus } insmod part_msdos insmod ext2 set root='(/dev/xvda,msdos1)' search --no-floppy --fs-uuid --set=root f395d5a0-4612-4872-806c-33cd37c152f0 if loadfont /usr/share/grub/unicode.pf2 ; then set gfxmode=640x480 load_video insmod gfxterm insmod part_msdos insmod ext2 set root='(/dev/xvda,msdos1)' search --no-floppy --fs-uuid --set=root f395d5a0-4612-4872-806c-33cd37c152f0 set locale_dir=($root)/boot/grub/locale set lang=en_US insmod gettext fi terminal_output gfxterm set timeout=5 ### END /etc/grub.d/00_header...

...d0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 0b8cebb6-e937-402c-b9e1-16d4e422b590 else search --no-floppy --fs-uuid --set=root 0b8cebb6-e937-402c-b9e1-16d4e422b590 fi font="/usr/share/grub/unicode.pf2" fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm fi terminal_input console terminal_output gfxterm set timeout=5 ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/09_xen ### menuentry ''Xen 4.2.2 / Arch GNU/Linux, with Linux linux'' --class xen --class arch --class gnu-linux --class gnu --class os { insmod part_gpt...

...nsmod video_bochs + insmod video_cirrus +} + +insmod part_msdos +insmod ext2 +set root=''(/dev/xvda,msdos1)'' +search --no-floppy --fs-uuid --set=root f395d5a0-4612-4872-806c-33cd37c152f0 +if loadfont /usr/share/grub/unicode.pf2 ; then + set gfxmode=640x480 + load_video + insmod gfxterm + insmod part_msdos + insmod ext2 + set root=''(/dev/xvda,msdos1)'' + search --no-floppy --fs-uuid --set=root f395d5a0-4612-4872-806c-33cd37c152f0 + set locale_dir=($root)/boot/grub/locale + set lang=en_US + insmod gettext +fi +terminal_output gfxterm +set timeout=5 +### END...

Hello, I have installed the Xen 4.1.1 and a working kernel 2.6.32.43 which supports Xen on a Ubuntu Linux 10.04 LTS. However, I have never successfully booted the Hypervisor and Dom0. The screen is always black after some kernel messages rapidly go by. I think that I may pass the wrong parameters to the kernel or Hypervisor with GRUB2. Can any one share his/her working grub.cfg for GRUB2 with

...d vga + insmod video_bochs + insmod video_cirrus +} + +insmod part_msdos +insmod ext2 +set root='(/dev/xvda,msdos1)' +search --no-floppy --fs-uuid --set=root f395d5a0-4612-4872-806c-33cd37c152f0 +if loadfont /usr/share/grub/unicode.pf2 ; then + set gfxmode=640x480 + load_video + insmod gfxterm + insmod part_msdos + insmod ext2 + set root='(/dev/xvda,msdos1)' + search --no-floppy --fs-uuid --set=root f395d5a0-4612-4872-806c-33cd37c152f0 + set locale_dir=($root)/boot/grub/locale + set lang=en_US + insmod gettext +fi +terminal_output gfxterm +set timeout=5 +### END /etc/grub....

Hi I did the dd iso to my USB. all is fine. I can mount the second partition (which is not iso 9660) and edit the grub.cfg file. Question is what do I run after that so my new menu option appears ? grub2-install /dev/sdd Is that the correct command to get grub to notice my new file ? Assuming sdd is the USB disk of course. Thanks, jerry

I''m running Xen 4.1 (4.1.3-3ubuntu1.3) on an Ubuntu 12.10 server with an AMD FX-8150 processor (8 cores) and 16 GB of RAM. When I boot the server, Xen sees only 3 GB of RAM (instead of 16 GB). If I try to create a domU with more than about 1.5 GB of RAM, the create fails with messages saying it "could not allocate memory for HVM guest". Here''s the output when I do

I''ve installed debian lenny amd64, it is frozen now. I''ve install kernel for xen support but it doesn''t start. It says "you need to load kernel first" but I''ve installed all the packages concerning xen, also packages related to the kernel. Perhaps lenny doesn''t support xen anymore? Any solution?

hi guys, It''s my first time here and in a mailing lists, I only participated in forums before. Please, If I make a mistake you should advise me. Let''s go! I was reading "xencommons not start" in a Remus Forum in order to install Remus. Well… I followed the tutorial < http://remusha.wikidot.com/configuring-and-installing-remus>, I reboot in xen_unstable and I had

hi guys, It''s my first time here and in a mailing lists, I only participated in forums before. Please, If I make a mistake you should advise me. Let''s go! I was reading "xencommons not start" in a Remus Forum in order to install Remus. Well… I followed the tutorial < http://remusha.wikidot.com/configuring-and-installing-remus>, I reboot in xen_unstable and I had

...efi\gcry_whirlpool.mod (24.4 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\gdb.mod (24.8 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\geli.mod (5.8 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\gettext.mod (5 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\gfxmenu.mod (40.7 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\gfxterm.mod (10.0 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\gfxterm_background.mod (2.9 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\gfxterm_menu.mod (5.0 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\gptsync.mod (3.8 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\halt.mod (3.9 KB) Extracting: F:\EFI\BOOT\grub\i386-ef...

On 3/3/2016 07:43, Pete Batard via Syslinux wrote: > [...] as far as I am concerned, 'A "version" such as "6.03" [is not] > enough'. [...] I'd like to help to improve Syslinux with regards to version-related concerns. Having typed that, perhaps we could discuss your (or Rufus') specific needs, in parallel? Do I understand correctly that the primary