fb: conflicting fb hw usage intel drmfb vs VESA VGA removing generic driver

[TO]

fb: conflicting fb hw usage intel drmfb vs VESA VGA removing generic driver

above mysterious (4 me) msg appears at boot after i specify the PCLOS partition (double-boot with a Win XP Pro in the beginning of a newly purchased blanked Hitachi hts 7220 ata hdd).
Laptop Dell Latitude D830 core2 duo cpu t7500 @ 2.2 ghz
PCLinuxOS 2011 (issued Sept 23) fresh download, slightly customised.

As a resullt all stuff on display is MICROSCOPIC, the message itself too and flashes fast so it needs to be re-read many times to write down.

Being a senior, self-taught and not competent in COMMAND LINE "stuff" i am not sure how to solve this; by ZOOMING the FFox page and others i still can do some work and i am sure the DeskTop Configurations are ... the usual; the WinXPpro display was of normal appearance ... before all of a sudden now it gives me a BlueSOD with a "memory dump" check  = uncomprehensible too.

Pls hlp. Thx, rgds

[Hootiegibbon]

fb: conflicting fb hw usage intel drmfb vs VESA VGA removing generic driver

<snip>
..the WinXPpro display was of normal appearance ... before all of a sudden now it gives me a BlueSOD with a "memory dump" check  = uncomprehensible too.

Pls hlp. Thx, rgds

All the first statement is saying is that a more suitable frambuffer driver was located and used, so the generic one is discarded - it sets the framebuffer to the native resolution for the card/monitor

It does not affect the graphical appearance of "X" - this is set by using "configure my computer" > hardware > graphics driver and adjusting the resolution used -

This is all unrelated to teh BSOD - which will be caused by a windows issue .

Jase

[AndrzejL]

This is all unrelated to teh BSOD - which will be caused by a windows issue .

Jase

A big +1. Linux and windows are installed separately and the only common thing that they are using is the bootloader. This will not cause a BSOD. Windows issues will do that ie. bad driver, bug in the software...

Regards.

[TO]

YES!
Indeed " ... this is set by using "configure my computer" > hardware > graphics driver and adjusting the resolution used - ..." this short and much to the point instruction was sufficient, Thx!
I learned from the settings F2 at boot that my Flat Panel 15.4" UXGX is 1920 by 1200 NATIVE; then adjusted the resolution accordingly and now what is on screen is not MICROscopic and is perfectly adjustable by Desktop Configuration tools.
However the mysterious msg still keeps flashig at every boot, so annoying ... well ... thx, best rgds, TO 

[AndrzejL]

However the mysterious msg still keeps flashig at every boot, so annoying ... well ... thx, best rgds, TO 

This is not an error but more of an information. It can be ignored - really I have it here too.

Regards.

[lightning slinger]

However the mysterious msg still keeps flashig at every boot, so annoying ... well ... thx, best rgds, TO 

This is not an error but more of an information. It can be ignored - really I have it here too.

Regards.

I have it too on my laptop running Xfce, just ignore it!

[Hootiegibbon]

When the operating system boots up, the kernel will probe for whether a framebuffer is available, it will assign the vesa-framebuffer module to this (or the fbdev framebuffer module) if however there is a dedicated frame buffer module found available during the probe it will replace the generic (vesa/fbdev) with the more appropriate framebuffer option.

available framebuffer options are

cirrusfb == Accelerated FBDev driver for Cirrus Logic chips
gxfb == Framebuffer driver for the AMD Geode GX
gx1fb == Framebuffer driver for the AMD Geode GX1
intelfb == Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets
pm2fb == Framebuffer driver for Permedia2 devices
savagefb == Framebuffer driver for S3 Savage PCI/AGP Chips
nvidiafb == Framebuffer driver for nVidia graphics chipset
cyber2000fb == Framebuffer driver for CyberPro 2000, 2010 and 5000
hgafb == Framebuffer driver for Hercules Graphics Adaptor
i2c-matroxfb == Support module providing I2C buses present on Matrox videocards
kyrofb == Framebuffer driver for STMicroelectronics
vga16fb == Framebuffer driver for standard vga
radeonfb == Framebuffer driver for ATI Radeon chipset
aty128fb == Framebuffer driver for ATI Rage128 / Pro cards
atyfb == Framebuffer driver for ATI Mach64 cards
cyblafb == Framebuffer driver for Cyberblade/i1 graphics core
tdfxfb == Framebuffer driver for 3Dfx devices
sisfb == Framebuffer driver for SiS 300/540/630/730/315/55x/65x/661/74x/330/76x/34x, XGI V3XT/V5/V8/Z7
arcfb == Framebuffer driver for Arc monochrome LCD board
neofb == Framebuffer driver for NeoMagic PCI Chips
s1d13xxxfb == Framebuffer driver for S1D13xxx devices
vfb == Framebuffer driver for virtual fb
i810fb == Framebuffer device for the Intel 810/815 and compatible cards
sstfb == Framebuffer driver for 3dfx Voodoo Graphics and Voodoo2 based video boards
tridentfb == Framebuffer driver for Trident cards

ok next question is what is a framebuffer and what is the Linux-Framebuffer

With the use of the framebuffer you can present graphical content without using "X".

that line of text is informational and can be necessary for troubleshooting.

Jase   

[TO]

WOW!
Impressive. This science goes FAR beyound my modest level as an user. Thanks a lot, ppl, now size solved, i am all set.