similar to: [Bug 84285] New: Framebuffer display around grabbing cursor

https://bugs.freedesktop.org/show_bug.cgi?id=101447 Bug ID: 101447 Summary: Nouveau on GP106 can't work with another framebuffer drivers (possibly uvesafb) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority:

Cursor always blinks in the left top corner, make the current entered line in the console text can''t be seen immediately! Who can explain this? Thx Andrew Liu _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

https://bugs.freedesktop.org/show_bug.cgi?id=92178 Bug ID: 92178 Summary: nouveau framebuffer fails to initialize properly on GeForce 2 Go (NV11M) Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium

I am trying to hook up linux to an LCD 1333x768 LCD TV. XP in 1024x768 show up just fine. X does not. I have set the screen preferences to 1024x768. I have edited the xorf.conf file instead of have a range from 50 - 70 I change it to be only 60. I start X and it still comes up on my A70F monitor but still will not show on my LCD TV. xvidtune does not run on this PC. It says something about

While rebooting my computer after installing the new kernel a few minutes ago, I got to wondering about how the initial bootup screen (after grub, before rhgb) is constructed. The "Loading kernel blah blah blah" lines start at the top of the screen and proceed to scroll down as one would expect. But "kernel alive" shows up at the bottom of the screen and then more write-up is

Hi list After I install xen4.0 in my debian squeezz,it added the following lines into /boot/grub/grub.cfg ### BEGIN /etc/grub.d/20_linux_xen ### menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64'' --class debian --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set

I'm still using CentOS 4.6, but have been planning an upgrade to CentOS 5 for quite a while. One of the things that was holding me back is that the CentOS 5.0 kernel did not have the framebuffer support enabled by default. So I waited for CentOS 5.1. However, on one of my test systems I ran into the bad NFS performance issue (see CentOS bug 2635), so I plan to use the centosplus

Hi all, I''m trying hard to get a framebuffer console on a dom0 (Ubuntu 7.04/Debian Etch with (virtual)framebuffer support compiled it + Xen3.1) and already tried different tutorials, e.g. starting dom0 with kernel parameters - "xencons=xvc console=xvc0 console=tty1" or - "xencons=ttyS0 console=ttyS0 video=xenfb" and appending "S0:2345:respawn:/sbin/mingetty

Hi all, I''m trying hard to get a framebuffer console on a dom0 (Ubuntu 7.04/Debian Etch with (virtual)framebuffer support compiled it + Xen3.1) and already tried different tutorials, e.g. starting dom0 with kernel parameters - "xencons=xvc console=xvc0 console=tty1" or - "xencons=ttyS0 console=ttyS0 video=xenfb" and appending "S0:2345:respawn:/sbin/mingetty

Hello everyone, i use the noveau framebuffer device in kernel version 2.6.37.6. my graphic adapter is a msi 9500gt, connected to a Barco CRT projector. The Barco will only accept RGB signals with a negative sync. Is there a kernel command line parameter to force negative sync polarity? Or is there a user space command to set framebuffer parameters, fbset does'nt work with nouveau frame

Greetings! I have installed xen-4.0 with kernel 2.6.32 on a gentoo box. Everything works perfectly, except one tiny detail. I do not have X installed on the machine, so I configured the (old, non-xen) kernel to use a framebuffer, so that I don''t have to cope with the ugly 80x25 resolution, especially on a 19" display. Unfortunately, with the xen kernel, dom0 now uses the 80x25 mode

On Tue, 9 Apr 2019 at 17:12, kraxel at redhat.com <kraxel at redhat.com> wrote: > > Hi, > > > If not for TTM, what would be the alternative? One VMA manager per > > memory region per device? > > Depends pretty much on the device. > > The cirrus is a display device with only 4 MB of vram. You can't fit > much in there. A single 1024x768 @ 24bpp

https://bugs.freedesktop.org/show_bug.cgi?id=33728 Summary: Framebuffer and Xorg display distorted only at monitor's native resolution Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

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

https://bugs.freedesktop.org/show_bug.cgi?id=39495 Summary: MX440-8X TV-detect/framebuffer problem Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hi, > If not for TTM, what would be the alternative? One VMA manager per > memory region per device? Depends pretty much on the device. The cirrus is a display device with only 4 MB of vram. You can't fit much in there. A single 1024x768 @ 24bpp framebuffer needs more 50% of the video memory already. Which is why the cirrus driver (before the rewrite) had to migrate buffers from/to

Hi, > If not for TTM, what would be the alternative? One VMA manager per > memory region per device? Depends pretty much on the device. The cirrus is a display device with only 4 MB of vram. You can't fit much in there. A single 1024x768 @ 24bpp framebuffer needs more 50% of the video memory already. Which is why the cirrus driver (before the rewrite) had to migrate buffers from/to

http://bugs.freedesktop.org/show_bug.cgi?id=26812 Summary: [lbm-drm:drm_mode_getfb] *ERROR* invalid framebuffer id Product: xorg Version: unspecified Platform: Other URL: https://bugs.edge.launchpad.net/ubuntu/+source/xserver- xorg-video-nouveau/+bug/529842 OS/Version: All Status: NEW

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

When I turn on the "Framebuffer console support" in compiling kernel, after system startup, the console doesn''t work properly and the kernel parameter( for example: vga=719) doesn''t do any effect on kernel. who can help me ? thanks in advance! Andrew Liu _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com