thr3ads.net - Xen devel - [Xen-devel] Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server [Sep 2009]

If this information is useful, please help other people find it:
Share via:

Boris Derzhavets

2009-Sep-23 15:45 UTC

[Xen-devel] Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Video card Radeon HD 4560.  X-server starts fine under native 2.6.28-11-server
ubuntu kernel.  

X-Windows Setup :-

Downsize the system:

 vi /etc/default/linux-restricted-modules-common:

DISABLED_MODULES=”ath_hal fc fglrx ltm nv”
Install the X11 bare bone:

# aptitude install x-window-system-core

# aptitude install fluxbox fluxconf #lightwight windows manager

# aptitude install dillo #lightweight browser

# aptitude install xfe #lightweight file manager

# apttitude install synaptic #  To install eset & esetroot

Change /etc/X11/xorg.conf:

 # dpkg-reconfigure xserver-xorg #guided setup

 Edit /etc/X11/xorg.conf (use “gtf 1024 768 60″ to obtain the Modeline values)
 X-server starts fine under native Ubuntu Server kernel  and fluxbox is
completely functional.

Attempt to start at Xen 3.5 Dom0 (with the most recent 2.6.31)

dmesg output :-
. . . . . .

[   43.572422] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic 0 pin 16
triggering 1 polarity 1
[   43.572437] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ
16
[   43.710523] [drm] Initialized drm 1.1.0 20060810
[   43.758245] pci 0000:01:00.0: setting latency timer to 64
[   43.758433] [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on
minor 0
[   43.763134] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   44.035133] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   44.035198] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   44.035263] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   44.061841] [drm] Setting GART location based on new memory map
[   44.095779] [drm] Loading RV730/RV740 PFP Microcode
[   44.095805] [drm] Loading RV730/RV740 CP Microcode
[   44.110868] [drm] Resetting GPU
[   44.215007] [drm] writeback test failed
[   79.050085] [drm] Resetting GPU
[  243.858191] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  243.858263] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132051] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132115] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132181] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.157265] [drm] Setting GART location based on new memory map
[  244.190885] [drm] Loading RV730/RV740 PFP Microcode
[  244.190911] [drm] Loading RV730/RV740 CP Microcode
[  244.205974] [drm] Resetting GPU
[  244.310103] [drm] writeback test failed
[  251.220092] [drm] Resetting GPU

Xorg.0.log :-

(II) AIGLX: Screen 0 is not DRI2 capable
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(EE) AIGLX error: Calling driver entry point failed(EE) AIGLX: reverting to
software rendering
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) RADEON(0): Setting screen physical size to 338 x 270
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.6.0, module version = 2.1.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2
keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
(**) Option "xkb_model" "pc105"
(**) AT Translated Set 2 keyboard: xkb_model: "pc105"
(**) Option "xkb_layout" "us"
(**) AT Translated Set 2 keyboard: xkb_layout: "us"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event2"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4,
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button
emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) config/hal: Adding input device HID 062a:0001
(**) HID 062a:0001: always reports core events
(**) HID 062a:0001: Device: "/dev/input/event4"
(II) HID 062a:0001: Found 5 mouse buttons
(II) HID 062a:0001: Found x and y relative axes
(II) HID 062a:0001: Configuring as mouse
(**) HID 062a:0001: YAxisMapping: buttons 4 and 5
(**) HID 062a:0001: EmulateWheelButton: 4, EmulateWheelInertia: 10,
EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "HID 062a:0001" (type:
MOUSE)
(**) HID 062a:0001: (accel) keeping acceleration scheme 1
(**) HID 062a:0001: (accel) filter chain progression: 2.00
(**) HID 062a:0001: (accel) filter stage 0: 20.00 ms
(**) HID 062a:0001: (accel) set acceleration profile 0

Boris.



      



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

Jeremy Fitzhardinge

2009-Sep-23 19:27 UTC

head link

[Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

On 09/23/09 08:45, Boris Derzhavets wrote:> Video card Radeon HD 4560.  X-server starts fine under native
> 2.6.28-11-server
> ubuntu kernel. 
>I assume you''re saying that it fails with 2.6.31-pvops dom0?  How does
it fail?  Is it completely non-functional?  Does the whole system
crash?  Or does X simply fail to start?   Or it does start but is
crippled in some way?

Does it work with 2.6.31 running without Xen?  How do the log files compare?

Thanks,
    J
>
> X-Windows Setup :-
>
> Downsize the system:
> vi /etc/default/linux-restricted-modules-common:
> DISABLED_MODULES=”ath_hal fc fglrx ltm nv” Install the X11 bare bone:
>
> # aptitude install x-window-system-core
> # aptitude install fluxbox fluxconf #lightwight windows manager
> # aptitude install dillo #lightweight browser
> # aptitude install xfe #lightweight file manager
> # apttitude install synaptic # To install eset & esetroot
> Change /etc/X11/xorg.conf:
> # dpkg-reconfigure xserver-xorg #guided setup
> Edit /etc/X11/xorg.conf (use “gtf 1024 768 60″ to obtain the Modeline
> values)
>  X-server starts fine under native Ubuntu Server kernel  and fluxbox
> is completely functional.
>
> Attempt to start at Xen 3.5 Dom0 (with the most recent 2.6.31)
>
> dmesg output :-
> . . . . . .
>
> [   43.572422] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic
> 0 pin 16 triggering 1 polarity 1
> [   43.572437] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
> IRQ 16
> [   43.710523] [drm] Initialized drm 1.1.0 20060810
> [   43.758245] pci 0000:01:00.0: setting latency timer to 64
> [   43.758433] [drm] Initialized radeon 1.31.0 20080528 for
> 0000:01:00.0 on minor 0
> [   43.763134] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035133] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035198] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.061841] [drm] Setting GART location based on new memory map
> [   44.095779] [drm] Loading RV730/RV740 PFP Microcode
> [   44.095805] [drm] Loading RV730/RV740 CP Microcode
> [   44.110868] [drm] Resetting GPU
> [   44.215007] [drm] writeback test failed
> [   79.050085] [drm] Resetting GPU
> [  243.858191] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  243.858263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132051] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132115] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132181] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.157265] [drm] Setting GART location based on new memory map
> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
> [  244.205974] [drm] Resetting GPU
> [  244.310103] [drm] writeback test failed
> [  251.220092] [drm] Resetting GPU
>
> Xorg.0.log :-
>
> (II) AIGLX: Screen 0 is not DRI2 capable
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:01:00.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: drmOpenMinor returns 11
> drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
> (EE) AIGLX error: Calling driver entry point failed(EE) AIGLX:
> reverting to software rendering
> (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
> (II) RADEON(0): Setting screen physical size to 338 x 270
> (II) config/hal: Adding input device AT Translated Set 2 keyboard
> (II) LoadModule: "evdev"
> (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
> (II) Module evdev: vendor="X.Org Foundation"
>     compiled for 1.6.0, module version = 2.1.1
>     Module class: X.Org XInput Driver
>     ABI class: X.Org XInput driver, version 4.0
> (**) AT Translated Set 2 keyboard: always reports core events
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
> (II) AT Translated Set 2 keyboard: Found keys
> (II) AT Translated Set 2 keyboard: Configuring as keyboard
> (II) XINPUT: Adding extended input device "AT Translated Set 2
> keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
> (**) Option "xkb_model" "pc105"
> (**) AT Translated Set 2 keyboard: xkb_model: "pc105"
> (**) Option "xkb_layout" "us"
> (**) AT Translated Set 2 keyboard: xkb_layout: "us"
> (II) config/hal: Adding input device Macintosh mouse button emulation
> (**) Macintosh mouse button emulation: always reports core events
> (**) Macintosh mouse button emulation: Device:
"/dev/input/event2"
> (II) Macintosh mouse button emulation: Found 3 mouse buttons
> (II) Macintosh mouse button emulation: Found x and y relative axes
> (II) Macintosh mouse button emulation: Configuring as mouse
> (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
> (**) Macintosh mouse button emulation: EmulateWheelButton: 4,
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "Macintosh mouse button
> emulation" (type: MOUSE)
> (**) Macintosh mouse button emulation: (accel) keeping acceleration
> scheme 1
> (**) Macintosh mouse button emulation: (accel) filter chain
> progression: 2.00
> (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
> (**) Macintosh mouse button emulation: (accel) set acceleration profile 0
> (II) config/hal: Adding input device HID 062a:0001
> (**) HID 062a:0001: always reports core events
> (**) HID 062a:0001: Device: "/dev/input/event4"
> (II) HID 062a:0001: Found 5 mouse buttons
> (II) HID 062a:0001: Found x and y relative axes
> (II) HID 062a:0001: Configuring as mouse
> (**) HID 062a:0001: YAxisMapping: buttons 4 and 5
> (**) HID 062a:0001: EmulateWheelButton: 4, EmulateWheelInertia: 10,
> EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "HID 062a:0001" (type:
MOUSE)
> (**) HID 062a:0001: (accel) keeping acceleration scheme 1
> (**) HID 062a:0001: (accel) filter chain progression: 2.00
> (**) HID 062a:0001: (accel) filter stage 0: 20.00 ms
> (**) HID 062a:0001: (accel) set acceleration profile 0
>
> Boris.
>
>

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

Boris Derzhavets

2009-Sep-23 20:25 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

>I assume you''re saying that it fails with 2.6.31-pvops dom0?  
Yes.
>How does it fail?  Is it completely non-functional?  
Yes, it is completely non-functional.
>Does the whole system crash?  
No, just in text mode.
> Or does X simply fail to start?   
No. It seems to be running. 
>Or it does start but is crippled in some way?
It starts due to logs content during system boot up ,

 like on F11, where everything is going fine.
 I attached both dmesg.log and Xorg.0.log to previous message for Ubuntu 9.04
Server.
> Does it work with 2.6.31 running without Xen?  How do the log files
compare?
I will check it tomorrow.

Boris.

--- On Wed, 9/23/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:

From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on
top of Ubuntu 9.04 Server
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, September 23, 2009, 3:27 PM

On 09/23/09 08:45, Boris Derzhavets wrote:> Video card Radeon HD 4560.  X-server starts fine under native
> 2.6.28-11-server
> ubuntu kernel. 
>I assume you''re saying that it fails with 2.6.31-pvops dom0?  How does
it fail?  Is it completely non-functional?  Does the whole system
crash?  Or does X simply fail to start?   Or it does start but is
crippled in some way?

Does it work with 2.6.31 running without Xen?  How do the log files compare?

Thanks,
    J
>
> X-Windows Setup :-
>
> Downsize the system:
> vi /etc/default/linux-restricted-modules-common:
> DISABLED_MODULES=”ath_hal fc fglrx ltm nv” Install the X11 bare bone:
>
> # aptitude install x-window-system-core
> # aptitude install fluxbox fluxconf #lightwight windows manager
> # aptitude install dillo #lightweight browser
> # aptitude install xfe #lightweight file manager
> # apttitude install synaptic # To install eset & esetroot
> Change /etc/X11/xorg.conf:
> # dpkg-reconfigure xserver-xorg #guided setup
> Edit /etc/X11/xorg.conf (use “gtf 1024 768 60″ to obtain the Modeline
> values)
>  X-server starts fine under native Ubuntu Server kernel  and fluxbox
> is completely functional.
>
> Attempt to start at Xen 3.5 Dom0 (with the most recent 2.6.31)
>
> dmesg output :-
> . . . . . .
>
> [   43.572422] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic
> 0 pin 16 triggering 1 polarity 1
> [   43.572437] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
> IRQ 16
> [   43.710523] [drm] Initialized drm 1.1.0 20060810
> [   43.758245] pci 0000:01:00.0: setting latency timer to 64
> [   43.758433] [drm] Initialized radeon 1.31.0 20080528 for
> 0000:01:00.0 on minor 0
> [   43.763134] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035133] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035198] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.061841] [drm] Setting GART location based on new memory map
> [   44.095779] [drm] Loading RV730/RV740 PFP Microcode
> [   44.095805] [drm] Loading RV730/RV740 CP Microcode
> [   44.110868] [drm] Resetting GPU
> [   44.215007] [drm] writeback test failed
> [   79.050085] [drm] Resetting GPU
> [  243.858191] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  243.858263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132051] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132115] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132181] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.157265] [drm] Setting GART location based on new memory map
> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
> [  244.205974] [drm] Resetting GPU
> [  244.310103] [drm] writeback test failed
> [  251.220092] [drm] Resetting GPU
>
> Xorg.0.log :-
>
> (II) AIGLX: Screen 0 is not DRI2 capable
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:01:00.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: drmOpenMinor returns 11
> drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
> (EE) AIGLX error: Calling driver entry point failed(EE) AIGLX:
> reverting to software rendering
> (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
> (II) RADEON(0): Setting screen physical size to 338 x 270
> (II) config/hal: Adding input device AT Translated Set 2 keyboard
> (II) LoadModule: "evdev"
> (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
> (II) Module evdev: vendor="X.Org Foundation"
>     compiled for 1.6.0, module version = 2.1.1
>     Module class: X.Org XInput Driver
>     ABI class: X.Org XInput driver, version 4.0
> (**) AT Translated Set 2 keyboard: always reports core events
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
> (II) AT Translated Set 2 keyboard: Found keys
> (II) AT Translated Set 2 keyboard: Configuring as keyboard
> (II) XINPUT: Adding extended input device "AT Translated Set 2
> keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
> (**) Option "xkb_model" "pc105"
> (**) AT Translated Set 2 keyboard: xkb_model: "pc105"
> (**) Option "xkb_layout" "us"
> (**) AT Translated Set 2 keyboard: xkb_layout: "us"
> (II) config/hal: Adding input device Macintosh mouse button emulation
> (**) Macintosh mouse button emulation: always reports core events
> (**) Macintosh mouse button emulation: Device:
"/dev/input/event2"
> (II) Macintosh mouse button emulation: Found 3 mouse buttons
> (II) Macintosh mouse button emulation: Found x and y relative axes
> (II) Macintosh mouse button emulation: Configuring as mouse
> (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
> (**) Macintosh mouse button emulation: EmulateWheelButton: 4,
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "Macintosh mouse button
> emulation" (type: MOUSE)
> (**) Macintosh mouse button emulation: (accel) keeping acceleration
> scheme 1
> (**) Macintosh mouse button emulation: (accel) filter chain
> progression: 2.00
> (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
> (**) Macintosh mouse button emulation: (accel) set acceleration profile 0
> (II) config/hal: Adding input device HID 062a:0001
> (**) HID 062a:0001: always reports core events
> (**) HID 062a:0001: Device: "/dev/input/event4"
> (II) HID 062a:0001: Found 5 mouse buttons
> (II) HID 062a:0001: Found x and y relative axes
> (II) HID 062a:0001: Configuring as mouse
> (**) HID 062a:0001: YAxisMapping: buttons 4 and 5
> (**) HID 062a:0001: EmulateWheelButton: 4, EmulateWheelInertia: 10,
> EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "HID 062a:0001" (type:
MOUSE)
> (**) HID 062a:0001: (accel) keeping acceleration scheme 1
> (**) HID 062a:0001: (accel) filter chain progression: 2.00
> (**) HID 062a:0001: (accel) filter stage 0: 20.00 ms
> (**) HID 062a:0001: (accel) set acceleration profile 0
>
> Boris.
>
>

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



      

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

Boris Derzhavets

2009-Sep-24 05:33 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

> Does it work with 2.6.31 running without Xen?  
Works fine. Logs are attached.
>How do the log files compare?
Look the same.

I was wrong regarding time of X-server startup,
in both case after login in text console.

# startx

Boris

--- On Wed, 9/23/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, September 23, 2009, 4:25 PM
>I assume you''re saying that it fails with 2.6.31-pvops dom0?  
Yes.
>How does it fail?  Is it completely non-functional?  
Yes, it is completely non-functional.
>Does the whole system crash?  
No, just in text mode.
> Or does X simply fail to start?   
No. It seems to be running. 
>Or it does start but is crippled in some way?
It starts due to logs content during system boot up ,

 like on F11, where everything is going fine.
 I attached both dmesg.log and Xorg.0.log to previous message for Ubuntu 9.04
Server.
> Does it work with 2.6.31 running without Xen?  How do the log files
compare?
I will check it tomorrow.

Boris.

--- On Wed, 9/23/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:

From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on
top of Ubuntu 9.04 Server
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, September 23, 2009, 3:27 PM

On 09/23/09 08:45, Boris Derzhavets wrote:> Video card Radeon HD 4560. 
 X-server starts fine under native> 2.6.28-11-server
> ubuntu kernel. 
>I assume you''re saying that it fails with 2.6.31-pvops dom0?  How does
it fail?  Is it completely non-functional?  Does the whole system
crash?  Or does X simply fail to start?   Or it does start but is
crippled in some way?

Does it work with 2.6.31 running without Xen?  How do the log files compare?

Thanks,
    J
>
> X-Windows Setup :-
>
> Downsize the system:
> vi /etc/default/linux-restricted-modules-common:
> DISABLED_MODULES=”ath_hal fc fglrx ltm nv” Install the X11 bare bone:
>
> # aptitude install x-window-system-core
> # aptitude install fluxbox fluxconf #lightwight windows manager
> # aptitude install dillo #lightweight browser
> # aptitude install xfe #lightweight file manager
> # apttitude install
 synaptic # To install eset & esetroot> Change /etc/X11/xorg.conf:
> # dpkg-reconfigure xserver-xorg #guided setup
> Edit /etc/X11/xorg.conf (use “gtf 1024 768 60″ to obtain the Modeline
> values)
>  X-server starts fine under native Ubuntu Server kernel  and fluxbox
> is completely functional.
>
> Attempt to start at Xen 3.5 Dom0 (with the most recent 2.6.31)
>
> dmesg output :-
> . . . . . .
>
> [   43.572422] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic
> 0 pin 16 triggering 1 polarity 1
> [   43.572437] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
> IRQ 16
> [   43.710523] [drm] Initialized drm 1.1.0 20060810
> [   43.758245] pci 0000:01:00.0: setting latency timer to 64
> [   43.758433] [drm] Initialized radeon 1.31.0
 20080528 for> 0000:01:00.0 on minor 0
> [   43.763134] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035133] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035198] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.061841] [drm] Setting GART location based on new memory map
> [   44.095779] [drm] Loading RV730/RV740 PFP Microcode
> [   44.095805] [drm] Loading RV730/RV740 CP Microcode
> [   44.110868] [drm] Resetting GPU
> [   44.215007] [drm] writeback test failed
> [   79.050085] [drm] Resetting
 GPU> [  243.858191] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  243.858263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132051] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132115] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132181] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.157265] [drm] Setting GART location based on new memory map
> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
> [  244.205974] [drm] Resetting GPU
> [  244.310103] [drm] writeback test failed
> [  251.220092] [drm] Resetting GPU
>
>
 Xorg.0.log :->
> (II) AIGLX: Screen 0 is not DRI2 capable
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:01:00.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: drmOpenMinor returns 11
> drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
> (EE) AIGLX error: Calling driver entry point failed(EE) AIGLX:
> reverting to software rendering
> (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
> (II) RADEON(0): Setting screen physical size to 338 x 270
> (II) config/hal: Adding input device AT Translated Set 2 keyboard
> (II) LoadModule: "evdev"
> (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
> (II) Module evdev: vendor="X.Org
 Foundation">     compiled for 1.6.0, module version = 2.1.1
>     Module class: X.Org XInput Driver
>     ABI class: X.Org XInput driver, version 4.0
> (**) AT Translated Set 2 keyboard: always reports core events
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
> (II) AT Translated Set 2 keyboard: Found keys
> (II) AT Translated Set 2 keyboard: Configuring as keyboard
> (II) XINPUT: Adding extended input device "AT Translated Set 2
> keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
> (**) Option "xkb_model" "pc105"
> (**) AT Translated Set 2 keyboard: xkb_model: "pc105"
> (**) Option "xkb_layout" "us"
> (**) AT Translated Set 2 keyboard: xkb_layout: "us"
> (II) config/hal: Adding input device Macintosh mouse button
 emulation> (**) Macintosh mouse button emulation: always reports core events
> (**) Macintosh mouse button emulation: Device:
"/dev/input/event2"
> (II) Macintosh mouse button emulation: Found 3 mouse buttons
> (II) Macintosh mouse button emulation: Found x and y relative axes
> (II) Macintosh mouse button emulation: Configuring as mouse
> (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
> (**) Macintosh mouse button emulation: EmulateWheelButton: 4,
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "Macintosh mouse button
> emulation" (type: MOUSE)
> (**) Macintosh mouse button emulation: (accel) keeping acceleration
> scheme 1
> (**) Macintosh mouse button emulation: (accel) filter chain
> progression: 2.00
> (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
> (**) Macintosh mouse button emulation: (accel) set acceleration profile
0> (II) config/hal: Adding input device HID 062a:0001
> (**) HID 062a:0001: always reports core events
> (**) HID 062a:0001: Device: "/dev/input/event4"
> (II) HID 062a:0001: Found 5 mouse buttons
> (II) HID 062a:0001: Found x and y relative axes
> (II) HID 062a:0001: Configuring as mouse
> (**) HID 062a:0001: YAxisMapping: buttons 4 and 5
> (**) HID 062a:0001: EmulateWheelButton: 4, EmulateWheelInertia: 10,
> EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "HID 062a:0001" (type:
MOUSE)
> (**) HID 062a:0001: (accel) keeping acceleration scheme 1
> (**) HID 062a:0001: (accel) filter chain progression: 2.00
> (**) HID 062a:0001: (accel) filter stage 0: 20.00 ms
> (**) HID 062a:0001: (accel) set acceleration profile 0
>
>
 Boris.>
>

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



      
-----Inline Attachment Follows-----

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



      



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

Boris Derzhavets

2009-Sep-24 05:54 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Sorry , there is difference in dmesg reports under xen and as vanilla.

dmesg under xen:-

[  243.858191] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  243.858263] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132051] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132115] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132181] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.157265] [drm] Setting GART location based on new memory map
[  244.190885] [drm] Loading RV730/RV740 PFP Microcode
[  244.190911] [drm] Loading RV730/RV740 CP Microcode
[  244.205974] [drm] Resetting GPU
->    [  244.310103] [drm] writeback test failed
[  251.220092] [drm] Resetting GPU

dmesg 2.6.31 vanilla:-

[   36.941430] [drm] Initialized drm 1.1.0 20060810
[   36.988225] pci 0000:01:00.0: setting latency timer to 64
[   36.988341] [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on
minor 0
[   36.989222] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   37.210900] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   37.210940] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   37.210976] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   37.232744] [drm] Setting GART location based on new memory map
[   37.248205] [drm] Loading RV730/RV740 PFP Microcode
[   37.248227] [drm] Loading RV730/RV740 CP Microcode
[   37.263281] [drm] Resetting GPU
-> [   37.263336] [drm] writeback test succeeded in 1 usecs

Boris



--- On Thu, 9/24/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Thursday, September 24, 2009, 1:33 AM
> Does it work with 2.6.31 running without Xen?  
Works fine. Logs are attached.
>How do the log files compare?
Look the same.

I was wrong regarding time of X-server startup,
in both case after login in text console.

# startx

Boris

--- On Wed, 9/23/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, September 23, 2009, 4:25
 PM
>I assume you''re saying that it fails with 2.6.31-pvops dom0?  
Yes.
>How does it fail?  Is it completely non-functional?  
Yes, it is completely non-functional.
>Does the whole system crash?  
No, just in text mode.
> Or does X simply fail to start?   
No. It seems to be running. 
>Or it does start but is crippled in some way?
It starts due to logs content during system boot up ,

 like on F11, where everything is going fine.
 I attached both dmesg.log and Xorg.0.log to previous message for Ubuntu 9.04
Server.
> Does it work with 2.6.31 running without Xen?  How do the log files
compare?
I will check it tomorrow.

Boris.

--- On Wed, 9/23/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:

From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on
top of Ubuntu 9.04 Server
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, September 23, 2009, 3:27 PM

On 09/23/09 08:45, Boris Derzhavets wrote:> Video card Radeon HD 4560. 
 X-server starts fine under native> 2.6.28-11-server
> ubuntu kernel. 
>I assume you''re saying that it fails with 2.6.31-pvops dom0?  How does
it fail?  Is it completely non-functional?  Does the whole system
crash?  Or does X simply fail to start?   Or it does start but is
crippled in some way?

Does it work with 2.6.31 running without Xen?  How do the log files compare?

Thanks,
    J
>
> X-Windows Setup :-
>
> Downsize the system:
> vi /etc/default/linux-restricted-modules-common:
> DISABLED_MODULES=”ath_hal fc fglrx ltm nv” Install the X11 bare bone:
>
> # aptitude install x-window-system-core
> # aptitude install fluxbox fluxconf #lightwight windows manager
> # aptitude install dillo #lightweight browser
> # aptitude install xfe #lightweight file manager
> # apttitude install
 synaptic # To install eset & esetroot> Change /etc/X11/xorg.conf:
> # dpkg-reconfigure xserver-xorg #guided setup
> Edit /etc/X11/xorg.conf (use “gtf 1024 768 60″ to obtain the Modeline
> values)
>  X-server starts fine under native Ubuntu Server kernel  and fluxbox
> is completely functional.
>
> Attempt to start at Xen 3.5 Dom0 (with the most recent 2.6.31)
>
> dmesg output :-
> . . . . . .
>
> [   43.572422] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic
> 0 pin 16 triggering 1 polarity 1
> [   43.572437] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
> IRQ 16
> [   43.710523] [drm] Initialized drm 1.1.0 20060810
> [   43.758245] pci 0000:01:00.0: setting latency timer to 64
> [   43.758433] [drm] Initialized radeon 1.31.0
 20080528 for> 0000:01:00.0 on minor 0
> [   43.763134] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035133] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035198] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.061841] [drm] Setting GART location based on new memory map
> [   44.095779] [drm] Loading RV730/RV740 PFP Microcode
> [   44.095805] [drm] Loading RV730/RV740 CP Microcode
> [   44.110868] [drm] Resetting GPU
> [   44.215007] [drm] writeback test failed
> [   79.050085] [drm] Resetting
 GPU> [  243.858191] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  243.858263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132051] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132115] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132181] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.157265] [drm] Setting GART location based on new memory map
> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
> [  244.205974] [drm] Resetting GPU
> [  244.310103] [drm] writeback test failed
> [  251.220092] [drm] Resetting GPU
>
>
 Xorg.0.log :->
> (II) AIGLX: Screen 0 is not DRI2 capable
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:01:00.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: drmOpenMinor returns 11
> drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
> (EE) AIGLX error: Calling driver entry point failed(EE) AIGLX:
> reverting to software rendering
> (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
> (II) RADEON(0): Setting screen physical size to 338 x 270
> (II) config/hal: Adding input device AT Translated Set 2 keyboard
> (II) LoadModule: "evdev"
> (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
> (II) Module evdev: vendor="X.Org
 Foundation">     compiled for 1.6.0, module version = 2.1.1
>     Module class: X.Org XInput Driver
>     ABI class: X.Org XInput driver, version 4.0
> (**) AT Translated Set 2 keyboard: always reports core events
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
> (II) AT Translated Set 2 keyboard: Found keys
> (II) AT Translated Set 2 keyboard: Configuring as keyboard
> (II) XINPUT: Adding extended input device "AT Translated Set 2
> keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
> (**) Option "xkb_model" "pc105"
> (**) AT Translated Set 2 keyboard: xkb_model: "pc105"
> (**) Option "xkb_layout" "us"
> (**) AT Translated Set 2 keyboard: xkb_layout: "us"
> (II) config/hal: Adding input device Macintosh mouse button
 emulation> (**) Macintosh mouse button emulation: always reports core events
> (**) Macintosh mouse button emulation: Device:
"/dev/input/event2"
> (II) Macintosh mouse button emulation: Found 3 mouse buttons
> (II) Macintosh mouse button emulation: Found x and y relative axes
> (II) Macintosh mouse button emulation: Configuring as mouse
> (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
> (**) Macintosh mouse button emulation: EmulateWheelButton: 4,
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "Macintosh mouse button
> emulation" (type: MOUSE)
> (**) Macintosh mouse button emulation: (accel) keeping acceleration
> scheme 1
> (**) Macintosh mouse button emulation: (accel) filter chain
> progression: 2.00
> (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
> (**) Macintosh mouse button emulation: (accel) set acceleration profile
0> (II) config/hal: Adding input device HID 062a:0001
> (**) HID 062a:0001: always reports core events
> (**) HID 062a:0001: Device: "/dev/input/event4"
> (II) HID 062a:0001: Found 5 mouse buttons
> (II) HID 062a:0001: Found x and y relative axes
> (II) HID 062a:0001: Configuring as mouse
> (**) HID 062a:0001: YAxisMapping: buttons 4 and 5
> (**) HID 062a:0001: EmulateWheelButton: 4, EmulateWheelInertia: 10,
> EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "HID 062a:0001" (type:
MOUSE)
> (**) HID 062a:0001: (accel) keeping acceleration scheme 1
> (**) HID 062a:0001: (accel) filter chain progression: 2.00
> (**) HID 062a:0001: (accel) filter stage 0: 20.00 ms
> (**) HID 062a:0001: (accel) set acceleration profile 0
>
>
 Boris.>
>

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



      
-----Inline Attachment Follows-----

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



      
-----Inline Attachment Follows-----

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



      

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

Boris Derzhavets

2009-Sep-24 16:40 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

To get X-server working on Ubuntu 9.04 Server (Radeon HD 4650 plugged in) I just
disabled DRM :-

-*- /dev/agpgart (AGP Support)  --->                                       x
x 
 < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) 
--->                 x x 
<M> Lowlevel video output switch
controls                                    x x 
 <*> Support for frame buffer devices 
--->                                    x x 
  -*- Backlight & LCD device support  ---->                  
                   x x 
  Display device support  --->                                               
          x x 
  Console display driver support 
--->                                             x x 

and rebuilt 2.6.31 kernel.

I also have to mention, that  kernel modeset Radeon initializing at Xen 3.4.1
Dom0 ( 2.6.31) shows failure  to load radeon_kms driver ( per dmesg report ) as
well.  But, by some reasons X-Server on F11 ignore this issue and comes up.
   
   If dmesg report (drm errors to initialize kernel modeset for Radeon) on F11
is  wanted, i will post it.

Boris.

9/24/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Thursday, September 24, 2009, 1:54 AM

Sorry , there is difference in dmesg reports under xen and as vanilla.

dmesg under xen:-

[  243.858191] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  243.858263] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132051] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132115] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.132181] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[  244.157265] [drm] Setting GART location based on new memory map
[  244.190885] [drm] Loading RV730/RV740 PFP Microcode
[  244.190911] [drm] Loading RV730/RV740 CP Microcode
[  244.205974] [drm] Resetting
 GPU
->    [  244.310103] [drm] writeback test failed
[  251.220092] [drm] Resetting GPU

dmesg 2.6.31 vanilla:-

[   36.941430] [drm] Initialized drm 1.1.0 20060810
[   36.988225] pci 0000:01:00.0: setting latency timer to 64
[   36.988341] [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on
minor 0
[   36.989222] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   37.210900] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   37.210940] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   37.210976] mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[   37.232744] [drm] Setting GART location based on new memory map
[   37.248205] [drm] Loading RV730/RV740 PFP
 Microcode
[   37.248227] [drm] Loading RV730/RV740 CP Microcode
[   37.263281] [drm] Resetting GPU
-> [   37.263336] [drm] writeback test succeeded in 1 usecs

Boris



--- On Thu, 9/24/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Thursday, September 24, 2009, 1:33 AM
> Does it work with 2.6.31 running without Xen?  
Works fine. Logs are attached.
>How do the log files compare?
Look the same.

I was wrong regarding time of X-server startup,
in both case after login in text console.

# startx

Boris

--- On Wed, 9/23/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk"
 <konrad.wilk@oracle.com>
Date: Wednesday, September 23, 2009, 4:25
 PM
>I assume you''re saying that it fails with 2.6.31-pvops dom0?  
Yes.
>How does it fail?  Is it completely non-functional?  
Yes, it is completely non-functional.
>Does the whole system crash?  
No, just in text mode.
> Or does X simply fail to start?   
No. It seems to be running. 
>Or it does start but is crippled in some way?
It starts due to logs content during system boot up ,

 like on F11, where everything is going fine.
 I attached both dmesg.log and Xorg.0.log to previous message for Ubuntu 9.04
Server.
> Does it work with 2.6.31 running without Xen?  How do the log files
compare?
I will check it tomorrow.

Boris.

--- On Wed, 9/23/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:

From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on
top of Ubuntu 9.04 Server
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, September 23, 2009, 3:27 PM

On 09/23/09 08:45, Boris Derzhavets wrote:> Video card Radeon HD 4560. 
 X-server starts fine under native> 2.6.28-11-server
> ubuntu kernel. 
>I assume you''re saying that it fails with 2.6.31-pvops dom0?  How does
it fail?  Is it completely non-functional?  Does the whole system
crash?  Or does X simply fail to start?   Or it does start but is
crippled in some way?

Does it work with 2.6.31 running without Xen?  How do the log files compare?

Thanks,
    J
>
> X-Windows Setup :-
>
> Downsize the system:
> vi /etc/default/linux-restricted-modules-common:
> DISABLED_MODULES=”ath_hal fc fglrx ltm nv” Install the X11 bare bone:
>
> # aptitude install x-window-system-core
> # aptitude install fluxbox fluxconf #lightwight windows manager
> # aptitude install dillo #lightweight browser
> # aptitude install xfe #lightweight file manager
> # apttitude install
 synaptic # To install eset & esetroot> Change /etc/X11/xorg.conf:
> # dpkg-reconfigure xserver-xorg #guided setup
> Edit /etc/X11/xorg.conf (use “gtf 1024 768 60″ to obtain the Modeline
> values)
>  X-server starts fine under native Ubuntu Server kernel  and fluxbox
> is completely functional.
>
> Attempt to start at Xen 3.5 Dom0 (with the most recent 2.6.31)
>
> dmesg output :-
> . . . . . .
>
> [   43.572422] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic
> 0 pin 16 triggering 1 polarity 1
> [   43.572437] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
> IRQ 16
> [   43.710523] [drm] Initialized drm 1.1.0 20060810
> [   43.758245] pci 0000:01:00.0: setting latency timer to 64
> [   43.758433] [drm] Initialized radeon 1.31.0
 20080528 for> 0000:01:00.0 on minor 0
> [   43.763134] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035133] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035198] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.061841] [drm] Setting GART location based on new memory map
> [   44.095779] [drm] Loading RV730/RV740 PFP Microcode
> [   44.095805] [drm] Loading RV730/RV740 CP Microcode
> [   44.110868] [drm] Resetting GPU
> [   44.215007] [drm] writeback test failed
> [   79.050085] [drm] Resetting
 GPU> [  243.858191] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  243.858263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132051] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132115] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132181] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.157265] [drm] Setting GART location based on new memory map
> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
> [  244.205974] [drm] Resetting GPU
> [  244.310103] [drm] writeback test failed
> [  251.220092] [drm] Resetting GPU
>
>
 Xorg.0.log :->
> (II) AIGLX: Screen 0 is not DRI2 capable
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:01:00.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: drmOpenMinor returns 11
> drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
> (EE) AIGLX error: Calling driver entry point failed(EE) AIGLX:
> reverting to software rendering
> (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
> (II) RADEON(0): Setting screen physical size to 338 x 270
> (II) config/hal: Adding input device AT Translated Set 2 keyboard
> (II) LoadModule: "evdev"
> (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
> (II) Module evdev: vendor="X.Org
 Foundation">     compiled for 1.6.0, module version = 2.1.1
>     Module class: X.Org XInput Driver
>     ABI class: X.Org XInput driver, version 4.0
> (**) AT Translated Set 2 keyboard: always reports core events
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
> (II) AT Translated Set 2 keyboard: Found keys
> (II) AT Translated Set 2 keyboard: Configuring as keyboard
> (II) XINPUT: Adding extended input device "AT Translated Set 2
> keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
> (**) Option "xkb_model" "pc105"
> (**) AT Translated Set 2 keyboard: xkb_model: "pc105"
> (**) Option "xkb_layout" "us"
> (**) AT Translated Set 2 keyboard: xkb_layout: "us"
> (II) config/hal: Adding input device Macintosh mouse button
 emulation> (**) Macintosh mouse button emulation: always reports core events
> (**) Macintosh mouse button emulation: Device:
"/dev/input/event2"
> (II) Macintosh mouse button emulation: Found 3 mouse buttons
> (II) Macintosh mouse button emulation: Found x and y relative axes
> (II) Macintosh mouse button emulation: Configuring as mouse
> (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
> (**) Macintosh mouse button emulation: EmulateWheelButton: 4,
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "Macintosh mouse button
> emulation" (type: MOUSE)
> (**) Macintosh mouse button emulation: (accel) keeping acceleration
> scheme 1
> (**) Macintosh mouse button emulation: (accel) filter chain
> progression: 2.00
> (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
> (**) Macintosh mouse button emulation: (accel) set acceleration profile
0> (II) config/hal: Adding input device HID 062a:0001
> (**) HID 062a:0001: always reports core events
> (**) HID 062a:0001: Device: "/dev/input/event4"
> (II) HID 062a:0001: Found 5 mouse buttons
> (II) HID 062a:0001: Found x and y relative axes
> (II) HID 062a:0001: Configuring as mouse
> (**) HID 062a:0001: YAxisMapping: buttons 4 and 5
> (**) HID 062a:0001: EmulateWheelButton: 4, EmulateWheelInertia: 10,
> EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "HID 062a:0001" (type:
MOUSE)
> (**) HID 062a:0001: (accel) keeping acceleration scheme 1
> (**) HID 062a:0001: (accel) filter chain progression: 2.00
> (**) HID 062a:0001: (accel) filter stage 0: 20.00 ms
> (**) HID 062a:0001: (accel) set acceleration profile 0
>
>
 Boris.>
>

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



      
-----Inline Attachment Follows-----

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



      
-----Inline Attachment Follows-----

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



      
-----Inline Attachment Follows-----

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



      


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

Konrad Rzeszutek Wilk

2009-Sep-24 16:48 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

On Wed, Sep 23, 2009 at 10:54:09PM -0700, Boris Derzhavets
wrote:> Sorry , there is difference in dmesg reports under xen and as vanilla.
> 
> dmesg under xen:-
> 
> [  243.858191] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  243.858263] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  244.132051] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  244.132115] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  244.132181] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  244.157265] [drm] Setting GART location based on new memory map
> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
> [  244.205974] [drm] Resetting GPU
> ->    [  244.310103] [drm] writeback test failed
> [  251.220092] [drm] Resetting GPU
> 
> dmesg 2.6.31 vanilla:-
> 
> [   36.941430] [drm] Initialized drm 1.1.0 20060810
> [   36.988225] pci 0000:01:00.0: setting latency timer to 64
> [   36.988341] [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on
minor 0
> [   36.989222] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [   37.210900] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [   37.210940] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [   37.210976] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [   37.232744] [drm] Setting GART location based on new memory map
> [   37.248205] [drm] Loading RV730/RV740 PFP Microcode
> [   37.248227] [drm] Loading RV730/RV740 CP Microcode
> [   37.263281] [drm] Resetting GPU
> -> [   37.263336] [drm] writeback test succeeded in 1 usecs
I think I know why this is not working.

The DRM and its AGP modules call virt_to_gart and gart_to_virt, which is defined
as:

#define virt_to_gart(x) (phys_to_gart(virt_to_phys(x)))
#define gart_to_virt(x) (phys_to_virt(gart_to_phys(x)))
and phys_to_gart and gart_to_phys are:
#define phys_to_gart(x) swiotlb_phys_to_bus(NULL, (x))
#define gart_to_phys(x) swiotlb_bus_to_phys(NULL, (x))

The swiotlb_* calls do return the wrong information when the
kernel is running under Xen.

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

Boris Derzhavets

2009-Sep-24 17:17 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

It happens at Xen 3.4.1 Dom0 (the most recent  2.6.31) 
on top F11 and at Xen 3.5 Dom0  (2.6.31commit
398b4b4cabdb27c06a7b8214c2044347ffc08c49 )
on top Ubuntu 9.04 Server.
However , X-Server starts at Dom0 on top of F11 and requires DRM get disabled in
2.6.31 pvops kernel in Xen 3.5 Dom0 on top of Ubuntu 9.04 Server for successful
startup. It''s Xorg 1.6 version in both cases.

Boris.


--- On Thu, 9/24/09, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:

From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>,
"Xen-devel" <xen-devel@lists.xensource.com>
Date: Thursday, September 24, 2009, 12:48 PM

On Wed, Sep 23, 2009 at 10:54:09PM -0700, Boris Derzhavets
wrote:> Sorry , there is difference in dmesg reports under xen and as vanilla.
> 
> dmesg under xen:-
> 
> [  243.858191] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  243.858263] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  244.132051] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  244.132115] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  244.132181] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [  244.157265] [drm] Setting GART location based on new memory map
> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
> [  244.205974] [drm] Resetting GPU
> ->    [  244.310103] [drm] writeback test failed
> [  251.220092] [drm] Resetting GPU
> 
> dmesg 2.6.31 vanilla:-
> 
> [   36.941430] [drm] Initialized drm 1.1.0 20060810
> [   36.988225] pci 0000:01:00.0: setting latency timer to 64
> [   36.988341] [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on
minor 0
> [   36.989222] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [   37.210900] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [   37.210940] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [   37.210976] mtrr: type mismatch for d0000000,10000000 old: write-back
new: write-combining
> [   37.232744] [drm] Setting GART location based on new memory map
> [   37.248205] [drm] Loading RV730/RV740 PFP Microcode
> [   37.248227] [drm] Loading RV730/RV740 CP Microcode
> [   37.263281] [drm] Resetting GPU
> -> [   37.263336] [drm] writeback test succeeded in 1 usecs
I think I know why this is not working.

The DRM and its AGP modules call virt_to_gart and gart_to_virt, which is defined
as:

#define virt_to_gart(x) (phys_to_gart(virt_to_phys(x)))
#define gart_to_virt(x) (phys_to_virt(gart_to_phys(x)))
and phys_to_gart and gart_to_phys are:
#define phys_to_gart(x) swiotlb_phys_to_bus(NULL, (x))
#define gart_to_phys(x) swiotlb_bus_to_phys(NULL, (x))

The swiotlb_* calls do return the wrong information when the
kernel is running under Xen.

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



      

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

Jeremy Fitzhardinge

2009-Sep-24 17:52 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

On 09/24/09 09:48, Konrad Rzeszutek Wilk wrote:> On Wed, Sep 23, 2009 at 10:54:09PM -0700, Boris Derzhavets wrote:
>   
>> Sorry , there is difference in dmesg reports under xen and as vanilla.
>>
>> dmesg under xen:-
>>
>> [  243.858191] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [  243.858263] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [  244.132051] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [  244.132115] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [  244.132181] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [  244.157265] [drm] Setting GART location based on new memory map
>> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
>> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
>> [  244.205974] [drm] Resetting GPU
>> ->    [  244.310103] [drm] writeback test failed
>> [  251.220092] [drm] Resetting GPU
>>
>> dmesg 2.6.31 vanilla:-
>>
>> [   36.941430] [drm] Initialized drm 1.1.0 20060810
>> [   36.988225] pci 0000:01:00.0: setting latency timer to 64
>> [   36.988341] [drm] Initialized radeon 1.31.0 20080528 for
0000:01:00.0 on minor 0
>> [   36.989222] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [   37.210900] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [   37.210940] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [   37.210976] mtrr: type mismatch for d0000000,10000000 old:
write-back new: write-combining
>> [   37.232744] [drm] Setting GART location based on new memory map
>> [   37.248205] [drm] Loading RV730/RV740 PFP Microcode
>> [   37.248227] [drm] Loading RV730/RV740 CP Microcode
>> [   37.263281] [drm] Resetting GPU
>> -> [   37.263336] [drm] writeback test succeeded in 1 usecs
>>     
> I think I know why this is not working.
>
> The DRM and its AGP modules call virt_to_gart and gart_to_virt, which is
defined as:
>
> #define virt_to_gart(x) (phys_to_gart(virt_to_phys(x)))
> #define gart_to_virt(x) (phys_to_virt(gart_to_phys(x)))
> and phys_to_gart and gart_to_phys are:
> #define phys_to_gart(x) swiotlb_phys_to_bus(NULL, (x))
> #define gart_to_phys(x) swiotlb_bus_to_phys(NULL, (x))
>
> The swiotlb_* calls do return the wrong information when the
> kernel is running under Xen.
>   
Ah, yes.  They used to be the right thing to call.  I guess we can put
in something hacky to get things going for now: (xen_pv_domain() ?
xen_swiotlb_bus_to_phys(NULL, (x) : (x)).

But it might be time to bite the bullet:

In this current merge window these functions are removed altogether, in
favour of making the dri drivers use the dma-mapping api properly to do
all those conversions.  AFAIK the only driver so converted is the Intel
graphics one, and then only when the Intel IOMMU is configured in. 
However, in discussions with the the dri folks I had no objection to
making it unconditional and adding the changes to other drivers (so long
as we can test them, since normal hardware configs won''t generally have
any IOMMU for typical gfx hardware).

    J

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

Jeremy Fitzhardinge

2009-Sep-24 19:37 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

On 09/24/09 10:17, Boris Derzhavets wrote:> It happens at Xen 3.4.1 Dom0 (the most recent  2.6.31)
> on top F11 and at Xen 3.5 Dom0  (2.6.31commit
> 398b4b4cabdb27c06a7b8214c2044347ffc08c49 )
> on top Ubuntu 9.04 Server.
> However , X-Server starts at Dom0 on top of F11 and requires DRM get
> disabled in 2.6.31 pvops kernel in Xen 3.5 Dom0 on top of Ubuntu 9.04
> Server for successful startup. It''s Xorg 1.6 version in both
cases.
>
I just committed a change to make the AGP phys<->bus conversions do the
right thing.

    J

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

Boris Derzhavets

2009-Sep-24 19:59 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Kernel been rebuilt with DRM support now works fine at Xen 3.5 Dom0 on top of
Ubuntu 9.04 Server. X-sever starts with no problems

Thanks
Boris.

--- On Thu, 9/24/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:

From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Thursday, September 24, 2009, 3:37 PM

On 09/24/09 10:17, Boris Derzhavets wrote:> It happens at Xen 3.4.1 Dom0 (the most recent  2.6.31)
> on top F11 and at Xen 3.5 Dom0  (2.6.31commit
> 398b4b4cabdb27c06a7b8214c2044347ffc08c49 )
> on top Ubuntu 9.04 Server.
> However , X-Server starts at Dom0 on top of F11 and requires DRM get
> disabled in 2.6.31 pvops kernel in Xen 3.5 Dom0 on top of Ubuntu 9.04
> Server for successful startup. It''s Xorg 1.6 version in both
cases.
>
I just committed a change to make the AGP phys<->bus conversions do the
right thing.

    J

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



      


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

Bruce Edge

2009-Sep-24 21:02 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Boris,
What did you use for the Xen 3.5 installation on Ubuntu? Is there a ppa
source package available?

Thanks

-Bruce

On Thu, Sep 24, 2009 at 12:59 PM, Boris Derzhavets
<bderzhavets@yahoo.com>wrote:
> Kernel been rebuilt with DRM support now works fine at Xen 3.5 Dom0 on top
> of Ubuntu 9.04 Server. X-sever starts with no problems
>
> Thanks
> Boris.
>
> --- On *Thu, 9/24/09, Jeremy Fitzhardinge <jeremy@goop.org>* wrote:
>
>
> From: Jeremy Fitzhardinge <jeremy@goop.org>
> Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 (
> 2.6.31) on top of Ubuntu 9.04 Server
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Xen-devel" <xen-devel@lists.xensource.com>,
"Konrad Rzeszutek Wilk" <
> konrad.wilk@oracle.com>
> Date: Thursday, September 24, 2009, 3:37 PM
>
>
> On 09/24/09 10:17, Boris Derzhavets wrote:
> > It happens at Xen 3.4.1 Dom0 (the most recent  2.6.31)
> > on top F11 and at Xen 3.5 Dom0  (2.6.31commit
> > 398b4b4cabdb27c06a7b8214c2044347ffc08c49 )
> > on top Ubuntu 9.04 Server.
> > However , X-Server starts at Dom0 on top of F11 and requires DRM get
> > disabled in 2.6.31 pvops kernel in Xen 3.5 Dom0 on top of Ubuntu 9.04
> > Server for successful startup. It''s Xorg 1.6 version in both
cases.
> >
>
> I just committed a change to make the AGP phys<->bus conversions do
the
> right thing.
>
>     J
>
> _______________________________________________
> Xen-devel mailing list
>
Xen-devel@lists.xensource.com<http://mc/compose?to=Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>

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

Boris Derzhavets

2009-Sep-25 05:18 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Just do the same for xen-unstable.hg :-

http://bderzhavets.wordpress.com/2009/06/25/setup-xen-3-4-1-dom0-on-top-of-ubuntu-9-04-server-via-marc-a-dahlhauss-udev-patch/

Details :-

# cd /usr/src

# hg clone http://xenbits.xensource.com/xen-unstable.hg

# cd xen-unstable.hg

Set in Config.mk

PYTHON = python

PYTHON_PREFIX_ARG 

Tuning Config.mk results Xen packages to be placed into
/usr/local/lib/python2.6/dist-packages due to Changeset 19594 in
xen-3.4-testing.hg. Otherwise, Xen packages would go to
/usr/lib/python2.6/site-packages, which is not default location for
python 2.6 on Ubuntu 9.04 ( vs F11 ). Thus you won’t be able to start
xend in Dom0. Same thing happens when building Xen Unstable on Ubuntu
9.04 Server.


Actually, you don''t need any PPA to make direct build Xen on Ubuntu
9.04 Server ( or 9.10). All what is required is tuning Config.mk per CS 19594.

Boris.




--- On Thu, 9/24/09, Bruce Edge <bruce.edge@gmail.com> wrote:

From: Bruce Edge <bruce.edge@gmail.com>
Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 
2.6.31) on top of Ubuntu 9.04 Server
To: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Thursday, September 24, 2009, 5:02 PM

Boris,
What did you use for the Xen 3.5 installation on Ubuntu? Is there a ppa source
package available?

Thanks

-Bruce

On Thu, Sep 24, 2009 at 12:59 PM, Boris Derzhavets <bderzhavets@yahoo.com>
wrote:


Kernel been rebuilt with DRM support now works fine at Xen 3.5 Dom0 on top of
Ubuntu 9.04 Server. X-sever starts with no problems

Thanks
Boris.

--- On Thu, 9/24/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote:

From: Jeremy Fitzhardinge <jeremy@goop.org>

Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31)
on top of Ubuntu 9.04 Server
To: "Boris Derzhavets" <bderzhavets@yahoo.com>

Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Konrad
Rzeszutek Wilk" <konrad.wilk@oracle.com>

Date: Thursday, September 24, 2009, 3:37 PM

On 09/24/09 10:17, Boris Derzhavets wrote:> It happens at Xen 3.4.1 Dom0 (the most recent 
 2.6.31)> on top F11 and at Xen 3.5 Dom0  (2.6.31commit
> 398b4b4cabdb27c06a7b8214c2044347ffc08c49 )
> on top Ubuntu 9.04 Server.
> However , X-Server starts at Dom0 on top of F11 and requires DRM get
> disabled in 2.6.31 pvops kernel in Xen 3.5 Dom0 on top of Ubuntu 9.04
> Server for successful startup. It''s Xorg 1.6 version in both
cases.
>
I just committed a change to make the AGP phys<->bus conversions do the

right thing.

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com

http://lists.xensource.com/xen-devel



      
_______________________________________________

Xen-devel mailing list

Xen-devel@lists.xensource.com

http://lists.xensource.com/xen-devel



-----Inline Attachment Follows-----

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



      

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

Bruce Edge

2009-Sep-25 05:26 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

It''d be nice to get a package set built from this. Maybe I''ll
try using
prevu and port the debian patch from the 3.4.1 ppa package to xen unstable.
That would make it a lot more convenient to deploy on multiple machines.

-Bruce

On Thu, Sep 24, 2009 at 10:18 PM, Boris Derzhavets
<bderzhavets@yahoo.com>wrote:
> Just do the same for xen-unstable.hg :-
>
>
>
http://bderzhavets.wordpress.com/2009/06/25/setup-xen-3-4-1-dom0-on-top-of-ubuntu-9-04-server-via-marc-a-dahlhauss-udev-patch/
>
> Details :-
>
> # cd /usr/src
> # hg clone http://xenbits.xensource.com/xen-unstable.hg
> # cd xen-unstable.hg
> Set in Config.mk
> PYTHON = python
> PYTHON_PREFIX_ARG >
> Tuning Config.mk results Xen packages to be placed into
> /usr/local/lib/python2.6/dist-packages due to Changeset 19594 in
> xen-3.4-testing.hg. Otherwise, Xen packages would go to
> /usr/lib/python2.6/site-packages, which is not default location for python
> 2.6 on Ubuntu 9.04 ( vs F11 ). Thus you won’t be able to start xend in
Dom0.
> Same thing happens when building Xen Unstable on Ubuntu 9.04 Server.
>
>
> Actually, you don''t need any PPA to make direct build Xen on
Ubuntu 9.04
> Server ( or 9.10). All what is required is tuning Config.mk per CS 19594.
>
> Boris.
>
>
>
>
> --- On *Thu, 9/24/09, Bruce Edge <bruce.edge@gmail.com>* wrote:
>
>
> From: Bruce Edge <bruce.edge@gmail.com>
> Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 (
> 2.6.31) on top of Ubuntu 9.04 Server
> To: "Xen-devel" <xen-devel@lists.xensource.com>
> Date: Thursday, September 24, 2009, 5:02 PM
>
>
> Boris,
> What did you use for the Xen 3.5 installation on Ubuntu? Is there a ppa
> source package available?
>
> Thanks
>
> -Bruce
>
> On Thu, Sep 24, 2009 at 12:59 PM, Boris Derzhavets
<bderzhavets@yahoo.com<http://mc/compose?to=bderzhavets@yahoo.com>
> > wrote:
>
>> Kernel been rebuilt with DRM support now works fine at Xen 3.5 Dom0 on
top
>> of Ubuntu 9.04 Server. X-sever starts with no problems
>>
>> Thanks
>> Boris.
>>
>> --- On *Thu, 9/24/09, Jeremy Fitzhardinge
<jeremy@goop.org<http://mc/compose?to=jeremy@goop.org>
>> >* wrote:
>>
>>
>> From: Jeremy Fitzhardinge
<jeremy@goop.org<http://mc/compose?to=jeremy@goop.org>
>> >
>> Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0
(
>> 2.6.31) on top of Ubuntu 9.04 Server
>> To: "Boris Derzhavets"
<bderzhavets@yahoo.com<http://mc/compose?to=bderzhavets@yahoo.com>
>> >
>> Cc: "Xen-devel"
<xen-devel@lists.xensource.com<http://mc/compose?to=xen-devel@lists.xensource.com>>,
>> "Konrad Rzeszutek Wilk"
<konrad.wilk@oracle.com<http://mc/compose?to=konrad.wilk@oracle.com>
>> >
>> Date: Thursday, September 24, 2009, 3:37 PM
>>
>>
>> On 09/24/09 10:17, Boris Derzhavets wrote:
>> > It happens at Xen 3.4.1 Dom0 (the most recent  2.6.31)
>> > on top F11 and at Xen 3.5 Dom0  (2.6.31commit
>> > 398b4b4cabdb27c06a7b8214c2044347ffc08c49 )
>> > on top Ubuntu 9.04 Server.
>> > However , X-Server starts at Dom0 on top of F11 and requires DRM
get
>> > disabled in 2.6.31 pvops kernel in Xen 3.5 Dom0 on top of Ubuntu
9.04
>> > Server for successful startup. It''s Xorg 1.6 version in
both cases.
>> >
>>
>> I just committed a change to make the AGP phys<->bus conversions
do the
>> right thing.
>>
>>     J
>>
>> _______________________________________________
>> Xen-devel mailing list
>>
Xen-devel@lists.xensource.com<http://mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>>
Xen-devel@lists.xensource.com<http://mc/compose?to=Xen-devel@lists.xensource.com>
>> http://lists.xensource.com/xen-devel
>>
>>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Xen-devel mailing list
>
Xen-devel@lists.xensource.com<http://mc/compose?to=Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
>
>

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

Pasi Kärkkäinen

2009-Sep-25 08:18 UTC

head link

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

On Thu, Sep 24, 2009 at 10:26:32PM -0700, Bruce Edge
wrote:> It''d be nice to get a package set built from this. Maybe
I''ll try using
> prevu and port the debian patch from the 3.4.1 ppa package to xen unstable.
> That would make it a lot more convenient to deploy on multiple machines.
> 
Just remember the latest Debian xen packages are broken; they have HVM
disabled because the maintainer didn''t like how Qemu was packaged..

-- Pasi
> -Bruce
> 
> On Thu, Sep 24, 2009 at 10:18 PM, Boris Derzhavets
<bderzhavets@yahoo.com>wrote:
> 
> > Just do the same for xen-unstable.hg :-
> >
> >
> >
http://bderzhavets.wordpress.com/2009/06/25/setup-xen-3-4-1-dom0-on-top-of-ubuntu-9-04-server-via-marc-a-dahlhauss-udev-patch/
> >
> > Details :-
> >
> > # cd /usr/src
> > # hg clone http://xenbits.xensource.com/xen-unstable.hg
> > # cd xen-unstable.hg
> > Set in Config.mk
> > PYTHON = python
> > PYTHON_PREFIX_ARG > >
> > Tuning Config.mk results Xen packages to be placed into
> > /usr/local/lib/python2.6/dist-packages due to Changeset 19594 in
> > xen-3.4-testing.hg. Otherwise, Xen packages would go to
> > /usr/lib/python2.6/site-packages, which is not default location for
python
> > 2.6 on Ubuntu 9.04 ( vs F11 ). Thus you won?t be able to start xend in
Dom0.
> > Same thing happens when building Xen Unstable on Ubuntu 9.04 Server.
> >
> >
> > Actually, you don''t need any PPA to make direct build Xen on
Ubuntu 9.04
> > Server ( or 9.10). All what is required is tuning Config.mk per CS
19594.
> >
> > Boris.
> >
> >
> >
> >
> > --- On *Thu, 9/24/09, Bruce Edge <bruce.edge@gmail.com>* wrote:
> >
> >
> > From: Bruce Edge <bruce.edge@gmail.com>
> > Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0
(
> > 2.6.31) on top of Ubuntu 9.04 Server
> > To: "Xen-devel" <xen-devel@lists.xensource.com>
> > Date: Thursday, September 24, 2009, 5:02 PM
> >
> >
> > Boris,
> > What did you use for the Xen 3.5 installation on Ubuntu? Is there a
ppa
> > source package available?
> >
> > Thanks
> >
> > -Bruce
> >
> > On Thu, Sep 24, 2009 at 12:59 PM, Boris Derzhavets
<bderzhavets@yahoo.com<http://mc/compose?to=bderzhavets@yahoo.com>
> > > wrote:
> >
> >> Kernel been rebuilt with DRM support now works fine at Xen 3.5
Dom0 on top
> >> of Ubuntu 9.04 Server. X-sever starts with no problems
> >>
> >> Thanks
> >> Boris.
> >>
> >> --- On *Thu, 9/24/09, Jeremy Fitzhardinge
<jeremy@goop.org<http://mc/compose?to=jeremy@goop.org>
> >> >* wrote:
> >>
> >>
> >> From: Jeremy Fitzhardinge
<jeremy@goop.org<http://mc/compose?to=jeremy@goop.org>
> >> >
> >> Subject: Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5
Dom0 (
> >> 2.6.31) on top of Ubuntu 9.04 Server
> >> To: "Boris Derzhavets"
<bderzhavets@yahoo.com<http://mc/compose?to=bderzhavets@yahoo.com>
> >> >
> >> Cc: "Xen-devel"
<xen-devel@lists.xensource.com<http://mc/compose?to=xen-devel@lists.xensource.com>>,
> >> "Konrad Rzeszutek Wilk"
<konrad.wilk@oracle.com<http://mc/compose?to=konrad.wilk@oracle.com>
> >> >
> >> Date: Thursday, September 24, 2009, 3:37 PM
> >>
> >>
> >> On 09/24/09 10:17, Boris Derzhavets wrote:
> >> > It happens at Xen 3.4.1 Dom0 (the most recent  2.6.31)
> >> > on top F11 and at Xen 3.5 Dom0  (2.6.31commit
> >> > 398b4b4cabdb27c06a7b8214c2044347ffc08c49 )
> >> > on top Ubuntu 9.04 Server.
> >> > However , X-Server starts at Dom0 on top of F11 and requires
DRM get
> >> > disabled in 2.6.31 pvops kernel in Xen 3.5 Dom0 on top of
Ubuntu 9.04
> >> > Server for successful startup. It''s Xorg 1.6 version
in both cases.
> >> >
> >>
> >> I just committed a change to make the AGP phys<->bus
conversions do the
> >> right thing.
> >>
> >>     J
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >>
Xen-devel@lists.xensource.com<http://mc/compose?to=Xen-devel@lists.xensource.com>
> >> http://lists.xensource.com/xen-devel
> >>
> >>
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >>
Xen-devel@lists.xensource.com<http://mc/compose?to=Xen-devel@lists.xensource.com>
> >> http://lists.xensource.com/xen-devel
> >>
> >>
> >
> > -----Inline Attachment Follows-----
> >
> > _______________________________________________
> > Xen-devel mailing list
> >
Xen-devel@lists.xensource.com<http://mc/compose?to=Xen-devel@lists.xensource.com>
> > http://lists.xensource.com/xen-devel
> >
> >
> >
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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

Xen devel - Sep 2009 - Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

[Xen-devel] Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

[Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server