similar to: Xen and x11

Hi, I''m not certain whether this belongs in ''users'' or ''devel'', the topic appears to turn up in both lists. I''ve started here on the assumption that it already works and I''ve missed something :) What we''d like to do is run several independant X11''s on a single CPU box. Using on-board (AGP) graphics, and additional

Hi all, I am trying to execute Xserver on Dom0 but an error occurres. I have a fresh Debian Lenny install. I''ve installed Xen via aptitude, restarted the system with Xen kernel, and then installed xfce4 with all dependencies. When i try startx i get this errors: (WW) RADEON; No matching Device section for instalnce (BusID PCI:4:0:1) found Fatal server error: xf86MapVidMem:

Hello, I compiled xen on ubuntu, but at the bot i got the kernel panic message. I enabled the support to ext4 fs. This is kernel panic error: EXT3-fs: unable to read superblock ETX4-fs (md0): unable to read superblock FAT: unable to read boot vector Kernel panic - not syncing: VFS: Unable to read superblock(9,8) My grub.cfg generated by update-grup: menuentry ''Ubuntu, with Linux

Hello, someone used trixbox domU with xen? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

https://bugs.freedesktop.org/show_bug.cgi?id=80675 Priority: medium Bug ID: 80675 Assignee: nouveau at lists.freedesktop.org Summary: KMS FB hand-over: no/black console on Nvidia MCP78S/C77/GeForce 8300 (10de:0848), X11 ok QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

https://bugs.freedesktop.org/show_bug.cgi?id=97505 Bug ID: 97505 Summary: X11 does not detect nouveau when using the linux kernel EFI Loader (GRUB loader works fine) Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

Hi, everyone, I installed the Xen3.1.0 based on Fedora8 and enter the Dom0 successfully. The kernel of dom0 is linux-2.6.18-xen0. But the Xorg could not start in the Dom0. When I use the "startx" command to start the X server, the error information is following: ......... (==) Using config file: "etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in

Try booting with drm_kms_helper.drm_fbdev_overalloc=200 and see if it works with that. (There's also CONFIG_DRM_FBDEV_OVERALLOC which sets the default.) Cheers, -ilia On Sun, Jul 5, 2020 at 3:41 PM <michael at michaelkloos.com> wrote: > > I am not familiar with that setting, but I have really struggled to find documentation on dealing with the framebuffer. Referring to this

Check fb_pan_display in drivers/video/fbdev/core/fbmem.c for the argument validation of the FBIOPAN_DISPLAY ioctl. CONFIG_FB_NVIDIA is a dedicated fbdev driver, not compatible with nouveau (it takes over the relevant PCI device). It also won't support your Pascal GPU, I believe -- I think it MIGHT support the Tesla generation (i.e. G80..GT21x) but definitely not anything newer. Most likely it

<div dir='auto'>I am not familiar with that setting, but I have really struggled to find documentation on dealing with the framebuffer. Referring to this guide, "http://betteros.org/tut/graphics1.php#doublebuffer", I attempted to set the mmap allocation size to double, but it caused the mmap to fail. I no longer believe that it is a driver issue, though, because I just

Hi all, I am running CentOS 7 on a NUC5CPYB. Intel video: 00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35) When I take a screen shot I get "different" things. I use: export DISPLAY=:0.0 /usr/bin/xwd -silent -root -out screen; convert screen screen.png I tried import also for the screen

This patch changes DRM clients to not map the buffer by default. The buffer, like any buffer object, should be mapped and unmapped when needed. An unmapped buffer object can be evicted to system memory and does not consume video ram until displayed. This allows to use generic fbdev emulation with drivers for low-memory devices, such as ast and mgag200. This change affects the generic framebuffer

On Thu, Apr 04, 2019 at 12:58:09PM +1000, David Airlie wrote: > On Wed, Apr 3, 2019 at 5:23 PM Gerd Hoffmann <kraxel at redhat.com> wrote: > > > > Time to kill some bad sample code people are copying from ;) > > > > This is a complete rewrite of the cirrus driver. The cirrus_mode_set() > > function is pretty much the only function which is carried over

Hi, I''ve been having troubles with bridge networking in Xen3. RHEL4 is running in dom0 and Debian sarge in domU. Both domains get their IPs from an external DHCP server. dom0 starts up OK and gets its IP from the server. (all networking services work fine; in and out) domU starts up OK and sometimes gets its IP while sometimes fails to get the IP. In any case, after logging into domU

Well...it's been a bit of a mixed bag.? Setting drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to 2160 as opposed to 1080 (My monitor vertical resolution)? This fixed the mmap() problem.? However, it only worked on my main workstation.? My laptop running Intel graphics wasn't affected by the change in kernel cmdline.? My workstation is a custom build from a few

Hi, Xen wiki states that using linux 3.0 and above as dom0 works with all graphics cards. I could install the fglrx graphics driver on my desktop machine with a discrete graphics card (Radeon HD 5870), but I see a blank screen while loading fglrx on my AMD Fusion E350 machine with integrated graphics card (Radeon HD 6310). The graphics driver loads fine when the Linux kernel runs alone not as

Oops, the FBIOPAN_DISPLAY ioctl error was a stupid mistake on mistake on my part.? Thanks for the info on where the validation code was.? Comparing against that made it easy to find the mistake.? It's working now, well...where I have been able to get over-allocation working!? Thanks for the help.? If I can't get the over-allocation to work on my other systems, I'll take it up in

Hello, we have the problem: We run 7 blades with a xen 3.0.1tha3 configuration (with the patches for debian from debianbase.de), which a is xenisied 2.6.12.6-kernel. Everything runs fine until we start producing heavy load on the network (e.g. multiple clients access our maxdb database), the dom0 and the domU network becomes unreachable (i.e. only every 100th-200th ping gets through).

Does NOUVEAU support mmaping a double-sized Framebuffer? When attempting to run, where fd refers to "/dev/fb0": mmap(ptr, screensize * 2, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); I get back an invalid argument error. This doesn't happen if I only request a single screensize. Is this a limitation of the driver? -------------- next part -------------- An HTML attachment was

On Thu, Feb 28, 2019 at 10:47:41AM -0600, Joshua Watt wrote: > Reports the size of the virtgpu framebuffer to userspace and installs > the deferred I/O handlers so that userspace can mmap() and write to it. Fixed already, as side effect of switching virtio to the generic fbdev emulation. Patches are in the drm-misc-next branch and should land upstream in the 5.1 merge window. cheers,