On 08/06/2010 11:32 AM, Jos Vos wrote:
> Hi,
>
> I have a problem with an IBM point-of-sale system with an Intel 82Q35
> graphics chipset that does not work in RHEL6/F13, but that does work
> fine on SLED 11 !!! That system has a 15" display attached and also
> a VGA port for a second display (to which I have connected a monitor).
>
> This is the dmesg output on F13 with one comment inserted:
>
> [...]
> usb 1-5.2: new full speed USB device using ehci_hcd and address 3
> usb 1-5.2: New USB device found, idVendor=05ba, idProduct=000a
> usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-5.2: Product: U.are.U® 4500 Fingerprint Reader
> usb 1-5.2: Manufacturer: DigitalPersona, Inc.
> usb 1-5.2: SerialNumber: {3740B292-0CE7-0C45-BFC2-5053D2C76391}
> fbcon: inteldrmfb (fb0) is primary device
> ###### HERE THE CONSOLE SWITCHES FROM PRIMARY TO SECONDARY DISPLAY !!! ######
> Console: switching to colour frame buffer device 160x64
> fb0: inteldrmfb frame buffer device
> registered panic notifier
> No ACPI video bus found
> [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
> [...]
>
> The dmesg output on SLED 11 (kernel 2.6.27.19) as far as related to
> the framebuffer part looks as follows:
>
> [...]
> vesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 6144k, total 8128k
> vesafb: mode is 1024x768x16, linelength=2048, pages=0
> vesafb: scrolling: redraw
> vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
> bootsplash 3.1.6-2004/03/31: looking for picture...
> bootsplash: silentjpeg size 57853 bytes
> bootsplash: ...found (1024x768, 31742 bytes, v3).
> Console: switching to colour frame buffer device 124x44
> fb0: VESA VGA frame buffer device
> [...]
>
> On F13, I can avoid the video switcthing with the "nomodeset" kernel
> parameter, but after that X can not be started at all.
>
> The same problem occurs with anaconda, BTW, so it also switches to
> the second display on F13/RHEL6, while a graphical install on the
> primary display is working fine for SLED11.
>
> I have the complete dmesg output of both F13 and SLED11, if needed.
>
> Any help is appreciated.
Without being an expert, it looks like SLED11 is using vesa, and F13 is
trying to use the intel driver... tell fedora to use vesa and it should
'work'. Though I'm guessing that the xorg folks may want to get the
actual intel driver working better...
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
