Re: conflict of hyperv_fb and the generic video driver?

[David Herrmann <dh.herrmann@gmail.com>]

Hi

On Sat, Aug 17, 2013 at 1:04 AM, Haiyang Zhang <haiyangz@microsoft.com> wrote:
>> > But I saw VESA VBE in the x log. Seems it's the default driver:
>> > "/var/log/Xorg.0.log":
>> > [    12.340] (II) VESA(0): Primary V_BIOS segment is: 0xc000
>> > [    12.341] (II) VESA(0): VESA BIOS detected
>> > [    12.341] (II) VESA(0): VESA VBE Version 2.0
>> > [    12.341] (II) VESA(0): VESA VBE Total Mem: 4096 kB
>> > [    12.341] (II) VESA(0): VESA VBE OEM: IBM SVGA BIOS, (C) 1993
>> International Business Machines
>> > [    12.341] (II) VESA(0): VESA VBE OEM Software Rev: 0.0
>> > [    12.365] (II) VESA(0): Creating default Display subsection in Screen
>> section
>> >         "Default Screen Section" for depth/fbbpp 24/32
>> > [    12.365] (=) VESA(0): Depth 24, (--) framebuffer bpp 32
>> > [    12.365] (=) VESA(0): RGB weight 888
>> > [    12.365] (=) VESA(0): Default visual is TrueColor
>> > [    12.365] (=) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
>> >
>> > There is no  /dev/fb*,  /dev/dri/, /sys/class/drm I see
>> > /sys/class/graphics/fbcon is here.  But console output is not working.
>> >
>> > Seems that the VESA VBE is causing conflict with my driver... Is there
>> > any way to disable VESA VBE driver?
>>
>> This is the Xorg vesa driver. There is no way to detect that from the kernel (at
>> least no sane way). Just uninstall the vesa driver, no one uses that these days.
>> At least I see no reason why you would use it.
>> Probably named xf86-video-vesa. Or make sure your hyperv fbdev driver is
>> loaded before xorg starts and then load xf86-video-fbdev over xf86-video-
>> vesa.
>
> Removing the xorg vesa driver has solved the conflict.
>
> Also, I found adding a xorg.conf which specifies fbdev can solve the problem too:
> [root@localhost ~]# cat /etc/X11/xorg.conf
> Section "Device"
>     Identifier  "HYPER-V Framebuffer"
>     Driver      "fbdev"
> EndSection
>
> Thank you SO MUCH for the help!!

You're welcome. Good to hear it's solved now.

Cheers
David