search for: fb_vesa

Displaying 5 results from an estimated 5 matches for "fb_vesa".

2010 May 28
0
xen 4.0.0 dom0 console video unreadable / scrambled
...1 lapic apic_verbosity=debug apic=debug iommu=off module /boot/linux-2.6.32-xen-r1-a ro root=/dev/sda3 console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10 I have an intel 82915G/GV/910GL graphics card so I configured AGP_INTEL, DRM, FB, FB_BOOT_VESA_SUPPORT, FB_VGA16, FB_UVESA, FB_VESA, VGA_CONSOLE, FONTS, FRAMEBUFFER_CONSOLE, and DUMMY_CONSOLE into the kernel. What am I missing or screwing up? Thanks. -mike d. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2014 Nov 03
0
[PATCH v4 10/10] x86: Support compiling out userspace IO (iopl and ioperm)
...the patch series respun to add that select in patch 10/10, or would you consider it sufficient to add that in a followup patch, since the kernel will build and boot either way (so it won't break bisection)? Related to that: Is it intentional that FB_UVESA doesn't depend on X86, even though FB_VESA does? Does v86d run on non-x86 hardware via emulation? If so, should FB_UVESA have "select X86_IOPORT if X86"? - Josh Triplett
2007 May 15
3
GRUB and vga=788
Hi, On a minimal (e. g. without X) server install, one of the first things I do is add 'vga=788' to the 'kernel' line in /boot/grub/menu.lst, so I can use the framebuffer in 800x600 mode and have a better readability in console mode. However, I tried this on my minimal CentOS 5 install, and right after GRUB, the screen just blanks. I add that this (test) machine ran maybe a
2014 Nov 03
2
[PATCH v4 10/10] x86: Support compiling out userspace IO (iopl and ioperm)
> > This isn't unreasonable but there are drivers with userspace helpers that > > use iopl/ioperm type functionality where you should be doing a SELECT of > > X86_IOPORT. The one that comes to mind is the uvesa driver. From a quick > > scan it may these days be the only mainstream one that needs the select > > adding. > > Should kernel drivers really
2014 Nov 03
2
[PATCH v4 10/10] x86: Support compiling out userspace IO (iopl and ioperm)
> > This isn't unreasonable but there are drivers with userspace helpers that > > use iopl/ioperm type functionality where you should be doing a SELECT of > > X86_IOPORT. The one that comes to mind is the uvesa driver. From a quick > > scan it may these days be the only mainstream one that needs the select > > adding. > > Should kernel drivers really