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] xen 3.0.3: blank screen in xserver-xorg in dom0

To: Yasir Assam <list1@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] xen 3.0.3: blank screen in xserver-xorg in dom0
From: Tim Post <tim.post@xxxxxxxxxxxxxxx>
Date: Tue, 24 Oct 2006 11:46:39 +0800
Cc: Xen <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 23 Oct 2006 20:47:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <453C7A75.2060006@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Net Kinetics
References: <453C7A75.2060006@xxxxxxxxxxxxxxx>
Reply-to: tim.post@xxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
What version of udev are you using? This sounds very much like a bug
that's been circulating on the Debian lists. 

If sarge, sarge + etch backports , udev may be your issue, from the time
frame you noted I'd venture to suggest upgrading udev and see if that
cures it.

HTH
-Tim

On Mon, 2006-10-23 at 18:16 +1000, Yasir Assam wrote:
> I was happily using an unstable version of xen built July from source 
> (pre 3.0.3) and I downloaded the 3.0.3 source and built it using:
> 
> # make world
> # make install
> 
> dom0 boots ok, but when the the xorg xserver starts I just get a blank 
> screen - I think it's not picking up the right modes.
> 
> (BTW - 640x480 does work, but it's the only resolution that works).
> 
> It's really strange, because xorg.conf is the same whether it's runinng 
> under Xen or a normal kernel. Here's a diff between the xorg log 
> starting on a normal kernel and the xen 3.0.3 kernel:
> 
> 
> 
> 6c6
> < Current Operating System: Linux eir 2.6.17.4-eir #1 SMP Tue Jul 11 
> 12:19:50 EST 2006 i686
> ---
>  > Current Operating System: Linux eir 2.6.16.29-xen #1 SMP Sun Oct 22 
> 19:30:13 EST 2006 i686
> 14c14
> < (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 23 09:44:56 2006
> ---
>  > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 23 09:41:44 2006
> 436,486c436
> < (II) VESA(0): VESA VBE DDC supported
> < (II) VESA(0): VESA VBE DDC Level 2
> < (II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
> < (II) VESA(0): VESA VBE DDC read successfully
> < (II) VESA(0): Manufacturer: MEL  Model: 4625  Serial#: 16843009
> < (II) VESA(0): Year: 2003  Week: 18
> < (II) VESA(0): EDID Version: 1.3
> < (II) VESA(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
> < (II) VESA(0): Sync:  Separate  Composite
> < (II) VESA(0): Max H-Image Size [cm]: horiz.: 37  vert.: 27
> < (II) VESA(0): Gamma: 2.20
> < (II) VESA(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
> < (II) VESA(0): First detailed timing is preferred mode
> < (II) VESA(0): GTF timings supported
> < (II) VESA(0): redX: 0.626 redY: 0.339   greenX: 0.279 greenY: 0.600
> < (II) VESA(0): blueX: 0.149 blueY: 0.072   whiteX: 0.283 whiteY: 0.297
> < (II) VESA(0): Supported VESA Video Modes:
> < (II) VESA(0): 720x400@70Hz
> < (II) VESA(0): 720x400@88Hz
> < (II) VESA(0): 640x480@60Hz
> < (II) VESA(0): 640x480@67Hz
> < (II) VESA(0): 640x480@72Hz
> < (II) VESA(0): 640x480@75Hz
> < (II) VESA(0): 800x600@56Hz
> < (II) VESA(0): 800x600@60Hz
> < (II) VESA(0): 800x600@72Hz
> < (II) VESA(0): 800x600@75Hz
> < (II) VESA(0): 832x624@75Hz
> < (II) VESA(0): 1024x768@87Hz (interlaced)
> < (II) VESA(0): 1024x768@60Hz
> < (II) VESA(0): 1024x768@70Hz
> < (II) VESA(0): 1024x768@75Hz
> < (II) VESA(0): 1280x1024@75Hz
> < (II) VESA(0): 1152x870@75Hz
> < (II) VESA(0): Manufacturer's mask: 0
> < (II) VESA(0): Supported Future Video Modes:
> < (II) VESA(0): #0: hsize: 640  vsize 480  refresh: 85  vid: 22833
> < (II) VESA(0): #1: hsize: 800  vsize 600  refresh: 85  vid: 22853
> < (II) VESA(0): #2: hsize: 1024  vsize 768  refresh: 85  vid: 22881
> < (II) VESA(0): #3: hsize: 1152  vsize 864  refresh: 75  vid: 20337
> < (II) VESA(0): #4: hsize: 1280  vsize 960  refresh: 85  vid: 22913
> < (II) VESA(0): #5: hsize: 1280  vsize 1024  refresh: 85  vid: 39297
> < (II) VESA(0): #6: hsize: 1600  vsize 1200  refresh: 75  vid: 20393
> < (II) VESA(0): #7: hsize: 1792  vsize 1344  refresh: 65  vid: 17857
> < (II) VESA(0): Supported additional Video Mode:
> < (II) VESA(0): clock: 157.5 MHz   Image Size:  356 x 266 mm
> < (II) VESA(0): h_active: 1280  h_sync: 1344  h_sync_end 1504 
> h_blank_end 1728 h_border: 0
> < (II) VESA(0): v_active: 1024  v_sync: 1025  v_sync_end 1028 
> v_blanking: 1072 v_border: 0
> < (II) VESA(0): Ranges: V min: 50  V max: 160 Hz, H min: 30  H max: 96 
> kHz, PixClock max 230 MHz
> < (II) VESA(0): Monitor name: DPLUS93SB
> < (II) VESA(0): Serial No: 3500101YR
> ---
>  > (II) VESA(0): VESA VBE DDC not supported
> 517c467
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 559c509
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 643c593
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 727c677
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 811c761
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 853c803
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 895c845
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 937c887
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 979c929
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1021c971
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1063c1013
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1105c1055
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1147c1097
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1189c1139
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1231c1181
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1273c1223
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1315c1265
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1357c1307
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1399c1349
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1441c1391
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1483c1433
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1525c1475
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1567c1517
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1609c1559
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1651c1601
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1693c1643
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1735c1685
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1777c1727
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1790d1739
> < *(WW) (2048x1536,DPLUS93SB) mode clock 266.95MHz exceeds DDC maximum 
> 230MHz
> 1820c1769
> <     PhysBasePtr: 0xe0000000
> ---
>  >     PhysBasePtr: 0x0
> 1835,1836c1784,1785
> < (II) VESA(0): DPLUS93SB: Using default hsync range of 30.00-96.00 kHz
> < (II) VESA(0): DPLUS93SB: Using default vrefresh range of 50.00-160.00 Hz
> ---
>  > (II) VESA(0): DPLUS93SB: Using default hsync range of 28.00-33.00 kHz
>  > (II) VESA(0): DPLUS93SB: Using default vrefresh range of 43.00-72.00 Hz
> 1842d1790
> < (II) VESA(0): Not using built-in mode "2048x1536" (width too large for 
> virtual size)
> 1850,1854c1798
> < (II) VESA(0): Attempting to use 85Hz refresh for mode "1280x1024" (11b)
> < (II) VESA(0): Attempting to use 85Hz refresh for mode "1024x768" (118)
> < (II) VESA(0): Attempting to use 85Hz refresh for mode "800x600" (115)
> < (II) VESA(0): Attempting to use 85Hz refresh for mode "640x480" (112)
> < (II) VESA(0): Attempting to use 85Hz refresh for mode "640x400" (13e)
> ---
>  > (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112)
> 1921,1922c1865,1866
> < (II) VESA(0): virtual address = 0xb38cb000,
> <     physical address = 0xe0000000, size = 67108864
> ---
>  > (II) VESA(0): virtual address = 0xb78d5000,
>  >     physical address = 0xa0000, size = 65536
> 1973a1918
>  > (II) Configured Mouse: ps2EnableDataReporting: succeeded
> 
> 
> 
> 
> The main difference beteween the blank screen and the ok screen is that 
> when the display works, I get "VESA VBE DDC supported" but when it goes 
> blank I get "VESA VBE DDC not supported". I'm guessing that because DDC 
> doesn't work under xen 3.0.3 it's not picking up the right modes and my 
> xorg.conf doesn't work. Here's xorg.conf:
> 
> 
> 
> # /etc/X11/xorg.conf (xorg X Window System server configuration file)
> #
> # This file was generated by dexconf, the Debian X Configuration tool, using
> # values from the debconf database.
> #
> # Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
> # (Type "man /etc/X11/xorg.conf" at the shell prompt.)
> #
> # This file is automatically updated on xserver-xorg package upgrades *only*
> # if it has not been modified since the last upgrade of the xserver-xorg
> # package.
> #
> # If you have edited this file but would like it to be automatically updated
> # again, run the following command:
> #   sudo dpkg-reconfigure -phigh xserver-xorg
> 
> Section "Files"
>     FontPath    "/usr/share/fonts/X11/misc"
>     FontPath    "/usr/X11R6/lib/X11/fonts/misc"
>     FontPath    "/usr/share/fonts/X11/cyrillic"
>     FontPath    "/usr/X11R6/lib/X11/fonts/cyrillic"
>     FontPath    "/usr/share/fonts/X11/100dpi/:unscaled"
>     FontPath    "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
>     FontPath    "/usr/share/fonts/X11/75dpi/:unscaled"
>     FontPath    "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
>     FontPath    "/usr/share/fonts/X11/Type1"
>     FontPath    "/usr/X11R6/lib/X11/fonts/Type1"
>     FontPath    "/usr/share/fonts/X11/100dpi"
>     FontPath    "/usr/X11R6/lib/X11/fonts/100dpi"
>     FontPath    "/usr/share/fonts/X11/75dpi"
>     FontPath    "/usr/X11R6/lib/X11/fonts/75dpi"
>     # path to defoma fonts
>     FontPath    "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
> EndSection
> 
> Section "Module"
>     Load    "i2c"
>     Load    "bitmap"
>     Load    "ddc"
>     Load    "dri"
>     Load    "extmod"
>     Load    "freetype"
>     Load    "glx"
>     Load    "int10"
>     Load    "type1"
>     Load    "vbe"
> EndSection
> 
> Section "InputDevice"
>     Identifier    "Generic Keyboard"
>     Driver        "kbd"
>     Option        "CoreKeyboard"
>     Option        "XkbRules"    "xorg"
>     Option        "XkbModel"    "pc104"
>     Option        "XkbLayout"    "us"
> EndSection
> 
> Section "InputDevice"
>     Identifier    "Configured Mouse"
>     Driver        "mouse"
>     Option        "CorePointer"
>     Option        "Device"        "/dev/input/mice"
>     Option        "Protocol"        "ExplorerPS/2"
>     Option        "Emulate3Buttons"    "true"
> EndSection
> 
> Section "Device"
>     Identifier    "Generic Video Card"
>     Driver        "vesa"
>     BusID        "PCI:0:5:0"
> EndSection
> 
> Section "Monitor"
>     Identifier    "DPLUS93SB"
>     Option        "DPMS"
> EndSection
> 
> Section "Screen"
>     Identifier    "Default Screen"
>     Device        "Generic Video Card"
>     Monitor        "DPLUS93SB"
>     DefaultDepth    24
>     SubSection "Display"
>         Depth        1
>         Modes        "1600x1200" "1280x1024" "1280x960" "1152x864" 
> "1024x768" "832x624" "800x600" "720x400" "640x480"
>     EndSubSection
>     SubSection "Display"
>         Depth        4
>         Modes        "1600x1200" "1280x1024" "1280x960" "1152x864" 
> "1024x768" "832x624" "800x600" "720x400" "640x480"
>     EndSubSection
>     SubSection "Display"
>         Depth        8
>         Modes        "1600x1200" "1280x1024" "1280x960" "1152x864" 
> "1024x768" "832x624" "800x600" "720x400" "640x480"
>     EndSubSection
>     SubSection "Display"
>         Depth        15
>         Modes        "1600x1200" "1280x1024" "1280x960" "1152x864" 
> "1024x768" "832x624" "800x600" "720x400" "640x480"
>     EndSubSection
>     SubSection "Display"
>         Depth        16
>         Modes        "1600x1200" "1280x1024" "1280x960" "1152x864" 
> "1024x768" "832x624" "800x600" "720x400" "640x480"
>     EndSubSection
>     SubSection "Display"
>         Depth        24
>         Modes        "1600x1200" "1280x1024" "1280x960" "1152x864" 
> "1024x768" "832x624" "800x600" "720x400" "640x480"
>     EndSubSection
> EndSection
> 
> Section "ServerLayout"
>     Identifier    "Default Layout"
>     Screen        "Default Screen"
>     InputDevice    "Generic Keyboard"
>     InputDevice    "Configured Mouse"
> EndSection
> 
> Section "DRI"
>     Mode    0666
> EndSection
> 
> 
> 
> 
> 
> As I said before, my previous build of Xen works fine. Here's the 
> difference in the kernel config files between an unstable build of Xen 
> from July and the latest unstable post 3.0.3 version:
> 
> 
> 
> 3,4c3,4
> < # Linux kernel version: 2.6.16.13-xen
> < # Tue Jul 11 14:40:35 2006
> ---
>  > # Linux kernel version: 2.6.16.29-xen
>  > # Mon Oct 23 13:37:44 2006
> 192a193
>  > CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
> 2379c2380
> < CONFIG_SND_FM801_TEA575X=m
> ---
>  > # CONFIG_SND_FM801_TEA575X_BOOL is not set
> 3012c3013
> < CONFIG_XEN_INTERFACE_VERSION=0x00030202
> ---
>  > CONFIG_XEN_INTERFACE_VERSION=0x00030203
> 3019a3021
>  > CONFIG_XEN_XENBUS_DEV=y
> 3021,3024d3022
> < CONFIG_XEN_PCIDEV_BACKEND=m
> < CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
> < # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
> < # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
> 3026c3024
> < CONFIG_XEN_XENBUS_DEV=y
> ---
>  > CONFIG_XEN_BLKDEV_TAP=y
> 3029a3028,3032
>  > CONFIG_XEN_PCIDEV_BACKEND=m
>  > CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
>  > # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
>  > # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
>  > # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
> 
> 
> 
> 
> 
> Does anyone know why this might be happening? Is it because of a kernel 
> difference between Xen 3.0.3 and Xen 3.0.2? Is it because of a 
> difference in kernel configuration?
> 
> 
> Any help given will be really appreciated!!
> 
> Yasir
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 


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

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