| View previous topic :: View next topic |
| Author |
Message |
Joseph_sys
Advocate
Joined: 08 Jun 2004
Posts: 2712
Location: Edmonton, AB
|
 Posted: Mon Jan 03, 2011 2:59 am Post subject: [SOLVED]another victim of Xorg 1.9 (intel i915) "X" |
 |
|
It seems to me I'm another victim of Xorg 1.9
Have VGA Intel Corporation 82945G/GZ Integrated Graphics Controller
driver: i915
| Code: | [ 31.582] (II) Module dri2: vendor="X.Org Foundation"
[ 31.582] compiled for 1.9.2, module version = 1.2.0
[ 31.582] ABI class: X.Org Server Extension, version 4.0
[ 31.582] (II) Loading extension DRI2
[ 31.582] (==) Matched intel as autoconfigured driver 0
[ 31.583] (==) Matched vesa as autoconfigured driver 1
[ 31.583] (==) Matched fbdev as autoconfigured driver 2
[ 31.583] (==) Assigned the driver to the xf86ConfigLayout
[ 31.583] (II) LoadModule: "intel"
[ 31.644] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 31.695] (II) Module intel: vendor="X.Org Foundation"
[ 31.695] compiled for 1.9.2, module version = 2.13.0
[ 31.695] Module class: X.Org Video Driver
[ 31.695] ABI class: X.Org Video Driver, version 8.0
[ 31.695] (II) LoadModule: "vesa"
[ 31.696] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 31.710] (II) Module vesa: vendor="X.Org Foundation"
[ 31.710] compiled for 1.9.2, module version = 2.3.0
[ 31.710] Module class: X.Org Video Driver
[ 31.710] ABI class: X.Org Video Driver, version 8.0
[ 31.710] (II) LoadModule: "fbdev"
[ 31.735] (WW) Warning, couldn't open module fbdev
[ 31.735] (II) UnloadModule: "fbdev"
[ 31.735] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 31.735] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
Sandybridge, Sandybridge
[ 31.737] (II) VESA: driver for VESA chipsets: vesa
[ 31.737] (++) using VT number 7
[ 31.737] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[ 31.737] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[ 31.742] (WW) Falling back to old probe method for vesa
[ 31.742] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 31.746] (EE) intel(0): No kernel modesetting driver detected.
[ 31.746] (II) UnloadModule: "intel"
[ 31.746] (EE) Screen(s) found, but none have a usable configuration.
[ 31.747]
Fatal server error:
[ 31.747] no screens found |
| Code: | dmesg | grep -i -e fb -e drm -e i915 -e agp -e kms
[ 0.000000] Command line: root=/dev/sda3 i915.modeset=0 acpi_enforce_resources=lax
[ 0.000000] Kernel command line: root=/dev/sda3 i915.modeset=0 acpi_enforce_resources=lax
[ 0.000000] No AGP bridge found
[ 0.460792] Linux agpgart interface v0.103
[ 0.461041] agpgart-intel 0000:00:00.0: Intel 945G Chipset
[ 0.461496] agpgart-intel 0000:00:00.0: detected 7932K stolen memory
[ 0.464664] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0x80000000
[ 0.473297] [drm] Initialized drm 1.1.0 20060810
[ 0.5Symbol: XEN_FBDEV_FRONTEND [=n]01812] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 |
Where is the module fbdev in the kernel driver is looking for?
It seems to me I have "fb" in the kernel:
| Code: | Symbol: XEN_FBDEV_FRONTEND [=n]
Prompt: Xen virtual frame buffer support
Defined at drivers/video/Kconfig:2064
Depends on: HAS_IOMEM && FB && XEN
Location:
-> Device Drivers
-> Graphics support
-> Support for frame buffer devices (FB [=y])
Selects: FB_SYS_FILLRECT && FB_SYS_COPYAREA && FB_SYS_IMAGEBLIT && FB_SYS_FOPS && FB_DEFERRED_IO
|
Last edited by Joseph_sys on Mon Jan 03, 2011 4:24 am; edited 1 time in total |
|
| Back to top |
|
 |
Logicien
Veteran
Joined: 16 Sep 2005
Posts: 1555
Location: Montréal
|
| Posted: Mon Jan 03, 2011 3:46 am Post subject: |
|
|
Hi,
first, you have to pass
as kernel parameter for i915 kernel support configure framebuffer modesetting at boot time. You can just remove the parameter if it is set by default in the kernel. As I know, the Xorg intel driver do not work without modesetting. Otherwise, you've gone probably have the vesafb as framebuffer driver if it is set in the kernel. Using i915 for framebuffer modesetting insure you to have native display resolution for console and characters terminals.
I suggest as a possible workaround to use the fbdev Xorg driver only if you have problems with the Xorg intel driver and you cannot resolv the problem. If the kernel side i915 work, you can keep a minimum 3D acceleration. To be able to set the fbdev driver, first, you have to emerge it. Xorg log say it is not installed. Then, you will have to set it as the graphic driver in the
| Code: | Section "Device"
driver "fbdev"
EndSection |
of a custom /etc/X11/xorg.conf or in a file in the subdirectory /etc/X11/conf.d/
_________________
Paul |
|
| Back to top |
|
|
Joseph_sys
Advocate
Joined: 08 Jun 2004
Posts: 2712
Location: Edmonton, AB
|
| Posted: Mon Jan 03, 2011 4:23 am Post subject: |
|
|
| Logicien wrote: | Hi,
first, you have to pass
as kernel parameter for i915 kernel support configure framebuffer modesetting at boot time. You can just remove the parameter if it is set by default in the kernel. As I know, the Xorg intel driver do not work without modesetting. Otherwise, you've gone probably have the vesafb as framebuffer driver if it is set in the kernel. Using i915 for framebuffer modesetting insure you to have native display resolution for console and characters terminals.
[snip]
|
You are correct, thank you.
I had it set "i915.modeset=0" setting it to 1 and "X" boots OK |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
