|
Like I said in my original reply, add it to the XEN line, NOT the kernel line. So, grub config should look like this:
title XEN -- openSUSE 10.3 - 2.6.22.17-0.1
root (hd0,0)
kernel /boot/xen.gz vga=keep,text-80x25
...
Make sense?
>>> On 2008/03/13 at 06:22, Stuart Poulton <swp@xxxxxxxxxxxxxx> wrote:
Nick,
Many thanks, no joy. Heres the grub config
###Don't change this comment - YaST2 identifier: Original name: xen###
title XEN -- openSUSE 10.3 - 2.6.22.17-0.1
root (hd0,0)
kernel /boot/xen.gz
module /boot/vmlinuz-2.6.22.17-0.1-xen root=/dev/disk/by-id/scsi-360019b90c3b604000f6a979902f95c1c-part1 console=ttyS1,57600 console=tty0 vga=keep,text-80x25 resume=/dev/sda2 splash=silent showopts
module /boot/initrd-2.6.22.17-0.1-xen
Thanks
Stuart
On Thu, 2008-03-13 at 06:13 -0600, Nick Couchman wrote:
> Append the following to the end of the XEN line (NOT the kernel line)
> in grub:
> vga=keep,text-80x25
>
> The issue seems to be with differing screen resolutions between SuSE
> and XEN, and this forces the XEN kernel to use the same screen
> resolution as SuSE eventually uses.
>
> -Nick
>
> >>> On 2008/03/13 at 03:35, Stuart Poulton <swp@xxxxxxxxxxxxxx> wrote:
>
> Dear all,
>
> I'm running Xen on an opensuse 10.3 system, with the following RPMS
>
> kernel-xen-2.6.22.17-0.1
> xen-3.1.0_15042-51.3
>
> Booting the system into a non xen kernel, gives a correctly
> functioning
> console.
>
> However on using a xen kernel, the console appears to be delayed by
> ~30/40 lines. Any suggestions as to what might be causing this please.
>
> Thanks
>
> Stuart
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
|
