search for: grub_terminal

...xen-hypervisor-4.1-amd64 xen-utils-4.1 xenwatch xen-tools xen-utils-common xenstore-utils 3) updated grub as follows: - changed the default boot order - added the following entries GRUB_DISABLE_OS_PROBER=true GRUB_SERIAL_COMMAND="serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1" GRUB_TERMINAL="console serial" GRUB_CMDLINE_XEN="com1=9600,8n1 console=com1,vga" GRUB_CMDLINE_LINUX="console=tty0 console=hvc0"for the new menu entries and xend-config.sxp 4) made the following changes to /etc/default/xendomains: XENDOMAINS_SAVE="" XENDOMAINS_RESTORE=false...

...LINUX ../vmlinuz INITRD ../initrd.img APPEND root=PARTUUID=c3b28cc5-93d5-4cdc-b86e-857231520205 rw quiet The same application running on the same system displays 16 colours if booted with grub2 (but still using VGA text mode). FWIW, grub2's config is using: GRUB_TERMINAL=console GRUB_GFXPAYLOAD_LINUX=keep Could anybody explain me why there's such difference and why syslinux leaves the VGA text mode with only 8 colours where there should be 16 ? Thanks.

...39; three times to switch input to DOM0) ---- /etc/default/grub ---- # If you change this file, run ''update-grub'' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n ''Simple configuration'' GRUB_TERMINAL=serial GRUB_SERIAL_COMMAND="serial --port=0x3f8 --unit=0 --speed=115200 --word=8 --parity=no --stop=1" GRUB_DEFAULT="Xen" #GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=32 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_XEN=&...

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703586 Ideas how to move this forward? Debugging techniques? I''m guessing that it''s specific to my hardware, since I''m not seeing anyone else complaining. Anyone else succeed in doing this on an EliteBook?

Hi all! Recently I found some problems after upgrading one of our virtual machines from ubuntu 10.10. to later releases. Root problem is inactive VNC terminal after booting grub. It happens because of using framebuffer at boot process. To fix this problem you should change at /etc/default/grub: GRUB_TERMINAL=console And run # update-grub # reboot This fixes problem. But I think there should be some fix to use fb in vnc without problems. I use: libvirt 0.9.11.3 QEMU emulator version 1.0 (qemu-kvm-1.0 Debian 1.0+dfsg-8~bpo60+1), Copyright (c) 2003-2008 Fabrice Bellard <graphics type='vnc...

...D ../initrd.img > APPEND root=PARTUUID=c3b28cc5-93d5-4cdc-b86e-857231520205 > rw quiet > > The same application running on the same system displays 16 colours if > booted with grub2 (but still using VGA text mode). FWIW, grub2's config > is using: > > GRUB_TERMINAL=console > GRUB_GFXPAYLOAD_LINUX=keep > > Could anybody explain me why there's such difference and why syslinux > leaves the VGA text mode with only 8 colours where there should be 16 ? > What system font are you using? -hpa

...asily install # packages and run commands in the target system. #d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh +d-i preseed/late_command string in-target sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT=.*/GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0,115200n8"/g; s/# *GRUB_TERMINAL=console/GRUB_TERMINAL=serial/g' /etc/default/grub; in-target update-grub diff --git a/builder/templates/make-template.ml b/builder/templates/make-template.ml index 7b46bdacb..42ff48eb9 100755 --- a/builder/templates/make-template.ml +++ b/builder/templates/make-template.ml @@ -1027,14 +1027,8...

...ots normally, but I didn't try to create any domU. Anyway i'ts not a good idea to use unstable on the server. About the attachments. I added these options into /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10" GRUB_TERMINAL=serial GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no --stop=1" GRUB_CMDLINE_XEN="dom0_mem=1024M loglvl=all guest_loglvl=all sync_console console_to_ring com1=9600,8n1 console=com1" and captured the output on the serial console. booting_acpi-off_VT-off.l...

Is there a way to get GRUB2 and the kernel to run a "serial" console under KVM? I'm running a Fedora 20 desktop, with libvirt-managed VMs. When I run a CentOS 6 VM, I can set both the boot loader and kernel up to use ttyS0 and get a console compatible with "virsh console". When I try the same with a CentOS 7 VM, it doesn't work. If I set it to ttyS0, I just

Hello List, I'm ironing out details to upgrade a few systems to CentOS7. My servers have BMC with Serial over LAN support. In C5 and C6, I determined how to have BIOS/POST, kernel, and serial console access. I'm reading up on the method to accomplish the pieces with C7. Presently SoL output works, so I see BIOS/POST messages and the GRUB boot list. My changes to enable serial

https://bugs.freedesktop.org/show_bug.cgi?id=58316 Priority: medium Bug ID: 58316 Assignee: nouveau at lists.freedesktop.org Summary: fedora 17 kernel 3.7.0-1.PAE failed plymouth and enable msi error QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified OS: Linux

...fy to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter t...

...fy to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter t...

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)