WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] OpenSuse 11 hvm domU: screen resolution up to 640x480

On Wed, Nov 9, 2011 at 10:35 AM, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> On Tue November 8 2011, 10:05:40 PM, Flavio wrote:
> This won't work for another reason: 'extra=' is a pv config option for passing
> extra kernel options to the boot process, as reflected by /proc/cmdline. Only
> adding it to menu.lst would work, IF xen-fbfront is builtin, and the syntax is
> as Fajar suggested - xen-fbfront.video=32,1280,1024. If it is not builtin, you
> must use the /etc/modprobe.d approach.
>

I lost track of what Flavio is using.

Anyway, if it's PV, using something like
"xen-fbfront.video=16,1280,1024" on kernel command line should work
regardless whether its built-on or module. If it's module, you also
have the option of using /etc/modprobe.d


> However, beyond syntax problems. I doubt this would work at all in an hvm
> domu, as they don't use fbfront - that's a pv driver. (Fajar - you can verify
> this, right?) 'lspci -vvv' will tell you what driver is loaded for your video
> controller. Pls post the output of 'lspci -vvv -s video-device-number', and
> then for the driver mentioned at the end, post 'modinfo driver-name'.

with stdvga=0, you'd get

00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00
[VGA controller])
        Subsystem: XenSource, Inc. Device 0001
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=32M]
        Region 1: Memory at f3000000 (32-bit, non-prefetchable) [size=4K]
        Expansion ROM at <unassigned> [disabled]
        Kernel modules: cirrusfb

and starting X directly would get you lots of entries like this on Xorg.0.log

[    89.540] (II) CIRRUS(0): Not using default mode "1280x1024" (bad
mode clock/interlace/doublescan)
[    89.540] (II) CIRRUS(0): Not using default mode "1600x1200"
(insufficient memory for mode)
[    89.540] (II) CIRRUS(0): Not using default mode "800x600" (bad
mode clock/interlace/doublescan)

... and

[    89.541] (--) CIRRUS(0): Virtual size is 1024x768 (pitch 1024)
[    89.542] (**) CIRRUS(0): *Default mode "1024x768": 65.0 MHz, 48.4
kHz, 60.0 Hz
[    89.542] (II) CIRRUS(0): Modeline "1024x768"x60.0   65.00  1024
1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
[    89.542] (**) CIRRUS(0): *Default mode "800x600": 40.0 MHz, 37.9
kHz, 60.3 Hz
[    89.542] (II) CIRRUS(0): Modeline "800x600"x60.3   40.00  800 840
968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)


-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>