[Fedora-xen] Dom0 kernels Xen Host connected via remote VNC Session

[Pasi Kärkkäinen]

On Sat, Jan 02, 2010 at 12:51:13AM -0800, Boris Derzhavets wrote:
>    > Does it work with "nomodeset" btw?
> 
>    Jeremy's kernel works either ways.
>    It just reports error and disable ksm.
>    Michael's kernel starts loading with "nomodeset" option.
>

Michael's kernel rpms are based on Fedora kernel rpms, so they contain
various drm/graphics related patches that are not yet upstream.

That could be the reason.

-- Pasi

>    Boris.
> 
>    --------------------------------------------------------------------------
> 
>    From: Pasi Kärkkäinen <pasik at iki.fi>
>    To: Boris Derzhavets <bderzhavets at yahoo.com>
>    Cc: fedora-xen at redhat.com; M A Young <m.a.young at durham.ac.uk>
>    Sent: Sat, January 2, 2010 3:19:43 AM
>    Subject: Re: [Fedora-xen] Dom0 kernels Xen Host connected via remote VNC
>    Session
>    On Fri, Jan 01, 2010 at 10:51:16AM -0800, Boris Derzhavets wrote:
>    >    I've just applied suggested patch to the most recent clone of
>    Jeremy's tree
>    >    and rebuilt
>    >    the JF's 2.6.31.6 kernel. Same error :-
>    >
>    >    [drm] Initialized drm 1.1.0 20060810
>    >    [drm] radeon default to kernel modesetting.
>    >    [drm] radeon kernel modesetting enabled.
>    >    xen: registering gsi 16 triggering 0 polarity 1
>    >    xen_allocate_pirq: returning irq 16 for gsi 16
>    >    xen: --> irq=16
>    >    xen_set_ioapic_routing: irq 16 gsi 16 vector 152 ioapic 0 pin 16
>    triggering 1
>    >    polarity 1
>    >    radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>    >    radeon 0000:01:00.0: setting latency timer to 64
>    >    [drm] radeon: Initializing kernel modesetting.
>    >    [drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon,
>    disabling
>    >    IOCTL
>    >    radeon 0000:01:00.0: PCI INT A disabled
>    >    radeon: probe of 0000:01:00.0 failed with error -22
>    >
> 
>    I guess this is some other problem then.. you might want to enable more
>    debugging options for drm to see what actually goes wrong.
> 
>    Basicly you should extract the initrd image, and change the "modprobe drm"
>    line to say "modprobe drm debug=255" in the init script. And then
>    repack the initrd and use the modified initrd instead.
> 
>    Does it work with "nomodeset" btw?
> 
>    -- Pasi