similar to: mgag200 driver does not work properly with Xen

Completely fresh,virgin install of b115 SXCE ,zero modifications done. If select XVM from boot menu,it comes all the way till "Starting Desktop login on Display:0..." and reboots. Regular Solaris(not XVM) boots fine. Intel XEON CPU,8G RAM Intel S3210SHLX motherboard(http://www.intel.com/Products/Server/Motherboards/Entry-S3200SH/Entry-S3200SH-overview.htm) Please help and thanks a lot

hi fyi, it seems redhat has just pushed RHEL 5.7 out. I see amoung others: kernel-2.6.18-274.el5.x86_64.rpm redhat-release-5Server-5.7.0.3.x86_64.rpm Rainer

QCOW2 disk image gets corrupted when you try to install Service Pack 1 AFTER installing GPLPV drivers. This means, without the pv drivers, everything works fine. I tested both RAW and QCOW2 without GPLPV drivers and the installation has completed without any error, and the image (at least qcow2) has no errors too. How to reproduce: - Install Windows 7 32-bit guest - Check the image with

John R Pierce wrote: > On 7/26/2016 10:20 AM, Fawzy Ibrhim wrote: >> I want to install Centos 7 latest build on NEC Server 5800/120b-2. >> >> The installation wizard fails to detect the storage connected to LSI >> SATA MegaRaid PCI. > > which megaraid card? they've made quite a lot. lspci will list the > card type... > > linux will only see storage

On 7/28/2016 3:41 PM, Fawzy Ibrahim wrote: > LSI SATA MEGARAID 95Q9 afaik, the megaraid cards are mostly all SAS, which support SATA drives, except very old ones were SCSI. Ok, I do see they had a series of MegaRAID SATA 150-xx and 300-xx cards, these were 64 bit PCI or PCI-X cards. 95Q9 does not appear to be a valid card number, 9240, 9260, 9280 are some pci-express SAS MegaRaid

select isn't recursive, so we can't turn on DRM_TTM + DRM_TTM_HELPER in config DRM_VRAM_HELPER, we have to select them on the vram users instead. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/Kconfig | 2 -- drivers/gpu/drm/ast/Kconfig | 2 ++ drivers/gpu/drm/bochs/Kconfig | 2 ++

This patch replaces mgag200's framebuffer console with DRM's generic implememtation. All respective code is being removed from the driver. The console is set up with a shadow buffer. The actual buffer object is not permanently pinned in video ram, but just another buffer object that the driver moves in and out of vram as necessary. The driver's function mga_crtc_do_set_base() used to

Because it is. Huge congrats to everyone who made this kind of refactoring happen! Signed-off-by: Daniel Vetter <daniel.vetter at intel.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Gerd Hoffmann <kraxel at redhat.com> Cc: virtualization at lists.linux-foundation.org --- MAINTAINERS | 2 +- drivers/gpu/drm/Kconfig | 2 --

Because it is. Huge congrats to everyone who made this kind of refactoring happen! Signed-off-by: Daniel Vetter <daniel.vetter at intel.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Gerd Hoffmann <kraxel at redhat.com> Cc: virtualization at lists.linux-foundation.org --- MAINTAINERS | 2 +- drivers/gpu/drm/Kconfig | 2 --

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

The mgag200 driver uses an empty implementation for its encoder. Replace the code with the generic simple encoder. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/mgag200/mgag200_drv.h | 7 --- drivers/gpu/drm/mgag200/mgag200_mode.c | 60 +------------------------- 2 files changed, 2 insertions(+), 65 deletions(-) diff --git

This patch proposes to remove the XEN_PRIVILEGED_GUEST kernel configuration parameter defined in arch/x86/xen/Kconfig, but used nowhere in the makefiles and source code. This dummy parameter was added 3 years back, and it may make sense to remove it now, as the reasons to use it were not very clear. Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com> ---

This patch proposes to remove the XEN_PRIVILEGED_GUEST kernel configuration parameter defined in arch/x86/xen/Kconfig, but used nowhere in the makefiles and source code. This dummy parameter was added 3 years back, and it may make sense to remove it now, as the reasons to use it were not very clear. Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com> ---

This patch proposes to remove the XEN_PRIVILEGED_GUEST kernel configuration parameter defined in arch/x86/xen/Kconfig, but used nowhere in the makefiles and source code. This dummy parameter was added 3 years back, and it may make sense to remove it now, as the reasons to use it were not very clear. Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> Reviewed-by:

--- drivers/gpu/drm/mgag200/mgag200_mode.c | 8 -------- 1 file changed, 8 deletions(-) diff --git a/drivers/gpu/drm/mgag200/mgag200_mode.c b/drivers/gpu/drm/mgag200/mgag200_mode.c index dc13c48..af8b4c1 100644 --- a/drivers/gpu/drm/mgag200/mgag200_mode.c +++ b/drivers/gpu/drm/mgag200/mgag200_mode.c @@ -1479,13 +1479,6 @@ void mga_crtc_fb_gamma_get(struct drm_crtc *crtc, u16 *red, u16 *green,