Re: Intel 82Q35 / framebuffer problem
On Fri, 2010-08-06 at 23:12 +0200, Jos Vos wrote: On Fri, Aug 06, 2010 at 04:41:33PM -0400, Adam Jackson wrote: This is almost certainly the root of the problem. We don't try to set up SDVO devices if they're not listed in the VBT, but not having a VBT means nothing's gonna be listed. We'll need the output from: # dd if=/dev/mem of=/tmp/rom bs=64k skip=12 count=1 Should I attach it to the bug? In what format? Preferably as a series of bytes. (To be clear, the output from that command is the resulting /tmp/rom file, not the 1+0 records in/out message on stdout.) - ajax signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Intel 82Q35 / framebuffer problem
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 :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 0xd000, mapped to 0xf888, 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.
Thanks,
--
--Jos Vos j...@xos.nl
--X/OS Experts in Open Systems BV | Phone: +31 20 6938364
--Amsterdam, The Netherlands| Fax: +31 20 6948204
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Intel 82Q35 / framebuffer problem
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 :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 0xd000, mapped to 0xf888, 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@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Intel 82Q35 / framebuffer problem
On Fri, Aug 06, 2010 at 12:27:52PM -0600, Nathanael D. Noblet wrote: 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... Not it is not using vesa for X, SLED11 is using the intel driver: Section Device BoardNameQ35 Driver intel Identifier Device[0] Option monitor-VGA Monitor[0] VendorName Intel EndSection And it does even handle both displays properly. After some googling, and seeing the openSUSE 11.3 has the same problem, I'm afraid the issue is related to kernel mode setting (but I'm not an expert in that area) and this is messing up things for this specific configuration. -- --Jos Vos j...@xos.nl --X/OS Experts in Open Systems BV | Phone: +31 20 6938364 --Amsterdam, The Netherlands| Fax: +31 20 6948204 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Intel 82Q35 / framebuffer problem
On Fri, Aug 06, 2010 at 03:26:16PM -0400, Adam Jackson wrote: intel-...@lists.freedesktop.org would be the place to go for this. As a guess, you've got LVDS attached over SDVO and we screwed that up again. I'm happy to do that, but I hope you don't mind that in the meantime I'll also file a bug against RHEL6 (and there dmesg output looks even more scary). Should such a bug then be filed against xorg-x11-drv-intel? Furthermore, given your guess, would there be a workaround? FWIW, I also see: [drm] set up 7M of stolen space [drm:intel_init_bios] *ERROR* VBT signature missing [drm] failed to find VBIOS tables -- --Jos Vos j...@xos.nl --X/OS Experts in Open Systems BV | Phone: +31 20 6938364 --Amsterdam, The Netherlands| Fax: +31 20 6948204 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Intel 82Q35 / framebuffer problem
On Fri, 2010-08-06 at 22:18 +0200, Jos Vos wrote: On Fri, Aug 06, 2010 at 03:26:16PM -0400, Adam Jackson wrote: intel-...@lists.freedesktop.org would be the place to go for this. As a guess, you've got LVDS attached over SDVO and we screwed that up again. I'm happy to do that, but I hope you don't mind that in the meantime I'll also file a bug against RHEL6 (and there dmesg output looks even more scary). Should such a bug then be filed against xorg-x11-drv-intel? Yeah. Furthermore, given your guess, would there be a workaround? Not really. FWIW, I also see: [drm] set up 7M of stolen space [drm:intel_init_bios] *ERROR* VBT signature missing [drm] failed to find VBIOS tables This is almost certainly the root of the problem. We don't try to set up SDVO devices if they're not listed in the VBT, but not having a VBT means nothing's gonna be listed. We'll need the output from: # dd if=/dev/mem of=/tmp/rom bs=64k skip=12 count=1 - ajax signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Intel 82Q35 / framebuffer problem
On Fri, Aug 06, 2010 at 04:41:33PM -0400, Adam Jackson wrote: This is almost certainly the root of the problem. We don't try to set up SDVO devices if they're not listed in the VBT, but not having a VBT means nothing's gonna be listed. We'll need the output from: # dd if=/dev/mem of=/tmp/rom bs=64k skip=12 count=1 Should I attach it to the bug? In what format? -- --Jos Vos j...@xos.nl --X/OS Experts in Open Systems BV | Phone: +31 20 6938364 --Amsterdam, The Netherlands| Fax: +31 20 6948204 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
